Procurement Path
All questions had to route through QuestCDN by June 5, with responses via addendum. The proposal deadline was June 18 at 2:00 PM Central Time, and award timing was targeted for August.
Metropolitan Council Proposals | Executive Summary
Light Rail Training Simulator First Call
Pre-proposal meeting summary for the Metropolitan Council Light Rail Train Operator Training Simulator RFP. Source: Fireflies transcript 01KT6YHDGSBQ9W11C7YABCVHA1, recorded June 3, 2026.
Executive Readout
The call established the procurement rules and technical boundaries for Metro Council's light rail operator training simulator. The opportunity centers on a Siemens-only cab simulator for the Blue Line, Green Line, and Green Line Extension, with pricing and implementation risk driven by the quality of Metro-provided route data, hardware specificity, and addendum responses.
Evaluation Weight
Price was described as roughly equal in importance to the combined non-price criteria: proposal quality, qualifications, and experience. That means assumptions and exceptions need to make the price defensible, not just low.
Technical Scope
The simulator scope covers Metro Blue Line, Green Line, and Green Line Extension. Metro described a Siemens train focus, cab controls, signaling, station counts, corridor profiles, and a simulator room under construction.
Data Dependency
CAD, GIS, track charts, timetables, station counts, mileage, corridor profiles, and route characteristics were called out as critical inputs. Weak or missing data is the central pricing and schedule risk.
Proposal Implications
| Area | Implication |
|---|---|
| Base simulator | Frame the base offer around Siemens cab operation and training outcomes, not a generic transit visualization. |
| Route model | Separate known route scope from assumptions about data fidelity, landmarks, extension maturity, and track geometry. |
| Hardware | Clarify whether real controllers, mixed physical/digital controls, or client-provided equipment are included or optional. |
| Compliance | Required forms include Workforce Certification, Equal Pay Certification, Subcontracting Declaration, and Conflict of Interest. |
Follow-Up Owners
Greg
Send written data needs for CAD, GIS, track charts, and timetables so Metro can include them in the addendum.
Greg
Provide quantitative data requests such as station counts, mileage, and route characteristics to support proposal preparation.
Laura
Submit hardware questions about physical and digital controls, master controllers, and train equipment availability.
Metro
Issue addendum responses, scope slides, data availability clarifications, certification guidance, and RFP numbering corrections.
Source packet: Fireflies meeting 01KT6YHDGSBQ9W11C7YABCVHA1. Local meeting archive: channels/metropolitan_council_proposals/meetings/2026-06-03-metropolitan-council-light-rail-train-operator-training-simulator-meeting-fireflies-id-01KT6YHDGSBQ9W11C7YABCVHA1.md