Charging is a schedule, not a socket
What changes when a fleet treats charging as a planning problem instead of an overnight ritual.
Most fleet charging is organised around a socket and a shift end. Vehicles come back, get plugged in, and leave when the charger or the driver says so. That works until the fleet grows and the charging window stops fitting the schedule.
The constraint moves
With a few vehicles, the constraint is the battery. With a working fleet, the constraint is often the charger, the parking bay or the person who moves the vehicles. Charging becomes a queue, and the queue becomes a service problem.
A schedule makes the constraint explicit. Which vehicle needs how much energy, by when, and which charger is free in between.
What a schedule needs
- A state of charge estimate that is close enough to plan against.
- A charging curve the charger will actually follow.
- A priority: which vehicles cannot leave late.
- A record of what happened, so the next schedule is better.
None of this requires exotic hardware. It requires the pack to report its state and the operator to have a place to plan.
Where storage fits
A small buffer battery at the depot can decouple the charger from the grid connection for the peak of the queue. It does not add energy; it moves when the energy is drawn. For a depot with a tight sanctioned load, that is often cheaper than a bigger connection.
The cultural part
Drivers and supervisors are used to a ritual, not a schedule. A tool that asks them to change the ritual without giving something back will be ignored. The useful version gives them a clear answer to “can I leave now?” and a warning when the answer is about to become no.