1. CAP Implementers Workshop - Geneve, 09-10.12.08 REACT [IST-2005-033607] CAP in the IST project REACT Massimo Cristaldi & Uberto Delprato – IES Solutions srl Marcello Marzoli – Italian Ministry of Interior, Firemen Dept. CAP Implementers Workshop WMO Geneve, 9-10 December 2008 – http://www.react-ist.nethttp://www.react-ist.net

2. – http://www.react-ist.nethttp://www.react-ist.net Current emergency services situation in Europe Fragmentation of Emergency Services Unique 112 (EU 911) -> still far from reality Only some European regions have unified emergency services (i.e. Ambulances and Fire Fighters) Need for interoperability

3. Ambulance C&C1 Fire Brigade C&C1 Police Dept. C&C1 REGION 1 UNCOORDINATED ACTION REGION 2 Ambulance C&C2 Fire Brigades C&C2 FRAGMENTED COMMUNICATION Police Dept C&C2 INTEROPERABILITY ENHANCED COORDINATED Need for interoperability – http://www.react-ist.nethttp://www.react-ist.net Not only for disasters, but usually for small limited incidents that may escalate in scale

4. REACT EU Project funded in 2006, finishing in 2009 7 technical partners from UK, Italy, Belgium, Germany, Slovenia, Austria 3 End Users Focused in: Citizen-to-PSAP interaction PSAP-to-PSAP coordination for incoming calls and incident knowledge Dont focus on resources mgt – http://www.react-ist.nethttp://www.react-ist.net

5. REACT - The mission Reaction to Emergency Alerts using voice and Clustering Technologies Main goals: capture more of the information available from sensors, being them human or technological make this information available to as many local Emergency Call Services as possible, by creating an interoperable European information-structure complement the data with associated services able to semantically analyse and cluster environmental and crisis management information Keeping data transfer secure – http://www.react-ist.nethttp://www.react-ist.net Voice capturing E-Call Interoperability Call grouping

6. Make information available Identification of right information recipient Seamless information sharing among different Emergency Services (ES) –Same ES covering two neighbor Jurisdictions (Police zone A, Police zone B) – Different ES acting on the same zone (Police zone A, Fire Brigades zone A) – http://www.react-ist.nethttp://www.react-ist.net

7. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

8. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

9. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

10. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

11. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

12. Same call seen by different C&C – http://www.react-ist.nethttp://www.react-ist.net C&C1 CNVVF Venezia C&C2 Venezia Ambulance

13. Additional services 1.Call and Incidents content mgt –Semantic Analysis of calls –Call Grouping for a wider view on an event 2.Voice recognition –Capturing keywords (e.g. gun, fire) –Suggesting keywords to the call-taker 3.Automatic translation of local codes into general codes –i.e. using TSO dictionary – http://www.react-ist.nethttp://www.react-ist.net

14. Where we are now Architecture Defined 1 st Round implementation completed 1 st verification round currently happening Interoperability – Achieved Voice recognition – Achieved Call Grouping – Partially achieved Trials will start in February next year – http://www.react-ist.nethttp://www.react-ist.net

15. REACT Architecture Loose coupling between components Uses standard TCP/IP based protocols and links –XML –Web Services –Atom Feeds Common Alerting Protocol as Calls/Incidents Message format TSO as Incident Dictionary – http://www.react-ist.nethttp://www.react-ist.net

16. Conceptual Architecture C&C CAP Adapters Incident API Input Analysis Router – http://www.react-ist.nethttp://www.react-ist.net

17. REACT Sequence Diagram REACTSequenceDiagram.png – http://www.react-ist.nethttp://www.react-ist.net

18. Using a common dictionary CAP alone is generic in classifying incident (cap.alertinfo.category.code) Local codes will be, in any case, sent to recipients in original format (in cap.alertinfo.event.code) For being interoperable across different nations TSO dictionary has been selected in REACT – http://www.react-ist.nethttp://www.react-ist.net

19. CAP/TSO CAP MESSAGE TSO CODED Car acc. + people Cod.10 People trapped Red code – http://www.react-ist.nethttp://www.react-ist.net

20. CAP useful features 1.Message Type –Alert/Update/Cancel/Error 2.Status –Actual/Exercise/Test 3.Urgency –Immediate/Expected/Future/Past/Unknown 4.Severity –Extreme/Severe/Moderate/Minor/Unknown 5.Certainty –Observed/Likely/Possible/Unlikely/Unknown – http://www.react-ist.nethttp://www.react-ist.net

21. Call/taking at a PSAP [CNVVF] – http://www.react-ist.nethttp://www.react-ist.net SO 115 GIS interface

22. CAP representation of an event: Car accident with passengers to be rescued Current CNVVF procedure –Always send resources –Inform other CNVVF HQs by phone (if needed) –Inform other rescue services by phone (if needed) CAP Status = Actual CAP Type = Alert CAP Category = Rescue CAP Urgency = Immediate CAP Severity= Severe CAP Certainty= Likely – http://www.react-ist.nethttp://www.react-ist.net

