Definition
Rate at which schedule performance degrades under disruption compared to normal conditions, measuring whether a schedule is merely feasible or genuinely resilient: able to absorb disruption and recover without cascading failure.
The Measurement Gap
Why This Metric Didn't Exist Before
Schedule optimization has always been about maximizing capacity utilization: fitting the most trains into available track time. Every minute of recovery slack is a minute that could carry a train. The pressure to optimize produces schedules that are mathematically feasible but operationally fragile: they work perfectly when everything goes right, and they cascade catastrophically when anything goes wrong.
Before AI-driven scheduling, this fragility was managed through dispatcher experience. Experienced dispatchers knew which parts of the schedule were tight and would preemptively adjust when disruptions approached. AI scheduling optimizers don't have that intuition: they optimize for the objective function they're given, which is typically throughput. If the objective doesn't include a resilience constraint, the optimizer will produce increasingly fragile schedules that maximize capacity and minimize the ability to recover.
Here's the decision SRUDI supports: Is the current schedule optimized for efficiency at the cost of resilience? Should the schedule include more recovery slack, equipment padding, or crew flexibility to absorb disruptions without cascading? SRUDI provides the data to make that tradeoff explicit rather than invisible.
Without SRUDI, you discover schedule fragility during major disruptions. When cascading delays shut down entire corridors and recovery takes days instead of hours. By then, the cost of fragility is measured in millions of dollars and thousands of stranded passengers. SRUDI measures the fragility before the disruption arrives, giving planners the information to add targeted resilience where it matters most.
Formula
Formula:
SRUDI = Total_delay_minutes / Disruption_duration_minutes
Variable Definitions:
| Variable | Definition | Unit | Source | Classification |
|---|---|---|---|---|
| Total_delay_minutes | Total accumulated delay across all trains in the network caused by a disruption event | Minutes | Operations system | NATIVE |
| Disruption_duration_minutes | Duration of the original disruption (mainline blockage, signal failure, equipment failure) before the immediate cause was resolved | Minutes | Incident log | NATIVE |
Sign Convention: 1.0 = each disruption minute causes exactly one delay minute (no cascade). Greater than 1.0 = cascade amplification (the schedule amplifies disruption). Higher = more fragile. Values of 3–5 are typical for tightly optimized schedules. Values above 8 indicate extreme fragility.
Data Requirements:
| Data Element | Source System | Classification |
|---|---|---|
| Disruption events with cause, duration, and location | Incident management system | NATIVE |
| Train delay minutes attributed to each disruption | Operations system / delay reporting | NATIVE |
| Network train schedule (planned vs. actual) | Scheduling / operations system | NATIVE |
| Disruption recovery actions (holds, reroutes, annulments) | Dispatching system | NATIVE |
Edge Cases and Measurement Boundaries:
Overlapping disruptions present a measurement challenge: if two disruptions overlap in time and geography, the combined cascade exceeds the sum of the individual disruptions. Measure overlapping disruptions as a single event with combined duration, or exclude from SRUDI and track separately. Controlled recovery matters too. If dispatchers deliberately hold trains to prevent cascade (accepting planned delay to avoid uncontrolled delay), the controlled delay should still count in SRUDI because it represents real capacity consumed for recovery. Minimum sample: 10 disruption events of 1+ hour duration per quarter.
Proposed formula, pending validation pilots.