For CSMS, EMS & charger cloud vendors

Your energy platform, ready to orchestrate
the depot
with the fleet.

Depots judge an energy platform by how many vehicles leave on time. Your platform knows the power; the fleet system knows the timetable. Our eMobility engineers - with your developers, or as your team - connect the two, so your customers get a readiness forecast per vehicle and lower peaks without a second system on the screen.

Talk to us How we work
With your team or as your team - inside your platform
Your UI stays the only screen
Honest fit check on the first call
Depot orchestration built into energy and charging platforms: EMS, CSMS and charger clouds
20+
years building software for mobility, since 2005
200+
projects delivered for the EV and automotive industry
50+
clients, from charging platforms to parts distributors
60+
engineers and specialists at i4B
What depot electrification asks of an energy system

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 now asks for orchestration: the plan lives in the fleet system, the power in your platform, and the two have to exchange what they know - every night, for every departure.

Electric depot: vehicles, chargers and the grid connection orchestrated together
Departures

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

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

Readiness is the KPI the customer judges you by

Depots judge the platform by vehicles that leave with enough energy, not by kWh delivered. Today nobody can say at 23:00 which pull-out will be short.

Reporting

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.

Scope of our support

Keep your power. Connect the fleet. Orchestrate the depot.

Depot orchestration lives in the connection between your energy platform and the fleet system, and both sides share it: your platform brings power, chargers and stalls; the fleet system brings timetables, vehicles and departures. Our team builds that connection with your developers - or as your team, if you have no capacity for it - and extends your platform with what depot electrification requires, as features in your UI, not a second screen.

Yours, unchanged

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
With your team or as your team - our eMobility engineers

What we connect

  • Demand from the fleet system over OCPI or VDV 463: which vehicle, how much energy, for which departure
  • Charging state and stall availability back to the fleet system, over the same interfaces
  • Telematics where you want to plan yourself: state of charge from rFMS and OEM APIs
  • One depot model: vehicle, stall, charger, envelope, departure
Yours, extended

What your platform gains

  • Departure-aware allocation: earliest pull-out first
  • Readiness forecast per vehicle, shared back with the fleet system
  • Vehicle view next to the station view
  • Energy per vehicle, route and customer; CDRs the fleet can reconcile

Where the fleet system speaks OCPI or VDV 463, we use it. Where it does not, we connect through the fleet system’s API and keep the connection current.

What your platform gains

Depot capabilities your customers expect - built into your platform

Each item becomes part of your platform. Your screens show it in your words; together with the fleet system we keep it accurate.

Allocation

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

Readiness as a forecast per vehicle, all night

Projected state of charge at departure for every vehicle, marked as estimated and recomputed all night. When the forecast says short, the fleet system’s dispatcher sees it early enough to act.

Vehicle view

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

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.

How the work runs
For energy and charging vendors
  1. Discover
    We learn your platform, the depots you serve or plan to serve and what they need, and pick the first depot to connect. Scope fixed before any commitment.
  2. Connect
    Built by our engineers - with yours, or as your team - over OCPI or VDV 463 where the fleet system supports it, or through the fleet system’s API where it does not.
  3. Extend
    Departures, readiness, vehicle view and flexibility become part of your platform; the first depot goes live in sprints, observing before controlling.
  4. Run and support
    The same engineers who built it support it in production.
The result is implemented into your platform, not added as a second screen.
Why it pays off

Benefits for your business

Fleet awareness turns a site deal into a depot deal. This is what the work does for your business, not only for the dispatcher.

Depot tenders you can win

Public transport operators now tender depot and charge management systems. With the fleet connected, your platform can answer for the whole depot, not only the chargers.

Customers who stay

Depots that get a readiness forecast per departure from your platform have no reason to put a second system next to it.

A clear answer when customers ask

When a depot asks what your platform does for its departures, you show it working in your platform, not on a roadmap.

Fleet expertise, without the hiring

