1 INTRODUCTION

#  1.1 PURPOSE OF THE DOCUMENT

This document describes how we defined the Data Management Plan (DMP) of
I-REACT and contains its second version. The first version of the DMP plan has
been delivered by the end of the first six months of the project and this new
version is a refinement of the former one. The DMP covers the data management
life cycle of the collected, processed and generated data during the project.
Specifically, the DMP is used to define the guidelines for data management in
the project in order to ensure a high level of data quality, security, and
accessibility.

According to the "Guidelines on FAIR Data Management in Horizon 2020" [RDOI],
"the DMP is intended to be a living document in which information can be made
available on a finer level of granularity through updates as the
implementation of the project progresses and when significant changes occur.".

This deliverable contains the second version of the DMP. The first version of
the DMP plan has been delivered by the end of the first six months of the
project. The DMP will be updated, providing finer details, during the periodic
evaluation/assessment of the project (i.e., at the midterm review and at the
final review).

We prepared the Data Management Plan by following the template provided in the
"Guidelines on FAIR Data Management in Horizon 2020" [RDOI] document.
Specifically, we generated the DMP of I-REACT by using the DMP online [RD02]
tool, which is compatible and compliant with the requirements set out in Annex
1 of the "Guidelines on FAIR Data Management in Horizon 2020" [RDOI]. DMP
online supports the generation of the DMP and allows exporting it in different
electronic formats (e.g., pdf file, doc file).

The DMP of I-REACT follows the FAIR principles, i.e., public research data are
made Findable, Accessible, Interoperable and Re-usable.

#  1.2 STRUCTURE OF THE DOCUMENT

The document is organized as it follows:

  * Chapter 1 is this introduction and description of the document itself; 

  

  * Chapter 2 contains the current version of the Data Management Plan of I-REACT. Specifically, the content of Chapter 2 corresponds to the export of the Data Management Plan (DMP) that we created by means of the DMP online [RD02] tool;  Chapter 3 draws conclusions. 

  

###  1\. DATA SUMMARY

The I-REACT project aims at supporting emergency activities related to hazards
(e.g., floods and fires) by integrating data from several external data
sources. Specifically, the I-REACT project aims at (i) supporting emergency
activities related to hazards (e.g., floods and fires) and (ii) generating
predictive and forecast models. To achieve the main goals of the project,
several heterogeneous data must be properly collected, transformed and
combined in order to tackle the problem from different perspectives.
Specifically, publicly available open data and external data sources will be
integrated with the content generated by the users of the I-REACT system
(e.g., the user generated reports). The integration of several data sources
will allow generating models based on complementary information that can be
used to support the different activities related to hazards and emergency
events in the I-REACT project. Both first responders and citizens will use and
exploit, at different granularities, the data collected, transformed, and
generated by I-REACT.

The collected data are mainly georeferenced data related to hazards and
emergency events (floods and fires). Based on the analysis of the available
data sources performed so far, the currently imported data, and the use cases
of the project, the following types of external data have been currently
identified as potentially useful for the I-REACT project:

  * Weather forecast data 

  

  * Flood maps 

  

  * Copernicus land monitoring service data 

  

  * European flood awareness system data 

  

  * European forest fire information system data 

  

  * Disaster event historical data 

  

  * Global administrative area data 

  

  * Statistical data 

  

  * Social media data (e.g., tweets) 

  

As reported in the above list, several external data sources will be re-used
by I-REACT, each one providing a different facet of the hazard/emergency event
we are facing. Both open and freely available data and non-public data will be
used. Open and freely available data will be preferred.

In the I-REACT project, standard data formats (e.g., GeoJSON and Shapefiles),
and metadata (e.g., INSPIRE complaint metadata) will be used in order to
improve findability, accessibility, interoperability and re-usability of the
data.

The I-REACT project will also generate data, based on the data (e.g., reports)
generated by the users of I-REACT, for instance by means of mobile
applications, and the transformation and analysis of the collected data.

The main types of data generated by I-REACT are the followings:

  * User generated reports 

  

  * Risk maps and weather forecast maps  Flood and fire nowcasts and forecasts 

  

  * Climate change maps 

  

  * UAV imagery 

  

Also, the data generated internally by I-REACT will be represented by means of
standard data formats (e.g., GeoJson) and will be enriched with standard
metadata.

Table 1 reports the data imported so far in the backend of I-REACT, with the
expected size (per file) and the partner that is responsible for importing the
data in the backend.  
  
<table>  
<tr>  
<th>

RESPONSIBLE

</th>  
<th>

