3-04. SCOPE OF WORK.V2X Management System.final.docx

SCOPE OF WORK

UTAH DEPARTMENT OF TRANSPORTATION (UDOT)

VEHICLE-TO-EVERYTHING (V2X) MAINTENANCE AND MANAGEMENT SYSTEM

Purpose of this Solicitation The purpose of this RFP is for the State of Utah to enter into a contract on behalf of the Utah Department of Transportation (UDOT) with a vendor to provide the development, implementation, and maintenance of a Vehicle-to-Everything (V2X) Maintenance and Management System to support UDOT’s V2X system, sometimes referred to as a Connected Vehicle Ecosystem. As described below, UDOT’s current V2X Maintenance and Management System is known as Cirrus by Panasonic; retention or replacement of this system and its functions at the expiration of the current contract with Panasonic is the primary goal of this RFP.

This RFP replaces an earlier RFP that was cancelled because of errors and omissions in the earlier RFP documents. Since cloud hosting and data management costs constitute a substantial portion of the overall cost of this V2X Maintenance and Management System, this RFP requires vendor response on how those costs will be managed and those costs have been added to the price proposal as a scored item. Other modifications have also been made to clarify components of the UDOT V2X system and various system requirements.

Background of the System UDOT desires to work with a vendor for the development and implementation of a V2X Maintenance and Management System to support our mature and growing connected vehicle deployment. UDOT envisions that the system will consist of a cloud-based, user-friendly, adaptable, platform / dashboard which will collect V2X data generated by and through our V2X Roadside Units (RSU), process and analyze that data for the purposes of monitoring system performance, manage and store the data, display information, analytics, and alerts, and provide data portals for users to access the data. In addition, the system will provide tools for monitoring and managing RSUs, OBUs, and related system components to support UDOT’s troubleshooting, maintenance and asset management of those devices. Since the Connected Vehicle Ecosystem generates large amounts of data, another element of the system will be to manage data flows to minimize data-related cloud costs. The vendor may propose system elements that are not hosted in the cloud.

Connected vehicle technology is the next generation of traffic management. It can provide mobility improvements, increased transportation reliability, reduced environmental impacts, and safety benefits. UDOT’s ultimate goal for connected vehicle technology is to provide information to drivers (both human and automated) which can prevent crashes and save lives. Connected vehicle technology is part of UDOT’s effort to reach Zero Fatalities in our transportation system.

V2X Hardware UDOT has been involved in planning for and deploying connected vehicle technology for almost 20 years and has functional V2X deployments that date back to 2017. Current and in-progress deployments, using Cellular V2X (C-V2X) hardware operating in the 5.9GHz spectrum, span much of the State of Utah.. A map of the UDOT projects, and information about other aspects of the V2X system, can be found at our website: transportationtechnology.utah.gov.

Field components of the current system include:

· C-V2X RSUs on 385 UDOT signalized intersections.

· C-V2X RSUs on 46 Orem City and Logan City signalized intersections.

· C-V2X RSUs at 92 locations along interstate or rural, non-signalized roadways.

· C-V2X On-Board Units (OBUs) on 421 UDOT, UTA and Orem fleet vehicles:

· 133 UDOT snowplows and fleet vehicles,

· 215 Utah Transit Authority buses, and

· 73 Orem City emergency vehicles, snowplows, and fleet vehicles.

Field components that are currently being added to the system, with an expected completion date of late-2025, include:

· C-V2X RSUs on 300 UDOT signalized intersections.

· C-V2X RSUs at 37 locations along interstate or rural, non-signalized roadways.

· C-V2X OBUs on 178 UDOT, Connect Transit, and Logan City fleet vehicles.

· 17 UDOT snowplows and fleet vehicles,

· 39 Connect Transit buses,

· 106 Logan City emergency vehicles, snowplows, and fleet vehicles, and

· 16 Wasatch Fire Department emergency response vehicles.

The RSUs listed above include approximately 304 Kapsch RIS-9360 RSUs and 556 Commsignia ITS-RS4-M RSUs. The OBUs listed above include approximately 348 Ficosa OBUs and 251 Commsignia OBUs.

By early 2026, an additional 600 to 700 RSUs and 215 OBUs will be installed in the system as part of a large federal grant program, Accelerating V2X Deployment: Connecting the West. Most of these will be Commsignia devices.

Typical roadside installations include an RSU and a power-over-ethernet fiber switch (Cisco IK-2000-16PTC-G-E and IE-2000-8TC-G-B V1 and Fortinet FSR-112D-POE). Nearly all RSU installations are connected to the UDOT fiber network. RSU installations at signalized intersections also include a Signal Command Module (Helix), a single-board computer with application and processing software, and a connection to the signal controller (Econolite Cobalt SC3 and Intelight X3).

