1. A Vehicle Manufacturer’s Perspective on VII Christopher Wilson ITS Oregon- Feb 1, 2005 Christopher Wilson

2. Overview Why do we want this communications system? How does VII help us deploy? What are OEMs doing to support the decision? VII Goal: An informed decision, late in this decade, regarding the deployment of cooperative V-V and V-I short range communications system

3. Communications benefits Safety 5.9 GHz DSRC (802.11p) appears to be the tool we need Traffic signal violation warning Curve speed warning - rollover warning Emergency electronic brake lights Stop sign violation warning In-vehicle signing Road condition warning Near Term Safety Opportunity Example Applications Problem Solution?

4. Other benefits Operations & maintenance  Software and data updates  Diagnostics New services to customers  Using VII communications  Other related technologies (802.11x)  Based on new DOT capabilities from VII  Traffic, precise maps, weather

5. Why Now? Dedicated spectrum Positioning capabilities Low chipset costs (WiFi) Data processing capabilities Technology is available Costs are tractable

6. But issues remain… Short term availability  National rollout  Time certain  Early value to our customers Guarantee of long term (25 year +) stability  Technology  Cost  Expansions and modifications No turning back…

7. How does VII help? Explicitly aligns interests  Federal DOT  Local DOTs  Vehicle manufacturers  Customers Must define ‘conditions’ for near term deployment  Early return on investment ‘Contract’ for long term stability OEMs DOTs  Congestion info  O-D pairs  Road condition Drivers  Increased safety  Traffic information  Services (ETC, MP3 download…)  Diagnostics  Differentiation through services to driver  Relationship management VII

8. Guarantee of connectivity for OEMs Connectivity:  Communications to/from vehicle with defined capabilities  bandwidth/data volume per vehicle  connection frequency/ RSU distribution  availability Attributes  Lifetime of vehicle  Quality of Service  Known cost Vehicle-to-Vehicle Vehicle-to- Roadside ‘Internet’

9. Guarantee of public services for our customers Service Type (e.g.):  Safety  Signal violation warning  Fog warning  Information  Speed limit  Work zone warning  Map data  Traffic information Features  Nationwide  Frequent access  Availability by date certain  Long-term commitment  Potential for future expansion  More services  More RSUs

10. Protection for our customers and our investment Assurances that our customers interests will be protected  Privacy  Security of data network and collection  Defined uses (and non-use) for system  Fee structures Understanding how our investment will be protected  Changes to VII ‘contract’  Extensions to VII ‘contract’

11. VII short term goal: Feasibility Analysis Provides test environment  Validating technology, business and institutional assumptions  Incremental commitments Provides discussion venue  Incremental trust and understanding  Relationship building between principal stakeholders  Vehicle manufacturers  DOTs Demonstrate value to key stakeholders  DOTs and OEMs  Drivers  Transportation businesses

12. What are Vehicle Manufacturers doing? We have formed the Vehicle Infrastructure Integration Consortium  New, non-profit corporation  Open to all vehicle manufacturers  Incorporated November, 2004 Current Membership (in process) Nissan DaimlerChrysler Ford Volkswagen BMW

13. VII Consortium (VIIC) The VII Consortium's primary goal is to evaluate the deployment viability (technical, economic, and political/social) of a national infrastructure to enable data collection and exchange in real-time between vehicles and between vehicles and the roadway. Members agree that such an evaluation proceeds from a position in support of eventual deployment of VII technology, provided that deployment viability is established.

14. VIIC Role Promote common business interests Promote public and private consensus Establish a venue for dialog Establish cooperative agreements for evaluating deployment viability Promote and encourage productive relationships

15. Conclusion: Our Commitment Consensus building through continued dialog among principal stakeholders Full evaluation of VII technology, applications, deployability, and acceptability Reach a joint decision regarding deployment late in this decade (i.e., understand how to deploy a VII system, or why we can not)