TWG 5: Deployment Standards

Chair: Ed Seymour, Texas A&M Transportation Institute, eseymour@tamu.edu

Co-Chair: Gary Duncan, Econolite, gduncan@econolite.com

There are several organizations currently developing standards for CV including the International Standards Organization Technical Committee 204 (ISO TC 204), SAE J2735 and IEEE. This TWG will identify and discuss applicable standards, the state of practice in standards development and deployment, and the expectations for future standards. This TWG will discuss issues related to the need for standards and the timeline for when the standards are needed, enabling the group to identify gaps among needs, the state of practice and plans for future standards.

 

SPAT Challenge Flyer

Standards Context Diagram

V2I DC Context Drawing

V2I DC Standards Attendance and Roster

Vehicle to Infrastructure Deployment Coalition (V2I DC) Technical Working Group 5 (TWG 5): Deployment Standards Work Plan 

July 2015 – June 2016

Meeting notes May 12, 2016

Draft – 8/10/2015

The Vehicle to Infrastructure Deployment Coalition Technical Working Group 5 (V2I DC TWG 5) is focused on V2I standards.  Membership in the TWG includes individuals with experience defining the need for creating, using, reviewing, and encouraging the use of standards for connected vehicles and Intelligent Transportation Systems (ITS). 

This document presents the work plan of activities to be completed by TWG 5 between July 1, 2015 and June 30, 2016.

2.Overall TWG Plan for the 12 Months

  • Meeting Frequency.  The TWG members agreed to meet by webinar once per month.  The meeting date will be the first Thursday of each month at 2:00 pm Eastern.  Meeting dates may be adjusted, as needed, to accommodate outside meetings or events.

  • V2I Issues to be Addressed.  The TWG members have agreed that Issue #8 (V2I Standards) is the most applicable issue to TWG 5 and will be the primary focus of the group.  In addition, members agreed that the group would provide input and support to other TWGs working on other issues, specifically in regards to standards related questions or support requests.  These issues, and a high level summary of actions are identified in Section 3.

  • Work Plan Activities.  TWG 5 members have defined five activities to advance the V2I issues over the coming 12 months.  These five activities are described in Section 4 of the Work Plan, together with tasks to be completed within each activity.

  • Work Plan Schedule.  Section 5 contains a high level summary of the TWG schedule of activities.  In summary, the assessment of V2I standards needs and gaps will continue for the duration of the TWG.  However, in order to develop action plans for addressing gaps, a sequential order of tasks has been defined.

    3.Planned Actions to Address V2I Deployment Coalition Issues

The following table represents the set of issues discussed by the V2I DC at the June 4-5 workshop.  For each issue, anticipated actions are identified as well as anticipated completion dates.  Where an issue is identified with “No Action Planned”, TWG 5 members have no current plans for action but are available to support questions or requests for assistance to the extent possible.   Five Activities are defined in Section 4 (and referenced in the table below).  Section 6 of this Work Plan includes the definitions of the five issues to be addressed by TWG 5.

 

V2I Deployment Issues

Anticipated TWG 5 Actions

Anticipated Completion Date

Issue 1: V2X Applications

  • Consider the most critical V2I applications identified by TWG 1 outreach and identify standards needs and gaps related to these applications.  See Activity 2, Task 2.3

April, 2016

Issue 2: Complementary Communications to DSRC

No action planned

 

Issue 3: V2I Data

  • Liaison and answer technical questions about V2I standards as needed to support Issue 3 activities. See Activity 5

June, 2016

Issue 4: Patents-Intellectual Property

No action planned

 

Issue 5: Security

  • Liaison and answer technical questions about V2I standards as needed to support Issue 5 activities. See Activity 5

June, 2016

Issue 6: V2I Outreach

  • Liaison to share information about standards needs and gaps in existing standards to be included in outreach recommendations by TWG 4. See Activity 5

June, 2016

Issue 7: Understanding the Benefits and Costs of V2I Deployment

No Action planned

 

Issue 8: V2I Standards

Oct, 2016

June, 2016

April, 2016

  • Determine candidate action plans to fill V2I standards needs and gaps.  See Activity 4

June, 2016

Issue 9: Understanding V2I Liability Assignment

No action planned

 

Issue 10: V2I Synergies with Other Emerging Technologies

No action planned

 

Issue 11: V2I Consumer Messaging

No action planned

 

Issue 12: V2I Multimodal Applications

No action planned

 

Issue 13: Infrastructure Processes as V2I Obstacles

No action planned

 

Issue 14: Federal V2I Policy Statement

No action planned

 

Issue 15: Maintaining V2I Infrastructure

No action planned

 

Table 1 – Summary of TWG 5 Approach to the V2I Issues

 

4.TWG 5 Work Plan – Year One

