Industrial & Manufacturing Heavy Construction & Infrastructure Heavy Civil Construction

Transit & Rail Infrastructure

Capital construction programs where procurement discipline, schedule certainty, and field execution determine delivery.

Example organizations in this space: Jacobs Parsons HNTB WSP

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey
  1. Funding & Fit Qualification

    Confirm project funding status, procurement timeline, decision-makers, and basic fit before investing in a full discovery.

    Qualification Questions

    Project fit and scope

    • To confirm basic fit, which of the following best describes your program's primary objective? Options: Increase capacity (new track/miles), Modernize signals and train control, Station replacements and accessibility upgrades, Grade separations and safety improvements, A combination of the above, Other (briefly describe)
    • Roughly how many new rail miles or major renewals are in scope? Options: Less than 5 miles, 5 to 15 miles, 15 to 30 miles, More than 30 miles (large program)

    Funding status

    • What is the current funding status for this program? Options: Fully funded with committed budget, Partially funded with a known funding gap, Funding expected but not yet committed, Funding contingent on an upcoming ballot or grant decision, No funding identified yet
    • If funding is not fully committed, briefly summarize the expected sources or the known gap.

    Procurement timeline

    • What procurement milestone are you targeting in the next 12 months? Options: RFP or RFQ release in 0-3 months, RFP or RFQ in 3-6 months, RFP or RFQ in 6-12 months, No procurement planned in the next 12 months, Other (briefly explain)
    • What specific date or fiscal milestone is driving that procurement timeline?

    Decision makers, compliance, and readiness

    • Who will sign the contract and who are the key influencers we should include in a discovery conversation? Options: Capital Program Director, Chief Engineer, Procurement Director, Operations Director, Executive Director / CEO, Board or oversight committee member, Other (please name)
    • Is this program subject to federal grant conditions or specific regulatory compliance that will affect procurement or delivery? Options: Yes — federal grant with FTA-like requirements, Yes — other regulatory/compliance conditions, No known regulatory constraints, Unsure
    • So we make the best use of your time: based on these details, would you like to schedule a focused 60–90 minute discovery workshop to validate scope, risks, and next steps? Options: Yes — please schedule, Maybe — please send a proposed agenda first, Not at this time
  2. Outcome Discovery

    Map desired capacity, safety targets, constraints, stakeholder priorities, and measurable success signals for the program.

    Discovery Questions

    Project snapshot: ground truth in 60 seconds

    • Briefly describe the program you are delivering, including the primary corridor, approximate scope scale, and your target completion year.
    • How many new rail miles or stations does your current program include? Options: Less than 5 miles, 5 to 15 miles, 16 to 50 miles, More than 50 miles, Station modernization only
    • Who within your organization owns program budget and schedule decisions? Options: Capital Program Director, Chief Engineer, Program Manager, Procurement Director, Shared committee
    • Which major funding sources support the program, for example local ballot measure, federal grant, state funding? Options: Local ballot measure, Federal grant, State appropriation, Public-private partnership, Other
    • Estimate the current board-approved budget range for the program. Options: Under $100M, $100M to $500M, $500M to $1B, Over $1B
    • What single program milestone, if missed, would trigger a formal funding re-evaluation by leadership?

    Where success actually shows up

    • If the program increased peak capacity by 20 percent but finished 10 percent over budget, would that meet your leadership's definition of success? Options: Yes, capacity gains outweigh cost, No, budget adherence is primary, Depends on which corridors benefit, Unsure
    • Describe the operational metrics you will use to judge success, for example peak trains per hour, on-time performance, and headway reliability.
    • How many distinct safety targets do you track today and which one is considered non-negotiable? Options: Zero formal targets, 1 to 3 targets, 4 to 7 targets, More than 7 targets
    • Who will sign final acceptance of operational metrics at the program acceptance gate? Options: Chief Operating Officer, Chief Engineer, Safety Director, Board representative, Shared signoff
    • Which measurable target would cause you to pause further construction until mitigation is approved? Options: On-time performance drop below target, Sustained safety incidents, Unacceptable signal fail rate, Failure to meet ridership projections, Other

    Where the plan bumps into reality

    • Tell me about the last time a utility discovery or unexpected geotechnical condition changed your sequencing; what happened and how did you respond?
    • When a discipline interface causes rework, which interface fails most often, civil to signals, track to power, or systems integration? Options: Civil to signals, Track to power, Train control to communications, Multiple interfaces equally, Not tracked
    • On average, how many weeks of delay does a typical rework event add to a construction phase? Options: Less than 2 weeks, 2 to 6 weeks, 6 to 12 weeks, More than 12 weeks
    • What contingency in your current plan do you now think is too optimistic?
    • Name the role that can approve scope changes which affect revenue service windows. Options: Program Manager, Chief Engineer, Operations Director, External oversight board
    • Is there a single unresolved site or utility risk that would cause you to pause the program if it cannot be mitigated within your target window? Options: Yes, No, Unsure

    Alternatives you're actively weighing

    • Tell us which option you would prefer to stick with if everything went as hoped, incumbent contractor, in-house delivery, or a new partner? Options: Incumbent contractor, In-house delivery, New external partner, Hybrid model
    • List the vendors or internal teams you have evaluated so far and the key reason each was advanced or discarded.
    • Under which circumstances would staying with your current approach remain acceptable instead of changing delivery model? Options: No cost increase, Schedule maintained, Safety record preserved, All of the above, Other
    • Has anyone proposed solving delivery internally without an outside partner, and if so who would lead that effort? Options: Yes - assigned leader exists, Yes - proposed but no leader, No internal proposal, Unsure
    • If you decided to keep delivery internal, what single capability gap would force you to switch back to an external partner?

    How you will know this worked

    • Name the single measurable signal at 12 months after service change that would make you declare the program a success. Options: Increased peak throughput, Reduced incident rate, Improved on-time performance, Maintenance cost reduction, Other
    • Do you currently have baseline ridership counts, fault logs, or maintenance records to validate that signal? Options: Ridership counts, Fault logs, Maintenance records, None available
    • Rate the accuracy and accessibility of those baseline sources. Options: High accuracy and accessible, Accurate but partial access, Questionable accuracy, Data not accessible
    • Assign the role that will own collection and reporting of the acceptance signal after go-live. Options: Operations data lead, Maintenance lead, Program controls lead, Third-party monitor, Other
    • At what point would you stop further phases and require remediation if the acceptance signal is not met? Options: Immediate pause, Allow one quarter for remediation, Allow phased fixes with monitoring, Proceed with caution

    Practical constraints that will gate any plan

    • Identify the single integration dependency, such as a specific signal interface or traction power handover, that would prevent you from accepting a phased module without mitigation.
    • Do you have APIs or test interfaces available for a vendor to validate systems integration in a staging environment? Options: Yes, full test interfaces, Limited test interfaces, No, interfaces not available, Unsure
    • Point to the organizational owner of asset data and indicate their role title for providing wiring diagrams, interlocking drawings, and asset registers.
    • Estimate the number of dedicated FTEs your team can assign to coordinate construction interfaces during the first 18 months. Options: 0, 1-3, 4-7, 8 or more
    • Are there permits or regulatory approvals not yet submitted that could delay mobilization beyond your target date? Options: Yes, Some submitted, All submitted, Unsure
    • Should the named asset owner be unable to provide full drawings within 8 weeks, would you delay awarding or require a different delivery approach? Options: Delay awarding, Require alternate delivery, Proceed with risk allocation, Unsure

    Decision dynamics and internal blockers

    • Identify the political or board-level objection that would make this program unapprovable even if technical criteria are met.
    • List the executive sponsors and what each will expect to see at the mutual commit gate.
    • Compare your target procurement window in months with the typical time required for regulatory review and indicate the gap. Options: Procurement shorter than review, Procurement matches review, Procurement longer than review, Unknown
    • Point to the internal team most likely to push back on vendor-led safety procedures, operations, or phasing and explain why.
    • Would a board requirement for a local hire percentage clause change your vendor selection criteria or timeline? Options: Yes, change criteria, Yes, extend timeline, No impact, Unsure

    Early escalations and kill-switches

    • In the event a safety incident occurs during preliminary work, what immediate action will you require from the delivery team? Options: Immediate stop work, Root cause analysis within 48 hours, Temporary mitigation and continue, Other
    • Describe the single unresolved legal or right-of-way issue that would force you to halt construction until resolved.
    • Does your operations leadership have a pre-approved set of night work windows and are those windows flexible? Options: Yes and flexible, Yes but limited, No fixed windows, Unsure
    • Specify the contractual guarantees you would need from the seller to keep the project moving past an early safety or technical gate. Options: Performance bonds, Named resource commitments, Milestone liquidated damages, Third-party verification, Other

    Practical next steps and early measures of alignment

    • Assuming you wanted an on-site proof-of-concept for the systems interface within 90 days, what must be true today for that to be possible?
    • Select the documents the seller should produce first to build confidence, for example integration test scripts, temporary works designs, or a consolidated risk register. Options: Integration test scripts, Temporary works designs, Consolidated risk register, Site survey report, Schedule baseline
    • Designate the day-to-day point of contact on your team during discovery and outcome mapping, including name, role, and contact readiness.
    • When would you be prepared to review an initial outcome map and agree to the acceptance signals? Options: Within 2 weeks, Within 1 month, Within 2 months, Longer than 2 months
    • Would you pause engagement or ask for a revised approach within a fixed timeframe if the initial outcome map does not reflect your safety targets? Options: Pause engagement, Request revision within 2 weeks, Request revision within 1 month, Work iteratively without pause
  3. Constructability & Systems Walkthrough

    Walk through how the proposed program delivers outcomes across civil, track, power, signals, and operations using the buyer's context and scenarios.

    Solution Experience

    • Constructability & Systems Walkthrough
    • Confirm the current state and its cost
    • You confirm the demonstrated walkthrough eliminates the discipline-interface ambiguity you described and materially reduces expected rework.
    • Deliver a discipline interface package within 7 business days including phased sequence diagrams, key cut sheets, and an updated constructability risk register that maps risks to mitigation actions and acceptance criteria.
    • You agree that the proposed mitigations and acceptance gates reduce schedule and cost exposure to an acceptable level.
    • Scenario-driven systems walkthrough
    • Provide the validated scenario list (for example peak service, single-track possession, emergency reroute) and the latest as-built drawing set for the corridors to be walked through.
    • Show mitigations and measurable acceptance criteria
    • You commit to the evidence items and named owners needed to finalize constructability assumptions before procurement or pre-construction.
    • Record named owners for civil, track, power, signals, and operations interfaces and capture them in the program RACI to enable decisions during pre-construction readiness.
    • Validate that the walkthrough matches your needs
    • Align immediate commitments and named owners
    • Constructability & Systems Walkthrough
    • Constructability Walkthrough Deck
    • Constructability Brief
    • meeting
    • slides
    • document
  4. Program Scope

    Define scope boundaries, phased construction modules, responsibilities, out-of-scope items, and measurable acceptance criteria.

    Scope Configuration

    • Construct New Passenger Stations
    • Build Grade Separations and Overpasses
    • Install Track Expansion and Turnouts
    • Perform Civil Earthwork and Structural Works
    • Relocate Utilities and Coordinate Conflicts
    • Install Traction Power and Substation Equipment
    • Install Train Control and Signaling Systems
    • Integrate Signaling with Legacy Systems
    • Deploy Communications and Wayside Networks
    • Maintain Revenue Service During Construction
    • On-Track Safety, Flagging, and Protection
    • System Testing, Commissioning, and Cutover
    • Deliver Operator and Maintenance Training
    • Construct Maintenance and Storage Facilities
    • Federal Funding Compliance and Closeout Support

    Scope Questions

    Construct New Passenger Stations

    • Who are the named owners on your side for station delivery (project role or discipline)?
    • How many new platforms or station platforms does your program require, listed by stop name or milepost? Options: 1-2, 3-5, 6-10, More than 10
    • Which station elements are full rebuilds versus canopy or finish upgrades (platform, concourse, elevator, signage)? Options: Full rebuild, Structural + systems, Cosmetic/fit-out only, Mixed
    • When do you need each new platform returned to revenue service (target date per station)?
    • Where will temporary passenger access routes be located during platform construction (describe adjacent streets, temporary ramps, or shuttle transfer points)?

    Build Grade Separations and Overpasses

    • List the major roadway or rail separation locations included in scope by station or milepost.
    • Identify the retaining wall, bridge, or culvert type anticipated for each separation and any reference design sheets. Options: Bridge with abutments, Retaining wall with deck, Culvert/box, Other
    • Specify the minimum vertical clearance requirements for each overpass and any clearance drawings that apply.
    • Estimate the number and location of traffic diversions or detours required during construction. Options: None, Short-term local diversions, Multi-day road closures, Multiple phased detours
    • How will environmental permits (wetland impact, stream crossings) be handled for separation structures and who holds existing permit applications?

    Install Track Expansion and Turnouts

    • Which turnout types and how many individual turnouts are included in your expansion scope (provide location and frog number if known)?
    • Specify the design speed and intended traffic mix on new track (passenger max speed, freight allowed Y/N). Options: Passenger only, ≤60 mph, Passenger only, >60 mph, Passenger + freight
    • Provide the proposed length of new continuously welded rail (CWR) in feet or track miles and reference alignment sheets.
    • Describe planned rail section and sleeper/tie types (e.g., 119RE rail, concrete ties) and any procurement constraints.
    • Indicate constraints for night work, possession windows, or limits on line blocks for turnout installation. Options: Daytime only, Nighttime possession windows, Weekend possessions, 24/7 with restrictions

    Perform Civil Earthwork and Structural Works

    • Which major cut/fill zones and structural elements (retaining walls, bridge abutments) are part of the civil scope by station or segment?
    • Specify piling or foundation types anticipated and reference geotechnical borehole IDs when available.
    • Provide allowable settlement thresholds adjacent to existing track and any instrumentation or monitoring requirements.
    • Attach or reference geotechnical report IDs and critical borehole logs for major earthwork areas.
    • Indicate erosion and sediment control measures and any seasonal restrictions for major earthworks. Options: Standard BMPs, Enhanced measures per permit, Seasonal moratoriums apply, Other

    Relocate Utilities and Coordinate Conflicts

    • How many identified utility conflict locations exist and please reference them by station or milepost? Options: 0-5, 6-15, 16-30, 30+
    • Which utility types require relocation (water, gas, telecom, electric, sewer) and indicate any high-voltage or major telecom ducts? Options: Water, Gas, Electric, Telecom, Sewer
    • Provide existing as-built or utility record drawing references and any known discrepancy reports.
    • Describe the need for temporary bypasses, service interruptions windows, and customer notification requirements for utility moves.
    • Indicate whether utility relocations require third-party easements or long-lead ROW agreements. Options: Yes, easements required, No easements, Unknown, needs review

    Install Traction Power and Substation Equipment

    • Which traction power substations or upgrade sites are included and provide site IDs or mileposts.
    • Specify required substation single-line diagrams (SLD) or one-line references and whether new SLDs must be created. Options: Existing SLDs available, New SLDs required, Partial SLD updates
    • Provide target kVA capacity and N+1 redundancy requirements for new or upgraded substations.
    • Describe conduit, cable routing, and clearance constraints from substation to overhead catenary or third rail.
    • Indicate preferred transformer spare ratio and maintenance space requirements in the substation footprint. Options: No spare, 1 spare, Space reserved for future spare

    Install Train Control and Signaling Systems

    • Who are the named owners for train control interface points on your operations team (title or discipline)?
    • How will interface test harnesses to interlockings be provisioned and where are test panels located by station?
    • Which train control logic change requests are anticipated and please reference interlocking IDs or relay bays?
    • Provide expected fail-safe behavior definitions for new interlockings and diagnostics alarms to be generated.
    • Indicate wayside equipment types planned (axle counters, track circuits, balises) and any preference for specific detection technology. Options: Axle counters, Track circuits, Balises/loops, Hybrid

    Integrate Signaling with Legacy Systems

    • Which legacy signaling systems and interlocking versions require protocol gateways or conversion (list interlocking IDs)?
    • Specify data mapping requirements between new signaling outputs and legacy SCADA or dispatch screens.
    • Provide legacy firmware baselines, relay logic references, or interface control documents if available.
    • Describe fallback or degraded-mode operations when integration nodes or gateways fail during service.
    • Estimate the number of protocol gateway ports or conversion nodes required by corridor segment.

    Deploy Communications and Wayside Networks

    • Indicate the required wayside network bandwidth and redundancy targets for train control communications (Mbps and redundancy topology).
    • Select the communications media you plan to use for wayside networks. Options: Fiber optic, Radio (licensed), Copper/ethernet, Hybrid
    • Who will manage IP addressing, VLAN design, and network segmentation for wayside devices?
    • How will latency and jitter be measured as acceptance metrics for train control communications?
    • Attach any network design diagrams, fiber route IDs, or telecom provider handoff points that exist.

    Maintain Revenue Service During Construction

    • Which passenger continuity measures are mandatory to maintain revenue service (temporary platforms, bus bridges, reduced headway operations)?
    • Specify acceptable single-leg service reductions or maximum daily delay per corridor segment (minutes/hours).
    • Provide your plan or reference for planned weekend possessions and expected frequency per month. Options: None, 1-2 weekends, 3-4 weekends, Weekly possessions
    • Describe temporary operational mitigations (turn-backs, skip-stop) and where timetable changes will be published.
    • Indicate staffing or passenger protection requirements at stations during construction (crowd managers, temporary attendants).

    On-Track Safety, Flagging, and Protection

    • Select which on-track safety certification regimes apply to your project. Options: Federal Railroad Administration (FRA), Regional transit regulator, Agency internal standard, Other
    • Who will provide qualified flaggers, watchmen, or on-track safety personnel and how are they certified?
    • How will possession handbacks be documented nightly (form, sign-off workflow, digital record)?
    • Provide required lockout/tagout (LOTO) and electrical isolation procedures for work adjacent to live third rail or catenary.
    • Describe contingency procedures for emergency egress from work zones adjacent to active track.

    System Testing, Commissioning, and Cutover

    • Which system test types are required for cutover at each interface: factory acceptance test, site acceptance test, integration, or stress tests? Options: FAT, SAT, Integration, Stress/soak
    • Specify performance thresholds for signal block occupancy reporting, interlocking response times, and end-to-end ATP (positive train control) latencies.
    • Provide the planned FAT and SAT schedule and who will witness each test (agency roles).
    • Describe alarm, logging, and event retention requirements during commissioning and cutover tests.
    • What measurable acceptance criteria will confirm successful commissioning of integrated signal and traction systems (for example end-to-end ATP performance thresholds, failover time, and zero critical defects)?
  5. Mutual Commit

    Finalize commercial, regulatory, and compliance terms, confirm resourcing and procurement deliverables, and document mutual obligations to begin work.

    Agreement Modules

    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Commercial Proposal & Price Schedule
    • Insurance and Bonding Addendum
    • Regulatory Compliance Addendum (Federal/State Funding Conditions)
    • Procurement and Resource Commitment Schedule
    • Subcontractor Approval and Flow-Down Agreement
    • Change Order Agreement
    • Termination and Suspension Terms
    • Health, Safety and Site Access Agreement
    • Commissioning and Acceptance Protocol
  6. Construction Execution

    Operationalize construction with readiness checks, sequenced execution, and formal go-live acceptance.

    1. Pre-Construction Readiness

      Capture permits, track possessions, utility relocation plans, access, and named owners required before mobilization.

      Pre-Deployment Questions

      Environment and site access

      • Confirm the deployment site(s) where the seller will mobilize — list each site name/identifier and the site-specific staging area we should plan for (so we can produce per-site mobilization modules).
      • For each listed site, is permanent or temporary access (right-of-way, staging, vehicle/equipment access) secured? Select the best current state — we use this to sequence early mobilization. Options: Yes — access fully secured for all listed sites, Partial — some sites secured, some pending, No — access not secured, Access not required for listed sites

      Permits, possessions and approvals

      • Which permit categories are still outstanding for the project work areas? Select all that apply — this tells us which approvals will gate mobilization. Options: None — all permits obtained, Traffic/roadway, Right-of-way/landowner, Railway authority possession, Environmental/air/land, Stormwater/erosion control, Building/structural, Utility work permits, Other
      • For required track possessions, list each possession window already approved or marked 'TBD' and name the approving authority (so we can lock the construction schedule).

      Utilities and site constraints

      • What is the current status of utility relocations affecting the work (so we can plan sequencing and contingency)? Options: All utilities relocated and schedule confirmed, Relocations planned and scheduled but not complete, Relocation designs approved but permits pending, No relocations required, Status unknown — buyer to confirm
      • Which utilities (electric, gas, telecom, water, sewer, other) require relocation and which party is responsible for coordination and sign-off? Provide the responsible owner for each utility.

      People, timing and constraints

      • Please provide the named owner (name and role) for these pre-construction deliverables: permits, track possessions, utility relocations, site access, and safety/operations liaison — one owner per deliverable (so we can assign tasks and approval points).
      • Has a joint safety and operations interruption plan for work adjacent to active service been reviewed and approved by the buyer's operations team? Options: Yes — approved and signed, Yes — approved, pending signatures, Drafted and under review, Not started
      • Are there fixed blackout windows, peak service hours, or special events that limit construction access? Select all that apply — if any apply, provide the specific dates or recurring windows in the adjacent field. Options: No blackout constraints, Daily peak service hours restrict work, Nighttime-only work allowed, Weekend-only possessions required, Fixed blackout dates (holidays, events)
      • Are there hard gating procurement or regulatory milestones the seller's mobilization depends on (for example, grant release, long-lead supplier delivery, regulatory sign-off)? If yes, list milestone name and expected date so we can include it on the critical path.
    2. Construction Configuration

      Lock execution-level details the delivery team will use — phasing schedules, possession windows, signaling interface points, and test plan parameters.

      Configuration Details

      Construction Configuration — Locking execution-level details

      • Execution plan identifier the delivery team will reference (single value; exact string used in schedules and reporting — e.g., 'NC-ExecPlan-v1')
      • Role-to-owner mapping for core execution responsibilities (enter semicolon-separated pairs in the format Role=OwnerRoleName; example: 'Phasing Schedule Lead=Program Scheduling Lead;Possession Approvals=Construction Manager;Test Plan Owner=Systems Integration Lead;Escalation Contact=Program Director') — single value

      Phasing & Possession Windows

      • Phasing model the delivery will follow (select one) Options: Multi-phased sequential (defined, non-overlapping phases), Rolling possessions windows (recurrent short windows), Accelerated overlap (parallel phases with dependencies managed), Continuous single-phase (no formal phase breaks)
      • Maximum possession window length in hours (numeric; Default is 8)
      • Authoritative phasing schedule document URL (single value; format: https:// — the delivery will fetch and reference this document)

      Signaling & Systems Integration

      • Signaling interface approach the program will use (select one) Options: Staged cutover (parallel testing of new system then cutover), Interface adapter between legacy and new systems, Full replacement with new interface specification, Temporary bypass/isolation with later integration
      • Signaling interface point identifiers (single semicolon-separated value; platform will parse into a list — example: 'SIP-001;SIP-002;SIP-003')

      Testing, Commissioning & Acceptance

      • Planned system integration test duration in days (numeric; Default is 7)
      • Commissioning acceptance threshold — percent of required subsystem tests that must pass to allow a go decision (numeric; Default is 100)
    3. Construction Execution

      Manage phased construction, coordination with operations, safety controls, and schedule milestones with clear owners and escalation paths.

    4. Go-Live Acceptance

      Formal acceptance gate confirming commissioning, systems integration tests, safety approvals, and operational readiness signed by named owners before service changes.

      Checklist items

      • Complete and sign Integrated Systems Test (IST) report
      • Accept final commissioning report
      • Obtain written Permission to Operate / Permission to Energize
      • Verify Lockout/Tagout (LOTO) and electrical isolation records
      • Confirm protective device and relay settings verification
      • Deliver and have acknowledged as-built documentation and configuration baselines
      • Close or formally accept punchlist with operational blockers defined
      • Complete operations and maintenance training sign-offs
      • Issue Service Change Authorization and cutover notice
      • Execute and validate rollback/recovery plan
      • Obtain formal safety acceptance
  7. Success

    Monitor operational outcomes, capture lessons learned, and track issues and enhancements through a shared review cadence.

    Success Reviews

    • Go-live Health Check (Week 1-4)
    • First Measurement Review (Weeks 4-10)
    • 90-day Realization Review and Remediation Closeout
    • Quarterly Operational Review
    • Annual Lessons Learned and Program Transition Review

    Issues & Enhancements

    • Owners to resolve the top three operational issues with documented verification within the quarter.
    • Verify phased milestone completion rate and traction power availability are documented and owners accept verification methods.
    • Agree the ongoing monitoring cadence and the content of the recurring operational reports.
    • Publish the remediation closeout register with evidence attachments and verification checklists.
    • Deliver the first quarterly operations report template and data pipeline definitions for ongoing measurement.
    • Confirm dates for operational handover activities required to move to recurring reviews.
    • Review quarter-to-date KPI trends
    • Keep signaling MTTR and milestone completion moving toward Program Scope targets through targeted remediation.
    • Ensure persistent issues are prioritized and have clear verification steps to prevent recurrence.
    • Maintain a prioritized operational backlog with agreed quarterly commitments.
    • Re-confirm success criteria and owners
    • Update the milestone schedule and publish an adjusted completion forecast.
    • Provide a post-incident report for any signal system outages including root cause and corrective actions.
    • Year-to-date outcomes vs discovery targets
    • Validate whether passenger capacity and safety outcomes meet the expectations captured in Outcome Discovery and document any accepted variances.
    • Produce a formal lessons learned record with recommended process changes and design notes for future programs.
    • Confirm complete transfer of operational responsibilities and long-term monitoring ownership to the operations organization.
    • Publish the annual lessons learned report including root-cause analyses and recommended changes to standards or procedures.
    • Deliver final operations handover package including runbooks, spare parts lists, and maintenance schedules.
    • Establish the 12-month monitoring plan with named monitoring owner roles and reporting dates.
    • Confirm the system baseline is stable for initial operations and that no showstopper defects remain open.
    • Establish an initial remediation plan with completion dates for all high-severity open defects.
    • Confirm operator and control-room operational checks and training status required for safe service.
    • Publish the post-launch issue log with severity, interim mitigations, and target close dates.
    • Provide evidence of operator procedure training completion and control-room readiness checklist.
    • Schedule the First Measurement Review and circulate required data extracts in advance.
    • Present first-period data vs targets
    • Determine whether peak hour train throughput and safety incident rate are moving toward the Outcome Discovery targets or require corrective plans.
    • Close or assign all high-severity go-live defects and capture concrete resolution dates.
    • Confirm the legacy system has been decommissioned or has an approved, time-boxed retention plan with archival evidence.
    • Deliver an updated KPI dashboard including data source annotations and measurement windows for throughput and safety metrics.
    • Publish a remediation plan listing tasks, acceptance criteria, and target close dates for each open item.
    • Provide documentation evidencing decommissioning or approved read-only retention and data archive completion.
    • Restate the source acceptance criteria
    • Close all remaining high- and medium-severity remediation items or agree time-boxed conditional closures with verification steps.
    • Deployment and system validation
    • Root-cause diagnosis for any gaps
    • Capture lessons learned and root-cause summaries
    • Present cumulative outcome data vs criteria
    • Surface and prioritize persistent operational issues
    • Open remediation register review
    • Confirm operations and maintenance handover status
    • Incumbent system decommission status and fallback closure
    • Agree quarter remediation and verification tasks
    • Early adoption and operational readiness signals
    • Agree final verification steps and timelines
    • Open defects and blockers triage
    • Agree unresolved item resolution plan and monitoring
    • Agree corrective actions, owners, and dates
    • Operational improvement backlog review
    • Transition plan to ongoing cadence
    • Agree immediate remediation actions
    • Short status and next steps wrap-up
    • Confirm timeline to remediation closeout
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.