#  INTRODUCTION

The present Data Management Plan (DMP) 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 is to be considered in combination with:

  * Section 9 “Access Rights” and Attachment 1 “Background included” of the Consortium Agreement, dealing with access rights and the use of the Workflow Tool. 

  

  * Section 3 “Rights and obligations related to background and results” of the Grant Agreement No. 777594, dealing with rights and obligations related to background and results. 

  

The DMP is organised per Work Package (WP) to concretely describe the
contribution of each WP to the outcomes as well as the spin-off potential of
each activity.

To understand the data that the project will generate, a brief overview of the
project is given below:

To meet the needs of S2R and Horizon 2020, OptiYard will design optimised
processes for managing marshalling yards and terminals, considering their
interaction with the network. The processes considered are those that must be
performed in real-time, to guarantee on-time delivery and operational
efficiency, for single wagon transport.

OptiYard addresses critical operational points of the transport chain (both
rail marshalling yards or as transfer points to other modes) to improve
capacity and reliability. Most importantly, these improvements will enhance
competitiveness whilst increasing service reliability and customer
satisfaction by providing accurate and updated information. Real-time
interaction between yard and relevant network IT systems will allow for
software-based planning and ultimately optimisation of single wagonload and
blocktrain operational processes.

The lack of full integration between yard and network is a current weakness,
and one that increases as more real-time data becomes available, because we
will miss the opportunities to realise the benefits of such improved data.
Hence, there needs to be much more progress in developing the integration of
information systems and control systems between the yard systems and the
network systems. It is in this field where OptiYard offers the most exciting
possibilities.

Large rail freight marshalling yards are complex operations which present
major challenges to achieving operational efficiency, such that managing them
effectively even in a stand-alone mode is a challenging task, for which
sophisticated scheduling systems are required. The arrival and departure of
freight trains to/from the yard are closely linked to the operations of the
wider network eco system, making some of the yard operation processes
(shunting, marshalling and departing train dispatches) more time-critical than
others.

Thus, a key challenge to the future success of yard management lies in the
real-time information exchange between the yard and the relevant network eco
system, and the interactive responses between the yard  
  
<table>  
<tr>  
<th>

and the network managements. With such information capabilities, yard
operations could be rescheduled at short notice to take account of
perturbations on the network, such as the delayed arrival of an incoming
freight train, allowing rapid re-optimisation of yard operations. Real-time
network information could also be used to identify more accurate departure
times for trains leaving yards, again allowing for beneficial rescheduling of
yard operations.

Hence, OptiYard develops a holistic approach to providing a real-time
decision-making framework for optimising yard operations and the yard-network
interface.

The technical WPs will address the following areas:

WP2 Data Analytics

WP3 Specification of the OptiYard Simulation Environment

WP4 Modelling

WP5 Process Optimisation

WP6 Business Cases - Feasibility & Simulation Tests

WP7 Dissemination, Communication and Results Exploitation

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

#  DATA MANAGEMENT AT PROJECT LEVEL

##  DATA COLLECTION

Data exchange is crucial in this project to allow an efficient and reliable
connection between the yard and the surrounding network. For simulation
purposes, data will be stored and used, which makes necessary to define the
corresponding data management plan. In addition to this data used for the
technical aspects of the project, there is also a need for defining the rules
concerning data related to management and dissemination activities.

Each Work Package Leader is responsible for defining and describing all (non-
generic) data sets specific to their individual work package.

The WP leaders shall formally review the data sets related to their WP when
relevant and at least at time for first and second project periodic report to
the European Commission.

All modifications and additions to the DMP shall be provided to the OptiYard
Coordinator, UIC, for inclusion in the DMP.

##  DATA ARCHIVING & PRESERVATION

A Workflow Tool platform was created to support the work of the consortium
members. For access to the website, users can register to the tool with a
valid e-mail address, need to choose a password and have then to validate a
link received by e-mail. Once done, the administrator of the workflow tool has
to validate the registration to the OPTIYARD workspace. Beneficiaries who do
not have access to the website can ask the Coordinator to open an account.

OptiYard Partners are strongly suggested to use the website to share project
information. The main functionality that should be used is the upload and
download of documents (contact list, deliverables, minutes of meetings,
agendas, presentations, Technical Annex of the Grant Agreement, etc.).

