#  CATANA H2020 CS2 PROJECT

##  Deliverable 6.2

###  1\. Data management and responsibility

The CATANA project is engaged in the Open Research Data (ORD) pilot which aims
to improve and maximise access to and re-use of research data generated by
Horizon 2020 projects and takes into account the need to balance openness and
protection of scientific information, commercialisation and Intellectual
Property Rights (IPR), privacy concerns, security as well as data management
and preservation questions.

The management of the project data/results requires decisions about the
sharing of the data, the format/standard, the maintenance, the preservation,
etc.

Thus the Data Management Plan (DMP) is a key element of good data management
and is established to describe how the project will collect, share and protect
the data produced during the project. As a living document, the DMP will be
updated over the lifetime of the project whenever necessary.

In this frame the following policy for data management and responsibility has
been agreed for the CATANA project:

  * **The CATANA Management Team (Coordinator ECL, Leader ECL-LMFA/ ECL-LTDS / VKI)** analyses the results of the CATANA project and will decide the criteria to select the Data for which make the OPT-IN. They individuate for all the dataset a responsible (Data Management Project Responsible (DMPR)) that will ensure dataset integrity and compatibility for its internal and external use during the programme lifetime, etc. They also decide where to upload the data, when upload, when how often update, etc. 

  

  * **The Data Management Project Responsible (DMPR)** is in charge of the integrity of all the dataset, their compatibility, the criteria for the data storage and preservation, the long-term access policy, the maintenance policy, quality control, the DMP’s update, etc. Of course he will discuss and validate these points with the Project Management team (ECL and VKI). 

  

  
<table>  
<tr>  
<th>

**Data management Project Responsible (DMPR)**

</th>  
<th>

**Christoph BRANDSTETTER**

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

DMPR Affiliation

</td>  
<td>

Ecole Centrale de Lyon

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

DMPR mail

</td>  
<td>

christoph.brandstetter@ec-lyon.fr

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

DMPR telephone number

</td>  
<td>

+33 (0) 4.72.18.61.94

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

  * **The Data Set Responsibles (DSR)** are in charge of their single Dataset and should be the partner producing the data: validation and registration of datasets and metadata, updates and management of the different versions, etc. The contact details of each DSR will be provided in each data set document presented in the annex I of the DMP. 

  

In the next section “2. Data summary”, the CATANA Project Management Team (ECL
and VKI) have listed the project’s data/results that will be generated by the
project and have identified which data will be open. The anticipated database
resulting from the experimental campaigns and the development of the open-
test-case will be exhaustive. All validated data will be made accessible to
the open domain. The internal database only contains non-validated results and
data concerning facility infrastructure and manufacturing documents which are
not related to the open-test-case.

Page **4 / 14**

#  CATANA H2020 CS2 PROJECT

##  Deliverable 6.2

###  2\. Data summary

The next table presents the different dataset generated by the CATANA project.
For each dataset that will be open to public, a dedicated dataset document
will be completed in Annex I once the data are generated.

_Explanation of the columns:_

  * **Nature of the data** : experimental data, numerical data, documentation, software code, hardware, etc. 

  

  * **WP generation** : work package in which the database is generated 

  

  * **WP using** : work package in which data are reused in the CATANA project - **Data producer** : partner who generates the data - **Format** : can be .pdf / .step / .txt / .bin, etc. 

  

  * **Volume** : expected size of the data 

  

  * **Purpose / objective** : purpose of the dataset and its relation to the objectives of the project. 

  

  * **Dissemination level** : internal (non-validated results and data concerning facility infrastructure and manufacturing documents) / public (validated experimental and design data, metadata and open-test-case) 

  

Page **5 / 14**  
  
<table>  
<tr>  
<th>

</th>  
<th>

**Dataset**

</th>  
<th>

**Nature of the data**

</th>  
<th>

**WP**

**generation**

</th>  
<th>

**WP**

**using**

</th>  
<th>

**Data producer**

</th>  
<th>

**Format**

</th>  
<th>

**Volume**

</th>  
<th>

**Purpose/objectives**

</th>  
<th>

**Dissemination Level**

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

**1**

</td>  
<td>

**Test Bench / Geometry Data**

</td>  
<td>

CAD/Plan

</td>  
<td>

