#  Executive Summary

This document, D12.3 Data Management Plan (DMP) is a deliverable of the SALUTE
project launched under the ENGINES ITD programme, which is funded by the
European Union’s H2020 through Clean Sky 2 Programme under Grant Agreement N°
821093.

ENGINES’s main objectives are to deliver substantial improvements in engine
technology. In particular, the following challenges are addressed:

  * Developing full engine and major engine system solutions that can deliver a step change reduction in emissions. 

  

  * Taking a step-by-step approach to progressing the technology’s maturity or "Technology Readiness Level" 

  

(TRL), utilising design studies and rig tests to explore and understand the
technologies under development, their system interactions and the risks
associated with their implementation. The ultimate goal of the project is to
achieve TRL4, supporting maturation of promising solutions toward TRL6.

These objectives will be achieved through the development of innovative
engine's subsystems that will allow, incrementally, improving the performance
and efficiency of the engine itself including the reduction of its noise
emission.

Indeed, modern aircraft propulsion is mostly based on high-bypass turbofan
engines. In this architecture, the gas turbine is used to operate the fan,
which provides a significant part of the thrust especially at approach. The
new used geometry and rotation speed produce new low frequency noise that need
to be treated. The main technologies of acoustic treatments currently used on
turbofan engines in service are no more as efficient to absorb UHBR fan noise
due to depth constraints. Indeed, these liners perform poorly at low
frequencies, which is a key requirement for UHBR engines. New liner
technologies are therefore needed and the present project will focus on
Active/Adaptive Acoustic Impedance treatments.

_Figure 1: active SDOF liner prototype developed in the frame of the ENOVAL
project_

The concept of Electroacoustic Resonator has been recently down-sized to
acoustic liner applications within the frame of the ENOVAL project, where an
array of 3x10 locally controlled (Electrodynamic) Electroacoustic Resonators
have been developed and assessed in a dedicated Acoustic Flow Duct facility.
Although local acoustic impedance control appears to allow efficient sound
absorption over a wide range of frequencies, the optimal organization of
individual active impedances can significantly extend the performances,
especially towards the low-frequency range. Inspired by acoustic metamaterials
concepts, where the array size rules the low frequency bound rather than the
individual unit size, distributed control strategies can be proposed. These
recent concepts still need to be developed and tested within a Distributed
Active Electroacoustic Liner configuration.

The main objective of this project is therefore to first reach TRL 3
implementations with a 2D liner implementing local and distributed active
acoustic impedance control, then reach TRL 4 in 3D liner integrations, and
finally assess their performances in realistic experimental test facility.

To tackle all the associated challenges the project is organized around 4
poles:

  * Smart components and technologies screening, integration and development 

  

  * 2D Liner Design, manufacturing and Characterization : TRL3 

  

  * 3D Liner Design, manufacturing and Characterization: TRL4 ✔ Advance modelling and simulations 

  

_Figure 2: Project overall description_

#  Data management and responsibility

##  DMP Internal Consortium Policy

The SALUTE project is engaged in the Open Research Data (ORD) pilot which aims
at improving and maximising access to and re-using of research data generated
by Horizon 2020 projects and takes into account the need to balance openness
and pro-tection of scientific information, commercialisation and Intellectual
Property Rights (IPR), privacy concerns, security as well as data management
and preservation ques-tions.

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
up-dated over the lifetime of the project whenever necessary.

##  Data management responsible

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

##  • The SALUTE Management Team (ECL-LMFA, ECL-LTDS, LAUM, FEMTO, EPFL) and
the topic manager

**(SAE)** analyse the results of the SALUTE 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 up-
load 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, etc. Of course he will discuss and validate these points with SALUTE Management Team (ECL-LMFA, ECL-LTDS, LAUM, FEMTO, EPFL) and the topic manager (SAE). 

  

  
<table>  
<tr>  
<th>

**Data management Project Responsible (DMPR)**

</th>  
<th>

**Manuel COLLET**

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

DMPR Affiliation

</td>  
<td>

Ecole Centrale de Lyon

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

DMPR mail

</td>  
<td>

Manuel.collet@ec-lyon.fr

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

DMPR telephone number

</td>  
<td>

**+33 (0)4 72 18 64 84**

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

  * **The Data Set Responsibles (DSR)** are in charge of their single Dataset and should be the partner possessing 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. 

  

##  Data nature, link with previous data and potential users

In the next section “1.4 Data summary”, the SALUTE Management Team (ECL-LMFA,
ECL-LTDS, LAUM, FEMTO, EPFL) and the topic manager (SAE) have listed the
project’s data/results that will be generated by the project and have
identified which data will be open. One also describes the link with previous
data and potential users.

