Risks

Risks

TransitSync faces several project-critical risks that could affect the reliability and usefulness of the platform. We have identified these risks early and prioritized the core functionality needed to address them.

Project-critical risk	Why it matters	First action taken	Evidence
Simulation accuracy and reliability	TransitSync's results are only meaningful if the simulation realistically represents train movements, passenger transfers, and delays. An inaccurate model could make an ineffective transfer coordination strategy appear beneficial.	We focus first on building a reliable simulation engine by modelling reproducible simulation runs, train and delay propagation, and passenger transfers before implementing transfer coordination strategies.	US-1.1 - Deterministic event engine US-1.2 - Train movement and delay propagation US-1.3 - Passenger generation and transfer arrivals
Incorrect holding decisions	If the calculation of passenger time saved versus time lost is incorrect, TransitSync could recommend holds that increase overall passenger delay while still producing results that appear reasonable.	Defined the break-even calculation as a standalone, testable component and planned hand-calculated examples and regression tests to verify that holding decisions correctly balance passenger time saved against time lost.	US-2.2 - Break-even calculation and hold length
Unrealistic operating behaviour	A strategy could perform well in the simulation by making decisions that would not be feasible on the actual Metro or REM network, making the results less useful for real-world decision support.	Defined safety limits and simulator-level operating constraints so strategies cannot bypass maximum hold times, minimum train gaps, or other operating rules.	US-2.4 - Connection protection with safety limits US-2.5 - Operating rules and constraint enforcement