#  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 will be curated and preserved. This document
should be considered in combination with:

  * Articles 9.1, 9.2, 9.3 and attachment 1 of the Consortium Agreement. 

  

  * Section 3 (Articles 23, 24, 25, 26, 27, 28, 29, 30 and 31) of the Grant Agreement No. 826098 

  

The DMP is organised per project WP in order to concretely describe the
contribution of each WP to the final outcome as well as the spin-off potential
of each activity.

In order to understand the data of the project a brief overview of the project
is given below.

##  CONNECTA-2 PROJECT OVERVIEW

CONNECTA-2 aims at contributing to the Shift2Rail’s next generation of TCMS
architectures and components with wireless capabilities. The research and
development work will address the second phase of activities of the Shift2Rail
Multi-Annual Action Plan (MAAP) on TD1.2 – TD Next Generation TCMS to reach
higher TRL (up to TRL5 expected).

This proposal covers the implementation of the new technological concepts,
standard specifications and architectures for the train control and monitoring
defined within CONNECTA-1 project. The project will be developed in five main
blocks of work which will both reinforce and extend the early work done in the
previous project. These blocks are described below.

  * A transversal common block to continue the research in basic technologies for wireless communications, produce new application profiles, explore new solutions for the humanmachine interface (HMI) and complete potential open points left at the end of CONNECTA1 (WP1, WP2). 

  

  * A second transversal block for implementing the technologies as defined in CONNECTA-1 (WP3) while defining the testing procedures (WP3, WP4). 

  

  * A vertical block for deploying and testing technologies in an urban (heavy metro) laboratory environment (WP5). 

  

  * A second vertical block, running in parallel, for deploying and testing technologies in a mainline (regional) laboratory environment (WP6). 

  

  * A project wide block to evaluate results (including KPI assessment), disseminate, communicate and exploit (WP7, WP8) as much as possible at this TRL5 level of achievements. 

  

CONNECTA-2 will be divided into eight work packages (WP). Each WP contributes
to the scope of the call S2R-CFM-IP1-02-2018. Figure 1: shows the organisation
of the project.

**Figure 1: Project structure** The goals of each WP are described below:

  * **WP1:** First topic is focusing on new technologies needed for the technical WPs of the project. These specifications will define the technologies to be implemented and integrated in the urban and/or regional demonstrators such as the new Wireless TCMS communications. Additionally, this WP will work in the definition of the Application Profile for ATO in collaboration with TD2.2. This WP will also support the definition of functions for DMI standardization and the completion of the Functional Open Coupling regarding the input and output needed for DMI visualization. 

  

  * **WP2:** It is working on implementation of the evolved Train-to-ground specified in WP1 (new functions of the IEC 61375-2-6) and further Application Profiles which will run on top of the FDF deployed in demonstrators. Further on members will be expected to participate together in interoperability tests of the IEC 61375-2-6 to be carried out in the laboratory and the demonstrator. Additionally, this WP will work together with the X2Rail-1 project from IP2 to extend the IEC 61375-2-6 architecture to the “Adaptable Communication” concept coming from that project to allow reusing the radio carriers used by signaling applications by TCMS train-to-ground applications. 

  

  * **WP3:** Is specifying and implementing components for laboratory demonstrators corresponding to two different application fields: a regional (train) demonstrator and an urban (train) demonstrator. Those demonstrators shall be used in subsequent WPs to provide a proof-of-concept of those technologies which have been investigated and selected during Connecta-1 and the Roll2Rail Lighthouse project, namely the wireless consist network and train to wayside communication, Drive-by-Data, Function Distribution Framework and Functional Open Coupling. The simulation framework defined in Connecta1 will be used for sub-system simulation. 

  

  * **WP4:** Is defining test cases and test scenarios in order to demonstrate the correct integration of the different technologies and architectures specified and implemented in WP3. These test specifications will be accomplished for both urban and regional laboratory demonstrators, with a view to testing the wireless train backbone and consist network, trainto-ground communication, Drive-By-Data solution, the integration of Application Profiles implemented in the Functional Distribution Framework, Functional Open Coupling functionality and Virtual Homologation Framework. 

  

  * **WP5:** Is integrating the set of components developed in WP3 in a laboratory demonstrator for an urban train application, thus ensuring interoperability of technologies and architectures from different suppliers. Namely, the urban demonstrator will include the wireless train backbone, train-to-ground communication, Drive-By-Data, Functional Distribution Framework and Virtual Homologation Framework. For this purpose, a series of simulators and test tools will be implemented, and after test facilities have been prepared, the tests previously defined in WP4 will be finally executed and carefully evaluated to check the fulfilment of requirements. This demonstrator will be the basis for the future validation and later deployment on real vehicles. 

  

  * **WP6:** Is integrating and evaluating the outcome (technologies, architectures and components) of WP3 in a laboratory demonstrator for regional rail environment. Among others, the demonstrator will include the Functional Distribution Framework, drive-by-data solution and train-to-ground communication. Consists inside this demonstrator will be provided by different partners to prove that chosen concepts yields functional interoperability. 

  

  * **WP7:** Is seeking to ensure proper dissemination and promotion of the project results, in a way which is consistent with the wider dissemination and promotion activities of Shift2Rail. The objective is to ensure that the outputs of the project are delivered in a form which makes them immediately available for use by the complementary actions, and ensure that all important actors in the European railway sector are informed about the results. 

  

  * **WP8:** Is focusing on the project management and technical coordination. Its main objectives are to ensure efficient coordination of the project together with the TMT (Technical Management Team) and the Steering Committee. Moreover, this WP is coordinating the technical work of the various WPs in order to keep the alignment with the overall objectives of the project and with Shift2Rail activities, as well as monitoring the TD1.2 contribution to the overall KPI of Shift2Rail. 

  

