
Fleet Energy Management Software: The Layer Above Your Depot Chargers
💡 Fleet Energy Management Software: Key Highlights
- Four layers, one kW budget: fleet operations, charging management, the site energy system and the utility all act on the same grid connection. Most depot problems come from two of them setting limits without knowing about each other.
- Price, not just power: in our worked example, moving the same 1,350 kWh into the off-peak band cuts one night’s energy bill from €278.60 to €222.60, about 20%, with no extra hardware.
- Solar and storage are a connection decision: a battery earns its place when a grid upgrade is slow or expensive. In December 2025, 14,000 Dutch businesses were waiting for a new or bigger connection.
- Cost per vehicle is the reporting test: kWh and cost should land on a vehicle, route or customer, across depot, public and home charging.
- Eight buyer questions at the end separate genuine energy management from a dashboard of meter readings.
Fleet energy management software decides how much power your depot draws, when it draws it and what it costs, so that every vehicle leaves on time at the lowest energy price the site can get. This guide is for enterprise and logistics fleet operators, and for the CPOs that run depots on their behalf, in Europe, the GCC, Australia, South-East Asia and India. If you have been told your electric fleet “needs energy management”, this is what that layer has to do and how to judge a platform that claims to do it.
Two neighbouring topics already have their own guides. Overnight sequencing of many vehicles through fewer chargers is covered in smart charging for fleet depots, and peak-kW billing is covered in our guide to demand charge management. This article sits one level above both: tariffs, site limits, on-site generation and cost accounting.
The stakes are rising. The IEA reports that global electric truck sales grew about 80% in 2024 to nearly 2% of truck sales. Each heavy vehicle that joins a depot adds hundreds of kWh to a night that already has a fixed grid connection.
Where Fleet Energy Management Software Sits In The Stack
A depot has four decision-makers, and each one thinks it owns the same kilowatts. Fleet energy management software is useful only if the boundaries between them are explicit.
| Layer | Typical system | What it decides | What it needs from the others |
|---|---|---|---|
| Fleet operations | Fleet management platform, telematics | Which vehicle runs which route, departure times, required range | Charging status and cost per vehicle |
| Charging management | Charging platform over OCPP | Which charger delivers how many kW to which vehicle, minute by minute | Departure times, state of charge, the current site limit |
| Site energy | Building or site EMS, solar inverter, battery controller | Total import, building load, solar output, battery charge and discharge | Forecast charging demand and flexibility |
| Utility / DSO | Tariff, connection agreement, demand response signals (for example OpenADR) | Contracted capacity, time-of-use or dynamic prices, curtailment events | Metered import and response to events |
Who decides what at an electric fleet depot. The energy layer sits between the charging system and the site and utility layers.
Why two systems end up fighting over the same kW
The classic failure is a building EMS and a charging platform that both set a limit on the chargers. The EMS cuts the depot to 120 kW because the warehouse cold store has kicked in. Seconds later the charging platform, which still thinks 200 kW is free, pushes a new OCPP charging profile back up. Chargers oscillate, vehicles miss their target state of charge and nobody can explain the bill.
The protocol is catching up. OCPP 2.0.1 added a separate charging-profile purpose for limits imposed by an external system, and the Open Charge Alliance’s OCPP 2.1 overview defines topologies in which a local EMS controls an additional profile, including extra power available from solar, with external limits the central system can read back. The principle for buyers is simple: one layer owns the site limit, and every other layer reads it rather than overwriting it.
Route planning, driver management and maintenance belong in the fleet operations layer, in a platform such as YoMobility’s fleet management platform. The energy layer should consume departure times and state of charge from that layer, not duplicate it.
Tariff-Aware Charging: Pricing The Night, Not Just The Kilowatts
Load management keeps a depot under its connection limit. Energy management also asks what each kWh costs and whether it can be moved to a cheaper hour without missing a departure. That needs three inputs: the tariff (time-of-use bands, or a dynamic price feed where the market offers one), the contracted capacity, and each vehicle’s departure time and target state of charge. Smart charging provides the control; the tariff engine provides the reason to use it.
Worked example: one depot, one night, two tariff bands
Illustrative figures, not a customer result. A depot of 30 electric vans returns at 20:00 and the first van leaves at 06:00. Each van needs 45 kWh, so the night’s demand is 1,350 kWh. The grid connection is 200 kW. The warehouse uses 40 kW until midnight and 15 kW after. The tariff is €0.28/kWh from 20:00 to 00:00 and €0.14/kWh from 00:00 to 06:00.
| Strategy | kWh at €0.28 | kWh at €0.14 | Energy cost per night | Cost per van |
|---|---|---|---|---|
| Charge on arrival, capped at the site limit (160 kW free) | 640 | 710 | €278.60 | €9.29 |
| Tariff-aware: fill the off-peak band first (185 kW free), top up the rest earlier | 240 | 1,110 | €222.60 | €7.42 |
Worked example (illustrative). Derived figures: 4 h x 160 kW = 640 kWh; 6 h x 185 kW = 1,110 kWh; savings are on energy charges only.
The tariff-aware schedule saves €56 a night, about 20%. Over 300 operating nights that is roughly €16,800 a year from software alone, before any demand-charge effect. The 240 kWh that still has to land in the expensive band should go to the vans with the earliest departures or the longest routes, which is why departure time and state of charge are inputs, not extras. If the off-peak band shortens or a dynamic price spikes, the schedule must re-plan rather than silently miss a departure.
In India the same logic runs on Time-of-Day tariffs and the sanctioned load as the site limit; in Europe and Australia it increasingly runs on day-ahead or dynamic retail prices. In every market the site limit itself is enforced by dynamic load management.
Solar And Battery Storage: When They Beat A Bigger Grid Connection
Most fleets charge overnight, when rooftop solar produces nothing. Solar pays off at depots with daytime dwell, such as buses returning between peaks or vans that top up at lunch, and the energy layer should steer those top-ups into the solar hours.
A battery is a different decision: it is a way to stretch a connection you cannot get enlarged quickly. In the Netherlands, KVK, the Dutch Chamber of Commerce, reported 14,000 businesses waiting for a new or more powerful connection in December 2025, and lists batteries and flexible-capacity contracts among the ways to cope. A simple test: if the depot needs 300 kW for two evening hours on a 200 kW connection, a battery with about 200 kWh of usable capacity, recharged off-peak, covers the gap (derived: 100 kW x 2 h). Compare that with the price and lead time of an upgrade from your utility.
Whichever you choose, the energy layer must treat solar output and battery state as live inputs to the charging schedule, not as separate systems with their own targets.
Per-Vehicle Energy Accounting Across Depot, Public And Home Charging
The most common reporting question we see in search is how to combine charging data, telematics and energy data into one report. The answer is to identify the vehicle in every session and price every session at the tariff that applied when it happened.
- Depot charging: meter values from each charger over OCPP, tied to a vehicle through Autocharge (the vehicle’s MAC address, VID or VIN sent by the charger) or an RFID card, and priced at the time-of-use band in which each kWh was delivered.
- Public charging: roaming sessions billed to the fleet account, so a driver’s motorway top-up arrives as a line item against the same vehicle rather than as an expense claim.
- Home charging: sessions from a charger at the driver’s home, reported against the vehicle so the reimbursement is based on metered kWh, not mileage estimates.
- Allocation: kWh and cost rolled up by vehicle, route, cost centre or end customer, and exported to finance in a format the ERP accepts.
When a logistics operator rebills energy to the shipper whose goods a vehicle carried, this ledger becomes revenue, not just reporting.
A Buyer’s Checklist For Fleet Energy Management Software
Ask every vendor these eight questions, and ask to see each answer working on a real charger rather than in a slide.
| # | Question | What a good answer looks like |
|---|---|---|
| 1 | Does it control chargers through standard OCPP smart-charging profiles? | Yes, across charger brands, on OCPP 1.6J and 2.0.1 |
| 2 | Where does it get each vehicle’s state of charge? | From the charger, from the vehicle via ISO 15118, or from telematics, with a stated fallback |
| 3 | Does it have a tariff engine? | Time-of-use bands and dynamic prices, with schedules re-planned when prices change |
| 4 | How is the site limit enforced? | A hard cap on contracted capacity that holds even if a charger or link drops |
| 5 | Who owns the limit when a building EMS is present? | One clear owner; the other system reads it rather than overwriting it |
| 6 | Can it act on utility signals? | Demand response events, and an open API; ask specifically about OpenADR if your utility uses it |
| 7 | Can it use solar and a battery? | Both treated as live inputs to the schedule |
| 8 | What does reporting export? | kWh and cost per vehicle, route and customer, across depot, public and home charging |
Eight questions to ask before you choose fleet energy management software.
Where YoCharge Fits
YoCharge is the charging and energy layer in this stack, not a fleet management system. Its fleet charging software runs on multi-vendor charger support across 60+ charger brands, on OCPP 1.6J and 2.0.1 and ready for 2.1. Load management enforces the site limit with priority tiers, first-in-first-out allocation, sharing by state of charge, Time-of-Day scheduling and demand response. Vehicles are identified by Autocharge today, and ISO 15118 Plug & Charge is supported and built on request. The platform integrates solar and wind, can integrate any custom battery storage system, and lets fleet drivers charge on partner networks with one bill.
The same charging management system behind YoCharge has delivered 50 GWh+ across 2M+ sessions in 25+ countries. See how it maps onto your depots on our EV fleet charging management page.
Frequently Asked Questions
Sources: IEA, Global EV Outlook 2025 launch release | Open Charge Alliance, What’s New in OCPP 2.1 | KVK, How to deal with grid congestion | OpenADR Alliance
Bring your connection size, your tariff and one night of departures. We will show you how YoCharge schedules your chargers against them and reports the cost per vehicle.
Talk to Sales