Intelligent Transportation Systems

(ITS) Joint Program Office (JPO)

Connected Vehicle Reference

Implementation Architecture Update
Stakeholders Webinar
November & December 2013

Poll Question 1
Which of the following best describes your role in Connected Vehicles?
Federal Government
State DOT or Metropolitan Planning Organization
Local government
Car maker / OEM
Roadside equipment maker
Consultant
Academic
Other

CVRIA Update Webinars

These webinars are meant to:
Familiarize attendees with the Connected Vehicle Reference
Implementation Architecture (CVRIA) so that they will be
equipped to provide feedback on the architecture
Provide an update on the development of the CVRIA
Review portions of the CVRIA Website
Discuss standardization planning and policy analysis
Todays Speakers
Walt Fehr
Carl Andersen
David Binkley, Ron Ice, Tom Lusco
Jim Marousek, Chris Karaffa
Dawn LaFrance-Linden, Scott Smith
3

CVRIA Update Webinar Agenda

Topic
Welcome & Background/Overview
Introduce Applications of the Day
CVRIA Applications (see table)
Interface Selection / Standardization Planning
Pertinent Policy Issues
Q&A

Start
2:00
2:10
2:15
3:00
3:15
3:30

End
2:10
2:15
3:00
3:15
3:30
4:00

(All Times Eastern)

CVRIA Update Webinar Applications to be

Reviewed
Applications for Webinar
V2I

Red Light Violation Warning

Curve Speed Warning
Speed Harmonization (SPD-HARM)

Signal Applications

Nov 14

Intelligent Traffic Signal System

Emergency Vehicle Priority
Eco-Approach and Departure

Road Weather

Date
Nov 6, 2013

Nov 19

Weather Responsive Traffic Management

Enhanced Maintenance Decision Support

CVRIA Update Webinar Topics, continued

Topics
Freight & Fleet Operations

Smart Roadside Initiative

Freight Advanced Traveler Information Systems (FRATIS)

Support Applications

Dec 10

Pedestrian & Turning Vehicle Crash Warning

Integrated Multi-modal Payment

R.E.S.C.U.M.E.

Dec 3

Data Distribution
Communications Support
Core Authorization

Transit Applications

Date
Nov 26

Dec 17

Incident Scene Pre-Arrival Staging Guidance for Emergency

Responders
Incident Scene Work Zone Alerts for Drivers & Workers

(Dates/Times and Specific Topics Subject to Change)

Connected Vehicle Reference Implementation

Architecture (CVRIA)
Landscape: Safety, Mobility, Environmental Applications with common
supporting infrastructure

Purpose of CVRIA is to identify a framework for integrating connected vehicle

technologies and identify interfaces for standardization
By...
Collecting and aggregating connected vehicle needs/requirements
Developing a multi-faceted system architecture
Identifying and prioritizing candidate interfaces for standardization
Conducting policy analysis around the architecture
Near term uses Define interfaces/functions/standards to support early
deployments, e.g. SE Michigan Testbed 2014
Longer term the National ITS Architecture will incorporate CVRIA to support use of
connected vehicle in
regional ITS architectures/plans
future transportation projects
SO We need your help.
Are we capturing the connected vehicle applications adequately
Are we including all of the necessary interfaces
Well show you how to provide feedback via the website.
7

Poll Question 2
With what area of the connected vehicle
program are you or your stakeholders
primarily interested?
Safety
Mobility
Environment
Support

CVRIA Website Users Guide

This site uses Scalable Vector Graphics (SVGs) to produce diagrams that
are crisp and support hyperlinks from the graphical elements to the detailed
descriptions
Different web browsers support SVGs in different ways (some not at all).
Try viewing the site with browsers like Firefox, Chrome, Safari for best
results.
As an alternative to SVGs all graphics are also available Portable Network
Graphics (PNG) format. You may have to click on the PNG option to see
it.
This site is still under construction, many pages are updated on a fairly
regular basis. Make sure you are looking at the latest version of a web page
by clicking Refresh or Reload within your browser.

Web Tour Road Map

Start here
JPO / Stds /
Activities /
CVRIA

Lets focus on an application

What about standards?

Applications Tab

Standards
Tab

How do I learn about an app?

Start / Home
www.iteris.com/c
vria/

