Somewhere in the electrification programme, the depot changed job description.
It used to be a logistics facility: the place vehicles parked, refuelled and got fixed. Electricity was a utility line, somewhere below fuel and tyres in the budget review. Nobody managed it, because there was nothing to manage.
That depot no longer exists. In its place is a facility that is simultaneously the largest single point of electricity demand on the site, a battery asset measured in megawatt-hours, and, in markets with demand response, a potential revenue source. Most operators are still running it like the old one.
The highest 30 minutes of your month
Commercial electricity tariffs include a demand charge: a fee based on the highest 15- or 30-minute average power draw in a billing period. It exists because the grid must be sized for your peak, and the utility prices that obligation accordingly.
Now consider what an unmanaged depot does. Vehicles return between 17:00 and 20:00. They plug in, more or less together, because that is when the shift ends. Every charger draws at once. The site's demand curve spikes, and that spike, thirty minutes wide, sets the demand charge for the entire month. Tens of thousands of dollars or pounds, added by one interval, repeated every month, in every billing period, for the life of the fleet.
Existing tools cannot prevent this. Charger management systems manage sessions. Fleet telematics tracks vehicles. Building energy systems watch the HVAC. None of them sees fleet state and grid load at the same time, so none of them can act on the interaction, which is where the money is.
Unmanaged depot energy failures add 15–25% to the effective cost of fleet electrification. That figure is not a risk. It is a line item you are already paying.
Readiness is a charging problem
The demand charge is the visible cost. The invisible one is readiness failure.
In a depot with 30 or more vehicles, a static charging schedule creates conflict. A bus with a 05:30 departure competes for charger access with one that does not leave until 09:00, because the schedule has no concept of priority. Vehicles get dispatched with insufficient charge. Others sit on chargers they no longer need. The morning failure that looks like a vehicle problem is usually a charging-sequence problem that started the night before.
Then there is the battery itself. Charging is the primary driver of accelerated degradation. Fast-charging into a hot pack, routinely charging to 100%, poorly timed high-rate sessions: all of it measurably shortens pack life. Packs cost around $100,000 per vehicle. Charging them for convenience rather than for condition is an expensive habit with a delayed invoice.
What orchestration actually means
ZAPPP Depot runs on an industrial edge server at the depot and treats the entire site as one optimisation problem. Every 60 seconds it evaluates the full state: which vehicles are plugged in, their charge state and departure times, the building load, the tariff window, the demand budget, each battery's thermal condition. Then it sets which chargers run, at what power, in what sequence.
The properties that matter:
- It is continuous, not scheduled. A vehicle arriving at 04:30 instead of 06:00 triggers an immediate re-plan. A charger that trips mid-session has its vehicles reassigned automatically. The plan is recomputed every minute, not printed once a night.
- It holds hard constraints. A vehicle reaches its required state of charge by departure. Non-negotiable. Cost and load are optimised within that boundary, never across it.
- It charges for battery condition. Where vehicle-level intelligence is present, hot or weakened packs get modified profiles. The depot stops quietly degrading the assets it is supposed to protect.
- It attributes cost. Per vehicle, per session, per route. The true cost of operating each vehicle becomes a reportable figure instead of a monthly mystery.
- It works without the cloud. All of it executes locally, on the depot network, with sub-second latency. Depots are not data centres, and connectivity is not a dependency.
The asset nobody has switched on
The third identity of the modern depot is the one furthest from most operators' planning: it is a distributed energy resource.
Thirty plugged-in buses are 6–12 MWh of dispatchable capacity. In markets with demand-response programmes, that capacity has commercial value today: reduce charging load on request during grid stress events, and get paid for it. As vehicle-to-grid infrastructure matures, the same control layer coordinates export events and settles the energy flows.
This is not speculative architecture. The capability is a designed revenue pathway: the platform tracks the combined capacity of plugged-in vehicles as a dispatchable resource and exposes it to programme APIs. The depots that build this control layer now will be the ones utilities call first. The ones that do not will keep paying demand charges to the people who do.
The depot is simultaneously a fleet facility, the site's largest load, and a grid asset. Managing one of the three is no longer sufficient.
The CFO's version of this article
Strip the engineering out and the argument is one paragraph. Depot energy failures (peak overruns, reactive charger maintenance, unoptimised charging windows) add 15–25% to the cost of electrification. That cost is recoverable with orchestration that already exists, at a price measured in thousands per year against savings measured in hundreds of thousands. In the reference case, a 35-bus depot, modelled annual value is $229,110 against a first-year cost of roughly $8,300. Even at 25% realisation, payback is under two months. [VERIFY: publish reference-depot economics: internal concept figures]
The depot stopped being a car park with cables the day the first electric bus arrived. The only remaining question is whether it is being run like the asset it now is.