Research Elements of 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 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 5 Program Activities & Tasks 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 6 There are many research issues to look at: Multiple threats and Prioritization of warnings Ways to avoid a crash Behavioral adaptation Non-useful warnings (includes false warnings) Effective DVI design

May, 2005ITS America 2005Slide 7 Multiple Threats A major issue with multiple warnings is not only alerting the driver to the presence of multiple threats, but communicating the hazard type and appropriate response. Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 8 Multiple Threats Example: FCW + Lane Change Warning *From Chiang, Brooks, and Llaneras, Nov 2004, “Investigation of Multiple Collision Alarm Interference Driving Simulator Study” Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 9 Multiple Threats How can multiple threats that occur at near-simultaneous points in time be communicated to the driver? –Is multi-modal presentation more or less effective than using one modality? –Can drivers discriminate between alerts and effectively respond to each threat? Can an IVBSS system be effective without prioritization? Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 10 Can a driver successfully be directed how to avoid a crash? –How many scenarios need to be developed to understand what is possible? Are auditory instructions (such as “swerve left”) appropriate or are there better ways to elicit quicker or appropriate responses from drivers? –For example, a haptic cue or a pedal push may result in quicker response times or less confusion as to how to respond Avoiding a crash Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 11 Avoiding a crash *From Chiang, Brooks, and Llaneras, Nov 2004, “Investigation of Multiple Collision Alarm Interference Driving Simulator Study” Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 12 How should the system be designed to minimize adverse behavioral adaptation by drivers? –What is needed to prevent riskier driving behavior due to the perception of increased safety provided by an (effective) crash avoidance system? Behavioral Adaptation Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 13 Non useful warnings include: –False alarms –Nuisance warnings Examples: –An FCW system detects an object ahead of the vehicle on a curve, out of the intended travel path, but in the radar’s field of view –A driver is already responding to an object detected by a CW system Non useful warnings Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 14 How will non-useful warnings (including false alarms) affect driver acceptance and system effectiveness? –What is the acceptable level of false alarms and other non-useful warnings? Additional Examples: –A driver changes a lane without using a turning signal and the system recognizes an off-path target –A false curve speed warning goes off and an off-path target is detected Non useful warnings Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 15 Sensors and technology may be able to detect a crash threat, but the Driver Vehicle Interface (DVI) must be effective or the IVBSS system will not be successful. DVI Design Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 16 How will individual differences and intervening variables such as age be accommodated? What are the DVI implications? Should a DVI adapt to the state of the driver? (distracted, impaired, alert) Are there DVI parameters that should be standardized? DVI Design Key Human Factors Research Issues for IVBSS

May, 2005ITS America 2005Slide 17 The key to driver acceptance and successful deployment of IVBSS technology will be an effective DVI There are significant human factors research issues that need to be and will be addressed in the IVBSS program Creating an effective DVI may be a larger challenge than the integration of system hardware and software Final Thoughts…

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