Track and systems can be built and tested — and the line still cannot safely carry passengers.
Civil completion does not equal safe, reliable public service. Safety cases must be approved, operators and mechanics trained, route knowledge proven, the network cut over, and readiness-for-service certified before service commencement.
Everything a service launch has to coordinate.
One Readiness Room spans every workstream that must be true before service commencement — each with owners, criteria, and accepted evidence.
Safety certification
Safety case approval and statutory certification.
Integrated testing
Systems integration and failover evidence.
Route knowledge
Operator route knowledge proven and recorded.
Operator & mechanic training
Competency, certification, and familiarization.
Network cutover
Service cutover sequencing and interfaces.
Service disruption & bus bridge
Disruption controls and bus-bridge planning.
Asset handover
Vehicle and systems acceptance from delivery.
Control center readiness
Operations control center readiness and escalation.
Three kinds of gate. One service commencement decision.
A service-commencement decision depends on distinct authorities. CitiriOS keeps the T-minus gate ladder separate, evidence-backed, and traceable.
Readiness-for-service gates
A T-minus gate ladder owned by the program — trial running and shadow service acceptance against criteria.
Safety case approval
SSOA / FTA evidence and statutory safety certification — cannot be overridden by the owner.
Service commencement
Owner acceptance to begin revenue service, recorded with residual conditions.
The same platform — in transit language.
Every CitiriOS module maps to how transit agencies run a launch.
Readiness Room
Every workstream, stakeholder, trial, issue, dependency, and gate for a launch.
Ready Score
Service readiness index by domain, with what is dragging it down.
Evidence Packs
Audit-ready safety case and readiness-for-service evidence for the SSOA and FTA.
Gate Authority
Safety, readiness-for-service, and commencement gates kept distinct.
Dependency Graph
Trial sequences, network cutover, and service dependencies made explicit.
Handover & Acceptance
Asset acceptance, conditions, and post-launch stabilization to D+90.
Fit across launch types.
Heavy rail / metro launch
Full revenue-service readiness across safety, systems, and operations.
LRT extension
Phased launch with live-network interfaces and cutover controls.
BRT launch
Corridor readiness, operator training, and service dependencies.
Zero-emission bus depot
ZEV charging, depot readiness, and operator familiarization.
Control center / system upgrade
Systems readiness, failover evidence, and cutover acceptance.
Another event type?
Configure a Readiness RoomWhen a launch is governed as evidence rather than status, agencies aim to protect the service date, close trial-running issues faster, and certify readiness-for-service with a defensible record.
Outcome figures are shown as target use cases. Published proof carries an internal source, date, method, and approval record.
Plan a Revenue Service Readiness Room for your launch.
Set up a working demo around your rail, LRT, BRT, or ZEV launch — with your safety case, trial running, and cutover gates loaded in.