distinct test campaigns for two sets of cavity configurations. The rig tests
will also study the performance of the high-speed turbine stage at off-design
conditions by varying the leakage flow rates and the stage operating point.

#  2.1.3 SPLEEN - Technical Work Packages

The SPLEEN project is organized in two main technical work packages that
include the activities planned for the experimental campaigns in the linear
cascade rig (Work Package 1), and in the rotating turbine facility (Work
Package 2).

#  2.1.4 Purpose of the data collection/generation and its relation to the
SPLEEN Objectives

The SPLEEN project will mark a fundamental contribution to the progress of
high-speed low-pressure turbines by delivering unique experimental databases,
essential to characterize the time-resolved 3D turbine flow, and new critical
knowledge to mature the design of 3D technological effects.

#  2.1.5 Types and formats of data

In WP1, the large scale, high speed, low Reynolds number linear cascade
facility will host 2 different blade rows (Airfoil 1 and Airfoil 2). Each
blade row will be associated to a specific cavity type (A, B and C) (ejection
or ingestion) simulating the hub or shroud leakage patterns observed in a real
engine. A reference geometry of each cavity is complemented by 3 variants.
Finally, an innovative technology concept will be defined to limit as much as
possible the impact of the leakage on the secondary flows and the associated
losses. Those different concepts have to be integrated and tested in the
existing, modular S1/C wind tunnel.

In WP2, a 1.5 stage turbine will be installed in the Light Piston Isentropic
Compression tube facility (CT3) of the von Karman Institute. The design of the
3 blade rows and end-wall geometries of the turbine will be performed,
allowing modular modifications of the stator-rotor cavity geometries.

The testing programmes in the linear cascade (WP1) and in the roating annular
rig (WP2) will be conducted by varying the hub rim seal purge mass flow,
cavity geometry and thermodynamic speed and/or stage pressure ratio for the
1.5 stage turbine rig (WP2).

Upon completion of each turbine test, a first online verification will be made
on the overall validity of the various collected data (.csv, .txt, .xls, etc.)
by live monitoring of the acquired sensor traces and verification that the
nominal turbine operating conditions have been established within a small
repeatability band. An in depth data reduction procedure will then be applied
in order to transform the electrical recorded quantities in physical
quantities of interest (pressures, temperatures, flow angles, heat transfer,
radial/axial gaps, etc.). Depending on the final purpose of the measurement,
time-averaged or time-resolved procedures will be defined to look at the mean
value of a signal or at its statistical moments. Space-time diagrams will help
the interpretation and the understanding of the unsteady or periodic
phenomena. The integration of several individual quantities (total and static
pressures, flow angles, etc.) will provide the global impact, i.e. loss, on
the cascade or turbine stage performance. The uncertainty analysis will be
finalized and applied to all measurements issued from the testing phase.
Finally, the results obtained for variations of geometrical and flow
parameters (geometry, leakage mass flow, etc.) will carefully be compared.
This will allow drawing conclusions about sensitivities that should result in
design guidelines. The first application of the latter will be to propose and
implement an innovative technology to limit as much as possible the impact on
losses of the leakage flows. Its validation will be conducted in the high-
speed cascade facility within the work plan of WP1.

#  2.1.6 Existing data re-use and their origin

Any existing data that can be useful to carry out efficiently the SPLEEN
project will be re-used. That includes numerical tools and data concerning the
safe wind tunnel operation obtained during previous experimental campaigns
performed in the linear cascade rig and in the rotating turbine facility at
the VKI.

#  2.1.7 Expected size of the data

The size of the data may range from several “Megabytes” to datasets of the
order of “Terabytes”. The size of the generated data during the entirety of
the SPLEEN project (numerical and experimental results, technical notes and
reports) is expected to be of the order of magnitude of several dozens of
“Terabytes”. Such size is estimated based on the expected output of the
project that will collect time-resolved signals sampled at high sampling rates
(between 20 to 1 MHz) and the high measurement count that is in the order of
500 measurement point per WP per test configuration.

#  2.1.8 Data utility

The data collected will mainly be useful for the scientific community involved
in the turbomachinery research area and the Low Pressure Turbine (LPT)
manufacturers. The SPLEEN project aims at demonstrating high-speed LPT designs
up to a Technology Readiness Level of 5.

