Understand the Impacts on Public Sector Infrastructure due to Connected Vehicle Deployments
A survey of lessons learned through deployment of V2I test beds
Made Public Date


United States

Lessons Learned: Deployment of Public Sector Infrastructure for VII


In August of 2010 the Michigan Department of Transportation (MDOT) developed a report documenting the lessons learned from the deployment of public sector deployments of vehicle to infrastructure (V2I) test beds throughout the country. The lessons developed provide non-technical and technical insight for deployment of V2I systems.

Lessons Learned

This document captures both detailed and general lessons learned from early deployments of Vehicle to Infrastructure (V2I) roadside infrastructure, but it does not cover on-board vehicle installations nor does it venture into the V2I applications realm. Individuals across the spectrum of V2I deployments were interviewed as part of this evaluation, including those involved with the United States Department of Transportation (U.S. DOT) Proof of Concept Project, various state demonstration projects, and the New York World Congress deployment. Specific questions within the interviews were targeted toward the interviewee's individual experiences, although the comments in this report are an assemblage and not attributed to any one individual. The following is an overview of the non-technical and technical lessons learned during these deployment projects:

Summary of Non-Technical Lessons

  • Use the Systems Engineering process to ensure the proper project controls
  • Determine requirements for the entire system lifecycle prior to deployment
  • Ensure that the project's scope is clear and consistent over the life of the project
  • Use the project scope to identify appropriate resources needed and roles/responsibilities for the tasks
  • Develop appropriate project management processes and controls to mitigate funding issues
  • Understand the differences between DSRC deployment inspection and traditional highway design and construction inspection
  • Choose a project team carefully so the appropriate project support and expertise will be available to achieve project success
  • Include a good communication plan as part of the project plans to keep all stakeholders informed of the project status
  • Clearly identify key program champions to support the project efforts

Summary of Technical Lessons-In the Field

  • Develop physical interface requirements to reduce installation complexity of the RSE
  • Ensure ALL coupler/cable connections are weatherproofed and outdoor-rated
  • Place serviceable parts of the RSE at a height that maintenance staff can reach without the need of a bucket truck
  • Discuss design with local agency and installers to ensure it is appropriate for mounting and serviceability of devices unique to that location
  • Install extra Ethernet connections to allow for maintenance and serviceability of field equipment
  • Evaluate conduit capacity prior to installation
  • Investigate existing conduit contents well in advance of any additions to the conduit
  • Inventory existing controller types before implementation
  • Provide multiple recovery techniques for RSE designs to minimize down time
  • Review overall design of RSE field deployment to reduce points of maintenance and failure

Summary of Technical Lessons-In the Vehicle

  • OBE manufacturers and RSE manufacturers should perform factory testing prior to deployment of devices
  • Algorithms should be developed within the OBE to choose the strongest RSEs for data transmission
  • Vehicle equipment messages should be standardized and additional development should be performed

Summary of Technical Lessons-Backhaul

  • Use a licensed frequency band of WiMax to increase reliability and stability of the network
  • Consider security and accessibility implications when choosing a backhaul method
  • Use multiple backhaul methods to provide the best coverage and failure protection, although this also increases maintenance and support responsibility

Summary of Technical Lessons-ENOC/SDN

  • Identify equipment by a static value, such as an intersection ID or some other pre-defined value
  • Ensure all critical connections are monitored and tracked
  • Create a standard for connected vehicle components to interconnect to the back office
  • Develop a process flow to clearly identify roles and responsibilities

The detailed lessons learned from these interviews provide a wide range of technical and non-technical suggestions to be considered by those interested in deploying V2I systems. From these interviews, it is clear that adherence to a rigorous program management effort, relying on the systems engineering process as a guide, will help reduce or eliminate many of the challenges and hurdles encountered during some of the early V2I deployments. The evolution of V2I will undoubtedly uncover new challenges, but already progress is being made and there is a sincere desire to not repeat mistakes. This document provides non-technical and technical lessons learned that can aid in the success of future projects.

Lessons Learned: Deployment of Public Sector Infrastructure for VII

Lessons Learned: Deployment of Public Sector Infrastructure for VII
Publication Sort Date
Parsons Brinckerhoff, Inc.
Michigan DOT

(Our website has many links to other organizations. While we offer these electronic linkages for your convenience in accessing transportation-related information, please be aware that when you exit our website, the privacy and accessibility policies stated on our website may not be the same as that on other websites.)

Focus Areas Taxonomy: