Grant Agreement No.

: 760941

Project acronym: ReSiSTant

Project title: Large riblet surface with super hardness,mechanical

and temperature resistance by nano functionalization

Call (part) identifier: H2020-NMBP-PILOTS-2017

Topic: PILOTS-03-2017 Pilot lines for manufacturing of

nanotextured surfaces with mechanically enhanced properties

Starting date of project: 1st of January, 2018

Duration: 48 months

WP 1 – Project Management
Deliverable D1.3 – Data Management Plan

Due date of deliverable: 30th June 2018

Actual submission date: 29th June 2018

Organisation name of lead contractor for this deliverable: RINA-C

Dissemination Level
CO Confidential, only for members of the consortium (including the
Commission Services)
PU Public X

1
D1.3 Data Management Plan
Executive Summary
The present document represents the Deliverable D1.3: Data Management Plan of the ReSiSTant
project, co-funded by the European Commission within the Horizon 2020 programme - Grant
Agreement nº 760941.
The Data Management Plan described in this document follows the template proposed by
the European Commission for Open Research Data Pilot projects within the H2020 program.
In particular the present DMP describes the data management life cycle for the data to be collected,
processed and/or generated by the project. As part of making research data findable, accessible,
interoperable and re-usable (FAIR) the present public document includes information on: i) the
handling of research data during and after the end of the project, ii) what data will be collected,
processed and/or generated, iii) which methodology and standards will be applied, iv) whether data
will be shared/made open access and how data will be curated and preserved (including after the
end of the project).

2
D1.3 Data Management Plan
Table of Contents
Executive Summary ...................................................................................................................... 2
List of abbreviations / Nomenclature ............................................................................................. 4
1 Introduction ........................................................................................................................... 5
2 Data Summary ...................................................................................................................... 6
3 FAIR Data ........................................................................................................................... 14
3.1 Making data findable, including provisions for metadata ............................................... 14
3.2 Making data openly accessible ..................................................................................... 14
3.3 Making data interoperable ............................................................................................ 14
3.4 Increase data re-use (through clarifying licences) ......................................................... 15
4 Allocation of resources ........................................................................................................ 15
5 Data security ....................................................................................................................... 16
6 Ethical aspects.................................................................................................................... 16
7 Other issues........................................................................................................................ 16
8 Conclusions ........................................................................................................................ 17

D1.3 Data Management Plan

List of abbreviations / Nomenclature
Abbreviation Definition
WP Work package
GA Grant Agreement
DMP Data Management Plan
CA Consortium Agreement
WBS Work Breakdown Structure
FAIR findable, accessible, interoperable and re-usable

D1.3 Data Management Plan

1 Introduction
The present document has been prepared in agreement with the FAIR template as such the
following Chapters are presented:
 Chapter 2: Data Summary
 Chapter 3: FAIR Data comprehending the subchapters:
o 3.1. Making data findable, including provisions for metadata
o 3.2. Making data openly accessible
o 3.3 Making data interoperable
o 3.4. Increase data re-use
 Chapter 4: Allocation of resources
 Chapter 5: Data security
 Chapter 6: Ethical aspects
 Chapter 7: Other issues
 Chapter 8: Conclusions
Since some information is considered Confidential from partners this report discloses only the
information has been considered might be for public dissemination by the Consortium. This
document presents the Data Management Plan for the Consortium at M6 and it will be revised
along with the course of the project at least every 6 months.

D1.3 Data Management Plan

2 Data Summary
The present chapter intends to provide and answer to a number of questions as:

 What is the purpose of the data collection/generation and its relation to the objectives of the
project?
 What types and formats of data will the project generate/collect?
 Will you re-use any existing data and how?
 What is the origin of the data? What is the expected size of the data? To whom might it be
useful ('data utility')?)
RESISTANT is a project aimed at optimizing two industrial pilot lines by using micro and nano-
structured surfaces for drag reduction. The main objective is to implement the new surfaces into
aircraft turbofan engines and industrial compressors. The demonstration at the two dedicated pilot
lines will occur at TRL7 level, this implies that the solutions must be tested and monitored in order
to be analysed. In addition, some techno-economic analysis must be done for each demonstrator,
facts that will produce a big number of data sets that must be handled properly.
RESISTANT data differentiates between two classes of datasets:
 Data generated during research activities. These data come from the activities developed