##  DATA MANAGEMENT PLAN (DMP) GUIDING PRINCIPLES

The Data Management Plan of CONNECTA-2 is coordinated by Work Package 8, and
is articulated around the following key points:

  * The Data Management Plan (DMP) described in this document has been prepared taking into account the template of the Guidelines on Data Management in Horizon 2020 [01]. The elaboration of the DMP will allow CONNECTA-2 partners to address all issues related with IP protection and data. The DMP is an official project Deliverable (D8.2) due in Month 4 (January 2019), but it will be a live document throughout the project. This initial version will evolve depending on significant changes arising and periodic reviews at reporting stages of the project. 

  

  * The consortium will comply with the Regulatiohn (EU) 2016/679 regarding the General Data Protection Regulation, meaning that beneficiaries will ensure that - if applicable - all the data intended to be processed are relevant and limited to the purposes of the research project (in accordance with the ‘data minimisation‘ principle). 

  

  * Procedures that will be implemented for data collection, storage, access, sharing policies, protection, retention and destruction will be in line with EU standards as described in the Grant Agreement and the Consortium Agreement, particularly Articles 18 (“Keeping Records - Supporting Documentation”; Article 23 (“Management of Intellectual Property”); 

  

Article 24 (“Agreement on background”); Article 25 (“Access Rights to
Background”); Article 26 (“Ownership of Results”); Article 27 (“Protection of
Results - Visibility of EU funding”);

Article 30 (“Transfer and Licensing of Results”); Article 31 (“Access Rights
to Results”); Article 36 (“Confidentiality”); Article 37 (“Security-related
Obligations”); Article 39 (“Processing of Personal Data”); Article 52
(“Communication between the parties”), and “Annex I – Description of Work” of
the Grant Agreement.

##  CONNECTA-2 DATA MANAGEMENT POLICY

CONNECTA-2 Data Management Plan applies the FAIR (Findable, Accessible,
Interoperable and Reusable) Data Management Protocols. This document addresses
for each data set collected, processed and/or generated in the project the
following elements:

  * **Contribution reference and naming:** Internal project Identifier (ID) for the data set to be produced. This identification code contains the six following sections: [Project] - [Domain] - [Type] - [Owner] - [Number] – [Version]. Where: 

    * [Project] is CTA2 for all CONNECTA-2 documents; o [Domain] is the relevant domain in the Cooperation Tool (WP, Task or project body); o [Type] is one letter defining the document category; o [Owner] is the trigram of the deliverable leader organisation; 

  

    * [Number] is an order number within a domain allocated by the Cooperation Tool when the document is first created; 

  

    * [Version] is the incremental version number, automatically incremented at each upload. 

  

  

  * **Standards and metadata:** Reference to existing suitable standards will be added if any. 

  

  * **Contribution description:** Description of the data that will be generated or collected. 

  

  * **Data sharing:** Description of how data will be shared, including access procedures and necessary software and other tools for enabling reuse, and definition of whether access will be open or restricted to specific groups. 

  

  * **Archiving and preservation:** Description of the procedures that will be put in place for long-term preservation of the data 

  

#  DATA MANAGEMENT PLAN

##  DATA SUMMARY

CONNECTA-2 will generate different type of data which are listed in the
following table: **Table 1: Existing Data used in CTA2**  
  
<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>

CTA2-1.1

</td>  
<td>

Measurement data

</td>  
<td>

Format: raw

data, text files, proprietary formats as

e.g. .mat, .xls, …, Units: e.g. Hz, bits/s, samples/s, m, s, …

</td>  
<td>

Data from former measurement campaigns

</td>  
<td>

Partner which generated the

measurement

data

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

CTA2-1.2

</td>  
<td>

Software

</td>  
<td>

</td>  
<td>

variable

</td>  
<td>

Partner institution

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

Data generated in this project include the following types:

**Table 2: Data Generated in CTA2**  
  
<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>

CTA2-2.1

</td>  
<td>

Measurement data

</td>  
<td>

E.g. Hz, m, bits/s,

samples/s, … Format: raw

data, text file,

.mat, …

</td>  
<td>

From several MB to GB of data from the wireless data transmission tests on
real vehicles

</td>  
<td>

Partner institution who executes the measurement

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

CTA2-2.2

</td>  
<td>

Software(Code):

Simulations, scripts, etc.

</td>  
<td>

e.g. .c, .m, …

</td>  
<td>

Several MB

</td>  
<td>

The rightful owner according to the contract of purchase

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

CTA2-2.3

</td>  
<td>

Source files for

RBD/FTA Calculations

</td>  
<td>

TBD

</td>  
<td>

Unknown

</td>  
<td>

Partner institution who executes the calculations

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

CTA2-2.4

</td>  
<td>

Source files for FMECA

</td>  
<td>

TBD

</td>  
<td>

unknown

</td>  
<td>

Partner institution who executes the calculations

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

CTA2-2.5

</td>  
<td>

DOORS requirements

</td>  
<td>

DOORS

database

</td>  
<td>

Unknown MB

</td>  
<td>

Shared between the contributing partners

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

CTA2-2.6

</td>  
<td>

SysML / UML diagrams

</td>  
<td>

MagicDraw,

Enterprise Architect… formats

</td>  
<td>

Several MB

</td>  
<td>

Partner producing the diagrams

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

CTA2-2.7

</td>  
<td>

Test logs

</td>  
<td>

Several formats: Text, raw data…

</td>  
<td>

From several MB to GB

</td>  
<td>

Partner institution who executes the

tests

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

##  FAIR DATA

CONNECTA-2 project will work to ensure as much as possible that its data will
be ’FAIR’, that is findable, accessible, interoperable and reusable, according
to the points below.

###  Making data findable, including provisions for metadata

CONNECTA-2 project is part of European Shift2Rail initiative, therefore it is
expected to deposit the generated results in the _Cooperation Tool_ online
repository. Within this repository, the deliverables marked as _public_ will
be accesible via Shift2Rail website. Each public deliverable goes with a
deliverable title and a short description of its content, which helps to find
the desired content.

Each task leader is responsible for ensuring that the dissemination level of
each deliverable is correctly set. Equally, the deliverables will use
references according to their dissemination level. This means that public
deliverables should not refer to confidential documents which invalidate their
correct understanding.

###  Making data openly accessible

In order to ease the future works within the Shift2Rail TD1.2, CONNECTA-2 will
make available all data which are identified as appropriate (public and
confidential) to future projects (i.e. AWP 2020). The CONNECTA-2 Steering
Commitee is responsible for IPR issues that may appear, and any confidential
data disclosure needs for its possitive decision.

Task leaders will collect data from each task and the IPR Committee will
review and approve all data that are identified as appropriate for open
access. This process will be carried out on an ongoing basis to facilitate the
publication of appropriate data as soon as possible.

Any additional data beside the foreseen deliverables that are likely to be
shared should be evaluated by the CONNECTA-2 consortium. The Steering
Committee of CONNECTA-2 will assess such justifications and make the final
decision, based on examination of the following elements regarding
confidentiality of datasets:

  * Commercial sensitivity of datasets 

  

  * Data confidentiality for security reasons 

  

  * Conflicts between open-access rules and national and European legislation (e.g. data protection regulations). 

  

  * Sharing data would jeopardise the aims of the project. 

  

  * Other legitimate reasons, to be validated by the IPR Committee 

  

Where it is determined that a database should be kept confidential, the
reasons for doing so will be included in an updated version of the DMP. Table
3 illustrates an example of a level of accesibility of CONNECTA-2 data for
future Shift2Rail AWP 2020 TD1.2 projects.

####  Table 3: Level of availability of additional CONNECTA-2 data ( _example_
)  
  
