#  1\. INTRODUCTION

TAHYA is part of the Horizon 2020 Open Research Data Pilot, the Pilot project
of the European Commission which aims to improve and maximize access to and
reuse of research data generated by projects. The focus of the Pilot is on
encouraging good data management as an essential element of research best
practice.

The Deliverable D8.6 Data Management Plan (DMP), represents the first version
of the DMP of the TAHYA project. TAHYA is a Research and Innovation Action
project funded under the Fuel Cells and Hydrogen 2 Joint Undertaking that will
last 36 months. As such, TAHYA participates in ORD Pilot, and, therefore, is
providing, as requested, the current deliverable six months after the
beginning of the project (M6, June 2018).

The DMP is not a fixed document, but it is likely to evolve during the whole
lifespan of the project, serving as a working document. This document will be
updated as needed during the Project General Assemblies.

st version Data Management Plan of the TAHYA

The purpose of the current deliverable is to present the 1 project. The
deliverable has been compiled with the collaborative work among the
coordinator and the consortium partners who were involved in data collection,
production and processing. It includes detailed descriptions of all datasets
that will be collected, processed or generated in all Work Packages during the
course of the 36 months of TAHYA project. The deliverable is submitted six
months after project start as required by the European Commission (EC) through
the latest guidelines: The Open Research Data Pilot (ORD Pilot). For the
methodological part, the latest EC guidelines  1  have been adopted for the
current deliverable.

The deliverable is structured in the following sections:

  1. An introduction to the deliverable and a brief description on how Data Management is approached in Horizon 2020 (H2020) program along with the importance of it. 

  

  2. A description of the methodology used, an analysis of the chapters of the provided template and last the methodological steps followed in TAHYA. 

  

  3. A description of the datasets to be used in TAHYA reflected on the template provided by the EC. 

  

  4. A summary table with all the datasets included in 1  st  TAHYA DMP. 

  

  

#  2\. DATA MANAGEMENT IN H2020 PROGRAM

According to the latest Guidelines on FAIR Data Management in Horizon 2020
released by the EC DirectorateGeneral for Research & Innovation on the 26th of
July 2016 “ _beneficiaries must make their research data findable, accessible,
interoperable and reusable (FAIR) ensuring it is soundly managed_ ”.

FAIR data management is part of the ORD Pilot promoted by the European
Commission. The purpose of the ORD is to improve and maximize access to and
re-use of research data generated by H2020 projects and to take into account
the need to balance openness and protection of scientific information,
commercialization and Intellectual Property Rights (IPR), privacy concerns,
security, as well as data management and preservation issues.

The inclusion of a DMP is a key element for FAIR data management in a H2020
project. In a DMP, the data management life cycle for the data to be
collected, processed and/or generated by a H2020 project is described and
analysed. The DMP should also include information on (a) the handling of
research data during & after the end of the project, (b) what data will be
collected, processed and/or generated, (c) which methodology & standards will
be applied, (d) whether data will be shared/made open access and (e) how data
will be curated & preserved (including after the end of the project).

#  3\. METHODOLOGY

##  a. DMP Template

In order to assist the beneficiaries with the completion of the DMP, the EC
produced and provided a template that act as a basis for data description. The
template contains a set of questions that beneficiaries should answer with a
level of detail appropriate to the project. If no related information is
available for a given dataset, then the phrase “ _Non-applicable_ ” or N/A
will be used. In the following paragraphs, the main sections and proposed
contents of the template are listed and presented, along with the way TAHYA
reflects to these sections.

##  b. Data summary

In this section, beneficiaries are asked to describe (a) the purpose of the
data collection or generation and how this purpose reflects to the objectives
set in the project as a whole, (b) the types and formats of data that will be
generated or collected, (c) the origin of the data, (d) the expected size of
the data, and also (e) whether existing data will be reused and (f) the
usefulness of the described datasets.

##  c. FAIR data

###  a) Making data findable, including provisions for metadata

This section includes a description of metadata and related standards, the
naming and keywords to be used. In the context of TAHYA the following naming
convention will be used for all the datasets of the project. First the work
package number will be placed, then the serial number of the dataset within
this work package and last the dataset title, all separated with underscore
(Data_<WPno>_<serial number of dataset>_<dataset title>).

An example can be the following Data_WP2_1_specifications_data.

However, it has to be noted that this naming convention describes only the
general dataset that can contain files of different size and format. The
naming of each separate file follows a different naming convention that is
proposed by the partners who creates the files.

The use of a standard identification mechanism in for the datasets of TAHYA
will be decided by the project consortium. If it turns out to be necessary,
the use of the Guidelines and standards provided by the International DOI
Foundation (IDF) and the DOI system and ISO 26324  2  will be considered.