within each work package. This document serves to define which dissemination level they
will have
 Project deliverables generated within the 10 project workpackages. These are the datasets
that will be based on the aforementioned results. Their dissemination level is already
defined within the Grant Agreement and reported in the following table.

Table 1. Project deliverables.

ID Deliv Deliverable name Type Disseminatio

# erabl n level
e
No.
1 D1.1 Executive Action Plan O CO
2 D1.2 Project Quality Plan R CO
3 D1.3 Data Management Plan ORDP PU
4 D2.1 Adaption of mesh quality for numeric riblet simulation R CO
5 D2.2 Adjustment of numerical simulation with riblet mesh vs. R CO
normal mesh
6 D2.3 Riblet simulation for industrial testing R CO
7 D2.4 Riblet numbers and positions DEM1 R CO
8 D2.5 Riblet numbers and positions DEM2 R CO
9 D2.6 Expected impact on performance R PU
10 D2.7 Riblet simulation evaluation R CO
11 D3.1 Design and construction test rig DEM2 R CO
12 D3.2 Assembly and commissioning test rig DEM2 D PU
13 D3.3 Aerodynamic design freeze of test rig R CO
14 D3.4 Structural mechanics and dynamics of test rig R CO
15 D3.5 Reference measurements test rig DEM2 R CO
16 D3.6 Test rig assembly and commissioning DEM1 D PU
6

D1.3 Data Management Plan

ID Deliv Deliverable name Type Disseminatio
# erabl n level
e
No.
17 D4.1 Feasibility study material for DEM1 and DEM2 R CO
18 D4.2 Master moulds manufactured and quality approved for R CO
DEM1 and DEM2
19 D4.3 Coating material for DEM1 R CO
20 D4.4 Coating material for DEM2 R CO
21 D4.5 Application Riblets DEM2 D CO
22 D4.6 Application Riblets DEM1 D PU
23 D4.7 Preliminary Life Cycle Sustainability of the ReSiSTant R PU
Pilot lines
24 D5.1 Design and development of functionalized D CO
nanoparticles with related nano-structuring process
(stabilization, nano-structure)
25 D5.2 Development of the optimized nanostructured coating D CO
material DEM1 and DEM2
26 D5.3 Nanosafety test results R CO
27 D5.4 Upscaling of the nanostructured coating material D CO
production at industrial level
28 D6.1 Demonstration KPI panel R CO
29 D6.2 Test report reference surface set up (without riblets) R CO
test rig DEM2
30 D6.3 Test report test rig DEM1 R CO
31 D6.4 Test report riblet surface set up test rig DEM2 D CO
32 D6.5 Reference measurements test rig DEM1 R CO
33 D7.1 Manufacturing and repair process evaluation R CO
34 D7.2 Test modified test engine CFM56-5C D PU
35 D7.3 Test and evaluation riblet test DEM1 D PU
36 D7.4 Certification for flight test campaign R CO
37 D8.1 Design review compressor stage DEM2 R CO
38 D8.2 Test design and assembly finished D CO
39 D8.3 Test and evaluation riblet tests DEM2 D PU
40 D9.1 Business model to support the partners aiming at the R PU
commercial exploitation of the project results
41 D9.2 ReSiSTant Commercialization technology roadmap R PU
42 D9.3 Plan for the upscale and optimization of ReSiSTant R PU
demonstrator pilot lines
43 D9.4 ReSiSTant standardization document R PU
44 D9.5 ReSiSTant Stakeholders’ vision document R CO
45 D9.6 Business plan for application of nanoriblet coatings in R CO
aircraft turbofans
46 D9.7 Business plan for application of nanoriblet coatings in R CO
industrial compressors
47 D10.1 Dissemination strategy R CO
48 D10.2 Public website online O PU
49 D10.3 Dissemination material: poster and flyer O PU
50 D10.4 Report on Dissemination and communication activities R PU
I

D1.3 Data Management Plan

 ID Deliv Deliverable name Type Disseminatio
# erabl n level
e
No.
51 D10.5 Report on dissemination and communication activities R PU
II
52 D10.6 Report on dissemination and communication activities R PU
III
53 D10.7 Safe by design report R CO
54 D10.8 Report on dissemination and communication activities R PU
IV
55 D10.9 Report on networking workshop R PU

