Deliverable D1. 10 Annual Report Final version · 2017-06-16 · D1.10 Annual Report Version 1.0 Date 12.06.2017 Document History This project has received funding from the European

D1.10

Annual Report

Version 1.0

Date 12.06.2017

This project has received funding from the European Union’s Seventh Framework Programme

for research, technological development and demonstration under grant agreement no 607821. 1/59

Authors Name Organization/Unit

Main Author E. Francioni e-GEOS

Contributing Author(s) All All

Approval Name Organization/Unit

Technical Reviewer Tom Flynn SAADIAN

Language Reviewer Tom Flynn SAADIAN

File SECTOR_D1.10_v1.0

Project

Project Reference: Grant agreement no. 607821.

Project Short Name: SECTOR

Call: FP7-SEC-2013-1

Funding Scheme: Collaborative Project CP-FP

Project web-site: http://www.fp7-sector.eu/

Deliverable D1.10

Annual Report

Final version

Document

Deliverable No.: 1.10 Due Date: 2017-06-30

Issued by Partner: e-GEOS Actual Date: 12.06.2017

WP/Task: WP1/T1.1 Pages: 59

Confidentiality Status: PU

http://www.fp7-sector.eu/

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Document History

Table 1 Document history

Document

information Chapters

affected

Description of

change Author

Document

Status Data Version

170510 0.01 The whole

document

ToC E. Francioni 0.01 draft

170515 0.02 Executive

summary, §1, 2

Contributions E. Francioni 0.02 draft

170522 0.03 §2.1 Contribution to

T1.3

F. Tunçer 0.03 draft

170526 0.04 §2.1, 2.5, 2.6 Contribution to

T1.4, WP5, T6.3

M. Fiorini 0.04 draft


T5.3

M. Fiorentino 0.05 draft


T3.3

F. Perez 0.06 draft

170531 0.07 §2.8 WP8 M. Oles 0.07 draft

170601 0.08 §2.6 WP6 M. Cinque 0.08 draft

170601 0.09 §2.1, 2.2 T1.4, WP2 S. Frings 0.09 draft

170602 0.10 All Conclusion and

minor reviews and

changes

E. Francioni 0.10 draft

170605 0.11 All Review T. Flynn 0.11 to

close

170612 1.0 All Review E. Francioni V1.0 Final

Document Reviews

The following table gives an overview of all document reviews.

Table 2 Document reviews

Date Version

reviewed

Remarks,

Corrections Reviewer New Status

170605 0.11 Editorial

changes made

SAADIAN Ready for

approval.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



across the

project.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Table of Content

Executive Summary 5

Definitions, Acronyms and Abbreviations 6

List of tables 6

List of figures 6

1 Introduction 7

1.1 Document Scope 7

1.2 Deliverable Description 7

1.3 Aims and Objectives 7

1.4 Project Consortium 8

1.5 Work Progress and Key Achievements to Date 8

1.6 Project Activities organisation 9

2 Project objectives, work progress and achievements, project management 12

2.1 WP1: Project Management 12

2.2 WP2: Pan-European inventory of past critical events, collaboration processes, data sets and IT support 30

2.3 WP3: Scenario definition and user requirements for the pan-European Common Information Space 30

2.4 WP4: Common Information Space definition and design 33

2.5 WP5: Common Information Space building 35

2.6 WP6: Common Information Space concept demonstration and validation 40

2.7 WP7: Ethical and societal impact assessment 47

2.8 WP8: Standardisation, exploitation and dissemination 50

3 Conclusion 56

References and Applicable document 57

ANNEXI - Monitoring Participant Forms 59

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Executive Summary

This document is aimed at reporting about the technical and management activities

performed during the third and final year of the SECTOR project (M25-M36).

It describes the technical work progress carried out by the Consortium accomplished

in each WPs already started, and the Project Management activities.

The following main facts characterize the final year of the project:

- finalization of all development and integration activities and therefore, the

availability of the SECTOR CIS (MS5 - CIS prototype built);

- a successful Final Demonstration Event, in April 2017, in Rome, when the

system has been presented to a wide audience, simulating an operational

scenario (MD6 - CIS tested and demonstrated);

- a very positive Final Dissemination day, in May 2017 and implemented as an

integral part of the 7th Workshop of the Community of Users;

- two successful Project Reviews (Second annual Review in September 2016,

and Second Interim Review in February 2017): all achievements of the

second-year activities were presented and first demonstrations of the solution

under development were presented.

Another important result achieved during the third year is the complete recovery of all

the delays occurred in the previous years: i.e. recovery and action plans were

prepared, applied and refined during the second part of the project life, leading to a

successful and on time closure of the project itself.

The document includes the following sections:

1) a short summary of the Project objectives;

2) a description of project objectives, work progress and achievements for each

work package, project management, and status of deliverables and

milestones;

3) Annex I: reporting the activities performed and the effort spent by the Project

partners.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Definitions, Acronyms and Abbreviations

DB Exploitation and Dissemination Board

DoW Description of Work

DPA Data Protection Authority

EC European Commission

EUB External Users Board

FP7 Framework Programme 7

GA Grant Agreement

GB Governance Board

ICTB ICT Board

PM Project Manager

PSC Project Steering Committee

QM Quality Manager

SECTOR

Secure European Common InformaTion Space for the InterOperability

of First Responders and Police Authorities

WBS Work Breakdown Structure

WP Work Package

WPL Work Package Leader

List of tables

Table 1 Document history ........................................................................................... 2

Table 2 Document reviews ......................................................................................... 2

Table 3 Work Packages timeline as proposed in D1.6 – Annex II .............................. 9

Table 4 Deliverable submitted in the reporting period .............................................. 13

Table 5 Risk register ................................................................................................. 18

List of figures

Figure 1 – New project Gantt .................................................................................... 11

Figure 2 - Members of CEN/TC 391 with SECTOR members .................................. 53

D1.10

Annual Report

Version 1.0

Date 12.06.2017



1 Introduction

In line with the Description of Work (DoW), this deliverable presents the technical

achievements and the financial details for the third and last year of the project. This

chapter provides a general overview of the project presented in terms of aims and

consortium.

1.1 Document Scope

This document is aimed at reporting on the technical and management activities

performed during the third year of the SECTOR Project (M25-M36). The document

describes the technical work progress carried out by the Consortium accomplished in

each WPs already started, and the Project management activities.

1.2 Deliverable Description

This deliverable provides an overview of the work performed during the period 1st

July 2016 to 30th June December 2017. It is important to note that:

with the Dissemination event (17th May 2017) all activities have been closed,

with the only exception of the preparation of pending deliverables and Final

Review organization;

Final Review has been planned within the project life (21st June 2017),

therefore a general description of activities performed during the last month is

reported. An update of this deliverable will be produced in case of main

changes to the expected activities.

The document provides the following information:

a description of work performed and achievements for each work package

(including project management) within the reporting period, the status of

deliverables and milestones, issues and deviations encountered, including

corrective actions;

Annex I, reporting information about project expenditure for each partner, for

each WP and type of cost. The financial information is based on estimated

costs, the official values are reported into the Form C and related explanations

of the use of resources submitted on ECAS Portal.

1.3 Aims and Objectives

The aims and objectives of the project are outlined as follows.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



The project original idea derives from one of the greatest challenges of the 21st

century: the management of crisis on global and local scale. The ever-growing

human, economic and environmental losses due to natural and man-made disasters

evidence the need for a systematic approach to the management of crisis. A multi-

disciplinary understanding and disaster risk management is required. In such

situations, Collaborative Crisis Management (CCM) is usually coordinated by local

authorities or dedicated civil protection organizations. Moreover, they are usually

supported by a variety of different national and international crisis management

organizations, all of them acting relatively autonomously. The process is typically

coordinated through periodic physical meetings of the involved organizations, in

which information is shared about the situation, priorities are set and responsibilities

allocated. Follow-up and execution of tasks is managed by each individual

organization, typically supported by a range of not interoperable information

management tools, depending on the level of informatization of the local or national

crisis management systems (DoW).

SECTOR aims at establishing the foundations of future Common CCM Information

Spaces by expanding the European scientific knowledge base on (cross-border)

multi-agency CCM processes and the complications these imply when aiming at

setting-up and design cross-border supporting information Systems.

1.4 Project Consortium

As well known, the SECTOR project is being taken forward by a European

consortium of 16 partners from 10 different European Countries, including:

large industry: LEONARDO, THALES, EGEOS, ASELSAN

top-academia: USTUTT, CINI, UPVLC, FOI

a research center on ethical and social issues: IZEW

high-tech SMEs: ITTI, SAADIAN

end-user crisis management organizations: SSV, SGSP, PAS, IAEMO, and

PSNI.

1.5 Work Progress and Key Achievements to Date

At M36, beyond the horizontal activities (Project Management, Ethical and societal

impact assessment, Standardization, exploitation and dissemination), all the work

has been done and all activities completed

In particular, the development cycle has been finalized as described in WP5

deliverables, and integration activities have been completed, resulting in the

D1.10

Annual Report

Version 1.0

Date 12.06.2017



completion of the SECTOR CIS that has been also tested and validate by users and

during the Final Demonstration.

This means that the fifth milestone MS5 “CIS prototype built up” has been reached at

the end of M30 and MS6 “CIS validated and tested” has been achieved at the

beginning of M34.

1.6 Project Activities organisation

The project is organized in 4 phases, with 8 Work Packages:

Phase 1: Inventory and analyses of European CCM processes, systems and

data (form M1 to M8);

Phase 2: Scenario Definition and Common Information Space Concept Design

(from M9 to M24);

Phase 3: (iterative) CIS development (from M16 to M25);

Phase 4: Demonstration and Validation (from M22 to M33).

The 8 Work Packages, that are strictly inter-correlated, are reported in the following

table with their respective timeline.

Table 3 Work Packages timeline as proposed in D1.6 – Annex II

WP N. Work package title Start

month

End

month

WP1 Project Management 1 36

WP2 Pan-European inventory of past critical events, collaboration processes,

data sets and IT support

1 8

WP3 Scenario definition and user requirements for the pan-European Common

Information Space

3 31

WP4 Common Information Space definition and design 5 24

WP5 Common Information Space building 19 28

WP6 Common Information Space concept demonstration and validation 24 34

WP7 Ethical and societal impact assessment 1 36

WP8 Standardisation, exploitation and dissemination 1 36

Changes with respect to the original plan are in bold

D1.10

Annual Report

Version 1.0

Date 12.06.2017



The reported plan corresponds to the one presented in D1.6. All the delay

accumulated during the first year have been recovered at the end of third year and

the overall project schedule have been respected.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Figure 1 – New project Gantt

JUL AUG SEP OCT NOV DEC GEN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC GEN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC GEN FEB MAR APR MAY JUN

WPs Tasks 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

WP2PAN-EUROPEAN INVENTORY OF

SECURITY SYSTEMS AND DATA SETS

WP3

SCENARIO DEFINITION AND USER

REQUIREMENTS FOR THE PAN-

EUROPEAN COMMON INFORMATION

SPACE

WP4COMMON INFORMATION SPACE

DEFINITION AND DESIGN


BUILDING


CONCEPT DEMONSTRATION AND

VALIDATION

WP7ETHICAL AND SOCIETAL IMPACT

