May, 2005ITS America 2005Slide 1 Integrated Vehicle Based Safety Systems Jack Ference, IVBSS Technical Manager ITS America Annual Meeting May, 2005

ITS America 2005Slide 2 What is IVBSS? A New Tier I Initiative Vision: All vehicles would be equipped with integrated driver assistance systems to help drivers avoid the most common types of crashes. Goal: To work with industry to accelerate introduction of integrated vehicle-based safety systems into the U.S. vehicle fleet. Addresses 3 Crash Types: Rear End Road Departure Lane Change

Who’s Involved Program Manager: Jack Ference Program Coordinator: Mike Schagrin, FHWA ITS JPO Commercial Vehicle Lead: Tim Johnson Evaluation Leader: Wassim Najm Transit Vehicle Lead: Brian Cronin

May, 2005ITS America 2005Slide 4 Why is Integration Important? Increased safety benefits Better overall system performance Reduced system cost (economies of scale) Improved driver and fleet acceptance Enhanced marketability Rear-end, run-off-road, and lane change crash countermeasure systems could prevent over 48% or 1,836,000 target crashes. Program Motivation

May, 2005ITS America 2005Slide 5 Target Crash Problems Buses* 21,000 crashes 8,000 injured 17 killed Medium/Heavy Trucks* 218,000 crashes 75,000 injured 1,336 killed Light vehicles* 3,659,000 crashes 1,535,000 injured 19,106 killed * Numbers represent rear-end, lane change, and run-off-road crashes only.

May, 2005ITS America 2005Slide 6 IVBSS Objectives Establish Government-Industry Partnership Facilitate introduction and commercialization of effective integrated systems Support the Government’s role in advancing safety product deployment

May, 2005ITS America 2005Slide 7 Leveraging Prior Work Government-Industry Partnerships Performance Specifications Objective Test Procedures Field Operational Tests Enabling and Enhancing Technologies Independent Evaluations

May, 2005ITS America 2005Slide 8 Program is feasible – industry supports it Program will be conducted by consortium Common sensor set and DVI concepts Level of system performance, R&D, size of field test(s) and other activities determines total project cost - tradeoffs Program will be carried out FY05-FY09 U.S. DOT’s “Going in” Assumptions

May, 2005ITS America 2005Slide 9 Program Timeline 7/04 10/0910/054/0610/064/0710/074/0810/084/09 System Design Performance Specifications Test Procedures Build and validate prototype vehicles Vehicle Validation Conduct FOT FOT Start FOT End Perform independent evaluation Benefits Gov’t-initiated activity Partner-led activity Preparatory Analyses Partner Selection Go/No Go

May, 2005ITS America 2005Slide 10 Program Activities Prepare program execution strategy Solicit stakeholder input Develop functional & evaluation requirements Conduct technical review Investigate preliminary DVI concepts Assess business case/ deployment potential Develop performance specifications Design, build, & test sensor subsystems Design, build, & test threat assessment algo. Design, build, & test DVI Develop objective test procedures Design & build data acquisition systems Integrate subsystems & build prototype vehicles Conduct objective test procedures Validate performance of prototype vehicles Finalize design & build FOT-ready vehicles Develop operational concepts Develop performance specifications and test procedures Build and validate prototype vehicles Preparatory AnalysesConduct FOT Perform evaluation System Design Gov’t-initiated activity Partner-led activity Devise FOT Concepts Recruit test subjects Build vehicle fleet Conduct pilot test Conduct FOT Devise evaluation strategy Develop evaluation plan Develop analysis methods Build database & tools Analyze data & write report Gov’t-Industry activity

May, 2005ITS America 2005Slide 11 Public Meeting Was held in Detroit September 21, 2004 to gather input from all stakeholders Information is published online by ITS America: Meeting was set up to be highly participatory in a workshop format so that all of the stakeholders would have a chance to provide input on the program

May, 2005ITS America 2005Slide 12 Public Meeting Summary Real World Validation crucial Timeline is aggressive Human Factors issues are critical: –DVI design is challenging: don’t add complexity –More research needed to create the most effective Driver-vehicle interface (DVI) –Account for unintended consequences Consumer Education and Training important

May, 2005ITS America 2005Slide 13 Current Status Preparatory Analyses completed RFA to be issued in May-June Pre bidders conference 2-4 weeks after RFA issued Applications due 60 days after RFA issued Selection will be made by end FY’05 System Design will start early FY’06

May, 2005ITS America 2005Slide 14 Contact: Jack Ference U.S. DOT /NHTSA (202)