#  1 EXECUTIVE SUMMARY

###  1.1 Introduction

The overall objective of the Horizon 2020 project AGILE is to obtain a
significant reduction in aircraft development costs by enabling a more
competitive supply chain able to reduce the time to market of innovative
aircraft products.

The overall project objective is translated in 4 technical objectives :

  1. The development of advanced multidisciplinary optimization techniques and their integration. 

  

  2. The development of processes and techniques for efficient multisite collaboration in overall design teams. 

  

  3. The development of knowledge enabled information technologies to support interdisciplinary design campaigns. 

  

  4. To develop and publish an Open MDO Test suite that can serve as a reference database for future aircraft configuration research. 

  

  

A new element in Horizon 2020 is the preparation and use of a Data Management
Plan. A Data Management Plan details what data the project will generate,
whether and how it will be exploited or made accessible for verification and
re-use, and how it will be curated and preserved. This document presents the
Draft Data Management Plan for the AGILE project. It is based on the results
of a questionnaire send out to all partners. An updated version of this
document will be prepared near the end of the AGILE project.

#  2 DATA MANAGEMENT PLAN

##  2.1 Introduction

The Data Management Plan (DMP) provides a short, general outline of the
consortium’s policy for data management, including the types of data which
will be generated/collected by the project, the standards which will be used,
how this data will be exploited and/or shared/made accessible for verification
and use and how this data will be curated and preserved. The described policy
will reflect the current state of consortium agreement regarding data
management and will be consistent with those referring to exploitation and
protection of results. A questionnaire was mailed out to all AGILE partners in
April 2016. 12 partners returned this questionnaire (partly) filled in, and
with 2 partners emails were exchanged that led to the conclusion that there
was no need for them to fill in this questionnaire at this stage of the
project.

###  2.2 Data Collection and Creation

The AGILE project will generate a wealth of data when using the different MDO
environments employed in the project. The first large test case data is the so
called Open MDO Test Suite obtained after optimization of the reference
aircraft configuration, other test case data are the so called Use Case data
bases obtained after performing optimization of so called Novel Configuration
Aircraft.

For the _Creation of data_ a large number of tools are used, each tool having
its specific input and output formats. The filesize varies heavily, ranging
from several kBytes for text based input files to several GBytes.

Most of the _tools being used_ in the AGILE project are able to read and/or
write CPACS (Common Parametric Aircraft Configuration Schema [1]) XML files.
Most of the tools are able to reproduce the data if needed.

_Tools/programming langagues the most often mentioned are:_

  * Matlab 

  

  * Python 

  

  * Tixi/Tigl viewer 

  

  * XML editor 

  

  * GNU Emacs 

  

  * Java 

  

  * Common Lisp 

  

  * Tecplot for visualization 

  

Possible _pre-existing data_ needed to execute the tools concern the CAD
geometry (CATIA, IGES, STEP, ..) and several partners listed tool specific
input data (for example GasTurb engine deck, aircraft requirements, critical
manoeuver load cases, ..).

High fidelity Aerodynamic solvers use all their own data formats. CGNS [2] was
not mentioned, one partner uses HDF5 [3].

###  2.3 Data documentation and description

Most partners did not fill in this section of the questionnaire. Partners that
did provide answers mentioned the use of :

  * *.docx 

  

  * *.xml 

  

  * *.xlsx 

  

as file formats for data documentation.

Several partners mentioned the use of internal company standards, one partner
mentioned the use of Sharepoint for the documentation of Metadata.

The CPACS XML format [1] will be used for saving aircraft design data.

###  2.4 Data storage and back-up

_How will the data be stored and backed-up ?_

All partners that answered this question have in place a system for data
storage and back-up.

_Storage media ?_

Most of the partners use external USB drives for data storage and back-up.
Some partners mentioned the use of the institutes back-up server or
(encrypted) network/cloud storage.

_Frequency of back-ups ?_

Back-up’s are made at least daily, at some partners hourly.

_Data backed-up at different locations ?_

Most partners save back-ups at two different locations.

###  2.5 Data access and security

_Copyright and handling of IPR issues :_

The general principle is that fully owned data remains property of the owner,
joined owned data is owned by the partners who generated the data. Non
Disclosure Agreements (NDAs) might be required.

_Who owns the data ?_

The partner(s) who generated the data.

_Limitations on access to your data ?_

Not many answers were received, one partner mention that no access will be
given to customer specific and military data. One partner mentioned that their
network is not accessible from outside. Another partner mentioned that data
can be shared during the AGILE project, and that the code will be released as
opensource after the AGILE project has finished.

_Access criteria ?_

Two partners mentioned open access, most partners mentioned restricted or
restricted to AGILE partners. One partner mentioned embargo period until the
end of the AGILE project.

_Who controls the access ?_

The AGILE partner owning the data.

###  2.6 Data sharing and re-use

_How will the data be shared?_

  * on request as needed (“only need to know”) 

  

  * as CPACS file 

  

  * through the AGILE cloud server 

  

_Requirements for sharing the data?_

  * Be AGILE partner 

  

  * Security 

  

_Who might be interested in the data?_

  * AGILE partners 

  

  * Customers of software providers 

  

  * Authorities 

  

  * Aircraft designers 

  

  * On-board system designers 

  

  * MDO Experts who wish to optimize the definition and execution of their MDO process 

  

  * Tool experts who with to see how their tool performs in the MDO process 

  

_Data linked to a scientific publication?_

  * One partner mentioned 3 publications linked to data 

  

  * Needs to be updated at the end of the project 

  

