Checklist for a successful deployment of the V2I Hub platform that facilitates communication between connected vehicle hardware and traffic control systems.
V2I Hub Deployment Guide provides agencies a roadmap through the pre-deployment and post-deployment process to supplement existing agency procedures.
Made Public Date

V2I Hub Deployment Guide


The V2I Hub software (formerly known as IVP) is designed for use by jurisdictions deploying connected vehicle systems to help bridge the gap between infrastructure messages and vehicle messages and allow the two systems to effectively communicate. By initializing the system with standard data such as intersection geometry and the correlation between signal phases and lanes, this software will be able to form and transmit Signal Phase and Timing (SPaT) messages that are key to connected vehicle applications such as red light violation warning. Through the use of Traveler Information Messages (TIM), the system can also develop and send infrastructure information about advisory speeds, attributes of physical elements such as bridge heights, and other data that can be used by applications such as curve speed warning and over-height warnings.

Lessons Learned

As the USDOT encourages state and local entities to deploy Connected Vehicle (CV) technology under their jurisdiction, the V2I Hub Deployment Guide was created to provide an outline with step-by-step instructions for deploying the V2I Hub software and hardware. This deployment guide outlines a phased approach and provides insight into needs analysis, planning, design, procurement, field deployment, and post deployment intended for use by traffic engineers responsible for performing the deployment.

The following V2I Hub Deployment Checklist has been developed as a guide to help provide direction and to ensure the successful deployment of the V2I Hub.

Project Initiation

  • Define project objectives, scope, how results will be measured, and lifespan.
  • Determine Connected Vehicle Safety Applications, messages, functionality, V2I Hub plugins, and supporting software needed to accomplish project objectives.
  • Identify required hardware.
  • Develop initial budget.
  • Develop initial schedule.
  • Identify constraints, risks, and mitigations/alternatives.
  • Identify project work areas and team.
  • Project team kickoff Meeting.
  • Update with new information as appropriate.

Coordination with Supporting Agencies

  • Kickoff meeting
  • Identify and confirm stakeholders requiring approval or coordination (e.g., State/City/County, utility agencies, business or private properties impacted).
  • Identify approvals and permits needed.
  • Determine if design plans are required and submittal requirements for preliminary, advanced, final, and as-built plans.
  • Obtain jurisdiction approval process and review times for development of project schedule.
  • Obtain any existing roadway, intersection, and traffic signal design plans.
  • Obtain current traffic signal timing plans and Phase to Lane Mapping (PTLM) assignments.
  • Ascertain what equipment is in the field; including make, model, and firmware version.
  • Determine FCC permit licensee (typically the jurisdiction).
  • Discuss potential locations for mounting the Roadside Unit (RSU) and hardware for mounting.
  • Determine any loading or structural analyses required for mounting the RSU on existing structures, specifically traffic signal mast arms or span wires. RSUs typically weigh less 15 pounds, excluding mounting hardware. Confirm weight with RSU vendor.
  • Determine approval requirements for equipment, specifically V2I Hub and the RSU. Determine any specific requirements for grounding or a surge protective device on the Ethernet cable to the RSU for lightning protection.
  • Determine any requirements for traffic management or control plans during installation, and the process and approval requirements for any lane closures.
  • Determine field inspection and installation approval requirements.
  • Determine the requirements for the Ethernet cable connecting the RSU to utilize existing conduit and anticipated feasibility.
  • Work with IT networking personnel to determine the protocols for accessing V2I Hub and the RSU in the field, and to enable them to retrieve external information (e.g., position correction data, security certificates, local weather information, etc.).
  • Site visit to confirm equipment in the field, RSU mounting options and obstructions, and junction box locations and condition of conduit.
  • Update scope and work plan as appropriate.


  • Refine the Connected Vehicle Safety Applications, messages, functionality, V2I Hub plugins, and supporting software identified during project initiation.
  • Security is a fundamental part of CV technology and will need to be part of the design from the beginning, specifically to meet the requirements of the Security Credential Management System (SCMS).
  • Determine how software updates can be implemented remotely, with minimal downtime, and without impacting traffic signal operations.
  • Determine RSU reception range required for project connected vehicle (CV) applications.
  • Determine if more than one RSU is required to cover project area.
  • Determine RSU mounting location and hardware required.
  • Determine if existing equipment is compatible and meets requirements to support CV technology (e.g., traffic signal controller).
  • Identify if the necessary infrastructure is in place (e.g., traffic signal poles to mount the RSU, conduits for Ethernet cable, etc.) or if new infrastructure will need to be constructed.
  • Identify hardware and equipment list for procurement.
  • Develop design plan sheets as required by approving jurisdiction.
  • Develop performance requirements (e.g., uptime, RSU reception range, maximum packet loss, lag, design life, etc.).
  • Develop Test/Verification Plans to confirm and document system operations, CV Application functionality, and network connections.
  • Identify equipment needed for testing (e.g., in-vehicle device for transmission and receipt of CV messages).
  • Develop Operations and Maintenance Plan as needed (e.g., equipment status, uptime, maintenance plan, field inspection and testing intervals, equipment replacement plan, software update plan, etc.).

Approvals and Permits

  • Security Credential Management System (SCMS).
  • Obtain Federal Communications Commission (FCC) Spectrum Permit for use of the protected 5.9GHz spectrum used by DSRC radios.
  • Obtain necessary jurisdiction approvals and permits. Obtain equipment and hardware approval.