DESCRIPTION

</th>  
<th>

FORMAT

</th>  
<th>

SIZE

</th> </tr>  
<tr>  
<td>

GeoVille

</td>  
<td>

Copernicus EMS Delineation Maps (crisis information, administrative
boundaries, area of interest, general information, hydrography, land cover,
physiography, points of interest, populated places, settlements,
transportation, utilities)

</td>  
<td>

Shapefile

</td>  
<td>

Depending on zoom level

</td> </tr>  
<tr>  
<td>

EOXPLORE

</td>  
<td>

Flood Forecast Period 1 — 5 year return period and

Flood Forecast Period 2 — 20 year return period

</td>  
<td>

GeoJSON

</td>  
<td>

MB

</td> </tr>  
<tr>  
<td>

EOXPLORE

</td>  
<td>

Fire Hotspots Comune and Points

</td>  
<td>

GeoJSON

</td>  
<td>

< 5 MB

</td> </tr>  
<tr>  
<td>

EOXPLORE

</td>  
<td>

Fire Weather Index

</td>  
<td>

GeoJSON

</td>  
<td>

< 5MB

</td> </tr>  
<tr>  
<td>

CSI

</td>  
<td>

ARPA Hydrogeological Alert Bulletin

</td>  
<td>

GeoJSON

</td>  
<td>

< IMB

</td> </tr>  
<tr>  
<td>

CSI

</td>  
<td>

FMI Weather alert (Wind, Snow-ice, Thunderstorms, Low temperature, Forest-
fire, Rain)

</td>  
<td>

GeoJSON

</td>  
<td>

N

3.5 MB

</td> </tr>  
<tr>  
<td>

TU Vienna

</td>  
<td>

Sentinel-I Flood Delineation Mapping

</td>  
<td>

GeoTlFF

</td>  
<td>

Sentinel-I:  rv  50 MB

Envi ASAR:  N  IOMB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Probability of gust limit 1, 2

</td>  
<td>

GeoJSON

</td>  
<td>

rv  2.5MB (per lead time)

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Probability of wind limit 1, 2

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Probability of temperature limit 1, 2,

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Probability of precipitation limit 1, 2, 3,

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Temperature

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Wind

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Precipitation 3h and 24h

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Pressure

</td>  
<td>

GeoJSON

</td>  
<td>

N2.5MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

Ensemble forecasts

</td>  
<td>

NetCDF

</td>  
<td>

N500MB

</td> </tr>  
<tr>  
<td>

FMI

</td>  
<td>

25th, 50th, and 75th percentile of daily max. temperature forecast
distribution

</td>  
<td>

NetCDF

</td>  
<td>

N13MB

</td> </tr> </table>

Table 1 — Imported data

The size of the data collected and generated depends on the considered data
sources. The size of the datasets and files associated with the several data
sources exploited by the project varies from some MBs to tens of GBs.

The collected and generated data will be useful for several end users and
stakeholders. Specifically, the users of the I-REACT system (both citizens and
first responders) will benefit from the data generated by the system.
Moreover, third parties could also be interested in the data collected and
generated by I-REACT, also for supporting decisions not directly related to
the management of emergency events.

###  2\. FAIR DATA

####  2.1 MAKING DATA FINDABLE, INCLUDING PROVISIONS FOR METADATA [FAIR DATA]