An instruction manual on how to use the Workflow Tool is circulated among
beneficiaries; the document is also accessible on the website (Tutorial for
all Project Members).

At the end of the project, when the OptiYard will be formally closed, all the
data material that has been collated or generated within the project and
registered on the Workflow Tool shall be copied and transferred to a digital
archive.

###  Data Security & Integrity

The OptiYard project will be subject to the same levels of data security as
applied to normal operations for the Workflow Tool within UIC.

All data types that are uploaded to the Workflow Tool shall not be encrypted,
irrespective of whether these data items have been identified for future
archiving or not.

Members are granted with access rights in the Workflow Tool according to their
role in the project.

Rights apply to directories, calendars and documents. They define which parts
can be seen and which actions can be done and by which group(s). Rights are
therefore given to group(s) on objects like directories, calendars and
documents.

Every rights settings interface looks the same. Only the list of rights is
different. Below is an example of rights applied to directories. There are
rights to “view” the directory, “modify” it, “export” it, “assign” or
“unassign” a user to it. All members of the project have access to all
documents and meetings in the tool.

All partners contributing in a work package are given rights to create new
documents.

The Coordinator has overall project administration rights, enabling to
administrate the complete project document database.

When the Coordinator intends to modify a WP domain, he has an obligation to
inform relevant WP leaders about the changes he intends to bring to the
document database.

###  Document Archiving

The document structure and type definition will be preserved as defined in the
document breakdown structure and work package groupings specified for the
Workflow Tool.

The process of archiving will be based on a data extract performed by UIC
within 12 weeks of the formal closure of the OptiYard project.

##  FILE NAMING CONVENTIONS

Whenever a new document is produced within the project, it must be uploaded on
the Workflow Tool. Before a document is uploaded, a unique document code must
be assigned according to the following subsections that describe how this
identification code is structured and set up.

The identification code contains the six following sections:

**[Project] – [Domain] – [Type] – [Owner] – [Number] – [Filename]**

  * [Project] is OptiYard for all OptiYard documents 

  

  * [Domain] is the relevant domain in the Workflow Tool (WP, Task or project body) 

  

  * [Type] is one letter defining the document category 

  

  * [Owner] is the trigram of the deliverable leader organisation 

  

  * [Number] is an order number allocated by the publisher when the document is first created • [Filename] is a short description of the document Examples: 

  

For documents being circulated internally without having been uploaded on the
Workflow Tool first, there should be significance in the filename as follows:
the project name, WP name, type, partner sharing the document, and filename
should be mentioned (i.e. OptiYard_WP1_A_UIC_001_WBS).

Documents are classified among the following types:

##  DATA & SHIFT2RAIL

The OptiYard deliverables and all other related generated data are
fundamentally linked to the future planned Shift2Rail project activity.

The data requirements of this DMP have been developed with the objective of
providing data structures that are uniform and not subject to possible future
ambiguous interpretation that will facilitate synergies.

Data shall be specifically selected for archiving based on the criteria that
it will be likely to be useful for future Shift2Rail activities.

#  DMP OF WP1: MANAGEMENT

##  DATA TYPES

Existing data used in this WP include the following data types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

OptiYard-1.1

</td>  
<td>

Database of consortium partners: this database contains data such as name,
e-mail, company, telephone.

</td>  
<td>

.xls

</td>  
<td>

Evolutive depending on the updates of the mailing list.

</td>  
<td>

The data will be kept in the UIC servers in accordance with the provisions of
Regulation (EU) 2016/679 OF THE EUROPEAN

PARLIAMENT AND OF THE

COUNCIL of 27 April 2016 on the protection of natural persons with regard to
the processing of personal data and on the free movement of such data, and
repealing Directive 95/46/EC (General Data Protection Regulation).

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

**Table 1: Existing Data used in WP1**

No additional data are planned to be generated in this WP.

##  STANDARDS, METADATA AND QUALITY ISSUES

No specific standards and metadata are planned to be used for data related to
WP1.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

OptiYard-1.2

</td>  
<td>

This data is confidential and only the consortium partners will have access to
it.

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

**Table 2: Data Sharing in WP1**

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

OptiYard-1.1

</td>  
<td>

Data will be stored on the UIC server.

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

**Table 3: Archiving and preservation of the data in WP1**

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

OptiYard-1.1

</td>  
<td>

Giancarlo DE MARCO TELESE (UIC)

</td>  
<td>

Update and maintenance of the data

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