TWG 5 members identified the following plan of action to be the primary focus of the TWG for the coming 12 months:

4.1 Activity #1: Develop a Standards Context Framework Drawing

Issue(s) Addressed

Issue 8: Standards. V2I stakeholders need a V2I standards needs assessment and gap analysis to ensure that all needed standards are in place when needed to support V2I deployment.

What’s Needed and Why

A standards context framework drawing is needed to structure the needed and available standards between the vehicles, infrastructure, and roadside units. 

This is needed to facilitate discussions about current and needed standards, and to discuss gaps and needs for additional standards.   

12 Month Plan of Action

Task 1.1   Develop a Standards Context Framework Drawing

TWG 5 members will collaborate to prepare the context drawing(s).  The drawing(s) will be a framework diagram showing the relationship of V2I standards, both current and needed, and how they relate to the vehicles, roadside units, and infrastructure.  

Deliverable: Context Framework Drawing(s) as Visio and PDF

Key individuals: Seymour, Rausch, Misener

Target completion: 10/1/15

 

4.2 Activity #2: Identify V2I Standards Needs and Gaps

Issue(s) Addressed

Issue 8: Standards. V2I stakeholders need a V2I standards needs assessment and gap analysis to ensure that all needed standards are in place when needed to support V2I deployment.

Issue 1: V2X Applications. There is a need for prioritization of V2X Applications (including multi-modal applications) and common understanding of how OEM and infrastructure applications work together.

What’s Needed and Why

Successful V2I deployment and operations will rely on a number of standards.  The first step towards ensuring all the needed V2I standards are available to the marketplace is to identify the standards needs and gaps.    TWG 5 has identified the need to:

- review the findings of the USDOT gap analysis efforts (USDOT ITS-JPO is conducting two efforts to identify Connected Vehicle standards gaps);

- assess the V2I related standards developed by the Standards Developing Organizations (SDOs);

- gather input on standards needs and gaps from V2I DC members; and

- gather input from the selected V2I Pilot Deployment sites. 

This is needed such that later activities can develop action plans for additional standards development, as needed.

External Resources / access needed

 

The V2I standards needs and gap analysis will require:

  • Access to preliminary or final findings from USDOT standards gap analyses efforts, and ideally participation from project team members to discuss the findings.
  • Input from other V2I DC TWGs describing V2I standards needs.
  • Access to information about the V2I related activities of SDOs.

12 Month Plan of Action

 

Task 2.1   Assess Ongoing USDOT Gap Analysis Efforts

TWG members will review ongoing USDOT sponsored gap analysis efforts in order to offer feedback to the studies and to establish a baseline understanding of V2I standards needs and gaps already identified.  As part of the review process, two webinars will be performed (one for each effort) to present findings to TWG 5 members, and to allow other individuals involved in the USDOT efforts to present additional comments.

Deliverables: 2 Webinars, Technical Memo summarizing results of assessment

Key individuals: Binkley (Iteris effort), Chan (Cambridge effort)

Target completion: 12/1/15

Task 2.2 Assess Ongoing V2I Related SDOs activities.  

TWG members will review and assess current and pending V2I related standards of SDOs.  Efforts are expected to review NEMA, NTCIP 1202, CVRIA, and SAE efforts.  As part of this task, one webinar will be conducted to enable TWG members who have reviewed SDO efforts to present their findings to other TWG 5 members.  A summary of the webinar will be prepared as the deliverable to this task.

Deliverables: 1 Webinar; Summary document of findings

Key individuals: Duncan (NEMA), Thai (NTCIP 1202), Binkley (CVRIA), TBD (SAE)

Target completion: 4/1/16

 

Task 2.3   Assess Standards Needs Identified by TWGs. 

TWG members will be assigned as liaisons to other TWGs in order to derive standards needs based on the efforts and findings of the TWGs.  For example: TWG 1 will be identifying the most critical V2I Apps identified by V2I deployment initiatives.  TWG 5 members will consider these critical applications for standards needs and provide feedback to TWG 1.  Conference calls with TWG 1 will be performed as their findings are available.

In addition to outreach to other TWGs, this task will facilitate input from the entire TWG 5 membership during monthly webinars to solicit needs and gaps in V2I standards.

Deliverables: Technical memo describing standards needs derived by other TWG efforts

Key individuals: Miller, Yang (TWG 1), TBD, Nace (TWG 2), Misener, Gardner, Tourville (TWG 3), Rausch, Clelland (TWG 4)

Target completion: Ongoing throughout life of TWG

Task 2.4   Standards Outreach and Needs Gathering with CV Related Initiatives.  

Once the CV Pilot Deployment sites are selected and efforts have begun, TWG members will establish communications with each site and request/offer to provide a standards update to each site.  During the standards update, each CV Pilot site will also be asked about any standards needs they have identified during their planning process.