###  b) Making data openly accessible

This section includes a description of the data that will be made accessible
and how. It also explains why some datasets cannot be made open due to
possible, legal, contractual or ethical issues. It is possible that some
beneficiaries have decided to keep their data closed. A description of the
potential data repositories is also included along with the potential software
tools required to access the data.

In the context of TAHYA, the following options for open repositories of data,
metadata, documentation or code will be considered: (a) The Registry of
Research Data Repositories  3  , (b) Zenodo  3  , (c) OpenAIRE  4  ,

In the context of the TAHYA DMP, not any arrangements have been made with an
identified repository. This will be discussed by the consortium during the
upcoming plenary meeting. Currently the data are collected and preserved on a
private platform: Project Netboard  5  .

###  c) Making data interoperable

In this section, data interoperability is detailed for every dataset of TAHYA.
Issues such as the allowing of data exchange between researchers, institutions
or even countries are covered along with all the technicalities including
standards for formats, metadata vocabularies or ontologies of vocabularies.

The issue of interoperability will be discussed among the consortium members
in the upcoming project plenary meeting.

###  d) Increase data re-use (through clarifying licenses)

This section describes the licenses, if any, under which data will be re-used
in TAHYA. It includes provisions regarding the period when data will be
available for reuse and if third parties will have the option to use the data
and when.

###  e) Allocation of resources

FAIR data management in TAHYA project is under WP9 –Dissemination and
Exploitation strategy lead by Partner N°6 Absiskey, in close collaboration
with the Coordinator. Within the project budget, a specific amount of person
months has been dedicated for these activities. All costs related to FAIR data
management that will occur during project implementation will be covered by
the project budget. Any other cost that may relate to long term data
preservation will be discussed among consortium members.

###  f) Data security

Data security is of major importance in the TAHYA project. Special attention
will be given to the security of sensitive data. The protection of data will
be ensured through procedures and appropriate technologies, on Project
NetBoard like the use of HTTPS protocol for the encryption of all internet
transactions and appropriate European and Internet security standards from
ISO, ITU, W3C, IETF and ETSI. If data will be kept in a certified repository,
then the security standards of that repository will apply.

###  g) Ethical aspects

With respect to the H2020 ethics self-assessment, the TAHYA proposal and the
use case scenarios to be defined will not be concerned with any ethical issue.

###  h) Other issues

In this section, other issues can be covered not included above such as the
use of other national/funder/sectorial/departmental procedures for data
management.

##  d. Methodological steps in TAHYA

For the 1  st  version of TAHYA DMP, the following methodological steps were
followed:

  1. Absiskey and the Coordinator, responsible for the implementation WP9 – Dissemination and Exploitation strategy - sent to all partners, well in advance, an email notifying them about the upcoming deliverable. Contribution was asked from all partners that were involved in any data collection in each task of the WPs. They were asked to answer a questionnaire on which data they were expecting to produce and collect during the project. 

  

  2. In parallel, the latest guidelines from the EC regarding data management were sent to all partners to be informed. Sufficient time was given to send their input. 

  

  3. The project team collaborated efficiently and contributed with the needed information. 

  

  

The first version of the TAHYA DMP is intended to provide an initial screening
of the data to be collected, processed and produced within TAHYA. It is also
the first attempt to collect the vision and input from all the partners
involved in any data management option. During the upcoming Project Steering
Boards in October 2018 special attention will be given to data management in
order to provide further clarifications and conclusions on data management.

#  4\. DATASETS

##  a. WP1 – Project Decision making and innovation management

N/A

##  b. WP2 – End-users' specifications, product, safety & service definition

N/A

Specifications are highly confidential results which cannot be share and held
by VW.

##  c. WP3 – Design and Prototyping

Design and developments for liner, composite and OTV are highly confidential
results which cannot be share to the scientific community and held by
industrial partners (Optimum, Raigi and Anleg).

Only one task in this WP could lead to the open access to data: Task 3.5
optimisation and filling and venting process.  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**WP3_1_Simulation assumptions_data**

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

1\. Data summary

</td>  
<td>

**Purpose:** Simulation data

**Data formats** : *.xlsx, *.docx, *.pdf, *.pptx

**Will you re-use any existing data and how?**

  * yes 

  

**What is the origin of the data?**

  * simulation, 

  

  * experimental protocols, measurement conditions **What is the expected size of the data?**

  

  * The total file of this dataset will be approximately 0,2 Gb. 

  

**To whom might it be useful ('data utility')?**

  * scientific community 

  

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

