Metropolitan Council / Metro Transit

LRT Operator Training Simulator Requirements

Known project requirements consolidated from the client-issued RFP, Addendum 1, pre-proposal materials, and focused compliance extracts.

Contract 25P049 Addendum 1 / June 4, 2026
S700Siemens vehicle model only
50.75 miExisting and planned corridors
180° min.Required visual field of view
3 yearsMinimum support requirement
01

System and Purpose

  1. 1.1Complete simulator systemDesign, provide, install, and support a Light Rail Train operator training simulator for Metro Transit.RFP p14
  2. 1.2Real operating environmentReplicate mainline alignments, yards, facilities, and operational features encountered by Metro Transit operators.RFP pp3,14
  3. 1.3Training usesSupport initial qualification, remedial instruction, performance evaluation, and ongoing operator development.RFP p14
  4. 1.4Realistic learning environmentProvide an immersive, realistic environment that improves operator safety, proficiency, emergency response, and instructor efficiency.RFP p14
  5. 1.5Standalone operationOperate as a standalone training platform. Any required Metro IT integration must pass Council architecture, security, and review requirements.RFP p14
02

Rail Network

  1. 2.1Blue LineModel the existing 12.4-mile Blue Line and the planned 13-mile extension. The existing corridor connects downtown Minneapolis and Mall of America and serves 19 stations.RFP p14 / ADD p9
  2. 2.2Green LineModel the existing 10.8-mile Green Line. The corridor connects downtown Minneapolis and downtown Saint Paul and serves 23 stations.RFP p14 / ADD p10
  3. 2.3Green Line ExtensionModel the 14.55-mile Green Line Extension under construction. It connects downtown Minneapolis and Eden Prairie and serves 16 stations.RFP p14 / ADD p11
  4. 2.4Track and infrastructureAccurately represent track, alignment, infrastructure, yards, facilities, and operating features across existing and planned corridors.RFP p14
  5. 2.5SignalsRepresent applicable train signals, ABS signals, bar signals, and lunar crossing lights. Automatic Train Protection is not installed and is not required.ADD pp9,16
  6. 2.6Corridor profile dataUse corridor profile maps for the two existing lines. The Green Line Extension profile map was identified as forthcoming.ADD p17
03

Cab, Hardware, and Visuals

  1. 3.1Siemens S700 onlyReplicate the Siemens S700 light-rail vehicle cab. Metro operates S70 and S700 vehicles, but the simulator requirement is to model only the S700.ADD p12
  2. 3.2Full-scale cabProvide full-scale replication of the current vehicle cab layout and functionality, with the ability to incorporate future cab configurations.RFP pp14-15
  3. 3.3High-resolution visualsProvide high-resolution visual presentation with a minimum 180-degree field of view.RFP p15
  4. 3.4Physics and environmentProvide realistic weather, track, infrastructure, and vehicle-physics modeling.RFP p15
  5. 3.5Power protectionInclude UPS/APS support for orderly shutdown and equipment protection.RFP p15
04

Instructor and Training Functions

  1. 4.1Instructor stationInclude a central instructor station for real-time management, monitoring, and influence of training sessions.RFP p15
  2. 4.2Fault injectionAllow instructors to inject malfunctions during training.RFP p15
  3. 4.3Dynamic scenariosAllow instructors to control scenarios and create dynamic scenarios, emergency conditions, and rulebook modifications without vendor intervention.RFP p15
  4. 4.4Concurrent stationsSupport multiple operator and instructor stations operating concurrently to improve instructor use and trainee throughput.RFP p14
  5. 4.5Training data managementAllow instructors to manage training data from the instructor station.RFP p15
05

Data, Playback, and Distributed Use

  1. 5.1Council data ownershipProvide the Metropolitan Council full ownership of generated simulator data.RFP p15
  2. 5.2Recording and playbackRecord simulator sessions and provide playback functionality.RFP p15
  3. 5.3Reporting and data miningSupport ad hoc and scheduled reports of generated data and provide data-mining capability.RFP p15
  4. 5.4Desktop and remote simulationInclude desktop and remote simulation visual-display options with observer and playback capabilities.RFP p15
  5. 5.5System scalabilityAllow expansion for additional trainees and future physical alignment changes.RFP p15
06

