Why vehicle-first orchestration matters.
Charging software was built around the charger. That made sense when the problem was installing chargers. It stops making sense the moment a fleet starts running on electricity, because the asset that moves, earns and consumes energy is the vehicle, not the socket.
For the last decade, EV charging software answered four questions well. Where is the charger? Is it online? Who used it? What did the session cost? Site maps, status dashboards, session records, invoices. For an operator installing infrastructure and billing for it, that was the whole job.
Fleets do not operate chargers. They operate vehicles. And the questions a fleet actually needs answered are different:
What does this vehicle need, where will it be next, what energy decision should be made now, and can that decision create value without disrupting operations?
That is the shift from charger-first to vehicle-first. It is not a feature. It is a change in where the intelligence sits.
A charger-centric system sees a socket
Charge point management systems (CPMS) are good at what they do. They manage charge points, balance load across a site, handle access and billing, and tell an operator what is happening at a depot. A number of capable platforms have been built on that foundation.
But they are anchored to a location. They know what is happening at the depot. They know far less about the vehicle’s next job, its operational constraints, or whether it can safely take part in a grid event without putting a delivery at risk. A charger-centric system asks “when should this charger turn on?” That is a useful question. It is not the question a fleet manager loses sleep over.
A vehicle-first system sees an asset
Treat the vehicle as the unit of decision, and a richer picture appears. The same factors a CPMS treats as background become the inputs that matter:
A modern depot rarely runs one vehicle type on one charger network. Vans charge overnight, a few vehicles top up at public hubs mid-shift, others return to a different site. The commercial value sits in understanding each vehicle across those environments, and that requires orchestration at the asset level, not the socket.
Charger-first
Anchored to a location. It can optimise the site it sits in, and it loses the asset the moment the vehicle leaves.
Vehicle-first
Anchored to the asset. The same energy decision travels with the vehicle, across depots, public hubs and third-party charging.
Why it matters to the people running the fleet
Fleet operators need three things, and only one of them is “charging.”
Operational confidence
Vehicles must be ready when the shift starts. This is not a soft concern: a meaningful fraction of depot charging sessions do not deliver what was expected. A charger that says “online” is not the same as a vehicle that is charged and ready to depart.
Lower energy cost
Once diesel becomes electricity, fuel stops being a purchase and becomes a management problem. When a fleet charges now matters as much as how much it uses.
Future flexibility revenue
A parked, plugged-in fleet is a controllable energy asset. Britain is short of exactly this kind of flexibility: NESO’s Clean Power 2030 advice, published in November 2024, calls for up to five times more demand-side flexibility by 2030 than the system has today. Fleets that can shift load predictably are part of the answer, and there is money attached to it.
A charger-centric system can help with the first part of the first item. A vehicle-first orchestration layer can decide, across the whole estate, when a vehicle should charge, pause, hold or stay available, and do it without ever compromising the departure board.
Where TOGL fits
TOGL is building a vehicle-first orchestration layer. It connects to the vehicle, and is designed to read the asset and help fleets make better energy decisions across depots, hubs and, as market access allows, flexibility markets.
Crucially, it is not another CPMS. It sits above fragmented infrastructure, through supported integrations built on open protocols, and makes the vehicle the centre of the decision. That makes it a partner to existing charging software, not a replacement for it. Same chargers, same CPMS, same energy supplier; the orchestration sits on top.
The sharpest expression of vehicle-first thinking is what happens before a vehicle even arrives. The design intent is for the platform to draw on telematics while a vehicle is still en route, so that state of charge, location and estimated arrival are known ahead of time. That advance notice is what would let a depot pre-schedule charging, prioritise the vehicles needed first, and hand the local network a credible forecast of demand before it lands. The data already exists in the vehicle. The opportunity is to put it where the depot and the network can act on it.
Vehicle tells the depot early
Telematics give state of charge, location and arrival time before the vehicle reaches the gate.
Depot pre-positions charging
Charging is planned against tariffs, site limits and departure times rather than reacting on plug-in.
Network gets a forecast
The local network operator receives an ahead-of-time demand forecast instead of discovering the load.
“A charger-centric system can optimise a location. A vehicle-centric system can follow an asset, wherever it charges.”
Key takeaways
- Charger-centric systems lose the asset picture the moment a vehicle leaves a managed site.
- Vehicle-first orchestration means charging control follows the asset across depots, hubs, and third-party charging.
- The five decisions that matter (readiness, flexibility, cost, grid signal and departure) all require vehicle-level data.
- TOGL is being built around an ahead-of-time approach, so that a depot can pre-position charging before vehicles arrive rather than react when they plug in.
- This is also the data that distribution networks need: a real-time demand forecast, not a historical billing estimate.
The point
The next phase of EV infrastructure is not mainly about installing more chargers. It is about coordinating vehicles, energy and operations in real time, and increasingly, ahead of time. Charger-first software solved the installation problem. Vehicle-first orchestration solves the operating problem.
That is why it matters.