Every DMS, TMS and ITCS is different, and connecting them is what our engineers do every day. We build the integration with your developers or as your team, and keep it current; your team stays focused on the power side.

How we work with you

From discovery to a running integration - with progress you can see

We start by learning your platform and the depots you serve or plan to serve, then our engineers work with yours - or as your team - and deliver working results every one to two weeks.

1

Discover

Your platform, the depots you serve or plan to serve, and their fleet systems. Scope fixed before you commit.

2

Connect

Your platform, connected to the depot’s fleet system over OCPI or VDV 463, or through its API.

3

Extend

Your platform, extended with fleet features in your data model and UI.

4

Run

Running within your software ecosystem, with all the information at your fingertips.

5

Support

The same engineers support it in production and keep it current as standards and systems change.

Before and after

What changes for your customers when your energy platform speaks fleet

Seen from the depot floor, not from the architecture diagram.

Today
With the depot orchestrated across both systems
What the allocation optimises
Fair power split among chargers
Earliest departure first under the grid limit
How readiness is known
Not by the platform - by someone in the yard
Forecast per vehicle all night, shared with the fleet system
How a curtailment is handled
Throttle everything, hope
Plan input: storage and priorities absorb it, departures hold
How energy is reported
Per charger, per session
Per vehicle, route and customer - reconciled with the fleet’s report
Who the customer calls at 02:00
Two vendors
One: you, with the fleet context already visible
Who we support

For software that already runs the depot’s energy

EMS vendors

Who meet depot customers asking for readiness per departure 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 → · Building your own fleet software for your depot? Depot orchestration for fleets that build their own software →

Talk to us

Tell us about your needs

Leave your details and we will get back to you to set up a short call.

  1. You send the form
    We get back to you to agree on a time.
  2. We talk
    A short call about your needs and how we could help.
  3. Next steps
    If there is a fit, we propose how to start.
Call requested

Thank you. We reply within 24 business hours to pick a slot for your 30-minute call.

Something went wrong. Please try again, or email us at contact@i4b.pl.
FAQ

Frequently asked questions

9
questions worth asking before the first call

We already have smart charging. What does this add?

The fleet. Smart charging distributes power among chargers; connected to the fleet system, your platform brings departures, vehicles and readiness into that decision and reports back. Your allocation stays - it gains the variable it was missing.

Where does the schedule come from?

From the fleet system the depot already uses - DMS, TMS or ITCS - over OCPI or VDV 463 where it speaks them, through its API where it does not. Where no system exists, a timetable import (e.g. VDV 452) is enough to start; the plan runs on what it has and marks what it assumed.

Does anything replace our platform?

No. We connect your platform to the fleet system and extend it from the inside. Your chargers, sessions, envelope and UI stay as they are; your platform gains the fleet side as part of its own model.

How does readiness get to the depot’s dispatcher?

Through the fleet system: over OCPI or VDV 463, your platform sends readiness forecasts back to the DMS or TMS where the dispatcher works, and receives changed departures.

Which fleet systems can you connect our platform to?

The ones your depot customers use - DMS, TMS or ITCS. Our engineers connect them over OCPI or VDV 463 where the fleet system supports it, and through its API where it does not.

How long does connecting our CSMS to a fleet system take?

We start with discovery, to understand your platform and what the depots you serve or plan to serve need. The first depot is then connected in one- to two-week sprints; how fast the full scope lands depends mostly on what the fleet system exposes. We fix the plan and the first milestones before you commit.

What do you need from us to start?

A short conversation about your platform and what your customers are asking for. The rest we work out together in discovery.

How do you work with our platform team?

Side by side with your developers, or as your team if you don’t have one for this. After discovery we work in one- to two-week sprints; the code lives in your platform, and the same engineers support it in production.

We don’t have developers for this. Can you still do it?

Yes. Our engineers work as your team: we build the integration into your platform, document it, and support it in production for as long as you need.

Your platform keeps the power, the fleet system keeps the plan. Connected, they orchestrate the depot so every departure is met.
Talk to us