C2-SENSET.3.5 & WP4

Organizational Interoperability

Ankara

T.3.5. Knowledge Layer components under PIAP responsibility

• Registry of Emergency Web Services (part of Collaborative Environment)– provides availability of web services, which were created from the emergency application and enables their discovery and reuse. Communication with Web Service Creator Tool.

• Emergency Interoperability Profile Repository (EMPR)– Profiles database and Content Management System

Both Repositories should provide flawless communication with Enterprise Service Bus (Apache Kafka)

To allow flexible communication and achieve process coherence between EMPR, Collaborative Environment and Aligned Procedure Layer - one platform for Process Management is needed (processing, storage, remote access).

Investigation done on Process Management platform by Alfresco (http://www.alfresco.com/solutions/process-management ), which is used by Amsterdam Fire Brigade to access profiles and tactical information. 200 mobile operatives can remotely access and update the fire department’s fire prevention and risk management database.

Partners (36 PM): SAGEM (2), LUTECH (7), AIT (4)IP (2)PIAP (12)Regola (9)

Time frame: M9-M24

WP 4 Partners effort and duration

Main goal is a Organizational interoperability profiles definition and necessary tools development.

Organizational interoperability deals with:

Quality of Operation Services

Mission or business objectives – Desicion Making Proccess, Mission Planning

Business goals definition

Modelling business processes and emergency actors. Create a common procedure.

Aligning information architectures with organizational goals

Collaboration of administrations for exchanging information purposes.

…emergency partners should be familiar with each other’s processes and can align their operations!!

4.1Aligned Procedures, Aligned Operations,4.2Harmonized Strategy Doctrines and High Level Objectives

Task 4.1. Aligned Procedures and Operations. PIAP

• In this task generic C2-SENSE profiles (conventional - not specific to a country and organization) will be customized to specific organizations and specific incidents by considering the existing procedures and operations of the organizations involved.

• This harmonization will be supported through Service Level Agreements negotiation tool service (SLA) which are formal contracts between service consumers and providers.

6

Following components will be developed :

PEE Profile Execution Enegine (Lutech - part of ESB)

PDST - Profile Definition and Specialization Tool (SRDC?)

MGT - Mapping Generator Tool (?)

Should PIAP provide collaborative environment for these 3 components? Or these will be done by ESB and/or choosen Business Process Management Platform?

Profile Execution Engine (top of the ESB) – possible software: Activiti BPM Platform

PEE executes the profiles specialized for specific organizations and incidents

Emergency Profiler Subsystem uploads an existing emergency profile or creates a new one.

Is the Emergency Profile Manager a Registry of Emergency Web Services?

Process Subsystem starts a new or existing process

Profile Definition and Specialization Tool

Graphical user interface (GUI) to define the profiles as an ad hoc workflow describing the order of tasks that emergency staff should realize

- Profile Definition Subsystem: This subsystem is responsible for providing necessary mechanism for Domain Expert to define new profile.

- Profile Specialization Subsystem: This subsystem is responsible for customizing the generic profiles to specific organizations and incidents

Mapping Generator Tool

Mapping Generator Tool enables local systems to map their local domain ontology to C2-SENSE Harmonized Ontology so that they are able to communicate with each other.

Mapping Generator Subsystem: This subsystem is responsible for defining mapping rules between local domain ontology and C2-SENSE Harmonized Ontology

Converter Engine Subsystem: This subsystem is responsible for converting a local content model to another according to the predefined mapping rules

Task 4.2. Harmonized Strategy Doctrines and High Level Objectives. Regola

• Harmonised Strategy/Doctrines layer involves aligning the cultural and social backgrounds of the emergency partners.

• During the development of these layers the complementarity will be ensured with the 'Framework Programme on Security and Safeguarding Liberties' (SSL), which focuses on actions related to policy and operational work.

List of deliverables:

4.1 Aligned Procedures/ Operations Profiles and Profile Specialization and Execution Tools (PIAP)

4.2. Harmonized Strategy Doctrines and High Level Objectives Profiles (Regola)

Should be ready before 24 month

Conclusions:

Shared common procedure model is required

Form of model organizations is required

Flexible interfacing with other components needed

NOT CLEAR WORK BREAKDOWN STRUCTURE

Next 2 weeks decision about software platforms and definition (in terms of possible software to be developed) of main components