C2-SENSEWP4

Organizational Interoperability

Szymon DabrowskiMilan

Main goal is a Organizational interoperability profiles definition.

Organizational interoperability requirements:

Formulation of common procedures is required of emergency partners

Formulation of model organizations is required

Actions:

Modelling business processes & processes and emergency actors definition.

Collaboration inside consortium for exchanging information about emergency domain in their countries.

Results:

Knowledge about Quality of Operation Services & Service Level Agreements in emergency domain

Task 4.1. Aligned Procedures and Operations. PIAP

• We should consider to choose collaborative Business Process Management

Platform.

• Based on State of the Art market analysis we found:

• Promising platforms Alfresco / Activiti

3

Activiti Explorer

• An online tool for creating, visualising and exchanging the procedures

• A repository that is accessible by all the necessary organisations and enables data sharing

• Procedures can be launched and modified by current conditions and time-dependent triggers

• Each organisation can be granted a strictly defined access to the service

• On-line tool for single or multi-user business modeling environment

Activiti (based on Eclipse)

• Advanced procedure management and administration

• Simple XML files are used to import/export the procedures – convenient communication with Activiti Explorer

• Allows to control and modify the procedures created for or supplied by each organisation

MuleSoft Platform

• Fully compatible with Activiti software• Enables easy management of data exchange

protocols (e.g. http requests simulation/modification)

• Creates the possibility of simple translation of almost any data format to the Enterprise Service Bus communication standard

Service Level Agreement• This Aligning Procedures will be supported through Service Level

Agreements negotiation tool service (SLA) which are contracts between service consumers and providers or between two organizations. Agreement on:

the functionalities of the service, quality, permission and security, who can receive what, when and what type of data etc.

Is it a part of Enterprise Service Bus? Or separate software tool? Lutech please consider it.

…Or our Activity Explorer can be treated as a SLA?

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

• Regola: Any progress on theese 2 bullets below? Time is running.

• Harmonized 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.

* Staff effort request was doneTime frame: M9-M24

WP 4 ManagementPartners effort and duration

*

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