**Publishable executive summary**

The document describes the way of data management in this project. A
significant portion of the project resources, estimated to be approximately
50%, are devoted to data management. The purpose of this document is to verify
that data which is managed, is treated in a so-called FAIR way, that is, data
are findable, accessible, interoperable and reusable as much as possible.

This Deliverable document is structured in the following way: The introduction
of this document lists the different categories of data storage used in this
project, and following from that all possible file types. The following
section “data summary” lists describes the management of data in the context
of FAIR principles.

As the main goal of this project is to interconnect different simulation tools
and component models with each other, it is strictly required that data in
this project are findable, which is enabled by a standardized naming
convention of signal data. Following up on that, the standardized naming
convention also allows for openly accessible data. The naming convention will
be made public, which is one purpose of this project. Partially, also
simulation component models will be made also openly accessible to the public.
This will allow re-usability beyond and after HIFI-ELEMENTS.
#  Purpose of the Document

The document describes the way of data management in this project. Data
management is understood in the sense of which data is being produced,
collected, stored and maintained in this project. The purpose of this document
is to verify that data which is managed, is treated in a so-called FAIR way,
that is, data are findable, accessible, interoperable and reusable as much as
possible.

##  Document Structure

This Deliverable document is structured in the following way: The introduction
of this document lists the different categories of data storage used in this
project, and following from that all possible file types. The following
section data summary lists describes the management of data in the context of
the so-called FAIR principles (findable, accessible, interoperable, and re-
useable).

##  Deviations from original Description in the Grant Agreement Annex 1 Part A

###  Description of work related to deliverable in GA Annex 1 – Part A

The Data Management Plan is a mandatory deliverable for all H2020 projects.
The general definition of the contents of the Data Management Plan reads [1]:

Data Management Plans (DMPs) are a key element of good data management. A DMP
describes the data management life cycle for the data to be collected,
processed and/or generated by a Horizon 2020 project. As part of making
research data findable, accessible, interoperable and re-usable (FAIR), a DMP
should include information on:

  * the handling of research data during and after the end of the project 

  

  * what data will be collected, processed and/or generated 

  

  * which methodology and standards will be applied 

  

  * whether data will be shared/made open access and 

  

  * how data will be curated and preserved (including after the end of the project). 

  

A DMP is required for all projects participating in the extended ORD pilot,
unless they opt out of the ORD pilot. However, projects that opt out are still
encouraged to submit a DMP on a voluntary basis.

###  Time deviations from original planning in GA Annex 1 – Part A

There are no deviations with respect to timing of this deliverable.

###  Content deviations from original plan in GA Annex 1 – Part A

There are no deviations from the Annex 1 – Part A with respect to the content.

#  Introduction

The Data Management Plan of HIFI-ELEMENTS will introduce first the storage
systems in which data are stored, and subsequently the types of data that have
to be managed within HIFI-ELEMENTS will be listed. Then, it will be explained
what type of data is stored where and comments on the data life cycle are
given.

##  Storage systems

For the activities within HIFI-ELEMENTS, the following storage systems are
being used:

###  Cloud services

####  Projectplace

