TEST VERIFICATION RESULTS

Nine System Test Plans (STPs) were executed to demonstrate that elements of the Connecting the West system operate as they were designed to. Each STP consisted of a series of Test Cases focused on details of the relevant Test Plan, with a total of 32 Test Cases. Since each of the Connecting the West states have independent central systems managing their V2X deployments, many of these Test Cases were executed in each state. A few Test Cases were applicable to only one or two of the states. Details of the STPs and Test Cases can be found in the Operational Readiness Plan (ORP).

Test Verification Results for each Test Case are provided below.

STP-1: Central Systems Create and Exchange Event Reports

Tests the ability of each state’s central system to generate traffic event reports (like closures or construction) using the standard ngTMDD structure. It verifies that these reports are successfully pushed to and consumed from the Situation Data Exchange (SDX).

STP-2: Central Systems Support TIM Exchanges

Ensures that central systems can create, send, update, and expire ASN.1 UPER-encoded TIMs through the SDX, and validates that central systems can process multiple versions of the SAE J2735 standard.

STP-3: Central Systems Create and Disseminate TIMs

Tests the end-to-end flow of critical safety and situational messages. Verifies that central systems can ingest incoming vehicle data to build Curve Speed Warnings (CSW), deploy downstream/statewide situational TIMs to Roadside Units (RSUs), and successfully share data with authorized third parties through the SDX.

STP-4: Central Systems Support Data Storage

Validates that the cloud architecture can scale to store the massive influx of new V2X data. Isolates storage metrics by message type—tracking BSMs (vehicle data), TIMs (hazard alerts), SRM/SSMs (transit priority metrics), MAP/SPaT (intersection geometry/phasing), and SDSMs (pedestrian safety packets) against each state's data retention policy.

STP-5: Central Systems Monitor Field Equipment Health

Tests the back-office health monitoring systems. By comparing actual ingested message counts against standard theoretical broadcast rates, it checks if the central systems accurately identify when an RSU drops messages or goes offline.

STP-6: Field Equipment Compatibility

Verifies that newly installed RSU hardware can actively understand and transmit standards-compliant packets. Checks crucial security frameworks—ensuring RSUs can validate cryptographic SCMS certificates from external agency vehicle fleets.

STP-7: Field Equipment Deployment Locations

Confirms that newly deployed RSUs were placed at intersections supporting project needs (active transit, snowplow, or emergency vehicle corridors), and along critical roadways (Interstates, US routes, or state highways).

STP-8: SCMS Top Off Without Cellular Communications

Verifies that OBU fleet vehicles without cell modems can connect to secure Wi-Fi networks at DOT maintenance depots to successfully download their security credential certificates from the SCMS provider.

STP-9: Vehicle System Compatibility

Confirms that project OBUs (on transit buses and the GM Test Vehicle) successfully parse incoming messages across different protocol versions (2016 and 2024), generate clean outgoing data, and correctly interpret/trust SCMS security signatures when crossing state lines.