smartphone, phone, charger, loading, connection, mobile, mass media, network, charger, charger, charger, charger, charger. How to test the everyday value of shared charger planning
Photo by FreePhotosART on Pixabay

Reviews

Part of Shared charger planning mistakes that cause delays

How to test the everyday value of shared charger planning

Test the plan before you build it: walk the rules through real scenarios, find the cases nobody decided, and fix them on paper instead of on site.

What to take away

  • Test the plan on paper before testing the equipment on site. It costs an hour and finds the gaps.
  • Walk ten real scenarios through your rules. Any that has no answer is a rule you have not written.
  • The scenarios that break a plan are almost always social rather than technical.
  • Do this before procurement, because the answers change what you buy.

Everyone tests the equipment. Almost nobody tests the plan, which is odd, because the plan is what residents actually experience and it is far cheaper to fix.

The method is simple. Sit down with the draft rules and walk real situations through them. Where the group cannot answer in a sentence, you have found a decision nobody made.

Ten scenarios that find the gaps

A resident's car finishes at 10pm and stays until morning. Is that allowed? Is there a fee? Who enforces it at 2am?

Ten scenarios that find gaps

  • Car finishes at 10pm, stays overnight
  • All ports busy, someone needs charge
  • Non-EV resident parks in charging bay
  • Guest asks to chargeprice and payment
  • Resident disputes a charge on bill
  • Cable damagedwho takes port offline
  • System offline for a daybilling
  • Resident moves out owing money

Every port is busy and someone needs a charge tonight. What are they supposed to do? Is there a queue, a booking, or nothing?

A resident without an electric car parks in a charging bay. Is that a violation? Of what, and who acts on it?

A guest asks to charge. Yes or no, and if yes, at what price and how do they pay?

A resident disputes a charge on their bill. Who investigates, against what record, and who can issue a refund? Answering that means deciding who may look at an individual session log, which is a policy question rather than a technical one.

A cable is damaged. Who takes the port out of service, who calls whom, and how long is acceptable?

The system is offline for a day. Does charging continue? Are those sessions billed later or lost?

A resident moves out owing money. How is that recovered, and by whom?

Two residents both claim a booked slot. What is the tie-break, and who applies it?

Demand doubles in a year. At what point do you add ports, and who decides?

If your group answers all ten in under twenty minutes, the plan is real. In practice most groups stall on three or four, and those are precisely the ones that become complaints.

The gaps are social, not technical

Notice what those scenarios have in common. Hardly any of them is about electricity.

They are about enforcement, money, fairness and who has authority at an awkward hour. Charging plans fail on those questions, and equipment vendors have no answers for them because they are not equipment questions.

This is also why the plan test has to happen before procurement rather than after. Deciding you need per-resident billing, idle fees and dispute records changes which system you buy.

Test the operating burden honestly

For each answer above, ask who does it and how often.

Who carries the operating burden?

Can a named person take several hours a month?

Yes

Name them and confirm they know

No

Choose unnetworked amenity or third-party operator

Then add it up. If the honest total is several hours a month of somebody's attention, name that person and confirm they know. A plan that quietly assumes a volunteer treasurer will administer accounts, chase idle vehicles and adjudicate disputes is not a plan.

If nobody can take it on, that is a finding, not a failure. It points you toward an unnetworked amenity model or a third-party operator, both of which remove most of the burden and move the risk somewhere else rather than deleting it.

Handbooks written for organizations hosting charging cover this operating side more fully than vendor material does. The handbook for workplace charging hosts is written for employers, and the day-to-day host responsibilities it sets out map closely onto a residential building running shared ports.

Then test the equipment

Once the plan holds, the commissioning tests are the familiar ones: every connector, every credential, price rules, offline behavior, power sharing at full occupancy, and the support path called at an inconvenient hour. Running each of those deliberately, rather than confirming the connector is live, is what separates a commissioning week from a handover.

Commissioning tests to run

  • Every connector
  • Every credential
  • Price rules
  • Offline behavior
  • Power sharing at full occupancy
  • Support path called at inconvenient hour

Run a pilot with a handful of real residents for a week or two before opening everything. Pilots find what neither the plan test nor the commissioning test can: signage nobody reads, coverage that dies below grade, a payment flow that fails on one carrier.

If you need help structuring any of this, public technical and planning resources exist and cost nothing, which is worth knowing before paying a consultant for a checklist.

Write the answers down

The output of this exercise is not a feeling that the plan is sound. It is a document: ten scenarios, ten answers, and a named owner for each action.

That document becomes the resident guide, the manager's runbook and the basis for the rules. It is also what a future board reads instead of rediscovering all of this.

Where the delays and rework come from is covered in what costs these projects time and money, and the questions worth putting to bidders become sharper once you know which scenarios your plan struggles with.

Common questions

When should we run the plan test?
Before procurement. The answers change the specification.
Who should be in the room?
Whoever will operate it, whoever approves spending, and at least one resident who is not on the board.
What if we cannot agree on a scenario?
Note it as unresolved and set a date. An unresolved question that is written down is manageable; one that is forgotten is not.
Do small installations need this?
A shorter version. Even two shared ports need answers on idle cars, guests and faults.

More in Reviews

Latest from Equipment Desk