**Table 4: Data Management Responsibilities in WP1**

#  DMP OF WP2: DATA ANALYTICS

##  DATA TYPES

Existing data used in this WP include the following data types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

RailData ISR

</td>  
<td>

ISR, the IT service used by railway undertakings to exchange information about

wagons' movements

</td>  
<td>

Data are used to enrich the

movement

information with the consignment data (transport description)

</td>  
<td>

Large

</td>  
<td>

http://www.raildata.coop/isr

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

RNE (TIS)

</td>  
<td>

The Train

Information System is a webbased application that supports international Train
Management by

delivering realtime train data concerning international (partly national)
passenger and

freight trains. The relevant data is obtained directly from the Infrastructure
Managers’ systems.

</td>  
<td>

Fully TAF/TAP TSI-compliant

</td>  
<td>

Large

</td>  
<td>

http://tis.rne.eu/

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

XML files

</td>  
<td>

For data exchange in marshalling facilities. XML is a file extension for an
Extensible

Mark-up Language (XML) file format

used to create common

information formats and share both the format and the data on the World Wide
Web, intranets, and elsewhere

</td>  
<td>

XML is similar to

HTML. Some

marshalling yards use this format for data exchange.

</td>  
<td>

Large

</td>  
<td>

A Marshalling yard/facility

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

</td>  
<td>

using standard ASCII text.

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

XSD Schema

file;

</td>  
<td>

To keep file of operating

processes with

freight trains. A file with the XSD file extension is most likely an XML
Schema file;

</td>  
<td>

A text-based file format that defines validation rules for an XML file and
explains the XML form. XML files can reference an XSD

file with the schema -

Location attribute.

</td>  
<td>

Large

</td>  
<td>

MYs, RUs and IMs

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

railML

</td>  
<td>

railML is published as a series of XML schemas holding subschemas, each of
which

encompasses a

particular field of

railway application:

  * Common 

  

concepts and objects, sometimes not mentioned separately;

  * Timetable (TT); 

  

  * Rolling stock (RS); 

  

  * Infrastructure 

  

(IS), both macroscopic and microscopic;

  * Interlocking, from railML 3 on. 

  

</td>  
<td>

railML is a data exchange format developed by a consortium of railway
companies,

academic

institutions and consultancy firms.

</td>  
<td>

Large

</td>  
<td>

railML.org

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

**Table 5: Existing Data used in WP2**

No data are planned to be generated in this WP.

##  STANDARDS, METADATA AND QUALITY ISSUES

Data sources have been identified. For the purposes of WP 2 data has not been
generated.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

OptiYard-2.1

</td>  
<td>

Information collected from public sources; used for the purposes of D2.1

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

**Table 6: Data Sharing in WP2**

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

OptiYard-2.1

</td>  
<td>

For internal use and the purposes of D2.1

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

**Table 7: Archiving and preservation of the data in WP2**

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

OptiYard-2.1

</td>  
<td>

Marin Marinov, UNEW

</td>  
<td>

Data identified is not confidential

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

**Table 8: Data Management Responsibilities in WP2**

#  DMP OF WP3: SPECIFICATION OF THE OPTIYARD SIMULATION ENVIRONMENT

##  DATA TYPES

WP3 sets out and describes the technical and functional specifications of the
models for yards and networks, and as such does not utilise formal data sets,
or produce formal datasets for subsequent work packages.

##  STANDARDS, METADATA AND QUALITY ISSUES

WP3 discussed issues to address in developing a data management interface for
real-time yard and network management system. The key elements identified are
summarised below:

  * Real-time animation facilitated by flexible simulation tools 

  

  * Clear specification of metadata sets 

  

  * Online reporting on the productivity of the rail freight system 

  

  * IT security in accordance with ISO 27001:2013 

  

  * Documentation of performance monitoring and updates 

  

  * Search facilities for metadata inspection and interrogation 

  

  * Common data structure and interface, for data portability 

  

  * Common specification for real time management interface 

  

##  DATA SHARING

Any identified data will be shared via the UIC server.

##  ARCHIVING AND PRESERVATION

Any identified data will be stored via the UIC server.

##  DATA MANAGEMENT RESPONSIBILITIES

Not applicable.

#  DMP OF WP4: MODELLING

##  DATA TYPES

Existing data used in this WP include the following data types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

OptiYard-4.1

