One Layer to Run Your Whole Electric Depot

A diesel depot was simple to run. Fuel arrived, a truck refueled, and it left for its route. That was all.

An electric truck depot works very differently. Vehicle readiness now depends on charging, on-site power, tariffs, storage, and on-site generation. Each of these runs on its own software system. The depot is no longer just a place where energy goes into vehicles. It is becoming a real-time system where all these parts must work together.

That is the real challenge of depot electrification. The answer is not more hardware or more software. The answer is making the whole depot work as one system. The next frontier of interoperability is not between charging networks or between vehicles and the grid.

It is inside the depot itself.

Where the current software stack breaks down

Every electrified depot runs several strong, specialized systems: a CSMS for chargers, an EMS for site power, a fleet management system, a PV controller, a BESS for storage, and a dispatch system for routes. Each system does its own job well.

The problem is that these systems do not talk to each other. Vehicle readiness depends on all of them at the same time. A charging session that ignores today's tariff, or a dispatch plan that ignores the site's real grid capacity, can quietly cause a missed departure. Coordinating this by hand does not scale. And depot operators should not need to become power-systems engineers just to keep trucks on schedule.

The stack is not missing features. It is missing one layer that makes all these systems act as a single operation.

What orchestration actually means

Orchestration is not a new system that replaces the ones you already use. It is a layer on top of your existing systems. This layer keeps one shared, real-time picture of the depot. It applies your operating priorities. And it sends coordinated actions back to the CSMS, the EMS, the fleet system, the PV and storage controllers, and dispatch.

Three things define this layer:

• One shared state - instead of each system seeing only its own part of the depot, the orchestration layer gives all systems the same real-time picture of vehicles, chargers, grid limits, and departures.
• Your priorities decide - the layer follows the rules your operation already uses: which vehicle comes first, how much to rely on storage, when to use PV. It turns these rules into a plan.
• Coordinated actions - the plan is sent back through the systems you already have. Your vendors and infrastructure do not need to change.

You stay independent from any single vendor, because the layer works with what you already have instead of replacing it. And it stays assisted, not autonomous: the priorities and the responsibility for depot operations stay with your people. The layer carries out a plan. It does not make the final decision.

What this looks like in practice

The easiest way to understand orchestration is to watch it manage one night. Picture a depot with 80 charging stations from two charger vendors, working under one 4 MW grid limit. Every vehicle has a departure time it must meet.

An orchestration layer running that night gives you three things that no single system can give you alone:

1. The whole depot in one view- every station, vehicle, and departure. Planned power next to measured power, all under the same shared grid limit.
2. A policy that decides who charges first - you can switch between strategies such as nearest departure, proportional allocation, or classic load management. The plan updates as soon as you change the policy.
3. Protected departures - each vehicle is tracked against its target charge. If a vehicle risks falling short, the system flags it hours in advance, not at the gate.

This is the difference between a depot that reacts to problems and a depot that sees them coming. It is also exactly what you want to see modeled on your own fleet, chargers, and grid limit before you invest in anything.

What it means for interoperability

For years, interoperability in EV charging has mainly meant compatibility between chargers, networks, and vehicles. That problem still matters, but it is no longer the hardest one.

The next challenge sits one level higher: inside a single depot, between systems that are each excellent on their own but were never designed to share a plan. Solving this does not mean replacing any of these systems. It means giving them one common layer that turns several strong, separate systems into one reliable operation. With that layer, an electrified depot can be as simple to run as the diesel yard it replaces - even though the reality underneath is far more complex.

The natural next step: we model your depot - your fleet, your chargers, your grid limit - and show you the night before you invest.