23. TSO representation of an event: Car accident with passengers to be rescued Current CNVVF description –Code = 10 [Incidente stradale (generico)] –Type = Incidente con persone a bordo –Icon = 10 Event/EType/Category (1st) = CRS (TRP) Event/EType/Category (2nd) = COL (TRP) Event/EType/Category (3rd) = TRP (ASR) Event/EType/Actor (1st) = VEH Event/EType/Actor (2nd) = PPL Event/EType/LocType (1st) = ROAD – http://www.react-ist.nethttp://www.react-ist.net

24. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net C&C2 Treviso Fire C&C1 CNVVF Venezia

25. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net SO115 C&C1 CNVVF Venezia C&C2 Treviso Fire

26. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net SO115 CAP adapter C&C1 CNVVF Venezia C&C2 Treviso Fire

27. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net SO115 CAP adapter C&C1 CNVVF Venezia C&C2 Treviso Fire

28. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net SO115 CAP adapterCAP parser C&C1 CNVVF Venezia C&C2 Treviso Fire

29. Interoperability btw Firemen in Italy – http://www.react-ist.nethttp://www.react-ist.net SO115 CAP adapter SO115 CAP parser C&C1 CNVVF Venezia C&C2 Treviso Fire

30. Pilots of the REACT project 1.Italy – FB PSAP, Venice district –Geographic integration –Link with Ambulance service 2.UK – Police PSAP, Sussex –Geographic integration 3.Germany – FB Aachen –EuRegio Maas-Rhein –Multilingual service –Geographic integration – http://www.react-ist.nethttp://www.react-ist.net

31. How can a C&C become interoperable with other C&Cs? Identify who they need to interoperate with Agree on a common dictionary or adopt an established dictionary (i.e. TSO) Match their local codes against an this dictionary Adapt their C&C to generate and receive CAP messages Adapt their C&C to process and display the received messages – http://www.react-ist.nethttp://www.react-ist.net

32. PSC Europe Forum Technical Meeting- Valabre, 01.12.08 Identify who you need to interoperate with Contact REACT Adapt your C&C to generate and receive CAP messages Adapt your C&C to process and display the received messages – http://www.react-ist.nethttp://www.react-ist.net How ITALIAN FB became interoperable with other C&Cs C&Cs from other provinces + Ambulance servicesWorked with the REACT partners SO115 adapted to generate and receive CAP messages [2 months] SO115 to process and display CAP messages on GIS [4 months]

33. CAP adopted by Italian Firemen Corps The Italian Ministry of the Interior has issued a formal decree concerning the sharing of data between the fire department and other emergency organisations, such as the ambulance service. The decree – published in the governments Official Journal of 3 July – defines the communication protocols for exchanging data and information between emergency service command and control rooms. This is the first time in Italy that an emergency organisation will open its databases to other similar organisations, providing they adopt the communication protocol which has been defined and developed within the REACT project. – http://www.react-ist.nethttp://www.react-ist.net

34. – http://www.react-ist.nethttp://www.react-ist.net

35. What Italian FB got having REACT working – http://www.react-ist.nethttp://www.react-ist.net C&C2 Treviso Fire SO115 C&C1 Venezia Fire C&C3 Venezia Ambulance Beta80

36. What is available but not deployed yet – http://www.react-ist.nethttp://www.react-ist.net CAP Generator CAP Viewer

37. What Italian Firemen will additionally get in 2009 – http://www.react-ist.nethttp://www.react-ist.net C&C1 Venezia Fire C&C3 Venezia Ambulance C&C Venezia Local Police C&C Envir. Agencies C&C Civil Protecion

38. An example of an unexpected application in Italy Although 112 is an emergency number, each emergency agency can be reached with different numbers (113, 115, 118) Caller not speaking Italian are often managed with problems With REACT in place, keywords may help......but it is possible to forward the call to another call-taker who can gather information in the caller language and make them instantly available to the local call-taker – http://www.react-ist.nethttp://www.react-ist.net

39. Lessons learnt 1.Legacy systems –Call-takers want to keep their current MMI –Adaptations should have a limited impact 2.CAP coding vs. current codes –Not trivial: time is needed to get it done properly –Flexibility vs. procedures: no code can fully represent reality 3.Representation with the TSO dictionary –Not straightforward -> many categories are insufficiently developed yet –Time-consuming task 4.Availability of testing tools –A functional demo is much better than a powerpoint –Many local users do not have a call management tool available 5.Being a standard is king! – http://www.react-ist.nethttp://www.react-ist.net

40. Conclusions Integrated use of both CAP and TSO as enhanced protocol for representing and sharing information about events Adopted by Fire Brigades in Italy Issues: –Make current C&C Systems CAP compliant –Define CAP message content –Agree on a common data dictionary: i.e. TSO is a bit primitive for Police officers Demonstrate the interest of the solution: at the end, from end user perspective, is just a dot on a screen that pops up… How to perceive the value? Trials in Venezia / Aachen / UK aims at demonstrating the concept Open issues: usage of some CAP fields –cap1091.xml – http://www.react-ist.nethttp://www.react-ist.net

41. Thank you very much for your time Massimo Cristaldi & Uberto Delprato IES Solutions Roma - Italy u.delprato@i4es.it www.react-ist.net See you at the stand – http://www.react-ist.nethttp://www.react-ist.net