At present the following data sets have been identified, specifying relevant aspects such as the
origin, utility or format.
Table 2. Datasets from WP1.

WP1 Project Management

Dataset 1.1
T1.3: Monitoring and reporting Task 1.4: Financial administration
Related project task
and maintenance of legal documents
Description Technical and economic reporting data will be reported to the EU
Origin and reuse of data Partners and participant portal
Data Utility Consortium and the EU
Type and Format Report (.doc/.pdf)
Expected Size -
Keywords Technical, financial, report
Open to the public or
Confidential
confidential
In case of confidential:
why? (separate legal and The technical and economical progression of the project is not of
contractual reasons from public interest
voluntary restrictions).

Table 3. Datasets from WP2.

WP2 Simulation
Dataset 2.1
T2.1: Adaption of mesh quality for numeric riblet simulation
T2.2: Adjustment of numerical simulation with riblet mesh vs.
Related project task normal mesh.
T2.3: Riblet simulation for industrial testing
T2.7: Riblet simulation evaluation
Description Mesh adaption and simulations

D1.3 Data Management Plan

Origin and reuse of data Partners participants and BST
Data Utility Validation and baseline for future work
Geometry (.stp), Mesh (.msh), Simulation (.cas,.dat (Fluent); .def,
Type and Format
.cfx, .res (CFX))
Expected Size Order of magnitude: 100 GB
Keywords Mesh, Simulation, Riblets, Performance
Open to the public or
Confidential
confidential
In case of confidential:
why? (separate legal and
Due to the privacy of the internal BST riblet algorithm.
contractual reasons from
voluntary restrictions).
Dataset 2.2
T2.4, T2.5:Riblet numbers and positions DEM1 and DEM2
Related project task
T2.6: Expected impact on performance
Description Detailed riblet geometries and the expected performance
Origin and reuse of data Data produced before by BST
Based on this data, the topography of the master moulds will be
Data Utility
manufactured and the utility of riblets will be exploited.
Type and Format Report (.doc/.pdf)
Expected Size Order of magnitude: 10 MB
Master mould, Riblet spacing, Riblet height, Coating Scenario,
Keywords
Performance
Open to the public or T2.4, T2.6: Confidential
confidential T2.6 Public
In case of confidential:
why? (separate legal and
Due to the privacy of the internal BST riblet algorithm.
contractual reasons from
voluntary restrictions).

Table 4. Datasets from WP3.

WP3 Rig design manufacturing and commissioning

Dataset 3.1
Related project task T3.1, T3.5
Description DEM 1 & DEM2 Aerodynamic design and CAD
Origin and reuse of data Partners participants and TUG/RWTH
Data Utility Based on this data the manufacturing, rig assembly will be done
Type and Format Dwg,…
Expected Size -

D1.3 Data Management Plan

Keywords CAD, DEM1,DEM2
Open to the public or
Confidential
confidential
In case of confidential:
why? (separate legal and
Data are protected according to partners policy
contractual reasons from
voluntary restrictions).
Dataset 3.2
Related project task T3.8
Description Data related to the upgrade of the measurement system
Origin and reuse of data DEM2 testing
These data allow to investigate the influence of flow phenomena on
Data Utility
the compressor performance experimentally
Type and Format -
Expected Size -
Keywords Flow field, boundary layer, performance measurement
Open to the public or
Public
confidential
In case of confidential:
why? (separate legal and Data will be made available in conjunction, for example, of papers
contractual reasons from publication
voluntary restrictions).
Table 5. Datasets from WP4.

WP4 Material and application

Dataset 4.1
T 4.1. Screening of raw material and coatings for high temperature
Related project task
riblet coatings
Screening for 2K-silicones and compatible co-binders e.g.
Description polyurethanes fulfilling the requirements for the
application cases.
Project partners, raw material manufactures und first own material
Origin and reuse of data
developments
Data Utility Consortium and the EU
Report Deliverable D4.1
Type and Format

Expected Size -
Keywords Screening raw material coatings
Open to the public or
Confidential
confidential
In case of confidential:
why? (separate legal and
The technical progression of the project is not of public interest
contractual reasons from
voluntary restrictions).
10

D1.3 Data Management Plan

 Table 6. Datasets from WP5.

