#  DATASETS

At this stage of the project, the following datasets are envisaged:

##  REFERENCE DESIGN

The reference design (v0) consists of a flat plate with no fins or any other
heat exchanger geometry and is intended to validate flow conditions inside the
wind tunnel and the heat transmission.

###  Experimental data: IDs **data_v0_exp_UPV** and **data_v0_exp_Purdue**

Table 1 _metadata for dataset Data_v0_exp_UPV_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the reference design

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

Creator

</td>  
<td>

UPV

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

Subject

</td>  
<td>

Reference design v0 (flat plate)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the reference design
gathered at UPV with the purpose of providing realistic conditions to create
and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v0_exp_UPV

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

Source

</td>  
<td>

UPV wind tunnel

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

Relation

</td>  
<td>

Data_v0_CFD, Data_v0_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

Table 2 _metadata for dataset Data_v0_exp_Purdue_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Validation data for the reference design

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

Creator

</td>  
<td>

Purdue

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

Subject

</td>  
<td>

Reference design v0 (flat plate)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the reference design
gathered at Purdue

with the purpose of validating both CFD simulations and initial experimental
measurements

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v0_exp_Purdue

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

Source

</td>  
<td>

Purdue wind tunnel

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

Relation

</td>  
<td>

Data_v0_CFD, Data_v0_exp_UPV

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

Rights

</td>  
<td>

TBD

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

###  Numerical data: ID **data_v0_cfd**

Table 2 _metadata for dataset Data_v0_cfd_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

CFD results for the reference design

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

Creator

</td>  
<td>

UPM

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

Subject

</td>  
<td>

Reference design (flat plate)

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

Description

</td>  
<td>

This dataset will include all the numerical results from the CFD calculations
carried out by UPM on

the v0 design geometry

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Numerical simulation data

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

Format

</td>  
<td>

ASCII text, HDF5, proprietary CFD format

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

Identifier

</td>  
<td>

Data_v0_cfd

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

Source

</td>  
<td>

UPM calculations

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

Relation

</td>  
<td>

Data_v0_exp_UPV, Data_v0_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

##  STANDARD DESIGN

The standard design (v1) will include typical heat exchanger fins and will
represent current state of the art approaches for SACOCs design.

###  Experimental data: IDs **data_v1_exp_UPV** and **data_v1_exp_Purdue**

Table 4 _metadata for dataset Data_v1_exp_UPV_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the reference design

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

Creator

</td>  
<td>

UPV

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

Subject

</td>  
<td>

Design v1 (standard fins)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v1 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v1_exp_UPV

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

Source

</td>  
<td>

UPV wind tunnel

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

Relation

</td>  
<td>

Data_v1_CFD, Data_v1_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

Table 5 _metadata for dataset Data_v1_exp_Purdue_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the standard design

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

Creator

</td>  
<td>

Purdue

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

Subject

</td>  
<td>

Design v1 (standard fins)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v1 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v1_exp_Purdue

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

Source

</td>  
<td>

Purdue wind tunnel

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

Relation

</td>  
<td>

Data_v1_CFD, Data_v1_exp_UPV

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

Rights

</td>  
<td>

TBD

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

###  Numerical data: dataset ID **data_v1_cfd**

Table 6 _metadata for dataset Data_v1_cfd_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

CFD results for the standard design

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

Creator

</td>  
<td>

UPM

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

Subject

</td>  
<td>

Design v1 (standard fins)

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

Description

</td>  
<td>

This dataset will include all the numerical results from the CFD calculations
carried out by UPM on

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

</td>  
<td>

the v1 design geometry

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

Publisher

</td>  
<td>

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

</td>  
<td>

TBD

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

Date

</td>  
<td>

</td>  
<td>

TBD

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

Type

</td>  
<td>

</td>  
<td>

Numerical simulation data

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

Format

</td>  
<td>

</td>  
<td>

ASCII text, HDF5, proprietary CFD format

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

Identifier

</td>  
<td>

</td>  
<td>

Data_v1_cfd

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

Source

</td>  
<td>

</td>  
<td>

UPM calculations

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

Relation

</td>  
<td>

</td>  
<td>

Data_v1_exp_UPV, Data_v1_exp_Purdue

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

Rights

</td>  
<td>

</td>  
<td>

TBD

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

</td>  
<td>

</td>  
<td>

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

##  ADVANCED DESIGN 1

The next iteration (v2) will feature an innovative design that departs from
the current approach of fin-type SACOCs.

###  Experimental data: IDs **data_v2_exp_UPV** and **data_v2_exp_Purdue**

Table 7 _metadata for dataset Data_v2_exp_UPV_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the advanced design 1

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

Creator

</td>  
<td>

UPV

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

Subject

</td>  
<td>

Design v2 (advanced design 1)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v2 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v2_exp_UPV

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

Source

</td>  
<td>

UPV wind tunnel

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

Relation

</td>  
<td>

Data_v2_CFD, Data_v2_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

Table 8 _metadata for dataset Data_v2_exp_Purdue_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the advanced design 1

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

Creator

</td>  
<td>

Purdue

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

Subject

</td>  
<td>