_Tools needed to visualize the data_

  * Tecplot, Paraview, gnuplot, xml editor, Matlab, Noesis Optimus, webbrowser, FEM post processor, Hyperview, Descartes, GNU emacs, Gendl, Genworks GDL 

  

_Additional information_

  * Specific design campaign results will be disseminated using scientific publications and the meta data is shared as a data set for the public 

  

###  2.7 Data preservation

_Criteria used to decide on the data to be archived for preservation and long
term access:_

  * data will be preserved if it is used in an official publication 

  

  * data files will be preserved, but only the final result 

  

  * enough data should be stored so that it is possible to interpret the results generated by the MDO process and to be able to reproduce the MDO process 

  

  * Optimus project files and results from Optimus execution will be stored and preserved. Filex created by applications driven by Optimus will be optionally stored and preserved 

  

  * related to the use of the Sharepoint file server 

  

  * data required to pass project milestones (SRR, PDR, CDR, …) 

  

  * certification relevant data 

  

  * all code and data will be archived indefinitely 

  

_How many years should/will the data be preserved_

  * 3 to 5 years 

  

  * indefinitely 

  

  * depends on the data usage, aircraft data are in general kept until the last aircraft is grounded, so typically between 60 and 80 years. 

  

_File formats used for data preservation?_

  * CPACS files 

  

  * txt files 

  

  * XML files 

  

  * png files 

  

  * binary solution files (FFA Format, MemCom data base, HDF5, ..) 

  

  * zip archives 

  

  * Mat files 

  

  * Native file formats 

  

  * ASCII and Unicode (UTF-8) 

  

_Costs associated with data preservation_

  * none to small 

  

  * 1000 $/year for hosting and server administration 

  

_Willingness/interest to use a central data repository for AGILE?_

  * 5 partners were interested 

  

  * 4 partners needed more information 

  

  * 1 partner said may be 

  

  * 1 partner mentioned if required 

  

  * 1 partner said no 

  

**3 REFERENCES**

  1. _https://software.dlr.de/p/**cpacs** /home/ _

  

  2. http://cgns.sourceforge.net/ 

  

  3. https://www.hdfgroup.org 

  

  

**4 APPENDIX: DATA MANAGEMENT PLAN QUESTIONNAIRE**

**DATA MANAGEMENT PLAN QUESTIONNAIRE**

Author(s): J.B. Vos

WorkPackage Nº: WP1

Due date of deliverable: 30.11.2015

Actual submission date: DD.MM.YYYY

Document ID: AGILE_DataManagementQuestionnaire.14.04.2016.docx

Grant Agreement number: 636202

Project acronym: AGILE

Project title: Aircraft 3  rd  Generation MDO for Innovative Collaboration of
Heterogeneous Teams of Experts Start date of the project: 01/06/2015

Duration: 36 months

Project coordinator name, title and organisation:

Björn Nagel, DLR – Air Transportation Systems | Integrated Aircraft Design 

Tel: +49 40 42878-2304 Fax +49 40 42878-2979

E-mail: _bjoern.nagel@dlr.de_

Pier Davide Ciampa, DLR – Air Transportation Systems | Integrated Aircraft Design 

Tel: +49 40 42878-2727

Fax +49 40 42878-2979

E-mail: _pier.ciampa@dlr.de_

Project website address: _www.agile-project.eu_

This project has received funding from the European Union’s Horizon 2020 Page
1 research and innovation framework programme under grant agreement No 636202

ID: AGILE_DMP_Questionnaire.17.02.2016.docx

Period: M06

**DOCUMENT INFORMATION**  
  
<table>  
<tr>  
<th>

**Document Name**

</th>  
<th>

</th>  
<th>

</th>  
<th>

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

Document ID

</td>  
<td>

D1.3.2-Questionnaire

</td>  
<td>

</td>  
<td>

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

Version

</td>  
<td>

1.1

</td>  
<td>

</td>  
<td>

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

Version Date

</td>  
<td>

14.04.2016

</td>  
<td>

</td>  
<td>

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

Author

</td>  
<td>

J.B. Vos

</td>  
<td>

</td>  
<td>

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

Security

</td>  
<td>

R

</td>  
<td>

</td>  
<td>

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

**APPROVALS**  
  
<table>  
<tr>  
<th>

</th>  
<th>

**Name**

</th>  
<th>

**Company**

</th>  
<th>

**Date**

</th>  
<th>

**Visa**

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

Coordinator

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP Leader

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**DOCUMENTS HISTORY**  
  
<table>  
<tr>  
<th>

**Version**

</th>  
<th>

**Date**

</th>  
<th>

**Modification**

</th>  
<th>

**Authors**

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

1.0

</td>  
<td>

17.02.2016

</td>  
<td>

Initial Version

</td>  
<td>

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

1.1

</td>  
<td>

14.04.2016

</td>  
<td>

Include comments from partners testing the questionnnaire

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**LIST OF AUTHORS**  
  
<table>  
<tr>  
<th>

**Full Name**

</th>  
<th>

**Organisation**

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

J.B. Vos

</td>  
<td>

CFS Engineering

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

</td>  
<td>

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

</td>  
<td>

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

</td>  
<td>

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

**DISTRIBUTION LIST**  
  
<table>  
<tr>  
<th>

**Full Name**

</th>  
<th>

**Organisation**

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

</td>  
<td>

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

</td>  
<td>

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

</td>  
<td>

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

</td>  
<td>

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

Page 2

ID: AGILE_DMP_Questionnaire.17.02.2016.docx

Period: M06