In a few cases, roadside installation also includes LiDAR technology from Ouster and Luminar / Seoul Robotics to detect presence of vulnerable road users. The LiDAR data is used by the RSU to create an SDSM message.

In-vehicle installations include an OBU, and in many cases, an On-board Processor, a single-board computer (Helix) with application and processing software and a connection to various on-board systems, including the vehicle CAN bus.

In most cases, V2X hardware has been tested, installed, integrated, and maintained by The Narwhal Group, a Salt Lake City-based technology services company, under contract to either UDOT or Panasonic. Narwhal has also provided the Helix Signal Command Modules and On-Board Processors.

Applications and Messages UDOT’s V2X system supports a variety of applications, including:

· Transit Signal Priority for buses that are behind schedule

· Signal Preemption for snowplows that are actively plowing snow

· Signal Preemption for emergency vehicles responding to emergency events

· Driver warnings for sharp curves, slick roads, high wind, disabled vehicles, and variable speed limits

· Driver warnings (in development) for work zones, lanes and roads closed, crashes, and other events To support these applications, the V2X system sends and receives the following standard messages, as defined by SAE J2735 and related standards:

· Signal Phase and Timing (SPaT). This data is generated by the signal controller and is assembled into the proper message format in the SCM.

· MAP. These are created using the USDOT MAP tool, and other tools, and stored in the SCM for forwarding.

· Basic Safety Message (BSM). Generated on board the vehicles, this message includes basic information created by the OBU GPS system and, in some cases, additional data gleaned from the vehicle’s CAN bus.

· Signal Request Message (SRM). Generated by the OBU and the SCM on the vehicle to request signal priority or preemption for vehicles that meet certain criteria (lateness for transit, emergency vehicle lights operating for emergency vehicles, plowing snow for snowplows); received by the RSU and processed by the SCM to send the appropriate request to the signal controller.

· Signal Status Message (SSM). Generated by the SCM to confirm the receipt of the SRM.

· Traveler Information Message (TIM). Generated by the current V2X Management System and sent to the OBU to warn drivers of various road conditions and events. The Connecting the West program has established uniform protocols for the interoperable use of TIM messages, as defined in these in-progress documents (which are attached):

· “Connected Vehicle Traveler Information Message Guidelines.pdf”

· “CTW-TIMs-ITIS-v20250507.xls”

· Radio Technical Commission for Maritime Services message (RTCM). Created by the SCM using GPS correction data obtained from a state network of servers and sent to the vehicle OBU. A few SCMs have an added chip which serves as an RTCM base station.

· Radio Technical Commission for Maritime Services (RTCM) message, a GPS correction message broadcast at a limited number of intersections.

· Sensor Data Sharing Message (SDSM). This message is created in the RSU based on the LiDAR data to report the location of vulnerable road users at the intersection.

UDOT currently uses the J2735-2016 standard and is migrating toward J2735-2024. The SDSM message is generated according to the 2024 standard.

All messages sent by UDOT’s V2X system have a security certificate attached as part of the Security Certificate Management System (SCMS). These certificates acknowledge that the message is authentic and hasn’t been tampered with during transmission. All current certificates are provided by Integrity Security Services (ISS) through a contract with Panasonic of North America. UDOT does not currently purchase certificates directly from ISS. UDOT has issued an RFP which will result in a direct contract for the purchase of security certificates; this RFP process is underway and has not been completed. The V2X Maintenance and Management System RFP does not include providing SCMS services or certificates.

Data and Communications The system operates on UDOT’s private fiber optic network which is accessible through UDOT’s VPN. RSUs request additional security certificates through the firewall permission which are configured by UDOT’s network administrators.

Data generated in the V2X System is transmitted from the roadside across UDOT fiber to the V2X Maintenance and Management System for storage and processing. Messages being forwarded include SPaT, MAP, BSM, SRM, SSM, and TIM.

· The V2X system interfaces with several other systems to obtain and share information, including: UDOT Advanced Traffic Management System (ATMS) system, known as “ARCH”, provided by SWRI. The data transfer occurs through a related system, a “BDX” data warehouse provided by Mindhop. For details on the API structure, please see the attached "ADX_API_Document_v1.10.pdf" and "ARCH to BDX Event Types Mapping.pdf". Note that the terms “ADX” and “BDX” are interchangeable.

· UDOT Road Weather Information is also available from UDOT’s BDX data warehouse; see the above documents for API structures.

· The Situational Data Exchange (SDX), a system developed for the Wyoming DOT by Trihydro. For details, please see the attached "SDX Integration Instructions Producer.pdf" file and this link to the SDX API Specification: https://sdx-service.trihydro.com/index.html.

Current V2X Maintenance and Management System Supporting UDOT’s V2X System is a robust, cloud-based Maintenance and Management System, known as Cirrus by Panasonic, developed by Panasonic of North America. Over the past five years, UDOT has contributed significantly to the development of Cirrus and its integration into the UDOT V2X System. Retention or replacement of this system and its functions is the primary goal of this RFP.