WP5 Nanofunctionalization
Dataset 5.1
Related project task T5.1
Description Development of material nanostructure material
Origin and reuse of data Lab data
Data Utility Demonstrators development
Type and Format Table / .xlsx, .csv
Expected Size Not known
Keywords Nanomaterial, functionalization, validation
Open to the public or
Confidential
confidential
In case of confidential:
why? (separate legal and
Data for Demonstrators
contractual reasons from
voluntary restrictions).

Table 7. Datasets from WP6.

WP6 Industrial testing

Dataset 6.1
Related project task Tasks 6.1-6.5
Description Demonstrator characterization and monitoring
Origin and reuse of data Data acquisition through monitoring system at test rigs
Data utility* Validation of numerical results
Type and Format Table / .xlsx, .csv
Expected size Not known
Keywords Demonstrators, validation
Open to the public or confidential Confidential
In case of confidential: Why?
(Separate legal and contractual
Data from Demonstrators
reasons from voluntary
restrictions).

11

D1.3 Data Management Plan

 Table 8. Datasets from WP7.

WP7 Demonstrator 1: aircraft turbofan

Dataset 7.1
Related project task Task 8.1-8.2
Description Raw data from demo cases
Origin and reuse of data Monitoring
Data Utility Demo sites evaluation
Type and Format .csv, .xlsx
Expected Size Not known
Keywords Monitoring, data acquisition
Open to the public or confidential Confidential
In case of confidential: why?
(separate legal and contractual
Data from demos
reasons from voluntary
restrictions).

Table 9. Datasets from WP8.

WP8 Demonstrator 2: Industrial compressor

Dataset 8.1
Related project task Task 8.1-8.2
Description Raw data from demo cases
Origin and reuse of data Monitoring
Data utility* Demo sites evaluation
Type and Format .csv, .xlsx
Expected size Not known
Keywords Monitoring, data acquisition
Open to the public or confidential Confidential
In case of confidential: Why?
(Separate legal and contractual
Data from demos
reasons from voluntary
restrictions).

12

D1.3 Data Management Plan

 Table 10. Datasets from WP9.

WP9 Upscaling and exploitation

Dataset 9.1
Related project task Task 9.4
Data to develop techno-economic analysis for demo
Description
partners
Origin and reuse of data W8, WP7,Wp6
Data utility* Replication of ReSiSTant Demonstrators
Type and Format .xlsx, .docx
Expected size -
Keywords investments
Open to the public or confidential Confidential
In case of confidential: Why?
The techno-economic analyses of the demonstrators
(Separate legal and contractual
contain information that is important to safeguard for the
reasons from voluntary
demo partners competitiveness
restrictions).

Table 11. Datasets from WP10.

WP10 Dissemination
Dataset 10.1
Related project task T10.1
Description Project identity toolkit
Origin and reuse of data Own development
Data utility* Public reports and presentations of the Project
Type and Format .docx, .png, .ppt
Expected size Not known
Keywords Identity toolkit
Open to the public or confidential Public
In case of confidential: why?
(separate legal and contractual
-
reasons from voluntary
restrictions).

13

D1.3 Data Management Plan

3 FAIR Data
3.1 Making data findable, including provisions for metadata
The present chapter intends to provide and answer to a number of questions as:
 Are the data produced and/or used in the project discoverable with metadata, identifiable
and locatable by means of a standard identification mechanism (e.g. persistent and unique
identifiers such as Digital Object Identifiers)?
 What naming conventions do you follow?
 Will search keywords be provided that optimize possibilities for re-use?
 Do you provide clear version numbers?
 What metadata will be created?
 In case metadata standards do not exist in your discipline, please outline what type of
metadata will be created and how.)
In this framework Metadata identity providing info as Description, Reference, Creator is prepared.
Besides the metadata described above, ReSiSTant will include version of the document in order to
make data discoverable and identifiable, and Zenodo, an open access repository will be
investigated to be used to publish the results. Finally, identification of data produced within the
project will be also supported by a common naming convention. Example: ReSiSTant _WPx -
Dx.y_Title_Rev.1.0.pdf

3.2 Making data openly accessible

The present chapter intends to provide and answer to a number of questions as:
 Which data produced and/or used in the project will be made openly available as the
default?
 How will the data be made accessible (e.g. by deposition in a repository)?
 Where will the data and associated metadata, documentation and code be deposited?
 Have you explored appropriate arrangements with the identified repository?

