Transit & Rail Infrastructure
Capital construction programs where procurement discipline, schedule certainty, and field execution determine delivery.
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
-
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?
- Roughly how many new rail miles or major renewals are in scope?
Funding status
- What is the current funding status for this program?
- 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?
- 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?
- Is this program subject to federal grant conditions or specific regulatory compliance that will affect procurement or delivery?
- 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?
-
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?
- Who within your organization owns program budget and schedule decisions?
- Which major funding sources support the program, for example local ballot measure, federal grant, state funding?
- Estimate the current board-approved budget range for the program.
- 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?
- 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?
- Who will sign final acceptance of operational metrics at the program acceptance gate?
- Which measurable target would cause you to pause further construction until mitigation is approved?
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?
- On average, how many weeks of delay does a typical rework event add to a construction phase?
- 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.
- 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?
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?
- 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?
- Has anyone proposed solving delivery internally without an outside partner, and if so who would lead that effort?
- 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.
- Do you currently have baseline ridership counts, fault logs, or maintenance records to validate that signal?
- Rate the accuracy and accessibility of those baseline sources.
- Assign the role that will own collection and reporting of the acceptance signal after go-live.
- At what point would you stop further phases and require remediation if the acceptance signal is not met?
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?
- 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.
- Are there permits or regulatory approvals not yet submitted that could delay mobilization beyond your target date?
- Should the named asset owner be unable to provide full drawings within 8 weeks, would you delay awarding or require a different delivery approach?
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.
- 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?
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?
- 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?
- Specify the contractual guarantees you would need from the seller to keep the project moving past an early safety or technical gate.
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.
- 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?
- 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?
-
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
-
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?
- Which station elements are full rebuilds versus canopy or finish upgrades (platform, concourse, elevator, signage)?
- 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.
- 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.
- 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).
- 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.
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.
Relocate Utilities and Coordinate Conflicts
- How many identified utility conflict locations exist and please reference them by station or milepost?
- Which utility types require relocation (water, gas, telecom, electric, sewer) and indicate any high-voltage or major telecom ducts?
- 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.
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.
- 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.
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.
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.
- 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.
- 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.
- 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?
- 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)?
-
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
-
Construction Execution
Operationalize construction with readiness checks, sequenced execution, and formal go-live acceptance.
-
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.
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.
- 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)?
- 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?
- 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.
- 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.
-
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)
- 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)
- 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)
-
Construction Execution
Manage phased construction, coordination with operations, safety controls, and schedule milestones with clear owners and escalation paths.
-
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
-
-
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