<table>  
<tr>  
<th>

**3.**

</th>  
<th>

**Data Formats**

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

Initially, data formats used for data representation within the ZAero project
(or at individual project partners) may be proprietary and/or of complex
structure. However, when preparing data for open access, the goal is to use
standard data formats that are well known and easy to handle. Any data that is
present in a highly proprietary complicated format must be converted to easily
readable data formats before publication. For example, HDF5, XML, or standard
image formats (.png, .jpg) are favoured over complex proprietary binary
formats. Every data set that is published will be accompanied by a simple
“readme.txt” text file that provides general information about the data as
well as a detailed description of the data format.  
  
<table>  
<tr>  
<th>

**4.**

</th>  
<th>

**Software and Interoperability**

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

In some cases it makes sense to provide data with software that is able to
load the data and/or process the data in order to make it easier to work with
it. From the current status within the project it is not yet completely clear,
how and if such software can be provided with the data. For each data set
there will be a decision if and how dedicated software can be provided
together with the data set. Preferably, we promote Python as programming
language to work with scientific open access data from the ZAero project.
Since Python has become very popular as the language of choice in research,
this would make it easy for a large number of researchers to get access to the
data and use it.  
  
<table>  
<tr>  
<th>

**5.**

</th>  
<th>

**Licences for Data**

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

For open access publication of pure data, the Creative Commons Attribution 4.0
International Public License (IPL) [5] will be considered in the first place.
This license essentially provides the right to freely copy and redistribute
the material in any medium or format. Re-mixing, transforming, and building
upon the material are explicitly permitted. This is granted for any purpose.
The licensor cannot revoke these freedoms as long as the license terms are
followed.

The use of the IPL is the preferable choice for data publication in ZAero. In
specific cases a different license might be considered.  
  
<table>  
<tr>  
<th>

**6.**

</th>  
<th>

**ZAero Data Sets**

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

The following list includes the data sets which are expected to be acquired
and/or used within the ZAero project. Each data set is characterized by:

  * Code: a code consisting of “ZAero-“ and a 3-letter code (e.g. “ZAero-DTD”). - Data set full name: a full name for the data set. 

  

  * Responsible beneficiary: the main responsible project partner. 

  

  * Description: a general description of the data set. 

  

  * Data Format: the expected format of the data. 

  

  * Data set size: the expected size of a single data set instance. 

  

  * Data sharing: information about whether the data set is confidential (not published) or published under open access criteria. 

  

The subsequent list of data sets defines mainly the type of data. During the
run of the project it can be expected that multiple instances for each data
set will be acquired. For example, dry material triangulation data might be
generated at a first trial and later repeated with modified parameters. In
this case, the specific instances of data sets should additionally be tagged
by

  * a date when the data set was acquired and 

  

  * a textual description of the conditions/environment under which the data was captured or initially generated. 

  

Multiple instances of a single type of data set will be tagged with a running
number. For example, data sets for code “ZAero-FCD” (see below) will be
referred to as ZAero-FCD-1, ZAero-FCD-2, etc. Additionally, data sets that are
uploaded to the Zenodo portal, will receive a unique DOI.

For the data sets listed below the entry “Data sharing” describes whether data
sharing is considered. “Publication” means that the plan is to publish the
data set (or at least specific instances). “Confidential” means that the
respective data set is not considered for publication.  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**ZAero-FCD**

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

**Data set full name**

</td>  
<td>

Fibre orientation sensor calibration data

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

**Responsible beneficiary**

</td>  
<td>

Ideko

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

**Description**

</td>  
<td>

Data used to evaluate calibration accuracy of

Profactor’s fibre orientation sensor: calibration images, position information
etc.

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

**Data format**

</td>  
<td>

HDF5 file

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

**Data set size**

</td>  
<td>

~40 MB

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

**Data sharing**

</td>  
<td>

Publication

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

**Code**

</th>  
<th>

**ZAero-LCD**

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

**Data set full name**

</td>  
<td>

Laser triangulation sensor calibration data

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

**Responsible beneficiary**

</td>  
<td>

Ideko

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

**Description**

</td>  
<td>

Data used to evaluate calibration accuracy of Profactor’s laser triangulation
sensor: calibration images, position information, etc.

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

**Data format**

</td>  
<td>

HDF5 file

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

**Data set size**

</td>  
<td>

