Metropolitan Council / Cost Scope Clarification

Two Scenario Capabilities, With One Clear Ceiling

One row sets up a training run. The new row lets instructors build and reuse plans from tools already delivered. It does not turn the simulator into a general software-development kit.

25Master rows read
+1Bounded scope split
26Estimator rows shown

What Changes In The Pipeline

Read

Master cost table

Kept exactly as read. No workbook or Slack action.

Clarify

Scenario scope overlay

Separates one-run setup from reusable authoring.

Present

River + ForgeRail

Both downstream views show the same definitions and ceiling.

The Simple Difference

Existing Row / Clarified

Training Scenario Configuration

Run-level setup using delivered scenario content: select route location, time, weather, visibility, obstructions, scheduled events, faults, and evaluation settings before a training session.

New Row / Pricing Split Required

Scenario Building Framework

A no-code instructor tool to compose, order, save, copy, load, and reuse scenarios from delivered route locations, conditions, faults, events, triggers, and evaluation rules.

The Authoring Ceiling

No-code composition of delivered simulator capabilities only. Excludes new vehicle logic, vehicle or environment assets, physics models, fault implementations, integrations, and custom scripting.

Why This Boundary Fits The Client Documents

Original RFP p. 15, section E.4; Addendum 3 pp. 7-8, response R19. The RFP requires dynamic scenario creation without vendor intervention. Addendum 3 says instructors must create and control dynamic scenarios in real time, using detailed content finalized with Metro rules, procedures, and infrastructure data.

The documents require vendor-free scenario creation and control. The no-code ceiling and exclusions are ForgeFX's explicit delivery boundary; they are not quoted client language.