The basic rule is based on the fact that only Data needed to validate the
results presented in scientific publications can be made accessible to third
parties. Research data linked to exploitable results will not be put into the
open domain if they compromise its commercialisation prospects or have
inadequate protection, which is a H2020 obligation.

##  Data summary

The next table (table1) presents the different data collections generated by
the SALUTE project. For each data collection 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 SALUTE project 

  

  * **Data producer** : partner who generates the data 

  

  * **Data user** : partners and the topic manager who can use data in the project or for internal research. 

  

  * **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. 

  

  * **Confidentiality level** : some data associated with results may have potential for commercial or industrial protection and thus will not be made accessible to a third party (“confidential” confidentiality level); other data needed for the verification of results published in scientific journals can be made accessible to third parties (“public” confidentiality level). 

  

  
<table>  
<tr>  
<th>

**Dataset**

</th>  
<th>

**Nature of the data**

</th>  
<th>

**WP**

**generation**

</th>  
<th>

**WP using**

</th>  
<th>

**Data producer**

</th>  
<th>

**Data user**

</th>  
<th>

**Format**

</th>  
<th>

**Volume**

</th>  
<th>

**Purpose/objecti ves**

</th>  
<th>

**Confidentiality level**

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

**1\. 2D Liners specification ‐ demonstrators data**

</td>  
<td>

CAD/Plan

</td>  
<td>

WP 2

</td>  
<td>

WP 3,4,7

</td>  
<td>

ECL-LMFA

</td>  
<td>

ALL

</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>

Confidential

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

**2\. UHBR Liners specification ‐ demonstrators data**

</td>  
<td>

Metrology

</td>  
<td>

WP 2

</td>  
<td>

WP 3,7,8

</td>  
<td>

ECL-LMFA

</td>  
<td>

ALL

</td>  
<td>

.txt, .bin

</td>  
<td>

1 GB

</td>  
<td>

  * Contains sensors calibration and 

  

position, test-bench qualification tests, tests log ...

  * Provides necessary information on the 

  

measurements and

2D test bench setup.

</td>  
<td>

Confidential

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

**3\. components screening data**

</td>  
<td>

Experimental measurements

</td>  
<td>

WP 3

</td>  
<td>

WP 4,7,8

</td>  
<td>

EPFL

</td>  
<td>

ALL

</td>  
<td>

.txt, .bin

</td>  
<td>

1 TB

</td>  
<td>

  * Contains all measurements in 

  

measured primary

units (generally

volt). Including

steady and unsteady pressure, sound pressure.

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

  

</td>  
<td>

Confidential

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

**4\. 2D prototypes panels design data**

</td>  
<td>

Metrology

</td>  
<td>

WP 4

</td>  
<td>

WP 5, 7

</td>  
<td>

LAUM

</td>  
<td>

FEMTO

TM

</td>  
<td>

.txt, .bin

</td>  
<td>

1 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>

Confidential

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

**5\. 2D prototypes**

**Transducers design data**

</td>  
<td>

Experimental measurements

</td>  
<td>

WP 4

</td>  
<td>

WP 5, 7

</td>  
<td>

EPFL

</td>  
<td>

FEMTO

TM

</td>  
<td>

.txt, .bin

</td>  
<td>

1 TB

</td>  
<td>

  * Contains all measurements in 

  

measured primary

units (generally

volt). Including

steady and unsteady

pressure and LDA measurements,

sound pressure.

  * Provides 

  

</td>  
<td>

Confidential

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

measurement ready to be converted in the physical units.

</td>  
<td>

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

**6\. 2D prototypes Hardware design data**

</td>  
<td>

Experimental measurements

</td>  
<td>

WP 5

</td>  
<td>

WP 6, 7

</td>  
<td>

FEMTO

</td>  
<td>

ECL-LTDS

TM

</td>  
<td>

.txt, .bin

</td>  
<td>

1 TB

</td>  
<td>

  * Contains only validated 

  

measurements in physical units.

  * Provides measurements for the analysis step. 

  

</td>  
<td>

Confidential

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

**7\. 2D Prototypes Hardware panels prototypes and software codes**

</td>  
<td>

Hardware and software codes

</td>  
<td>

WP5

</td>  
<td>

WP 6

</td>  
<td>

ECL-LTDS,

EPFL, FEMTO and LAUM

</td>  
<td>

ECL-LMFA

TM

</td>  
<td>

NA

</td>  
<td>

All 2D prototypes

</td>  
<td>

\- Supply 2D prototypes

hardware (electromechanic and

electonical

components) and software codes

</td>  
<td>

Confidential

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

**8\. 2D Prototypes Validated experimental data**

</td>  
<td>

Documentation

</td>  
<td>

WP 6

</td>  
<td>

WP 7,8

</td>  
<td>

ECL-LTDS

</td>  
<td>

ALL