ASSESSMENT

WP8STANDARDISATION, EXPLOITATION

AND DISSEMINATION

MS1

MS2MS3 MS4 MS5 MS6

Year 1 Year 2 Year 3

Milestones

YEAR

Month

Project Year

2014 2016 20172015

D1.10

Annual Report

Version 1.0

Date 12.06.2017



2 Project objectives, work progress and achievements, project

management

The present session provides the progress of the work performed in line with the

structure of Annex I to the Grant Agreement, delineated for each Work Package

whose activities were performed during the first sixth month of second year of

project.

2.1 WP1: Project Management

This WP is led by e-GEOS SPA (EGEOS).

In the framework of the WP1 “Project Management”, according to the DoW and the

Consortium Agreement the following tasks are being performed:

T1.1. Project Coordination;

T1.2. Administrative Management;

T1.3. Risk Management;

T1.4. User Group setup and management.

In addition, Project Boards (Project Steering Committee, Governance Board, ITC

Board, Exploitation and Dissemination Board) activities are included within WP1.

During the third year, some Governance and End User Board meetings have been

held (usually concomitantly with WP1 monthly coordination call conferences) in order

to support the Demonstration event preparation. Whereas there has been no need

for setting up any meeting of the other boards: all encountered issues have been

managed within the WPs’ activities.

Main goals gained during the third year were:

Finalization of the SECTOR CIS development and its demonstration;

very positive SECTOR Dissemination Day;

successful result of the second annual review and the second interim review.

During this period (overall 3rd year), a total of 24 deliverables (including this

document) have been submitted at the day of the finalization of this periodic report:

3 deliverables (D2.1, D4.1, D4.2), have been reviewed and resubmitted in

order to respond to some comments collected after the second annual review.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



6 deliverables (D5.1, D5.3, D5.4, D5.5, D5.6, D5.7), have been fully

reorganized and resubmitted, responding to the request by the advisory board

to provide more information on development process.

2 deliverables (D6.1, D6.2) have been reviewed and resubmitted after the

rejection after the 2nd Interim review, in order to include some additional

information requested by the reviewers.

12 deliverables (D1.7, D1.9, D3.5, D3.6, D5.2, D7.3, D7.4, D7.5, D8.5, D8.6,

D8.7 and this document D1.10) have been submitted in their first release.

Table 4 Deliverable submitted in the reporting period

ID Del.

N° Title Release

Submission

date Status

1 1.3 User Group Definition and

Management 3rd 26/08/2016 Accepted

2 1.7 Interim Monitoring Reports 1st 01/02/2017 Accepted

3 1.9 Annual Report 1st 24/08/2016 Accepted

4 2.1 Activity Report on Information

gathering of past critical events 4th 03/10/2016 Accepted

5 3.5 User requirements tracking 1st 30/09/2016 Accepted

6 3.6 User requirements tracking 1st 01/02/2017 Accepted

7 4.1

A common taxonomy/data model for

European Collaborative Crisis

Management

3rd 30/01/2017 Accepted

8 4.2 Network enabled communication

system design 3rd 30/01/2017 Accepted

9 5.1 Crisis Management Model

Development Report 2nd 01/02/2017 Accepted

10 5.2 SECTOR CIS Implementation Report 1st 01/02/2017 Accepted

11 5.3 Collaborative Processes tool 2nd 02/05/2017 Submitted

12 5.4 Network Enabled Communication

System prototype 2nd 02/05/2017 Submitted

13 5.5 HMI components 2nd 02/05/2017 Submitted

14 5.6 Interfaces and adapters for the

interoperability of tools 2nd 02/05/2017 Submitted

15 5.7 Common Information Space 2nd 02/05/2017 Submitted

D1.10

Annual Report

Version 1.0

Date 12.06.2017



16 6.1 Validation Plan 2nd 02/05/2017 Submitted

17 6.2 Test Report 2nd 03/05/2017 Submitted

18 7.3 Ethics monitoring internal interim

report 2 1st 26/07/2016 Accepted

19 7.4 Ethical monitoring final report 1st 18/05/2017 Submitted

20 7.5 Ethics and privacy by design

workshop report 1st 02/06/2017 Submitted

21 8.5 Second Dissemination Report 1st 03/10/2016 Accepted

22 8.6 Final Dissemination and Exploitation

Plan 1st 18/05/2017 Submitted

23 8.7 Project Dissemination Day Report 1st 05/06/2017 Submitted

24 1.10 Annual Report 1st 12/06/2017 Submitted

D3.5 – “User requirements tracking” was originally due at M24 when, according to

the new plan, the developments were in a very early stage. According to this

consideration, the D3.5 submission was postponed to M27.

Concerning the WP5, according to the DoW, no deliverables are due for this WP.

Anyway, the consortium decided to prepare activity reports in order to register the

activity status. During the review, the advisory board asked to include additional

information related to developments process and methodology. Therefore, the overall

WP organization has been reviewed: All deliverables of WP5 have been reorganized

in 2 deliverables D5.1 and D5.2 in order to reflect the real management of the WP: in

fact, all developments of tasks T5.2 – T5.6 were managed together by the

consortium. Deliverables D5.3, D5.4, D5.5, D5.6, D5.7 represent link to the main

D5.2 deliverable.

In addition to this, a report of the Demonstration Day has been produced and

included in the new version of D6.2 as Annex.

T1.1 - Project Coordination is led by e-GEOS SPA (EGEOS).

The task activities were aimed at managing the consortium through constant

dialogue with the Project stakeholders.

In general, the first part of the last year has been dedicated to developments

finalization, accomplished at the end of M30 as first implementation cycle and

finalized at M32.

Several important events have characterized in this reporting period.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



During the first 6 month of the year, we registered the following meetings, mainly

voted to finalization of development activities and project management:

1. Second technical meeting (Rome, 6-8 September 2016): technical teams met

in order to check the general development status, speed up developments

activities and defining the following steps.

2. Second annual review (8 September 2016): project partners and REA

advisory board met in order to assess the overall project status and

achievements.

3. Participation of the SECTOR CIS to the DOMINO II event (Tiel, 22-23

September 2016): a very first prototypal version of the SECTOR CIS has been

presented and used during an operational scenario.

4. First technical implementation meeting (Rome, 28 November – 1 December

2016): technical teams met in order to finalize developments and start system

integration in the final demonstration environment.

5. Third progress meeting (Rome, 30 November – 1 December 2016): project

partners met in order to assess the overall project status and define and plan

next important activities. Minutes of the event at included as an attachment.

During the last part of the year additional meetings have been held, many of them

involving technical teams in order to finalize the integration and preparing the system

for the final demonstration:

1. Second integration meeting (Rome, 14-15 February 2017): technical teams

met to test the developments and continue the integration phase.

2. Second interim review (Brussels, 21 February): to assess the Project

progresses and verify the submission of all deliverables due at the end of the

second year.

3. Third integration meeting (Rome, 27 February - 2 March 2017): technical

teams met to test the developments and continue the integration phase.

4. First demo preparation meeting (Rome, 30-31 March 2017) technical teams

met to scenario and CIS behavior in case of operational use.

5. First demo preparation meeting and final demo (Rome, 3-6 April 2017): final

set up of the system, Demonstration rehearsal and final demonstration.

Then additional meeting related to dissemination activities have been held:

D1.10

Annual Report

Version 1.0

Date 12.06.2017



1. Task Forces event (Brussels, 28 February): the achievements reached within

the four Tasks Forces have been presented and a video of SECTOR solution

has been showed to the audience.

2. Final Dissemination Day (Brussels, 17 May): SECTOR Final Dissemination

Day has been hosted by the Community of Users. The SECTOR Project has

been presented including achievements and a live demo of the developed

CIS.

As is clear from the number of meetings, the consortium adopted as much as

possible a face-to-face approach also for the development and integration phase: this

approach has allowed speeding up a lot the process with the consequent recovery of

the delay accumulated during the previous years.

It is worth mentioning that during the third year, two review meetings were held (the

second annual review and the second interim review) both assessing a very good

progress of the project and impressive technical achievements.

All comments and remarks collected after the two reviews have been deeply

analyzed by the consortium and, in some cases, they have led to the updates in the

deliverable in order to complete the information provided.

T1.2 - Administrative Management is led by e-GEOS SPA (EGEOS).

No major activities have been performed in this period concerning administrative

management. In fact, payments for the second year of the project have been

postponed after the second annual review up to the interim review and administrative

activities were almost blocked.

The only one deserving to be mention has been the FORM C review for the second-

year activities. All partners have been asked to compile the Form C according to a

defined template agreed with the REA Project Officer during the second year. A

second review of them has been required.

Eventually, concerning the continuous activity of project expenditures monitoring,

some partners have expressed the need to reallocate part of their budget moving

from one WP to another in order to reflect the real involvement and effort. In every

case, the person/months equivalent was of few units and compliant with the partner’s

grant.

This changes with respect to what planned will be reported in the Form C for the third

year.

T1.3 - Risk Management led by ASELSAN with the cooperation of LEONARDO

(former FINMECCANICA/SELEX-ES/SESM), UPVLC, ITTI, CINI, EGEOS, USTUTT,

D1.10

Annual Report

Version 1.0

Date 12.06.2017



and IZEW aims at continuously monitoring quality of deliverables and potential risks

at the project. In addition to these, ethical approvals of partners for carrying out

research related with SECTOR project is within the scope of this task.

The work performed consisted in the following main steps:

1. Quality and language reviews of submitted and revised SECTOR Deliverables.

2. Risk Monitoring throughout the project life.

3. Updating and monitoring Risk Registry.

No main issue was encountered during the reporting period.

No deliverable was submitted during the reporting period.

Hereinafter the final version of the risk register (updated after the demonstration) has

been reported. Clearly the most part of the identified risks have been eliminated.

Some risks remain or pending deliverables are outstanding, project final assessment

(Final Review) and remaining administrative activities.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Table 5 Risk register

ID Description of Risk

Identify consequences Score

Change to Score

since last

assessment

Mitigation Actions / Status Responsible Officer

1.1 Inadequate funding to complete the

project 0.2

Decreased from

0.3

Re-scope project, focusing on time and resourcing

with an updated plan to be submitted. Reallocation of

resources according to real effort and involvement.

Project Coordinator

1.2

Delays and lower quality than expected

for final reports and deliverables due to

the limited time available

Change of the involved people during

the project life time

0.5 Increased from

0.3

A plan for final deliverables production has been

agreed with partners before organizing the Final

Review. Intermediate (but complete) versions will be

shared with the PO and Reviewers in case of delays.

Regular control of the project status and proposal of a

corrective and constructive mitigation plan.

The Management Structure will be further enforced by

e-GEOS and LEONARDO, introducing a dedicated

Technical Manager.

Project Coordinator

Project Steering Committee

1.3 Insufficient End-Users involvement 0.1 Decreased from

0.2

Enlargement and maintenance of the External User

Board (EUB).

Involvement strategy; set up of joint initiatives with

FP7 and ESA Projects addressing the same topics in

order to enlarge the End User Community.

Direct involvement of the Project Coordinator in the

EUB activities in order to foster users’ involvement.

External User Board

Leader

Project Coordinator

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


1.4

Insufficient effort allocation for the