In this framework there are limitations that will be followed by partners for publishing results, and
they already reported in the project Grant Agreement. The main project communication channel
will be the official website of ReSiSTant which was on air in April 2018. Other repositories like
Zenodo, an open access repository created by OpenAIRE, will be also considered for being used
for depositing the publications.

3.3 Making data interoperable

The present chapter intends to provide and answer to a number of questions as:

 Are the data produced in the project interoperable, that is allowing data exchange and re-
use between researchers, institutions, organisations, countries, etc. (i.e. adhering to
standards for formats, as much as possible compliant with available (open) software
applications, and in particular facilitating re-combinations with different datasets from
different origins)?

14

D1.3 Data Management Plan

  What data and metadata vocabularies, standards or methodologies will you follow to make
your data interoperable?
 Will you be using standard vocabularies for all data types present in your data set, to allow
inter-disciplinary interoperability?
 In case it is unavoidable that you use uncommon or generate project specific ontologies or
vocabularies, will you provide mappings to more commonly used ontologies?
As presented above the aforementioned standardized metadata is defined and it will be included
by default in the official template for deliverables, .ppts, etc. Moreover in case of executable files,
an additional .txt file with metadata content will be provided.

3.4 Increase data re-use (through clarifying licences)

The present chapter intends to provide and answer to a number of questions as:
 How will the data be licensed to permit the widest re-use possible?
 When will the data be made available for re-use?
 If an embargo is sought to give time to publish or seek patents, specify why and how long
this will apply, bearing in mind that research data should be made available as soon as
possible. Are the data produced and/or used in the project useable by third parties, in
particular after the end of the project?
 If the re-use of some data is restricted, explain why.
 How long is it intended that the data remains re-usable?
 Are data quality assurance processes described?
As anticipated in order to ensure the reuse of the generated results as much as possible Zenodo
repository will be considered. Moreover public data could be stored on the project website.

4 Allocation of resources
The present chapter intends to provide and answer to a number of questions as:
 What are the costs for making data FAIR in your project?
 How will these be covered?
 Note that costs related to open access to research data are eligible as part of the
Horizon 2020 grant (if compliant with the Grant Agreement conditions). Who will be
responsible for data management in your project?
 Are the resources for long term preservation discussed (costs and potential value, who
decides and how what data will be kept and for how long)?
Each partner will be responsible for their own confidential data management and conveniently and
clearly inform their WP leader about confidentiality requirements of each produced dataset.
Each WP leader will be responsible for providing open results from their work packages to the
WP10 leader, who will be in charge of uploading them to the Zenodo repository.
The WP10 (Communication and dissemination) leader will also take charge of publishing results in
the official website.

15

D1.3 Data Management Plan

5 Data security
The present chapter intends to provide and answer to a number of questions as:
 What provisions are in place for data security (including data recovery as well as secure
storage and transfer of sensitive data)?
 Is the data safely stored in certified repositories for long term preservation and curation?
 Are your data stored in a secure way? Where are you storing it? Is that server certified or
not?
In this framework each partner is going to follow its internal data security procedure whose
details are not herein presented for confidentiality reasons.

6 Ethical aspects
The present chapter intends to provide and answer to a number of questions as:
 Are there any ethical or legal issues that can have an impact on data sharing? These can
also be discussed in the context of the ethics review. If relevant, include references to ethics
deliverables and ethics chapter in the Description of the Action (DoA).
 Is informed consent for data sharing and long term preservation included in questionnaires
dealing with personal data?
In this framework there is not any ethical issue but informed consent for data sharing will be
collected if personal data will be needed from stakeholders feedback/info collection.

7 Other issues
Details in relation to other national/funder/sectorial/departmental procedures for data management
used by each partner are not herein presented as this is a public DMP release.

16

D1.3 Data Management Plan

8 Conclusions
The present DMP constitutes the firsts release of the ReSiSTant DMP.
The DMP foresees that each task leader and WP leader is responsible for defining the data
generated within his/her task and the level of confidentiality and agree with partners the path for
disclosing it. The present DMP is planned to be updated the project whenever significant changes
arise and in any case the document planned revision will occur on a yearly based timeframe and
uploaded on the project website private area.

17

D1.3 Data Management Plan