Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
First, some definitions and context:
Situation data: applies to the fundamental data that move throughout the system.  e.g., location of a vehicle at a specific time; color of traffic light at a specific time.  So whenever data on the state of an element is transmitted, it needs to include a time stamp.
The USDOT has passed the Internet of things and has moved on to the Internet of Something Big.
Something is needed that brings all installations into a nation-wide or continent-wide uniformity at a fundamental level.
Everyone should be able to participate and benefit.  This is bigger than a single company or governmental unit.
Transportation has experienced several “Something Bigs”
The transcontinental railroads.  Standards-based uniformity of the fundamentals (rail gauge, time, etc.) and government support (land grants, etc.)
Interstate highways.  Uniform construction of roadways by independent states and their contractors.  Again, significant US government support in the form of guidelines and funds.
Signage.  Every day, operations of the 250,000,000 vehicles on the roadway in the US are presented with Megabytes of data in the form of metal signs.  Those signs are very uniform in nature independent of who installed them or where they are installed.  Based on the Manual for Uniform Traffic Control Devices.
Uniform deployment based on concepts developed in Southeast Michigan 2014 project.
More likely that system will be interoperable.
Goal is continent-wide deployment.  Everything in the testing is being developed to be deployed on a much larger scale.
Comments and critiques are welcome
Question: How do we know when a particular application is “approved” 
Answer: Complex policy question – no answer yet.  We will learn more about the level of governance and peer review needed as we move ahead
Question: What is the threat model used to evaluate security?  Who is the attacker?
Answer: everything from innocent pranksters to malicious hackers
Time and place context:  e.g., vehicle location is hyper-local data: needs to be known at the millisecond level.  But, it can also be used in other contexts, where it does not need to be hyper-local any more.   Can be aggregated, for example, for analysis – derivative data.  And can then be returned back to hyper-local level, to assist drivers with decisions
This is a fundamental concern – and needs to be built into the design of the system from the beginning.
Privacy/anonymity protection team – to guide development to ensure that privacy protection is application and communication media neutral.
To facilitate the movement of data from one object in the system to another
New collections of objects are constantly forming, dissolving and re-forming.  Never the same collection of objects for very long.
So, an overall data exchange strategy is needed that that takes this into account.
The data exchange sequence is designed to work in this context: objects come together, establish trust, communicate, dissolve, and have a record to deal with disputes
The CV architecture and systems are designed to address all these needs – now we are testing them to see how well they work, both with transactional data, and in “broadcast mode.”
Integrity: being able to detect bad actors/bad data