Bus breakdown during peak hours
-
Detection
Driver panic-button or radio call, GPS shows the vehicle stationary off-schedule, engine telemetry fault code (if IoT-equipped).
-
Data
Nearest reserve vehicle location, driver availability, passengers onboard, route geometry.
-
Recommendation
Dispatch the nearest reserve vehicle; if none is within an acceptable ETA, short-turn the following bus to absorb passengers.
Alternatives: Mutual-aid vehicle from an adjacent depot; bridging via a different route.
-
Approval
Yes: dispatcher confirms the replacement dispatch.
Automation: Auto-detection and auto-recommendation yes; auto-dispatch no (safety/liability).
-
Action
Dispatch order to driver app; PIS passenger notification auto-published; trip status updated.
-
Outcome
Service restored; incident ticket auto-populated with the full timeline. Closure needs dispatcher sign-off + maintenance root-cause code.
Full dispatch workflow (12 steps)
- Detection
- Impact analysis
- Identify replacement vehicle
- Identify driver
- Check route/depot compatibility
- Passenger impact calc
- Recommend
- Approve
- Dispatch
- Notify driver/passengers
- Update trip/KPI
- Close