1\. Executive Summary

The aim of the Data Management Plan, in short DMP, is to manage data used and
generated within the TER4RAIL project. It describes how data  1  will be
collected, processed, stored and managed from the perspective of external
accessibility and long-term archiving. It takes account of the particular
characteristics of the TER4RAIL project, which has features such as diverse
data sources and formats and greater initial uncertainties typical of
coordination and support actions. The DMP is therefore designed for
flexibility to meet emerging needs.

The DMP supports a project which has as its principal aims the establishment
of a research observatory for rail, the correlation of its outputs with
existing roadmaps so they may be improved and updated and setting out the key
argument for the use of rail as the backbone of European mobility.

More precisely, the DMP addresses the following points for each of the
project’s Work Packages:

  1. Type of data to be utilised and generated within TER4RAIL. This section identifies and describes the (existing) input data that will be utilised and the output data to be generated by the project. 

  

  2. Standards to be used, metadata and quality issues. GDPR and compliance issues are covered as appropriate. 

  

  3. How data are exploited and shared/accessed for their verification and reutilisation. The exploitation of data will follow the strategies of each partner concerning their business potential, in accordance to the exploitation plan produced in WP4, and in accordance to the access to data by the partners specified in the Consortium Agreement. Specific restrictions and confidentiality aspects are clarified. 

  

  4. Data storage and conservation. Where the data will be held and the arrangements and responsibilities for managing, updating and maintaining the data. 

  

  

  2. Abbreviations and acronyms 

  

  
  
<table>  
<tr>  
<th>

**Abbreviation / Acronyms**

</th>  
<th>

**Description**

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

CSA

</td>  
<td>

Coordination and Support Actions

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

DMP

</td>  
<td>

Data Management Plan

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

ERRAC

</td>  
<td>

European Railway Research Advisory Council’s

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

EU

</td>  
<td>

European Union

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

GDPR

</td>  
<td>

General Data Protection Regulation

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

JU

</td>  
<td>

Joint Undertaking

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

MAAP

</td>  
<td>

Multi Annual Action Plan

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

NA

</td>  
<td>

Not Applicable

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

R&D

</td>  
<td>

Research and development

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

S2R

</td>  
<td>

Shift2Rail

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

UIC

</td>  
<td>

Union Internationale des Chemins de Fer

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

WP

</td>  
<td>

Work Package

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

  3. Background 

  

  

This document constitutes the Deliverable D4.2 “Data Management Plan” for the
TER4RAIL project, a 24-month coordination and support action for transversal
exploratory research activities to benefit the railways, within the overall
framework of Shift2Rail, which is developing the fundamental building blocks
that will allow the creation of the future railway interoperable system.

The DMP supports TER4RAIL’s principal aims - the establishment of a research
observatory for rail, the correlation of its outputs with existing roadmaps so
they may be improved and updated and setting out the key argument for the use
of rail as the backbone of European mobility.

The DMP is a vital management tool, particularly as the project has seven
partners from five countries and different disciplines, and the project has a
particularly wide field of activity.

The partners recognise the challenges of this type of project for data
management, so have committed themselves to devising and honouring a formal
process to ensure the data are managed and maintained in a way which will
mitigate the complexity and diversity of the data sources and ensure an
efficient and sustainable process to deliver the project objectives and the
ongoing usefulness of its products for the success of the rail sector and its
contribution to delivering S2R’s wider social, economic and environmental
objectives.

4\. Objective

This 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. 826055, 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:

TER4RAIL entails a coordination and support action to determine transversal
exploratory research activities among different actors that are beneficial for
railways. The Shift2Rail Multi Annual Action Plan (MAAP) will play a central
role in the establishment of future interoperable railway systems suitable for
European society and environment. However, due to the rapid pace of
technological change and innovation, it is necessary to be aware of the novel
possibilities that can enable an increasingly sustainable progress in this
regard.

Additionally, the European railway community is represented by different
actors (industry, academia, users, researchers, and policy makers) with
different perceptions regarding technological applications and different
objectives for the future.