</td>  
<td>

.docx+.pdf

</td>  
<td>

10 MB

</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>

Confidential

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

**9\. 2D Prototypes Published experimental data**

</td>  
<td>

Experimental measurements

</td>  
<td>

WP 6

</td>  
<td>

WP 7, 8

</td>  
<td>

ECL-LTDS

</td>  
<td>

ALL

</td>  
<td>

.docx+.pdf

</td>  
<td>

100 MB

</td>  
<td>

  * Contains experimental data 

  

used for publication purposes.

  * Provides an experimental open- 

  

access database for the research community.

</td>  
<td>

Public

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

**10\. Advanced modelling Codes**

</td>  
<td>

Numerical simulation

</td>  
<td>

WP 7

</td>  
<td>

WP 5, 8

</td>  
<td>

LAUM

</td>  
<td>

ALL

</td>  
<td>

.m .dat, ….

</td>  
<td>

TB

</td>  
<td>

  * Contains numerical results of 

  

simulations.

  * Provides numerical results for the analysis step. 

  

</td>  
<td>

Confidential

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

**11\. Modelling Documentation DATA**

</td>  
<td>

Documentation

</td>  
<td>

WP 7

</td>  
<td>

WP 5, 8

</td>  
<td>

LAUM

</td>  
<td>

ALL

</td>  
<td>

.docx+.pdf

</td>  
<td>

10 MB

</td>  
<td>

\- Contains the numerical strategy setup (excluding the

</td>  
<td>

Confidential

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

Page  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

mesh or all

geometrical aspects).

\- Provides the necessary setup to

initialise numerical simulations with used software.

</th>  
<th>

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

**12\. Published modelling DATA**

</td>  
<td>

Documentation

</td>  
<td>

WP 7

</td>  
<td>

WP 5, 8

</td>  
<td>

LAUM

</td>  
<td>

ALL

</td>  
<td>

.docx+.pdf

</td>  
<td>

10 MB

</td>  
<td>

  * Contains numerical data used for publication purposes. 

  

  * Provides a numerical open- 

  

access database for the research

community.

</td>  
<td>

Public

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

**13\. 3D prototypes details design data**

</td>  
<td>

CAD/Plan

</td>  
<td>

WP 8

</td>  
<td>

WP 7, 9

</td>  
<td>

FEMTO

</td>  
<td>

ECL LMFA, ECL-

LTDS

TM

</td>  
<td>

.docx+.pdf

</td>  
<td>

TB

</td>  
<td>

  * Contains plans and CAD of test vehicles. 

  

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

  

</td>  
<td>

Confidential

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

**14\. 3D prototypes integration data**

</td>  
<td>

Metrology

</td>  
<td>

WP 9

</td>  
<td>

WP 7, 10

</td>  
<td>

ECL-LMFA

</td>  
<td>

ECL LMFA/LTDS

TM

</td>  
<td>

.txt, .bin

</td>  
<td>

1 TB

</td>  
<td>

  * Contains only validated 

  

measurements in physical units.

  * Provides measurements for the analysis step. 

  

</td>  
<td>

Confidential

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

**15\. 3D Prototypes**

**Hardware panels prototypes and software**

**codes**

</td>  
<td>

Hardware and software codes

</td>  
<td>

WP9

</td>  
<td>

WP 10

</td>  
<td>

ECL-LTDS,

EPFL, FEMTO and LAUM

</td>  
<td>

ECL-LMFA/LTDS

TM

</td>  
<td>

NA

</td>  
<td>

All 3D prototypes

</td>  
<td>

\- Supply 3D prototypes

hardware (electromechanic and

electonical

components) and software codes

</td>  
<td>

Confidential

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

**16\. 3D Prototypes Validated experimental data**

</td>  
<td>

Experimental measurements

</td>  
<td>

WP 10

</td>  
<td>

WP 7

</td>  
<td>

ECL-LMFA

</td>  
<td>

ECL

LMFA/LTDS

TM

</td>  
<td>

.bin, .dat, .m

</td>  
<td>

1 TB

</td>  
<td>

  * Contains 

  

measurement

descriptions and the

operating conditions

from the validated experimental

database.

  * Provides necessary 

  

</td>  
<td>

Confidential

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

Page  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

information to

perform analysis of the validated

experimental database.

</th>  
<th>

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

**17\. 3D Prototypes**

**Published experimental data**

</td>  
<td>

Documentation

</td>  
<td>

WP.10

</td>  
<td>

WP 7

</td>  
<td>

ECL-LMFA

</td>  
<td>

ALL

</td>  
<td>

.docx+.pdf

</td>  
<td>

1 GB

</td>  
<td>

  * Contains experimental data 

  

used for publication purposes.

  * Provides an experimental open- 

  

access database for the research community.

