Response proposal — for human approval
No options selected yet.
This proposal is not sent anywhere. In a real deployment it would be routed to the named roles for approval, and every decision would be logged with who made it.
Prototype · Synthetic data
Disruption Command
Synthetic scenario, 16:41: national IC 718 is running 27 minutes late into Fernpass Junction. Its passengers feed the regional Alpine railway, local buses, a cableway and partner hotels. One screen, five kinds of impact, and a set of options for the people who decide.
Situation
Impact across the whole system
- Risk
Operational impact
Capacity pressure on next service
- RA 36 (18:06) forecast at 131% of seated capacity
- 1 crew consequence: guard on RA 34 exceeds shift end by 22 min
- Risk
Passenger impact
143 passengers affected
- IC 718 arriving Fernpass Junction +27 min
- 38 with reduced mobility or heavy luggage (booking flags)
- Risk
Connection impact
37 onward connections at risk
- RA 34 to Aldern — 26 passengers
- Bus 7 to Oberau — 11 passengers
- 1 mountain connection likely missed (last ascent 18:45)
- Watch
Destination impact
2 group bookings affected
- Group of 14 — Berghaus Hochfirn, dinner 19:00
- Group of 9 — ski school induction, Aldern, 08:30 next day (luggage transfer)
- Watch
Commercial impact
Compensation and reputation exposure
- Est. 23 passengers eligible for delay compensation
- Partner hotel may bear cost of late dinner service
Response options
Compare options, then assemble a proposal
Select options to build a response proposal for approval. Nothing is executed.
- Decision support
Protect / hold RA 34 connection
- Why
- 26 IC passengers connect; next RA 34 is 60 min later.
- Benefit
- Keeps the chain intact, including the hotel group.
- Trade-off
- RA 34 departs ~12 min late; crossing at Brendel shifts; 91 existing passengers delayed.
- Who needs to approve
- Regional railway dispatcher
- Decision support
Route passengers differently
- Why
- Bus 7 via Oberau reaches Aldern 18:31 with seats available.
- Benefit
- No timetable change needed for RA 34.
- Trade-off
- +19 min journey for rerouted passengers; not step-free.
- Who needs to approve
- Operations controller
- Decision support
Prepare additional capacity
- Why
- RA 36 forecast at 131%; spare unit at Aldern sidings.
- Benefit
- Reduces crowding and dwell-time knock-on.
- Trade-off
- Needs a driver within rest limits; unit unavailable for later spare cover.
- Who needs to approve
- Fleet controller + roster manager
- Decision support
Coordinate with cableway and hotel
- Why
- 1 mountain connection likely missed; group dinner committed at 19:00.
- Benefit
- Partners can prepare a late ascent or adjust service.
- Trade-off
- Depends on partner willingness and cost; not in operator's control.
- Who needs to approve
- Partner liaison / duty manager
- Decision support
Communicate immediately
- Why
- Passengers currently see only the IC delay, not onward consequences.
- Benefit
- Reduces uncertainty and station crowding at Fernpass.
- Trade-off
- Message may need correction if the plan changes.
- Who needs to approve
- Passenger information team
- Decision support
Monitor without intervention
- Why
- IC delay may recover; decision point is 16:55.
- Benefit
- Avoids disruption to on-time passengers.
- Trade-off
- If delay holds, fewer options remain after 16:55.
- Who needs to approve
- Operations controller
Decision support. Recommendations are presented for human judgement. This is not autonomous dispatch — operators and commercial teams remain responsible for every decision.
Synthetic demonstration. All operators, places, services, staff and figures shown here are fictional and generated for demonstration purposes. No real operational or passenger data is used, and no client relationship is implied.