<table>  
<tr>  
<th>

**Dataset number**

</th>  
<th>

**Task number**

</th>  
<th>

**Dataset name**

</th>  
<th>

**Open / Restricted**

</th>  
<th>

**Reason for**

**Restriction**

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

_1_

</td>  
<td>

_T5.2_

</td>  
<td>

_Report on Regional lab demonstrator Test_

_Platform_

</td>  
<td>

_Restricted_

</td>  
<td>

_IPR_

_Sensitivities across datasets_

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

_2_

</td>  
<td>

_T6.1_

</td>  
<td>

_Report on Urban lab demonstrator Test_

</td>  
<td>

_Open_

</td>  
<td>

_N/A_

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

_3_

</td>  
<td>

_T6.2_

</td>  
<td>

_Report on Regional lab demonstrator Test_

</td>  
<td>

_Open_

</td>  
<td>

_N/A_

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

###  Making data interoperable

The data type and unique identifiers for the data produced by CONNECTA-2 are
introduced in section 1 and section 2.1. For further data generated during the
project, this information will be oulined in subsequent versions of this
document. In that case, information on data and metadata vocabularies,
standards or methodology to follow to facilitate interoperability will be
defined.

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

CONNECTA-2 project will generate valuable data for subsequent project in AWP
2020. Specifically, the experimental results obtained in CONNECTA-2 will be
the basis for the future CFM project starting in 2020\.

