1. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads” Mr. Matti Kutila, Mr. Jukka Laitinen and Mr. Harri Koskinen VTT (Finland) firstname.surname@vtt.fi WP2.3 LEADER SAFESPOTSAFESPOT

2. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 2 CONTRIBUTION OVERVIEW CAMERA VISION SYSTEMS AND LASER SCANNERS –VTT, LCPC, IBEO RFID AND MAGNET STRIPES –LCPC, BME SENSOR NETWORKS –MIZAR, ISMB, CRF, VTT, LCPC DATA FUSION –PTV AG, CSST, CRF, NAVTEQ, IBEO, PTV AG, VTT, CIDAUT, CSST, SODIT, TUM LOCAL DYNAMIC MAPS –TA, CIDAUT, NAVTEQ METHODOLOGIES –CERTH, MIZAR, NAVTEQ, TUM IN-VEHICLE EQUIPMENT AND COMMUNICATION –CRF, MIZAR, VTT ROAD SIDE ALERTING SYSTEMS –CERTH, MIZAR, VTT, TUM

3. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 3 T2.3.1 ROADSIDE SENSORS LEADER: BME (9,0), Budapest University of Technology and Economics OTHER PARTNERS: VTT (2,0), IBEO (1,0), MIZAR (2,4), LCPC (2,0), ISMB (1,0), TA (2,0) The road side sensors: types and characteristics –The investigation of new low cost detection technologies –Further revision of the sensor survey in WP2.2 New approaches to and improvements of traditional incident detection systems –Innovative utilisation of currently installed devices will be carried out The basic road side elements to be used in the infrastructure test bed and field trials

4. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 4 T2.3.2 DETECTION ALGORITHMS LEADER: CSST (3,0), CENTRO STUDI SUI SISTEMI DI TRASPORTO OTHER PARTNERS: VTT (1,0), MIZAR (2,4), CERTH (1,7), CRF (2,0), TUM (6,0), CIDAUT (2,5), PTVAG (2,0) New algorithms for safety related condition estimations Process the data from non homogeneous sources (including. moving vehicles, different types of roadside sensor, etc) –Prioritisation of available data sources, –Data filtering (contradictory information handling) –Data management Specify the format of output data

5. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 5 T2.3.3. DATA FUSION LEADER, NAVTEQ (6,0), NAVTEQ Europe B.V. OTHER PARTNERS: MIZAR (2,4), CERTH (1,7), IBEO (1,0), CRF (4,0), CSST (3,0), TUM (6,0), CIDAUT (2,5), PTVAG (2,0), SODIT (3,0) Methods and algorithms for validating and fusing the incident related data collected from various and non-homogenous sources –Generate local dynamic traffic situation maps in combined co- ordination from information received from different sources –Data fusion specifications include algorithms for local dynamic maps and event detection

6. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 6 T2.3.4 ROAD SIDE ACTUATION EQUIPMENT LEADER: TUM (6,0), Technische Universitaet Muenchen OTHER PARTNERS: VTT (2,0), MIZAR (2,4), CERTH (1,7) The actuating elements of a distributed network of road side nodes –Investigation of local warning/guidance/control actions –Sensor networks –Communication methods –Further revision of the D2.2.2 exploration The basic road side elements to be used in the infrastructure test bed and field trials

7. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 7 T2.3.5 HARMONISATION AND COMPATIBILITY LEADER: CRF (2,0), Centro Ricerche Fiat S.c.p.A. OTHER PARTNERS: MIZAR (2,4) The data interface between applications and road side detection systems Ensure the compatibility of the specifications with –The traffic control strategies –The Core Architecture (SP7) –Autonomous on-board vehicle systems (SP1) Done parallel with the specification work

8. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 8 MILESTONES AND DELIVERABLES Deliverables: –D2.3.1 Interim report of specifications at M12 (Jan 2007) –D2.3.2 Final report of specifications at M18 (Jul 2007) (BME will lead the deliverable preparation with strong support of all the partners contributing to the WP2.3) Milestones: –M2.3.1 Interim specifications for infrastructure-based components at M12 (Jan 2007) –M2.3.2 Completion of specifications for infrastructure-based components at M18 (Jul 2007)

9. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 9 INPUT FROM WP2.2 User needs, non-functional and functional requirements for the infrastructure based sensing Scenarios of safety-critical events, conditions and behaviour on a road Ideas for technique to detect safety-critical objects or events Requirements for the components of the INFRASENS systems Sensor survey results (state-of-art and innovative prospects) Proposition for the actuating devices Usage of the dynamic local maps

10. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 10 RESULTS FOR WP2.4 Definition of the test bed for roadside detection techniques Specification for implementation of the road-side sensors Specifications for the detection algorithms Suggestion for data fusion methodologies Determination of the road-actuating equipment for applying warnings and interaction with the road users Definition of the common communication methodology with the core architecture (SP7) and the on-board vehicle systems (SP1) More expectations from the WP2.4 leader?

11. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 11 FIRST STEPS TOWARDS WP2.3 Initiate the review of the requirements determined by D2.2.1 and D2.2.2 (T2.3.1) Determine the methodology for specifying the detection and data fusion algorithms (UML, is there common methodology for whole IP?) (T2.3.2 and T2.3.3) Check from D2.2.1 and D2.2.2 the envisioned actuating techniques (T2.3.4) Review the requirements of SP1 and SP7 (T2.3.5) One day WP2.3 workshop in begin of September –Option 1: parallel with some official IP/SP meeting, if there is any? –Option 2: meeting in Tampere (or in Brussels) –Option 3: A video conference (saves the travelling expenditures) –Should be decided before August

12. SAFESPOT Project, SP2 PARTNERS PROGRESS MEETING 12th July 2006, Cofiroute, Paris 12 TIME PLAN M6-M18 (Aug 06-Jul 07) Leader AprApr MayMay JunJun JulJul AugAug SepSep OctOct NovNov DecDec JanJan FebFeb MarMar AprApr MayMay JunJun JulJul Select the task leadersVTT Revise the task resourcesVTT Organise a workshop (Finland, Brussels, video conference)VTT Short task planTask leaders Review the requirements determined by D2.2.1 and D2.2.2 (Tasks 2.3.1 and 2.3.4)BME, TUM Methodology for specifications (T2.3.2 and T2.3.3) CSST, NAVTEQ Review the requirements of SP1 and SP7 (T2.3.5)CRF Specify the innovative ways of using road side sensors (T2.3.1)BME Specify the detection algorithms and their interfaces (T2.3.2)CSST Specification for data fusion with using local dynamic maps (T2.3.3)NAVTEQ Specify new sensor technologies (e.g. sensor networks) (T2.3.4)TUM Ensure harmonisation and compatibility with the other SPs (T2.3.5)CRF D2.3.1 Interim report of specifications, M12BME D2.3.2 Final report of specifications, M18BME