With regard to this context, the work of TER4RAIL is organised as follows:

  * TER4RAIL will identify and monitor new opportunities for innovative research and facilitate the cross-fertilisation of knowledge from other disciplines, at what is referred to as the Rail Innovative Research Observatory. Permanent contact with other relevant sectors will have a prominent role in importing disruptive perspectives from other disciplines and facilitating interactions. 

  

  * TER4RAIL will determine and assess the existing roadmaps that drive the future of railways and compare them with the interpretations obtained from the observatory. This analysis will indicate the gaps that require to be covered and serve as the anchor for the prospective roadmaps, among others, the Shift2Rail MAAP. 

  

  * TER4RAIL considers railways as the backbone of future European mobility, as stated in the rail sector’s European Railway Research Advisory Council’s (ERRAC) Rail 2050 Vision published in December 2017, and therefore, it is necessary that TER4RAIL raise arguments that can sustain this essential system. To that end, data analysis and statistical reporting are foreseen and conducted. 

  

  * Finally, the work performed under TER4RAIL will be communicated to the transport community, liaising with the Shift2Rail communication team with a correlated communication strategy. A strategy of exploitation of the results will guarantee that these are properly employed in this area with maximum impact. 

  

  * TER4RAIL will be able to select and synthetise a considerable amount of information regarding railways’ futures and transmit them in a consolidated, improved, clear, and understandable manner. This should facilitate the realisation of TER4RAIL’s ambition of being the CSA of reference for the evolution of EU railways. 

  

The WPs will address the following areas:

  * WP1: Rail Innovative Research Observatory 

  

  * WP2: Roadmaps 

  

  * WP3: Arguments supporting rail 

  

  * WP4: Work package title Dissemination, exploitation, and knowledge transfer  WP5: Coordination and management 

  

5\. Data Management at Project Level

###  5.1. Data Collection

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

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

All modifications and additions to the DMP shall be provided to the TER4RAIL
Data Manager Coordinator, UIC, for inclusion in the DMP. Each WP Leader is
responsible for the quality and completeness of the datasets related to its
work package: the quality check will be done at WP level by the WP leader as
some of the data will have to be pre-worked and validated by the WP leader
having the only access to the corresponding raw data (for instance case of
survey data to be anonymized / aggregated before being communicated to other
partners).

###  5.2. Data Archiving & Preservation

A Workflow Tool platform was created to support the work of the consortium
members. The partners have received a link with an invitation to access to the
platform.

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

####  5.2.1. Data Security and Integrity

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.

All the partners invited to the platform have the same publication rights.
These rights include viewing, modificating or creating new documents. All
members of the project have access to all documents and meetings in the tool.

The internal structure of the five WP folders will be determined by the Work
Package Leader. The Project Coordinator has overall project administration
rights, enabling to administrate the complete project document database.

Uploaded data to the Workflow Tool are protected against disturbances and
possible loss of data in the server. As backup, all the information is also
stored in the hard disk of four different computers in EURNEX headquarters.

####  5.2.2. 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 EURNEX
within 12 weeks of the formal closure of the TER4RAIL project. Data will be
copied and transferred to a digital repository provided by EURNEX.

###  5.3. Computer file formats

To ensure document compatibility, the following file formats should be used:

  * WORD version Microsoft Office 2007 or higher (including the OOXML and ODT formats) for documents; 

  

  * EXCEL version Microsoft Office 2007 or higher (including the OOXML and ODT formats) OR 

  

Commas Separated Value format (CSV) for spreadsheets and databases;

  * PowerPoint version Microsoft Office 2007 or higher (including the OOXML and ODT formats) for overhead slides; 

  

  * PDF for consolidated releases of project documents; 

  

  * ZIP for compressed documents; 

  

  * JPEG/PNG for pictures; 

  

  * AVI or MPEG-4 for videos; 

  

  * MP3 or MPEG-4 for audio 

  

For any other cases, the Mendeley Open Data platform will be applied:
_https://data.mendeley.com/file-formats_ .

###  5.4. File Naming Conventions

Documents produced during the project and uploaded to the Workflow Tool will
be assigned a unique document code.

####  5.4.1. Document code structure

The identification code contains the five following sections:

**[Project] - [Domain] - [Type] - [Filename] - [Version]**

  * [Project] is T4R for all TER4RAIL documents; 

  

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

  

  * [Type] is one or two letters defining the document category, with the addition of a 1 to 3 digits code (such as deliverable number as stated in the Grant Agreement, or such as dataset number as stated in this Data Management Plan);  [Filename] is a short description of the document;  [Version] is a version number starting at 001. 

  

Examples:  
  
<table>  
<tr>  
<th>

**PROJECT CODE**

</th>  
<th>

**-**

</th>  
<th>

**DOMAIN**

**(3-4 letters)**

</th>  
<th>

**-**

</th>  
<th>

**TYPE**

**(1-2 letters)**

**\+ if applicable:**

**CODE**

**(1-3 digits)**

</th>  
<th>

**-**

</th>  
<th>

**FILENAME**

**(n letters)**

</th>  
<th>

**-**

</th>  
<th>

**Version**

**(3 digits)**

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

T4R

</td>  
<td>

\-

</td>  
<td>

SC

</td>  
<td>

\-

</td>  
<td>

MA

</td>  
<td>

\-

</td>  
<td>

5th_April_2019_Minutes

</td>  
<td>

\-

</td>  
<td>

002

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

T4R

</td>  
<td>

\-

</td>  
<td>

WP1

</td>  
<td>

\-

</td>  
<td>

P

</td>  
<td>

\-

</td>  
<td>

1st_Periodic_Report

</td>  
<td>

\-

</td>  
<td>

001

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

T4R

</td>  
<td>

\-

</td>  
<td>

WP1

</td>  
<td>

\-

</td>  
<td>

D1.1

</td>  
<td>

\-

</td>  
<td>

Mapping

</td>  
<td>

\-

</td>  
<td>

001

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

T4R

</td>  
<td>

\-

</td>  
<td>

WP1

</td>  
<td>

\-

</td>  
<td>

DA1.1

</td>  
<td>

\-

</td>  
<td>

List_of_Key_Documents

</td>  
<td>

\-

</td>  
<td>

001

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

Table 1 - Examples of file naming

####  5.4.2. Document types

This information will be used to set up the identification code.

Documents are classified among the following types:  
  
<table>  
<tr>  
<th>

**Letter**

</th>  
<th>

**Name**

</th>  
<th>

**Description**

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

A

</td>  
<td>

Administrative

</td>  
<td>

Any administrative document except contractual documents

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

C

</td>  
<td>

Contractual document

</td>  
<td>

Consortium Agreement, Grant Agreement and their approved amendments

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

D

</td>  
<td>

Deliverable

</td>  
<td>

Deliverable identified as such under the Grant Agreement

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

DA

</td>  
<td>

Dataset

</td>  
<td>

Dataset identified as such in the Data Management Plan

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

EC

</td>  
<td>

EC document

</td>  
<td>

Document provided by EC (general rules, guidelines or EC experts documents)

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

M

</td>  
<td>

Model

(template)

</td>  
<td>

MS-Office document templates including TER4RAIL visual identity

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

MA

</td>  
<td>

Meeting Agenda

</td>  
<td>

Meeting Agenda

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

MI

</td>  
<td>

Minutes

</td>  
<td>

Minutes

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

P

</td>  
<td>

Periodic Report

</td>  
<td>

All intermediate/periodic reports except those listed as deliverables. May be
a WP intermediate report or a project intermediate report requested by the
Grant Agreement but not listed as deliverable.

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

PR

</td>  
<td>

Presentation

</td>  
<td>

Presentation

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

T

</td>  
<td>

Technical contribution

</td>  
<td>

Technical document contributing to a task/deliverable but not part of the
deliverable

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

W

</td>  
<td>

Proposal

</td>  
<td>

Proposal for changes to the Consortium Agreement or Grant Agreement

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

X

</td>  
<td>

External document

</td>  
<td>

Document produced by non-members of the project (e.g. papers, reports,
external public deliverables, etc.) that, upon authorisation of the author(s),
are

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

</td>  
<td>

</td>  
<td>

shared with the project due to its relevancy.

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

