**Executive Summary**

This document presents the Initial Data Management Plan (DMP) for the WADI
project. WADI has chosen to participate in the extended Open Research Data
pilot. Following the recommendations provided by the European Commission (EU,
2016), in the scope of making data FAIR, this DMP provides an initial approach
to the following topics:

  * the handling of research data during and after the end of the project 

  

  * what data will be collected, processed and/or generated 

  

  * which methodology and standards will be applied 

  

  * whether data will be shared/made open access 

  

  * how data will be curated and preserved (including after the end of the project) 

  

The WADI DMP was prepared using the Digital Curation Centre (DCC) DMP online
tool  (https://dmponline.dcc.ac.uk/),  which provides a DMP template that
match the demands and suggestions of the Guidelines on FAIR Data Management in
Horizon 2020(EU, 2016).
#  Introduction

This document is developed as part of the WADI (Water-tightness Airborne
Detection Implementation) project, which has received funding from the
European Union’s Horizon 2020 Research and Innovation programme, under the
Grant Agreement number 689239. The Data Management Plan (DMP), integrated in
Task 10.1 (Communication, Dissemination and Data Management Plan), represents
the Deliverable 10.2 of Work Package10 (WP10) – Communication and
dissemination. WADI has chosen to participate in the extended Open Research
Data pilot.

The project WADI includes eleven work packages from which seven of them (WP2
to WP7 and WP9) will result in relevant information to be shared with the
research and end-user communities. The purpose of the DMP is to support the
data management life cycle for all data that will be collected, processed or
generated by the WADI project. Following the recommendations provided by the
European Commission (EU, 2016), in the scope of making data FAIR (findable,
accessible, interoperable and reusable), this DMP provides an initial approach
to the following topics:

  * the handling of research data during and after the end of the project 

  

  * what data will be collected, processed and/or generated 

  

  * which methodology and standards will be applied 

  

  * whether data will be shared/made open access 

  

  * how data will be curated and preserved (including after the end of the project) 

  

More developed versions of the Plan will be released at later stages.

The WADI DMP was prepared using the Digital Curation Centre (DCC) DMP online
tool  (https://dmponline.dcc.ac.uk/),  which provides a DMP template that
match the demands and suggestions of the Guidelines on FAIR Data Management in
Horizon 2020 (EU, 2016).

#  Data summary

The main objective of WADI is to develop an innovative airborne water leak
detection surveillance service to provide water utilities with adequate
information on leaks in water infrastructures outside urban areas (rural
areas) and optimise their performance in this field. Throughout the project,
data will be produced and reused to support the development of research and
innovation activities focusing on: defining end-user requirements for water
leak surveillance services (WP2); defining system requirements including
optical device coupling; optimisation and their application on aerial
platforms (WP3); developing cost-effective data processing techniques,
reliable data processing and a new interface for end-users (WP4); evaluating
WADI’s service feasibility using a performance matrix and its environmental
and economic impacts (WP7); validating and demonstrating on both French and
Portuguese sites (WP5, WP6), conducting a comprehensive legal and regulatory
analysis (WP8); as well as developing pertinent market studies, marketing
strategies, and business plans (WP9). Table 1.1 summarises the types of data
produced / made available in different work packages of the WADI project.
Table 1.2 presents a more detailed description of data and its use (or re-
use), formats, standards and metadata, data availability (open, confidential)
and the expected resources to store, curate and preserve (size, backup
frequency, resources to maintain it after project ends, repository choices for
open and private data).  
  
<table>  
<tr>  
<th>

**TYPE OF DATA**

</th>  
<th>

**WP**

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

**WADI surveillance system development**

</td>  
<td>

Hyper-spectral/IR image database

</td>  
<td>

WP3

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

Optimized detection wavelengths

</td>  
<td>

WP3

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

Preliminary data from the platform for data processing development

</td>  
<td>

WP3, WP4

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

Imagery data for tests and validation

</td>  
<td>

WP3, WP5, WP6

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

Flight data of WADI process tests

</td>  
<td>

WP5

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

Flight data of WADI operational and surveillance tests

</td>  
<td>

WP6

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

Multi-spectral/IR image database

</td>  
<td>

WP7

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

Flights results, frequency, instrumentation used, fuel consumed, renting,
staff costs

</td>  
<td>

WP7

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

**End-users demonstration sites information**

</td>  
<td>

Network maps

</td>  
<td>

WP3, WP4, WP5, WP6,

WP7, WP9

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

Infrastructure data base

</td>  
<td>

WP5, WP6, WP7

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

Water company operational info

</td>  
<td>

WP2, WP7

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

Flow data

</td>  
<td>

WP5, WP6, WP7

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

Water losses data, leaks localisation

</td>  
<td>

WP2, WP5, WP7

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

Ground leak detection investigation

</td>  
<td>

WP5, WP6, WP7

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

**General information**

</td>  
<td>

Environmental data from satellites and other open sources

</td>  
<td>

WP7

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

Socioeconomic public reports analysis

</td>  
<td>

WP7

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

Table 1. 1 Summary of types of data to be used / created in different work
packages (WP)  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**OFFICE NATIONAL**

**D'ETUDES ET DE**

**RECHERCHES**

**AEROSPATIALES**

**(ONERA)**

</td>  
<td>

WP3

(task3.1)

</td>  
<td>

Hyperspectral/IR image database

</td>  
<td>

From Airborne measurement

</td>  
<td>

Not available

</td>  
<td>

Standards are not

available

for this type of data.

Data formats are owner

format of the

suppliers :

NEO for hyperspectr al camera

and FLIR for

IR camera

</td>  
<td>

Not applicable

</td>  
<td>

All

</td>  
<td>

Data too complex for

others to use it, data sets have

very large size, and they

cannot be

exploitable

without specific software

owned by

ONERA

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

By ONERA in its own servers

</td>  
<td>

Process

done by

ONERA

using their own

resources and procedures

</td>  
<td>

Data will be produced during WP

3-1

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on ONERA server and repositories

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

WP3

(task3.1)

</td>  
<td>

Optimized detection wavelengths

</td>  
<td>

Exploitation of

database image

</td>  
<td>

Available data will be reported in WADI report

</td>  
<td>

Not applicable,

wavelength standards do not exist

</td>  
<td>

All data is open access

</td>  
<td>

None

</td>  
<td>

Not applicable

</td>  
<td>

Researcher s, endusers,

service providers

</td>  
<td>

Can be shared to all at the

end of the

WP3-1, through

WADI

repository

at ZENODO

</td>  
<td>

Not applicable

</td>  
<td>

Process done using

ZENODO's own procedures

</td>  
<td>

Data will be produced during WP

3-1

</td>  
<td>

At the end of the WP3

</td>  
<td>

In

conferences presentations

</td>  
<td>

Through publication

and available through

ZENODO

during the

period that

this repository offers for

H2020 projects

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

WP7

(task 3.1)

</td>  
<td>

Multispectral/IR image database

</td>  
<td>

Through

Airborne measurements achieved on WP5 and WP6

</td>  
<td>

WADI report

</td>  
<td>

Standards will be

defined

later in WP4 with NTGS and LNEC partner

</td>  
<td>

Images database

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Researcher

s, end-users, service providers

</td>  
<td>

Can be shared to all at the

end of the

WP7, using

WADI

repository

at ZENODO

</td>  
<td>

Not applicable

</td>  
<td>

Process done using

ZENODO's own procedures

</td>  
<td>

Database will be

produced during WP7

</td>  
<td>

At the end of WP7

</td>  
<td>

During WP10 process

</td>  
<td>

Through publication

and available through

ZENODO

during the

period that

this repository offers for

H2020 projects

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

Table 1. 2Description of data to be used / created in different work packages,
including standards and metadata, availability, storing resources for open and
confidential data  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**AIR MARINE SARL**

**(AIR MARINE)**

</td>  
<td>

WP5

(task 5.2)

</td>  
<td>

Flight data of

WADI process

tests

(validation of Water leak

Airborne

Detection on

SCP

infrastructure)

</td>  
<td>

GIS output: data of the mission

Onboard mission recording: raw data sensor output and navigation

sensor output

(synchronised metadata)

</td>  
<td>

Internal technical

document, proprietary repository

</td>  
<td>

SHAPE format + Images

(geotiff)

</td>  
<td>

None

</td>  
<td>

All: WADI consortium restricted

</td>  
<td>

Flight data is

protected and

will be

provided to the consortium

partners on demand.

</td>  
<td>

End-users, researchers, data providers,…

</td>  
<td>

Not applicable

</td>  
<td>

Confidential data is

managed using Air

Marine resources

</td>  
<td>

Backup and

versioning data is

managed using Air

Marine resources

</td>  
<td>

Data produced

according to the

project

schedule

(demonstra tion flights in 2018)

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on Air Marine server and repositories

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

WP6

(task 6.2)

</td>  
<td>

Flight data of

WADI operational and

surveillance tests

(validation of Water leak

Airborne

Detection on

EDIA infrastructure)

</td>  
<td>

GIS output: data of the mission

Onboard mission recording: raw data sensor output and navigation

sensor output

(synchronised metadata)

</td>  
<td>

Internal technical

document, proprietary repository

</td>  
<td>

SHAPE format + Images

(geotiff)

</td>  
<td>

None

</td>  
<td>

All: WADI consortium restricted

</td>  
<td>

Flight data is

protected and

will be

provided to the consortium

partners on demand.

</td>  
<td>

End-users, researchers, data providers,…

</td>  
<td>

Not applicable

</td>  
<td>

Confidential data is

managed using Air

Marine resources

</td>  
<td>

Backup and

versioning data is

managed using Air

Marine resources

</td>  
<td>

Data produced

according to the

project

schedule

(demonstra tion flights in 2018)

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on Air Marine server and repositories

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

**LABORATORIO**

**NACIONAL DE**

**ENGENHARIA CIVIL**

**(LNEC)**

</td>  
<td>

WP7

(task 7.3)

</td>  
<td>

Infrastructure data for

reliability

analysis

(water levels, discharge flows,…)

</td>  
<td>

Field data acquisition

</td>  
<td>

Internal endusers reports and

databases. Will

be provided by

EDIA and SCP on request.

</td>  
<td>

Not applicable

</td>  
<td>

None

</td>  
<td>

All:

Infrastructur e data for reliability analysis (water levels,

discharge flows,…)

</td>  
<td>

According to the Consortium agreement,

infrastructure data is

protected and

will be

provided to the partners on demand.

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Infrastructure data is already managed by the end-users

using their own resources

</td>  
<td>

Not applicable

</td>  
<td>

Data already

exists. It will be used in

WADI as part of the reliability data processing.

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on LNEC

server and repositories

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

WP7

(task 7.3)

</td>  
<td>

Environmental data from

satellites and

other open sources

</td>  
<td>

Remote sensing and field data acquisition

</td>  
<td>

In open repositories on the internet

(Copernicus) and provided by other endusers (e.g.

Water authority in Portugal)

</td>  
<td>

Satellite data:

standards used by

Copernicus;

Water

authorities: distinct data

formats and standards

</td>  
<td>

All

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

End-users, researchers, general public,…

</td>  
<td>

Available in open

repositories

</td>  
<td>

Not applicable

</td>  
<td>

Procedures done by

the data

owners with their own resources

</td>  
<td>

Data already

exists. It will be used in

WADI as part of the reliability data processing.

</td>  
<td>

Already available

</td>  
<td>

Through websites

</td>  
<td>

Depending on data owner

policies

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

Table 1. 2 Description of data to be used / created in different work
packages, including standards and metadata, availability, storing resources
for open and confidential data(continuation)  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**EDIA-EMPRESA DE**

**DESENVOLVIMIENTO**

**E INTRA-ESTRUTURAS**

**DO ALQUEVA**

</td>  
<td>

WP3

WP6

</td>  
<td>

and

</td>  
<td>

Digital data about EDIA network localisation

</td>  
<td>

Working drawings

</td>  
<td>

Internal

documentation

, available through

request to

EDIA project team, internet

EDIA website

</td>  
<td>

PDF maps,

SHP files or other GIS format

</td>  
<td>

All not included as

restricted in the

consortium agreement

</td>  
<td>

Those included as

restricted in the

consortium agreement

</td>  
<td>

Operational data from EDIA

</td>  
<td>

Partners, public

</td>  
<td>

By EDIA through its website

</td>  
<td>

By EDIA in EDIA server

</td>  
<td>

Using EDIA own

resources

</td>  
<td>

In website already available

</td>  
<td>

After the analysis of

WP6 flights

(2019)

</td>  
<td>

EDIA website

</td>  
<td>

Depending on EDIA owner

policies

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

WP6

</td>  
<td>

</td>  
<td>

Flow data at specific locations

</td>  
<td>

Flow meters

</td>  
<td>

Internal

documentation

, available through

request to

EDIA project team

</td>  
<td>

Distinct data

formats and standards

</td>  
<td>

Restricted in the

consortium agreement

</td>  
<td>

Those included as

restricted in the

consortium agreement

</td>  
<td>

Operational data from EDIA

</td>  
<td>

Partners, public

</td>  
<td>

Not applicable

</td>  
<td>

By EDIA in EDIA server

</td>  
<td>

Using EDIA own

resources

</td>  
<td>

Data already exists

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Depending on EDIA owner

policies

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

**SOCIETE DU CANAL**

**DE PROVENCE ET**

**D'AMENAGEMENT**

**DE LA REGION**

**PROVENCALE SA**

**(SCP)**

</td>  
<td>

WP3

WP5

</td>  
<td>

and

</td>  
<td>

Digital data about SCP network localisation

</td>  
<td>

Working drawings

</td>  
<td>

Internal

documentation

, available through

request to SCP project team,

or available at

internet SCP website

</td>  
<td>

PDF maps,

SHP files or other GIS format

</td>  
<td>

Data sets on

localisation

on 1/25000 scale

without

associated data (size,

material, age…)

</td>  
<td>

All others

</td>  
<td>

Operational data from SCP

</td>  
<td>

Partners, public

</td>  
<td>

SCP

internet website

</td>  
<td>

SCP

</td>  
<td>

Using SCP own

resources

</td>  
<td>

Data already exists

</td>  
<td>

Data already exists

</td>  
<td>

SCP internet website

</td>  
<td>

SCP internet website

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

WP5

</td>  
<td>

</td>  
<td>

Leaks localisation

</td>  
<td>

Analysis of remote sensing acquisition

</td>  
<td>

cf. partners

(SGI, GG) who will produce

this kind of data

</td>  
<td>

cf. partners

(SGI, GG) who will

produce

this kind of data

</td>  
<td>

Data sets on

localisation

on 1/25000 scale in

general map

(without precise localisation)

</td>  
<td>

Data sets with more precise

presentatio n

</td>  
<td>

Communicatio

n

management with local residents

</td>  
<td>

Partners, public

</td>  
<td>

Not applicable

</td>  
<td>

SCP, on our

GIS and WADI partner who will produce the data

</td>  
<td>

SCP, on our

GIS and by

WADI

partners who will

produce the data

</td>  
<td>

During WP5

</td>  
<td>

After the analysis of

WP5 flights

(2018)

</td>  
<td>

SCP internet website

</td>  
<td>

SCP internet website

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

Table 1. 2 Description of data to be used / created in different work
packages, including standards and metadata, availability, storing resources
for open and confidential data(continuation)  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**NEW**

**TECHNOLOGIES**

**GLOBAL SYSTEMS SL**

**(NTGS)**

</td>  
<td>

WP3

(task 3.2)

</td>  
<td>

Preliminary data from the

platform for data

processing development

</td>  
<td>

Engineering

</td>  
<td>

Internal reports. Data will be provided by

NTGS on request

</td>  
<td>

PDF maps

</td>  
<td>

none

</td>  
<td>

All

</td>  
<td>

According to the Consortium agreement,

infrastructure data

(imagery) is protected and

will be

provided to the partners on demand.

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data owners in their own repositories

</td>  
<td>

NTGS own backup

</td>  
<td>

M18

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

WP4

(task 4.3)

</td>  
<td>

Preliminary data from the

platform for data

processing development

</td>  
<td>

Design

</td>  
<td>

Internal reports. Data will be provided by

NTGS on request

</td>  
<td>

PDF maps

</td>  
<td>

none

</td>  
<td>

All

</td>  
<td>

According to the Consortium agreement,

infrastructure data

(imagery) is protected and

will be

provided to the partners on demand.

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data owners in their own repositories

</td>  
<td>

NTGS own backup

</td>  
<td>

M19

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

**FUNDACION CIRCE CENTRO DE**

**INVESTIGACION DE**

**RECURSOS Y**

**CONSUMOS**

**ENERGETICOS**

**(CIRCE)**

</td>  
<td>

WP7

(task 7.1)

</td>  
<td>

Infrastructure information for building

inventories for

both demos:

Pipes info, pumping

consumption, chemical

consumption,

Flights results,

Frequency, instrumentatio n used, fuel consumed,

renting, staff costs

</td>  
<td>

Information will be obtained from WP 2

</td>  
<td>

Data bases will be internally

build and stored

according to

WP 2 information.

</td>  
<td>

As in WP2

</td>  
<td>

None, unless endusers (EDIA

and SCP) allow

sharing the info

</td>  
<td>

All data will be

considered as

confidential unless endusers (EDIA

and SCP) allow

sharing the info

</td>  
<td>

According to the Consortium agreement,

infrastructure data is protected

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Internally in databases

(included in

SimaPro software)

</td>  
<td>

Backup will be done weekly

according to CIRCE procedures

</td>  
<td>

Databases will be

developed

during the

WP7 framework, once WP2 tasks will start

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

WP7

(task 7.2)

</td>  
<td>

Environmental data from

satellites and other open

sources and

socioeconomi c public reports analysis

</td>  
<td>

Type of ecosystem will be defined

according to

MAES methodology internally,

according to the information

obtained from demo sites definition

</td>  
<td>

In open repositories on the internet

(Copernicus) and provided by other endusers (e.g. Water authority in Portugal
and

France)

</td>  
<td>

Water

authorities: distinct data

formats and standards

</td>  
<td>

All

</td>  
<td>

None

</td>  
<td>

Not applicable

</td>  
<td>

End-users, researchers, local inhabitants

</td>  
<td>

By means of open repositories

</td>  
<td>

Not applicable

</td>  
<td>

Backup will be done weekly

according to CIRCE procedures

</td>  
<td>

Databases will be

developed

during the

WP7 framework, once WP2 tasks will start

</td>  
<td>

At the end of the project

</td>  
<td>

By means of project website

</td>  
<td>

By means of project website

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

Table 1. 2 Description of data to be used / created in different work
packages, including standards and metadata, availability, storing resources
for open and confidential data(continuation) Table 1. 2 Description of data to
be used / created in different work packages, including standards and
metadata, availability, storing resources for open and confidential
data(continuation)  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**SST-CONSULT ADAM**

**STACHEL, RAFAL**

**STANEK, DAVID**

**ANDREW TOFT (SST - Consult)**

</td>  
<td>

WP9

(task 9.1)

</td>  
<td>

Data on

WADI results obtained from

validation

(WP5&6), results (WP 7) and legal

analysis (WP

8). Desk study for market conditions.

</td>  
<td>

Data on WADI results obtained from validation

(WP5&6), results

(WP 7) and legal analysis (WP 8)

</td>  
<td>

Internal project documentation and for

communicatio n with funders.

Not publicly available

directly from project.

</td>  
<td>

Distinct data

formats and standards

</td>  
<td>

Restricted in the

consortium agreement

</td>  
<td>

Those included as

restricted in the

consortium agreement

</td>  
<td>

Operational data from end-

users

</td>  
<td>

Partners, public

</td>  
<td>

Not applicable

</td>  
<td>

In end-users servers

</td>  
<td>

Using endusers own resources

</td>  
<td>

During WP9

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on end-users server and repositories

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

WP9

(task 9.2)

</td>  
<td>

Data on

WADI results obtained from

validation

(WP5&6), results (WP 7) and legal

analysis (WP

8). Desk study for market conditions.

</td>  
<td>

Data on WADI results obtained from validation

(WP5&6), results

(WP 7) and legal analysis (WP 8)

</td>  
<td>

Internal project documentation and for

communicatio n with funders.

Not publicly available

directly from project.

</td>  
<td>

Distinct data

formats and standards

</td>  
<td>

Restricted in the

consortium agreement

</td>  
<td>

Those included as

restricted in the

consortium agreement

</td>  
<td>

Operational data from end-

users

</td>  
<td>

Partners, public

</td>  
<td>

Not applicable

</td>  
<td>

In end-users servers

</td>  
<td>

Using endusers own resources

</td>  
<td>

During WP9

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on end-users server and repositories

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

WP9

(task 9.3)

</td>  
<td>

Based on market strategy

</td>  
<td>

Based on market strategy

</td>  
<td>

Based on market strategy

</td>  
<td>

Distinct data

formats and standards

</td>  
<td>

Restricted in the

consortium agreement

</td>  
<td>

Those included as

restricted in the

consortium agreement

</td>  
<td>

Operational data from end-

users

</td>  
<td>

Partners, public

</td>  
<td>

Not applicable

</td>  
<td>

In end-users servers

</td>  
<td>

Using endusers own resources

</td>  
<td>

During WP9

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Data archive on end-users server and repositories

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

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**Galileo Geosystems S.L. (GG)**

</td>  
<td>

WP3

(task 3.3)

</td>  
<td>

Imagery data for tests and validation

</td>  
<td>

RPAS data acquisition

</td>  
<td>

Will be provided by

GG on request

</td>  
<td>

End-users standards

for

geographic information

</td>  
<td>

None

</td>  
<td>

All: high resolution

imagery from

infrastructur es and

preliminary data report

</td>  
<td>

According to the Consortium agreement,

infrastructure

data (imagery)

is protected

and will be

provided to the partners on demand.

</td>  
<td>

End-users, researchers

</td>  
<td>

Available in restricted repositories

</td>  
<td>

High resolution imagery

archived by end-users

</td>  
<td>

Procedures done by

end-users

with their own

resources

</td>  
<td>

M18

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

WP5

(task 5.2)

</td>  
<td>

Imagery data for tests and validation

</td>  
<td>

RPAS data acquisition

</td>  
<td>

Will be provided by

GG on request

</td>  
<td>

End-users standards

for

geographic information

</td>  
<td>

None

</td>  
<td>

All: high resolution

imagery from

infrastructur es and

preliminary data report

</td>  
<td>

According to the Consortium agreement,

infrastructure

data (imagery)

is protected

and will be

provided to the partners on demand.

</td>  
<td>

End-users, researchers

</td>  
<td>

Available in restricted repositories

</td>  
<td>

High resolution imagery

archived by end-users

</td>  
<td>

Procedures done by

end-users

with their own

resources

</td>  
<td>

M23

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

WP6

(task 6.2)

</td>  
<td>

Imagery data for tests and validation

</td>  
<td>

RPAS data acquisition

</td>  
<td>

Will be provided by

GG on request

</td>  
<td>

End-users standards

for

geographic information

</td>  
<td>

None

</td>  
<td>

All: high resolution

imagery from

infrastructur es and

preliminary data report

</td>  
<td>

According to the Consortium agreement,

infrastructure

data (imagery)

is protected

and will be

provided to the partners on demand.

</td>  
<td>

End-users, researchers

</td>  
<td>

Available in restricted repositories

</td>  
<td>

High resolution imagery

archived by end-users

</td>  
<td>

Procedures done by

end-users

with their own

resources

</td>  
<td>

M31

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

**SGI STUDIO GALLI**

**INGEGNERIA SRL**

**(SGI )**

</td>  
<td>

WP1

</td>  
<td>

Commercial

(expectations from WADI)

</td>  
<td>

Questionnaires

</td>  
<td>

Aggregated

analysis, rough

data; internal repository

</td>  
<td>

None

</td>  
<td>

None

</td>  
<td>

All

</td>  
<td>

Either part of

Partners' (EDIA and SCP)

commercial

strategy and

competitivenes s or protected according to

the Consortium

Agreement

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Questionnaires archived by

end-users and

SGI

</td>  
<td>

Not applicable

</td>  
<td>

Within M2

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

WP2

</td>  
<td>

Water losses data, water company

operational info

</td>  
<td>

Questionnaires

</td>  
<td>

Aggregated analysis; internal repository

</td>  
<td>

None

</td>  
<td>

None

</td>  
<td>

All

</td>  
<td>

Either part of

Partners' (EDIA and SCP)

commercial

strategy and

competitivenes s or protected according to

the Consortium

Agreement

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Questionnaires archived by

end-users and

SGI

</td>  
<td>

Not applicable

</td>  
<td>

Within M4

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

</td>  
<td>

Not applicable

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

Table 1. 2 Description of data to be used / created in different work
packages, including standards and metadata, availability, storing resources
for open and confidential data(continuation)  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Work Package**

</th>  
<th>

**Type of data/ data description**

</th>  
<th>

**Methodology of data production**

</th>  
<th>

**Data documentation and how that**

**will be made available**

</th>  
<th>

**Data standards**

</th>  
<th>

**Which data sets will be classified as Open**

**Access**

</th>  
<th>

**Which data sets will be**

**classified as**

**confidential**

</th>  
<th>

**In case of datasets that**

**are not shared, reasons for that**

</th>  
<th>

**To whom data**

**classified as Open**

**Access could be useful**

</th>  
<th>

**How will open data**

**be shared / by whom and where**

</th>  
<th>

**How will confidential data be**

**archived / by**

**whom and where**

</th>  
<th>

**How is backup and**

**versioning realised?**

</th>  
<th>

**When data will be**

**produced**

</th>  
<th>

**When data will be**

**placed in Open**

**Access**

</th>  
<th>

**How will the data be disseminated**

</th>  
<th>

**How will data be available**

**after the end of the project**

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

**SGI STUDIO GALLI**

**INGEGNERIA SRL**

**(SGI )**

</td>  
<td>

WP5

</td>  
<td>

Network maps,

infrastructure dB, flow

measurement

s, GLD investigation

</td>  
<td>

The pilot area/s will be identified

with SCP. SCP will

provide network maps,

infrastructure

characteristics and flow data

through GIS, dB, xls or other media

according to availability.

Investigation will be planned by

SGI together with SCP, who will provide

gauged data

accordingly. SGI will process

investigation

data and submit relevant report.

</td>  
<td>

Documented through maps,

spreadsheets, dB

</td>  
<td>

To be defined

</td>  
<td>

To be defined

</td>  
<td>

To be defined

</td>  
<td>

Operational data from Water

Companies

</td>  
<td>

Anyone

interested in direct

check of

WADI performanc

e

</td>  
<td>

WADI

repository

at ZENODO

</td>  
<td>

Internal WADI project repository

</td>  
<td>

To be defined

</td>  
<td>

M20-M23

</td>  
<td>

M23

</td>  
<td>

Training, public

reports, conferences

</td>  
<td>

Reports, conference / training papers,

dissemination material

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

WP6

</td>  
<td>

Network maps,

infrastructure dB, flow

measurement

s, GLD investigation

</td>  
<td>

The pilot area/s will be identified

with EDIA. EDIA will provide

network maps, infrastructure

characteristics and flow data

through GIS, dB, xls or other media

according to availability.

Investigation will be planned by

SGI together with EDIA, who will provide

gauged data

accordingly. SGI will process

investigation

data and submit relevant report.

</td>  
<td>

Documented through maps,

spreadsheets, dB

</td>  
<td>

To be defined

</td>  
<td>

To be defined

</td>  
<td>

To be defined

</td>  
<td>

Operational data from Water

Companies

</td>  
<td>

Who is interested in direct

check of

WADI performanc

e

</td>  
<td>

WADI

repository

at ZENODO

</td>  
<td>

Internal WADI project repository

</td>  
<td>

To be defined

</td>  
<td>

M24-M30

</td>  
<td>

M23

</td>  
<td>

Training, public

reports, conferences

</td>  
<td>

Reports, conference / training

papers,

dissemination material

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

Table 1. 2 Description of data to be used / created in different work
packages, including standards and metadata, availability, storing resources
for open and confidential data(continuation)

#  FAIR data

##  Making data findable, including provisions for metadata

WADI will produce and reuse a variety of data types, from images to time
series and georeferenced information in GIS format, covering a broad range of
areas (remote sensing, hydrology, hydraulics,..). Metadata will be produced
for all data, using standards when available. Standards such as ISO19115
(http://rd-alliance.github.io/metadata  directory/standards/iso-19115.html) or
the OGC Sensor Observation Service (SOS)

Interface Standard (  http://rd-alliance.github.io/metadata-
directory/standards/observations-and  measurements.html) are expected to be
adopted. Consistency between metadata for similar data sets will be sought
when standards are not available. Elements to be included in the metadata
include a clear description of the data, the institution and person of contact
responsible for the data creation, its format, creation date and possible
modifications, data units and georeferencing (when applicable) and a number of
keywords (metatags). The choice of adequate keywords will be included to
promote and ease the discoverability of data. These keywords will include a
number of fixed, common keywords in WADI’s scientific area and several new,
free keywords that can help attract researchers from other areas to use and
adapt WADI’s results to their scientific fields.

For all open data in the project, ZENODO will be used as the project’s open
data repository. ZENODO provides Digital Object Identifiers for all data sets,
thus guaranteeing that all open data in WADI will have persistent and unique
identifiers.

For consistency and promotion of data discovery, consistent naming conventions
will also be used and agreed among the partners (to be defined later).

Open access publication will also be sought, with direct links to the
underlying data sets deposited in ZENODO.

LNEC will be responsible for uploading data and other items in ZENODO, through
the project designated data manager. Each partner will provide the datasets
and publications to be integrated in the ZENODO repository to the data
manager, dully informed on its access policy. The datasets and the expected
time of availability and access policies are described in Table 1.2. For
publications subject to embargo periods (due to the publishers’ policies), the
data manager will upload them in ZENODO as soon as the embargos are finished.
The coordinator will inform LNEC as soon as the datasets are delivered to
youris.com, for data management monitoring purposes.

In the scope of the surveillance system developed in WADI, a succession of
data sets will be produced, creating several databases of images at different
stages of development and processing, from the raw data from cameras to the
processed and quality-certified images included in the end-user application.
This sequence can be labelled as several versions of a single dataset or it
can be identified and managed as different datasets. Regardless of the
approach chosen by the partners for this data, a clear versioning policy will
be adopted and linked with detailed metadata and supporting documentation.

##  Making data openly accessible

WADI will create or reuse a variety of data sets, which have different natures
and correspondingly distinct access privileges. Part of these privileges was
set up in the project’s Consortium Agreement. These different access
privileges are described in detail in Table 1.2 and are reviewed here in a
concise manner. Table 1.2 also provides a detailed description of all aspects
related to dataset management. A short overview on data access policies and
availability is presented here.

Regarding end-users’ infrastructure data (such as digital information
regarding the networks’ location in very fine detail, the customer's data and
the location of leaks), these are classified as confidential in the Consortium
agreement to protect personal information (as described in the D11.1 POPD -
Requirement No. 3) as well as the security of the companies’ assets.
Infrastructure data at a granular scale is already openly available at the
companies’ website, thus fulfilling its usefulness for scientific or other
public purposes. Regarding classified data, it is kept at the companies’ own
repositories, fulfilling their own policies on data backup and preservation,
and will be maintained by these entities after the end of the project.

Regarding the data from the surveillance system developed at WADI (Tables 1.1
and 1.2), different access policies are defined according to the Consortium
agreement. These data sets include mostly several databases of images at
different stages of development and processing, ranging from the raw data
derived from the hyperspectral, multi-spectral and I/R cameras to the
processed and quality-certified images. The raw data from the several types of
cameras have an immense size and require specialized, proprietary software to
be accessed. Therefore, it is not made available, although it will be fully
documented in reports and scientific publications. In contrast, the optimised
detection wavelengths (developed in WP3) and the multi-spectral/IR image
database to be developed during the demonstrations in Portugal and France will
be openly available through ZENODO.

In-situ ground data is also part of the WADI service, but given the
information’s sensitivity and the restrictions posed by the infrastructure’s
competitive operation, it will not be open. Like all confidential data in
WADI, its preservation and maintenance during and after the project will be
handled by the data owners and/or the end-users.

Deposits in ZENODO will include the data, their metadata and their
documentation. For most data sets, access is granted through generalised use
software such as ArcGIS or similar.

##  Making data interoperable

All data developed in WADI will be fully documented and accompanied with
detailed metadata supported by a set of select keywords, to facilitate
automatic discovery and integration of WADI data for other purposes. Besides
usual metadata fields, technical aspects such as units (complying with SI
standards) and spatial and temporal references will be supplied. All data will
be provided in generally used extensions, adopting well established formats
(csv, shapefiles, image formats,...) whenever possible which will also
facilitate its use by other parties. The exception will be the raw data from
the optical devices which can only be interpreted using ONERA’s own software.

##  Increase data re-use

Open data availability will occur as soon as possible in WADI while respecting
the team’s publication targets. Typically, open data will be available for
publication in ZENODO at the end of respective WP (Table 1.2), and its
publication will occur within one month. The team expects that this fast
publication of data created in WADI will promote its reuse by other
researchers and end-users, thereby contributing to the dissemination of WADI
methodology and tools.

The usefulness of the data for third parties is closely linked to the
perception of quality and robustness of the available data. Therefore, a
dedicated task was defined in WP4 to validate data and standards compliance,
setting the stage for the data reliability analysis performed in WP7. In this
last analysis, other sources of data will be combined with images to provide a
quality index for the leak detection data generated in WADI. All these methods
will be expected to contribute to a long term usefulness of this data.

#  Allocation of resources

In WADI there is a considerable amount of confidential data (see the
aforementioned reasons). This data will be managed by the partners responsible
for its creation and/or by the end-users (Table 1.2). Therefore its
maintenance, backup and versioning and long term preservation will be
guaranteed by their own resources and at their own expense.

A repository in ZENODO was created (
https://zenodo.org/communities/h2020-wadiproject/  ) for the projects´ open
data, therefore ensuring data availability, backup and versioning. Long term
preservation will be guaranteed for the lifetime of the ZENODO repository
(https://zenodo.org/policies).  This is currently the lifetime of the ZENODO’s
host laboratory CERN, which currently has an experimental programme defined at
least for the next 20 years. After the end of that period, the data will only
be kept at the data owners’ servers and repositories.

Publications featuring the data will be produced in the project (specifically
by the research partners) and will be made available through open access
(using open access journals or journals selected for a short embargo period).
This channel will provide a long term availability of data and data analysis.

The partners expect the data to have immense value in short to medium term to
support the optimised management of water mains and to reduce water losses.
The methodology and data products developed in the project are expected to
have a large impact in this field, through generalised application at European
and other international sites. Moreover, we expect that the scientific and
technological developments may serve as a basis in other fields of
application, with the data demonstrating and promoting WADI’s exceptional
quality of service. The long term usefulness of the data collected during WADI
will depend on the technological advances in this area. The resolution
achieved with today's technology may prove lacking in the future, given the
advances in camera quality and the supporting data’s infrastructure.

#  Data security

Open data security will addressed in WADI taking advantage of ZENODO’s
services of secure storage, backup and preservation and protected transfer
mechanisms. Regarding the confidential data, different approaches will be used
by each data-owner institution, but common rules apply. Data will be housed on
servers under direct management of the institution’s personnel to be installed
in already provisioned data centres. These data centres are expected to be
equipped with various features ranging from secure physical access, air
conditioning, generators and fire extinguishing measures. Typically, hardware
/ electricity failure are addressed with redundant hardware and generators.

Access to data under different permission conditions (read-only, read-write,
etc.) are granted to users and authorized computers by project managers or to
whomever this task is delegated, according to a well-defined protocol.
Confidentiality is assured by additional methods, encryption and anonymization
to name a few, depending on their nature and final applications.

Taking in account the size of the data at stake that requires regular backup
(be it either for security versus a hardware failure or for archival
purposes), a sequence of regular full backups, differential backups and
incremental backups on an increasingly frequent basis are envisaged, and
following already installed procedures. The physical media used to store the
data will be maintained in secure locations. Access to these backups is
limited to the personnel authorised to use the backup system, and as a general
rule, not authorised for external sources.

All data transfers should be encrypted to render all stolen/lost data useless.
Encryption methods are to be specified at a later date.

#  Ethical aspects

The WADI partners are to comply with the ethical principles as set out in
Article 34 of the Grant Agreement, which states that all activities must be
carried out in compliance with:

  1. Ethical principles (including the highest standards of research integrity – as set out, for instance in the European Code of Conduct for Research Integrity – and including, in particular, avoiding fabrication, falsification, plagiarism or other research misconduct) 

  

  2. Applicable international, EU and national law. 

  

  

Activities raising ethical issues must comply with the “ethics requirements”
set out in Annex1 of the Grant Agreement. The WP11 “Ethics requirements” aims
to follow-up the ethical issues applicable to the WADI project implementation.
It includes: informed consent procedures that will be implemented by each
partner that foreseen activities that require such procedures (Deliverable
11.1); administrative clearance procedures and approvals for flights to be
carried out in WP3 in France and Portugal (Deliverable 11.2); copies of
confirmation/notification by the National data Protection Authority
(Deliverable 11.3); and information on the procedures implemented for data
collection, storage, protection, retention, destruction and confirmation and
compliance with national and EU legislation (Deliverable 11.4).

Legal and regulatory issues also have a dedicated WP (WP8 “Legal and
regulatory aspects analysis, including IPR protection”). This WP will provide
legal guidance to the project partners, in particular with regard to the
authorisations for executing the flight tests in real environment (WP5 and WP6
pilots), the compliance with relevant rules and procedures such as the
applicable rules for privacy protection and processing of personal data in
relation to the unmanned airborne vehicles use and for all issues with regard
to the intellectual property rights of the project results. It will also
develop the legal and regulatory framework for the commercialisation of the
project results. The WP8 includes: Project legal framework (Deliverable 8.1);
WADI service provision legal framework (Deliverable 8.2); WADI service
provision terms and conditions (Deliverable 8.3).