Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Communication, data, and communication media fundamentals needed to produce CV system
Purpose of Slide: Discuss the deployment plan.
Transition: The connected vehicle program is moving toward infrastructure deployment.
Key Messages: NHTSA has mobilized staff from their policy, legal, and rulemaking divisions to work with their research division and the ITS Joint Program Office (JPO) staff to analyze the results of the research to date and make a decision on how to move forward.
In early February, NHTSA announced that it would finalize its analysis of the data gathered as part of its year-long pilot program and will publish a research report on V2V communication technology for public comment in the coming weeks. The report will include analysis of the department's research findings in several key areas including technical feasibility, privacy and security, and preliminary estimates on costs and safety benefits.
NHTSA also announced it would begin working on a regulatory proposal that would require V2V devices in new vehicles in a future year, consistent with applicable legal requirements, executive orders, and guidance. DOT believes that the signal this announcement sends to the market will significantly enhance development of this technology and pave the way for market penetration of V2V safety applications.
Policy research on system security, privacy, governance, business models, and legal issues are also front and center to the decision-making process. We are well on our way for the safety research. Assuming a positive decision, this paves the way for the rest of the program. As we look ahead, the department is planning a significant investment in infrastructure-related research for safety, mobility, environment, and weather.
You will see significant research in applications development. We are also working on the enabling technology and FHWA is planning to develop infrastructure deployment guidelines for State and local agencies.
Pending success for these efforts, we see an opportunity to build off the safety pilot and conduct additional pilots to assess benefits and seed implementation. We are currently in an open process to look at the opportunities and needs for a new wave of connected vehicle pilots.
On a continuum of deployment
Lots of factors coming into alignment to make possible real world deployment of CV systems
By 2016 – large pool of stakeholders, ready to participate
Just finished V2V crash avoidance testing in Ann Arbor
Now, working on fundamentals to get ready for 2015-2016 timeframe – large scale deployments
Goal: nationwide or even continent-wide deployment
Communication/security: communication security practices apply to ALL information flows throughout entire system.  Can be applied to any communication medium regardless of where it sits in the architecture
Privacy by design: want to perpetuate the concepts tested in Ann Arbor and apply them to entire system
Data flow/evolution: needs to be able to scale up to a national level.  Architecture designed to support 2 types of data:
* Private data used to support P2P transactions – like ecommerce
* Data that everybody should have access to in a CV environment, and everybody should have access to
Multiple communication media: working on getting them all to function together seamlessly. 
Tools: convenient way to share knowledge / institutionalize knowledge, to share with people who will actually implement the CV projects.  To support interoperability with previous work, and other projects being developed concurrently
We think that there are three things that if done well will project connected intelligent transportation systems into the “after” state:
1)To accomplish transportation application goals, we have a number of communication resources that have to be properly, efficiently melded together, and
2)There are two classes of data used in transportation systems.
3)Those two things can then be unified through well-organized tools.
The Southeast Michigan 2014 project embodies the fundamentals we need to work on:
All elements of a connected vehicle system – mobile, field, center.
Multiple communication media with a common process for assuring trust and protecting confidentiality.
Data abstraction points to facilitate data flow and aggregation.  A place is provided for multiple application interest groups to connect up and use (and contribute to) the flow.
The things in the boxes are physical objects.  Lines are information flows
The blue boxes (upper right) are inside the vehicle
Yellow boxes are travelers and their equipment
In the middle (orange and teal) exist at the boundary between moving and fixed elements.  Bridge between wired and wireless
On the left side: fixed infrastructure – they exist somewhere at an IP address.  Data are gathered and aggregated and synthesized
Black oval: facilitate the flow of the fundamental data that all travelers need.
Bottom (dark green): support services for overall concept – to make it all work
This is the kind of system that we think could be scaled up to national level
We’ve held a number of stakeholder events – training and testing.
We are gearing up to do CV pilots that the DOT will sponsor.
People can get involved in the Southeast Michigan 2014 project two ways:
Be part of an on-going DOT activities, and/or
Be part of the Affiliation of Test Beds.