Table 2 - Document types

###  5.5. Data and Shift2Rail

The TER4RAIL 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.

6\. DMP of WP1: Rail Innovative Research Observatory

###  6.1. 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>

T4R-WP1-DA1.1

</td>  
<td>

List of Rail R&D key documents

</td>  
<td>

EXCEL

</td>  
<td>

21KB

</td>  
<td>

FFE

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

T4R-WP1-DA1.2

</td>  
<td>

Folder containing the public documents of the list of Rail R&D key documents

</td>  
<td>

PDF + ZIP

</td>  
<td>

\-

</td>  
<td>

FFE

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

T4R-WP1-DA1.3

</td>  
<td>

Folder with the confidential documents of the list of Rail R&D key documents
(#6 and #23): #6 is the “Capabilities and

areas of development” of UIC and #23 is “MAIN PUBLIC TRANSPORT TRENDS &
DEVELOPMENTS OUTSIDE EUROPE” from the UITP.

</td>  
<td>

PDF + ZIP

</td>  
<td>

\-

</td>  
<td>

FFE

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

T4R-WP1-DA1.4

</td>  
<td>

Rail stakeholders survey: answers provided at SurveyMonkey – nonpersonal
information

</td>  
<td>

EXCEL

</td>  
<td>

\-

</td>  
<td>

FFE

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

T4R-WP1-DA1.5

</td>  
<td>

Rail stakeholders survey: answers provided at SurveyMonkey – personal
information: results of Q#33 (Would you like to keep in touch regarding
TER4RAIL activities? If so, feel free to leave here you name and contact
details). Question is accompanied by information concerning the GDPR
compliance.

</td>  
<td>

EXCEL

</td>  
<td>

.

</td>  
<td>

FFE

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

T4R-WP1-DA1.6

</td>  
<td>

Rail stakeholders survey: aggregated answers – result of analysis: included
inside D.1.1.

</td>  
<td>

PDF

</td>  
<td>

\-

</td>  
<td>

FFE

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

T4R-WP1-DA1.7

</td>  
<td>

Database of rail related projects financed under H2020

</td>  
<td>

EXCEL

</td>  
<td>

\-

</td>  
<td>

FFE

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

T4R-WP1-DA1.8

</td>  
<td>

Shift2Rail specific questionnaire / interview

</td>  
<td>

WORD

</td>  
<td>

\-

</td>  
<td>

FFE

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

Table 3 - Existing Data used in WP1

Regarding the “Rail stakeholders survey” (1.4. and 1.5.), the following
statement was included at the beginning of the questionnaire “Answers will be
treated confidentially and results will be aggregated”, making the
participants aware of the treatment and use of their answers. The survey
includes only one question affected to the GDPR law Q#33. Before answering
this question, the applicable data protection terms and conditions were
presented  2  and the participants had to agree in order to provide an answer.
In case of disagreeing they were not able to answer Q#33.

In case additional data will be generated in this WP, additions to the DMP
will be made.

6.2. Standards, Metadata and Quality Issues

Not applicable.

###  6.3. Data Sharing  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

T4R-WP1-DA1.1

</td>  
<td>

Publicly available. Included in M.S. 1, D.1.1., shared with other projects /
stakeholders that may have interest (so far: FLEX4RAIL project)

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

T4R-WP1-DA1.2

</td>  
<td>

Can be shared with any stakeholder interested in it.

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

T4R-WP1-DA1.3

</td>  
<td>

Restricted only to Project partners.

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

T4R-WP1-DA1.4

</td>  
<td>

Not shared. It will be stored at FFE’s internal servers and used only for the
generation of D.1.1., elaborating aggregated analysis.

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

T4R-WP1-DA1.5

</td>  
<td>

Not shared. It will be stored at FFE’s internal servers according to the Data
Protection Law applicable  2  . Consent with this data protection law terms
has been asked as a requirement for answering this question.

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

T4R-WP1-DA1.6

</td>  
<td>

Publicly available. Included in D.1.1.

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

T4R-WP1-DA1.7

</td>  
<td>