Project Coordinator within the WP1 (3

persons/months per project year)

0.7 Unchanged

The Project Coordinator expressed concerns about

the WP1 effort allocation since the negotiation phase.

The project management will be supported by the

consortium and the management board.

Project Coordinator

Management Boards

3.2 Incomplete or missing capture of

requirements 0.0 Eliminated

An iterative process for the review and refinement of

requirements and scenario was put in place

Project Coordinator

Technical Manager

ICT Board Leader

4.1 Development of User Interface / tools is

more complex than expected. 0.0 Eliminated

User Interfaces are kept at a minimum, as SECTOR

CIS is a common platform to which end-users can

connect via their IT tools and their own user

interfaces.

Technical Manager

ICT Board Leader

4.2

The lack of overlap between detailed

scenario description in WP3 and data

from WP2 may make it difficult for WP4

to produce a taxonomy that matches

the scenario. (Task 4.1)

0.0 Eliminated

CIS Taxonomy has been correctly produced as

detailed in D4.1, starting from available data

requirements and investigating systems and

information sources to be connected to the platform

Technical Manager

Technical lead for the Task

leader (FOI)

4.3

As a result of the above (risk 4.2), there

is a risk that a part of the time allocated

for the taxonomy building will have to

be invested into obtaining further data

that is more related to the scenario

than the data obtained during WP2.

(Task 4.1)

0.0 Eliminated

CIS Taxonomy has been correctly produced as

detailed in D4.1, starting from available data

requirements and investigating systems and

information sources to be connected to the platform

Technical Manager

ICT Board members


leader (FOI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


4.4

It could be difficult to justify some of the

research done in WP2 if its data finds

little use within SECTOR. (Task 4.1)

0.00 Eliminated

In order to proceed with taxonomy acceptance, the

users have been involved to validate the produced

deliverable, collecting feedbacks on possible

improvements to be considered. It is assumed that

during the future validation activity the strong support

of end-users is expected.

Technical Manager

ICT Board members


leader (FOI)

4.5

Inputs from WP2 to WP4 do not contain

the details we need for data modelling.

(Task 4.1)

0.0 Eliminated Additional work was done in Task 4.1 in order to cover

all data needs that were not specified in WP2

Technical Manager

ICT Board members


leader (FOI)

4.6

Input from WP3 to WP4 (i.e. scenario

and use case) does not contain the

details needed. (Task 4.1)

0.0 Eliminated

Scenario was updated and additional work was done

in Task 4.1 in order to cover all data needs that were

not specified in WP2. The produced scenario will be

taken into account as the starting point for validation

activities.

Technical Manager

ICT Board members


leader (FOI)

4.7 Input to WP3 from WP4 is delayed.

(Task 4.1) 0.0 Eliminated

The available inputs have been taken into account as

the starting point for taxonomy definition and the

scenario has been extended to cover all expected

users and systems interactions over the platform, to

be finally validated during validation activities.

Technical Manager

ICT Board members


leader (FOI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


4.8

Unclear demarcation between Tasks

4.1 and 4.2 (and also 4.3) has earlier

been identified as a risk. However,

these three tasks are now cooperating

to produce one deliverable D4.1, but

the coordination of these three tasks

may create a new risk. (Task 4.1)

0.0 Eliminated

Coordination of these tasks in order to produce D4.1

was successfully achieved by strong coordination

between Task leaders, WP-level coordination by WP

leader, clarification of scopes, and clear separation of

duties of task leaders.

Technical Manager

ICT Board members


leader (FOI)

4.9 Insufficient allocation of resources

(personnel/time) for the task. (Task 4.1)

0.0

Eliminated

Detailed work plan. It has been required to delay the

Taxonomy and Crisis Collaborative Model definition

activities due to effort required for scenario

improvement, systems/sources selection and users’

feedback collection and implementation. The timeline

update impacts T5.1 activities start-up.

Technical Manager

ICT Board members


leader (FOI)

4.10 Lack of feedback from partners for

allocation of work within T4.1.

0.0

Eliminated Task coordination teleconferences and frequent

status updates were used to eliminate the risk

Technical Manager ICT

Board members


leader (FOI)

4.11

Unnecessary time consumption -

partners with limited time in the T4.1 /

T4.2 may not have enough time to

understand the NIEM. (Task 4.1)

0.0

Eliminated

FOI led all NIEM based activities and guided other

partners as needed. Partners actively participated to

Tasks T4.1 and T4.2 activities.

Technical Manager

ICT Board members


leader (FOI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


4.12 Invalid detailed scenario description.

(Task 4.3)

0.0

Eliminated Scenario has been updated with users review, to be

validated in the context of WP6 activities.

Technical Manager

ICT Board members


leader (FOI)

4.13 Inconsistent use cases. (Task 4.3)

0.0

Eliminated Use cases have been updated in line with the updated

scenario.

Technical Manager

ICT Board members


leader (USTUTT)

4.14 Postponement of D3.3 may affect T4.3

schedule (Task 4.3) 0.0 Eliminated

Task 4.3 was completed successfully by monitoring of

delay by WP4 leaders and coordination telcos with

WP3 leader.

Technical Manager

ICT Board members


leader (USTUTT)

4.15

Delay for receiving inputs (use cases,

user requirements and data

requirements) might cause delay in the

task. (Task 4.4)

0.0 Eliminated

Project timeline was updated to compensate this

delay. The timeline update impacts WP5 development

activities start-up.

Technical Manager

ICT Board members


leader (ASELSAN)

4.16

Without a full consensus on CIS

system requirements, CIS architectural

design might be incomplete and

misunderstood in relation to DoW.

(Task 4.4)

0.0 Eliminated

System Requirements were identified by review of the

detailed scenario in order to detail the system

behavior and functionality. Performed the required

extra time allocation with possible impact on platform

development activities start-up.

Technical Manager

ICT Board members


leader (ASELSAN)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


4.17

The detailed design of interoperability

boxes might be delayed due to the late

closure of T4.4. (Task 4.5)

0.0 Eliminated Task 4.5 was completed successfully in respect to the

new defined timeline.

Technical Manager

ICT Board members


leader (CINI)

4.18

The design of the communication

services might be delayed due to the

late closure of T4.4 and the late

definition of taxonomies in T4.1. (Task

4.5)

0.0 Eliminated Task 4.5 was completed successfully in respect to the

new timeline.

Technical Manager

ICT Board members


leader (CINI)

4.19

The selection of the Treatment model

might be delayed due to the late design

of collaborative processes in T4.3.

(Task 4.5)

0.0 Eliminated

Thanks to T4.3 investigation on collaboration

processes, the definition of the treatment model has

been completed successfully. The model has been

properly used to design the required treatment

services to interface Treatment systems within the

platform in the context of T4.5.

Technical Manager

ICT Board members


leader (CINI)

4.20

D4.2 is due on month 18, before the

closure of D4.1, foreseen on month 22,

hence D4.2 could not be completed on

time due to the unavailability of D4.1.

(Task 4.5)

0.0 Eliminated

The deadlines of D4.1 and D4.2 was modified. Project

timeline was updated to compensate this delay, with

impact on WP5 timeline.

Technical Manager

ICT Board members


leader (CINI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


4.21

The “deliberate” service design,

envisioned in T4.5, might be delayed

due to the unavailability of the

treatment model to be specified in T4.3.

(Task 4.5)

0.0 Eliminated

Thanks to T4.3 investigation on collaboration

processes, the definition of the treatment model has

been completed successfully. The model has been

properly used to design the required treatment

services to interface Treatment systems within the

platform in the context of T4.5.

Technical Manager

ICT Board members


leader (CINI)

5.1

Unexpected developments of the

technology and emerging trends, in

respect of the existing tools that will be

integrated in the CIS

0.0 Eliminated

In order to support CIS future extensions, a modular

layered distributed architecture has been designed,

providing multiple ways to easily extend itself, through

identification and usage of latest technologies for data

distribution and distributed secure services definition.

To allow a fast integration process for future systems,

a common development environment and modules

project structure has been distributed among partners

and it will be part of delivered content in the context of

development activities through the project repository.

Technical Manager

ICT Board manager

5.2 Lack of inputs in terms of system

architecture design 0.1

Decreased from

0.3

Based on updated WP4 timelines, new schedule of

the WP5 activities and deliverables will be proposed

with a new timeline.

D4.2 and D4.1 have been shared allowing the WP5

activities start-up, but in order to continuously align

development progresses to initial provided design, an

iterative approach will be implemented, through

required design (D4.1 and D4.2) periodic updates.

WP4 leaders will support iterative approach activities.

Project Coordinator

Technical Manager

WP5 and WP4 leaders

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


5.3

The implementation might be delayed

due to the late closure of WP4. (Task

5.1)

0.0 Eliminated

D4.1 delivery delay required a new schedule for T5.1

finalization. Thanks to strict coordination with T4.1

and T4.2 tasks leaders it has been possible to

proceed with a first CIS Model implementation, to be

improved through the defined iterative development

approach. Such updates might have impact on

Collaborative Management Services development

(T5.2) and Interoperability boxes (T5.5) finalization.

Technical Manager

ICT Board members


leader (LEONARDO)

5.4



5.2)

0.0 Eliminated

D4.1 and D4.2 delivery delay required a new schedule

for T5.2 finalization. As Collaborative Management

Services have been designed as platform services,

related implementation has to be considered part of

platform modules. This decision might have an impact

on T5.3 activities finalization.

Technical Manager

ICT Board members


leader (THALES)

5.3



5.3)

0.0 Eliminated

The implementation of core, transversal and utility

services have been started, thanks to development

activities coordination and a shared common

development/integration environment.

Basic security mechanisms and existing libraries have

started to be integrated. Collaborative Management

Services and Treatment Services development

activities have been started, providing design

refinements, improving D4.1 and D4.2, whose new

versions have to be released once the first refinement

cycle is closed

Technical Manager

ICT Board members


leader (CINI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


5.3



5.4)

0.0 Eliminated

The implementation of the SECTOR HMI has been

started, thanks to development activities coordination

and a shared common development/integration

environment.

Configuration, Supervision and Security modules

development have been started, with some difficulties

linked to platform development delay. It has been

agreed to proceed with a first implementation,

respecting design decisions and interfacing HMI with

pilot platform external services modules. The

integration process will continue during tasks T5.7

and T6.1.

Technical Manager

ICT Board members


leader (SAADIAN)

5.4



5.5)

0.0 Eliminated

The implementation of Interoperability Boxes has

been started, thanks to development activities

coordination and a shared common

development/integration environment.

IBXes modules development have been started, with

some difficulties linked to platform development delay.

It has been agreed to proceed with a first

implementation, respecting design decisions and

interfacing systems/sources with pilot platform

external services modules. The integration process

will continue during tasks T5.7 and T6.1.

Technical Manager

ICT Board members


leader (UPVLC)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


5.5



5.6)

0.0 Eliminated

The platform integration activities have been started

through the definition of the integration/development

environment based on designed technologies. The

integration plan was not required by the DoW, but in

order to proceed with integration activities, it is

required and currently under production based on

updated modules interactions identified through

design analysis. The integration process cannot

continue until integration plan and platform modules

have been finalized, so it has been agreed to proceed

gradually, starting with Core Layer modules

