A charger is online but the van is empty: design for dispatch failures

An online port can still miss a departure

A fleet procurement discussion on Reddit placed reliability, local controls, and support costs ahead of decorative charger features. That priority makes sense because a failed session can become a missed customer visit the next morning. A station can report online while a vehicle is not charging: the connector may not be seated, authorization may fail, a schedule may conflict, or the vehicle may have reached a user-set limit. Dispatch readiness requires evidence about energy delivery and vehicle availability. This guide begins after a departure-energy plan exists: its purpose is to detect and recover an exception before dispatch, rather than size the normal daily charging allocation.

Source: Fleet charging - best options for depot chargers?

Assign the first support call

DOE's fleet guidance includes driver training and vehicle maintenance, local servicing, and a service agreement in planning. Those responsibilities extend beyond installation warranty. The charging network may report a communications fault while the electrical contractor handles a damaged circuit, and the vehicle supplier may own a vehicle-side problem. Establish a triage path that identifies which organization takes the first call and who coordinates when the cause is uncertain. Otherwise each provider can correctly report that its own component appears healthy while the van remains unready.

Source: Alternative Fuels Data Center: Electric Vehicles for Fleets

Illustrative scenario: three different incomplete sessions

Illustrative scenario: ten vans connect at 6 p.m. One begins no session, one stops after adding only 2 kWh, and one charges normally but is assigned an earlier departure overnight. A simple green-status dashboard may miss all three operational problems. A useful evening check instead compares expected starts and minimum energy progress with the current schedule. The aim is to flag a recoverable shortfall while there are still hours left, not create a report after the shift has already begun.

Set alarms while recovery remains possible

Define alert thresholds from the actual charging plan. A low-energy alarm that fires after ten minutes may be noisy for a deliberately delayed off-peak schedule. A threshold that waits until dawn may be useless. Assign an employee or service provider to acknowledge each actionable alert and record the remedy. Include weekends, holidays, and staff absence. A spare charging bay helps only if its cable reaches, it supports the vehicle, its allocation is available, and someone can move the van safely.

Test shared failure points, not just spare ports

Test the difference between port redundancy and common-point redundancy. Two dispensers fed by the same failed controller, circuit, or communications device may both be unavailable. Conversely, an extra independent AC charger may provide a practical recovery path even when it is slower. Compare the cost of this resilience with the business cost of a missed route. Do not describe a manufacturer's hardware warranty as a guaranteed repair response unless that response is explicitly included in the agreement.

Turn an alarm into a time-bounded recovery decision

An actionable alert should identify the affected vehicle or port, the expected departure, the observed shortfall, and the time remaining for recovery. Compare two messages: charger offline and van seven has received no recorded energy since arrival and leaves at 5 a.m. The second gives operations a decision to make. It still needs verification because communications loss can interrupt reporting while charging continues. Define which observable evidence confirms an actual energy shortfall and which condition should trigger a support call rather than a vehicle move.

Build the escalation around the remaining window. Early in the evening, there may be time to investigate an authorization problem and restart a session through approved controls. Later, the most useful response may be switching a route to an already ready vehicle. At some point, a slow spare charger cannot recover the needed energy before departure. Record that point for representative routes rather than asking the night supervisor to improvise calculations under pressure. The contingency should account for driver availability, parking access, and vehicle assignments as well as charger availability.

After an incident, retain enough evidence to distinguish cause from coincidence: the relevant session times, charger identifier, vehicle state, error message, reported connectivity, and action taken. Do not repeatedly reset equipment merely to clear the screen before support can review the fault. A monthly review can group failures into connection errors, access problems, vehicle settings, hardware faults, and insufficient charging windows. Count operational impact as well as incidents. Ten quickly corrected plug-in errors and one common-controller failure that stops the entire depot should not receive the same improvement priority simply because both appear in a fault log.

Keep the incident records needed for triage

The closeout package should include a port map, charger identifiers, circuit references, support contacts, alert ownership, and an incident log template. Train drivers on a short observable check: connection, successful session indication, and the correct departure assignment. Keep electrical diagnosis and internal equipment access with qualified personnel. Review incidents monthly to distinguish repeated user errors, unreliable hardware, communications failures, and unrealistic energy targets. Each category has a different remedy; replacing chargers will not fix a dispatch schedule that never allowed enough charging time.

Put it into practice

A decision table to keep handy