#  Introduction

##  Project summary

MOVINGRAIL (‘MOving block and VIrtual coupling New Generations of RAIL
signalling’) is a

Shift2Rail project addressing the topic ‘Analysis for Moving Block and
implementation of Virtual Coupling concept’. The aims of MOVINGRAIL are

  * To identify and assess the most suitable methodology in order to test and bring into service Moving or Fixed Virtual Block contributing to the definition of the Operational Procedures and highlighting the differences with the traditional signalling systems. 

  

  * To analyse the potential business and market response thanks to the application of the Virtual Coupling concept identifying pros/cons in terms of performance and cost, and to assess the needs and work done for the Train-to-Train (T2T) both in IP1 and IP2 and propose convergence of technical communication solution(s). 

  

##  Purpose of this document

This document has been prepared to provide the Data Management Plan (DMP)
which addresses the way research data is managed in the MOVINGRAIL project
within the Open Research Data Pilot (ORD Pilot). The ORD pilot aims to improve
and maximise access and re-use of research data generated by Horizon 2020
projects, considering the need to balance openness and protection of sensitive
information, commercialisation and Intellectual Property Rights (IPR), privacy
concerns, as well as data management and preservation of questions.

DMPs are a key element for good data management, as they describe the
management of the data to be collected, processed and published during a
research project, creating awareness about research data management topics
such data storage, backup, data access, data sharing, archiving and licensing.
MOVINGRAIL hereby states the adherence to the FAIR data principles, whereby
research data is made Findable, Accessible, Interoperable and Re-usable for
the community, responsibly considering possible data restrictions on public
sharing.

It is acknowledged that a DMP is a living document and, therefore, as the
implementation of the project progresses and significant changes occur, this
plan is updated accordingly on a finer level of granularity at the end of each
project period (M12 and M24).

##  Context

The present document constitutes the Deliverable D5.1 “Data Management Plan”
in the framework of the TD2.3 of IP2 (Moving Block) task 2.3.1 (Moving Block
Operational and

Engineering Rules) and task 2.3.6 (Test Specifications), as well as the TD2.8
of IP2 (Virtual

Coupling) task 2.8.3 (Feasibility Analysis) and task 2.8.6 (Impact Analysis).

#  Data Summary

MOVINGRAIL collects various kinds of data:

  1. Semantic data 

  

  2. Stated preference data from surveys and workshops 

  

  3. Simulation data. 

  

  

The responsibility to define and describe all non-generic data sets specific
to an individual work package is with the WP leaders. The WP leaders formally
review and update the data sets related to their WP. All
modifications/additions to the data sets are provided to the MOVINGRAIL
Coordinator (TUD) for inclusion in the DMP.

The table below shows the various data collected with the purpose of the data
collection and its relation to the objective of the project.  
  
<table>  
<tr>  
<th>

**Work Package**

</th>  
<th>

**Data**

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

**WP 1 (TUBS)**

</td>  
<td>

**Semantic data of railway signalling**

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

Purpose

</td>  
<td>

The data supports the operations analysis of train centric signalling

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

Types and format

</td>  
<td>

Excel and PDF

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

Reuse of existing data

</td>  
<td>

Semantic data from X2RAIL-1

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

Origin of data

</td>  
<td>

X2RAIL-1 and own work

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

Expected size of data

</td>  
<td>

Less than 100 MB

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

Data utility

</td>  
<td>

Useful for anyone working on railway signalling engineering and operations

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

**WP 1 (TUBS)**

</td>  
<td>

**Glossary**

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

Purpose

</td>  
<td>

The data supports the operations analysis and terminology for describing
various scenarios.

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

Types and format

</td>  
<td>

mysql, php, flatfile, pdf, epub, html

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

Reuse of existing data

</td>  
<td>

Various literature as specified in references

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

Origin of data

</td>  
<td>

Literature and own work

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

Expected size of data

</td>  
<td>

Less than 100 MB

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

Data utility

</td>  
<td>

Useful for anyone working on railway signalling engineering and operations,
accessible via  _https://glossary.ivev.bau.tu-bs.de/tikiindex.php_ and
_www.movingrail.eu_ under a Creative Commons Attribution 4.0 International
License (CC BY 4.0).

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

**WP 1 (TUBS)**

</td>  
<td>

**Symbol library**

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

Purpose

</td>  
<td>

This TikZ library is a toolbox of symbols geared primarily towards creating
track schematic for either research or educational purposes. It provides a
TikZ frontend to some of the symbols which may be needed to describe
situations and layouts in railway operation.

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

Types and format

</td>  
<td>

TeX, TikZ, pdf, png

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

Reuse of existing data

</td>  
<td>

\-

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

Origin of data

</td>  
<td>

own work

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

Expected size of data

</td>  
<td>

Less than 50 MB

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

Data utility

</td>  
<td>

Useful for anyone working on railway signalling engineering and operations,
accessible via CTAN (Comprehensive TEX Archive Network) under an ISC license
at  _https://ctan.org/pkg/tikz-trackschematic_

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

**WP 2 (UoB)**

</th>  
<th>

