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. The FTA Readiness Review — Oversight Procedure 54 — draws the same line: before revenue service a sponsor must evidence system integration testing, safety and security certification, pre-revenue operations, and the management capacity and capability to operate, not just contract completion. CitiriOS is where a sponsor produces and governs that readiness.
Tailored to the FTA Readiness Review.
FTA Oversight Procedure 54 defines readiness for service in four parts. CitiriOS runs all four as one evidence-backed Readiness Room — and keeps owner readiness distinct from delivery completion.
CitiriOS references FTA Oversight Procedure 54 to describe transit readiness scope. Ready Score and Readiness Room are CitiriOS features, not regulatory terms or requirements.
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 Centers 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
Statutory safety certification and SSOA approval — the regulatory hard gate confirmed under the FTA Readiness Review; cannot be overridden by the owner.
Service commencement
Owner acceptance to begin revenue service, recorded with residual conditions.
Built for Transit.
Every CitiriOS module maps to how transit agencies run service launches.
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, organized to the FTA Readiness Review scope 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.
Supports every launch type.
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 protect the service date, close issues faster, and certify readiness-for-service with a predictable outcome and defensible record.
Outcome figures are shown as target use cases. Published proof carries an internal source, date, method, and approval record.
Demo a Revenue Service Readiness Room for your launch type.
Set up a working demo around your rail, LRT, BRT, or ZEV launch — with your safety case, trials, and cutover gates loaded in.