Publicly available. Available at TER4RAIL website, emails to all interested
stakeholders requesting it (e.g. so far FLEX4RAIL, ERRAC WG2, Shift2Rail
Secretariat.

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

T4R-WP1-DA1.8

</td>  
<td>

Confidential. Q3, Q4, Q5 and Q15 may be incorporated to the aggregated results
of the online survey in an anonymous way. Q8, Q9, Q10, Q17 will be shared with
projects partners as input for T.1.2. The complete questionnaire will not be
shared. It will be stored at FFE’s internal servers and used internally to
align WP1’s activities.

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

Table 4 - Data Sharing in WP1

2 The data provided under Q#33 will be stored and controlled by Fundación de
los Ferrocarriles

Españoles (FFE) in compliance with the information set out in the Act 3/2018
on the Personal Data Protection and Guarantee of Digital Rights and the
provisions of the General Data Protection Regulation (Regulation (EU) 2016/679
of 27 April 2016), applying GDPR 6.1.a) The data subject has given consent to
the processing of his or her personal data for one or more specific purposes,
with the objective to contact you in case of requests for further information
on the topics addressed by this questionnaire or distribution of results and
information from TER4RAIL project. Personal data will not be published, nor
shared with third parties unless legal obligation. For further information, or
making use of your rights, please consult:
_https://www.ffe.es/fundacion/aviso_legal_en.htm_ .

###  6.4. Archiving and Preservation  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

T4R-WP1-DA1.1

</td>  
<td>

Workflow Tool Project folders. It can be archived and preserved.

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

T4R-WP1-DA1.2

</td>  
<td>

Workflow Tool Project folders. It can be archived and preserved.

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

T4R-WP1-DA1.3

</td>  
<td>

Workflow Tool Project folders only accessible to project partners. It will be
deleted once the project ends.

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

T4R-WP1-DA1.4

</td>  
<td>

FFE internal servers. It will be deleted once the project ends.

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

T4R-WP1-DA1.5

</td>  
<td>

FFE internal servers. It will be deleted once the project ends.

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

T4R-WP1-DA1.6

</td>  
<td>

Included in D1.1. Publicly available at the project web. It can be archived
and preserved.

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

T4R-WP1-DA1.7

</td>  
<td>

Workflow Tool Project folders and project web. It can be archived and
preserved.

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

T4R-WP1-DA1.8

</td>  
<td>

FFE internal servers. It will be deleted once the project ends.

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

Table 5 - Archiving and preservation of the data in WP1

###  6.5. Data Management Responsibilities  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

T4R-WP1-DA1.1

</td>  
<td>

EURNEX

</td>  
<td>

Manages project Workflow Tool folders

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

T4R-WP1-DA1.2

</td>  
<td>

EURNEX

</td>  
<td>

Manages project Workflow Tool folders

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

T4R-WP1-DA1.3

</td>  
<td>

EURNEX

</td>  
<td>

Manages project Workflow Tool folders

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

T4R-WP1-DA1.4

</td>  
<td>

FFE

</td>  
<td>

Stores and guards the data

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

T4R-WP1-DA1.5

</td>  
<td>

FFE

</td>  
<td>

Stores and guards the data

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

T4R-WP1-DA1.6

</td>  
<td>

EURNEX

</td>  
<td>

Manages project Workflow Tool folders

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

T4R-WP1-DA1.7

</td>  
<td>

EURNEX / UIC

</td>  
<td>

Manages project Workflow Tool folders / manages website

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

T4R-WP1-DA1.8

</td>  
<td>

FFE

</td>  
<td>

Stores and guards the data

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

Table 6 - Data Management Responsibilities in WP1

7\. DMP of WP2: Roadmaps

###  7.1. 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>

T4R-WP2-DA2.1

</td>  
<td>

SurveyMonkey Delphi Survey Round 1 responses

</td>  
<td>

Qualitative and

Quantitative data

</td>  
<td>

Unknown at this stage, likely to be

<100mb

</td>  
<td>

UNEW: Thomas Zunder

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

T4R-WP2-DA2.2

</td>  
<td>

SurveyMonkey Delphi Survey Round 2 responses

</td>  
<td>

Qualitative and

Quantitative data

