safeguarding cultural heritage through technical and … · 2017-05-12 · safeguarding cultural...

This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement n°700191

Safeguarding Cultural Heritage through Technical and Organisational Resources

Management

D12.1 Quality Plan

STORM Project

H2020- DRS-11-2015: Disaster Resilience & Climate

Ethical/Societal Dimension Topic 3: Mitigating the impacts of climate change and natural hazards on Cultural Heritage sites, structures and artefacts

Grant Agreement n°: 700191

Start date of project: 1 June 2016

Duration: 36 months

Document. ref.: D12.1/ENG/WP12/V 1.0

D12.1 : Quality Plan

H2020 – DRS11 - 700191 2

Disclaimer

This document contains material, which is the copyright of certain STORM contractors, and may not be reproduced or copied without permission. All STORM consortium partners have agreed to the full publication of this document. The commercial use of any information contained in this document may require a license from the proprietor of that information. The reproduction of this document or of parts of it requires an agreement with the proprietor of that information. The document must be referenced if is used in a publication.

The STORM Consortium consists of the following partners:

Participant No

Participant organisation name Partic. short name

Country

1 (Coord.) Engineering – Ingegneria Informatica S.p.A. ENG IT

2 INOV Inesc Inovação - Instituto de Novas Tecnologias INOV PT

3 Foundation for Research and Technology, Hellas FORTH GR

4 Technological Educational Institute of Piraeus TEIP GR

5 Resiltech RESIL IT

6 Soprintendenza Speciale Per il Colosseo il Museo Nazionale Romano e l’area Archaeologica di Roma

SSCOL IT

7 Università della TUSCIA TUSCIA IT

8 Kpeople ltd, KP UK

9 University of Stuttgart USTUTT DE

10 Ministero degli Interni - Corpo Nazionale Vigili del Fuoco

CNVVF IT

11 Mellor Heritage Trust’s MAT UK

12 Sparta technologies SPA UK

13 Salford University (Archaeology, Climatology) USAL UK

14 Nova Conservacao NCRS PT

15 Troiaresort – Investimentos Turísticos, S.A. TRO PT

16 Portuguese General Direction of Cultural Heritage DGP PT

17 Município de Grândola – Serviço Municipal de Proteção Civil

SMPC PT

18 Zentralanstalt für Meteorologie und Geodynamik ZAMG DE

19 Ephorate of Antiquities of Rethymno, Hellenic Ministry of Culture, Education and Religious Affairs

EFARETH

GR

20 Bogazici University BU TR


H2020 – DRS11 - 700191 3

PROGRAMME NAME: DRS-11-2015

PROJECT NUMBER: 700191

PROJECT TITLE: STORM

RESPONSIBLE PARTNER: ENG

INVOLVED PARTNERS:

DOCUMENT NUMBER: D12.1

DOCUMENT TITLE: Quality Plan

WORK-PACKAGE: WP12

DELIVERABLE TYPE: Report

CONTRACTUAL DATE OF DELIVERY:

LAST UPDATE:

DISSEMINATION LEVEL: CO

Dissemination level:

PU = Public,

CO = Confidential, only for members of the STORM Consortium (including the Commission Services)


H2020 – DRS11 - 700191 4

Document History

VERSION DATE STATUS AUTHORS, REVIEWER DESCRIPTION

v.1.0 09/08/2016 Draft ENG Draft version

v.1.1 25/08/2016 Draft TEIP First draft

v.1.2 31/08/2016 Final ENG Final version


H2020 – DRS11 - 700191 5

Definitions, Acronyms and Abbreviations

ACRONYMS / ABBREVIATIONS DESCRIPTION

GA General Assembly

IMB Innovation Management Board

PD Project Director

QP Quality Plan

ToC Table of Contents

WPL Work Package Leader


H2020 – DRS11 - 700191 6

Table of Contents

1 General issues concerning quality .................................................................................... 10

2 Organizational structure of the project for quality assurance and management .............. 11

2.1 Quality Control Activities .............................................................................................. 12

