For DMS, TMS & ITCS vendors

Your fleet system, ready to orchestrate the electric depot.

Your customers are electrifying, and they expect their fleet system to keep up. We work with your developers to connect your product to the depot’s charging and energy systems, bringing those capabilities into the platform they already use.

Built with your team, inside your product
Your UI stays the only screen
Honest fit check on the first call
Depot orchestration built into fleet management systems: DMS, TMS and ITCS
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 electrification asks of a fleet system

Charging features for DMS, TMS and ITCS products

Diesel did not limit the plan. Energy does. Your product knows the vehicles and departures. The depot’s CSMS and EMS know charging and available power. We connect the two with your team.

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

Energy as a planning constraint

Range per vehicle, state of charge on arrival, time to charge - the timetable now depends on them. The plan has to know, before 04:00, which vehicles can take which blocks.

Operations

Charging state next to the vehicle

Which vehicle is plugged in, at what power, on which charger, faulted or not. Today that lives in a charger portal; your dispatcher needs it next to the pull-out list.

Readiness

Will it be ready at 05:04?

A projected state of charge at departure for every vehicle, recomputed as the night goes, and an early warning when the answer is no.

Economics

Energy as a cost line per vehicle and route

Delivered kWh per vehicle per night, tariff windows, grid limits and curtailments - the numbers your customers put next to kilometres and the ones their energy supplier invoices.

Scope of our support

Keep your plan. Connect the energy. Orchestrate the depot.

Your product keeps its plan and its screens. We connect it to the depot’s energy system and add what electrification requires, inside your UI.

Yours, unchanged

What your product keeps

  • Vehicles, blocks, routes and departures
  • Dispatcher screens and workflows
  • Telematics and OEM data you already hold
  • Customer, cost and reporting structure
Built together - your developers and our eMobility team

What we connect you to

  • The depot’s CSMS or EMS, over OCPI, VDV 463 or the vendor’s API: sessions, stall state, power envelope and tariff windows
  • Stalls and charging slots matched to your plan: where and when each vehicle plugs in, for which departure
  • The grid limit as a planning input - and the request for more power when the timetable needs it
  • One depot model: vehicle, stall, charger, envelope, departure
Yours, extended

What your product gains

  • Charging state and session history per vehicle
  • Readiness forecast per departure, early warning when one is at risk
  • Charging plan under the grid limit, departure-aware
  • Energy cost per vehicle, route and customer; CDRs that reconcile
What your product gains

Electrification features your customers expect - built into your product

Each item becomes part of your data model. Your front end shows it in your words; together we keep it accurate against the depot’s charging and energy systems.

Charging state

Charging state in your vehicle record

Plugged in, charging at 75 kW on charger C-24, faulted, reserved for the 04:20 pull-out - live, next to the vehicle, without a second login.

Readiness

Readiness per departure, with early warning

Projected state of charge at departure for every vehicle in the plan, marked as estimated. When a pull-out is at risk, your dispatcher sees it early enough to act.

Charging plan

A charging plan that respects the grid

Earliest departure first, under the depot’s envelope, tariff windows and curtailments. Recomputed through the night and exchanged with the depot’s CSMS or EMS.

Energy cost

Energy that reconciles

Delivered kWh per vehicle, per route, per customer, with a charge detail record per session. The operator’s report and the energy supplier’s invoice match.

Depot orchestration in a fleet system: vehicle timeline with charging state, readiness per departure and charging plan
Why it pays off

Benefits for your business

Electrification turns a customer request into a product line. This is what the work does for your business, not only for the depot.

Customers who stay

Operators who electrify keep the fleet system that handles charging for them. The churn risk becomes an upsell conversation.

Tenders you can answer

Public transport operators now tender depot and charge management systems. If you sell ITCS or depot systems to them, you can answer yes without building a charging platform.

A clear answer when customers ask

When an operator asks what your product does for electric depots, you show it working in your product, not on a roadmap.

Charging expertise, without the hiring

OCPI versions, CSMS and EMS vendor APIs and their changes are what our engineers work with every day. You get that expertise without hiring for it; we keep your integration current and your roadmap stays yours.

How we work with you

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

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

1

Discover

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

2

Connect

Your product, connected to the depot’s CSMS or EMS over OCPI, or through the vendor’s API.

3

Extend

Your product, extended with charging 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 fleet system handles electrification

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

Today
With depot orchestration in your fleet system
Where charging state lives
In the charger vendor’s portal, on a second monitor
In your vehicle record, next to the block
How readiness is known
Someone walks the yard at 04:00
Forecast all night, at-risk departures flagged early enough to act
How the grid limit is respected
Chargers throttled by the energy system, blind to departures
Plan under the grid limit, earliest departure first
How energy is reported
Supplier invoice vs. a spreadsheet
kWh per vehicle and route, matching the supplier’s invoice
Who the dispatcher calls at 02:00
Two vendors
One: you, with the cause already visible
Who we support

For software that already runs the fleet

Depot management systems

Asked for charging and readiness by every electrifying operator - without wanting to become a charging-platform vendor.

Transport and fleet management systems

Whose customers run mixed fleets and need charging planned where routes are planned.

ITCS and scheduling vendors

Whose timetables decide the energy demand - and should decide the charging plan too.

Truck service and booking platforms

Whose trucks charge on the road as well as at the depot. We do not plan the road - but the depot plan counts on the state of charge and the arrival time each vehicle actually comes back with.

Are you a CSMS or EMS vendor? Fleet integration for energy platforms → · 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

8
questions worth asking before the first call

Do we need our own charging platform to support electric fleets?

No. An electric depot runs its own CSMS or EMS for its chargers and grid connection. Your fleet system connects to it, and we build that connection with your developers. Your product gains charging state, readiness and a charging plan; it does not turn into a charging platform.

Our customers’ depots are not electric yet. Can we start?

Yes. Discovery works from your product, the fleet and the timetable, so it can start before the depot charges its first vehicle. We connect your product to the depot’s CSMS or EMS once it is in place.

How will our product know a vehicle’s state of charge?

We connect it to the sources you have: telematics such as rFMS and OEM APIs, and the charging session once the vehicle is plugged in. Where neither is available, we estimate it from the plan and mark the value as estimated.

Which charging systems can you connect our product to?

Whichever the depot runs - a CSMS or an EMS. Our engineers connect them over OCPI or VDV 463 where supported, and through the vendor’s API where not. Vehicle data comes from the telematics you already have.

How long does it take to add charging to our product?

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

What do you need from us to start?

A 30-minute conversation about your product and what your customers are asking for. Everything else - the depot model, the energy side, the details of your system - we work out together in discovery.

How do you work with our development team?

Side by side with your developers, as one team. After discovery we deliver in short iterations, and the same engineers support the result in production.

Where will the integration live?

In your platform, built together with your developers.

Your product plans the day. Connected to the energy side, it orchestrates the depot so every vehicle is charged for its departure.
Talk to us