**Stakeholders requirements data**

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

Purpose

</td>  
<td>

The data supports the identification of gaps in ETCS Level 3 testing, current
issues and requirements needed for an effective system testing, validation and
certification.

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

Types and format

</td>  
<td>

PDF questionnaires and PDF survey results

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

Reuse of existing data

</td>  
<td>

\-

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

Origin of data

</td>  
<td>

The data derives from questionnaires made originally on paper in a workshop
and then aggregated and anonymized.

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

Expected size of data

</td>  
<td>

Less than 100 MB

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

Data utility

</td>  
<td>

The data can be used for developing operational concepts and testing
strategies for the verification and validation of moving block signalling
systems that draws on best practice and meets all stakeholder requirements. It
is available at
_https://beardatashare.bham.ac.uk/getlink/fiNYac39GLAxPfS7s5WWRvi_

_9/_

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

**WP 3 (PARK)**

</td>  
<td>

**Stakeholders requirements data**

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

Purpose

</td>  
<td>

The data will establish and refine the communications requirements for Virtual
Coupling and the Performance of communications architectures and equipment’s
including developments relating to autonomously driven cars.

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

Types and format

</td>  
<td>

It is expected that the primary new data used in WP3 will be in the form of
textual requirements from stakeholders via questionnaires and workshops,
anonymized in accordance with GDPR.

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

Reuse of existing data

</td>  
<td>

It is expected that data will be received and shared from the complementary
projects (CONNECTA-2, X2RAIL-3) which will be in accordance with the
Collaboration Agreements. In addition, we will reuse data from the public
domain, and other data made available, from ASTRail, CONNECTA-1, ETALON,
IN2RAIL, MISTRAL, Roll2Rail, Safe4Rail1, Safe4Rail-2, X2RAIL-1-WP3, and
X2RAIL-2-WP3/4/5 projects are also expected to be of use to MOVINGRAIL WP3.

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

Origin of data

</td>  
<td>

Original research, industry, preceding and collaborating Shift2Rail projects.

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

Expected size of data

</td>  
<td>

Less than 1 GB

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

Data utility

</td>  
<td>

The data will be useful to the signalling industry to identify virtual
coupling technical communication requirements and solutions; review previous
studies and projects into virtual coupling; analyse solutions against
requirements for virtual coupling; investigate the application, solutions and
dynamics of automated car driving; and evaluate the applicability of
autonomous vehicles to the railway field.

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

**WP 3 (PARK)**

</td>  
<td>

**Requirements data**

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

Purpose

</td>  
<td>

The data will establish and refine the communications requirements for Virtual
Coupling and the Performance of communications architectures and equipment’s
including developments relating to autonomously driven cars.

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

Types and format

</td>  
<td>

Statistical performance data on communications systems.

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

Reuse of existing data

</td>  
<td>

It is expected that performance data will be subject to commercial

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

</td>  
<td>

confidentiality.

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

Origin of data

</td>  
<td>

Original research, industry, preceding and collaborating Shift2Rail projects.

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

Expected size of data

</td>  
<td>

Less than 100 MB

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

Data utility

</td>  
<td>

The data will be useful to the signalling industry to identify virtual
coupling technical communication requirements and solutions.

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

**WP 4 (TUD)**

</td>  
<td>

**Stated preference data from surveys and workshops**

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

Purpose

</td>  
<td>

The data supports the assessment of market potentials and impact assessment of
Virtual Coupling for different railway segments

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

Types and format

</td>  
<td>

Surveys from railway experts to gather feedback and opinions about actual
technological and operational feasibility of Virtual Coupling

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

Reuse of existing data

</td>  
<td>

Part of the information about operational scenarios from X2RAIL-3 WP6 & 7 will
be reused to make surveys to railway experts.

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

Origin of data

</td>  
<td>

The data will derive from surveys made originally on paper and then
electronically transferred to an Access database

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

Expected size of data

</td>  
<td>

Less than 1 GB

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

Data utility

</td>  
<td>

The data produced in WP4 will be useful to railway industry stakeholders,
academic researchers to assess feasibility and multidimensional impacts of
Virtual Coupling as well as to make predictions/plans about development and
implementation plans for such a technology. Furthermore it is useful to other
experts of the broader transport industry and statisticians to estimate
environmental repercussions that Virtual Coupling could have by potentially
attracting more passengers towards the railways.

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

**WP 4 (TUD)**

</td>  
<td>

**Simulation data**

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

Purpose

</td>  
<td>

Investigate applicability and impacts on safety, costs, and performance of
Virtual Coupling

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

Types and format

</td>  
<td>

Simulation data will have different formats, specifically .xslm (Excel), .csv
files, RailML, InfraAtlas and plain text files

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

Reuse of existing data

</td>  
<td>

Input data from railway traffic simulation models already built during other
national and international projects (e.g. ON-TIME) are expected to be re-used.

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

Origin of data

</td>  
<td>

Input and output of simulation models and multi-criteria analyses.

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

Expected size of data

</td>  
<td>

Less than 10 GB

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

Data utility

</td>  
<td>

