#  1\. Outline

This deliverable aims at providing details for “STRATOFLY Data Management
Plan”. It involves data management purposes and architecture, initial strategy
for data collection, storage, maintenance and publication. It also takes into
account includes information on how research data will be dealt with during
the project; what data will be collected, processed and/or generated, which
strategy and methodology will be used for data collecting and which data can
be open-access or restricted to the project partners.

#  2\. Data Summary

##  2.1 Purpose of the Data collection

The data collected by STRATOFLY is technical data of new high-speed civil
transportation concept required to parametrize multi-disciplinary simulation
model as well as socio-economical data. The main purposes of the data
collection are explained with three objectives given below:

**Main Objective I** : The STRATOFLY project will develop a new high-speed
civil transportation platform by taking advantage of that the scientific
groups from different disciplinaries work together. The multi-disciplinary
subjects in this project contains air traffic management, design of propulsion
system, flight mechanics/dynamics, thermal stress and load management,
investigation and modeling of structural/control dynamics and stresses,
studies on clime and noise impacts. The data collection, sharing, storage and
management are needed by these subjects to use and get benefit from each
other’s outputs.

**Main Objective II:** The development of high-speed civil transportation
platform requires the propulsion plant which should provide stable and
sufficient thrust along the flight trajectory. The design of the plant is
conducted both numerically and experimentally by different consortium
partners. The design performance mostly depends on the interaction between
these partners and how much efficient they can benefit each other’s data.
Thus, data management is very essential for their communication and the usage.

**Main Objective III:** STRATOFLY aims to change social, public and
environmental aspects about for high-speed civil transportation platform in
positive direction and produce significant technical data to turn this idea be
real by gathering innovative resources, feedbacks from public and
stakeholders’ opinions.

##  2.2 Types, Formats, and Utility of the collected Data

The type of data, formats of data, accessibility and list of partners who are
responsible to provide, are given in the Table.1:

##  Table 1 Data type, format, standards, accessibility, storage type and
partner  
  
<table>  
<tr>  
<th>

Type of Data

</th>  
<th>

WP

</th>  
<th>

Standards

</th>  
<th>

Accessibility

</th>  
<th>

Curation/ preservation

</th>  
<th>

Partner

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

Progress, interim and final reports

</td>  
<td>

\-

</td>  
<td>

STRATOFLY report templates

</td>  
<td>

Restricted to the project partners and

</td>  
<td>

Website’s intranet

(Alfresco)

Partners’

</td>  
<td>

All

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

</th>  
<th>

</th>  
<th>

</th>  
<th>

the EC

</th>  
<th>

premises

</th>  
<th>

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

Raw model output data

</td>  
<td>

\-

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners and the EC

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

All

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

Meeting records

</td>  
<td>

1

</td>  
<td>

STRATOFLY MoM

template

</td>  
<td>

Restricted to the project partners and the EC

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

All

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

1D reduced propulsion system

model

</td>  
<td>

3.2

2.4

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Partners’ premises

</td>  
<td>

VKI, CIRA

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

CFD database for the aero-propulsive system

</td>  
<td>

3.3

3.4

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

VKI, CIRA

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

CFD database for the PAC parameters

</td>  
<td>

3.4

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

VKI, FOI

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

CFD database for the combustor optimization

</td>  
<td>

3.3

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

CIRA, DLR-GO

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

Thermal management database

</td>  
<td>

2.2

3.5

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

CIRA, POLITO

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

Experimental database of noise investigation

</td>  
<td>

4.2

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

VKI, NLR

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

Database for flight trajectory

</td>  
<td>

3.5

4.4

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Website’s intranet

(Alfresco) Partners’ premises

</td>  
<td>

POLITO, CIRA, VKI, NLR, DLR, TUHH, CNRS

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

Structural analysis (FEA) database

</td>  
<td>

2.3

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Partners’ premises

</td>  
<td>

FICG

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

Atmospheric composition model database

</td>  
<td>

4.3

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Partners’ premises

</td>  
<td>

DLR-OP, CNRS, TUHH

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

CAD data for aircraft airframe

</td>  
<td>

2

</td>  
<td>

CATIA

</td>  
<td>

Restricted to the project

</td>  
<td>

Partners’ premises

</td>  
<td>

POLITO

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

partners

</td>  
<td>

</td>  
<td>

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

Experimental database for PAC

</td>  
<td>

4.1

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Partners’ premises

</td>  
<td>

ONERA

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

Experimental database for NOX measurement

</td>  
<td>

4.1

</td>  
<td>

Model dependent

</td>  
<td>