2\. FAIR Data

</td>  
<td>

Findable, Accessible, Interoperable, Re-usable

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

2.1 Making data findable, including provisions for metadata

</td>  
<td>

Description of the data:

\- WP3_1_Simulation assumptions_data

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

2.2 Making data openly accessible

</td>  
<td>

\- assumption data on gas and Temperature distribution to members of a
consortium on project, members of an international scientific community for
research purposes. The data will be stored on Project Netboard a secure
platform and TUC servers.

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

2.3 Making data interoperable

</td>  
<td>

\- the data produced in the project are interoperable, that is allowing data
exchange and re-use between researchers, institutions, organisations

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

2.4. Increase data re-use (through clarifying licences)

</td>  
<td>

Specify the licenses and the conditions for sharing and reusing the data:

\- No specific conditions

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

3\. Allocation of resources

</td>  
<td>

All costs related to the data collection and processing are covered by the
project budget with dedicated person months under WP9.

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

4\. Data security

</td>  
<td>

Audio, doc and xls files will be deposited in ABSISKEY servers and will be
protected with the ABSISKEY server’s security protocol:

PNB security is provided by OVH. OVH is currently the number 3 web hosting
provider worldwide.

OVH condition of security:  https://www.ovh.co.uk/aboutus/security.xml  and
https://www.ovh.co.uk/aboutus/datacentres.xml

In addition to this security, a complete database backup is performed each day
and stored during one week. Each week a secured backup is stored on CD.

Finally, every connection to Project NetBoard is made using the https protocol
to login to the platform _._

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

5\. Ethical aspects

</td>  
<td>

There are no ethical issues regarding the project.

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

6\. Other

</td>  
<td>

N/A

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

##  d. WP4 – Design verification phase

To be defined later on in the project according to IP management of
development realised in WP3.

##  e. WP5 – System validation phase and safety aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**WP5_1_performance results_data**

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

1\. Data summary

</td>  
<td>

**Purpose:** Results of the hydraulic performance and fire resistance tests.

**Data formats** : *.xlsx , *.docx, *.pdf , *.pptx, *.mp4, *.asc , *.opj

**Will you re-use any existing data and how?**

  * N/A 

  

**What is the origin of the data?**

  * Experimental measurement data recorded with universal measurement amplifiers **What is the expected size of the data?**

  

  * The total size of all data will be approx. less than 2 Gb. 

  

**To whom might it be useful ('data utility')?**

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

</th>  
<th>

\- Project partners, scientific community, notified bodies, competent
authority

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

2\. FAIR Data

</td>  
<td>

Findable, Accessible, Interoperable, Re-usable

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

2.1 Making data findable, including provisions for metadata

</td>  
<td>

Description of the data:

\- The following naming for the dataset will be WP5_1_BAM_performance
results_data

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

2.2 Making data openly accessible

</td>  
<td>

  * mainly results of normalised data needed for publications (national/international scientific community and standards committee) 

  

  * raw measurement data only to members of the consortium 

  

  * Shared documents/data uploaded to Project Netboard All Data will be stored on company internal shared directory with limited number of users 

  

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

2.3 Making data interoperable

</td>  
<td>

All published data are generated with common programs and stored within common
file formats and therefore they are interoperable and can be re-use between
researchers, institutions, companies etc.

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

2.4. Increase data re-use (through clarifying licences)

</td>  
<td>

Specify the licenses and the conditions for sharing and reusing the data:

\- Creative Commons:

(CC BY-ND 3.0 DE or CC BY-NC-ND 3.0 DE) https://creativecommons.org/

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

3\. Allocation of resources

</td>  
<td>

All costs related to the data collection and processing are covered by the
project budget with dedicated person months under WP9.

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

4\. Data security

</td>  
<td>

Files will be deposited in ABSISKEY servers and will be protected with the
ABSISKEY server’s security protocol:

PNB security is provided by OVH. OVH is currently the number 3 web hosting
provider worldwide.

OVH condition of security:

_https://www.ovh.co.uk/aboutus/security.xml_ and
_https://www.ovh.co.uk/aboutus/datacentres.xml_

In addition to this security, a complete database backup is performed each day
and stored during one week. Each week a secured backup is stored on CD.

Finally, every connection to Project NetBoard is made using the https protocol
to login to the platform _._

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

5\. Ethical aspects

</td>  
<td>

There are no ethical issues regarding the project.

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

6\. Other

</td>  
<td>

N/A

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

##  f. WP6 – Manufacturing process

N/A according to IP definition and management.

##  g. WP7 – Economical aspects and implementation strategy

N/A

