Vehicle Infrastructure Integration

1. Vehicle Infrastructure Integration Technical Status Update Steve Sill, P.E VII Technical Manager June 4, 2007

2. Key VII Viability Questions • Technically, will the infrastructure, vehicles, and applications work together to deliver the intended functionality? • Once fully deployed, do the overall Economics make sense? • Can a realisticDeployment plan be developed: • Have Political and Policy Issues been addressed to the satisfaction of key stakeholders?....including security?, privacy?

3. Status in brief – Where are we today? • Herndon “Lab Test” of network up and running • Test results encouraging • Vehicle integration/test of On-Board Equipment (OBE) began June 1 • Detroit Proof of Concept Test (POC) to begin in August • Connected to Herndon and California test environments • POC testing expected to be completed early 2008 • Data Analysis to Follow • USDOT plans to keep Detroit test environment available for further testing by other as well as USDOT

4. VII Development Plan Joint Viability Decision Refine Costs, Benefits and Risks Progressive Engagement Proof of Concept Functionality & Feasibility Technical Social/Political Economic Governance Deployability Cost/Benefit Business Model Security Private Services Privacy Risks Safety Mobility Accessibility Reliability Viability Criteria Maintainability

5. Viability criteria will be addressed using a variety of methods • Paper Studies, Analyses • Simulation & Modeling • Laboratory Testing • Closed Test Track evaluations • Over-the-road testing (POC and other DTE)

6. POC Goals and Objectives • Test and demonstrate the technical viability of the VII system concept. • Prove that system can meet basic objectives required to demonstrate feasibility of VII-enabled applications • Supports intended safety functionality • Supports intended mobility functionality • Supports private/commercial services • Demonstrate that the VII System provides technical solutions to address policy concerns: anonymity, privacy, and security

8. POC will Address Decision Criteria to Varying Degrees • Technical– Primarily shown via POC • System can competently and reliably deliver intended services and functionality with acceptable risk • System Functionality – both Vehicle-to-Infrastructure & Vehicle-to-Vehicle • Network Management Tools • Technical System Security and System Privacy Solutions • Safety, Mobility, and Private Application Feasibility • Concurrent operation/prioritization of multiple applications • Economic – Limited data via POC • Provides data to feed future analyses to estimate: RSE installation, Hardware, O&M, and Backhaul Communications costs/skills • Costs incurred during POC not directly scaleable • Social/Political – Limited data via POC • Demonstrate intrinsic privacy protections • Demonstrates the technical provisions built into system to ensure security

9. POC Integration and Testing Flow VII Subsystem Testing (OBE, RSE, Infrastructure) System Integration and Test (Herndon, VA) System Integration and Test (Detroit, MI) POC Application Integration and Test

10. Phases of POC Testing Testing will take place in three major phases: 1. VII Infrastructure Subsystem Testing • Focus on component requirements verification • Allow us to execute performance and stress tests not possible at DTE 2. VII Systems Integration and Testing • Herndon Laboratory, and, OEM Garages/Test Tracks • Focus on the integration of OBE, RSE and the VII Infrastructure • Includes a limited set of test software that will test the VII System services • Detroit DTE • Focus on testing the VII System in a real-world environment • Simplified “application stubs” to test functionality 3. POC Application Integration and Test • End-to-End Testing the ability of VII to support the Day-1 applications

11. POC testing will progress from laboratory through the open road tests in Michigan Laboratory & Garage Closed Test Track Open Road • Simulated probed data sets and messages; simulated failure modes • Completed at developers labs & garages • Component Stress Testing • Subsystem Integration and interface specification Tests • Test to standards • Controlled environment on closed proving ground facility, • Professional Drivers • Highly instrumented vehicles (to know “ground truth”) • Staged events • Testing on public roads in Michigan, • OEM supplied and leased vehicles operated by professional drivers • Standardized HMI • Fully functioning test vehicles • Function-specific tests, and, end-to end application testing

12. POC Test Schedule

13. What is not directly addressed by POC • Validation of scalability issues • System provides benefits to all stakeholders at all levels of deployment • Economic benefits • System supplies intended benefits within acceptable cost and risk limits and can be deployed in a manner that is self-sustaining • Social / public acceptability • Benefits are adequately demonstrated and publicized, and system can be deployed and governed in a manner acceptable to the public and its political advocates and leaders • Applications Benefits Assessments • Demonstrate business value for expected Day-One applications

14. What happens after POC? • USDOT will engage stakeholders in further discussion of how to move forward • Will develop best approach considering funds available • At minimum, we expect to: • Keep the Detroit test environment up and available • Use for applications development • May be used by interested parties for their own development efforts • Correct major deficiencies identified during POC • Maintain connection to Herndon and CA environments

15. What happens after POC? (continued) • Additional potential future efforts – first priorities?: • Infrastructure enhancements to improve performance • Additional testing/development • More detailed national deployment analyses • Additional potential future efforts – next priorities?: • Expand test environment, vehicle fleet • Enhance vehicle fleet size and capability • Additional testing/development

16. Next: VII Applications