The Integrated Safety programme

1
The Integrated Safety programme
2
The Integrated Safety programme

• C2C and C2I Comm.
• Suppliers
• Automotive Industry

• HMI Concept
• Automotive Industry
• Suppliers
• Research Institutes

• Advanced Restraint
• Systems
• Suppliers
• Automotive Industry
• Research Institutes

• ADAS Maps
• Suppliers
• Automotive
• Industry

• In-vehicle Network
• Automotive Industry
• Suppliers

• Environment Sensing /
• Sensor Fusion
• Suppliers
• Research Institutes
• Automotive Industry

Also cooperation foreseen with SPARC and ADASIS
Forum

• Actuators
• Suppliers
• Automotive Industry
• Research Institutes

3
The vision of IP PReVENT

• IP PReVENT creates a virtual safety belt around
  the vehicle by
• developing a set of complementary safety
  functions
• Exploiting sensor data fusion, maps and
  communication technologies
• using an integrated approach to increase system
  capabilities and achieve optimum cost-benefit
  ratio

4
Preventive and active safety
Inform
Support
Intervene
5
The virtual safety belt
6
IP PReVENT Phase 1 3 Cross-functional activities
7
IP PReVENT Phase 1 4 Function fields - 8
Vertical Subprojects
8
(No Transcript)
9
(No Transcript)
10
Main results from IP Requirements
 

• Deducing functional requirements based on
• Previous work,
• Knowledge of driver behaviour and accidents,
• Current road safety situation and on-going
  programs.
• Describing the PReVENT vision
• Describing functional requirements for various
  applications in four functional areas
• Defining integration aspects

11
IP Requirements Approach
12
PReVENT vision and integration

• Safety zone
• Extend drivers field of view

13
ProFusionsensor data fusion technologies

• Sensors and functional areas

14
MAPSADASInterface to safety digital maps
ADAS MAP
ADAS Interface
15
RESPONSE3 Code of Practice
Identification of possible risky situations
Specification Framework
16
Role within IP PReVENTSafe Speed and Safe
Following
17
RequirementsSafe speed and safe following

• Driving situations
• Dangerous obstacles or conditions ahead
• Sensors
• LR radar, maps, camera, on-board sensors,
  communication
• Actuator function
• Warning, active gas pedal

18
RequirementsSafe speed and safe following

• Requirements at IP level Main issues
• Sensor data fusion for object and road geometry
  estimation
• Link between data by on-board sensors and hazard
  messaging by communication Input from WILLWARN
  to SASPENCE functions
• HMI and warning strategies through primary
  controls
• Link with collision mitigation and intersection
  safety

19
Role within IP PReVENTLateral Support
20
RequirementsLateral support and driver
monitoring

• Driving situations
• Supporting the maintenance or even recovering the
  correct lateral position (focus on critical
  conditions)
• Lane change
• Sensors
• CMOS camera, radars, (long short range) maps,
  stereo
• Actuator function
• Information, Warning, Intervention

21
RequirementsLateral support and driver
monitoring

• Requirements at IP level Main issues
• Sensor data fusion for monitoring large area
  (lateral and rear)
• Interaction between longitudinal and lateral
  vehicle controls indications for 2nd phase

• HMI solutions different levels integration
  with other functions

22
Role within IP PReVENTIntersection safety
23
RequirementsIntersection safety

• Driving situations
• Crossing and turning at intersections
• Red lights and stop-signs

• Sensors
• Laser scanner and camera
• Actuator function
• Warning

24
RequirementsIntersection safety

• Requirements at IP level Main issues
• Solutions for capturing complex and heterogeneous
  environment
• Communication method
• Model for risk assessment in intersection
  scenarios

25
Role within IP PReVENT Collision mitigation and
vulnerable road users
26
RequirementsVRUs and Collision Mitigation

• Driving situations
• Imminent collisions
• Pedestrians and VRUs (mostly urban
  scenarios)
• Sensors
• SR radar, camera (day night), scan laser,
  ultrasonic, 3D camera
• Actuator function
• Warning, start inhibit, brakes, reversible
  restraints, active hood bumper, air-bags
  pre-conditioning

27
RequirementsVRUs and Collision Mitigation

• Requirements at IP level Main issues
• Transition from warning to intervention phase
  (inputs from SASPENCE)
• Data fusion, recognition of VRUs
• Link to passive safety
• Testing methods
• New approaches for scene reconstruction at short
  range (UseRCams)

28
The PReVENT partners

• 53 Partners from Industry, Public Authorities,
  Institutes, Universities, Public Private
  Organisations
• 12 OEMs
• DCAG, AUDI, BMW AG, BMW FT GmbH, CRF, FFA, PSA
  Peugeot Citroen, REGIENOV, VTEC, VOLVO CAR, VW
• 17 Suppliers
• BLAUPUNKT, BOSCH, DELPHI, FCS, IBEO, IMITA, LEW,
  NAVIGON
• NAVTECH, PHILIPS, SAGEM, SIEMENS, SIEMENS VDO,
  Signalbau Huber, TELEATLAS, TRW CONEKT, VDO
• 24 Institutes others
• AVV, CERTH/HIT, CIDAUT, CNRS IDFA, ERTICO, fka,
  FHG, FORGIS, FORWISS, ICCS, IMC, INRIA, LCPC,
  LUND, MW, NTUA, TNO, TUC, TRANSVER, TRL, UNI
  HANNOVER, UNIPR, UNISI, UNITN, VTT

29
PReVENT Project data

• Total budget 55 milion
• EU contribution 29.8 milion
• Project duration 02/2004 till 01/2008
• Contact prevent_at_mail.ertico.com
• Website www.prevent-ip.org