The data produced in WP4 will be useful to railway industry stakeholders,
academic researchers to assess feasibility and multidimensional impacts of
Virtual Coupling as well as to make predictions/plans about development and
implementation plans for such a technology. Furthermore it is useful to other
experts of the broader transport industry and statisticians to estimate
environmental repercussions that Virtual Coupling could have by potentially
attracting more passengers towards the railways.

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

#  FAIR data

##  Making data findable, including provisions for metadata

The data will be securely stored at 4TU.Centre for Research, which is a
Trusted Digital Repository for technical-scientific research data in the
Netherlands that complies fully with H2020 requirements of making data
findable, accessible, interoperable and reusable (FAIR). See

_https://researchdata.4tu.nl/en/home/_

Data collections, processed data and data representations will be stored for
15 years after the end of the project. Research data that is not privacy
sensitive will be open access available through the data repository mentioned
above as far as this is compatible with and does not infringe IP requirements
of the partners. These data, including the metadata that ensures that others
can find and use the data, will be stored and made available in the TU Delft
data archive 4TU.ResearchData.

The Dublin Core ( _www.dublincore.org_ ) metadata standard will be adopted and
further information on the data will be delivered in file headers or in
separate documentation files. This also applies to documentation files (e.g.
reports) and other types of data including experimental data and input/output
tabular data for code training, testing and validation.

##  Making data openly accessible

Once scientific journal publications are published (in Open Access),
publishable data (according to the Consortium Agreement) will be publicly
archived for the long term via the 4TU.Centre for Research Data archive
(documentation, experimental data and tabular data), following their metadata
standards (Dublin Core). TUD researchers can upload up to 1 TB of data per
year free of charge. This should suffice for the data that will be archived
for the long term. The 4TU.Centre for Research Data Archive ensures data will
be well-preserved and findable in the long term (each uploaded dataset is
given a unique persistent digital identifier).

Open and standard formats will be preferred for archived data files (e.g.,
.csv, .txt). Proper documentation files will be delivered together with the
datasets in order to facilitate reuse of data.

##  Making data interoperable

All publishable data will be delivered in open and standard data formats.
Discipline specific metadata is currently under discussion. If applicable,
metadata will be delivered in XML format together with the data (depending on
the chosen format). Proper documentation (README) files will be delivered
accordingly. Tabular data will be archived with informative and explanatory
headers to facilitate data re-use and interoperability.

##  Increase data re-use (through clarifying licences)

All data that cannot be disclosed will be kept at the respective institutional
server for the long term (at least 4 years after the end of the project);
accessed only by team members within the institution, for auditing and
validation purposes. It is also acknowledged that, for some of the outcomes,
conditions for exploitation as stated in the Consortium Agreement may apply.

Since the results from this project will make a strong impact in the railway
sector, we find it is extremely important to share the data responsibly. Hence
datasets that will be open to the public will be released along the journal
scientific publications after proper discussion with partners. The datasets
will be published via repositories such as the 4TU.Centre for Research Data
Archive. In the same way, and in order to motivate re-use of data, the journal
articles associated to these datasets will be published in open access and/or
self-archived on the MOVINGRAIL website and subject repositories, following
the publisher’s self-archiving policies.

#  Allocation of resources

TUD researchers can upload up to 1 TB of data to the 4TU.Centre for Research
Data Archive (per year) free of charge. Also, the storage capacity and
privately accessed drives managed by each partner are already available.

For internal document sharing between partners we make use of SURFdrive, a
password protected cloud storage service. Each TUD staff member may use
SURFdrive (100 GB storage, access via institutional account). The SURFdrive is
shared between all MOVINGRAIL partners.

The WP leaders are in charge of the management of the data from their work
package.  
  
<table>  
<tr>  
<th>

**Work package**

</th>  
<th>

**Responsible partner**

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

**WP 1**

</td>  
<td>

TUBS

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

**WP 2**

</td>  
<td>

UoB

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

**WP 3**

</td>  
<td>

PARK

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

**WP 4**

</td>  
<td>

TUD

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

#  Data security

Some data will be processed in work laptops of research team members only when
allowed. Master copies will be kept at the drives of each respective
institution. The IT departments of each institution will maintain the data
regarding backups (redundancy) and secure storage (protected access to only
team members). Only team members within each institution will have access to
the data during the research project. Such data access will be set up by the
respective IT departments of each institution. The data that will remain close
to the public will be archived at each partner’s servers for at least 4 years
after the end of the project.

SURFdrive will be used for temporal data storage and for data sharing among
different partners coordinated by TUD (coordinator).

#  Ethical aspects

There are no ethical issues that have an impact on data sharing.

It is important to mention, in case there are ethics-related questions or
issues arising throughout the project, these will be reported to the
scientific coordinator and will be discussed accordingly among team members.
Extra advise can be discussed with the Human Research Ethics Committee of TUD
(at HREC@tudelft.nl).

#  Other

MOVINGRAIL will make use of the TUD Research Data Framework Policy which can
be found via
_https://www.tudelft.nl/en/2018/library/researchdatamanagement/tu-delft-
research-dataframework-policy-published/_

| 10