integration, proceeding with higher layers up to HMI

and Systems. Based on current delay on development

activities, it has been also agreed to continue

integration with support of T6.1, together with the

initial validation plan definition.

Technical Manager

ICT Board members


leader (LEONARDO)

6.1

Unavailability of resources at End-

Users’ premises to support to the CIS

prototype integration for the

demonstration and validation activities

0.0 Eliminated from

0.5

SECTOR partners involved in the ICT board will

support End Users in demonstration and validation

activities

ICT Board members

6.2 Integration activities support to T5.6 0.0 Eliminated from

0.5

In order to support T5.6 in integration activities

finalization, possible extra effort might be required.

Technical Manager

ICT Board members


leader (CINI)

D1.10

Annual Report

Version 1.0

Date 12.06.2017





Change to Score

since last

assessment


7.1

Legal and national constraint in

providing information related to the past

events and technical audits

0.0 Unchanged N/A NA

5.2 Risk related to architectural design and

system development 0.0

Eliminated from

0.3

There is a redundancy of 5 months built in between

architecture design and CIS prototype building,

therefore delays can be tolerated without postponing

any other activity with the project.; although

inconsistencies in the Dow (design and

implementation activities run parallel with only two

months of difference) will be overcome by proposing a

different schedule of WP4 and WP5 activities.

Technical Manager

ICT Board manager

8.1 The R&D results are not sufficiently

disseminated. 0.1 Unchanged

A set of dissemination actions defined at the

beginning of the project in order to assure the correct

dissemination of the results, will be monitored during

the project lifetime.

Dissemination Manager

D1.10

Annual Report

Version 1.0

Date 12.06.2017



T1.4 - End User Board Management, led by LEONARDO SPA (LEONARDO), an

External Users Board (EUB) composed by representatives of the following

organization has been established in order to guarantee the proactive End-Users

involvement: EGEOS, ITTI, LEONARDO, SAADIAN, USTUTT, IZEW, SSV (Internal

End-User), PSNI (Internal End-User), PAS (Internal End-User), IAEMO (Internal End-

User) and SGSP (Internal End-User).

An additional group of end-users hereinafter called External End-Users, was

established to ensure that requirements and needs for the system are gathered from

the widest possible group of potentially interested persons and organizations. The

Governance Board was identified as the central body for the management of all end-

user related activities, respectively the SECTOR User Group. The Governance Board

consists of different partners of the SECTOR Consortium. It is organized in a

hierarchical structure. The leader of the Governance Board is the University of

Stuttgart, which is supported by LEONARDO and EGEOS from the side of the

External Users Board. Furthermore, all relevant Work Package and Task leaders of

the SECTOR project are part of the Governance Board, because their specific project

related activities often require the support of Internal and External End-Users. The

Governance Board involves all members of the User Group, meaning Internal and

External end-users.

The work done in the last year of the project consisted in the following main steps:

1. The structure of the board was revised to ensure a better involvement of internal

and external end-users.

2. An action plan discussing steps and activities regarding the best involvement of

the internal and external end-users was set up and implemented.

3. All end-users were provided with relevant information on the SECTOR DEMO and

their potential roles during the aforementioned event..

4. The “Save the Date” letters to all invited end-users for SECTOR Demo (scheduled

on 5th April 2017 in Rome, Italy) have been sent out in December 2016

5. The “Invitation” letter to the SECTOR Demonstration Day on 5th April 2017 in

Rome, Italy, c/o LEONARDO S.p.A., via Tiburtina km 12.400, has been drafted

and circulated within Board members.

6. End-user travel planning was accomplished.

7. The demo was held on April 5th in Rome: the Board fostered the End Users

participation and involvement.

8. Collecting feedback and preparation of the partner list composed by 32 rows and

10 columns with data such as organization, name, role, contact details and

availability to participate in the final demonstration day.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



9. Supervising the logistics concerning external users for the final demo held in

Rome in April 2017.

The following main issues were encountered during the reporting period:

1. Formal commitment of more end-users covering other countries and types of

organizations was challenging, but could be solved due to the active support of all

members of the SECTOR consortium.

2. Structured gathering of feedback from end-users, but could be realized through a

feedback questionnaire.

3. Few last-minute adjustments before the demonstration were recorded but nothing

seriously to affect the final results.

The following deliverable was submitted during the reporting period:

1. Second update and revised version of D1.3 on August 2016 (accepted by the EC).

2.2 WP2: Pan-European inventory of past critical events,

collaboration processes, data sets and IT support

The WP2 is led by USTUTT, with an overall duration of 8 months (from M1 – July

2014 to M8 – February 2015), and includes the participation of EGEOS, ASELSAN,

LEONARDO, FOI, ITTI, CINI, SAADIAN, THALES, PSNI, PAS, IAEMO, SSV, SGSP

No activities have been performed in the reporting period.

2.3 WP3: Scenario definition and user requirements for the pan-

European Common Information Space

WP3 is led by UPVLC, with an overall duration of 29 months (from M3 – Sep 2014 to

M31 - Jan 2017), and includes the participation of LEONARDP, ASELSAN, FOI, ITTI,

CINI, SAADIAN, EGEOS, USTUTT, THALES, PSNI, PAS, IAEMO, SGSP and SSV.

The objective of this WP is to specify the user needs as a basis for the CIS concept.

This includes the definition of crisis scenarios, the analysis of data requirements and

the collection and formalisation of user requirements, including their acceptance

criteria.

The participation of the end user partners is key for establishing an initial set of

needs, verifying the final requirements and defining a validation scenario to cover all

the stated requirements.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



During the previous reporting period (M1-M24), the following activities were

carried out:

T3.1 - Crisis scenario definition - led by UPVLC

Four cross-agency/cross-border scenarios were proposed by the end user partners.

These scenarios were based on the high-level requirements and the analysis of

previous past events gathered in WP2. The final scenario for the demonstration was

selected among them.

The selection criteria for the scenario was discussed during a consortium meeting

and the European rivers freight crisis was selected due to:

Its complexity due to the number of involved actors.

Its commonality with the others scenarios.

The economic impact caused by collapse in European waterways.

Floods crisis occur in all participant countries.

DOMINO workshop as an opportunity for developing the scenario, collecting

requirements and disseminating SECTOR.

The outcome of this task, D3.1 “Scenario definition”, was submitted in M9 with two

months delay. The reason for the delay was to take advantage of the progress

meeting celebrated in M7 in Valencia for deciding the selection criteria for the final

scenario. The extended lead time for the deliverable also allowed and iterative

refinement process of its content.

T3.2 - Data requirements analysis - led by THALES SA (THALES)

User requirements for the Sector Common Information Space in terms of data were

gathered from heterogeneous groups of stakeholders by means of a specific

questionnaire, workshops (Paris in M10 and Zwijndrecht in M11) and interviews.

These relevant data were collected, identified, classified and analysed to produce a

first synthetic set of types of data to be exchanged among crisis managers and

responders within cross-border inter-agencies crisis situations.

The results of this task were D3.2 "User requirement formalization", submitted in M13

with one month delay to take advantage of Zwijndrecht workshop results for

gathering and validating the final requirements. And D3.3 "Data requirement

analysis" submitted in M18 with four months delay due to the remarks received from

the reviewers during the progress meeting celebrated in M15 about the new project

focus in terms of interoperability among already existing CMS obliged to change the

definition of detailed scenario and is associated uses cases.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



T3.3 - User requirements collecting and tracking - led by ITTI SP.ZO.O (ITTI)

User requirements were collected by means of a questionnaire developed through an

iterative process that started with the analysis of the preliminary high-level

requirements provided by WP2. The questionnaire was completed by 35 end users

participating in interviews and workshops and the following analysis of its output was

the base for formalizing the final user requirements for the design phases of

SECTOR CIS.

Traceability matrixes were also created for following-up the compliance of the user

requirements in the subsequent work packages along all the project schedule

Deliverable D3.4 was submitted in M13, one month after the scheduled data due to

the same delay in the submission of D3.2, and the need to be aligned with this

deliverable. The deliverable was rejected in the progress meeting and the document

was amended according to the reviewer instructions and resubmitted in M17.

Main achievements and activities performed during the reporting period M31-

M36 are the following:

T3.3 - User requirements Collecting and tracking - led by ITTI SP.ZO.O (ITTI) with

the cooperation of LEONARDO, ASELSAN, UPVLC, CINI, SAADIAN, EGEOS,

USTUTT, THALES, PSNI, PAS, IAEMO, SGSP, SSV aims at collecting and tracking

requirements for the Common Information Space. During the reported period only

tracking activities were performed.

The work done consisted in the following main steps:

1. Users requirements tracking and deliverables preparation.


1. Deliverable D3.5 was submitted in M27, three months after the schedule data due

to previous delays in required deliverables and no significant progress were

performed in the implementation.

2. Deliverable D3.6 was submitted in M32, one month after the schedule data to

include last updates in integration activities.

The following deliverables were submitted during the reporting period:

1. D3.5 User requirements tracking (M27);

2. D3.6 User requirements tracking (M32).

D1.10

Annual Report

Version 1.0

Date 12.06.2017



2.4 WP4: Common Information Space definition and design

The WP4 is led by ASELSAN, with an overall duration of 22 months (from M3 to

M24, from September 2014 to June 2016) and includes the participation of EGEOS,

UPVLC, FOI, ITTI, CINI, SAADIAN, LEONARDO, USTUTT, and THALES.

For this WP activities were performed only in the first part of the year. Therefore, in

the following, the same information reported in D1.7 are provided.

WP4 aims to finalize the conceptual and architectural system design of the SECTOR

Integration platform, which provides the Common Information Space to first

responders and police authorities in order to collaborate, to data providers to serve

their data and to service/system providers to serve their services as value adding

services enhancing features of CMSs’ in an interoperable way for crisis management

and response processes, especially for cross-border crisis situations.

The design process of SECTOR platform was planned with seven tasks in WP4.

During two years all tasks were active and they were finalized with two deliverables.

The result of T4.1, T4.2 and T4.3 has been delivered in D4.1, which is a special

deliverable as it was planned at M22, with a desired pre-release at M20, and a

desired post-release at M24. So D4.1 was delivered in three phases as follows:

1. The Interim D4.1 - A pre-release with version no 00.15 delivered at M20.

2. The Final D4.1 - The main deliverable with version no 1.0 delivered at M22.

3. The updated final version of the D4.1 – A post-release with version no 2.0

delivered at M24.

The result of T4.4, T4.5, T4.6 and T4.7 has been delivered in D4.2. This deliverable

was due at M24, with a desired interim version at M20. As such the deliverable D4.2

was delivered in two phases as follows:

1. The Interim D4.2 - A pre-release with version v1.0 at M20.

2. The Final D4.2 - The main deliverable with version no 1.8.1 delivered at M24.

The activities performed in seven tasks during first two year can be summarized as

follows:

T4.1 - Taxonomies identification and definition delivered a common emergency

management vocabulary, including SECTOR specific vocabulary. It has been done

by encompassing a common emergency management vocabulary with SECTOR

specific vocabulary; more specifically NIEM (National Information Exchange Model)

Core, NIEM EM (Emergency Management), general extensions of the NIEM EM

vocabulary and extensions with SECTOR specific material coming from SECTOR

specific message formats.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