The turbine experiments run in the high-speed linear cascade allows
reproducing correctly the Strouhal numbers of incoming wakes, flow
coefficients, Reynolds and Mach numbers of engine turbines. Integration into
the cascade test section of engine cavity configurations and simulation of
purge or leakage flows with measurements of the 3D flow enables the turbine
designs to be validated up to TRL 3-4. The project will also introduce a new
strategy for the mitigation of turbine losses induced by the unsteady
interactions between the secondary-air and leakage streams with the passage
flow (TRL 1-2). Such technology will be then brought to higher TRLs (3-4) by
means of laboratory tests in the linear cascade facility. The experimental
campaigns planned on the rotating turbine rig will demonstrate a TRL of 5 for
a fully-featured multi-row high-speed LPT stage.

#  FAIR data

##  Making data findable, including provisions for metadata

###  Identification mechanism and keywords

The databases generated in the project will be identified by means of a
Digital Object Identifier, and archived on the secure SPLEEN data repository
(see Section 5) together with pertinent keywords. The choice of adequate
keywords will be included to promote and ease the discoverability of data.
These keywords will include a number of common keywords in the turbomachinery
area but also generic keywords that can help to attract researchers from other
research areas to use and adapt SPLEEN results to their scientific fields.

###  Naming conventions

Documents generated during the course of the project are referenced following
the convention “SPLEEN<Type>_<Title>_<Version>.<extension>” - <Type>:

MoM: Minutes of Meeting

KOM: Kick of Meeting

TN: Technical Note (biweekly frequency)

DS: Data Set

DX.Y: Deliverable (and the associated deliverable number: “X.Y” as example)
FR: Flash Report

Meeting#0: Presentation during technical meeting between VKI and the Topic
Leader “VKI/Safran