Design v2 (advanced design 1)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v1 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v2_exp_Purdue

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

Source

</td>  
<td>

Purdue wind tunnel

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

Relation

</td>  
<td>

Data_v2_CFD, Data_v2_exp_UPV

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

Rights

</td>  
<td>

TBD

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

###  Numerical data: dataset ID **data_v2_cfd**

Table 9 _metadata for dataset Data_v2_cfd_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

CFD results for the advanced design 1

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

Creator

</td>  
<td>

UPM

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

Subject

</td>  
<td>

Design v2 (advanced design 1)

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

Description

</td>  
<td>

This dataset will include all the numerical results from the CFD calculations
carried out by UPM on

the v2 design geometry

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Numerical simulation data

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

Format

</td>  
<td>

ASCII text, HDF5, proprietary CFD format

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

Identifier

</td>  
<td>

Data_v2_cfd

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

Source

</td>  
<td>

UPM calculations

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

Relation

</td>  
<td>

Data_v2_exp_UPV, Data_v2_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

##  ADVANCED DESIGN 2

The final iteration (v3) will feature a different innovative design for the
SACOC geometry.

###  Experimental data: IDs **data_v3_exp_UPV** and **data_v3_exp_Purdue**

Table 10 _metadata for dataset Data_v3_exp_UPV_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the advanced design 2

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

Creator

</td>  
<td>

UPV

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

Subject

</td>  
<td>

Design v3 (advanced design 2)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v3 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v3_exp_UPV

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

Source

</td>  
<td>

UPV wind tunnel

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

Relation

</td>  
<td>

Data_v3_CFD, Data_v3_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

Table 11 _metadata for dataset Data_v3_exp_Purdue_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

Experimental data for the advanced design 2

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

Creator

</td>  
<td>

Purdue

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

Subject

</td>  
<td>

Design v3 (advanced design 2)

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

Description

</td>  
<td>

This dataset will include all the experimental data of the v3 design gathered
at UPV with the

purpose of providing realistic conditions to cre-

ate and validate the CFD model

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Experimental data

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

Format

</td>  
<td>

ASCII text, MAT file, Excel workbook

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

Identifier

</td>  
<td>

Data_v3_exp_Purdue

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

Source

</td>  
<td>

Purdue wind tunnel

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

Relation

</td>  
<td>

Data_v3_CFD, Data_v3_exp_UPV

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

Rights

</td>  
<td>

TBD

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

###  Numerical data: dataset ID **data_v3_cfd**

Table 12 _metadata for dataset Data_v3_cfd_

####  FIELD VALUE  
  
<table>  
<tr>  
<th>

Title

</th>  
<th>

CFD results for the advanced design 2

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

Creator

</td>  
<td>

UPM

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

Subject

</td>  
<td>

Design v3 (advanced design 2)

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

Description

</td>  
<td>

This dataset will include all the numerical results from the CFD calculations
carried out by UPM on

the v3 design geometry

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

Publisher

</td>  
<td>

TBD

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

Contributor

</td>  
<td>

TBD

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

Date

</td>  
<td>

TBD

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

Type

</td>  
<td>

Numerical simulation data

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

Format

</td>  
<td>

ASCII text, HDF5, proprietary CFD format

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

Identifier

</td>  
<td>

Data_v3_cfd

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

Source

</td>  
<td>

UPM calculations

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

Relation

</td>  
<td>

Data_v3_exp_UPV Data_v3_exp_Purdue

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

Rights

</td>  
<td>

TBD

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

#  FAIR DATA

##  Making data findable, including provisions for metadata

The data produced in the project and described in the aforementioned tables
1-12 will be issued with DOI identifiers once it has reached an approved level
of maturity for consumption by interested parties. It is envisaged that the
DOIs will be assigned by the final, public data repository, which at this
point it is expected to be Zenodo. The metadata described in the
aforementioned tables follows the Dublin Core standard and will be uploaded to
the repository alongside the data and indexed, thus making it discoverable.

##  Naming conventions

The dataset ID will be Data_[design iteration]_[experimental/CFD]_[Facility
(if experimental)]; inside the dataset the variables will be named according
to habitual aerospace engineering vocabulary. It is envisaged that both static
and total thermodynamic will be provided. This will be updated with the
precise structure of the dataset once the data becomes available.

##  Search keywords

Adequate keywords will be provided alongside the data to maximize the re-use
potential. This will be updated with such keywords once the data is uploaded.

##  Version numbers

Presently the following overall version numbers are envisaged.

  * v0 Reference design: a flat plane with no special heat exchanger geometry 

  

  * v1 Standard design: SACOC equipped with standard fins 

  

  * v2 Advanced design 1: an innovative heat exchange geometry (TBD) 

  

  * v3 Advanced design 2: another innovative heat exchange geometry (TBD) 

  

Sub-versions will be added to this document if required.

_Searchable metadata_

The metadata will be added to the repository search mechanism.

##  Standardized formats

It is envisaged that standardised data formats will be used, such as:

  * ASCII text (.txt, .csv, .dat) 

  

  * Level 5 MAT-file format (MATLAB) (.mat) 

  

  * Microsoft Excel Workbook (.xls) 

  

  * Portable Document Format (.pdf) 

  

  * HDF5 (.hdf) 

  