</td>  
<td>

Trieste Campo Marzio terminal track layouts

</td>  
<td>

jpeg pdf

dwg

</td>  
<td>

10 MB

</td>  
<td>

Adriafer

Confidential

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

OptiYard-4.2

</td>  
<td>

Trieste Campo Marzio schematic track diagrams with signalling

</td>  
<td>

Tiff pdf

</td>  
<td>

10 MB

</td>  
<td>

Adriafer

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

OptiYard-4.3

</td>  
<td>

Trieste Campo Marzio CAD drawing

</td>  
<td>

dwg

</td>  
<td>

2 MB

</td>  
<td>

Adriafer

Confidential

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

OptiYard-4.4

</td>  
<td>

Trieste Campo Marzio surrounding

railway network

maps

</td>  
<td>

pdf

</td>  
<td>

10 MB

</td>  
<td>

Adriafer

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

OptiYard-4.5

</td>  
<td>

Trieste Campo Marzio anonymised train schedules

</td>  
<td>

pdf

</td>  
<td>

100 kB

</td>  
<td>

Adriafer

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

OptiYard-4.6

</td>  
<td>

Ceska Trebova terminal track layouts

</td>  
<td>

dwg

</td>  
<td>

500 kB

</td>  
<td>

CD Cargo/Oltis confidential

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

OptiYard-4.7

</td>  
<td>

Ceska Trebova schematic track diagrams with signalling

</td>  
<td>

xlsx

</td>  
<td>

1.5 MB

</td>  
<td>

CD Cargo

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

OptiYard-4.8

</td>  
<td>

Ceska Trebova CAD drawing

</td>  
<td>

dwg

</td>  
<td>

500 kB

</td>  
<td>

CD Cargo/Oltis confidential

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

OptiYard-4.9

</td>  
<td>

Ceska Trebova surrounding railway network maps

</td>  
<td>

various formats

</td>  
<td>

10 MB

</td>  
<td>

CD Cargo

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

OptiYard-4.10

</td>  
<td>

Ceska Trebova anonymised train schedules

</td>  
<td>

various formats

</td>  
<td>

1 MB

</td>  
<td>

CD Cargo

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

OptiYard-4.11

</td>  
<td>

Ceska Trebova anonymised wagon lists for inbound trains

</td>  
<td>

xlsx

</td>  
<td>

1 MB

</td>  
<td>

CD Cargo/Oltis confidential

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

**Table 9: Existing Data used in WP4**

Data generated in this WP include the following types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

OptiYard-4.12

</td>  
<td>

Ceska Trebova Yard Model (nonoptimized operation)

</td>  
<td>

Executable

(installation package)

</td>  
<td>

50 MB

</td>  
<td>

SIMCON

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

OptiYard-4.13

</td>  
<td>

Ceska Trebova Yard simulation results (nonoptimized operation)

</td>  
<td>

Results are part of the simulation model with stored simulation protocol from
simulation run

(included in installation package)

</td>  
<td>

see executable with yard model

</td>  
<td>

SIMCON/CD Cargo

confidential

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

OptiYard-4.14

</td>  
<td>

Trieste Yard Model (non-optimized operation)

</td>  
<td>

Executable

(installation package)

</td>  
<td>

50 MB

</td>  
<td>

SIMCON

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

OptiYard-4.15

</td>  
<td>

Trieste Yard simulation results (non-optimized operation)

</td>  
<td>

Results are part of the simulation model with stored simulation protocol from
simulation run

(included in installation package)

</td>  
<td>

see executable with yard model

</td>  
<td>

SIMCON/Adriafer confidential

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

OptiYard-4.16

</td>  
<td>

Ceska Trebova Network Model

</td>  
<td>

executable

</td>  
<td>

1 MB

</td>  
<td>

LEEDS

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

OptiYard-4.17

</td>  
<td>

Ceska Trebova Network simulation results

</td>  
<td>

various formats

</td>  
<td>

50 MB

</td>  
<td>

LEEDS

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

OptiYard-4.18

</td>  
<td>

Trieste Network Model

</td>  
<td>

executable

</td>  
<td>

1 MB

</td>  
<td>

LEEDS

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

OptiYard-4.19

</td>  
<td>

Trieste Network simulation results

</td>  
<td>

various formats

</td>  
<td>

50 MB

</td>  
<td>

LEEDS

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