3 Co-ordination between the partners .................................................................................. 14

4 Planning and control .......................................................................................................... 15

4.1 Planning and control .................................................................................................... 15

4.1.1 Supplementary Reports ..................................................................................... 16

4.1.2 Evaluation Process ............................................................................................ 17

5 Control of the documentation ............................................................................................ 18

5.1 Language ...................................................................................................................... 18

5.2 STORM public and Private web sites .......................................................................... 18

5.3 Documents exchange methods ................................................................................... 18

5.4 List of templates to be used ......................................................................................... 18

5.4.1 Template for deliverables ................................................................................... 19

5.5 Files and Archives ........................................................................................................ 19

5.6 Documents Naming ...................................................................................................... 19

5.6.1 Deliverables ........................................................................................................ 19

5.6.2 Other Documents ............................................................................................... 20

5.7 Process for peer review and control of non-conforming of deliverables ..................... 20

5.8 Publications, Presentations, Papers ............................................................................ 21

ANNEX 1 – List of Deliverables ............................................................................................... 22

ANNEX 2 – List of Milestones .................................................................................................. 29

ANNEX 3 – Action List Template ............................................................................................. 31

ANNEX 4 – Deliverable Template ........................................................................................... 32

ANNEX 5 – Deliverable Peer-Review Report Template ......................................................... 35

ANNEX 6 – STORM Leaflet Template..................................................................................... 38


H2020 – DRS11 - 700191 7

List of Figures

Fig. 1: Overall Organizational structure of STORM ................................................................. 11

Fig. 2: WP Leaders group ........................................................................................................ 12


H2020 – DRS11 - 700191 8

List of Tables

Table 1: Steps for the preparation of deliverables ................................................................... 16

Table 2: List of deliverables ..................................................................................................... 28

Table 3: List of milestones ....................................................................................................... 30

Table 4: Action ListTemplate ................................................................................................... 31


H2020 – DRS11 - 700191 9

Executive Summary

The goal of this document is to set-up the rules and procedures in order to produce high-quality deliverables and reports of the STORM project, so as to guarantee that the outcomes of the project meet its objectives and are of high quality. Additionally, the quality plan will determine the specific arrangements for controlling the developments that are made in the several design and development centres of STORM partners.

This deliverable will describe the planning and reporting throughout the project, as well as refer to all issues related to documentation, such as repository for exchanging documents, language, template documents, deliverables review process and scientific publications.


H2020 – DRS11 - 700191 10

1 General issues concerning quality

Quality in an EC-funded integration project, such as STORM, should be addressed not only in deliverables and reporting but also in prototypes, demonstrations and for the project process itself.

The management process shall be submitted to periodical reviewing with respect to:

Adequacy of the project management procedures and how the work performed complies with it, including IPR management and results dissemination,

How well the project processes are synchronized and inter-linked,

Identification and evaluation of activities and results that would adversely affect the achievement of the project objectives,

Process improvement in the project by identifying deviations and changes.

The WP Leader group will continuously monitor and control in cooperation with the project management (i.e. taking corrective actions) expenses, resources and schedules versus plans (i.e. technical and financial annexes to the EC Grant Agreement). This is done through:

The Interim Management Reports (every 9 months – in the middle of each periodic review)

The periodic review to be performed every 18 months, and the Final Report at the end of the project.

Any deviations in costs, resources or schedules will be identified, recorded and used as input for continuous improvement. Possible impacts on the schedule, changes on the budget and resources of the project and on the quality of the product should be determined.

All these procedures are based upon consensus decision-making procedures; in case of conflict, decisions should be submitted to the General Assembly .


H2020 – DRS11 - 700191 11

2 Organizational structure of the project for quality assurance and management

Large European integration projects such as STORM are complex organizations, where entities with different backgrounds, culture and interests join forces and know-how to achieve common goals. For a successful completion of the project, a functional organizational structure is essential to ensure efficient, result-driven management. The following image describes the organizational structure of STORM.

