Your energy system, ready for the depot.
Depots judge an energy platform by one thing: how many vehicles leave on time. i4B builds and runs the integration layer between your platform and the fleet side — timetables, vehicles, departures held in DMS, TMS and ITCS — and extends your platform with what depot electrification demands, so your customers get readiness guarantees and lower peaks without a second system on the screen.
Fleet features for CSMS and EMS platforms
Four things a depot needs that a charging or energy platform was not built for. Power is handled. The depot asks the platform to also know the timetable, the vehicles and the departures — and to be judged by them.
The plan ends at a time, not at a kilowatt
Every vehicle has a departure and a block. Without them, load balancing is fair and the 04:04 pull-out leaves at 70 %.
Vehicles are the unit, not sessions
State of charge on arrival, battery capacity, the block it serves next. The fleet system holds it; the platform has to read it.
Readiness is the KPI the customer signs
Projected state of charge at departure for every vehicle, all night — and a swap proposal when the forecast says no.
Energy that reconciles on the fleet’s side
kWh per vehicle, route and customer; CDRs per session that match the operator’s report and your invoice.
You keep the power. We connect the fleet side. Together we extend your platform.
The integration layer is the necessary piece between an energy system and a fleet system. We build it for your platform, run it against your customers’ fleet systems, and extend your platform with what depot electrification requires — as data your UI renders, not as a second screen.
What your platform keeps
- Chargers, sessions and charging profiles
- Grid envelope, tariffs, storage, PV
- Smart charging and site management
- Your UI, your customers, your contracts
What we connect
- Timetables and route plans — GTFS, VDV-452, planning exports
- Vehicles and state of charge — telematics, rFMS, OEM APIs
- Dispatcher events from DMS, TMS and ITCS — blocks, swaps, pull-outs
- One depot model: vehicle, stall, charger, envelope, departure
What your platform gains
- Departure-aware allocation: earliest pull-out first
- Readiness forecast per vehicle, swap proposals back to the fleet system
- Vehicle view next to the station view
- Energy per vehicle, route and customer; CDRs the fleet can reconcile
Fleet-side adapters are built per source and per customer. We do not pretend one connector fits every ITCS — we build the one your customer’s system needs and keep it current.
Depot capabilities your customers expect — rendered by your UI, fed by the layer
Each item is data with a contract. Your platform shows it in its own screens; the layer keeps it true against the fleet system.
Departures as the first input to allocation
Earliest pull-out first, under your envelope and tariffs. Your smart charging stays; it gains the one variable it was missing.
Readiness as a number the customer can sign
Projected state of charge at departure for every vehicle, recomputed all night. When the forecast says short, a swap proposal goes back to the fleet system — their dispatcher confirms.
A vehicle view next to the station view
Which vehicle is on which charger, how much it needs by when, and why it is waiting — in your platform, without a second login for the depot.
Flexibility you can quantify
How much the depot can shed at 02:00 without a short departure, and for how long — the kW and minutes a DSO contract or an aggregator bid needs.
- DiscoveryAbout two weeks: your systems, your customers’ depots and the first depot to connect. Scope fixed before any commitment.
- Integration layerBuilt and run by i4B, one adapter per system, delivered as a versioned API.
- ExtensionDepartures, readiness, vehicle view and flexibility arrive as data for your UI; the first depot goes live in sprints, observing before controlling.
- SupportThe same team in production, on a retainer you choose.
Thirty minutes, one depot in mind, a straight answer.
What you can sell to depot operators
Fleet awareness turns a site deal into a depot deal. This is what the integration does for your business, not only for the dispatcher.
Depot tenders you can win
Bus and truck depot tenders increasingly ask for readiness per departure and schedule-aware charging. Your platform answers with its own screens.
Customers who stay
Depots that get readiness guarantees from your platform have no reason to put a second system next to it.
A fleet module on your price list
Departure-aware allocation, readiness, vehicle view and quantified flexibility as a priced add-on per depot.
No fleet adapters to maintain
Every DMS, TMS and ITCS is different. We build and run the adapters; your team keeps working on the power side.
From discovery to a running integration — in sprints you can see
We start by learning your platform and your customers’ fleet systems, and we deliver working results every one to two weeks.
Discover
Your platform’s model, your customers’ fleet systems and depots, the first depot to connect. Scope and approach fixed before any commitment.
Connect
The fleet side: timetable, vehicles, dispatcher events — an adapter per system, built to what it actually exposes.
Extend
Your platform gains departures, readiness, vehicle view and flexibility — as a versioned API your developers call like any other service.
Run
Live on a real depot. Readiness recomputed as the night goes; swaps and deviations exchanged with the fleet system.
Support
The team that built the integration supports it in production and keeps the fleet-side adapters current as the customer’s systems change.
What changes for your customers when the energy platform speaks fleet
Seen from the depot floor, not from the architecture diagram.
Why energy and charging vendors work with i4B
i4B has built software for mobility since 2005; our charging software runs in production in 12 EU countries.
OCPP and OpenADR, natively
OCPP 1.6 and 2.0.1 and OpenADR as specified. Open Charge Alliance member, tested on real chargers in our EVLAB.
Fleet data, translated
GTFS and VDV timetables, rFMS telematics and DMS, TMS or ITCS events turned into departures and vehicles your allocation can use.
One adapter per fleet system
Built to what your customer’s fleet system exposes, in 1–2 week sprints, supported by the same team in production.
For platforms that already own the energy side of the depot
EMS vendors
Who meet depot customers asking for readiness guarantees and schedule-aware charging.
CSMS vendors
Whose depot customers expect the platform to know when the bus leaves.
Charger manufacturers with a cloud
Who sell the hardware and the platform, and are asked for the fleet view too.
Energy service providers and ESCOs
Who sell the connection, the storage and the tariff — and need the depot plan to prove the business case.
Building a DMS, TMS or ITCS? Charging integration for fleet software → · Running the depot yourself? Choose your fleet system with us →
Tell us about your platform and the depots that are asking
Thirty minutes. We look at how your platform holds sites and sessions, walk through how the fleet side would arrive in your screens, and tell you honestly what the integration would take — and whether we are the right partner for it.
- 1 · You send one emailWe reply within 24 business hours to pick a slot.
- 2 · Bring one customer’s depot in mindGrid connection, fleet size and the fleet system they run, if any.
- 3 · You get a straight answerFit or no fit, which capabilities first, what the fleet-side adapter would need. No sales sequence afterwards.
Thank you. We reply within 24 business hours to pick a slot for your 30-minute call.