WP 1/2

</td>  
<td>

WP

3,4,5

</td>  
<td>

ECL-LMFA

</td>  
<td>

.pdf,

.step

</td>  
<td>

1 GB

</td>  
<td>

  * Contains plans and CAD of test vehicles. 

  

  * Provides necessary information for test bench implementation and numerical simulation. 

  

</td>  
<td>

Internal

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

**2**

</td>  
<td>

**Rotor Blade**

**Manufacturing**

**Documents**

</td>  
<td>

CAD/Plan

</td>  
<td>

WP 1/2

</td>  
<td>

WP

3,4,5,6

</td>  
<td>

ECL-LMFA

</td>  
<td>

.txt,

.step,

.pdf

</td>  
<td>

1 GB

</td>  
<td>

Allows Fabrication of Rotor blades by

Manufacturer

</td>  
<td>

Internal

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

**3**

</td>  
<td>

**Accessory Part**

**Manufacturing Documents**

</td>  
<td>

CAD/Plan

</td>  
<td>

WP 1/2

</td>  
<td>

WP

3,4,5,6

</td>  
<td>

ECL-LMFA

</td>  
<td>

.txt,

.step,

.pdf

</td>  
<td>

1 GB

</td>  
<td>

\- Allows fabrication of Nose Cone, Liner,

Interblade Platform, OGV, OGV Platform, Liner Inserts

</td>  
<td>

Internal

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

**4**

</td>  
<td>

**components screening data**

</td>  
<td>

Experimental measurements, tomography

</td>  
<td>

WP 2

</td>  
<td>

WP 4,5

</td>  
<td>

ECL-LMFA

</td>  
<td>

.txt,

.bin

</td>  
<td>

1 TB

</td>  
<td>

  * Contains all measurements in measured primary units (generally volt). Including geometry, roughness, weight, porosity 

  

  * Provides measurement ready to be converted in the physical units. 

  

</td>  
<td>

Internal

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

**5**

</td>  
<td>

**Rotor structural**

**Data (Ping**

**Test/Vacuum**

**Test PHARE-1)**

</td>  
<td>

Metrology

</td>  
<td>

WP 3

</td>  
<td>

WP

4,5,6

</td>  
<td>

ECL-LTDS ECL-LMFA

</td>  
<td>

.txt,

.bin

</td>  
<td>

10 GB

</td>  
<td>

  * Contains sensors calibration and position, test-bench qualification tests, tests log … 

  

  * Provides necessary information on the measurements and 3D test bench setup. 

  

</td>  
<td>

Internal

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

**6**

</td>  
<td>

**Measurement Results PHARE-2**

</td>  
<td>

Metrology

</td>  
<td>

WP5

</td>  
<td>

WP 6

</td>  
<td>

ECL-LMFA

VKI

</td>  
<td>

.txt,

.tdms,

.bin,

.b16,

.cgns

</td>  
<td>

100 TB

</td>  
<td>

\- Raw data and calibrated data of:

Performance Instr.; Strain Gauges, Wall

Pressure/Microphone, Tt/Pt Probes, Tip

Timing, Tip Clearance, PIV, LDA

</td>  
<td>

Internal

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

**8**

</td>  
<td>

**Validated experimental data**

</td>  
<td>

Experimental Measurements

</td>  
<td>

WP 5

</td>  
<td>

WP 6

</td>  
<td>

ECL-LMFA

VKI

</td>  
<td>

.txt,

.tdms,

.bin,

.b16,

.cgns

</td>  
<td>

1 TB

</td>  
<td>

  * Contains measurement descriptions and the operating conditions from the validated experimental database. 

  

  * Provides necessary information to perform analysis of the validated experimental database. 

  

</td>  
<td>

Public

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

#  CATANA H2020 CS2 PROJECT

##  Deliverable 6.2  
  
<table>  
<tr>  
<th>

**9**

</th>  
<th>

**Published experimental data**

</th>  
<th>

Experimental Measurement

</th>  
<th>

WP 5

</th>  
<th>

WP 6

</th>  
<th>

ECL-LMFA

VKI

</th>  
<th>

.txt,

.tdms,

.bin,

.b16,

.cgns

</th>  
<th>

50 GB

