SAGEM RTD Activities C2-Sense project Paris – 20 & 21 January 2015

1. SAGEM RTD Activities C2-Sense project Paris – 20 & 21 January 2015

2. SAGEM : RTD Activity in the Project • WP3 – Technical & Semantic Interoperability • Partners : Sagem (leader), AIT, Innova Puglia, Lutech, PIAP, Regola, SRDC • Objectives • Develop the profiles and SW components concerning technical interoperability layers • Covering the physical, protocol, Data/Object model, Information and Knowledge layers • Planning • All Tasks beginning at T0+8 (01/12/2014) , ending at T0+24 (01/04/2016) • Inputs • D2.2 – user & technical requirements of the C2-Sense architecture • D2.3 – Conceptual design of the C2-Sense architecture • D7.1 – Requirement specifications and scenario of the pilot applications • D7.2 draft – Design of the implementation of the pilot application Scenario (M16) • D5.1 draft – Integrated Emergency Profiles (M30)

3. WP3 tasks • Task 3.1 - Physical Interoperability • Partners : PIAP (leader) , Innova Puglia and REGOLA • Objectives : • managing the physical connections between the networked applications and devices • Profiles will be developed based on the SECRICOM Project results up to “IP Packets Layer” • developing an IP based gateway (by PIAP and REGOLA) to enable the exchange of data using prominent wired and wireless communication mediums in emergency domain. • Output: • D3.1 – “Physical interoperability Profiles and IP based Gateway” • Lead : PIAP – due at T0+24 (31 mars 2016) • HW/SW: Physical interoperability Profiles and IP based Gateway

4. WP3 tasks • Task 3.2 - Protocol Interoperability • Partners : LUTECH (leader), SAGEM, AIT • Objectives : • to achieve the protocol interoperability of emergency applications/systems and sensors addressing the transport level protocols such as TCP/IP, HTTP, SOAP, REST or SMTP and using Web service protocols for this layer • The detailed Operational and Core Web Service categories will be identified under the supervision of SAGEM, and the abstract definition of these services will be developed. Their interface schemas describing inputs/outputs in detail will be defined in Task 3.3 and the services will be implemented in Task 3.4. • After that, profiles will be developed and based on these profiles corresponding Protocol Adapters will be implemented. • These protocol adapters will be used to access emergency applications/systems and sensors in the C2-SENSE architecture through Web Service protocols. • There will be two types of Protocol Adapters: (1) Sensor Protocol Adapters (to be developed by AIT) and (2) Emergency Applications/Systems Protocol Adapters (to be developed by SAGEM). • Furthermore, the communication among the components and services of the C2-SENSE Architecture will be based on an Enterprise Service Bus (ESB) which will be developed by LUTECH. • Output: • D3.2 – “Protocol interoperability Profiles and communication adapters” • Lead : LUTECH – due at T0+24 (31 mars 2016) • SW: applications’ adapters, ESB, protocol adapters

5. WP3 tasks • Task 3.3 – Data /object model interoperability • Partners : Sagem (leader) and SRDC • Objectives : • Data/Object Model Interoperability Layer involved using the relevant content standards. • The interfaces (and profiles) of the Operational Web Services identified in Task 3.2 will be developed. • The “Web Service Creator” tool will be developed by SAGEM. A Web Service Creator exposes the functionality of legacy systems as Web services based on the identified profile and by creating all the necessary code. • This task covers the development of necessary Web service based Data/Object Model Interoperability Profiles, the implementation of Web Service Creator Tool and Data Integrators. • Output: • D3.3 – “Data/Object Model interoperability Profiles and data Integrators, and WS Creator tool” • Lead : Sagem – due at T0+24 (31 mars 2016) • SW: WSCT, Data model, Data Integrators

6. WP3 tasks • Task 3.4 – Information Interoperability • Partners : SRDC (leader) , Lutech and Sagem • Objectives : • Information Interoperability layer is about mapping dynamic information to each other. • C2-SENSE will expose the functionality of emergency applications as Web services with standard interfaces, • C2-SENSE will use the approach developed in the “OASIS Semantic Support for Electronic Business Document Interoperability (SET) TC ” which highlights the semantics of different but overlapping electronic business document standards as ontologies and then provide semantic mediation among these ontologies. • The business and operational properties of services will be described through the Universal Service Description Language (USDL) • In this task, related Information Interoperability Profiles will be developed and semantic interoperability suite will be developed. • Output: • D3.4 – “Information interoperability Profiles and Semantic interoperability Suite” • Lead : SRDC – due at T0+24 (31 mars 2016) • SW: Semantic mediator / semantic interoperability suite

7. WP3 tasks • Task 3.5 – Knowledge Interoperability • Partners : AIT (leader), PIAP, SRDC • Objectives : • Knowledge layer is about having a common operational picture of the crises situation and the support of collaboration for joint decision making. • An Emergency Profile Definition Language (EPDL) will be developed by the technical partners of the C2-SENSE under the supervision of AIT. • Knowledge Interoperability Profiles will be developed and following tools will be implemented: • Collaboration Environment, Emergency Maps Tool, Sensor Management Tool : AIT • Messaging/Communication Platform: LUTECH • Registry of Emergency Web Services: PIAP • Profile Monitoring Tool, Profile Definition Tool, Security and Privacy Tool : SRDC • Profile Repository: PIAP • GIS Server: AIT • Output: • D3.5 – “Knowledge interoperability Profiles and Collaboration environment” • Lead : AIT – due at T0+24 (31 mars 2016) • SW: EPDL, tools listed above

8. WP3 Delivrables & milestones • Milestone(s) • MS3 : C2-Sense individual components and interoperability profiles • Leader : SAGEM • Delivery : 31/03/16 (T0+24) • Verified by : D3.1, D3.2, D3.3, D3.4, D3.5 (and D4.1, D4.2) • WP3 Delivrables

9. Synthesis of WP3 • Risks and Highlight points • End-users requirements w.r.t. global system use cases • Internal interfaces definitions / existing technologies selection • Final demonstration scenario • Others … ??