This topic and associated results are highly confidential and cannot be shared
by industrial partners.

##  h. WP8 – RCS standardisation work  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**WP8_1_safety levels composite cylinders_data**

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

1\. Data summary

</td>  
<td>

**Purpose:** Identify and improve existing safety level of composite cylinders
and standards.

**Data formats** : *.xlsx, *.docx, *.pdf, *.pptx

**Will you re-use any existing data and how?**

  * N/A 

  

**What is the origin of the data?**

  * Experimental test results 

  

**What is the expected size of the data?**

  * The total size of all data will be approx. less than 0,2 Gb. 

  

**To whom might it be useful ('data utility')?**

  * Project partners, scientific community, notified bodies, competent authority 

  

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

2\. FAIR Data

</td>  
<td>

Findable, Accessible, Interoperable, Re-usable

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

2.1 Making data findable, including provisions for metadata

</td>  
<td>

Description of the data:

\- The following naming for the dataset will be

WP8_1_BAM_safety levels composite cylinders_data

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

2.2 Making data openly accessible

</td>  
<td>

  * mainly results of normalised data needed for publications (national/international scientific community and standards committee) 

  

  * Shared documents/data uploaded to Project Netboard All Data will be stored on company internal shared directory with limited number of users 

  

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

2.3 Making data interoperable

</td>  
<td>

All published data are generated with common programs and stored within common
file formats and therefore they are interoperable and can be re-use between
researchers, institutions, companies etc.

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

2.4. Increase data re-use (through clarifying licences)

</td>  
<td>

Specify the licenses and the conditions for sharing and reusing the data:

\- Creative Commons:

(CC BY-ND 3.0 DE or CC BY-NC-ND 3.0 DE) https://creativecommons.org/

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

3\. Allocation of resources

</td>  
<td>

All costs related to the data collection and processing are covered by the
project budget with dedicated person months under WP9.

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

4\. Data security

</td>  
<td>

Audio, doc and xls files will be deposited in ABSISKEY servers and will be
protected with the ABSISKEY server’s security protocol:

PNB security is provided by OVH. OVH is currently the number 3 web hosting
provider worldwide.

OVH condition of security:  _https://www.ovh.co.uk/aboutus/security.xml_ and
_https://www.ovh.co.uk/aboutus/datacentres.xml_

In addition to this security, a complete database backup is performed each day
and stored during one week. Each week a secured backup is stored on CD.

Finally, every connection to Project NetBoard is made using the https protocol
to login to the platform _._

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

5\. Ethical aspects

</td>  
<td>

There are no ethical issues regarding the project.

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

6\. Other

</td>  
<td>

N/A

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

_**i. WP9 – Dissemination and exploitation strategy** _

NA  
  
<table>  
<tr>  
<th>

**WP /**

**Task**

</th>  
<th>

**Responsible partner**

</th>  
<th>

**Dataset name**

</th>  
<th>

**File types**

</th>  
<th>

**Findable**

</th>  
<th>

**Accessible**

</th>  
<th>

**Interoper able**

</th>  
<th>

**Reusable**

</th>  
<th>

**Size**

</th>  
<th>

**Security**

</th>  
<th>

**Ethics**

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

WP3

T3.5

</td>  
<td>

TUC

</td>  
<td>

WP3_1_Simulation

assumptions_data

</td>  
<td>

*.xlsx, *.docx, *.pdf, *.pptx 
</td>  
<td>

WP3_1_Simulation

assumptions_data

</td>  
<td>

Results published (papers, presentation

etc.)

\- depository: project netboard

</td>  
<td>

Yes

</td>  
<td>

Yes

</td>  
<td>

<0,2 GB

</td>  
<td>

Kept in AK /TUC servers

</td>  
<td>

N/A

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

WP8 /

T08.01,

T08.02, T08.03.

</td>  
<td>

BAM

</td>  
<td>

WP8_1_safety levels composite cylinders_data

</td>  
<td>

*.xlsx, *.docx, 

*.pdf, *.pptx 

</td>  
<td>

WP8_1_BAM_safe

ty levels

composite cylinders_data

</td>  
<td>

  * Results published (papers, presentation 

  

etc.)

  * depository: project netboard and company 

  

internal

</td>  
<td>

Yes

</td>  
<td>

License publications

CC BY-ND 3.0 DE or CC BY-NC-ND

3.0 DE

</td>  
<td>

<0,2 GB

</td>  
<td>

Kept in AK

/BAM

servers

</td>  
<td>

N/A

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

**D1.4__TAHYA-P6_AK_190115** Page **13** / **16**

**5.**

**SUMMARY TABLE**

**6.**