T4.2 - Crisis Management Model Definition and Design improved the T4.1 CIS

Model in support to systems and information sources integration on interoperability

platform. Such model improvement process has been performed through the T4.1

selected framework, NIEM.

T4.3 - Collaborative Processes Definition and Design defined and designed a

SECTOR scenario specific crisis management metamodel as well as the related

information exchange content model. By relating processes with requirements,

information sources and IT tools, it put the base for the further model design

activities.

T4.4 - Architecture Design produced high level design of SECTOR Common

Information Space and Collaboration Platform.

T4.5 - Network Enabled Communication System design focused on detailed

design of the interoperability boxes for IT tools, Information Source and Value Added

Systems, and detailed design of the Event-Driven SOA so to enhance

communication services offered by the SECTOR system.

T4.6- HMI Design defined and designed the final IT tools, Information Source and

Value-Added Systems’ HMI extensions UI design and function that will be required.

T4.7- Security and Data Protection proposed a security framework to ensure

access and authorization controls for the Sector CIS and for the systems, sources

and IT tools, which will be integrated and designed the final security model to be

implemented within the framework via security policies and certificates.

During the period M25-M30, the work package 4 was active to improve deliverables

D4.1 and D4.2 in the lights of comments of reviewers as below:

D4.1 have been improved to show:

how the proposed NIEM-based data model would be able to support the

language-sensitive semantic interoperability.

how the taxonomy could be corrected and modified in case of wrong or

missing term definitions and enhanced with respect to different use cases.

In D4.2 the following improvements have been realized:

Hypothetical scenario is updated to show transnational interoperability

capabilities of the CIS to allow for better preparedness and faster response of

the cross-border ERAs as the crisis begins and evolves.

High level IBX design have been more detailed in the data transformation

mechanism description with respect to the CIS data format and taxonomy the

proposed NIEM- based data model would be able to support the language-

sensitive semantic interoperability.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



The Data Validation and Transformation (DVT) CIS service have been

clarified.

Purpose of Help Information Services service have been clarified.

Human Machine Interface Design for updating and modifying of the CIS data

model (taxonomy) have been added.

Some figures and typos have been corrected.

2.5 WP5: Common Information Space building

The WP5 is led by LEONARDO SPA (LEONARDO), with an overall duration of 12

months (from M13-M25), and includes the participation of EGEOS, UPVLC,

ASELSAN, FOI, ITTI, CINI, SAADIAN, USTUTT and THALES.

In the previous reporting, i.e. period (M13-M24), the CIS platform was designed in

the context of WP4 and the development activities have been started based on

LEONARDO FINBOX approach, which provided the required information about

possible steps to be performed, in terms of platform organization, external systems

and required information sources integration. Useful first annual period Software

Configuration Management guidelines have been used and new

development/integration ones provided in order to assure both software quality and

homogeneity between all produced projects, in respect to distributed Quality Plan.