Restricted to the project partners

</td>  
<td>

Partners’ premises

</td>  
<td>

DLR-GO

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

###  2.3 STRATOFLY data management methodology

The guide of data management in STRATOFLY project is given in Figure 1\. The
management consists of three aspects:

  1. Architecture: It explains that the structure and function of data sharing and storing system. 

  

  2. Process: The process as shown in Figure 2, is for checking whether data contributed to STRATOFLY project can be usable and accessible or not. 

  

  3. Reporting: The monitoring the data archives can be used to inform the decision-making mechanism for future improvement in the Data Management planning. 

  

  

As it is demonstrated in Figure 1, online data archiving and sharing are
provided via scientific outputs in journals and conference proceedings. The
open-public data can be accessible by using project website and the data
restricted to project partners can be available in project collaborative site
Alfresco. The partners can also store the data in their local repository such
as memories of clusters.

The data processing scheme contains the processing steps from raw state to the
end. Data considered to be used in project steps, comes as raw state and is
stored in local repositories. As a result of data analysis by the partners, it
is determined whether this data can be evaluated as important or not. If it is
seen as important, it can be shared in collaborative website Alfresco,
monitored in project database and also discussed during the project meetings.
When the data is thought as qualified to be published, it is presented and
stored in online journal repository and Alfresco.

#  3\. FAIR Data

STRATOFLY uses the Alfresco depository to store all data which are accessible
to all project partners. The Alfresco platform is a modern, enterprise-class,
cloud-native platform that provides the quick way for project partners to
interact with information and to share documents with each other in a storage
pool.

STRATOFLY also publicly share the data generated by the consortium. This
action aims at facilitating access and exploitation of scientific data by all
levels of the society. In parallel with the scientific publications (necessary
for the impact factor of the STRATOFLY publications), the consortium endeavors
to submit an amount of its results to the European Open Science Cloud (EOSC)
through its network of repositories. A majority of partners of this consortium
are already connected to the EOSC through the OpenAIRE network and will use
their institutional repository to that end. In parallel, the project will use
the CERN-based ZENODO open-access repository to upload i) all the public
deliverables generated by the consortium ii) Open publications, and iii)
selected subsets of the experimental and numerical databases.

##  3.1 Making data findable, including provisions for metadata

All outcomes (summary of meetings and presentations during the progress of
meetings) are uploaded in Alfresco server within 15 days following the project
meetings. The data is assigned with descriptive names keywords and metadata in
order to access it easily.

**Naming conventions:**

Data is named by using given naming conventions accordingly to its type:
Deliverables: D.x.y.z

  24. number of work package 

  

  25. number of sub work package 

  

  26. number of deliverables 

  

  

**Metadata:**

The metadata which is related with published dataset must be by default ✔
Digital Object Identifiers and version numbers ✔ Bibliographic information ✔
Keywords ✔ Abstract/information ✔ Associated project and communities ✔
Associated publications and reports ✔ Grant information

✔ Access and licensing information ✔ Language

##  3.2 Making data openly accessible

All scientific outputs are by default made publicly accessible conveniently
with the Green / Gold access regulations applied by each scientific publisher.
As much as possible the technical papers will be freely accessible through the
project website. Additionally, data can be available to access via journal and
conference repository. The project consortium also endeavors to provide a
significant amount of the results to the European Open Science Cloud (EOSC)
via the network of repositories.

##  3.3 Making data interoperable

Scientific notations as S.I. units and vocabulary as in ISO test standards are
used in data files. The Alfresco and Zenodo here the data and metadata are
shared and stored uses popular formats such as BibTex, CSL, DataCite, ASCII
and export to Mendeley.

##  3.4 Increase data re-use

The data published in scientific journals are made available as Open Access is
granted for the paper or preprint. Open data will be reusable as defined by
the license conditions. However, data restricted to the project partners and
European commission is defined as confidential and will not be reusable as
default to avoid commercial exploitation.

#  4\. Allocation of Resources

The resources allocated for the management involves project management man
hours of the deputy coordinator. von Karman institute will be responsible for
the management of data generated by STRATOFLY consortium in coordination with
Politecnico di Torino. Dr. Riamando Giamanco (VKI) will be involved on the
information technologies resources allocation for the external services
(STRATOFLY website domain provider). The file exchange server (Alfresco) for
the consortium will be provided, managed and maintained by the deputy
coordinator. The data storage of Alfresco server will be provided by IT
services of the von Karman

Institute.

von Karman Institute will provide updating the project related databases i.e.
Zenodo, monitoring database in STRATOFLY Alfresco server and the continuous
reporting feature in the EC’s participant portal in coordination with
Politecnico di Torino.