~40 MB

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

**Data sharing**

</td>  
<td>

Publication

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

**Code**

</th>  
<th>

**ZAero-DTD**

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

**Data set full name**

</td>  
<td>

Automated dry material placement triangulation data

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

**Responsible beneficiary**

</td>  
<td>

PROFACTOR

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

**Description**

</td>  
<td>

Profile depth data that is generated by the in-line depth sensor from
Profactor in the dry material placement shop floor at Danobat.

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

**Data format**

</td>  
<td>

16-bit PNG uncompressed image files in combination with simple text-file
providing meta-information about the raw depth data (e.g. calibration
information, position information, etc.)

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

**Data set size**

</td>  
<td>

~2 GB

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

**Data sharing**

</td>  
<td>

Publication

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

**Code**

</th>  
<th>

**ZAero-FTD**

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

**Data set full name**

</td>  
<td>

Automated fibre placement triangulation data

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

**Responsible beneficiary**

</td>  
<td>

PROFACTOR

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

**Description**

</td>  
<td>

Profile depth data that is generated by the in-line depth

sensor from Profactor in the AFP test environment at MTorres and FIDAMC

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

**Data format**

</td>  
<td>

16-bit PNG uncompressed image files in combination with simple text-file
providing meta-information about the raw depth data (e.g. calibration
information, position information, etc.)

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

**Data set size**

</td>  
<td>

~1 GB

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

**Data sharing**

</td>  
<td>

Publication

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

**Data set short name**

</th>  
<th>

**ZAero-FOS**

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

**Data set full name**

</td>  
<td>

Dry material fibre orientation sensor data

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

**Responsible beneficiary**

</td>  
<td>

PROFACTOR

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

**Description**

</td>  
<td>

Dense fibre orientation data. For a dense grid of points over the surface of a
scanned ADMP part fibre orientations are determined. Each measurement position
is stored as a tuple of 6 floating point values: x, y, z (position as 3D
point), vx, vy, vz (fibre orientation as 3D-vector).

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

**Data format**

</td>  
<td>

HDF5 file containing a single Nx6 matrix of floating point values.

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

**Data set size**

</td>  
<td>

~10 GB (Probably, data sets will be down-sampled or only parts of it will be
made publicly available to make data easily usable)

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

**Data sharing**

</td>  
<td>

Publication

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

**Data set short name**

</th>  
<th>

**ZAero-CTD**

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

**Data set full name**

</td>  
<td>

Curing monitoring: temperature data

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

**Responsible beneficiary**

</td>  
<td>

AGI

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

**Description**

</td>  
<td>

Temperature profile (temperature over time at different locations) during CFRP
curing

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

**Data format**

</td>  
<td>

Xyz coordinate for each location, temperature value in °C, time stamp

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

**Data set size**

</td>  
<td>

< 1 MB

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

**Data sharing**

</td>  
<td>

Confidential

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

**Data set short name**

</th>  
<th>

**ZAero-CFD**

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

**Data set full name**

</td>  
<td>

Curing monitoring: flow front data

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

**Responsible beneficiary**

</td>  
<td>

AGI

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

**Description**

</td>  
<td>

Flow front propagation at different locations during CFRP resin injection

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

**Data format**

</td>  
<td>

Xyz coordinate for data points, yes/no value on resin arrival, time stamp

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

**Data set size**

</td>  
<td>

< 1 MB

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

**Data sharing**

</td>  
<td>

Confidential

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

**Data set short name**

</th>  
<th>

**ZAero-CDD**

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

**Data set full name**

</td>  
<td>

Curing monitoring: degree of curing data

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

**Responsible beneficiary**

</td>  
<td>

AGI

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

**Description**

</td>  
<td>

Information on the degree of curing during resin curing in a CFRP fabrication
process

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

**Data format**

</td>  
<td>

Xyz coordinate for each location, value for degree of curing, time stamp

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

**Data set size**

</td>  
<td>

< 1 MB

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

**Data sharing**

</td>  
<td>

Confidential

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

**Data set short name**

</th>  
<th>

**ZAero-SPE**

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

**Data set full name**

</td>  
<td>

Schema Specification

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

**Responsible beneficiary**

</td>  
<td>

DS

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

**Description**

</td>  
<td>

Schema used in defining the content of the manufacturing database.