As the project progresses and data are identified and collected, further
information on increasing data re-use will be outlined in subsequent versions
of the DMP.

##  DATA SHARING

Table 4 summarizes the data sharing mechanisms to be used within CONNECTA-2
project. **Table 4: Data Sharing in CONNECTA**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data sharing**

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

CTA2-2.3 / 2.4 / 2.6

</td>  
<td>

Cooperation Tool (Project’s online repository)

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

CTA2-2.5

</td>  
<td>

DOORS requirements will be shared as ReqIF exchange format, together with the
Microsoft Word version, and stored in Cooperation Tool (Project’s online
repository) for sharing.

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

CTA2-2.2

</td>  
<td>

Generated source code and executable files may be shared with the project
partners additionally through an online repository (CVS like) or FTP.

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

CTA2-2.1 / 2.7

</td>  
<td>

Produced test logs and measured data may be shared with the project partners
additionally through FTP if its size rises over 20 MB, otherwise the
Cooperation Tool will be used.

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

##  ARCHIVING AND PRESERVATION

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

During the life of CONNECTA data extraction from the Cooperation Tool will be
supported. Table 5 summarizes the archiving and preservation policies to be
used.

####  Table 5: Archiving and preservation of the data in CONNECTA  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

CTA-2.1 / 2.2 / 2.5 / 2.7

</td>  
<td>

Regular backup of data on server, managed by IT departments

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

CTA-2.3 / 2.4 / 2.6

</td>  
<td>

Data will be stored on the Cooperation Tool which already has its backup
procedures.

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

##  DATA SECURITY

The research outputs of the project will be publicly available within the
website of the project (
_https://projects.shift2rail.org/s2r_ip1_n.aspx?p=CONNECTA-2_ ) unless the
result is marked as confidential in the Grant Agreeement.

The reasons to consider the results as confidential are the following ones:

  * Protection of intellectual property rights regarding new processes, products and technologies that would impact the competitive advantage of the consortium or its members. 

  

  * Commercial agreements as part of the procurements of components or materials that might foresee the confidentiality of data. 

  

  * Members background knowledge that might foresee the confidentiality of data. 

  

#  DMP REVIEW PROCESS & TIMETABLE

Shift2Rail TD1.2 MAAP (deployed by CONNECTA-1, CONNECTA-2 and CONNECTA-3
projects) is based on the V-Model illustrated in Figure 2. This model must be
contextualised to Shift2Rail, and in particular to the MAAP. CONNECTA-2 does
not cover the whole life cycle of the new TCMS generation but only some of the
first activities. Indeed, the project outcomes will reach TRL 4 or 5, but not
higher.

So the “V” can be split into three parts, each of them corresponding to a
different call or phase. While the specification, system architecture and
subsystem design correspond to CONNECTA-1, the implementation of the
components and integrating them into subsystems are allocated to CONNECTA-2,
and finally, putting everything together on the Integrated Technology
Demonstrator (ITD) for system testing in CONNECTA-3.

**Figure 2: Project structure**

Due to the continuous iteration between design and testing of developed
technologies, it may be needed to update the design specifications, applying
also to some specifications already finished in CONNECTA-1 project. _In order
to keep the specification of the NG-TCMS updated along the whole_ _MAAP, this
section will include in subsequent releases (mainly in M24 and M30) any
additional_ _document (not foreseen initially in the project proposal), which
amends of complements any_ _specification already released._

##  DMP REVIEW IN M24

This section is temporally empty until M24 of the project.

##  DMP REVIEW IN M30

This section is temporally empty until M30 of the project.

#  CONCLUSIONS

The purpose of the Data Management Plan (DMP) is to support the data
management life cycle for all data that will be collected, processed or
generated by the CONNECTA-2 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 review to fine-tune it to the data
generated and the uses identified by the consortium since not all data or
potential uses are clear at this stage of the project.