Intelligence for Environment and Security – IES Solutions CAP in PSAP interoperability 2 European...

Intelligence for Environment and Security – IES Solutions http://www.iessolutions.eu

CAP in PSAP interoperability

2 European experiences

Massimo Cristaldi, CTO IES Solutions

[email protected]


Presentation outline

• AGENDA– How we use the CAP – 2 European Examples

• The Italian Fire Fighters• The EU Project IDIRA

– Lessons Learnt

• Focus on Challenges and Actions to convince PSAP to adopt CAP


IES Solutions

• VASP in Security and Enviroment• Advisory Board member of the European

Emergency Number Association http://EENA.org • Member of the Public Safety Communication

Europe forum http://www.psc-europe.eu/ • Works in EU Projects on Emergency

Management – www.iessolutions.eu • Creator of JIXEL, the first Web 2.0 Joint

Command and control center – www.jixel.eu


EDXL-CAP use in EU

• Not only for “Last mile” citizen notifications– Some experiences after L’Aquila Earthquake

• But, mainly, for PSAP-to-PSAP interoperability

• HOW TO DISTRIBUTE CAP Messages:– FUTURE: Bundled in SIP (following NG112

Long Term Specs) – VOICE&DATA– TODAY: Delivered in ATOM feeds for DATA

only Interop – DATA ONLY


FUTURE - The EENA NG112 LT Definition• http://www.eena.org/view/en/Media/press/press_2013/NG112-

march2013.html • Objective:

– Communication between citizens and emergency services: NG112 is designed to enable citizens to reach an authority (e.g., PSAP) by calls using VoIP, text messaging, real-time text, pictures and video.

– Interoperability between emergency services: NG112 enables several PSAPs to be part of a common emergency services IP network

– Open Standards approach: NG112 is based on Internet Protocol (IP)-network based standard interfaces between all forms of communications components

• Existing experience from other regions (e.g. NENA)


CAP in SIP

• The MESSAGE method, an extension to SIP, allows the transfer of Instant Messages and is also used to carry a Common Alerting Protocol (CAP) message.

• Still a long term definition, no real implementations


TODAY – “per PSAP” Atom Feeds

• Loose coupling btw components

• HTTP based

• 1 personalized feed for each “interoperability partner”

• http://CAPfeed/SENDER/RECIPIENT_1

• http://CAPfeed/SENDER/RECIPIENT_2


3 STEPS

1. INCIDENT CREATION (or updates)– C&C publishes CAP Messages OR message are

created by a “CAP Generator”, i.e. a web app or a smartphone app

2. INFORMATION DISTRIBUTION– The Addresses of intended recipients are

analyzed and publishes as protected, personalized CAP feeds (SENDER/RECIPIENTS)

3. INFORMATION VISUALIZATION– C&C read the feed OR the feeds are read by a “CAP

viewer” or a Feed reader/Browser


The Italian CAP experience

• Ministry of the Interior – Department of Fire Brigades:– Management of all incidents with 110 control

rooms distributed all over Italy– Unique body (>31.000 professional fire

fighters+ >6.000 volunteers)– Main Body in the Italian Civil Protection

mechanism


Italian Experience timeline• 17 June 2008 1st: DECREE

– CAP as interoperability standard

• 2009 Used after L’Aquila Earthquake

• 2010-2011 – Used for Calabria Fire seasons

• 23 May 2011 2nd DECREE – Definition of the Italian CAP Profile

• 2012 - Adaptation of Italian Fire Brigades C&C (SO115)

• 2013 - The ROME Trial

• End of this year: deployed in ITALY completed

• First planned region with 25 Interop Partners: VENETO

• All this means AGREEMENT btw Fire Brigades and other PSAPs


Key facts on the Italian Profile

• Carrying also “normal” incidents, not only major events

• Use of the Tactical Situation Object as Data Dictionary

• Use of the SAME codes allowed

• Gives brief information about RESOURCES

• Distinction btw CALLS and INCIDENTS

• Keeping track of the incident progress


Italian Profile: More then Just CAP specific stuff

• New CAP parametric fields but also:– rules for updating incidents, and for modifying

messages generated by other organizations– rules for representing incidents categories using

universal and standard codes (TSO and SAME) inside the CAP message

– rules to link resources to a given incident, by inserting information about mobilized resources inside the CAP message

• Definition of ATOM feeds as standard for CAP distribution and format for ATOM feeds


Italian CAP Profile – Cross references

<alert xmlns="urn:oasis:names:tc:emergency:cap:1.2">