Whats the overall layout?

Architecture
Viewpoints Tab

Physical Tab
(objects, flows,
comm)
Enterprise Tab
(4 phases)
Functional &
Requirements
Tabs

What else is here?

Resources /
Glossary

How do I provide feedback?

Comment on
Page
10

Lets Begin the Tour

Go To Website

http://www.standards.its.dot.gov/DevelopmentActivities/CVReference
Or
http://www.iteris.com/cvria/index.html

11
At conclusion of webtour Skip to Use of CVRIA Slides

Uses of CVRIA
Now that youve completed the tour of the website, lets talk about some ways that CVRIA can
be used...

SE Michigan Test Bed 2014

Future Connected Vehicle Projects

Provide platform for interoperability

between vendors, operators and
solution providers by developing V2I
data exchanges
Field and Back-Office functions
Developing Architecture Views using
CVRIA:
Physical (What)
Multi-layer diagrams
Enterprise (Who)
Communications

CVRIA Mini-Tool allows developers to

use the CVRIA Visio Drawings
Customize physical view drawings to
describe future projects using same
language and format
Supports multi-layer approach
Layer 0 high-level objects and
interconnections
Layer 1 project specific physical,
application objects
Layer 2 application level (just like the
application drawings on CVRIA
website)

Connected Vehicle projects can be defined as collections of applications from

CVRIA and use the same language, interfaces, standards
12

CVRIA Next Steps

November / December
Gathering feedback from webinars and website
Incorporate inputs
Update tools
Ongoing
Maintain CVRIA
2014 / 2015
Monitor usage in Test Beds, Demos, Early Deployments
Updating architecture, tools as needed
Merge / Incorporate CVRIA into Natl ITS Arch

13

Intelligent Transportation Systems (ITS)

Joint Program Office (JPO)

Connected Vehicle Reference Implementation

Architecture:
Standards Development Strategy and Plan

14

CVRIA and Standards

The USDOTs Intelligent Transportation Systems (ITS) Joint Program Office
(JPO) is developing a standards plan to guide ITS standards-related efforts
and activities in support of the USDOT ITS connected vehicle research
program, and to support broad deployment of connected vehicle (CV)
technologies
This plan will be a living document that will evolve as ITS technologies,
implementation strategies, and policies develop
The plan will help the USDOT bridge the standards gap

15

Standards Plan Approach

Once interfaces are identified and defined, they must be prioritized and
associated with standards, which will then be prioritized
The CVRIA will identify and define
interfaces within the connected vehicle
environment (CVE).

Standards
Plan

The standards prioritization will be applied to

those gaps to develop the standards plan.

16

Using Prioritization
Scoring process and criteria are not absolute
They are one factor, among many, in determining how to allocate
resources to support standardization activities
Prioritization
Criteria

USDOT Policy

Standardization
Activity Support

Leadership
Direction

They may be adapted to evolving goals and objectives

17

Next Steps
Currently
The CVRIA viewpoints/database are being analyzed now to identify and
define interfaces within the architecture.
Feedback
Feedback on applications or other aspects of the architecture will help us
to refine: interface identification and definition; scoring; interpreting results.
Second Public Workshop
Presentation of findings and results of interface and standards prioritization
First opportunity to share results of the interface and standards analyses
Tentatively planned the San Francisco Bay Area, February 2014

18

Poll Question 3
Are these views clear and stable enough
to start interface analysis for standards?
Yes
No
Unsure

19

Intelligent Transportation Systems (ITS)

Joint Program Office (JPO)

Connected Vehicle Reference Implementation

Architecture
and
Connected Vehicle Policy
Dawn LaFrance-Linden
USDOT / Research and Innovative Technology Administration /
Volpe National Transportation Systems Center
November 2013

20

When we say Policy Issue Areas Include

Certification.what certification is required?

Communicationswhat technologies are preferred?

Credentialingwho has access to CV systems?

Data governancewho may access the data?

Governance.what are the roles of the participants?

Intellectual Property..what are the risks for exposure?

Interoperabilityhow is data exchange handled?

Liability.who is responsible for bad outcomes?

Privacy..what information to protect?

Resiliency.what are the failure modes?

Security.how to we prevent inappropriate usage?

Social equity....how are benefits distributed?

21

Curve Speed Warning

