MENU ☰

SPAT Challenge Resources

SPAT Challenge

SPAT CHALLENGE RESOURCES 

Many resources are available to support agencies deploying the broadcast of SPaT messages, and others will be added as they become available.  The resources are organized according to a series of high-level steps that describe anticipated agency actions and outcomes, and mimic the systems engineering process, which agencies are encouraged to follow to ensure successful deployment of the SPaT Challenge.

The first seven steps will assist agencies with an entry-level approach to accomplishing the SPaT Challenge that includes:

  • Step 1: Determining the feasibility of SPaT deployment and selecting location(s);
  • Step 2: Defining the planned operations for SPaT at the selected location(s);
  • Step 3: Defining functional requirements for infrastructure deployments;
  • Step 4: Developing the design for the SPaT deployment;
  • Step 5: Procuring and/or developing the hardware and software installing the Roadside Units (RSUs) and obtaining needed DSRC licenses;
  • Step 6: Deployment and testing of the deployed systems; and
  • Step 7: Operating the deployments

The final step (Step 8) includes activities for agencies that have completed the initial seven steps of the SPaT Challenge (successfully reaching deployment of basic functions) and are prepared for a second phase in the process that will achieve a fully-verified SPaT broadcast to support near-term deployment of V2I applications (e.g. to support vehicle based V2I applications). 

In addition to the resources described below, this website includes a map of active and completed deployments with contact information for representatives who are willing to share information about their deployment experience.

 

Step 1: Determine Feasibility and Location(s) for SPaT Broadcasts

During Step 1, agencies are encouraged to conduct internal meetings with stakeholders to determine if DSRC broadcasts of SPaT are appropriate at this time and where they are most appropriate.  Components of these discussions should include high-level cost estimates, an understanding of the how the communications standards are likely to evolve over the duration of the SPaT deployment, and lessons learned from agencies that have implemented SPaT broadcasts.

 

Target Outcome of this Step:

  • Identification of appropriate intersection(s) and corridor(s) for the deployment of SPaT broadcasts, based on need and available equipment.

Resources Available to Support this Step:

  • SPaT Challenge Frequently Asked Questions (SPaT Challenge Resource)
  • Guidelines for Selecting Corridors (SPaT Challenge Resource)
  • Standards Versioning Management to Support SPaT Deployments (SPaT Challenge Resource) (Coming Soon)
  • Estimated Costs of Deployment & Operations (SPaT Challenge Resource) (Coming Soon)
  • V2I Deployment Guidance, Chapter 2 (USDOT-FHWA) (Coming Soon)
  • Desk reference and tools for estimating the local, regional, and statewide economic development benefits of connected V2I deployments (USDOT-FHWA) (Coming Soon)

 

Step 2: Define Planned Operations of SPaT Broadcasts

During Step 2, agencies are encouraged to conduct internal meetings with stakeholders to discuss the applications that will eventually be implemented based on the SPaT broadcasts.  Specifically, discussions should focus on what needs will be addressed by the deployment, who the stakeholders will be (e.g. if transit priority is deployed the vehicle equipment will be installed on transit vehicles), who will operate and maintain the infrastructure and vehicle components.  The discussions and decisions will include the topics that are typically included in a Concept of Operations document. 

 

Target Outcome of this Step:

  • Definition of the planned applications to be deployed to utilize the SPaT broadcasts
  • Identification of stakeholders, and associated responsibilities
  • Development of a Concept of Operations document (or surrogate documentation).

Resources Available to Support this Step:

  • Implementation Guidance (SPaT Challenge Resource)
  • V2I Deployment Guidance, Sections 3.2, 3.5 (USDOT-FHWA) (Coming Soon)
  • Sample Documentation – Concept of Operations (SPaT Challenge Resource) (Coming Soon)
  • Connected Vehicle V2I Systems Engineering Guidance (USDOT-FHWA) (Coming Soon)

 

Step 3: Specify Requirements

During Step 3, agencies are encouraged to define requirements for the SPaT broadcast deployment, including requirements for the Roadside Unit (RSU), requirements for the SPaT message generation and broadcast, and requirements for the MAP message generation and broadcast.  The SPaT Challenge Resource Team has been working with automobile manufacturers to define requirements that will enable SPaT broadcasts to interface with the eventual on-board applications that are expected to be deployed in passenger vehicles.  While these requirements remain under development, they represent the current best definition of requirements that SPaT locations should develop towards.

 

Target Outcome of this Step:

  • Developed system requirements describing overall infrastructure requirements, SPaT Message requirements, and MAP message requirements.

Resources Available to Support this Step:

  • SPaT Challenge Model Functional Requirements (SPaT Challenge Resource) (Coming Soon)
  • V2I Deployment Guidance, Sections 3.6 and 3.8 (USDOT-FHWA) (Coming Soon)
  • ITS Standards Training, Module 43. I261:V2I ITS Standards for Project Managers (USDOT-FHWA)
  • Connected Vehicle Standards Fact Sheet (USDOT-FHWA)
  • Sample Documentation – Requirements (SPaT Challenge Resource) (Coming Soon)
  • Connected Vehicle V2I Systems Engineering Guidance (USDOT-FHWA) (Coming Soon)

 