Fig. 1: Overall Organizational structure of STORM

The EPM is responsible for the day-by-day project management of the entire project. It consists of the following entities:

Project Director (PD) : The PD is the intermediary between the Commission and the Consortium. The PD is responsible for the project control, for administrative and financial reporting, project time control, coordination issues and overall IP activities (e.g. training, dissemination) and is also responsible for the overall technical management and technical coordination within and between work packages. The PD is the direct contact point to the Work Package Leaders (WPLs). The WPLs send all technical progress reports to the PD. The is also responsible for the correct application of all EU rules, particularly concerning the handling of payments and maintenance of accounts.

Secretariat: the secretariat provides secretarial, administrative, financial and legal support to the PD. The Secretariat will be a permanent contact person who also supports project participants, WPLs and EAC members.


H2020 – DRS11 - 700191 12

WP Leaders group: the WP Leader group consist of a senior team. In Figure 2 the STORM composition.

Fig. 2: WP Leaders group

General Assembly (GA): All partners of the Consortium are represented in the GA via one senior reprehensive from each of the partner organization (with the necessary delegated authority to make decisions on behalf of their organization with respect to the project). The GA takes final decisions on the Consortium Agreement. The IP Coordinator will keep the GA informed about progress and achievements. The GA shall solve conflicts within the Consortium that cannot be resolved by the EPM or the PD. The GA meets regularly twice a year, and if more than 30% of the GA members require it. It can take decisions by correspondence. The PD will chair the GA

Innovation Management Board (IMB): Innovation is the change that brings a novelty in the previous practice as proposed by STORM tool. Innovation management is crucial for the success of the project therefore an Innovation Management Board (IMB) shall be composed of high-profile business and innovation managers recruited from the Consortium partners. The IMB when necessary will be consulted about the protection of privacy and personal data, as well as other ethical issues. As a sub division of IMB: Exploitation Advisory Committee (EAC): A specific committee, chaired by the Project Coordinator, addressing market reach procedures and exploitation of technologies will be specifically considered for the STORM project The EAC shall develop concrete proposals on how new business may be generated and how exploitation should be organised from the project results. Any PMC member can propose EAC members. The PMC decides regarding the composition of the EAC. IMB will cover also Management of Intellectual Property Rights: The Consortium Agreement will specify how IPR will be managed.through a IPR Audit Committee (IAC) that will meet at least once a year or upon request by the GA, to ensure that IPR issues are addressed.

2.1 Quality Control Activities

The Quality control of activities and deliverables are of main importance to the STORM project. The Quality Plan (QP) – this report – is issued early in the project aiming at describing the actions and measures that will be taken by the Consortium, in order to ensure the quality of the project and its full conformance with its contractual requirements. The aim of the QP is to:

1. Provide to all concerned a guide for the actions required by each one involved in the project work and deliverables,

2. Exhibit the performance of the project’s quality plan in accordance to the contractual requirements,

3. Decide which internal members of the Quality Control Board will review deliverables and provide the corresponding assignment of responsibilities (see below).


H2020 – DRS11 - 700191 13

The QP is applicable to all the project’s activities, and a strict compliance with the QP is mandatory for all parties involved.

The QP is documented and authorized by the Executive Project Management (EPM). All subsequent changes are approved by the WP Leader group and submitted to the Project Director for approval. The description of the quality system will focus on the prevention of deviations during each task of the project.

The EPM is responsible for the co-ordination and supervision, regarding the implementation of the measures for the quality assurance. specifically the WP Leader group is responsible for:

Overviewing the reports produced in the project;

Controlling the timely and good execution of the project work;

Controlling and assuring the conformity of all deliverables with specifications described in the project Description of Work and with additional criteria defined throughout the lifetime of the project;

Consulting the Work Package Leaders and providing them with guidance on the expected technical and scientific achievements in the deliverables;

Defining project deliverable review process and appointing the corresponding reviewers;

In accordance with the contractual agreements, the project’s quality management plan, this report has been prepared in order to define organizational structure, flow of the quality system and the quality management procedures to be applied.

