Metropolitan Council · LRT Operator Training Simulator · FR-36

12-Month Base-Term Delivery Schedule

A pre-award, dependency-led schedule aligned to the one-year initial contract term. Extension work is deliberately outside this base-term Gantt.

BASE DURATION: EXACTLY 12 MONTHS
Calendar dates are not proven. Month 1 means contract execution / formal kickoff. Contract award, kickoff, review, acceptance, installation, and handover dates must be confirmed after award; this artifact does not invent them.
Workstream / typed dependency
M1M2M3M4M5M6M7M8M9M10M11M12
Mobilization, Scope Confirmation & Delivery BaselineM1–M2 · contract execution
Metro Source Data, SME Access & Acceptance PlanM1–M3 · SS:mobilize
Architecture, Cab Interfaces & PrototypeM1–M4 · SS:mobilize
Route, Yard, Infrastructure & Environment ProductionM3–M8 · PI:inputs, PI:architecture
S700 Cab, Controls, Displays & Hardware IntegrationM3–M8 · PI:inputs, PI:architecture
Instructor Station, Scenarios, Faults & EvaluationM4–M9 · PI:architecture
Integrated Build, Verification & Acceptance CyclesM7–M10 · PI:content, PI:cab, PI:training
Installation, Commissioning, Training & HandoverM10–M12 · PI:integration
Controlled Contingency & Defect ClosureM11–M12 · FS:integration
Base deliveryClient-input / technical integrationVerification, acceptance, installation or contingency

FS finish-to-start (predecessor ends before successor starts) · SS start-to-start · PI progressive input (predecessor is active when successor starts) · FC finish-coincident milestone

Compact Month Ranges

Milestones & Review Gates

  • M2 · Scope & Acceptance BaselineReview / decision gate · FC:mobilize.
  • M4 · Design / Prototype ReviewReview / decision gate · FS:inputs, FC:architecture.
  • M8 · Integrated Alpha ReviewReview / decision gate · FC:content, FC:cab.
  • M10 · Beta / Formal Acceptance StartReview / decision gate · FC:integration, FS:training.
  • M12 · Commissioning, Training & Base-Term HandoverPlanned base-term completion · FC:install, FC:contingency.

Base-Term Guardrails

The base includes one operator station, one instructor station, one observer station, S70/S700 simulation context, both current lines, both extensions, yards and related infrastructure, as clarified by Addendum 3.

Acceptance is staged: scope and criteria baseline before scale-up; prototype/design review before production; integrated alpha and beta/formal acceptance before installation; commissioning, train-the-trainer, defect closure, and handover by Month 12.

Any extension beyond the base term is an option requiring a duly executed contract action—not assumed schedule capacity.

Schedule Basis, Dependencies & Open-Date Flags

BasisApplied Schedule TreatmentConfidence
RFP contract-term statement, confirmed in the July 15 meetingOne-year initial term beginning at contract execution; up to 24 months only through extension options. Gantt ends at Month 12.Confirmed meeting decision; exact execution date not proven.
Addendum 3Expanded base scope is absorbed through parallel content, cab, training, and integrated acceptance work—not moved into an 18-month schedule.Client-issued source; its schedule dates were not established in this artifact.
Metro-provided data and SME / acceptance accessSS dependencies start mobilization, inputs, and architecture together. PI dependencies allow M3 production to consume approved inputs progressively while source-data and architecture work continue. Late data, facility readiness, or delayed decisions shift affected milestones through change control.Typed dependency, not a committed Metro date.
Installation, commissioning, training and warranty/support readinessReserved M10–M12 after integrated verification and formal acceptance start; controlled contingency runs M11–M12.Planned sequencing; site readiness date not proven.