<identifier>20130411-I-10029-6</identifier>

<sender>[email protected]</sender>

<sent>2013-04-11T00:30:32+02:00</sent>

<status>Actual</status>

<msgType>Update</msgType>

<source>SFRVCN*******1T</source>

<scope>Private</scope>

<addresses>[email protected] [email protected]</addresses>

<code>CAP-IT-VF:0.1</code>

<references>[email protected],20130411-I-10029-5,2013-04-11T00:20:11+02:00</references>

<incidents>[email protected],20130411-C-1-0,2013-04-11T00:08:01+02:00</incidents>

………….

Identifies the profile

Identifies the profile

Identifies the parent message of the current thread (for

messages updates by different orgs)

Identifies the parent message of the current thread (for

messages updates by different orgs)


Italian CAP Profile – Categories……………………

<info>

<language>it-IT</language>

<category>Infra</category>

<event>Fuga gas</event>

<urgency>Unknown</urgency>

<severity>Unknown</severity>

<certainty>Unknown</certainty>

<eventCode><valueName>Code_L1</valueName>

<value>Fuga gas</value></eventCode>

<eventCode><valueName>Code_L2</valueName>

<value>Fuga Gas in appartamento</value></eventCode>

<eventCode><valueName>TSO-ETYPE-CATEGORY</valueName>

<value>POL</value></eventCode>

……………………

Incident code and sub-code (VVF coding)

Incident code and sub-code (VVF coding)

TSO category code

TSO category code


Italian CAP Profile – Parameters……………………

<parameter><valueName>INCIDENTPROGRESS</valueName>

<value>CLOSED</value></parameter>

<parameter><valueName>TIMEARR</valueName>

<value>2013-04-11T00:20:00+02:00</value></parameter>

<parameter><valueName>TIMECANC</valueName>

<value>2013-04-11T00:30:32+02:00</value></parameter>

<parameter><valueName>VEHICLES</valueName>

<value>3/A,APS,2013-04-11T00:11:00+02:00,2013-04-11T00:20:00+02:00,2013-04-11T00:30:00+02:00</value></parameter>

<area>

<areaDesc>Via Pietro Ottoboni, 12 00100 Roma, Italy</areaDesc>

<circle>41.90804416,12.53977850 0.01</circle>

</area>

</info>

</alert>

Link information about resources to

the incident

Link information about resources to

the incident


Physical Deployment in Italy


2013 - ROME LIVE Screenshot


THE EU PROJECT IDIRA


IDIRA Facts and objectives• Integrated project funded by the EU in the FP7 framework

programme– 11 million funding 4 years duration (now @1,5 years)– 18 partners from Germany, Italy, Greece, Austria, UK,

Switzerland– Project coordination Fraunhofer IVI (DE)– Technical coordination IES Solutions (ITALY)

• IDIRA stands for “Interoperability of data and procedures in large-scale multinational disaster response actions”

• AIM: provide guidelines and software services for improving cooperation, coordination and data sharing during big emergencies management

• www.idira.eu


How it is used – the MICS (Physical view)• MICS (Mobile

Integrated Command and Control Structure)– information hub, to

collect information from disparate data sources during both the pre-incident and the incident response phases

– on site information space and cooperating platform to facilitate and improve effectiveness of response actions “on the field”


Interoperability and standards: not only CAP


IDIRA

• The new developed modules will become part of the EU Civil Protections mechanism

• EDXL family of standard will be largely used

• End users (German and Austrian Red Cross, Italian Fire Brigades) pushes for the adoption of OPEN standard


Challenges with PSAPs (our experience)

• Why interoperate?– The Dog and the Tail

• How to convince that there is a need?– Show something REAL– Convince that it is possible– Disseminate and educate

http://jixel.eu/adotta_standard_cap.php?lang=EN

• Social media trend opens to Internet• Keep impact low on what is today existing


The online PREZI on www.jixel.eu


10 ACTIONS

1. Learn Some Basics about CAP

2. USE CAP Sources

3. Considering Tools to convert inputs into CAP

4. Acquiring CAP Mapping tools

5. Implementing a CAP Source Alert

6. Publish a CAP Alert news feed

7. Registering an Alerting Authority

8. Choose and Internet host for CAP

9. Consider other interfaces for CAP dissemination

10.Developing public outreach and education


THANK [email protected] // +39-348-2816167

Intelligence for Environment and Security – IES Solutions CAP in PSAP interoperability 2 European...

Documents

Transcript of Intelligence for Environment and Security – IES Solutions CAP in PSAP interoperability 2 European...