In addition, TWG 5 members will outreach to other organizations or programs related to Connected Vehicles to request feedback on standards needs and gaps.  One such organization is the Crash Avoidance Metrics Partnership (CAMP), a cooperative research organization made up of car manufacturers.

 

Deliverables: Webinar briefings (# to be determined), summary of any standards needs identified.

Key individuals: Narla (ITE), V2I Project Team

Target completion: 12/1/2015

Task 2.5   Catalog Standards Needs Identified.

With input from technical memos, webinar notes, and other documents, TWG 5 members will catalog standards needs and gaps, and prepare a document for circulation to V2I Stakeholders.

Note that TWG 5 has identified that the identification of standards needs and gaps will be an ongoing process, however, an interim deliverable of needs and gaps is expected by January 1, 2016 in order to allow subsequent activities to begin.

 

Deliverables: Document cataloging standards needs

Key individuals: TWG 5 members

Target completion: 12/1/2015

4.3 Activity 3: Validate V2I Standards Needs and Gaps

Issue(s) Addressed

Issue 8: Standards. V2I stakeholders need a V2I standards needs assessment and gap analysis to ensure that all needed standards are in place when needed to support V2I deployment.

What’s Needed  and Why

In order to prioritize and rank the V2I standards needs and gaps identified in Activity 2, it is important to validate each gap in order to understand the likely impacts of the gap (what is impacted, how is it impacted, how severe the impact will be to stakeholders).

12 Month Plan of Action

Task 3.1   Identify Impacts of V2I Standards Gaps

For each V2I standards gap, TWG 5 members will conduct internal discussions and analysis to identify the likely impacts of the gap (e.g. are there safety impacts, operational cost impacts, and technology impacts if standards are not developed?).  Efforts in Task 3.1 will begin to identify the impacts of these gaps concurrently as the gaps are identified. Impacts will be identified through experiences and judgement of TWG 5 members.  Monthly webinars will be used to define parameters to be used to assess the impacts of gaps, and then assess gaps as defined by Activity 2 efforts.

 

Deliverable: Update to the Standards Catalog to describe impacts of the gaps

Key individuals: TBD

Target completion: 4/1/16

Task 3.2   External Assessment of Gaps

In addition to internal TWG efforts in Task 3.1, efforts in Task 3.2 will invite input and feedback from external groups on the impacts of V2I standards gaps.  Candidate groups to be contacted include: CVRIA Architecture group, other SDOs such as NEMA and SAE, groups such as CAMP, and other V2I DC TWGs.  This outreach will seek additional input beyond the internal TWG 5 opinions on the impacts of each gap.

 

Deliverable: Update to the impacts described for each Gap based on outside input

 Key individuals: TBD

Target completion: 94/1/16

Task 3.3   Vetting and Ranking of Candidate Gaps.

After the internal and external assessment of gap impacts, efforts in Task 3.3 will vet and rank each candidate gap.  This process will be primarily performed by TWG 5 during monthly webinars or specially arranged webinars.  The target outcome is the identification of those high priority standards gaps that will be considered in Activity 4 and action plans will be created to address.  

Deliverable: Technical memo defining the prioritized V2I standards gaps

Key individuals: TBD

Target completion: 4/1/16

4.4 Activity #4: Determine Candidate Action Plans to Fill Standards Gaps

Issue(s) Addressed

Issue 8: Standards. V2I stakeholders need a V2I standards needs assessment and gap analysis to ensure that all needed standards are in place when needed to support V2I deployment.

What’s Needed

V2I Stakeholders need a set of action plans to address the highest prioritized V2I standards gaps identified in previous activities.  This will allow SDOs, funding agencies, infrastructure owners, and OEMs to plan and develop the needed standards over the coming years. 

12 Month Plan of Action

Task 4.1   Define Action Plans for Prioritized Gaps

For each V2I standards gaps identified to be high priority, efforts in this task will define a high level action plan that is needed to bring the new or supplemental standard to the marketplace.  Typically, this process will include assigning the most appropriate SDO to develop the standard.  However, it will also involve developing plans for any prototyping, testing, or certification needed before the standard is finalized and ready to support stakeholders.

 

Deliverable: Technical memo defining Action Plans for addressing the prioritized set of V2I Standards gaps.

Key individuals: TBD

Target completion: 7/1/16

 

 

4.5 Activity #5: Liaison and Support to Other V2I DC TWGs

Issue(s) Addressed

Issue 3: V2I Data - V2I partners need to understand and reach common agreement on the availability, accessibility, security, ownership, management, and storage of data.

Issue 5: V2I Security - At this time V2I partners need to identify the specific security concerns in order to prepare to address the security issue in more depth in subsequent years. 

Issue 6: V2I Outreach - Additional outreach, education, and information sharing is needed within the V2I community.

What’s Needed

As other V2I DC TWGs work on issues, there will likely be questions or discussion topics related to V2I standards.  Given the experience and expertise of TWG 5 members, it is likely that assigning liaisons from TWG5 to observe and participate in other TWGs will help address these issues with minimal resources required from TWG 5 members.  

12 Month Plan of Action

Task 5.1   Liaisons Participate in other TWGs

One or more TWG 5 members will participate in the webinars and discussions of other TWGs, as available.  TWG 5 will also be available to respond to email questions from other TWGs.  Specific areas where standards input is expected include:

  • V2I Data discussions;
  • V2I security discussions; and
  • V2I outreach, specifically related to helping TWG 4 identify standards information to share when conducting outreach.

 

Deliverable: Participation in other TWG webinars; Responses to questions as needed

Key individuals: TBD

Target completion: 7/1/16

5.Work Plan Schedule

The following schedule identifies the anticipated period of performance for the planned activities and tasks, including planned completion dates.

Work Plan Schedule

6.Description of V2I Issues

Previous sections have identified activities and tasks to address five of the V2I issues identified by the V2I DC.  This section includes the current description describing each issue.  Note: For brevity, only the five issues addressed in the work plan are included in this document (Issue #1, Issue #3, Issue #5, Issue #6, and Issue #8).  Issues are not prioritized at this time.  The numbering of issues does not imply prioritization.

Description of Issues

Issue 1: V2X Applications

There is currently a list of safety and mobility applications that have been developed through a collaborative effort between the auto industry, and public agencies facilitated by USDOT. These efforts have led to concepts of operations and requirements for selected applications, based on the systems engineering process. In addition, the auto industry is in the process of developing applications for their customers. There has also been some limited pilot testing done at the state and local level of selected applications (e.g. signal priority, wrong way driving).

There is a need for prioritization of V2X Applications (including multi-modal applications) and common understanding of how OEM and infrastructure applications work together.  It is also important to include multi-modal aspects in considerations about V2X applications.

 

 

Issue 3: V2I Data

Discussions surrounding V2I data have advanced in recent years, but there still remains unanswered questions regarding: data needs of transportation agencies; availability of data (particularly the Basic Safety Message Part 1 (BSM 1) and BSM 2); accessibility of V2I data; security of V2I data; ownership and business models for data access, management and storage.  

V2I partners need to understand and reach common agreement on the availability, accessibility, security, ownership, management, and storage of data.

 

Issue 5: Security

Security for Connected Vehicle continues to be a concern even though substantial work has been done by USDOT and others attempting to define an effective system. In 2014 NHTSA released request for information (RFI) requesting ideas from the private sector on how they would approach and operate a national security system. There is other environments where security is being addressed (e.g. NHTSA, Homeland Security, etc.). 

As a coalition, the V2I DC recognizes the value of having a robust security framework that extends beyond specific individual solutions, and recognizes the need to develop a framework within the transportation industry. The V2I DC looks forward to leading or collaborating with other activities in this area, with the intent of leveraging and applying frameworks developed by other domains, such as the Industry Council for Emergency Response Technologies (ICERT) within the Department of Homeland Security (DHS), if possible. 

At this time V2I partners need to identify the specific security concerns in order to prepare to address the security issue in more depth in subsequent years. 

 

Issue 6: V2I Outreach

Since the state and local transportation agencies will be directly involved with operating a connected vehicle system there is a sense that they should be more prominently and directly involved with the OEMs and USDOT in developing the system. It is essential for the USDOT to have broad stakeholder input into the Guidance and the program.

V2I information sharing topics should include planning and investing for V2I deployments; control, operations and maintenance of V2I applications; adding DSRC devices to roadside ITS devices; and other physicality related issues that surround a transition to supporting large scale RSE that will be required for V2I applications.

Additional outreach, education, and information sharing is needed within the V2I community.

 

 

Issue 8: V2I Standards

As transportation agencies begin the process of deploying V2I equipment and supporting systems, they may begin to deploy V2I infrastructure during their normal life cycle replacement period. This poses a challenge with understanding how an agency can confidently procure and deploy infrastructure that will be compatible with future V2I applications. Similarly, from the vendor perspective, vendors will inevitably want to begin to design, develop and manufacture devices and systems that they are confident will be compatible with future V2I applications.

Standards are perhaps the most logical solution to ensure interoperability, vendor independence, and scalability of V2I systems and applications.  This scope of V2I standards could include both migration of current ITS and vehicle standards to the V2I environment, as well as developing new standards as needed to enable consistent development, procurement, and deployment of the infrastructure and devices that will eventually comprise the nation’s V2I network. 

The V2I industry needs a V2I standards needs assessment and gap analysis to ensure that all needed standards are in place when needed to support V2I deployment.