We will share the public data related to the I-REACT publications in the
Zenodo repository ( _https://www.zenodo.org/_ ). Zenodo provides a set of
basic functionalities that allows publishing data and searching them by means
of keywords. Moreover, Zenodo automatically assigns a DOI to each new uploaded
dataset and allows specifying metadata, which can be profitably exploited to
find the shared datasets.

The uploaded files will be identifiable and versioned by using a name
convention consisting of project name, dataset name, version, and date.

For the data for which it is appropriate, the standard INSPIRE
(http://inspiregeoportal.ec.europa.eu/) metadata will be used to enrich the
shared data.

####  2.2 MAKING DATA INTEROPERABLE [FAIR DATA]

The sharing of the data will follow the ORD pilot principle "as open as
possible, as closed as necessary". Specifically, when it is possible (i.e.,
when the data can be released as open without violating any copyright), the
research data needed to validate the results presented in the published
scientific papers will be made available. To support the sustainability of the
project, according to the defined business plan, the data that are fundamental
for the sustainability of the I-REACT project and are not used in the
published scientific papers will not be disclosed.

As already introduced before, the public datasets, and the related metadata,
will be made available through the Zenodo repository. Standard data formats
and metadata will be used to improve accessibility to the data by means of
standard freely available tools.

We will use standard data formats (e.g., GeoJSON and Shapefiles) for
representing the data used by I-REACT and standard metadata (INSPIRE complaint
metadata) to improve interoperability and re-usability of the data. This
solution improves the interoperability of the modules of I-REACT and the
interoperability with respect to external users interested in using the data
of I-REACT.

####  2.3 INCREASE DATA RE-USE (THROUGH CLARIFYING LICENSES) [FAIR DATA]

The data collected from external sources, or generated transforming external
data, will use the same license of the original data sources. For the subset
of internally generated data that will be open, not based on external data
sources, an open license will be used.

The public research data associated with the published research papers will be
made available as soon as the accepted papers will be published. The research
data associated with the published research papers will be made available as
soon as the accepted papers will be published. An embargo period will be
applied only if the policy of the related scientific publication enforces it.
The public research data published on Zenodo will be available for third
parties also after the end of project and will be freely available as long as
the Zenodo service will be available.

###  3\. ALLOCATION OF RESOURCES

The public data will the published in the free Zenodo repository. Hence, there
are no specific costs related to the storage of the public data.

Regarding the subset of non-publicly disclosed data exploited by the I-REACT
project, the costs of the management of the data, and the related privacy
issues, are already part of the costs related to the cloud architecture that
will be used to implement the I-REACT system.

Regarding the long-term preservation of the data, we plan to cover the costs
for the management of the non-public data by the revenue associated with the
exploitation of the data itself and the related services.

###  4\. DATA SECURITY

Security and privacy are two important issues managed by the project.
Specifically, Task "T2.4: Security & Privacy by design" addresses the security
and privacy issues by adopting a security and privacy by design methodology. A
detailed description of the selected methodology is reported in the
deliverable "D2.4: Report on Privacy and Security". The solution described in
D2.4 will be further specialized during the project based on the new privacy
and security issues that will emerge during the project. Any further changes
to the privacy and security solution that will arise during the project will
be included in the following versions of the DMP.

Regarding the secure storage of the data, the project will use an architecture
based on cloud services to store the data. The used services provide the
functionalities needed to address secure storage and data security. Regarding
sensible data, a secure and privacy by design methodology will be used to
avoid the disclosure of sensible and personal data.

###  5\. ETHICAL ASPECTS

According to the content of the ethics review and ethics section of DOA, the
designed solution will imply the collection and the processing of personal
data once operational. The management of such data will be regulated by a
clear term of service, which must be read and accepted by users, and which
will follow the EU data protection regulation. Note that data regarding
financial details, sexual lifestyles, ethnicity, political opinion, religious
or philosophical conviction will not be included in the Information
Architecture. Different features of the system will rely on locationbased
technologies to determine the position of people and "objects" (such as
infrastructures, resources, vehicles, etc.), which is crucial for the
implementation of the I-REACT products.

Regarding the localization of people, two different categories will be
distinguished:

First responders — who are the emergency operators and/or volunteers. Since
they are professional users, they must accept the geolocation of their devices
during the working time through a formal agreement with their employee. Their
positioning is needed to send in-field reports and it is also aimed at
monitoring their safety during the emergency response phase.  Citizens — who
must read and accept specific term of service in order to submit geolocalized
reports through the I-REACT mobile application. Optionally, they can allow the
I-REACT system to locate their position, which will be shared only with
subscribed authorities in case of emergency in order to effectively perform
search and rescue operations. With respect to the data retrieved from Social
Networks, the regulation included in their terms of service will be applied.

All personal data will be solely used for the project purpose, and they will
be only accessible by the data owner. The geolocated reports will include only
the user category and an ID that is not linkable with the user personal data.
Personal data will not be subject of any exploitation and will not be
distributed to any third party. Such data will be collected, stored, and
processed following Privacy-by-design approaches in order to guarantee
confidentiality, and anonymity. Thus, the data that will be publicly made
available will be anonymized. I-REACT does not foresee the management of
health data.

###  6\. OTHER

Regarding the privacy issues, the data will be managed in compliance with the
European regulation, as already described in Sections 4 and 5 of this Data
Management Plan.

#  3 CONCLUSIONS

This deliverable describes how the data management plan of the I-REACT project
has been generated and contains its second version. A first version was
released at the end of the first size months of the project and this updated
version was released in November 2017. The DMP of lREACT will be periodically
updated, providing finer details, in time with the following periodic
evaluation/assessment of the project (i.e., at the final review).

END OF THE DOCUMENT