This section will be updated if additional data formats are used.

##  Open file formats

Some of the formats may require the use of proprietary tools. The intention
however is to provide copies of the data in openly accessible formats for all
the data.

##  Open source tools

The objective is that all data be made accessible through open source tools,
such as Python, Octave, Calc, etc. for the experimental data, and ParaView,
VTK, etc. for the simulation data.

#  MAKING DATA OPENLY ACCESSIBLE

##  Openly available data

All data underlying the scholarly publications produced by the SACOC project
will be made openly available. it is envisaged at this point that data will
cover the thermodynamic variables describing the flow state in the
aforementioned designs.

##  Data location

The data will be included at first in the internal project repository with a
short description of the test case represented by the data and the information
contained in the data (limited metadata). Once that the data has reached
appropriate maturity, it will be uploaded to a public repository such as
Zenodo where it will be available free of charge for any user.

##  Methods or software tools

The data will be accessible through standard software such as EXCEL, MATLAB,
etc. It is expected that all data will be accessible through open source tools
such as Python, Octave, ParaView, etc.

##  Software documentation

The data should be easily ingested into the software as it will be provided in
standardized file formats. It is possible that examples for popular
applications may be included.

##  Included software

Links will be included to open source software that can be used to access the
data. Custom software written by the consortium members to process the data
may be included. This document will be updated to reflect such decision.

##  Location of data and associated metadata, documentation and code

During the project, and for each WP, data will be stored at partner’s
datacenters and replicated in the shared SACOC repository provided by SAFRAN.
Open data will be deposited in an open access repository. At the moment Zenodo
has been identified as the most likely candidate.

##  Special arrangements with the identified repository

At the moment it is not envisaged that the processed, scientific data
surpasses the standard Zenodo quota per dataset. If that was the case, special
arrangements will be sought.

##  Restrictions on use and access provision

At this stage, it is envisaged that access to the data will be open.
Restrictions on use will be defined by the relevant license. It is expected
that this license will be Creative Commons’ AttributionNonCommercial-
ShareAlike 4.0 International (CC-BY-NC-SA 4.0). This document will be updated
to reflect changes in these decisions.

_Data access committee_

Not expected

_Conditions for access_

The acceptance of the license, will be included in a machine-readable format.

_Identification_

Data will be public access without identification.

#  MAKING DATA INTEROPERABLE

It will be an objective that all data produced in the project shall be as
interoperable as possible, thus allowing data exchange and re-use between
researchers, institutions, organisations, countries, etc. In particular,
participants will adhere to the aforementioned standards for formats that will
be compatible with open source software applications thereby facilitating re-
combinations with different datasets from different origins.

This is especially important when comparing experimental datasets with
numerical results. Care will be put in defining a common and frame of
reference for all variables. These variables will be described by stablished
engineering vocabulary in order to maximize the interoperability of the data.

#  INCREASE DATA RE-USE (THROUGH CLARIFYING LICENCES)

##  Data licensing

It is envisaged that the Creative Commons’ Attribution-NonCommercial-
ShareAlike 4.0 International (CC-BY-NC-SA 4.0) license will be used for the
public datasets.

##  Time framework for data availability within the project

Data will be made available for re-use immediately upon publication of the
accompanying article. There will be no embargo period for the data.

##  Re-use after the end of the project

As the data will be deposited in Zenodo, it is expected that re-use will
continue after the end of the project. However, no permanent support, storage
facility or point of contact person for the general public is at this point
expected after the closing of the project budget.

_Time framework for data availability after the project conclusion_

Data will remain in Zenodo for as long as the repository operators allow.

#  ALLOCATION OF RESOURCES

_Costs for making data FAIR in your project_

Will be updated on next DMP versions.

_Covering of FAIR costs_

Will be updated on next DMP versions.

_Responsible for data management_

The coordinator will be responsible for data management in SACOC.

_Resources for long term preservation_

Will be decided in agreement with the Topic Manager on next DMP versions.

_National or institutional repositories_

At this stage no depositing in national or institutional depositories is
envisaged.

#  DATA SECURITY

##  Provisions in place for data security

Partners’ data is stored in the respective datacenters of each institution,
which are secured and backed up by different means. Additionally, a secure,
managed shared repository has been provided by SAFRAN for use by all partners
and to secure the data transfers.

##  Certified repositories for long term preservation and curation

Long term preservation is expected to be carried out by depositing the
scientific data in the Zenodo repository. Raw and auxiliary data will be kept
for a period to be decided and then deleted, as no budget can be allocated for
data preservation or curation after the end of the project.

#  ETHICAL ASPECTS

The participants have not identified any ethical issue regarding the data, as
no experiments or data concerns living organisms whatsoever, nor is it
expected any impact on the environment as the tests will be carried out in a
closed, appropriate facility.

#  OTHER ISSUES

At this stage, the data will not be subject to any additional data management
procedures, as this DMP will be used as a common framework that supersedes the
individual procedures of each member of the consortium.