The list of reviewers for each deliverable will be kept updated in the Internal Collaboration Platform (http://demo-storm.eng.it ).

In the case that shortcomings in quality are encountered, the responsible task leader will be informed within a pre-defined period (max. 2 weeks), in order to be able to make amendments. The review will be done on basis of the QP.

http://demo-storm.eng.it/


H2020 – DRS11 - 700191 14

3 Co-ordination between the partners

An important key of success for the STORM project is to ensure a good communication among project partners and towards outside entities. A fast, reliable, and easily accessible communications infrastructure is crucial for the proper operation within a large-scale pan-European project. This will be realised through the intensive use of electronic communications (e.g., email, web based exchanges). A project web site, in particular the collaboration platform within the private area, will also be used to enable fast and efficient exchanges of information.

Additionally, WP leaders should keep an updated list of actions, detailing the open issues of their WP, the severity of the task, the deadline (probably a new deadline if the task is for a reason postponed), the name or initials of the responsible assigned with the task, a small description and the issue status, according to the following list:

open, assigned, closed, postponed, delayed

A template Action List is available in ANNEX 3.


H2020 – DRS11 - 700191 15

4 Planning and control

The infrastructure chosen to hold the documentation produced by the project (interim reports, cost statements, working papers, and deliverables) will be based on an online portal and collaboration platform. This is available at the following link: http://demo-storm.eng.it/

The Project Director will be responsible for maintaining the following kinds of libraries, respectively, to be kept on the portal:

Document Library (All WP documentation including deliverables, internal documents, bibliography..)

Event Library (each event (internal meetings, project meetings, dissemination meetings, cals,,,) will be recorded in the internal website)

Moreover, in order to limit any duplication of information and to facilitate an efficient communication process by both real and virtual channels, the distribution of all relevant project information will be channelled to one key person for each partner. This person will act as partner switchboard, thus ensuring that the concerned person within its organisation is reached by the communication.

4.1 Planning and control

The foreseen reporting procedures for the STORM project are the following:

The responsible partner/author should begin at least 60 calendar days before the deadline with the presentation of initial Table of Contents (ToC).

After input, editing, emails and iterations, the leading author should deliver the final document to the internal reviewers two weeks before the deadline.

The internal reviewers will deliver the final document to the Technical & Quality Manager one week before the deadline.

The Technical & Quality Manager will approve and send the final version to the Coordinator by the Deadline.

More specifically, the following steps will be followed for the preparation of deliverables:

Steps When1 Who What

1 60 Responsible partner – Editor

Table of Contents (ToC)

2 58 All involved partners Comments on ToC


Final ToC + Chapter Editors Responsibilities

4 54 Chapter Editors Assign Section Editors (if needed) and go to Step 6, or decline the responsibilities

1 This column shows the days before the contractual delivery date



H2020 – DRS11 - 700191 16

5 52 All involved partners Arrange phone conference for new Chapter Editors

6 45 Chapter/Section Editors

Send 1st input to the Responsible partner – Editor


Circulate the 1st version of the deliverable

8 42 All Agreement on deliverable progress


Send 2nd input to the Document Editor


Circulate the 2nd version of the deliverable

11 25 All Agreement on deliverable progress


Send final input to the Responsible partner – Editor


Circulate the pre-final version of the deliverable

14 15 All Agreement for the pre-final version

Two Document Reviews are assigned

15 12 Internal Reviewers Approve completeness and scientific part of the deliverable

16 10 Internal Reviewers Approve the syntactical and grammatical part

17 7 Technical Coordinator Approves and turns document to Final

18 1 Project Coordinator Approves and turns document to Final Frozen

Table 1: Steps for the preparation of deliverables

4.1.1 Supplementary Reports

In addition to the reports defined in the contract, the Project Coordinator will submit to the Commission Interim Management reports every nine months. These reports will provide, for the reporting period:

The technical progress and achievements of the project

The project status

Work started

Work completed


H2020 – DRS11 - 700191 17

Work delayed

Status of deliverables

Remedial actions required, if applicable

Resources expenditure by subproject, work-package and activity.

Absolute values for the reported period

Aggregated values (actual vs. planned)

4.1.2 Evaluation Process

The work progress of the STORM Project will be constantly monitored and supervised by the Project Management Group. In addition to that, evaluation meetings will be carried out to evaluate the work and progress of the project.

An internal peer review will be performed for each document produced, especially official deliverable. Each WP leader will submit all the produced documents to at least one appropriate expert internal to another partner organization, which is not involved in the same WP, to check for the quality of the documents produced. The deliverable review process is described below in section 5.7.

A basis for measuring the quality of the conducted work is the various measures of success specified in the work packages descriptions of the individual work packages (e.g. milestones, deadlines etc.). The academic and research partners are encouraged to target submission of papers to peer reviewed journals indexed in SCI or SCI expanded, having impact factors (unless they have been established recently), and to high impact conferences and workshops. Furthermore, the publication of achieved results in journals as well as European and international conferences will be taken as a measure of success for the involved universities and research teams.


H2020 – DRS11 - 700191 18

5 Control of the documentation

The documentation produced by the project will be hosted in an online portal and collaboration tool available at the following link: http://demo-storm.eng.it/

The Project Coordinator will be responsible for maintaining on the server:

• Interim Management reports

• Annual Project Reports

• Meeting Minutes

• Teleconference Meeting Minutes

• Contractual Documentation

• Deliverables

• Technical Reports

• Technical Papers

• Market Studies

• Any other relevant document and content

5.1 Language

The official language for documents and e-mail exchange will be English (UK). In case of official deliverables, participants that are native English speakers should peer-review the documents.

5.2 STORM public and Private web sites

The public STORM website will be available at the following link:

http://www.storm-project.eu/

Apart from general information about the project and related news and events, the public deliverables and documents will be available for download from this web site.

Regarding the documents with restricted access, the private STORM portal will be used:


and will be accessible only by the STORM partners and other authorized people (e.g. members of the advisory board, other relevant experts, etc.)

5.3 Documents exchange methods

Documents will be exchanged via uploading at the STORM private portal. After successful uploading of the document, the partner should also provide (via e-mail) the document title and link. In case document uploading is not feasible, e-mail exchange will be used instead.

5.4 List of templates to be used

The following templates are to be used for the preparation of STORM deliverables and reports. They are available on the project web site (private area) or from the Technical & Quality Manager or Project Coordinator.

Template for deliverables (already available – ANNEX 4)

Template “Peer-Review Report” (ANNEX 5)


http://www.storm-project.eu/



H2020 – DRS11 - 700191 19

STORM Leaflet template (ANNNEX6)

5.4.1 Template for deliverables

The official project deliverables should have a first page as for the reference/template in Annex 4. They should also use the page layout (headers / footers) suggested in the same Annex.

Furthermore, they should comply with the following rules:

Have a document history table;

Have a list of abbreviations used within the Deliverable;

Have a table of contents;

Have a list of Figures, if relevant;

Have a list of Tables, if relevant;

Start with one-page max Executive Summary;

End the main part with a Conclusions section of around 1 page; Include a References section after the Conclusions section.

5.5 Files and Archives

All “released” versions of the project deliverables are centrally stored for download on the project Web site, either in the “restricted” area for deliverables classified as “CO”, or in the public area for all deliverables classified as “PU”. Flexible access rights can be attributed alternatively.

5.6 Documents Naming

Proper document naming is essential in order to keep track of the project technical and administrative resources.

5.6.1 Deliverables

The official deliverable will be named using the naming format

STORM_Dw.d_YYYYMMDD_ACR_Vx.y.ext

where:

w: is the workpackage number

d: is the deliverable number

YYYY: is the year

MM: is the month

DD: is the day

ACR: is the partner Acronym that initiated and has the responsibility for the document

x: is the version major number

y: is the version minor number

ext: is the extension (.doc, .pdf, .ppt, .xls, .exe, .zip)

The partner that initiated and has the responsibility for the document will have the authority to change the version number. In case a partner aims to send comments on the document, track changes can be used, adding the partner’s acronym at the end.

STORM_Dw.d_YYYYMMDD_ACR_Vx.y_ACR2.ext


H2020 – DRS11 - 700191 20

After some iterations, the responsible partner (editor) will have the authority to change the version number and date.

When the deliverable is finalised, the partner that has the responsibility for it will have the authority to change the version number and date.

STORM_Dw.d_YYYYMMDD_ACR_FF.ext

Where FF represents the “Final Frozen” version, which cannot be modified, unless requested by the PO or the external reviewers appointed by the EC.

5.6.2 Other Documents

The STORM documents (public and private) will have the following format:

STORM_WPw_ShortTitle_YYYYMMDD_ACR_Vx.y.ext

where:

w: is the workpackage number

ACR: is the partner Acronym that initiated and has the responsibility for the document

ShortTitle: is an explanatory short title of the document

x: is the version major number

y: is the version minor number

YYYY: is the year

MM: is the month

DD: is the day

ext: is the extension (.doc, .pdf, .ppt, .xls, .exe, .zip)

5.7 Process for peer review and control of non-conforming of deliverables

The following procedure refers only to project deliverables and not to internal reports and other documents.

Each deliverable will be reviewed by at least one member of the Consortium who has not participated to that deliverable, acting as internal reviewer. He/she will evaluate the deliverable with respect to the following matters and must conclude whether the deliverable is internal accepted or not:

Deliverable contents

Relevance

Quality of achievements

Quality of presentation of achievements

Comprehensibility, spelling, etc.

Technical terminology

The relevant comments will be included in a Deliverable Peer-Review Report, as indicated in Annex 5.

The layout and format of the deliverable will finally be checked by the Quality Manager to assure a uniform layout. The final rating of the Deliverable draft will be marked as:

Fully accepted

Accepted with reservation


H2020 – DRS11 - 700191 21

Rejected unless modified properly

The deliverable under consideration/examination will be sent by the author (according to the timing defined in section (4.1) to the Coordinator, who will forward it to the reviewers.

The reviewers for each deliverable are listed in a table that will kept update by the Coordinator in the internal collaboration platform.

The reviewers will revise the deliverable and prepare the «Peer Review Report», which are all collected by the Technical & Quality Manager. The reviewers will also send back the deliverable with detailed comments, suggestions, and changes directly within the MS Word document by activating the “track changes” option.

The Quality Manager upon receiving the above reports will send them to the deliverable author with potentially some additional comments or suggestions in a separate Peer Review Report and/or directly within the MS Word document by activating the “track changes” option.

The main author of the deliverable has to send back the peer review report, where the "Author response" fields under each question are completed and the deliverable (two Word document: one with all changes visible and one cleaned and ready to be published). If needed, the author sends also a document with the summary of main feedback and actions taken, as a result of the comments in the Peer Review Reports.

5.8 Publications, Presentations, Papers

If a partner is about to submit for publication a part of work performed within the project, the partner shall inform the coordinator, the Technical & Quality Manager and the consortium members before the submission, by sending an email to them with the relevant information about that publication (titles, authors, abstract).

A written acceptance shall be returned to the partner (within 2 weeks) before he/she proceeds to the submission. Moreover, the participation in exhibitions through a stand and the presentation of demos of the project results require prior agreement of the whole project Consortium.

All publications, presentations, active participation to events etc. in the name of the project must be announced to the Coordinator and the Technical & Quality Manager and will be centrally documented. Updates need to be done in the respective tables in the interim reports. In addition, each partner shall fill in the respective template “Dissemination Form” which is available from the Coordinator and the Dissemination responsible.


H2020 – DRS11 - 700191 22

ANNEX 1 – List of Deliverables

Deliverable Number

Deliverable Title

WP numbe

r

Lead beneficiary

Type Disseminatio

n level

Due date (in mont-

hs)

D1.1 Current practice management and conservation of Cultural Heritage

WP1 7- UNITUS Report Public 9

D1.2 Non-invasive and non-destructive methods of surveying and diagnosis

WP1 2 - INOV Report Public 12

D1.3 Cost effective conservation and restoration methods

WP1 14 - NCRS Report Public 12

D1.4 Quick damage assessment methods

WP1 7 - UNITUS Report Public 12

D1.2 State of the art policies on government of Cultural Heritage against natural disaster and climate changes

WP2 16 - DGPC Report Public 6

D2.2 Safeguard of Cultural Heritage recommendations in

WP2 16 - DGPC Report Public 32


H2020 – DRS11 - 700191 23

government policies

D3.1 STORM use case and scenarios

WP3 15 – TROIA RESORT

Report Public 9

D3.2 System and User Requirements

WP3 4 - TEIP Report Public 12

D3.3 System Architecture

WP3 1 - ENG Report Public 15

D4.1 Report on the results of application of the ground-based sensors


D4.2 Operational software extractors from all major SN (explicit crowd sensing)

WP4 1 - ENG Demon-strator

Public 24

D4.3 Report about capabilities of the implicit crowd sensing: screening


D4.4 Sensor data collection and representation framework


D5.1 STORM Risk Management methodology

WP5 9 - USTUTT Report Public 18


H2020 – DRS11 - 700191 24

D5.2 STORM Risk Management tool

WP5 9 - USTUTT Demon-strator

Public 20

D5.3 Risk Management guidelines

WP5 18 - ZAMG Report Public 24

D6.1 STORM Models for the Contents Management


D6.2 STORM Report on Information Fusion Techniques


D6.3 STORM Event Stream Real Time Analysis for Situation Awareness

WP6 5 - RESILTECH

Report Public 24

D6.4 STORM Monitoring Services for Damages and Threats Detection

WP6 13 - USAL Report Public 30

D6.5 STORM Surveying and Diagnosis services

WP6 11 - Mellor Report Public 30

D6.6 STORM Damage Assessment and Decision Support Services

WP6 5 - RESILTECH

Report Public 30


H2020 – DRS11 - 700191 25

D6.7 STORM Integrated Solution for Situational Awareness and Decision Support

WP6 5 - RESILTECH

Demonstrator

Public 30

D7.1 Collaboration and Knowledge-sharing infrastructure definition


D7.2 Definition of knowledge-sharing tools

WP7 12 – SPARTA DIGITAL

Report Public 15

D7.3 Implementation of the collaboration and knowledge sharing infrastructure and tools

WP7 1 - ENG Demonstrator

Public 32

D7.4 Resilient communication services implementation


D7.5 Resilient communication services implementation

WP7 2 - INOV Demonstrator

Public 32

D7.6 Definition of crowdsourcing services and apps for crisis management


D7.7 Crowdsourcing services and apps


Public 32


H2020 – DRS11 - 700191 26

development

D7.8 Functional easy-to-use Web-GIS interface

WP7 3 - FORTH Other Public 15

D7.9 Web-GIS interface implementation

WP7 3 - FORTH Demonstrator

Public 32

D8.1 STORM integration planning


D8.2 Cloud based infrastructure definition


D8.3 Cloud base infrastructure implementation

WP8 4 - TEIP Demonstrator

Public 26

D8.4 Data analytics specification

WP8 14 - USAL Report Public 12

D8.5 Platform integration, testing and deployment v1


Confidential only for member of the consortium (including the Commission Services)

25

D8.6 Platform integration, testing and deployment


Public 32

D9.1 STORM Experimental Scenarios Definition and planning

WP9 6 - SS-COL Report Public 24

D9.2 Experimental Journal

WP9 11 - Mellor Report Public 24


H2020 – DRS11 - 700191 27

D9.3 STORM Assessment and Validation Midterm Report

WP9 7 - UNITUS Report Public 36

D10.1 Dissemination plan

WP10 8 – KPEOPLE LTD

Report Public 6

D10.2 Report on Dissemination activities v1


Report Public 18

D10.3 Final Report on Dissemination activities


Report Public 36

D10.4 Stakeholders Group Report v1


Report Public 18

D10.5 Final Stakeholders Group Report


Report Public 36

D10.6 Training plan

WP10 9 - USTUTT Report Public 24

D10.7 Training implementation report

WP10 10 - CNVVF Report Public 36

D11.1 Project viability analysis

WP11 8 - KPEOPLE LTD

Report Public 12

D11.2 Innovation Strategy plan


Report Public 12

D11.3 Sustainability model


Report Public 24

D11.4 Exploitation and Business plan


Report Public 36


H2020 – DRS11 - 700191 28

D12.1 Quality Plan WP12 1 - ENG Report Confidential only for members of the consortium (including Commissions Services )

3

D12.2 Management Website


Confidential only for members of the consortium (including Commissions Services )

3

D12.3 Data Management Plan

WP12 1 - ENG ORDP:Open Research Data Pilot

Confidential only for members of the consortium (including Commissions Services )

6

D12.4 1st Progress Report

WP12 1 - ENG Report Confidential only for members of the consortium (including Commissions Services )

9

D12.5 2nd Progress Report

WP12 1 - ENG Report Confidential only for members of the consortium (including Commissions Services )

27

Table 2: List of deliverables


H2020 – DRS11 - 700191 29

ANNEX 2 – List of Milestones

Milestone number

Milestone title

WP number Lead

beneficiary Due Date

(in months) Means of

verification

MS1 Overall STORM fundamentals

WP1, P10, WP11, WP2, WP3, WP6

7 - UNITUS 12 This milestone will be the result of D1.1, D1.2, D1.3, D1.4, D2.1, D3.1, D3.2, D6.1, D10.1, D11.1, D11.2

MS2 First prototype complete

WP10, WP3, WP5, WP6, WP7, WP8

1- ENG 18 The first prototype reflect the activities carried out in D3.3, D7.2, D7.4, D7.6, D7.8, D8.1, D10.2, D10.4, D5.1, D6.2, D7.1

MS3 In field evaluation of first prototype complete

WP10, WP11, WP4, WP4, WP6, WP9

4 - TEIP 24 This milestone report the integrated results of D5.2, D8.2, D4.4, D4.1, D10.6, D11.2, D11.2, D4.2, D4.3, D5.3, D6.3, D9.1, D9.2

MS4 Fully working, functionally complete version of the overall STORM platform ready

WP8 1 - ENG 28 This work will be the results of D8.5, D8.3, D8.4

MS5 Second and final fully working, functionally complete version of the overall STORM

WP10, WP2, WP6, WP8

2 - INOV 32 This milestone is the result of D6.4, D6.5, D6.6, D6.7, D10.6, D2.2, D7.3, D7.5, D7.7, D7.9, D8.5


H2020 – DRS11 - 700191 30

platform ready

MS6 Project complete

WP1, WP10, WP11, W9

1 - ENG 36 This milestones represents the fully achieved projects results. The main deliverable involved are D1.2, D1.3, D1.4, D10.3, D10.5, D10.7, D11.4, D9.2, D9.3

Table 3: List of milestones


H2020 – DRS11 - 700191 31

ANNEX 3 – Action List Template

The Action List will be kept as excel worksheet.

# Deadline Assigned to

Description

Status

New Deadline

Table 4: Action ListTemplate


H2020 – DRS11 - 700191 32

ANNEX 4 – Deliverable Template


H2020 – DRS11 - 700191 33


H2020 – DRS11 - 700191 34


H2020 – DRS11 - 700191 35

ANNEX 5 – Deliverable Peer-Review Report Template


H2020 – DRS11 - 700191 36


H2020 – DRS11 - 700191 37


H2020 – DRS11 - 700191 38

ANNEX 6 – STORM Leaflet Template