Integrating depot charging with fleet telematics

This is the whole article in one table. Everything else is how to verify it.

It is not usually a technical limit; it is a commercial and permissions one. Charging platforms publish session data readily because session data is theirs and exporting it makes their product look good. Vehicle data belongs to the vehicle OEM and to the telematics provider, and it is commonly gated behind partner agreements, data-sharing consent and a certification process. So the path from the charger outward is easy, and the path from the vehicle inward is a negotiation. The result is an integration that shows you beautiful reports of what happened last night while remaining structurally incapable of changing what happens tonight. If schedule-aware charging is your reason for integrating, you must confirm the inbound path specifically. Confirming that 'the two systems integrate' does not confirm it.

Session data without vehicle identity is much less useful than it looks, and identity is not automatic. There are four ways to establish it and they differ a lot in effort and reliability. RFID cards or fobs assigned per vehicle work everywhere but depend on a driver doing something at the end of a long shift. Automatic identification based on the vehicle's communication address is convenient where the charger and vehicle both support it, but it is a de-facto method rather than a standard and support varies. ISO 15118 with Plug and Charge is the standards-based version and is the cleanest when both ends support it. Fixed assignment — this van always parks on port seven — is free and works until somebody parks in the wrong bay. Ask both vendors which of these they support, and pick one before commissioning rather than discovering the problem in the first month's report.

Take this list into both sales conversations, ask for written answers, and give the two documents to whoever will own the integration.

In rough order of cost and of how much control you retain.

Charge to the state of charge tomorrow's route needs rather than to full, which reduces both the energy and the peak power the site draws — and reduces time spent in the slow part of the charge curve near a full battery. Order the queue by departure time, so the van leaving at 4am is not waiting behind the one leaving at 10am. Flag unplugged vehicles at a time somebody can still walk out and plug them in. Reconcile kilowatt-hours against miles per vehicle, which is how you find the vehicle with a developing problem and how you validate the energy assumptions from your pilot. And produce metered, per-session data in the format a utility program requires, which several programs do require as a condition of payment.

Do not try to build the whole thing at once. The outbound flow — sessions, energy and faults from the chargers into your fleet system — is the easy half, it is the half that works with almost any vendor pair, and it is what lets you reconcile energy against miles and find the vehicles that are quietly costing you money. Ship that, use it for a month, and you will discover which of the inbound capabilities you actually want, because some of them turn out to matter far less than they did in the planning meeting. A yard with a long dwell window and comfortable capacity may not need departure-time prioritisation at all: everything is full by morning regardless of order. A yard that is tight on power or tight on time needs it badly. Building the outbound half first tells you which yard you have, at a fraction of the effort and before you commit to a middleware subscription you may not need.

Two questions, asked at purchase, save a great deal later. Who owns the session and vehicle data — you, or the platform — and can you export the full history in a usable format when a contract ends. And who supports the integration when it breaks, because it will break: firmware updates on chargers, API versions deprecated by telematics providers, and credentials that expire are all routine, and an integration built between two vendors who each consider it the other's responsibility fails permanently the first time it stops. Name a party in the contract. If nobody will take it, budget for the fact that it is yours.

One last caution, because it is a real pattern. A depot that integrates well is still a depot that has to deliver the energy, and the electrical design should come out of your measured nightly kilowatt-hours and your real dwell window, not out of the feature list of a software platform. Smart charging makes a well-sized site more efficient and cheaper to run. It does not rescue a site whose service capacity was sized wrong, and no scheduling algorithm can move more energy through a feeder than the feeder carries. Get the load profile from a properly sited pilot, size the electrical work from that, and treat the integration as the layer that makes a correct design work better.