During the final reporting period (i.e. starting at M25), the CIS platform (which been

designed in the context of WP4 and developed starting from the framework FINBOX

(provided by LEONARDO), capabilities has been integrated and tested up to the final

demonstration event, which took place in April 2017 at LEONARDO premises in

Rome, Italy.

Moreover, useful and previous period software configuration and development

management guidelines were integrated and used in order to assure both software

quality and homogeneity between all produced artefacts, in respect to distributed

Quality Plan.

It is important to note that after the second review, it was decided to reorganize WP5

activities and, consequently deliverables, in order to manage the overall

developments and integrations in a more effective and choral way.

This approach was approved by the EC and the following deliverables were

submitted and approved during the interim review:

- Deliverable D5.1, Crisis Management Model Development Report. Led by

LEONARDO.

- Deliverable 5.2, SECTOR CIS Implementation Report. Led by LEONARDO.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Final developments and integration activities were performed during the first part of

the third year, therefore in the following, the same information included in D1.7 are

reported with only minor updates.

T5.1 - Crisis Management Model and Treatment System development - led by

LEONARDO SPA (LEONARDO) with the cooperation of EGEOS, UPVLC,

ASELSAN, FOI, ITTI, USTUTT, THALES aims both at developing the SECTOR CIS

infrastructure Information Model and realizing the Treatment System Services on the

basis of the results achieved in WP2, WP3 and WP4.

The work performed in the context of this reporting period consisted in the following

main steps:

1. Update and improvements to the design documentation and overview of CIS

Architecture and model dependency where appropriate upon testing feedback

(cook-books).

2. Implementation of the roadmap and design/development iterative approach for

continuous improvement.

3. Realization of CIS Model modules.

4. Implementation of the accepted recovery action plan.


D5.2 SECTOR CIS Implementation Report.

T5.2 – Collaborative processes development

Led by THALES with the contribution of ASELSAN, FOI, LEONARDO, USTUTT, this

task aims at developing the SECTOR CIS infrastructure Collaborative Processes

services on the bases of the results achieved in WP2, WP3 and WP4.

The work performed during the first year consisted in the following main steps:

1. Analysis of currently available design documentation and overview of CIS

Architecture and model dependency.

2. Definition of development activities guidelines with Development Activities report

distribution.

In the context of the second annual report, such activity has been continued,

improving the infrastructure design together with WP4 applying a development

iterative approach and the required services modules have been structured and

currently developed.


D1.10

Annual Report

Version 1.0

Date 12.06.2017



1. WP2 presented high level description of possible procedures and processes to be

considered in the context of emergency management, because a deep analysis

was required and expected through User requirements definition process.

2. WP3 user requirements delay: in order to have a complete and correct view of

user requirements, several interview steps have been performed, also providing

details on demonstration scenario included in Data Requirements definition.

3. WP4 Collaborative Processes services design: in order to properly design such

services, the detailed scenario details were required, but it had been produced in

the context of data requirements analysis with delay.

Based on the encountered issues, it was not possible to startup D5.3 Collaborative

Processes tool activities to be closed in M19, but a recovery Action Plan has been

discussed and proposed, where D5.3 is expected to be released in M26 within

infrastructure deliverable, D5.4.

D5.3 and D5.4 are finally delated in favour of D5.2, which collects related activities.

Therefore, the following deliverable was submitted during the reporting period:


T5.3 – Network Enabled Communication System development

Led by CINI with the contribution of UPVLC, ASELSAN, FOI, ITTI, LEONARDO, this

task has the following main objectives:

To develop the Network Enabled Communication System designed in WP4 to

enable interoperability among IT tools, via the SECTOR CIS platform, at

infrastructure level;

To develop “white-book” web services for enabling IT tools to get/feed data

from/to the SECTOR CIS platform in a collaborative way;

To provide the treatment system (based on IsyProc and Omar Thales results -

SECPLAN) for enhancing decision support and resources optimization on

available organizations’ activities plans.

All the activities have been successfully accomplished. In line with comments made

by reviewers during the second interim review held in Brussels, the output of the task

has been integrated, in a concentrated activity summary, in D5.2 (SECTOR CIS

Implementation Report – final) that includes all aspects related to the development

activities in relation to WP5 and hence what concern the T5.3.

During the implementation of T5.3, the following activities have been performed:

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Evaluation of the design outputs included in D4.2 concerning Decision Support

services (AfPA and Deliberate) and value added such as SECPLAN.

Collaborative Planning services have been evaluated as well;

Refinements of the design for gaps identified in D4.2;

Development activities for the SECTOR CIS core part (network enabled

communication system) based on LEONARDO FIN-BOX, treatment tool and

collaborative services;

Realization of the cook-books for the FIN-BOX core part as to support further

enhancements and extensions of the platform;

Finalization of the development activities and integration aspects for making

the FIN-BOX fully compatible with the SECTOR requirements;

Finalization of D5.2 with inclusion and merging of contributions related to the

old D5.4;

Continuous development activities monitoring for supporting bug fixing as per

result of the unit and integration tests.

Thus, the following deliverable was submitted during the reporting period:


T5.4 - HMI Development

Led by SAADIAN TECHNOLOGIES LIMITED (SAADIAN) with the contribution of

UPVLC and ASELSAN, the main objectives of this task are:

To develop the CMS HMI application, which will allow the authorization and

access control to be configured for the CIS services, systems and sources via

the HMI. The development will be based on the HMI design along with the

Security Management Services designed and outlined in WP4.

To allow the sources, systems and services within the CIS to be configured via

the CMS HMI. The development will be based on the HMI design along with

the Configuration Management Services designed in WP4.

According to the new action plan the tasks output will be delivered in D5.5 and the

expected date of completion of development activities is in M27.

During the T5.4 the following activities have been performed:

D1.10

Annual Report

Version 1.0

Date 12.06.2017



The visual design of the Configuration Management and Security

Management Components within the CMS HMI was outlined as part of the

D4.2 deliverable, and feedback was gathered from the partners.

The core functionality for the final CMS Configuration Management and

Security Management HMI Components were determined.

A prototype implementation of the client was developed and deployed on the

EGEOS repository.

The prototype has been refined in order to integrate the client with the

backend Configuration Management and Security Management Services.

Contributions to D5.2.

Testing, validation and documenting the test outputs in D6.1 and D6.2.

D5.7 is finally delated in favour of D5.2, which collects related activities. Testing and

validation outputs are moved to D6.1 and D6.2 deliverables.



T5.5 - Interfaces and Adapters development for the interoperability of tools

Led by UPVLC with the contribution of LEONARDO, ASELSAN, FOI, ITTI, CINI,

SAADIAN, EGEOS and THALES. The main objective of the task is:

to develop the IBXs designed in WP4 for all the IT tools, Information services

and Value-added services, to enable interoperability of all involved tools with

SECTOR CIS.

According to the new action plan, the tasks output will be delivered in D5.2.

During task T5.6, the following activities have been performed:

Evaluation of the design outputs included in D4.2 concerning IBXs.

Refinements of the design for gaps identified in D4.2.

Development activities for all IBXs (IT tools, Information services and Value-

added services).

Distribution of ToC for D5.6 and contributions’ merges.

Testing and validation of the developed components.

D1.10

Annual Report

Version 1.0

Date 12.06.2017




D5.6 is finally delated in favour of D5.2, which collects related activities.



T5.6 - CIS development

Led by LEONARDO SPA (LEONARDO) with the contribution of EGEOS, ASELSAN,

FOI, SAADIAN and THALES, the main objectives of the task are the development of

CIS regards the integration of all previous results from WP5. Software developed and

adapters implemented are progressively integrated. The CIS enables the

interoperability of all involved agencies, through the continuous and shared access to

all necessary data and information, besides the use of collaboration process models

to support coordination and cooperation.

According to the new action plan, the task will converge its outputs in deliverable

D5.2.

During the task T5.6, the following activities have been performed:

Evaluation of the developed modules in order to progressively integrate them

in the platform.

Refinements of the design for gaps identified in D4.2.

Distribution of ToC for D5.2 and contributions’ merges.

Finalization of the integration activities,

Testing and validation of the developed components.


Therefore, the following deliverable was submitted during the reporting period:


2.6 WP6: Common Information Space concept demonstration and

validation

The WP6 is led by CINI, with an overall duration of 11 months (from M24 – June

2016 – M34 – April 2017), and involves UPVLC, ASELSAN, FOI, ITTI, SAADIAN,

EGEOS, USTUTT, THALES, PSNI, PAS, IAEMO, SGSP and SSV.

The official start of WP6 activities was month M24 (June). However, in order to be

pro-active and support the SECTOR CIS demonstration activities best, the

D1.10

Annual Report

Version 1.0

Date 12.06.2017



consortium, during the WP4 / WP5 activities, started to work on task T6.1 with an

initial characterization of what would then become the final demonstration scenario

script. The realized demonstration script has been finally used as main reference for

the SECTOR CIS platform demonstration.

Previous to this reporting period, the consortium started the characterization of

scenario script, trying to detail the scenario definition delivered D3.3 laying an

emphasis on involved systems and their interactions. During this reporting period,

the consortium finalized D6.1 and D6.2 completing the assigned contributions and

incorporated the comments and remarks reviewers expressed during the last interim

review held @ REA, Brussels on February 21st.

CINI guided the activities of the WP by means of regular conference calls with all

project partners involved in WP6, prescheduled at the beginning of the WP and held

on July 4th, July 29th, September 30th, October 28th, and December 23rd, 2016.

Dedicated WP6 slots have replaced the calls on August and November during the

technical meetings held in EGEOS premises, Rome on September 6th and 7th, 2016,

and in LEONARDO, Rome, from November 28th to December 1st, 2016. Other

activities were performed during WP5 integration meetings on February 14-15, 2017

and February 27 – March 2, 2017, while final preparations have been performed at

the demo preparation meeting held on March 30-31, 2017 and April 3-4, 2017. The

final demo event has been performed successfully on April 5th, 2017. The calls and

physical meetings were essential to monitor the activities performed by partners,

schedule internal deadlines for deliverables, and quickly respond to emerging issues.

In the following we report on the activities performed during the reporting period M25-

M36 on a task by task basis.

T6.1 – Validation Plan on the selected scenario - led by CINI with the cooperation

of UPVLC, ASELSAN, LONARDO, FOI, ITTI, SAADIAN, EGEOS, USTUTT and

THALES aims at characterizing, refining and definitively producing a SECTOR CIS

validation plan. The validation plan includes all activities that are necessary to

accomplish the verification and validation of the SECTOR CIS platform. In particular,

activities conducted in this task had the main objective to verify, if the SECTOR CIS

platform is compliant with the requirements defined in D3.2 and matches with the use

cases produced in D3.3. The main output of the activity has been the deliverable

D6.1 – Validation Plan that according to the last agreed action plan has been

completed and submitted on M30 for the official quality review and has been finally

submitted on M31 (v1.0). As a follow-up of the interim review, reviewers requested to

modify the deliverable to include missing project demo preparation activities reports

(e.g., ELSI regulations application plan). The reviewers also requested that the

consortium to add performance tests in order to evaluate the performance of the

D1.10

Annual Report

Version 1.0

Date 12.06.2017



platform services. Feedbacks have been completely implemented and the D6.1

(v2.0) was submitted at M34.

The work performed during the reporting period consisted in the following main steps:

1. Specification and finalization of the scenario script in which the consortium, led by

CINI, has detailed the scenario delivered at M24, focusing not only involved

systems and systems’ interactions, but also including the definition of potential

end-user roles within the scenario and the communication of dedicated roles

towards the involved end-users;

2. Specification and finalization of the validation strategy that has been used for

platform validation activities;

3. Conduction a of a consistency check to verify if and how the demo script covers

the CIS requirements defined in D3.2;

4. Specification and finalization of the SECTOR Test Plan that includes: unit test

cases for all components developed by partners (e.g., Information Services, Core

Services, Knowledge Management Services, External systems and sources

IBXes);

5. Specification and finalization of the Integration Plan according to developed

Integration boxes and the final demonstration script;

6. Definition of the Integration test cases for the components developed by partners,

including penetration tests. A total of 54 integration test cases have been

specified to verify the actual and successful integration of SECTOR components.

Considering the complexity of the platform and the conformance of specified tests

in respect to the demonstration scenario we consider these results, together with

the 329 test cases, as a valid output of T6.1 activities;

7. Design and specification of performance tests used to evaluate the performance

of the SECTOR platform and for evaluating platform reactions in the case of

massive submitted requests. Each partner participating in the activities was asked

to provide a script with the specification of performance tests to be run for its own

developed component. CINI had the responsibility to join those contributions and

run performance tests.

8. Analysis of ELSI regulations to be applied in order to preserve end-users’ privacy

taking part to the final demonstration event that led to two main findings:

8.1. Characterization of an Informant Consent to be signed by all the SECTOR

final demonstration participants;

8.2. Verification of the final demonstration scenario in terms of privacy and ethical

issues for data used and definition (if any) of remedy actions to be taken in

order to be compliant with ELSI regulations.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



9. Definition of the demonstration plan, including the final demonstration script. This

also takes into account the feedbacks collected during end-user validation

sessions (i.e., a dedicated end-users workshop held in Rome, IT on September

7th, 2016 with internal end users, and the participation to the DOMINO II event

held in Tiel, Netherlands on Sept. 22nd-23rd, with external end users, in the context

of T6.4). Partners involved in T6.1 supported T6.4 for the organization and

participation to the validation events. Received feedbacks have been reflected in

the final version of the demo script in D6.1.


1. The delays accumulated in WP4 and WP5 forced some partners to deliver

integration test cases only in late December. For this reason, deliverable D6.1

(v1.0) has been finalized at the end of M30, and sent on December 30th 2016 for

the official quality review. The document (v1.0) has been finally submitted on

January 15th, 2017.

2. An additional delay was accumulated also due to the need of specifying

penetration test cases (initially not foreseen and requested by reviewers) with a

dedicated integration block. The addition of such test cases required a study of

available tools, applicable to the CIS, to automatize the process and speed-up the

penetration test cases execution in T6.2.

After the interim review, the document (D6.1 v2.0) has been submitted, according to

plans, on M34.

T6.2 – Testing – led by CINI with the cooperation of UPVLC, ASELSAN,

LEONARDO, FOI, ITTI, SAADIAN, EGEOS, USTUTT and THALES, aims at

performing the testing activities according to the test cases specifications and

responsibilities of project partners defined in the validation plan (D6.1). The objective

is to exercise the services provided by CIS components and IBXes in order to ensure

the quality of the CIS implementation and verify its correct functioning. The main

output of the activity is deliverable D6.2 – Test Report, which collects all results of the

testing activities conducted on the SECTOR platform.


1. Execution of the unit test cases by all partners, according to the specifications in

D6.1, hence including standard functional testing plus further evidence obtained

by means of robustness, stress and performance testing, where needed;

2. Execution of integration test cases, following the integration blocks ordering

defined in D6.1, to check the communication and interoperability among CIS

components, and including penetration tests;

D1.10

Annual Report

Version 1.0

Date 12.06.2017



3. Execution of performance tests, following specification included in D6.1 v.2.0 for

the correct evaluation for platform reactions in the case of heavy workloads;

4. Collection of operational data to provide evidence of the actual execution of the

test cases and to perform the accurate verification of CIS capabilities.

The following main issue was encountered during the reporting period:

1. The delays accumulated in WP4 and WP5 caused a shift in the timing of platform

integration activities, that then caused the late execution of integration tests

specified in the validation plan (D6.1). For this reason, D6.2 (v1.0) was not

completed at the end of M30. Only few contributions were missing on integration

tests execution, allowing fully completing and submitting D6.2 (v1.0) by end of

M31.

After the interim review in Brussels, the D6.2 (v2.0) has been correctly submitted at

M34.

T6.3 – Demonstration - led by LEONARDO SPA (LEONARDO), with the

cooperation of all project partners except IZEW and SSV. This task aims at arranging

and orchestrating (local conduction) the final demonstration event of the SECTOR

CIS concept which took place at LEONARDO premises in Rome on April 2017, with

the collaboration of end users invited to act on the real CIS prototype during the

Demo event.

The work performed consisted in the following main steps focused on the Demo

event:

1. Demonstration Room and Server Room configuration and setting according to the

following schematic representation of the working scenario.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



This includes software environment preparation (virtual machines configuration) and

customised software settings.

2. Directing configuration according to the Demo script in order to distribute the most

relevant information always on the main screen and the complementary on the

later monitor in the Demo room.

3. Guest and Users lists were created well in advance and kept constantly updated

according to invitation reply received. Entrance registration procedures were

anticipated 30 days in advance to Company Security Office and officially started 2

weeks in advance according to Company policies.

4. Logistics of the Demo day include coffee break and sitting lunch for 70 circa

people. End user-management during the final demo event required travel

planning for external end-users, preparation and analysis of an end-user

validation questionnaire regarding the CIS solution.

5. Dissemination activity include a news on LEONARDO Hub intranet available at

Corporate level with all LEONARDO companies.


1. The set-up of the VPNs between consortium partners were reporting few

technical (set-up) problems solved after a while.

2. During the rehearsal, the available bandwidth was bottlenecked for a short period

due to sharing the LAN resources with other test-beds within the LEONARDO

company.

There are no deliverables for this task according to the DOW, however a demo report

has been documented in an Appendix to the D6.2 deliverable.

T6.4 – End-users validation - led by SAADIAN TECHNOLOGIES LIMITED

(SAADIAN) with the cooperation of PSNI, PAS, IAEMO, SGSP, SSV, and with CINI

as WP leader, aims at validating the SECTOR CIS using end users’ own scenarios

and processes.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



The end user validation was performed in conjunction with the following end users:

PSNI, PAS, IAEMO, SGSP, SSV, and the scenarios were formulated based on the

end users’ scenarios and processes. It was important that as many of the tools that

were integrated with SECTOR CIS were used within the different scenarios in order

to validate the overall SECTOR CIS.

As part of the end user validation, the following steps were performed:

SSV End User Validation

o Evaluation of SECTOR prototype at DOMINO II workshop by external

end users (SSV) held at Tiel, Netherlands in September 2016.

o Validation of SECTOR scenario by end users at SECTOR technical

meeting at Rome in September 2016.

o The results, comments and suggestions were collated for input into the

ongoing development activities.

o The output of this session was reflected in D6.1.

IAEMO / PSNI User Validation

o Planning meeting for Ireland based validation exercise held in

November 2016.

o Irish scenario (based on a cross border event) was formulated by

IAMEO and evaluation toolset selected.

o Mapping of scenario steps, SECTOR tools involved, actors, data needs

& evaluation criteria was formulated by SAADIAN / CINI in conjunction

with PSNI/IAEMO.

o A Power Point presentation was created by SAADIAN in conjunction

with IAEMO which outlined the series of steps to be followed within the

scenario and the tools to be used.

o A guide to the tools involved was also documented by SAADIAN and

sent on to IAEMO / PSNI.

o A series of questions was formulated via an online questionnaire, which

were cross referenced against the original requirements captured in

D6.1 in order to ensure that the requirements were met for the end

users.

o The IAEMO / PSNI validation exercise was conduction in March 2017

by IAEMO/PSNI.

o The results of the questionnaire were formulated, along with the

scenario steps, questionnaire and tool involved and documented in an

Appendix deliverable to D6.2.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



PAS / SGSP User Validation

o The PAS / SGSP scenario was formulated by PAS.

o The scenario, tools used, data, actors and evaluation criteria was

formulated by PAS in conjunction with SAADIAN.

o The questionnaire that was used for the PSNI/IAEMO end user

validation session was used by PAS in order to ensure consistency of

input by end users across different scenarios.

o The end user validation session took place in April.

o The results of the questionnaire were formulated, along with the

scenario steps, questionnaire and tool involved and documented in an

Appendix to the D6.2 deliverable.

The overall results of the end user validation sessions were collated and documented

in the Appendix of deliverable D6.2. The results were consistent across all the end

user validation sessions and illustrated quite a positive response by the end users.

The results also showed that the original user requirements were captured

satisfactorily within the platform.


The end user validation session required a fully functional SECTOR CIS

environment even though integration and testing of the SECTOR CIS was still in

progress.

There was a lack of formal answers to the questionnaires provided to the SSV

end users during the workshop, instead general feedback was provided instead.

The availability of Copernicus satellite disaster analysis for multiple end users’

scenarios was limited and alternatives were suggested.

Given resource constraints, the SECPLAN decision support tool was not

incorporated in the original IAEMO / PSNI scenario but was included in the PAS

scenario.

2.7 WP7: Ethical and societal impact assessment

This WP is led by IZEW, with an overall duration of 36 months (from M1 July 2014 to

M36 June 2017) and includes the sole participation of IZEW. WP7 aims at providing

a comprehensive analysis of the ethical and human rights aspects arising from

SECTOR field of research (i.e. transnational crisis management), the tasks

performed within the SECTOR project and the design and functioning of the

SECTOR CIS. The WP is thus divided into three tasks. Task T7.1 was closed before

the reporting period with delivering an ethical and social impact assessment of the

D1.10

Annual Report

Version 1.0

Date 12.06.2017



technology under development within SECTOR. The work done in the reporting

period within tasks T7.2 and T7.3 is reported in the following.

T7.2 – Ethical monitoring of the project’s activities – led by IZEW with the sole

contribution of IZEW aims at monitoring the activities performed throughout the

SECTOR lifecycle that may have the potential to raise critical ethical, legal and social

issues.


1. All project activities were monitored through participation in communication,

telephone conferences and meetings of the respective WPs.

2. The monitoring tables developed in D7.1 and updated in D7.3 have been

reassessed and revised on a regular basis.

T7.3 – Ethics and privacy by design workshop – led by IZEW with the sole

contribution of IZEW. The ethics and privacy-by-design workshop took place on 1

December 2016 in Rome in cooperation with the progress and integration meetings.

In this workshop, the technical developers of SECTOR had the unique opportunity to

collectively discuss with an external expert how the main ethical, privacy and data

protection aspects can be taken into account in the design, implementation and

validation of the SECTOR CIS. We invited Dr. Nolen Gertz from 4TU.Centre for

Ethics and Technology, the Netherlands, one of the leading European institutions

studying ethical issues in the development, use and regulation of technology to act

as the expert in the workshop. Through presentations and discussions, important

ethical and privacy-related issues could be addressed and an evaluation of the

existing consideration of privacy by design during the already conducted technical

development was undertaken. The content and results of the workshop has been

reported in deliverable D7.5.


1. Identification of possible experts, invitation and organisation of the participation.

2. Identification of core issues, relevant content and scope of the workshop.

Preparation of a concept for the privacy by design workshop including some

revisions and adjustments as needed. Close collaboration with the expert on the

final concept.

3. Several phone calls and communication with the expert in order to prepare the

workshop.

4. Organisation of the venue with the help of local partners.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



5. Organisation of the participation of the technical developers and the technical

contributions to the workshop.

6. Realisation of the workshop, introduction and participation in the discussion.

7. Reporting of the workshop results.


The reviewers asked the consortium to dedicate more effort to legal issues of the

introduction and implementation of a SECTOR CIS. It has to be noted that the

DoW does not foresee an analysis of legal issues related to the application and

potential use of a SECTOR CIS and the legal aspects of data sharing among

countries. Nevertheless, as a response to the remarks, a preliminary overview of

legal aspects of the implementation has been included as an annex to D7.5.


1. D7.4 “Ethics Monitoring Final Report”, delivered at M35 and is the main outcome

of T7.2 in the reporting period. It is an update and extension of the previous

interim reports D7.1 and D7.3 and summarizes the ethical assessment of the

research and development activities undertaken in the SECTOR project. The

assessment is based on high ethical standards presented in the deliverable, such

as autonomy, beneficence, non-maleficence, justice, privacy and data-protection,

dual use as well as well-being. There were no critical ethical concerns identified

within the reported period (M25–M36) and, to summarize, in the complete project

lifecycle. However, some aspects with regard to the implementation of the Google

Person Finder, SECPLAN and the demonstration event have been highlighted.

Responses or mitigation strategies as well as specific further action has been

suggested with regard to every task where ethical issues and concerns were

identified.

2. D7.5 “Ethics and privacy by design workshop report”, delivered at M35 reported

on the main event of Task T7.3, the ethics and privacy by design workshop that

took place on 1 December 2016. The workshop was a successful event with

fruitful and interdisciplinary discussion. In the report, the main topics and relevant

issues of discussion are reported, e.g. different concepts and strategies of privacy

by design, already implemented privacy sensitivity and points for further

improvement.

Furthermore, this report includes an annex that is dedicated to legal aspects that

are important for the implementation and application of the SECTOR CIS.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



2.8 WP8: Standardisation, exploitation and dissemination

The WP is led by ITTI SP.ZO.O (ITTI), with an overall duration of 36 months (from

M1 July 2014 to M36 June 2017), and includes the participation of LEONARDO, FOI,

THALES, ASELSAN, ITTI, SAADIAN, PSNI, PAS, IAEMO, SGSP, USTUTT, UPVLC,

CINI, EGEOS and SSV.

The overall objectives of WP8 include a creation of an exploitation plan (T8.1). The

final version of the document features a comprehensive market analysis as well as

identification of potential commercialization and exploitation channels for the

prototype. Furthermore, work involved impacting European standards. SAADIAN

compiles, as a part of T8.2, a set of recommendations and good practices for the

entities involved in crisis management, to facilitate interoperability should a disaster

occur. Moreover, the crucial part of the WP is dedicated to active dissemination the

project goals and achievements (T8.3). Project partners have been disseminating the

project via multiple channels in order to reach diversified audience groups. The

hereby report presents the progress of work within WP8 in the period M25-M36.

Moreover, a short overview of WP8 activities performed in the period M1-M24 is

given below.

The major actions performed in the period M1-M24 include the following points:

As a part of T8.2, major activities included:

o Organisation and realisation of the "European Security Research - The

Next Wave" (ESR) event in Dublin in November 2015, over 3 days as

well as during the build-up. The event was supported by the National

Standards Authority of Ireland.

o Vision, organisation, lobbying CEN/CENELEC, National Standards

Authority of Ireland, the European Commission, encouraging individual

projects' participation, planning, securing best venue,

promotion/awareness, communications, monitoring and multiple

engagements during the planning for the ESR event.

As a part of T8.3, SECTOR was represented and promoted at numerous

events including Community of Users (24-25 November, 2014 – Brussels,

Belgium), SECTOR Workshop (1 April, 2015 – Paris, France), SECTOR

Workshop (9 April, 2015 – Rome, Italy), Theoretical categories and practical

elements of national security – scientific conference (28 April, 2015 – Warsaw,

Poland), 2nd Community of Users (5 May, 2015 – Brussels, Belgium),

DOMINO Conference (20-22 May, 2015 – Brussels), 12th International

Conference on Information Systems for Crisis Response and Management

(ISCRAM 2015, 24-27 May, 2015 – Kristiansand, Norway), Public Safety

Communication Europe (PSCE, 27-28 May, 2015 – Graz, Austria), Future

Security 2015 (held in Berlin on 15-17 September, 2015), CENTERIS –

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Conference on ENTERprise Information Systems (in Vilamoura on 7-9

October 2015), European Security Research: The next wave (held in Dublin

on 4-6 November, 2015), COBACORE’s project workshop held in Leiden (The

Netherlands) on the 1st of March, 2016.

As a part of T8.3, the following SECTOR related papers were published:

o Cinque M., C. Esposito, M. Fiorentino, J. Mauthner, Ł. Szklarski, F.

Wilson, Y. Semet, and J.-P. Pignon. „SECTOR: Secure Common

Information Space for the Interoperability of First Responders”,

Conference on ENTERprise Information Systems, available at Procedia

Computer Science (2015) 64: 750-757

o Cinque M., D. Cotroneo, C. Esposito, S. Russo, M. Fiorentino, M.

Fiorini, V. Esposito and S. Di Domenico, “Confidential Crisis Information

Sharing through an Interoperability Framework among First

Responders: A discussion and a preliminary solution”, Proc. of

European Intelligence & Security Informatics Conference (EISIC) 2016,

Uppsala, Sweden, 17-19 August 2016, pp. 1-4

o Mauthner Jana, Sandra Frings, Wolf Engelbach, Łukasz Szklarski, Piotr

Gmitrowicz, Yann Semet, and Frank Wilson. „SECTOR: Secure

Common Information Space for the Interoperability of First

Responders”, Paper presented at Future Security 2015 Conference in

Berlin.

o Szklarski Łukasz, Rafał Renk, Piotr Gmitrowicz, Mateusz Oleś and

Sandra Michalska. „SECTOR’s Common Information Space for

Partnership and Bridging in Response Phase”, published in The

BaltPrevResilience Monograph Report on Awareness Rising, Bridging

and Building Community Resilience in the Baltic Region. Edited by:

Zwęgliński Tomasz, Paweł Gromek, Magdalena Gikiewicz, and Anna

Prędecka.

The following points present the progress of work between M25-M36:

T8.1 - Exploitation plan - led by ITTI SP.ZO.O (ITTI) in cooperation with

LEONARDO, FOI, THALES, ASELSAN, ITTI, SAADIAN, PSNI, PAS, IAEMO and

SGSP this task aims at the development of an exploitation plan.


1. Carrying out an in-depth analysis of the market. The analysis focused on the

existing problems in crisis management domain such as interoperability problems

D1.10

Annual Report

Version 1.0

Date 12.06.2017



and cross-border cooperation. Furthermore, it has been indicated how the defined

problems could be solved by SECTOR platform. The analysis also pinpointed

potential competitive products and prospective clients/target group to whom the

software could be dedicated. The analysis has been included in D8.6.

2. Preparation of a detailed SWOT (Strengths, Weaknesses, Opportunities, and

Threats) analysis of the SECTOR platform. The analysis combined both technical

aspects of the software as well as non-technical view.

3. Definition of a SECTOR business Model Canvas, which is presented in D8.6.

4. SECTOR consortium partners prepared individual exploitation plans, which

contain description of the exploitable results as well as their exploitation strategy.

No main issues were encountered during the reporting period.


1. D8.6 Final dissemination and exploitation plan, M35 (the deliverable was

originally supposed to be submitted in M33, however it got delayed in order to

cover dissemination events held in April and to provide necessary time for

partners to clarify individual exploitation plans).

T8.2 - Contribution to Policy Making, Best Practices and Standards - led by

SAADIAN TECHNOLOGIES LIMITED (SAADIAN) in cooperation with CINI,

USTUTT, ASELSAN, UPVLC, FOI, ITTI, PSNI, IAEMO, SGSP and SSV this task

aims at the overall improvement of standards and policies related to crisis

management.


1. Close engagement with DIN (German Institute for Standardization) as Secretary

and with EPISECC for the development and advancement of the CEN Workshop

Agreement and Project Plan on Terminologies in Crisis and Disaster

Management. A blog was produced on the 3rd November 2016 to support our

ongoing work on Standardization. To date, it received 82 views and 8 likes. Blog:

https://www.linkedin.com/post/edit/standardization-helping-make-work-better-

future-tom-flynn

2. The CWA kick off meeting is planned for February 2017 with a view to finalising

the CWA by August 2017. Tom Flynn (SAADIAN) is an editor of the CWA and

was appointed the vice-chairman. Input contributions received from both FOI and

USTUTT.

https://www.linkedin.com/post/edit/standardization-helping-make-work-better-future-tom-flynn

https://www.linkedin.com/post/edit/standardization-helping-make-work-better-future-tom-flynn

D1.10

Annual Report

Version 1.0

Date 12.06.2017



Figure 2 - Members of CEN/TC 391 with SECTOR members

3. Separately, SECTOR is actively contributing to the development of the draft CEN

Crisis Management – Guidance for developing a strategic capability – standard,

which led by SAADIAN is ongoing and contribution to the advancement of the

standard have been received from USTUTT. Work is ongoing on the drafting of

the standard through the CEN/TC 391 working committee. The 2nd draft of the

standard is presently released at national level for review. The drafting process

will continue into 2017.

4. Significant work was implemented during this period with regards to

standardization. For instance, SAADIAN was heavily active in the work being

conducted for the development of the CEN workshop agreement document on

Terminologies in Crisis and Disaster Management, which involved the related

Common Information Space projects of EPISECC, SecInCore and REDIRNET.

The development of this CWA is important because during the management of

large scale crisis1 and past disasters2, it turns out that not only language barriers,

but also differences in understanding of the terms applied in crisis and disaster

management (difference of applied definitions of same terms) as well as use of

different terms for the same parameters hamper the success of effective

information exchange. By providing a contextual3 enriched overview on terms and

definitions provided by different type of organizations such as a standardization

organization or the United Nations, this initiative is aimed at improving the current

common information space situation of crisis and disaster management,

especially for those situations that involve cross-agencies and cross-borders.

Tom Flynn (SAADIAN) was the vice-chairperson of the CWA and Editor of the

CWA Project Plan, supporting in particular the Austrian Institute of Technology

(EPISECC, chairperson) and DIN (Secretariat). FOI and USTUTT have also been

1 In this document “crisis” is defined according to Crisis management – Guidance and Good Practice

prEN11200:2014 “crisis abnormal and unstable situation that threatens the organization’s strategic objectives, reputation or viability”.

2 see for instance Neubauer et al, “A methodology to analyse interoperability in crisis and disaster

management”, IDIMT 2015.

3 Contextual means provision of information on the source of the data (e.g. ISO, UN, DIN,..), intended

user group (e.g. first responders, CI operators) and area of application (e.g. natural disasters, large scale accidents,..).

D1.10

Annual Report

Version 1.0

Date 12.06.2017



active in supporting SAADIAN in the development of the CWA. The Project Plan

was approved by CEN in March 2017 in Brussels of which SAADIAN represented

the interest of the project at the kick off meeting with CEN/CENELEC. The

development of the CWA is expected to be finalised by September 2017 and Tom

Flynn will continue to support the development of the CWA beyond the life of the

SECTOR project.

5. SAADIAN has also been active in the development and advancement of the Crisis

Management – Guidance for developing a strategic capability TS *(Technical

Specification) standard, which is being driven by CEN TC 391 / WG3 group. This

standard sets out the principles and good practice for the provision of a crisis

management response, delivered by strategic decision-makers of any

organization of any size in the public or private sector. The intention of the

technical specification is to aid the design and/or ongoing development of an

organization’s crisis management capability. The work is being undertaken in line

with the Commissions’ Mandate 487. Reviews of the TS are ongoing and

advancements to the standard will be made beyond the life of the SECTOR

project.

6. Tom Flynn will continue with this work at national level to continue to influence

standards and policy. Under the working group on crisis management standards

formed by him, the National Standards Authority of Ireland will host the CEN TC

391 in Dublin, November 2017, to continue with the advancement of

standardization in the area of Crisis Management. It is believed that the TS will

be finalized at the Dublin meeting if not before.


1. Contribution to the CWA was not part of the original DoW.

No deliverables were submitted during the reporting period.

T8.3 - Dissemination - led by ITTI SP.ZO.O (ITTI) in cooperation with LEONARDP,

UPVLC, ASELSAN, FOI, CINI, SAADIAN, EGEOS, USTUTT and THALES this task

aims at effective dissemination of the project goals and achievements.


1. Standardization meeting between representatives of SECTOR and EPISECC

projects, German Institute for Standardization as well as CEN/CENELEC.

2. Domino II Workshop (Cascading Effects) held in Tiel from 20th to 21st

September, 2016 – Presentation of the SECTOR project innovations and practical

session showing capabilities of the platform to gathered guests

D1.10

Annual Report

Version 1.0

Date 12.06.2017



3. SECTOR dissemination at Community of Users in the Disaster Risk and Crisis

Management sectors (CoU) on 10 October, 2016 in Brussels

4. Promotion of the project at the DESTRIERO project Dissemination Day, 19th

August 2016, in Dublin.

5. Task Forces Joint Event – meeting on Common European Space – Cluster of

European Projects for Enhanced Interoperability. The meeting was held on 28th

February 2017 in Brussels and it featured four FP7 projects such as EPISECC,

ReDIRNET, SecInCoRe, and SECTOR. The event was held in order to address

the aspects of interoperability, interconnectivity and intercommunication of

European systems for crisis and disaster management. All of the four

aforementioned projects were to demonstrate the concept of Common

Information Space, its possible realisation and to collect feedback from

organisations at European level.

6. SECTOR final demonstration – the event was held on 5th April, 2015 in Rome.

The objective of the event is to demonstrate and validate the CIS concept

developed through previous project tasks. Demonstration has been supported by

end-users’ validation activities, simulations involving information sharing among

different agencies and organisations. The project partners have supported end-

users and provided assistance to interact with the CIS. The output of the

validation activities has provided a mean to ensure and quantify the quality of the

prototype CIS.

7. SECTOR Dissemination Day – the workshop event has been conducted as a

part of the 7th Community of Users event in Brussels on 17th May, 2017. The

meeting has been the final event, which featured SECTOR Common Information

Space presentation to the public and the targeted community. Led by SADDIAN,

the workshop event was planned, designed and implemented with the support of

two other projects in the CIS space – EPISECC and SecInCoRe.

8. SECTOR website updates (new articles published).

9. SECTOR social media (Twitter and LinkedIn) regular updates.

No main issues were encountered during the reporting period.


1. D8.5 Second Dissemination Report, M27 (T8.3), submitted on time.

2. D8.7 Project Dissemination Day Report, M36 (T8.3), submitted on time.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



3 Conclusion

The SECTOR project has come to its official conclusion reaching two very important

achievements during its final phase:

1. Completion and release of the SECTOR CIS.

2. Demonstration of the usefulness of the SECTOR CIS Concept and of the

developed systems (Demonstration Day and Dissemination Event).

These two points, excellent results by themselves, are even more impressive looking

at the history of the project that faced a very difficult period at the very beginning

incurring in delays and in unclear project objectives definition.

As is often the case, the consortium has come out enforced from this critical phase,

reorganizing the activities and the roles and improving internal communication and

refining continuously the recovery plan in order to mitigate risks and overcome

difficulties. This has probably been the key for achieving the very good results

obtained in the end.

The high interest showed by users even at a very early stage of developments

(DOMINO II event, in Tiel, September 2016) and the wide attendance registered at

Demonstration Day and Dissemination Day events have, in facts, demonstrated the

very level of innovation and brought by the SECTOR solution.

Moreover, a high-level analysis of the collected feedbacks demonstrates that:

The system has been perceived as very useful in support to activities of during

preparedness phase and during the crisis management thanks to the CIS

capability to share real-time data and information and improve the

communication process.

The high level of integration of the CIS infrastructure, allowing user to maintain

their own systems and tools is a major breakthrough, enabling a concrete

adoption of the system by Organization and Agencies involved in crisis

management.

There is a strong interest on the system evolution and on testing the current

version in order to explore the integration opportunities with the third party

systems.

Therefore, even if the system should be considered at a prototype level as overall

maturity, the strong input received from the market of possible users is to finalize the

solution in order to make it available as soon as possible.

D1.10

Annual Report

Version 1.0

Date 12.06.2017



References and Applicable document

AD1. Sector DOW(607821)-2014-03-13

AD2. SECTOR (607821) Consolidated Review Report 1st project review

AD3. SECTOR (607821) Consolidated Review Report (ad hoc review)

AD4. SECTOR (607821) Signed Amendment Ares (2016) 2224664

R1. D1.1 Project management Plan

R2. D1.2 Project Implementation plan

R3. D1.3 User Group Definition and Management

R4. D1.4 Quality Plan and provision of information provided for ethical

approvals

R5. D1.5 Interim Monitoring Reports and ethical issues

R6. D1.6 Interim Monitoring Reports

R7. D1.8 Annual Report

R8. D1.9 Second Annual Report

R9. D2.1 Activity Report on Information gathering of past critical events

R10. D2.2 Activity Report on Information gathering of data sets, procedures

and tools

R11. D2.3 Analysis of information on past events

R12. D2.4 Analysis of information on data sets, procedures and tools

R13. D2.5 Organizations Business Model analysis

R14. D2.6 Results of standards and technologies use survey

R15. D3.1 Scenario definition

R16. D3.2 User requirements formalization

R17. D3.3 Data requirement analysis

R18. D3.4 User requirements tracking



R21. D4.1 A common taxonomy/data model for European Collaborative

Crisis

Management

D1.10

Annual Report

Version 1.0

Date 12.06.2017



R22. D4.2 Network enabled communication system design

R22. D5.1 Crisis Management Model Development Report

R23. D5.2 SECTOR CIS Implementation Report

R24. D6.1 Validation Plan

R25. D6.2 Test Report

R26. D7.1 Ethics monitoring internal interim report 1

R27. D7.2 Ethical and Societal Impact review report

R28. D7.3 Ethics monitoring internal interim report 2

R29. D7.4 Ethics monitoring final report

R30. D7.5 Ethics and privacy by design workshop report

R31. D8.1 Initial Dissemination and exploitation Plan

R32. D8.2 Project web-site

R33. D8.3 Project presentation (leaflet)

R34. D8.4 First Dissemination Report

R35. D8.5 Second Dissemination Report

R36. D8.6 Final Dissemination and Exploitation Plan

R37. D8.7 Project Dissemination Day

D1.10

Annual Report

Version 1.0

Date 12.06.2017



ANNEXI - Monitoring Participant Forms

See attachment.

Documents

Deliverable D1. 10 Annual Report Final version · 2017-06-16 · D1.10 Annual Report Version 1.0 Date 12.06.2017 Document History This project has received funding from the European