← Content
Industry

SaaS AVM and electric buses: adapting your system to the energy transition

How to adapt your AVM system for electric buses joining your fleet: energy data integration, state of charge, charge sequencing and unified supervision.

Laetitia Montagne, Marketing Manager
· 4 min read · Updated

Short answer: to adapt an AVM system to electric buses joining your fleet, the AVM must see the vehicle's energy data (state of charge, range) over open onboard protocols such as FMS and ITxPT, alert dispatchers before a bus runs flat, and sequence charging at the depot around departure priorities. A SaaS AVM with an open hardware architecture does this without replacing the onboard equipment.

Fleet electrification is not only a procurement and financing decision. It is an operational transformation that directly affects the AVM. An electric bus is not operated like a diesel: its range varies with temperature, route profile, and driving style. It needs charging, which must be integrated into service scheduling. And if the AVM cannot see this data, the operator is running a partially blind fleet.

What changes with electric buses

Range management. An electric bus has a range that varies with the model, battery capacity, weather, and route profile. The AVM must alert the dispatcher before a bus runs flat on the line.

Charge scheduling. Electric buses must be charged during operational troughs. Depot supervision must integrate the state of charge of each vehicle: a bus pulled off charge at 30% to cover an 80 km line is an operational problem.

Onboard equipment. Electric buses are often delivered with embedded telematics systems (OBD/FMS gateway). For the AVM to consume this data, it needs an open architecture compatible with these protocols.

What Pysae addresses

Pysae Fleet provides onboard telematics: its box is wired to the vehicle's CAN/FMS bus and reads mileage, engine data, fuel consumption and fault codes via the manufacturer standard, without extra sensors. Fleet also includes smart EV charging orchestration, with charging sequenced by departure time and off-peak rates, and a departure timeline that confirms vehicle, driver and margin in advance.

Pysae Operations handles real-time supervision: live map, advance and delay on every trip, diversions, alerts and messaging between drivers and controllers, with GTFS-RT, SIRI and ITxPT exports. Pysae already supervises networks in energy transition: on the Elios network (Grand Villeneuvois), the whole fleet switched to HVO, a renewable fuel, in 2024, with Pysae as the AVM.

How to adapt your AVM for electric buses: five steps

  1. Check that the incoming electric buses can be fitted with the onboard terminals of the chosen AVM, or that the AVM can read their embedded telematics (OBD/FMS gateway).
  2. Define which energy data the AVM should consume, at what frequency, and with which alert thresholds.
  3. Bring the state of charge of each vehicle into depot supervision, so no bus leaves charge below what its next service requires.
  4. Build charging constraints into roster construction, and sequence charges by departure priority during operational troughs.
  5. Set range alerts per vehicle and per line, so dispatchers act before a bus runs flat on the line.

Frequently asked questions

How do I adapt my AVM system for electric buses joining my fleet?

Follow the five steps above: confirm the onboard equipment or telematics gateway, define the energy data and alert thresholds, add state of charge to depot supervision, integrate charging into rosters, and alert on range before the line. The AVM must be able to consume vehicle data over open protocols.

Can an AVM read the state of charge of an electric bus?

Yes, when the vehicle exposes this data on its onboard interface and the AVM consumes the vehicle's embedded telematics through open protocols. Pysae Fleet's onboard box is wired to the vehicle's CAN/FMS bus and reads vehicle data via the manufacturer standard.

What range should dispatchers plan for with electric buses?

It depends on the model, the battery capacity, the weather and the route profile, so rely on the manufacturer's data and on your own operating records. Alert thresholds should therefore be set per vehicle and per line rather than fleet-wide.

Does the same approach apply to hydrogen or other zero-emission buses?

The principle is the same: what matters is whether the AVM can consume the vehicle's energy data over open protocols such as FMS and ITxPT, and whether the platform can account for refuelling or charging constraints in service planning.

Does Pysae already work with networks in energy transition?

Yes. On the Elios network (Grand Villeneuvois), the whole fleet switched to HVO, a renewable fuel made from hydrotreated vegetable oils, in 2024, with Pysae as the AVM.

Are you introducing electric buses into your network? Talk to our team.