# Presentation: 738875

## Integrated Vehicle Based 

**Integrated Vehicle Based **
**Safety Systems**

**Jack Ference, IVBSS Technical Manager**
**ITS America Annual Meeting**
**May, 2005**

## 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

## 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**

## Target Crash Problems

## IVBSS Objectives

**	**
**Establish **Government-Industry Partnership
**Facilitate **introduction and commercialization of effective integrated systems** **
**Support **the Government’s role in advancing safety product deployment

## Leveraging Prior Work

- Government-Industry **Partnerships**
- Performance **Specifications**
- Objective Test **Procedures**
- Field Operational **Tests**
- Enabling and Enhancing **Technologies**
- Independent **Evaluations**

## 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

- 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**

## Program Timeline

**7/04**

**Gov’t-initiated activity**

**Partner-led activity**

## Program Activities

**Gov’t-initiated activity**

**Partner-led activity**

**Gov’t-Industry activity**

## Public Meeting

**Was held** in Detroit September 21, 2004 to gather input from all stakeholders
**Information **is published online by ITS America: **http://www.itsa.org/ivbss.html**
- 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

## 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

## 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

## Contact:

**Jack Ference**
**U.S. DOT /NHTSA**
**(202) 366-0168 **
**jack.ference@nhtsa.dot.gov**

**Notes:**
Here is my contact information. Please feel free to contact me at any time with any questions. Thank you!