22

Policy Process (1/2)

For each application:
Identify information flows
Primarily from physical
view
Some enterprise
Look for policy issues

23

Policy Process (2/2)

Write brief summaries of each
issue
One information flow may
apply to multiple applications

24

Curve Speed Warning (CSW)

Application Specific Issues
Governance: Setting the appropriate speed
Inconsistency among jurisdictions today
Ability to gather data on actual driver
speeds.
Resiliency: Multiple data sources
Most of the CSW application can be
implemented without connected vehicle
technology
What happens when the radar and OBE
differ on their measurements of vehicle
speed?
Resiliency: What happens if map data is not
available?

Universal Issues
Interoperability between roadside equipment
(RSE) and onboard equipment (OBE)
Communications
When is DSRC really needed?
Security of links between external data
sources (Maps and RSE) and vehicle OBE;
security of links to RSE
Dependence on reliable map and roadway
geometry information
Social Equity
Safety impacts on non-connected vehicles
Use of data
Privacy (movement tracking)
Enforcement
Liability

25

Red Light Violation Warning (RLVW)

26

Red Light Violation Warning (RLVW)

Application Specific Issues

Universal Issues

Governance: How does the signal respond

to a hazardous situation (e.g., driver is
approaching at high speed, unable to stop for
the red - should the cross-street green be
delayed? )

Interoperability between roadside equipment

(RSE) and onboard equipment (OBE)
Communications
When is DSRC really needed?
Security of links between external data
sources (Maps and RSE) and vehicle OBE;
security of links to RSE
Dependence on reliable map and roadway
geometry information
Social Equity
Safety impacts on non-connected vehicles
Use of data
Privacy (movement tracking)
Enforcement
Liability

Data governance: Who has access to the

data and for what purposes? For example:
Law enforcement, insurance companies, etc.
Liability: If a vehicle with right-of-way ignores
the warning that another vehicle is likely to
run the red light, does the vehicles driver
bear any liability for the accident?

27

Speed Harmonization (SH)

28

Speed Harmonization (SH)

Application Specific Issues
Governance: How is the correct speed
determined? When is speed harmonization
indicated? Is compliance voluntary or
mandatory?
Credentialing: How are Traffic Operations
Personnel trained? What actions are they
permitted with respect to SH?
Social Equity: Are drivers more likely to
comply with speed harmonization requests
received through CV system vs. more
traditional approaches? What percentage of
vehicles need to harmonize speed in order for
this traffic management technique to be
effective?

Universal Issues
Interoperability between roadside equipment
(RSE) and onboard equipment (OBE)
Communications
When is DSRC really needed?
Security of links between external data
sources (Maps and RSE) and vehicle OBE;
security of links to RSE
Dependence on reliable map and roadway
geometry information
Social Equity
Safety impacts on non-connected vehicles
Use of data
Privacy (movement tracking)
Enforcement
Liability

Liability: Does a driver bear any liability if

involved in an accident caused wholly, or in
part, by adhering to SH directions?
29

Conclusion
Why perform this analysis? Government role is to:
Encourage use of connected vehicle technologies to provide public
benefit
Discourage misuse that would create harm to the public
Tools that are available to the government:
Resources and guidance
Regulation and policies
Provide a stable environment for others to use/deploy in
Build public trust in the system
Discourage misuse

30

Poll Question 4
Do you plan to visit the CVRIA website
and add comments by the end of
December?
Yes
No
Unsure

31

Poll Question 5
Do you plan to attend any subsequent
CVRIA webinars?

Signal Applications on Thursday 11/14

Road Weather on Tuesday 11/19
Freight and fleet operations on Tuesday 11/26
Support applications on Tuesday 12/3
Transit and non-motorized user applications on Tuesday 12/10
Public Safety on Tuesday 12/17
None

32

Intelligent Transportation Systems (ITS)

Joint Program Office (JPO)

Connected Vehicle Reference Implementation

Architecture Update

Q&A + Final Thoughts

33

Thank You!
This concludes todays webinar.
Check out the T3 site and the CVRIA website for the next
webinar or to view archives of previous webinars.
Keep those comments coming!
[email protected]
For other questions on CVRIA or
the connected vehicle program:
[email protected] 202-366-1603
[email protected] 202-366-0278

34