The current V2X Maintenance and Management system has five primary, distinct, but interrelated, functions:

· Data storage, processing, manipulation, analysis and sharing

· Ingest and store SPaT, MAP, BSM, SRM, and SSM messages.

· Report number of messages ingested each day by message type at each deployment site

· Deduplicate repetitive BSM, MAP, and SRM messages

· Display specific BSM data elements received each day

· Allow data to be filtered and sorted

· Run queries on raw data

· Download blocks of data for independent analysis

· Available for a variety of outside users with permission

· Manage the V2X roadside and vehicle hardware assets

· View the hardware assets in list format, including RSUs, signal controllers, switches, and SCMs

· Display hardware assets on a map of deployment locations

· Add new hardware assets into the system

· Monitor the health and performance of the V2X roadside hardware

· Query the roadside hardware to determine status

· Allow remote reboot of hardware through the Power-over-Ethernet fiber switch

· View the deployed hardware assets in a map and in list format, with intersection number, street names, longitude and latitude, and device types per location

· Review alerts produced at each deployment location, including total number of alerts, devices producing alerts, and alert types

· Monitor the messages being sent and evaluation of behavior that is outside the expected behavior

· View traffic events

· Review events retrieved from BSM data: hard braking, hazard lights, and temperature

· View information retrieved from UDOT Road Weather Information Stations: temperature, precipitation, icy road, high wind

· View data in lists or by location on a map

· View MAP messages at individual deployment locations overlaid on aerial imagery of intersection

· View V2X locations and play animation of vehicle movements and signal states, including lane connections, for any given time and date, over a brief time interval

· Evaluate irregular vehicle movements at intersections to identify possible errors in SPaT and MAP messages (using the Connected Intersection Message Monitoring System (CIMMS) developed by the Connected Vehicle Pooled Fund Study, found here: CVPFS | University of Virginia School of Engineering and Applied Science https://engineering.virginia.edu/labs-groups/cvpfs ). Irregular vehicle movements include vehicles traveling in wrong lanes, non-allowed vehicle turning movements

· Create Traveler Information Messages (TIMs)

· Curve Speed Warning, Spot Weather Impact Warning, Variable Speed Limit, Disabled Vehicle Warning, Emergency Vehicle Presence Warning The V2X Maintenance and Management system currently stores approximately 42 terabytes of data and ingests approximately 350 million messages each weekday, before deduplication. Of these 350 million messages, approximately 64% are SPaT, 29% are BSM, 6% are MAP, and the remainder are SRM, SSM, and TIM. As UDOT’s V2X system expands and, potentially, production vehicles are sold with OBUs, the number of messages will increase substantially.

System Requirements As noted above, the primary goal of this RFP is the retention or replacement of UDOT’s V2X Maintenance and Management system and its functions. In conjunction with that goal, UDOT desires a system that will manage the flow of data, minimize the cost of processing and storing the data, and expand the capabilities of the system to provide additional features and applications. The successful vendor will propose a system that manages the data in a cost-effective way, within UDOT’s budget. Two examples of data management could be deduplication before the data reaches the cloud or storing smaller amounts of live data. UDOT is seeking creative, practical solutions to the data management challenge. The vendor will also be expected to provide on-going support of their system.

UDOT desires a system to be operational soon after the expiration of the current Panasonic contract. As noted in the instructions for the Vendor Response Sheet, UDOT expects features to be available within 90 days of the Notice to Proceed (NTP). If a vendor needs additional development effort to meet specific requirements, they must indicate the time needed. Feature delivery time will impact scoring.

The specific requirements of the V2X Maintenance and Management System with which the vendor must comply are itemized in the “Vendor Response Sheet”. Responses provided in that document will be the basis for technical scoring.

The vendor may offer additional scope and features beyond the requirements itemized in the “Vendor Response Sheet”. These additional features can be provided in a section of the “Vendor Response Sheet” labelled “Additional Scope and Features”.

The vendor should also offer general information about the proposed system in the “General System Information” section of the “Vendor Response Sheet”.

Support of UDOT Contracts and V2X Program The selected vendor may be requested to create additional features in the system and/or participate in UDOT’s projects or provide general support of UDOT’s V2X program. In addition to building existing features, tasks could include project management support, V2X system design, system consultation, and participation in meetings, workshops, training, or presentations. Information about the vendor’s staff and qualifications shall be provided in the “Vendor Response Sheet” section labelled “System Hosting, Installation, and Support”. Staff billing rates shall be included in the separate Cost Proposal.

Any requested efforts for additional features or support will be negotiated subsequent to the execution of the primary contract and may be either hourly or lump sum, based on these rates.

Scope of Work Page 2 of 2