(Also used for Effects of Defects Database)

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

**Data format**

</td>  
<td>

MSWord document

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

**Data set size**

</td>  
<td>

~70 KB

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

**Data sharing**

</td>  
<td>

Publication

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

**Data set short name**

</th>  
<th>

**ZAero-MDB**

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

**Data set full name**

</td>  
<td>

Manufacturing Data Base

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

**Responsible beneficiary**

</td>  
<td>

DAS

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

**Description**

</td>  
<td>

Manufacturing database for test model; Will contain simulated and/or measured
data. Whole model data to show the full sweep of zero defect simulation and
decision methods. One version of this data set is expected for each
demonstration within the project.

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

**Data format**

</td>  
<td>

HDF5 file

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

**Data set size**

</td>  
<td>

~5 GB

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

**Data sharing**

</td>  
<td>

A few representative versions of data sets are planned to be published.
Probably, these data sets will be reduced before publication to meet
confidentialy concerns.

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

**Data set short name**

</th>  
<th>

**ZAero-EDB**

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

**Data set full name**

</td>  
<td>

Effects of Defects Database (EDB)

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

**Responsible beneficiary**

</td>  
<td>

DS

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

**Description**

</td>  
<td>

Database which tabulates the results of multiple FE analysis for use as a
lookup during manufacture to determine the knock-down factors to apply for
measured defects.

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

**Data format**

</td>  
<td>

HDF5 file

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

**Data set size**

</td>  
<td>

~20 MB

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

**Data sharing**

</td>  
<td>

Publication

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

**Data set short name**

</th>  
<th>

**ZAero-FEA**

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

**Data set full name**

</td>  
<td>

Effects of Defects FE analysis results

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

**Responsible beneficiary**

</td>  
<td>

DS

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

**Description**

</td>  
<td>

Datasets for multiple FE analysis runs used to determine the effect of
different defects and defect locations on the properties of laminates. Use to
create the lookup EDB for use during manufacture to determine the knock-down
factors to apply for measured defects. Many (100 - 1000s) instances are
expected.

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

**Data format**

</td>  
<td>

Proprietary file format

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

**Data set size**

</td>  
<td>

~10 GB

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

**Data management**

</td>  
<td>

Confidential

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

**Data set short name**

</th>  
<th>

**ZAero-ALU**

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

**Data set full name**

</td>  
<td>

Automated fiber placement lay-up definition

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

**Responsible beneficiary**

</td>  
<td>

MTorres

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

**Description**

</td>  
<td>

Definition of paths for lay-up on AFP machines.

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

**Data format**

</td>  
<td>

CATIA file

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

**Data set size**

</td>  
<td>

~5 MB

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

**Data sharing**

</td>  
<td>

Confidential

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

**Data set short name**

</th>  
<th>

**ZAero-DLU**

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

**Data set full name**

</td>  
<td>

Automated dry material placement lay-up definition

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

**Responsible beneficiary**

</td>  
<td>

Danobat

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

**Description**

</td>  
<td>

Definition of paths for lay-up on ADMP machines.

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

**Data format**

</td>  
<td>

JT format (could be provided in any other CAD data format)

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

**Data set size**

</td>  
<td>

~5 MB

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

**Data management**

</td>  
<td>

Confidential

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

**7.**

</th>  
<th>

**Allocation of Resources**

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

Costs for making data FAIR in the ZAero project will not be extensive. Due to
the use of the Zenodo repository, no additional costs for infrastructure
concerning storage and online availability of the data will occur. Concerning
efforts related to preparation of the data for easy re-use, all partners need
to work together to define clear interfaces within the project anyway. If the
definition of internal interfaces is done in a good way, this will ease
preparation of data for publication. We therefore expect that all efforts will
be covered by the activities within the individual technical work packages
and/or the dissemination work package.

As a coordinator, Profactor will be responsible for keeping an overview and
guiding data management across the whole project. However, individual partners
are associated to data sets and declared “responsible beneficiary” as
specified in the tables above. As such, partners are expected to supervise
data acquisition, storage, and documentation for “their” data sets. In case
specific versions of data sets that allow interesting (scientific) insights
are identified, these will be presented and discussed in the regular telephone
conferences or at general meetings. Activities for publication of data sets
(preparation of scientific publications, upload to online repository, etc.)
will be driven by the respective responsible beneficiaries.