</th>  
<th>

  * Contains experimental data used for publication purposes. 

  

  * Provides an experimental open-access database for the research community. 

  

</th>  
<th>

Public

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

**10**

</td>  
<td>

**Published Open Test Case Data**

</td>  
<td>

CAD/Plan

Experimental

Measurement

</td>  
<td>

WP 1,2,3

</td>  
<td>

WP 6

</td>  
<td>

ECL-LMFA

ECL-LTDS

VKI

</td>  
<td>

.txt,

.tdms,

.cgns,

.docx,

.pdf

</td>  
<td>

50 GB

</td>  
<td>

  * Contains geometry data of Rotor, Annulus and OGV incl. roughness and measured tip clearance for each blade, Measured 

  

structure-dynamic spectra of Rotor blades,

Eigenmodes, structural damping, mistuning patterns,

  * Provides necessary information to perform analysis of the validated experimental database (metadata). 

  

</td>  
<td>

Public

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

**11**

</td>  
<td>

**Experimental**

**Documentation DATA**

</td>  
<td>

Documentation

</td>  
<td>

WP 3,4,5

</td>  
<td>

</td>  
<td>

ECL-LMFA

ECL-LTDS

VKI

</td>  
<td>

.docx+ .pdf

</td>  
<td>

10 MB

</td>  
<td>

  * Contains the experimental strategy setup, all plan 

  

  * Provides the necessary setup to realize experiments. 

  

</td>  
<td>

Internal

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

Page **7 / 14**

#  CATANA H2020 CS2 PROJECT

##  Deliverable 6.3

###  3\. FAIR Data

**3.1 Making data findable**

####  Public database (data sets 9 and 10)

The databases generated in the project will be identified by means of a
Digital Object Identifier linked to the published paper, and archived on the
ZENODO searchable data repository together with pertinent keywords. As part of
the attached documentation, the file naming convention will be specified on a
case-by-case basis. In case of successive versions of a given dataset, version
numbers will be used. Where relevant, the databases will be linked to
metadata.

Articles and the attached data will be findable via their DOI, unique and
persistent identifier. A DOI is usually issued to every published record on
each publisher review and on other repositories as ZENODO, HAL and
ResearchGate. A homepage of CATANA project will be created on ResearchGate
with a link to ZENODO to make data findable.

####  Internal database

#####  Database repository

Internal databases are composed of both the methods and the results. ECL and
VKI (as indicated in Table 1) are the owners of all results. Partners are
owners of methods used to generate results. Each owner is responsible for its
database repository.

#####  Data identification

Each measurement raw data are identified by a unique identifier. Each
measurement is recorded in the test log using this identifier and the
measurement information. A validated measurement data uses the same
identification as the corresponding raw data. Main information on measurement
is reported in the data experimental guide.

######  3.2 Making data openly accessible

By default, all scientific publications will be made publicly available with
due respect of the Green / Gold access regulations applied by each scientific
publisher. Whenever possible, the papers will be made freely accessible
through the project web site and the open access online repositories ArXiv and
HAL.

The public databases that will be selected to constitute the project
validation benchmarks will be archived on the ZENODO platform, and linked from
the CATANA project website. If the volume of the produced data exceeds
limitations of the open repository, the data will be made accessible via the
CATANA website hosted by Ecole Centrale de Lyon with a link to the data
included in the ZENODO repository. The most relevant data will be stored
directly in ZENODO. Ascii-readable file formats will be preferred for small
datasets, and binary encoding will be implemented for large datasets, using
freely available standard formats (e.g. the CFD Generic Notation System) for
which the source and compiled import libraries are freely accessible. In the
latter case, the structure of the binary records (headers) will be documented
as part of the dataset. The CATANA Consortium as a whole will examine the
suitability of the datasets produced by the project for public dissemination,
as well as their proper archival and documentation. Each dataset will be
associated with a name of a partner responsible for its maintenance.

#####  Access procedures

Databases declared public will be available on online depositories (ZENODO) to
a third party. All data set contains conditions to use public data in the file
header. These conditions are an obligation to refer to the original papers,
the project name and a reference to Clean Sky 2 Joint Undertaking under the
European Union’s Horizon 2020.

#####  Tools to read or reuse data

Public data are produced in common electronic document/data/image formats
(.docx, .pdf, .txt, .jpg, etc.) that do not require specific software.