</td>  
<td>

Unknown at this stage, likely to be

<100mb

</td>  
<td>

UNEW: Thomas Zunder

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

T4R-WP2-DA2.3

</td>  
<td>

TER4RAIL Webinars

</td>  
<td>

Video data, usually

MPEG-4

</td>  
<td>

Unknown at this stage but likely to

be >1Gb

</td>  
<td>

UNEW: Thomas Zunder

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

Table 7 - Existing Data used in WP2

The participants in the Delphi Survey are asked to give explicit consent for
the use of their responses by agreeing to the following statement by
explicitly opting-in. If they choose to not opt-in then the survey ends. This
is fully compliant with the GDPR.

Welcome to TER4RAIL Delphi survey round 1.

[You may wish to maximise this browser window.]

The main objective of TER4RAIL is to reinforce the cooperation between rail-
related stakeholders to improve the efficiency of the research in the rail
sector, in order to facilitate emerging innovative ideas and the cross-
fertilisation of knowledge from other disciplines or of disruptive technology
and innovation. TER4RAIL intends to promote this process by strengthening
transversal exploratory research in Europe for and with a railways perspective
in the frame of multimodality.

The objective of this Delphi survey is to review, support, and improve the
sector roadmaps, in preparation for the next iteration of the roadmapping
process in the railway sector, considering multimodal environments and railway
as the backbone of mobility in the future;

This is the first round questionnaire of the Delphi survey. Your contribution
to the first round will be used to develop a second round questionnaire. We
are therefore interested in broad answers.

Please expand upon your answers whenever appropriate.  
  
<table>  
<tr>  
<th>

Your opinions expressed in this survey are 'personal to you as an expert'. We
understand that they do not necessarily represent the opinions or policy of
your organisation and will not be used as such. Your response will be treated
in strict confidence, and names of individual respondents or organisations
will not be used in published material or given to third parties. The general
findings of the survey will be published. If you participate in the survey and
enter an email address, a copy of the result will be emailed to you.

Thank you,

If you have queries then please do not hesitate to contact: Thomas Zunder,
tom.zunder@ncl.ac.uk

Newcastle University

Stephenson Building

Newcastle upon Tyne

NE1 7RU

United Kingdom

Data Protection and Privacy Terms

we will process all personal data fairly and lawfully

we will only process personal data for specified and lawful purposes

we will endeavour to hold relevant and accurate personal data, and where
practical, we will keep it up to date

we will not keep personal data for longer than is necessary we will keep all
personal data secure

we will endeavour to ensure that personal data is not transferred to countries
outside of the

European Economic Area (EEA) without adequate protection

We would like to assure you that your opinion will be held anonymously and
securely. Personal data is asked for and retained for the purpose of the
survey but will not be published or used in an identifiable manner. Survey
results and feedback will be analysed and stored securely within Newcastle
University as well as on SurveyMonkey servers. The anonymised data and results
will be made available publicly.

Since data will be held on SurveyMonkey then the SurveyMonkey Privacy Policy
will apply, please refer to and read policy here:
_https://www.surveymonkey.com/mp/legal/privacy-policy/_

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

Note that data may be transferred out of the EU as part of the SurveyMonkey
Privacy Policy, see above.

Do you consent to the Data Protection and Privacy Terms above?

Yes No

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

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

###  7.2. Standards, Metadata and Quality Issues

The following standards and metadata are planned to be used for data related
to WP2: Compliance with GDPR. All participants are to be clearly advised of
the privacy policy and the nature of sharing.

###  7.3. Data Sharing  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

T4R-WP2-DA2.1

</td>  
<td>

Shared within consortium and to public as anonymised data and summaries only.

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

T4R-WP2-DA2.2

</td>  
<td>

Shared within consortium and to public as anonymised data and summaries only.

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

T4R-WP2-DA2.3

</td>  
<td>

Shared with public on VIMEO video sharing platform and embedded in TER4RAIL
website.

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

Table 8 - Data Sharing in WP2

###  7.4. Archiving and Preservation  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

T4R-WP2-DA2.1

</td>  
<td>