</td>  
<td>

Public

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

**18\. Experimental Documentation DATA**

</td>  
<td>

Documentation

</td>  
<td>

WP 6, 10

</td>  
<td>

WP 11

</td>  
<td>

ECL-LTDS

</td>  
<td>

ALL

</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>

Confidential

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

**19\. Miniaturized & integrated liner design data **

</td>  
<td>

CAD / Plan Documentation

</td>  
<td>

WP 11

</td>  
<td>

NA

</td>  
<td>

EPFL

</td>  
<td>

ALL

</td>  
<td>

.pdf, .step

</td>  
<td>

1 GB

</td>  
<td>

  * Contains plans and CAD engine integration. 

  

  * Provides necessary information for future implementation and numerical simulation. 

  

</td>  
<td>

Confidential

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

**20\. Innovative tunable demonstrator and results**

</td>  
<td>

Hardware and software codes

Experimental measurements

</td>  
<td>

WP11

</td>  
<td>

NA

</td>  
<td>

ECL-LTDS,

EPFL, FEMTO and LAUM

</td>  
<td>

ECL-LMFA/LTDS

TM

</td>  
<td>

NA

</td>  
<td>

All Innovative tunable demonstrator

</td>  
<td>

\- Supply Innovative tunable

demonstrator

hardware (electromechanic and

electonical

components) and software codes - Provides necessary information relative to
performance and integration tests

</td>  
<td>

Confidential

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

_Table1: datasets generated by the SALUTE project_

Page

#  FAIR Data

**2.1 Making data findable**

##  Public database (data sets 8, 11 and 15)

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
such as movies or sound recordings.

##  Confidential database

Confidential databases are composed of both the methods (databases 1,2,4, 7
and 10) and the results (databases 3, 5, 6, 8 and 9).. Each owner is
responsible for its database repository and has to guarantee access of other
partners for its used during the project. Only datasets linked to 3D
implementations has restricted access.

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 (databases 7, 14) uses
the same identification as the corresponding raw data. Main information on
measurement is reported in the data experimental guide (database 16).

Each numerical run (databases 9 and 11) corresponds to a unique identifier
recorded in the corresponding data guide (databases 10).

**2.2 Making data openly accessible**

##  Public database (databases 8, 11 and 15)

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 databases that will be selected to constitute the project validation
benchmarks will be archived on the ZENODO platform, and linked from the SALUTE
project website. The consortium has already used the ZENODO repository for a
previous project, and is familiar with the associated procedure. 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 SALUTE 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.

##  Confidential database

Each Partners in charge of a confidential database has to allow access for the
use during the project and validate its procedure by the project coordinator
(ECL) and ITD topic manager (SAE).

For all concerning PHARE implementation, ECL and ITD topic manager are
authorised to exchange all necessary data and allow other partners to access
necessary materials. At long term the data generated project can be used for
internal research.

**2.3 Making data interoperable**

##  Public database (databases 8, 11 and 15)

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.

##  Confidential database

Validated databases are used for analysis (3, 6 and 9). These databases are
directly expressed in physical units

(using SI unit system). Necessary information about results are recorded in
the different data guides (10 and 15).

**2.4 Increase data re-use**

**Data licence**

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

##  Public database (databases 8, 11 and 15)

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

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

##  Confidential database

The experimental setup and the huge quantity of experimental and numerical
data cannot be completely exploited in the SALUTE 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 SALUTE project:

  * Subsequent projects for consortium members and SAE. 

  

  * Additional academic partners to work on not exploited data. 

  

  * Supplementary experimental measurements: 

    * Using the already installed adaptive liners on new operating conditions ✔ Measurements of supplementary field with SALUTE project results. ✔ Investigates new concept of vibroacoustic control. 

  

  

  * Investigation of numerical prediction performances: 

    * Calibrate low fidelity numerical method using higher fidelity methods. ✔ High fidelity simulatin of other speed. 

  

  

For all these next projects the agreement with the topic manager (SAE) is
necessary.

#  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 and MyCore 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 SALUTE 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:**

Each partner is responsible for the data it produces and must contribute
actively to the data management as set in the DMP.

_**Refer to part 1.2 “DATA MANAGEMENT Responsible”.** _

#  Data security

##  Public database (databases 8, 11 and 15)

Long-term preservation: Using ZENODO and MyCore data repositories.

Data Transfer: Using ZENODO and MyCore web platforms

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

##  Confidential 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 Partners to SAE. 

  

  

  * _Intellectual property_ : Data are confidential and need to strictly respect the intellectual property rights as set out in the Consortium and Implementation agreement. 

  

  5. **Ethical aspects**

  

  

The data generated by the SALUTE project is not subject to ethical issues.

  6. **Other**

  

  

No other procedure for data management.