Beyond the four
Whatever else a party runs.
Maintenance, charging, scheduling, customer apps. The framework is transit-agnostic: any system a party operates can publish through the same adapter, under the same classification.
- Maintenance
- Work orders, inspections, fault codes and parts. Built for the garage, not for analysis. Beside location and charging data it becomes the training set for predictive maintenance.
- Charging
- Session start and end, energy delivered, power and state of charge for every electric bus. Over months it shows how each battery is ageing. Chargers sit on the equipment side of the OT and IT line.
- Mobility providers
- Station status, vehicle availability, trips and wait times from bike share, scooter and ride-hail operators, usually already published as GBFS or MDS feeds.
- Anything else
- Scheduling, incidents, customer feedback. If it has an owner, a contract and a classification, it can join.
None of these were in the sample. The design does not depend on them. A party with only a timetable and a vehicle feed is a full member; a party with ten systems is not asked to share ten.