GovSprint
← Back to today

Cooperative Driving Automation (CDA) Small-Scale Industry Prototype

Department of Transportation · Federal Highway Administration · 693JJ3 ACQUISITION AND GRANTS MGT
Account requiredWhy it scored this way

Every reason behind the verdict rather than the headline one — which of your certifications match, how much runway is left, whether the work is your size, and what we would need to know to sharpen it.

Draft the paperwork

Written against this notice and what you have told us about your company. Anything we do not know is marked [NEEDS INPUT] in the draft rather than guessed at — read it before you send it.

Start a free trial to draft these. Nothing is sent to an agency on your behalf, ever — you get a document to review, edit and submit yourself.

Compliance matrix

Every stated and implied requirement, its source section, whether it is mandatory, and where your response will address it.

Proposal outline

A submission skeleton where every required element is a heading with its source requirement quoted beneath it. You write the substance; nothing gets forgotten.

Questions to submit

Genuine ambiguities and requirements that disadvantage a smaller bidder, drafted as questions you can submit before the Q&A deadline.

Past performance write-ups

Which of your prior awards best match this requirement, and draft write-ups in the format the agency asked for.

Solicitation details

Solicitation number
693JJ3-26-BAA-0005
Notice type
Solicitation
NAICS
541715
Product service code
AS13
Set-aside
No Set aside used
Posted
2026-07-30
Response deadline
Sep 13, 2026, 7:00 PM UTC
Place of performance
Washington, DC
Contracting contact
jessica.prutz@dot.gov

Market intelligence

Account requiredWho wins this work, and what it pays

Comparable awards under NAICS 541715 at this agency — the incumbent, what they were paid, when their period of performance ends, and the real pricing distribution rather than the headline number. From public federal award records.

Statement of work, as posted

BACKGROUND: USDOT envisions a future transportation ecosystem where CDA complements both human-driven and automated vehicles to improve roadway safety, mobility, and operational efficiency. While standalone vehicle automation has advanced, it continues to struggle with complex edge cases such as occlusion, complex merging, or identifying pedestrians hidden behind buildings at corners, and vehicle sensors alone cannot adequately resolve these issues. Prior USDOT-supported research projects have successfully demonstrated the technical proof-of-concept at technology readiness levels (TRL) of 3-5 for CDA applications in laboratory and closed environments. However, most new vehicles are not equipped with CDA capabilities and Original Equipment Manufacturers (OEMs) remain reluctant to integrate these technologies into production lines due to a lack of consumer awareness and unclear regulatory, policy, and institutional frameworks. This acquisition seeks to build on foundational CDA research by bridging the gap between research concepts and commercial viability. There is a critical need to develop and test pre-production, industry-led prototypes at a TRL of 6-7, to validate that the data shared between vehicles and roadside infrastructure is accurate, secure, and reliable enough to support functional safety. By demonstrating CDA technologies in operational conditions, researchers will gain a better understanding of cooperative systems and if they are more valuable in terms of improving roadway safety, than standalone automation or vehicle-to-everything (V2X) technologies alone. PURPOSE: The purpose of this requirement is to demonstrate industry-led CDA prototypes in controlled and real-world conditions in order to generate data-driven insights that will support the development of a national strategy to deploy CDA across rural, suburban, and urban roadway systems. This effort prioritizes industry-ready CDA technology for use cases with clear safety and/or mobility benefit potential, specifically focusing on: (1) Work Zone Management, (2) Traffic Incident Management, (3) Cooperative Perception, and/or (4) Emergency/Transit Vehicle Awareness. Contractors will first validate the prototype's interoperability, functional safety, and cybersecurity in a relevant, controlled testbed environment. Following successful controlled testing, the effort will progress into a small scale real-world demonstration on public roads with mixed traffic to validate operational readiness and generate data-driven insights.

Contact

Point of contact
Jessica Prutz
Role
not stated on this notice — SAM publishes a role for only about 5% of them, so this may be a contract specialist rather than the contracting officer
Email
jessica.prutz@dot.gov
Secondary
james.mikell@dot.gov
Submit questions

Ambiguities and requirements worth clarifying, written as questions you can send before the deadline.

Open email
Request documents

Ask for attachments, drawings or specifications referenced in the notice but not posted.

Open email
Add me to interested vendors

Ask to be listed as an interested vendor so other bidders can find you for teaming.

Open email

Opens in your own mail client, addressed and with a subject line — you write the message. GovSprint never sends anything on your behalf.

Emails open in your mail client and are sent from your address, so the reply comes back to you and the exchange stays yours. Confirm the correct channel and any question deadline on the notice before sending — many solicitations require questions in a specific way.