Equipment and Procurement

  • Hire traffic signal contractor to procure equipment (for contractor installations).
  • Industrial computer to run the V2I Hub software platform.
  • RSU Dedicated Short Range Communications (DSRC) radio with GPS attachment.
  • Power over Ethernet (PoE) adapter (may be provided with RSU).
  • RSU mounting hardware (for pole, span wire, or mast arm).
  • Ethernet surge protector for lightning protection (if required by jurisdiction).
  • In-cabinet mounting hardware or ground wires (if required by jurisdiction).
  • Up to 3 Cat5e or Cat6 Ethernet cables (patch cables for connecting equipment in cabinet, less than 5 feet in length).
  • Shielded, outdoor-rated, Cat5e or Cat6 Ethernet cable (for connecting the RSU and traffic signal controller, length varies by deployment).
  • Equipment for an Internet and Transportation Management Center (TMC) connection, if needed.
  • Associated or upgraded equipment, as needed (e.g., compatible traffic signal controller, Ethernet switch, etc.).
  • Any additional hardware or equipment identified in the design.
  • In-vehicle device for testing/verifying message transmission.

Pre-Deployment Development and Preparation

  • Custom V2I Hub plugins – Develop to support new project applications, functionality, and hardware connections & message translation (if needed).
  • Development of backend software at the TMC for the reception and transmission of messages and data with V2I Hub.
  • Develop intersection geometry input file for MAP Plugin. Refer to the ISD Message Creator tool documentation located in the U.S. DOT CV Tools Library ( for instructions for instructions on how to create a MAP file.
  • Develop PTLM XML input file for SPaT Plugin.
  • Assign IP addresses to RSU and V2I Hub in accordance with the IP address schema used by the devices in the traffic cabinet. The RSU must be assigned its IP address in an environment where its GPS antenna has an open view of the sky.
  • Document all device IP addresses and configuration settings.
  • Install the RSU software compliant with the RSU 4.1 specification on the RSU.
  • Obtain RSU security certificates and install on RSU per RSU manufacturer guidance
  • Install V2I Hub software on industrial computer by downloading it from the Open Source Application Development Portal. Refer to the V2I Hub Application Software Installation section of the V2I Hub Application Software Installation section of the V2I Hub Software Configuration Guide.
  • Configure V2I Hub, RSU, and plugins. Refer to the V2I Hub Application Software Installation section of the V2I Hub Application Software Installation section of the V2I Hub Software Configuration Guide.
  • Configure network connections and ports for remote access to V2I Hub and the RSU, and to enable these devices to access information external to the TMC (e.g., position correction data, security certificates, etc.).
  • Load the MAP file onto the V2I Hub. Refer to the MAP Plugin Configuration section of the V2I Hub Software Configuration Guide.
  • Verify plugin message activity if associated equipment is available (e.g., traffic signal controller).
  • Test software and field equipment functionality and message transmission to a representative in-vehicle device in the lab prior to field deployment, as feasible with available equipment. Note: If the application being deployed requires an OBU test the GPS signal and verify the quality of DSRC reception required.
  • Create a block or wiring diagram of all the connections made between components for use during the installation.

Field Verification Prior to Installation

  • Connect V2I Hub, RSU, traffic signal controller, and maintenance computer prior to mounting hardware to confirm operation.
  • Configure traffic signal controller.
  • Verify communications between traffic signal controller, V2I Hub, RSU, and TMC.
  • Verify plugin message activity.
  • Verify transmission of messages to a representative in-vehicle device.
  • Verify remote access to V2I Hub and the RSU.
  • Verify V2I Hub is able to retrieve external information as needed (e.g., position correction data, security certificates, local weather information, etc.)
  • Verify field conditions are consistent with design plans or proposed equipment locations.
  • Confirm line-of-sight without physical or vegetation obstructions between proposed RSU location(s) and all roadway approaches necessary for CV applications.

Field Installation

  • Schedule utility location if underground work is anticipated.
  • Schedule deployment and jurisdiction participation/oversight as needed.
  • Schedule/Coordinate traffic management, including lane closures and law enforcement support (if needed).
  • Field verification of equipment locations with jurisdiction may be needed if obstacles require shifting from their planned locations.
  • Install equipment and Ethernet cable connections.

System Test, Inspection, and Approval

  • Verify transmission of messages to a representative in-vehicle device (OBU).
  • Verify signal phase and timing on in-vehicle device matches what is displayed on the traffic signal heads. Note: When select traffic signal controllers are sent into flash mode, the SPaT data transmitted from the controller may not be representative of the flash mode it entered as it may still display the SPaT information from the traffic signal program prior to entering flash mode.
  • Verify remote access to V2I Hub and the RSU.
  • Passes Test/Verification Plan developed as part of the design documents.
  • Verify RSU transmission reception range meets project CV application requirements on all roadway approaches.
  • Jurisdiction inspection and approval, as required.
  • Develop and submit as-built plans, as required.

Operations and Maintenance

  • Implement Operations and Maintenance Plan.
  • Maintain records of equipment, status, costs, and lifecycle according to agency asset management practices.
  • Follow-up with stakeholders for discussing operational value and enhancements.

V2I Hub Deployment Guide

V2I Hub Deployment Guide
Publication Sort Date
Gregory Zink, Anthony Polinori
Federal Highway Administration

(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: