Operational impact · Financial exposure

BreachCalc

Loading sector assumptions…

INCIDENT LAB · RAILWAY / DISPATCH & SCHEDULING

Dispatch under pressure.

When information stops, the timetable unravels.

Interactive cyber exercise

Explore a supplier outage, manual fallback, and the work that remains after restoration. Informed by documented railway disruptions. This browser-local simulation uses fictional scheduling requests and compressed time; it is not a live railway feed.

DISPATCH DESK · FICTIONAL NETWORKT+0.0 h
Scheduling information networkRequests pass through scheduling services or manual fallback into a work queue. Amber means scheduling service is unavailable. The lower marker shows exercise progress, not a train position. Scheduling requests24 per simulated hourSupplier serviceAvailableDispatch deskStandbyUnresolved work0 requests waiting EXERCISE PROGRESS · no physical train movement modeled

● Scheduling information ● Degraded operations

CHAPTER 01 / 05

Real incidents, fictional network

Preparing Bruce Mellow narration…

Incoming demand24 requests/h
Processing capacity24 requests/h
Unresolved queue0 requests
Processed to date0 requests
Incident research, model assumptions & narration transcript

DSB · Denmark · October 2022. DSB says a cyberattack on a subcontractor’s test server indirectly caused many trains to stand still for four hours. This supports the supplier-dependency scenario; it does not establish a compromise of dispatch or signaling systems. DSB, 9 February 2023.

Transnet · South Africa · July 2021. INCIBE-CERT reports that the July 22 cyberattack forced some activities into manual operation and led to force majeure despite activation of business continuity plans. This is evidence of logistics disruption, not a measured dispatch-throughput benchmark. INCIBE-CERT, 4 August 2021.

Poland · August 2023. Unauthorized radio-stop transmissions halted trains and disrupted traffic. PAP reported PKP PLK’s statement that these incidents did not create a threat to people. This communications misuse is distinct from ransomware or a compromised scheduling database. PAP / PKP PLK, 30 August 2023.

Fictional model: Demand is 24 scheduling requests/hour. Normal service lasts from hour 0 to 1 at 24/hour; degraded service from hour 1 to 4 uses your selected fallback; restored service from hour 4 to 8 processes 36/hour. Backlog = previous backlog + arrivals − processed, where processed cannot exceed available work. There are no cancellations. Figures are rounded for display. Requests are work items, not trains or movement authorities. Track occupancy, interlocking, crew limits, passenger impacts and financial losses are not calculated here. The calculator below remains a separate model.

Loading calculator…

Saved scenarios

Saving, sharing and PDF export require an active license. Public calculations remain available offline.