AE” (and the associated meeting number: “#0” as example)

CP: Conference Presentation

PU: Journal Publication - <Title>:

Description of the document - <version>:

See section 3.1.3 - <extension>:

depends on the document type

###  Clear Versioning

Authors, approvers and modifiers of any kind of documents (deliverables,
technical notes,…) are recommended to use the Track changes functionality of
Word or PDF when making changes to any version of a document. Correction and
remarks can also be sent by email or directly discussed with the consortium
members.

If some modifications are made between members of the same affiliation, the
editable version changes from version 1.x to 1.x+1. Any -even minor-
modification required by a member from a different affiliation implies a
revision and hence the production of new reference by incrementing the version
(i.e. version 1.x to 2). The approval mechanism should be repeated until the
final formal approval of the document.

Modifications brought to the documents are identified in the “Document
history” section on the front page. The corresponding “Reason of change”
column details the origin of the modifications and summarizes the implemented
modifications.  
  
<table>  
<tr>  
<th>

DOCUMENT HISTORY

</th>  
<th>

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

Version

</td>  
<td>

Date

</td>  
<td>

Changed by

</td>  
<td>

Reason of change

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

1.0

</td>  
<td>

01.01.2019

</td>  
<td>

A. Aaa

</td>  
<td>

First version

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

###  Type of metadata

Where relevant, the databases will be linked to metadata such as:

  * _Descriptive metadata_ (describe a resource for purposes such as discovery and identification): it includes SPLEEN Identifier, Title, Abstract, Descriptive comments and Keywords. 

  

  * _Structural metadata_ (metadata about containers of data and indicates how compound objects are put together): Table of contents (for each delivered document) but also some Management Document describing the Types, Versions and Relationships between the SPLEEN digital materials (developed tools and experimental results) 

  

  * _Administrative metadata_ (provides information to help manage a resource): Author(s) and affiliation, Reviewer(s) and affiliation, Acceptance, Type of document, Dissemination Level, Document Status, Work Package, Estimated delivery date, Actual delivery date and Circulation List. 

  

  * _Process metadata_ (describe processes that collect, process, or produce data): Description of Calibration Procedure and Data Acquisition Method. 

  

##  Making data openly accessible

###  Data produced and/or used in SPLEEN openly available as the default

By default, all SPLEEN scientific publications will be made publicly available
with due respect of the Green/Gold access regulations applied by each
scientific publisher. Whenever possible, the scientific publication will be
made freely accessible through the project web site (
_https://www.h2020-spleen.eu/_ ).

###  Datasets to be shared under restrictions

The SPLEEN consortium as a whole (VKI in accordance with Safran AE and under
the access rights defined in the SPLEEN Implementation Agreement) will examine
the suitability of the datasets produced by the project for public
dissemination.

###  Data accessibility

The databases that will be selected to be made openly accessible will be
archived on a data repository called “Zenodo” ( _https://zenodo.org/_ ) and
listed and linked from the SPLEEN project website and referred to in any
publications which contain and report such datasets.

###  Methods or software tools needed to access the data

No specific methods or software tools are foreseen to get access to the SPLEEN
data. VKI has built up a strong experience using “Zenodo” and is familiar with
all the associated procedure. VKI will deliver all the necessary instructions
to invited members for a proper use of “Zenodo” and access to the open data
repositories.

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

Being the only beneficiary of the SPLEEN project, VKI will generate the SPLEEN
data and associated metadata, documentation and code. VKI will therefore be
responsible for the generated dataset preservation and maintenance. The
datasets (including the data, metadata and documentation) will be stored on
the “Zenodo” platform and on the VKI server (only accessible from the VKI
network).

###  Data restrictions on use and data access committee

Final decision concerning the data access and data restrictions on use will be
taken in accordance with the Topic Leader. Access to the SPLEEN datasets will
be granted under the responsibility and the supervision of the Project
Coordinator.

3.2.7 Identification of the identity of the person accessing the data

The “Zenodo collaboration” does not track, collect or retain personal
information from users of “Zenodo”.

##  Making data interoperable

The interoperability of the SPLEEN published datasets will be enforced by the
adoption of:

  * generally used extensions, adopting well established formats (whenever it is made possible), 

  

  * clear metadata, 

  

  * keywords to facilitate discovery and integration of SPLEEN data for other purposes, - and detailed documentation (such as user guide, for instance). 

  

User interfaces will be developed and documented where needed. A clear and
common vocabulary will be adopted for the definition of the datasets,
including variable names, spatial and temporal references and units (complying
with SI standards).

##  Increase data re-use

SPLEEN is expected to produce a considerable volume of novel data and
knowledge through experimental investigation that will be presented to the
outside world through a carefully designed set of dissemination actions (see
“SPLEEN-Deliverable 3.1: First plan for communication dissemination and
exploitation actions”).

The SPLEEN consortium will specify a license for all publicly available files
(see Section 3.2). A licence agreement is a legal arrangement between the
creator/depositor of the data set and the data repository, signifying what a
user is allowed to do with the data. An appropriate licence for the published
datasets will be selected by the SPLEEN consortium as a whole (VKI in
accordance with Safran AE) by using the standards proposed by Creative Commons
(2017) [2].

Open data will be made available and accessible at the earliest opportunity on
the “Zenodo” repository. This fast publication of data is expected to promote
the data re-use by other researchers and industrials active in the Low
Pressure Turbine field as soon as possible, thereby contributing to the
dissemination of SPLEEN methodology, developed tools and state-of the art
experimental results. Possible users will have to adhere with the “Zenodo”
Terms of Use and to agree with the licensing content.

The SPLEEN consortium plans to make its selected data accessible to third
parties up to a period of 5 years after the project completion.

All these aforementioned methods are expected to bring their contributions to
a long-term and efficient reuse of the SPLEEN data.

#  Allocation of resources

Being the only beneficiary of the SPLEEN project, VKI is responsible of the
SPLEEN proper data archival (for a period of up to 5 years after the project
completion), curation, maintenance, and documentation. The handling of the
“Zenodo” repository as well as all data management issues related to the
project fall in the responsibility of the Project Coordinator. Consequently,
VKI will also be responsible for applying for reimbursement for costs related
to making data accessible to others beyond the SPLEEN consortium.

Costs related to data management (dissemination, including open access and
protection of results) are eligible for reimbursement under the conditions
defined in the H2020 Grant Agreement, in particular Article 6 and Article 6.2.
D.3. The efforts associated with the archival, curation, documentation and
maintenance of the SPLEEN datasets is estimated equivalent to about 1 person-
month.

#  Data security

##  Transfer of sensitive data

The Project Coordinator launched a SPLEEN-store project site for information
and document exchange between the Beneficiary and the Topic Leader (VKI/Safran
AE) via an open source Enterprise Content Management (ECM) system called
“Alfresco”.

A so-called “Alfresco site” is an area where you can share content and
collaborate with other site members. The site creator becomes the Site Manager
by default, though additional or alternate managers can be added after this.
Each site has a visibility setting that marks the site as public, moderated,
or private. This setting controls who can see the site and how users become
site members. In the frame of the SPLEEN project, all created sites will be
private (i.e. only sites members can access the site and users must be added
to the site by a site manager).

An “Alfresco” site offers the following services:

  * Online access to project-relevant documents like reports, minutes of meeting and deliverables. 

  

  * Track version functionality for documents, 

  

  * Upload, store and share documents such as CAD or experimental data files, 

  

  * Online notification on specific issue, 

  

  * A secure back-up system for final official document of the SPLEEN project. 

  

All invited SPLEEN members will be granted to a personal access. Depending on
the need, members will be assigned to one specific role on the web based data
exchange site:

  * Manager has full rights to all site content - what they have created themselves and what other site members have created, 

  

  * Collaborator has full rights to the site content that they own; they have rights to edit but not delete content created by other site members, 

  

  * Contributor has full rights to the site content that they own; they cannot edit or delete content created by other site members, 

  

  * Consumer has view-only rights in a site; they cannot create their own content. 

  

The SPLEEN-store is registered under the following address:

_https://www.h2020-spleen.eu/share_

The site created on the Alfresco platform has been named
“SPLEEN_Data_Exchange”.

The home page of the SPLEEN-data repository looks as follows:

Figure 1: Screenshot of the SPLEEN-data repository

It contains five main folders containing all the shared SPLEEN-relevant
documents:

  * Data Exchange (from Safran AE): contains all the documents from Safran AE to be shared with VKI, 

  

  * Data Exchange (from VKI): contains all the documents from VKI to be shared with Safran AE, 

  

  * Deliverables: contains both “Management” and “Technical” deliverables (only the final/approved versions), 

  

  * Meetings: contains files presented during VKI/Safran AE meetings as well as the related MoM (only the final approved versions), 

  

  * Reports: contains flash reports issued with a bi-weekly frequency. 

  

##  Data recovery and secure storage (VKI)

SPLEEN documents are stored on each team member’s computers (daily back-up for
data generated by each SPLEEN member and weekly back-up for all the SPLEEN
documents performed by each SPLEEN member). Computers used in the frame of the
SPLEEN project are all password-protected and can only be used on VKI ground
or accessed remotely by secured password available exclusively to SPLEEN team
members.

Besides that, all the documents issued by VKI members (including draft
versions) are stored and shared on the so-called SPLEEN-network
(turbomachinery department server that can only be accessed by granted VKI
members). This constitutes a secure back-up system for all the SPLEEN
documents issued by VKI members.

The SPLEEN folder contains four sub-folders related to each Work Package:

Figure 2: Folder organisation (screenshot)

An “Alfresco site” has also been created for VKI-relevant final versions of
the SPLEEN documents. This includes:

  * deliverables, 

  

  * minutes of meetings with the Topic leader, 

  

  * academic presentations and papers, 

  

  * useful data reduction documents, 

  

  * final CAD files, 

  

  * internal reports, 

  

  * minutes of internal meetings, - purchases (quotations and invoices), - management documents. 

  

The created site is named “SPLEEN_VKI” and the documents are stored under the
following adress: _https://www.h2020-spleen.eu/share_

#  Ethical aspects

The SPLEEN consortium complies with the ethical principles as set out in
Article 34 of the Grant Agreement, which states that all activities must be
carried out in compliance with:

  1. Ethical principles (including the highest standards of research integrity – as set out, for instance in the European Code of Conduct for Research Integrity – and including, in particular, avoiding fabrication, falsification, plagiarism or other research misconduct) 

  

  2. Applicable international, EU and national law. 

  

  

These ethical principles also cover the data management activities. The data
generated in the frame of the SPLEEN project are not subject to ethical
issues.

#  Other issues

The SPLEEN project does not make use of other
national/funder/sectorial/departmental procedures for data management.