Stored on SurveyMonkey and on Newcastle University secure and password
protected servers. To be shared using the Mendeley open data platform:
_https://data.mendeley.com_ .  
</td> </tr>  
<tr>  
<td>

T4R-WP2-DA2.2

</td>  
<td>

Stored on SurveyMonkey and on Newcastle University secure and password
protected servers. To be shared using the Mendeley open data platform:
_https://data.mendeley.com_ .  
</td> </tr>  
<tr>  
<td>

T4R-WP2-DA2.3

</td>  
<td>

Stored on Newcastle University secure and password protected servers and VIMEO
video sharing platform as well as embedded into TER4RAIL website.

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

Table 9 - Archiving and preservation of the data in WP2

###  7.5. Data Management Responsibilities  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

T4R-WP2-DA2.1

</td>  
<td>

UNEW: Thomas Zunder

</td>  
<td>

Principal Research Associate

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

T4R-WP2-DA2.2

</td>  
<td>

UNEW: Thomas Zunder

</td>  
<td>

Principal Research Associate

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

T4R-WP2-DA2.3

</td>  
<td>

UNEW: Thomas Zunder

</td>  
<td>

Principal Research Associate

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

Table 10 - Data Management Responsibilities in WP2

8\. DMP of WP3: Arguments supporting rail

###  8.1. 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>

T4R-WP3-DA3.1

</td>  
<td>

Collection and description of tables, graphs, charts, statistics regarding
rail and non-rail transport, summarized in a descriptive report.

</td>  
<td>

Word,

Excel, PDF, images/ta bles/chart s in JPG,

PNG

format

</td>  
<td>

Variable

</td>  
<td>

Consortia members. All sources/references are properly quoted. The results of
the

deliverables also belong to European

Commission and S2R JU.

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

T4R-WP3-DA3.2

</td>  
<td>

Report summarizing analysis and comments to the data collected in 3.1, also
providing insights on bottlenecks and gaps elimination.

</td>  
<td>

Word, PDF, images/ta bles/chart s in JPG,

PNG

format

</td>  
<td>

Variable

</td>  
<td>

Consortia members. All sources/references are properly quoted. The results of
the

deliverables also belong to European

Commission and S2R JU.

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

T4R-WP3-DA3.3

</td>  
<td>

Description of success stories regarding rail, summarized in a handbook.

</td>  
<td>

Word, PDF, images/ta bles/chart s in JPG,

PNG

format

</td>  
<td>

Variable

</td>  
<td>

Consortia members. All sources/references are properly quoted. The results of
the

deliverables also belong to European

Commission and S2R JU.

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

Table 11 - Existing Data used in WP3

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

8.2. Standards, Metadata and Quality Issues

Not applicable.

###  8.3. Data Sharing  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

T4R-WP3-DA3.1

</td>  
<td>

Deliverable will be public

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

T4R-WP3-DA3.2

</td>  
<td>

Deliverable will be public

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

T4R-WP3-DA3.3

</td>  
<td>

Deliverable will be public

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

Table 12 - Data Sharing in WP3

###  8.4. Archiving and Preservation  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

T4R-WP3-DA3.1

</td>  
<td>

All documents/data utilized as “sources” for producing the deliverables will
be stored in NEW OPERA archive. Deliverables and other public documents will
be uploaded on the Workflow Tool for consultation.

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

T4R-WP3-DA3.2

</td>  
<td>

All documents/data utilized as “sources” for producing the deliverables will
be stored in NEW OPERA archive. Deliverables and other public documents will
be uploaded on the Workflow Tool for consultation.

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

T4R-WP3-DA3.3

</td>  
<td>

All documents/data utilized as “sources” for producing the deliverables will
be stored in NEW OPERA archive. Deliverables and other public documents will
be uploaded on the Workflow Tool for consultation.

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

Table 13 - Archiving and preservation of the data in WP3

###  8.5. Data Management Responsibilities  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

T4R-WP3-DA3.1

</td>  
<td>

Giuseppe Rizzi (NEW OPERA)

</td>  
<td>

Update and maintenance of the data

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

T4R-WP3-DA3.2

</td>  
<td>

