CVAZ Vulnerable Road User Detection Systems

Solicitation No.

9402185313

Type / RFx

IFB

Status

Active

Level

county

Published Date

July 23, 2026

Due Date

August 11, 2026

NAICS Code

334511AI guide

Jurisdiction

Maricopa County Procurement Services

State

Arizona

Agency

Maricopa County Procurement Services

INTENT: Maricopa County Department of Transportation (MCDOT) is seeking qualified contractors to provide and configure Vulnerable Road User (VRU) Detection Systems that generate Society of... **Solicitation Type**: IFB - Invitation for Bid (Formal) **Source ID**: PU.AG.USA.2550080.C22854076 **Piggyback Contract**: No **Questions are submitted online**: Yes **Bid Submission Type**: Electronic Bid Submission **Additional Bidding Instructions**: Arizona Unified Transportation Registration and Certification System (AZ UTRACS) Registration – Prime contractors and all subcontractors including Disadvantaged Business Enterprises (DBEs) must be registered in the AZ UTRACS web portal https://utracs.azdot.gov/. ... **Solicitation Number**: 260098-C **Reference Number**: 0000431421 **Pricing**: In attached document **Bid Documents List**: | Item Name | Description | Mandatory | Limited to 1 file | |---|---|---|---| | Attachment A | Vendor Information | Yes | No | | Attachment B | Agreement Page | Yes | No | | Attachment C | References | Yes | No | | Attachment D | Pricing Sheet | Yes | No | | Attachment E | CVAZ V2X In Kind Match Template | Yes | No | | Exhibit 15 | Equal Employment Opportunity Clause and The Filing of Required Reports | Yes | No | | Exhibit 16 | Affidavit of Compliance | Yes | No | | Exhibit 17 | Non-Collusion Affidavit | Yes | No | **Pre-Bidding Events**: Event: Prebid Conference | Date: 08/03/2026 01:00 PM EDT | Location: Microsoft Teams **Questions and Answers**: | Question | Answer | |---|---| | Please clarify whether the scope of work includes field installation at the 75 intersections, or if installation will be performed by Maricopa County or another contractor. | Installation will be performed by Maricopa County or another contractor. | | Please confirm that the county will be providing the roadside processors. | The County is not intending to provide a processor for this application. If the respondents assumes the use of any County processing capability in traffic signal cabinet, the requirements for this processing capability should be clearly stated to determine feasibility. Alternative pricing and proposal should be provided in the event the County processor cannot be utilized. | | Does the detection system need to also detect vehicles? | No, the detection system does not need to detect vehicles. Additional capabilities may be considered as a value add. | | Which device is going to be responsible for generating the SAE J3224 SDSM. The VRU detection system or the RSP? Also, what is the method the RSP will ingest the VRU detector data? The 2.1.1.1 and VRU table for functional requirements (VRUD-FR-005-v2.2) contradict each other for who is responsible for the message generation. | Please see changes to section 2.1.1.1 and Table 1: VRU Detection System Requirements as shown in Addendum #2. | | Section 6.1.1 states the roadside processor generates the SAE J3224 SDSM from detection data, while Requirement VRUD-FR-005 states the VRU Detector generates the SDSM itself. Please clarify: does the VRU Detection System deliver raw detection data to the Roadside Processor (RSP) for SDSM generation, or does it deliver a complete, standards-compliant SDSM ready for broadcast? | Please see changes to section 2.1.1.1 and Table 1: VRU Detection System Requirements as shown in Addendum #2. | **Addendums**: | Addendum | Date | Note | |---|---|---| | Addendum No. 1 | 07/28/2026 01:27 PM EDT | | | Addendum No. 2 | 07/30/2026 05:44 PM EDT | |

1. July 23, 2026Published
2. August 11, 2026Responses Due