**Gold Data stored on Zenodo depository:** There will be no long-term
archiving costs for the project because it is already financed depository used
and externally freely usable. The storage time of data curation is only
limited by the lifetime of the Zenodo depository

**Self-archiving or so-called 'green' Open Access** : It will be also applied
through the developed Zenodo repository. As also required, open access to the
publication will be ensured in a maximal delay of 6 months. The difference
between gold and green open access (including related fees) can be found in
the table below.  
  
<table>  
<tr>  
<th>

</th>  
<th>

Gold open access

</th>  
<th>

Green open access

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

Definition

</td>  
<td>

Open access publishing (also called 'Gold' open access) means that an article
is immediately provided in open access mode by the scientific publisher. The
associated costs are shifted away from readers, and instead to (for example)
the university or research institute to which the researcher is affiliated, or
to the funding agency supporting the research.

</td>  
<td>

Self-archiving (also called 'Green' open access) means that the

published article or the final peerreviewed manuscript is archived by the
researcher – or a representative - in an online repository before, after or
alongside its publication. Access to the article is often – but not
necessarily - delayed (‘embargo period’) as some scientific publishers may
wish to recoup their investment by selling subscriptions and charging payper-
download: view fees during an exclusivity period.

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

Options

</td>  
<td>

  * Publish in an open access journal 

  

  * Or in a journal which supports open access 

  

</td>  
<td>

  * Link to the article 

  

  * Select a journal that features an open archive 

  

  * Self-archive a version of the 

  

article

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

Access

</td>  
<td>

  * Public access is to the final published article 

  

  * Free access to a version of the article 

  

</td>  
<td>

  * Access is immediate 

  

  * Time delay may apply (embargo period) 

  

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

Fees

</td>  
<td>

  * Open access fee is paid by the author 

  

  * Fees range between $500 and $5,000 USD depending on the journal 

  

</td>  
<td>

✔ No fee is payable by the author as publishing costs are covered by library
subscriptions

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

Use

</td>  
<td>

✔ Authors can choose between a commercial & noncommercial

user license

</td>  
<td>

✔ Accepted manuscripts should attach a Creative Common

License ✔ Authors retain the right to reuse their articles for a wide range of
purposes

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

#  5\. Data Security

The data security is as specified by the Zenodo depository

  1. **Versions:** Data files are versioned while meeting records are not versioned. The uploaded data is archived as Submission Information Package. 

  

  

Derivatives of data files are generated, but original content is never
modified. Records can be retracted from public view; however, the data files
and record are preserved.

  2. **Replicas:** All data files are stored in CERN Data Centres, primarily Geneva, with replicas in Budapest. Data files are kept in multiple replicas in a distributed file system, which is backed up to tape on a nightly basis. 

  

  3. **Retention period:** Items will be retained for the lifetime of the repository. This is currently the lifetime of the host laboratory CERN, which currently has an experimental program defined for the next 20 years at least. 

  

  4. **Functional preservation** : Zenodo makes no promises of usability and understandability of deposited objects over time. 

  

  5. **File preservation:** Data files and metadata are backed up nightly and replicated into multiple copies in the online system. 

  

  6. **Fixity and authenticity:** All data files are stored along with a MD5 checksum of the file content. Files are regularly checked against their checksums to assure that file content remains constant. 

  

  7. **Succession plans:** In case of closure of the repository, best efforts will be made to integrate all content into suitable alternative institutional and/or subject based repositories. 

  

  

#  6\. Ethical Aspects

No sensitive personal data will be collected (see Grant Agreement, Annex 1
(part B)).

#  7\. Other Procedures

No other national, funder, sectorial, or departmental procedures for data
management are planned.

##  8\. Conclusions

This document provides the nature of the data management, in the way it is
collected, preserved and shared, and explains principles of data management
procedures for STRATOFLY project in detail. The classification of the data
related to STRATOFLY project is also outlined. The preservation and protection
of the proprietary data possessed by STRATOFLY consortium is detailed.
Moreover, determination and sharing of the open access data by the STRATOFLY
consortium will be made through various platforms. The gold open access data
will be disseminated by high impact factor journals while an extract of green
data will be generated from the experimental and numerical data obtained
during the execution of the project by the coordinator and the partner who is
the source of the information. One of the relevant platforms for open access
data sharing designated as European commissions is the Zenodo platform. The
basic principles of Zenodo platform and FAIR data policy are also provided in
this deliverable. The resources allocation of STRATOFLY data management
through the execution of the project and beyond is also summarized.