In order to manage the project coordination, data exchange between the
different work packages on management level, organization of appointments and
on-line meetings is organized using the web services provided by Projectplace
(  _https://www.projectplace.com/_ )  . The coordination data and parts of
major technical results (e.g. system diagrams, topology definitions etc.) are
stored on that share. Manager of the project data is the contractor
UNIRESEARCH.

####  Wordpress

The official project website (  _http://www.hifi-elements.eu/_ )  is
maintained via the cloud based hosting server Wordpress.

####  SYNECT

The tool SYNECT by dSPACE is an essential part of the project and is described
as the following [2]:

SYNECT is a data management and collaboration software tool with a special
focus on model based development and ECU testing. The software is designed to
help you manage data throughout the entire development process. This data can
include models, signals, parameters, tests, test results, and more. SYNECT
also handles data dependencies, versions and variants, as well as links to the
underlying requirements. One key aspect of SYNECT is direct connection to
engineering tools, e.g., MATLAB®, Simulink®, TargetLink®, or AutomationDesk,
and application/product lifecycle management systems (ALM/PLM) so that you can
work with your preferred tools and seamlessly exchange data. SYNECT is ideal
for automotives, aerospace, industrial automation and medical engineering –
and wherever embedded systems are developed through model based design.

###  Version Control Systems

####  Subversion

Documents or files that undergo multiple stages of revisions or development
are stored in version control systems such as available with the Open Source
Tool Subversion (  _https://subversion.apache.org/_ )  . Subversion supports
web protocol based and server based access to the versioned repository,
forking of files into different revisions and releases are supported as well
as renaming of files from one repository revision to the other. Subversion is
able to maintain both text based as also binary files.

###  Network File Shares

Other data are stored individually at each partner on proprietary (Network)
File Shares. Those network shares are in general only available in the
intranet of each partner and are accessible only by the members of the
project. The partner network shares are used for the daily work of each task
to keep and manage working data.

##  Data Types

In this section, the different data types dealt with in the project are
presented.

###  Documentation

For general documentation and presentation of project results and its
communication, only commonly used data formats are being used:

  * Text documents (.txt) 

  

  * Adobe Acrobat Portable Document Format (.pdf) 

  

  * Microsoft Office Word (.docx) 

  

  * Microsoft PowerPoint (.pptx)HTML 

  

The first four mentioned file formats are used at each project partner
internally, but also for exchange between the project partners and for
presentation purposes. All file formats can be opened and edited not only by
proprietary software of the file format developers (e.g. Microsoft Office,
Adobe Acrobat), but also Open Source Software like Open Office.

In order to exchange presentations between the partners, each of them is
recommended to use pdf as standard file format to control the distribution of
information from the owner of that information. However, the users are also
allowed to distribute presentations in editable PowerPoint format if they
would like to explicitly allow for the dissemination of presentation contents
by other partners.

###  Tabulated Data

Tabulated Data files are mainly used in the context of the simulation and
testing activities but also during meetings, for simple analysis and
visualisation of values. These fall mainly under the following categories:

  * Simulation Data 

  

  * Testing Data 

  

  * Parameter Files 

  

Tabulated data are mostly contained in the following types:

  * Microsoft Excel (.xlsx) 

  

  * Comma Separated Values (.CSV) 

  

  * Plain text files (.txt) 

  

  * Binary data 

  

###  Program Files (Data)

HIFI-ELEMENTS also deals with different simulation tools and programs and with
the inter exchange of those programs between the partners. Therefore, such
program in and output also need to be partially exchanged between the partners
and the usage of programs need to be managed.

Those programs can be proprietary simulation software or commercial software
like GT-SUITE, KULI, Matlab, MOTOR CAD, Maxwell, Morphee/Xmod, etc. Depending
on the license agreement situation, the program files may be exchanged freely,
otherwise it needs to be ensured that each partner has the required license to
perform his task or receives this license, if possible, from another partner.
In- and output of program data are discussed in the following section ‘Model
Data’.

###  Model Data

Pertinent to the simulation software described in the previous sub-section,
for each simulation software model data are required, either serving as input
to the simulation or as an output that requires post-processing. In general
each file format for the model data of the simulation task is proprietary and
requires conversion tools to openly readable file formats.

##  FAIR Data

###  Making Data findable, including provisions for metadata

As one main goal of this project is to interconnect different simulation tools
and component models with each other, it is strictly required that data in
this project are findable. First of all, between simulation tools signal data
have to be exchanged. In the context of this project data from signals become
findable when the naming of the signals follow a pre-defined structure.
Therefore, as an output of WP1, the deliverable D1.1 “Document describing the
safety requirements and modelling guidelines” explains the naming convention
(see Figure 1) of the in- and output signals from each component simulation
model.

This allows for an replacement of component models (low fidelity model against
high fidelity model or plant models for different component hardware).
Furthermore, the connection of different component data signals will be
enabled efficiently by the standardized naming convention. Thirdly, only the
standardised naming convention allows for an easy access of data signals for
post-processing of results.
D1.1 [4]

###  Making data openly accessible

Following up on the standards described in the previous sub-section, the
standardised naming convention also allows for openly accessible data. The
naming convention will be made public, which is one purpose of this project.
Partially, component models will be made also openly accessible to the public.
The FMU/FMI description will be made publicly available as well.

###  Making data interoperable

Also, by the principles of signal data naming convention and component model
interface standardization as described above, data that are generated and used
above are thereby interoperable.

###  Increase data re-use

The standardization of interface for component models allows for the easy
exchange of such models and their reuse. This is especially due to those
component models which will become publicly available. Those simulation models
will be re-useable beyond and after HIFI-ELEMENTS.

##  Allocation of resources

A significant portion of the project resources, estimated to be approximately
50%, are devoted to data management.

##  Data security

Principles of data security are taken into account when the layout of the data
management was defined. All data are password protected and only made
available to project members On the publicly accessible website, only public
data are stored.

##  Ethical aspects

Ethical aspects are regarded in this project or are not compromised by this
project. Only technically related data are treated in this project and
therefore do not contain person related data. Exception are the financial
reports to EUfin which may contain some person related data reports.

Storage locations, of data are in EU or other partner countries (Turkey).

##  Other

Software development and the data management that goes alongside with it, will
be conducted using the Agile Model Development Principles. This principle is
presented in the framework of WP1, see also [3].

#  Overview of Data Management

**Table 3-1 Overview on Storage Systems**  
  
<table>  
<tr>  
<th>

Type of

Storage

</th>  
<th>

Storage Location

</th>  
<th>

Indexing

</th>  
<th>

Access

</th>  
<th>

Versioning

</th>  
<th>

Security/ Encryption

</th>  
<th>

Security/Backup

</th>  
<th>

Costs

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

**Cloud –**

**Projectplace**

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

Restricted, individual access rights

</td>  
<td>

Yes

</td>  
<td>

Password protected

</td>  
<td>

</td>  
<td>

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

**Cloud –**

**Wordpress**

</td>  
<td>

Germany

</td>  
<td>

</td>  
<td>

Public

</td>  
<td>

No

</td>  
<td>

Password

</td>  
<td>

</td>  
<td>

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

**SYNECT**

**Server**

</td>  
<td>

Amazon Cloud hosted, Ireland

</td>  
<td>

Data queries (SQL)

</td>  
<td>

Restricted, individual access rights

</td>  
<td>

Yes

</td>  
<td>

Encryption (httpsprotocol)

</td>  
<td>

Incremental backup

</td>  
<td>

Hosting costs

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

**Version**

**Control –**

**Subversion**

</td>  
<td>

Not partner specific, dSPACE, Germany

</td>  
<td>

no

</td>  
<td>

Restricted,

HIFI “global” access rights

</td>  
<td>

Yes

</td>  
<td>

Password

</td>  
<td>

Incremental backup

</td>  
<td>

Open

Source Tool, only file storage costs

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

**Version**

**Control –**

**Subversion**

</td>  
<td>

Partner specific servers,

e.g. at FEV

</td>  
<td>

no

</td>  
<td>

Restricted, individual access rights

</td>  
<td>

Yes

</td>  
<td>

</td>  
<td>

Incremental backup

</td>  
<td>

Open

Source Tool, only file storage costs

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

**File Shares**

</td>  
<td>

Partner specific servers

</td>  
<td>

yes

</td>  
<td>

User access limited.

</td>  
<td>

No

</td>  
<td>

</td>  
<td>

Incremental backup

</td>  
<td>

various

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

**Table 3-2 Overview on Data File Types**  
  
<table>  
<tr>  
<th>

File Type Example Type of

Storage

</th>  
<th>

Access/Licensing

</th>  
<th>

Versioning

</th>  
<th>

Confidential/

Classified/Public

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

**Text**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Adobe Acrobat**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Word**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**PowerPoint**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**HTML**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Excel**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**CSV**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Binary data**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

SYNECT Database

Backup File (*.bak)

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Program File Data**

</td>  
<td>

MATLAB/

Simulink

</td>  
<td>

</td>  
<td>

Partially proprietary

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

KULI

</td>  
<td>

</td>  
<td>

Commercial License

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

xMOD

</td>  
<td>

File

</td>  
<td>

License to HIFIUsers

</td>  
<td>

YES

</td>  
<td>

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

</td>  
<td>

SYNECT Client

</td>  
<td>

</td>  
<td>

License to HIFIUsers

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

SYNECT Client Add-

Ons (.ADDON /

.ADDONZ)

</td>  
<td>

</td>  
<td>

No license required.

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

MOTOR CAD

</td>  
<td>

File

</td>  
<td>

Commercial License

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

Maxwell

</td>  
<td>

File

</td>  
<td>

Commercial License

</td>  
<td>

</td>  
<td>

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

**Scripts**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

Python Scripts (.PY)

</td>  
<td>

File

</td>  
<td>

No license

</td>  
<td>

Yes

</td>  
<td>

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

</td>  
<td>

MATLAB Scripts

(.M)

</td>  
<td>

File

</td>  
<td>

License to

execute

</td>  
<td>

yes

</td>  
<td>

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

**Model Data**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

Enterprise

Architect SysML

</td>  
<td>

File

</td>  
<td>

Commercial License

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

**MATLAB**

**SIMULINK Models**

**(.SLX/.MDL)**

</td>  
<td>

File

</td>  
<td>

Commercial License. **Limited access for IP**

**protection**

</td>  
<td>

yes

</td>  
<td>

**Confidential**

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

</td>  
<td>

**KULI Models**

</td>  
<td>

File

</td>  
<td>

Commercial License.

**Limited access for IP**

**protection**

</td>  
<td>

yes

</td>  
<td>

**Confidential**

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

</td>  
<td>

**xMOD models**

(.xmodel/.dll/.rtdll)

</td>  
<td>

File

</td>  
<td>

License to HIFIUsers

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

FMI 2.0 FMU Files (.FMU)

</td>  
<td>

</td>  
<td>

In general no license. May contain license check or

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

reference to a specific runtime system for simulation.

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Simulation Data**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

ASAM MDF-4

Capturing Results

(.MF4)

</td>  
<td>

</td>  
<td>

XML format, license for

reader/writer tooling

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

MATLAB Data (.MAT)

</td>  
<td>

</td>  
<td>

Commercial license

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

xMOD ASCI files

(.CSV, .txt)

</td>  
<td>

File

</td>  
<td>

No license

</td>  
<td>

Yes

</td>  
<td>

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

**Testing Data**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

ASAM XIL API

Stimulation Files

(.STI)

</td>  
<td>

</td>  
<td>

XML format, license for

reader/writer tooling

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

xMOD API testing format (.xcce)

</td>  
<td>

File

</td>  
<td>

No license

</td>  
<td>

No

</td>  
<td>

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

**Parameter**

**Files**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

ASAM Parameter

Values (.CDFX)

</td>  
<td>

</td>  
<td>

XML format, license for

reader/writer tooling

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

xMOD calibration parameters based on XML (.XPAR)

</td>  
<td>

File

</td>  
<td>

XML format, no license

</td>  
<td>

Yes

</td>  
<td>

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

</td>  
<td>

MATLAB Scripts

(.M)

</td>  
<td>

</td>  
<td>

License to

execute

</td>  
<td>

yes

</td>  
<td>

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

</td>  
<td>

MATLAB Data (.MAT)

</td>  
<td>

</td>  
<td>

Commercial license

</td>  
<td>

yes

</td>  
<td>

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

#  Discussion and Conclusions

The document described the way of data management in this project. A
significant portion of the project resources, estimated to be approximately
50%, are devoted to data management. The purpose of this document is to verify
that data which is managed, is treated in a so-called FAIR way, that is, data
are findable, accessible, interoperable and reusable as much as possible.

#  Recommendations

It is recommended that this document will be updated in case that significant
changes of the data management procedure that is used in this project will
occur.

#  Risk Register

##  Risk Register

“With reference to the critical risks and mitigation actions this deliverable
is not linked to any open risk. See D8.1 – “Project handbook” and the
monitoring file of the Steering Committee

( _https://service.projectplace.com/pp/pp.cgi/r1293387004_ ):

New identified risks that occurred are listed in the table below. Currently no
risks are identified.  
  
<table>  
<tr>  
<th>

Risk

number

</th>  
<th>

Description of Risk

</th>  
<th>

Proposed Risk Mitigation Measure

</th>  
<th>

Probability / effect

</th>  
<th>

Current estimation

of risk occurence

(comments)

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

##  Quality Assurance

The Steering Committee is the body for quality assurance. The procedure for
review and approval of deliverables is described in the deliverable report
D8.1 – “Project Handbook”. The quality will be ensured by checks and approvals
of Work package leaders, see front pages of all deliverables.