Step 4: Develop Design

During Step 4, agencies are encouraged to develop the needed designs to support the SPaT broadcast deployment.  As a minimum, agencies should plan on performing the following designs:

  • Connected Vehicle Roadside Process Software Design – describing the detailed approach for how the SPaT messages will be extracted from the signal controller in real-time, translate the messages into the SAE J2735 standard and communicate the message to the DSRC Radio.
  • Intersection Layout Design – describing the design aspects needed to assess and prepare for deployment at the intersection, including a site survey, site plans (e.g. illustrate where the RSU is mounted, where cables are run, etc.)
  • Backhaul Design – describing the plan for data communications between the signal controller and a central management center.
  • Security Design – describing the plans for ensuring security as the DSRC Radios are deployed (note security design may be deferred until Step 8).

 

Target Outcome of this Step:

  • Technology and intersection design documents

Resources Available to Support this Step:

  • V2I Deployment Guidance, Sections 3.9-3.12, 3.18 (USDOT-FHWA) (Coming Soon)
  • DSRC Roadside Unit (RSU) Specifications Document v4.1 (USDOT-FHWA)
  • Sample Documentation – Design (SPaT Challenge Resource) (Coming Soon)
  • Connected Vehicle V2I Systems Engineering Guidance (USDOT-FHWA) (Coming Soon)
  • V2I Message Lexicon (USDOT-FHWA) (Coming Soon)

 

Step 5: Procure and Install Hardware/Software

During Step 5, agencies will procure and/or develop and install the needed hardware and software.  This will include such things as:

  • Procuring the RSUs;
  • Procuring any needed software and hardware to support the interface between the signal controller and the RSU;
  • Developing the MAP files;
  • Acquiring the DSRC license(s); and
  • Registering the deployed DSRC radios to the license(s).

 

Target Outcomes of this Step:

  • Vendor qualification requirements, bid solicitation information, and specifications
  • Procurement, download, and installation of equipment, hardware, and software
  • The necessary DSRC license(s) are acquired and radios are registered to the license(s).

 

Resources Available to Support this Step:

 

Step 6: Deployment and Testing of Systems

During Step 6, agencies will deploy the hardware and software procured or developed.  This is expected to include:

  • Signal controller updates or replacements (if needed);
  • Deployment of the RSU, including installation of the DSRC radio, cabling, and any interfaces to the signal controller cabinet; and
  • Testing and validation of the systems deployed.

 

Target Outcomes of this Step:

  • Deployed Systems
  • Completed Test Plan

Resources Available to Support this Step:

  • Connected Vehicle V2I Systems Engineering Guidance (USDOT-FHWA) (Coming Soon)

 

Step 7: Operate and Maintain

During Step 7, agencies will operate the DSRC broadcast of SPaT messages on a continuous basis.  Ideally, efforts in Step 2 would have defined the operations and maintenance responsibilities.

 

Target Outcomes of this Step:

  • Operational system

Resources Available to Support this Step:

  • V2I Deployment Guidance, Section 3.15 (USDOT-FHWA) (Coming Soon)

 

Step 8: Enhance to Fully-Verified Broadcast

Step 8 includes activities that agencies would take to advance their SPaT broadcast deployments to a status where they are fully verified to be compatible with future automobile manufacturer-developed on-board applications.  While some aspects of Step 8 could be completed initially, there are some aspects (e.g. the Security Credential Management System connection) that is not possible at this time.  The primary activities anticipated during Step 8 include the following:

 

  • Deployment of Connection and Interaction with the Security Credential Management System (SCMS) – this will secure and protect the SPaT broadcast from hacking or rebroadcast of the message;
  • Deploy location position correction (if needed) to broadcast data that enables on-board applications in the vehicles to correct their position – this will help ensure that on-board applications can properly identify the approach phase they are following towards the intersection and distance to the stop line; and
  • Perform a validation of the broadcasts following validation procedures currently being defined.

 

Target Outcomes of this Step:

  • Connection and interaction with the Security Credential Management System (SCMS) to secure and protect the SPaT broadcast from hacking or rebroadcast of the message;
  • Validation of the DSRC broadcast with an established process to ensure that V2I-equipped vehicles (as certified by USDOT) can receive and process the SPaT, MAP, and RTCM messages for connected vehicle applications; and
  • RTCM (GPS correction) message broadcast to increase GPS positioning accuracy of vehicles approaching the intersection

Resources Available to Support this Step:

  • Security Credential Management Systems and SPaT (SPaT Challenge Resources) (Coming Soon); and
  • Connected Vehicle V2I Systems Engineering Guidance (USDOT-FHWA) (Coming Soon)

 

Future Steps Beyond SPaT Broadcast Deployments

 

Once SPaT Broadcasts are deployed, agencies are encouraged to deploy V2I applications and expand RSU deployments as planned in Step 2.

 

Resources Available to Support Future Steps

 

REGISTER AND BE UP-TO-DATE!

Subscribe to our website & newsletter to get your transportation operations updates!

Register Today!