####  Internal database

#####  Access procedures

After agreement within the CATANA Consortium, all validated experimental data
and cleared geometry information can be shared and published according to the
consortium agreement. At long term the data generated by ECL and VKI can be
used for internal research.

######  3.3 Making data interoperable

The interoperability of the published datasets will be enforced by the
adoption of freely available data standards and documentation. Ad-hoc
interfaces will be developed and documented where needed. A common vocabulary
will be adopted for the definition of the datasets, including variable names
and units.

Classical vocabulary in turbomachinery domain is used (based on the experience
of all partners in turbomachinery publications).

####  Public database (databases 9 and 10)

The validated experimental database which will be opened for publication will
contain both dimensional (SIUnits) as well as dimensionless variables (Mach-
Number, Pressure Ratio , efficiency, etc.) to maximize the impact of the
generated results, specifically to permit comparison with other cases allow
the community to validate computational methods.

####  Internal database

Validated databases are used for analysis. These databases are directly
expressed in physical units (using SI unit system). Necessary information
about results are recorded in the different data guides

**3.4 Increase data re-use**

_Data licence_

Data from public databases are open access and used a common creative licence
(CC-BY).

#####  Data quality assurance processes

The project will be run in the frame of the quality plan developed at LMFA,
since 2005, in the context of the measurement campaigns carried out with the
high-speed compressors of LMFA. This quality plan is based on an ISO 9001
version 2000 approach and the use of an intranet tool (MySQL database coupled
with a dynamic php web site) to store, to classify and to share the data
between the partners, such as measurement data, documents including a
reference system.

Page

_After the end of the project_

####  Public database (databases 6 and 7)

With the impulsion of CATANA project, the open access databases can be used by
other laboratories and industrials to made comparison with other machines.

Methods developed and physical analyses become references to other test cases
and improve the knowledge of the community.

####  Internal database

The experimental setup and the huge quantity of experimental and numerical
data cannot be completely exploited in the CATANA project. The project is the
starting point to a long collaboration. At the end of the project, the re-use
of data and test bench can be:

  * Analysis of data generated in CATANA project: 

    * Subsequent projects for consortium members. 

  

    * Additional academic partners to work on not exploited data. 

  

  

  * Supplementary experimental measurements: o Using the already installed compressor module on new operating conditions o Measurements of supplementary field with CATANA project results. 

  

  * Investigation of numerical prediction performances: o Calibrate aerodynamic, structure-dynamic, acoustic and coupled numerical methods 

  

###  4\. Allocation of resources

####  _Costs related to the open access and data strategy_

  * Data storage in partner data repositories: Included in partners structural operating cost. 

  

  * Data archiving with ZENODO data repositories: Free of charge. 

  

####  _Data manager responsible during the project_

The Project Coordinator (ECL) is responsible for the establishment, the
updates during the lifetime of the project and the respect of the Data
Management Plan. The relevant experimental data and the generated data from
numerical simulations during the CATANA project will be made available to the
Consortium members within the frame of the IPR protection principles and the
present Data Management Plan.

####  _Responsibilities of partners_

ECL (all measurement/geometric data) and VKI (probe measurements) are the
owners of all generated data. Methods and analysis keep the ownership of the
partner which generates it. Every partner is responsible for the data it
produces, and must contribute actively to the data management as set in the
DMP.

###  5\. Data security

####  Public database (databases 6 and 11)

_Long-term preservation_ : Using ZENODO repositories.

_Data Transfer_ : Using ZENODO web platforms

Intellectual property: All data set contains are attached to a common creative
licence.

####  Internal Data

_Long-term preservation:_ ensured by partner institutions’ data repositories.

_Data Transfer:_ depending on the data volume:

  * Small and medium size files are transferred by partners securitised data exchange platform (Renater FileSender, OpenTrust MFT ...) 

  

  * Huge size files are transferred by an external hard disk during face to face meeting. This type of transfer is infrequent and only concerns transfer of final databases from ECL and VKI. 

  

_Intellectual property:_ Data are confidential and need to strictly respect
the definition of data producer, user and owner.

  6. **Ethical aspects**

  

  

No ethical issue has been identified.

  7. **Other**

  

  

No other procedure for data management.