**Table 10: Data Generated in WP4**

##  STANDARDS, METADATA AND QUALITY ISSUES

All the data produced within this work package will following the rules set in
chapters 2.2 and 2.3.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

OptiYard-4.20

</td>  
<td>

The identified data is shared via the UIC server.

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

**Table 11: Data Sharing in WP4**

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

OptiYard-4.21

</td>  
<td>

Data is stored on the UIC server.

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

**Table 12: Archiving and preservation of the data in WP4**

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

OptiYard-4.22

</td>  
<td>

Miloš Zaťko (SIMCON)

</td>  
<td>

Update and maintenance of nonoptimized yard simulation models

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

**Table 13: Data Management Responsibilities in WP4**

#  DMP OF WP5: PROCESS OPTIMISATION

##  DATA TYPES

Data generated in this WP include the following types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

OptiYard-5.x

</td>  
<td>

Ceska Trebova Yard Model with interface to

optimization module

</td>  
<td>

Executable

(installation package)

</td>  
<td>

50 MB

</td>  
<td>

SIMCON

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

OptiYard-5.x

</td>  
<td>

Trieste Yard Model with interface to

optimization module

</td>  
<td>

Executable

(installation package)

</td>  
<td>

50 MB

</td>  
<td>

SIMCON

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

##  STANDARDS, METADATA AND QUALITY ISSUES

We use the XML standard fixed by the following (and typical) code:

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="  _http://www.w3.org/2001/XMLSchema_ "
elementFormDefault="qualified">

All the data of our XML data model follows the W3C standard.

We use two categories of files. The metadata of the first one gathers the
static data (e.g., yard layout, signals, available operations). The second
file groups the data which can change over time (e.g., trains/cars, yard
locomotive).

The following quality issues will be handled:

We obtain a standardized XML model with the software Oxygen XML Editor. This
editor integrates the latest version of the Xerces-J XML parser to validate
documents against XML Schemas, i.e., the documents are "Well-Formed", and also
conform to the rules of a Document Type Definition (DTD), XML Schema, or other
type of schema that defines the structure of an XML document.

We declare all the types and structures data through the software (lists,
lists of lists etc.). As a result, we obtain a normalized schema, saved in a
'.xsd file". The same software generates automatically all the documentation
explaining in detail the different metadata used for the two types of file.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

OptiYard-5.x

</td>  
<td>

The identified data is shared via the UIC server.

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

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

OptiYard-5.x

</td>  
<td>

Data is stored on the UIC server.

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

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

OptiYard-5.x

</td>  
<td>

Miloš Zaťko (SIMCON)

</td>  
<td>

Update and maintenance of yard simulation models with interface to
optimization module

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

#  DMP OF WP6: BUSINESS CASES - FEASIBILITY & SIMULATION TESTS

##  DATA TYPES

Existing data used in this WP include the following data types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

Optiyard-6.1

</td>  
<td>

Mainly input from the other WP

</td>  
<td>

Mainly Word and Excel files

</td>  
<td>

Variable

</td>  
<td>

Respective WP leaders

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

OptiYard-6.2

</td>  
<td>

Mainly input from the other WP

</td>  
<td>

Mainly Word and

Excel files

</td>  
<td>

Variable

</td>  
<td>

Respective WP leaders

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

OptiYard 6.3

</td>  
<td>

Mainly input from the other WP

</td>  
<td>

Mainly Word and

Excel files

</td>  
<td>

Variable

</td>  
<td>

Respective WP leaders

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

**Table 14: Existing Data used in WP6**

Data generated in this WP include the following types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset / Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

Optiyard-6.1

</td>  
<td>

Agenda, minutes, reports, slides…

</td>  
<td>

Word, Excel and PPT files

</td>  
<td>

Variable

</td>  
<td>