Giuseppe Rizzi (NEW OPERA)

</td>  
<td>

Update and maintenance of the data

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

T4R-WP3-DA3.3

</td>  
<td>

Daria Kuzmina (UITP)

</td>  
<td>

Update and maintenance of the data

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

Table 14 - Data Management Responsibilities in WP3

9\. DMP of WP4: Work package title Dissemination, exploitation, and knowledge
transfer

###  9.1. 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>

T4R-WP4-DA4.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

EURNEX as coordinator and to UIC as WP leader to use images for dissemination
purposes of TER4RAIL.

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

T4R-WP4-DA4.2

</td>  
<td>

Contact information of persons who have

registered for the final conference

</td>  
<td>

html format

</td>  
<td>

Variable

</td>  
<td>

The data will be collected and processed 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 15 - Existing Data used in WP4

No additional data are planned to be generated in this work package.

###  9.2. Standards, Metadata and Quality Issues

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

###  9.3. Data Sharing  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

T4R-WP4-DA4.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>

T4R-WP4-DA4.2

</td>  
<td>

The data will be collected and processed by UIC only for the logistics purpose
of the final conference and will not be shared outside the consortium.

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

Table 16 - Data Sharing in WP4

##  9.4. Archiving and Preservation  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

T4R-WP4-DA4.1

</td>  
<td>

Data will be stored in the Workflow Tool

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

T4R-WP4-DA4.2

</td>  
<td>

Data will be stored on UIC servers

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

Table 17 Archiving and preservation of the data in WP4

##  9.5. Data Management Responsibilities  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

T4R-WP4-DA4.1

</td>  
<td>

Christine HASSOUN (UIC)

</td>  
<td>

Update and maintenance of the data

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

T4R-WP4-DA4.2

</td>  
<td>

Christine HASSOUN (UIC)

</td>  
<td>

Update and maintenance of the data

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

Table 18 - Data Management Responsibilities in WP4

#  DMP of WP5: Coordination and 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>

T4R-WP5-DA5.1

</td>  
<td>

Consortium partners data (Telephone number, email, name, company/institution)

</td>  
<td>

.xlsx

</td>  
<td>

Small

</td>  
<td>

Consortium members

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

T4R-WP5-DA5.2

</td>  
<td>

Candidates for the

Stakeholders Reference Group (Name, company/institution), email)

</td>  
<td>

.xlsx

</td>  
<td>

Small

</td>  
<td>

Consortium members

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

Table 19 - Existing Data used in WP5

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

##  Standards, Metadata and Quality Issues

Not applicable.

##  Data Sharing  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Sharing**

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

T4R-WP5-DA5.1

</td>  
<td>

Access granted only to consortium partners

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

T4R-WP5-DA5.2

</td>  
<td>

Access granted only to consortium partners

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

Table 20 - Data Sharing in WP5

##  Archiving and Preservation  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

T4R-WP5-DA5.1

</td>  
<td>

The data will be erased after the end of the project

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

T4R-WP5-DA5.2

</td>  
<td>

The data will be erased after the end of the project

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

Table 21 - Archiving and preservation of the data in WP5

##  Data Management Responsibilities  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

T4R-WP5-DA5.1

</td>  
<td>

Armando Carrillo (EURNEX)

</td>  
<td>

Update, maintenance and subsequent erasure of the data

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

T4R-WP5-DA5.2

</td>  
<td>

Armando Carrillo (EURNEX)

</td>  
<td>

Update, maintenance and subsequent erasure of the data

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

Table 22 - Data Management Responsibilities in WP5

#  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
TER4RAIL project. For this particular project, the DMP is more important than
usual because data are at the heart of delivering the outputs and they are to
be sourced from a diverse range of origins.

The DMP is not intended to be a static document but is designed to allow for
its own evolution during the lifespan of the project to take account of
emerging needs. This flexibility is important because the transversal project
itself is far-reaching, with diverse and potentially complex data that are yet
to be identified. This document is therefore expected to mature during the
project; more developed versions of the plan could be included as additional
revisions of this deliverable at later stages. The DMP will be updated at
least after the mid-term and final reviews to finetune 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.