Facility, Installation, and Delivery

  1. 6.1Installed systemDeliver a fully installed simulator with instructor and trainee workstations in Metro Transit's training facility.RFP p16
  2. 6.2Delivery accessPlan delivery through a 9-foot-wide street-access door, a 12-by-24-foot corridor, and a 7-foot 4.5-inch-wide simulator-room entry.ADD p19
  3. 6.3Simulator roomInstall within the identified oblong simulator room, which was under construction when Addendum 1 was issued.ADD p20
  4. 6.4Negotiated scheduleProvide a detailed design-through-payment timeline in the proposal. The final project timeline will be negotiated and incorporated into the contract.RFP pp7,16
07

Training, Documentation, and Support

  1. 7.1Operator trainingProvide one operator-training course.RFP p15
  2. 7.2Train-the-trainerProvide one train-the-trainer course for at least three full-time instructors.RFP p15
  3. 7.3Controlled documentationProvide user manuals and technical documentation in digital and print formats with revision control.RFP p15
  4. 7.4Three-year supportProvide at least three years of technical support, software updates, replacement parts, and warranty details.RFP p15
  5. 7.5Calibration certificationCertify initial system performance and identify ongoing calibration needs.RFP p15
  6. 7.6Support packageDeliver a support plan, warranty, and service agreements with the simulator.RFP p16
08

Proposal Submission Requirements

  1. 8.1Due dateSubmit by July 21, 2026, at 2:00 PM local time. The addendum supersedes earlier due dates.ADD pp2,4
  2. 8.2Electronic PDF submissionSubmit the proposal electronically in PDF format through QuestCDN. Late submission is not accepted.ADD pp2,4
  3. 8.3Required proposal contentInclude qualifications, relevant experience, a detailed work plan and schedule, visual/display approach, training approach, support model, updates, repairs, parts, warranties, maintenance, and calibration.RFP p7
  4. 8.4Price proposalInclude a detailed price proposal executed by an officer of the proposing firm.RFP p7
  5. 8.5Required certificationsSubmit subcontractor information and conflict-of-interest forms. Submit workforce certification above $100,000 and equal-pay certification above $500,000.RFP pp7,35-40
  6. 8.6Contract exceptionsIdentify contract exceptions by redlining the sample contract and including it with the proposal.ADD p5
09

Contract and Compliance Requirements

  1. 9.1Safety and legal complianceComply with applicable safety, industry, local, state, and federal requirements.RFP p15
  2. 9.2InsuranceMaintain required commercial general liability, automobile, workers' compensation, employers' liability, professional liability, and applicable pollution liability coverage.RFP pp23-26
  3. 9.3Key insurance limitsCGL: $1M occurrence / $2M aggregate; auto: $1M; employers' liability: $500K; professional liability: $3M; applicable pollution liability: $5M.RFP pp24-25
  4. 9.4Subcontractor approvalObtain written Council consent before subcontracting and disclose subcontractors and their scopes. Flow applicable contract obligations into subcontracts.RFP p27
  5. 9.5Council ownershipProvide project documents and records to the Council. Deliverables become Council property, with rights to reproduce, distribute, modify, and use them for Council purposes.RFP p28
  6. 9.6Accessible deliverablesPrepare deliverables in Standard English, US units, and accessible electronic formats compatible with the Council's agreed software formats.RFP p28
10

Known Limits and Conditional Items

  • Vehicle: S700 only. The S70 is identified but explicitly excluded from modeling.
  • Automatic Train Protection: not installed on Metro's system and therefore not part of the simulator requirement.
  • Metro IT integration: conditional, not automatically required. The simulator must operate standalone.
  • Green Line Extension data: the corridor profile map was not yet available in Addendum 1 and was described as forthcoming.
  • Schedule: no fixed project completion date is stated; the timeline will be negotiated.
  • Facility: the simulator room was still under construction when the client issued the pre-proposal materials.
Source rule: Spoken pre-proposal discussion does not change the written RFP. Only a written addendum changes the requirements.
11

Client Source Documents

Original RFP / Contract 25P049Primary technical, submission, legal, and compliance requirements Addendum 1 and Pre-Proposal MaterialsRevised dates, S700 scope, lines, signals, profiles, and facility access QuestCDN Submission ExtractElectronic submission and proposal package requirements Workforce Certification ExtractCertification obligations tied to proposal value Insurance Requirements ExtractRequired coverage, limits, endorsements, and verification