A depot needs vehicles ready for work, not simply chargers installed in parking spaces. The charging design should begin with an energy timetable showing when vehicles arrive, what they need and when they must leave. This turns infrastructure procurement into a defined scheduling problem. It also reveals whether the proposed equipment can use the available site supply without depending on an unrealistic parking or dispatch routine.
Build the arrival picture
Record the expected return time and remaining energy for each vehicle group. Include the variation caused by late work, reassignment or a changed route. A plan based on simultaneous, predictable returns may fail even if its total daily energy calculation is correct.
Then map departure deadlines and required readiness. Vehicles sharing a depot may have different needs, so equal allocation is not necessarily the right operating rule. Explain which work has priority and how that priority changes when schedules are disrupted. The timetable should reflect dispatch decisions that staff can apply in practice.
Match energy with site capability
Establish the usable electrical capacity through the appropriate site assessment. Include other building demands and any restrictions affecting operation. The charging plan should use a defined supply assumption rather than treating the equipment's combined nameplate power as available site power.
The National Laboratory of the Rockies' EVI-X tools connect vehicle activity and infrastructure planning. That modelling perspective is useful even before choosing a particular tool. Test whether the available hours and supply can meet the departure requirements, and identify the periods when the proposed system is most constrained.
Give managed charging an operating owner
A control system can allocate power, but somebody must define and maintain the rules. Agree who updates vehicle schedules, handles an urgent departure and investigates a missed charge. A technically capable platform becomes unreliable if its inputs remain disconnected from the people assigning the work.
Specify the information drivers and depot staff need. They should know where to park, whether connection succeeded and how to report an exception. The system also needs an agreed response to unavailable equipment or lost communication, so a software problem does not leave every vehicle's next departure dependent on improvised intervention.
Design for the next deployment stage
Future fleet additions may change the timetable as much as the power requirement. Model the proposed expansion separately and identify what can be accommodated through existing arrangements. Where additional infrastructure is needed, clarify the trigger and lead-time assumption rather than promising unspecified scalability.
The procurement brief should cover readiness outcomes, scheduling inputs, monitoring and the operational handover as well as charger hardware. Run acceptance exercises against representative return and departure patterns. A completed installation only demonstrates the intended service when the depot can repeatedly turn its actual fleet activity into vehicles ready at the agreed time, including the practical exceptions that occur during everyday work. Include the person authorised to change priorities during disrupted depot operations.
Sources & further reading
National Laboratory of the Rockies: EVI-X tools ↗
Vehicle schedules and infrastructure configuration can be modelled together.
Prepared 2026-10-13. Source references retained from that edition. Corrections and feedback.