WP leader (UIRR°

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

OptiYard-6.2

</td>  
<td>

Agenda, minutes, reports, slides…

</td>  
<td>

Word, Excel and PPT files

</td>  
<td>

Variable

</td>  
<td>

WP leader (UIRR)

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

OptiYard 6.3

</td>  
<td>

Agenda, minutes, reports, slides…

</td>  
<td>

Word, Excel and PPT files

</td>  
<td>

Variable

</td>  
<td>

WP leader (UIRR)

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

**Table 15: Data Generated in WP6**

##  STANDARDS, METADATA AND QUALITY ISSUES

All the data produced within this work package will following the rules set in
chapters 2.2 and 2.3.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

Optiyard-6.1

</td>  
<td>

Data will only be shared with the project partners. Sharing with third parties
will only be possible with prior consent of the SMC.

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

OptiYard-6.2

</td>  
<td>

Sharing with third parties will only be possible with prior consent of the
SMC.

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

OptiYard 6.3

</td>  
<td>

Sharing with third parties will only be possible with prior consent of the
SMC.

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

**Table 16: Data Sharing in WP6**

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

Optiyard-6.1

</td>  
<td>

Stored and archived until the end of the project on the UIC server – after the
project lifetime: at least until the official end of the period of an
internal/external audit

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

OptiYard-6.2

</td>  
<td>

Stored and archived until the end of the project on the UIC server – after the
project lifetime: at least until the official end of the period of an
internal/external audit

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

OptiYard 6.3

</td>  
<td>

Stored and archived until the end of the project on the UIC server – after the
project lifetime: at least until the official end of the period of an
internal/external audit

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

**Table 17: Archiving and preservation of the data in WP6**

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

Optiyard-6.1

</td>  
<td>

Eric FEYEN (UIRR)

</td>  
<td>

Storage and maintenance of all related data for task 6.1

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

OptiYard-6.2

</td>  
<td>

Eric FEYEN (UIRR)

</td>  
<td>

Storage and maintenance of all related data for task 6.2

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

OptiYard 6.3

</td>  
<td>

Armand CARILLO (EURNEX)

</td>  
<td>

Storage and maintenance of all related data for task 6.3

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

**Table 18: Data Management Responsibilities in WP6**

#  DMP OF WP7: DISSEMINATION, COMMUNICATION AND RESULTS EXPLOITATION

##  DATA TYPES

Existing data used in this WP include the following data types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of**

**Dataset/Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

OptiYard-7.1

</td>  
<td>

Images: Images and logos from partners participating in the project.

</td>  
<td>

.eps, .ai,

.png,

.jpeg

</td>  
<td>

Variable

</td>  
<td>

The owner gives permission to UIC to use images for dissemination purposes of
OptiYard.

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

OptiYard-7.2

</td>  
<td>

Database of Advisory Board: this database contains data such as name, e-mail,
company, telephone and field of expertise of the partners participating in the
Advisory Board.

</td>  
<td>

.xls

</td>  
<td>

Evolutive depending on the updates of

the mailing list.

</td>  
<td>

The data will be kept in the UIC servers in accordance with the provisions of
Regulation (EU) 2016/679 OF THE

EUROPEAN PARLIAMENT AND OF

THE COUNCIL of 27 April 2016 on the protection of natural persons with regard
to the processing of personal data and on the free movement of such data, and
repealing Directive 95/46/EC

(General Data Protection Regulation).

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

**Table 19: Existing Data used in WP7**

No specific data is planned to be generated in this work package.

##  STANDARDS, METADATA AND QUALITY ISSUES

The pictures and logos are stored in common formats: vector image formats and
picture compression standards.

##  DATA SHARING  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

OptiYard-7.1

</td>  
<td>

The data will not be shared but some of the image database will be used for
dissemination purposes and therefore will become public.

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

OptiYard-7.2

</td>  
<td>

This data is confidential and only the consortium partners will have access to
it.

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

**Table 20: Data Sharing in WP7**

##  ARCHIVING AND PRESERVATION  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

OptiYard-7.1 and 7.2

</td>  
<td>

Data will be stored on the UIC server.

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

**Table 21: Archiving and preservation of the data in WP7**

##  DATA MANAGEMENT RESPONSIBILITIES  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

OptiYard-7.1 and 7.2

</td>  
<td>

Giancarlo DE MARCO TELESE

(UIC)

</td>  
<td>

Update and maintenance of the data

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

**Table 22: Data Management Responsibilities in WP7**

#  CONCLUSION

The purpose of the Data Management Plan is to support the data management life
cycle for all data that will be collected, processed or generated by the
OptiYard project. The DMP is not a fixed document but evolves during the
lifespan of the project. This document is expected to mature during the
project; more developed versions of the plan could be included as additional
revision of this deliverable at later stages. The DMP will be updated at least
after the mid-term and final reviews to fine-tune it to the data generated and
the uses identified by the consortium since not all data or potential uses are
defined at this stage of the project.