National Connected Vehicle Field Infrastructure Footprint Analysis

Wright, James; Garrett, J. Kyle; Hill, Christopher J.; Krueger, Gregory D.; Evans, Julie H.; Andrews, Scott; Wilson, Christopher K.; Rajbhandari, Rajat; Burkhard, Brian · 2014 · ROSA P / United States. Department of Transportation. Intelligent Transportation Systems Joint Program Office

archive: archived pipeline: cataloged verified

Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)

Summary

This report, produced by the American Association of State Highway and Transportation Officials (AASHTO) with support from the U.S. Department of Transportation and Transport Canada, addresses the strategic planning required for deploying connected vehicle (CV) field infrastructure. The analysis was motivated by the National Highway Traffic Safety Administration’s (NHTSA) move toward rulemaking for vehicle-to-vehicle (V2V) communications in light vehicles. While this federal action does not mandate infrastructure deployment by state and local agencies, it creates a likely nationwide fleet of equipped vehicles, necessitating that agencies understand the investments and preparations required to leverage vehicle-to-infrastructure (V2I) applications for safety, mobility, and environmental benefits. The study utilizes a collaborative approach involving the AASHTO Connected Vehicle Deployment Coalition and various state and local transportation agencies. The methodology involves defining a vision for a mature CV environment by 2040, analyzing potential applications grouped by safety, mobility, and environmental objectives, and developing specific deployment concepts for diverse contexts such as urban intersections, rural roadways, freight corridors, and border crossings. The analysis establishes assumptions regarding system elements, including roadside communications equipment, traffic signal interfaces, security credential management, and mapping services. It further estimates costs for Dedicated Short Range Communications (DSRC) site deployment, backhaul upgrades, and signal controller replacements, while outlining deployment milestones and timelines. Key findings outline a preliminary national infrastructure footprint aiming for up to 80% (approximately 250,000) of traffic signal locations and 25,000 other roadside locations to be V2I-enabled by 2040. The report identifies that accurate, real-time traveler information should cover 90% or more of roadways. Cost estimations provide specific figures for DSRC site equipment, installation, planning, and operations and maintenance, alongside costs for backhaul and signal controller upgrades. The analysis highlights that viable deployments require supporting multiple applications simultaneously to maximize the utility of physical infrastructure and data components. It also details the operational and organizational impacts, including the need for new funding strategies and the integration of third-party data services. The significance of this report lies in its provision of a structured framework for agency decision-makers to prepare for the emerging CV environment. It concludes that achieving the envisioned footprint requires cooperation among stakeholders, including infrastructure owners, vehicle manufacturers, and service providers. The authors recommend the development of a National Deployment Plan to guide this transition through proactive collaboration. By providing detailed cost estimates, deployment scenarios, and a long-term vision, the report enables state and local agencies to align their infrastructure investments with federal safety initiatives and their own operational objectives, ensuring they can effectively support a connected transportation system.

Key finding

The analysis projects that up to 250,000 traffic signal locations and 25,000 other roadside locations will need to be V2I-enabled to support a mature connected vehicle environment by 2040.

Methodology

modeling

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.

• v2x connected vehicle