**1\. INTRODUCTION**

The present Document Management Plan (onwards 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. 636078. 

  

The DMP is organised per Work Package (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 that the project will generate, a brief
overview of the project is given below:

IT2Rail is a first step towards achieving the objectives of the long term
Shift2Rail

Programme.

More specifically the 4

th

Innovation Programme (IP4) focusing on “IT Solutions for Attractive

Railway Services”. The overall aim is to provide a new seamless travel
experience giving access

to a complete multimodal travel offer which connects th

e first and last mile to long distance

journeys by:

•

Transforming global travel interactions into a fully integrated and customised

experience;

•

Providing a door

\-

to

\-

door (D2D) multi modal travel experience, through services

distributed by multiple providers;

•

Helping operators to adapt their level of service, better to satisfy customer
expectations

and optimise their own operations.

Even though the scope of IT2Rail is reduced in comparison to IP4, the work is
organised around

the six Technology Demonstrators (

TDs) that can be found in IP4 and are essentially equivalent

to the Work Packages 1

\-

6

shown in Figure 1.

**Figure**

**1**

**:**

**Project Organisation**  
  
<table>  
<tr>  
<th>

  * WP1 will provide IT2Rail functional applications with a ‘web of transportation data’ abstraction of the distributed resources they need to operate. The abstraction is constructed by using semantic web technology open standards. 

  

  * WP2 will: 

    * Establish the architecture for managing and aggregating distributed travel shopping data and distributed journey planning expertise; 

  

    * Create the basis for a one-stop shop for co-modally marketed transport products and services whose combinations can answer to door-to-door mobility queries; 

  

    * Allow for the presentation of transport service attributes and facilities answering to 

  

  

Customer preferences in connection with carbon footprint and ‘reduced
mobility’ needs;

  * Interface with WP1 to overcome interoperability obstacles, so protecting the Customer from the fragmentation of messaging and codification standards which make travel shopping so difficult and risky in today’s fragmented travel marketplace. 

  

  * WP3 will extend the interoperability between modes, operators and systems by providing travellers with the possibility to book and pay in a ‘one-click’ action, complete multimodal door-todoor travel journeys and to validate their travel entitlements across heterogeneous transport systems. It also includes ticketing activities. 

  

  * WP4 will monitor irregularities in transport and respond to such anomalies in on-line mode, including suggestions of alternative solutions. 

  

  * WP5 will develop the key concepts of unique Traveller identifier, smart device and virtualised data store to bolster attractiveness of the Rail transport ecosystem. An allencompassing user front end offering access to a wealth of multimodal services and products will promote a new door-to-door traveling experience. 

  

  * WP6 will focus on leveraging social, mobile, structured and unstructured data to obtain valuable, actionable insights that allows rail operators, product/service providers, Traveller/Transport Enterprises to make better decisions in order to increase quality of service and revenues, to better adapt their level of service to the passenger demand and to optimise their operations in order to bring and retain more people on the train-urban mobility. 

  

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

**2\. DATA MANAGEMENT AT PROJECT LEVEL**

  1. **DATA COLLECTION & DEFINITION **

  

  

The responsibility to define and describe all non-generic data sets specific
to an individual work package shall be with the WP leader.

The WP leaders shall formally review and update the data sets related to their
WP.

All modifications/additions to the data sets shall be provided to the IT2Rail
Coordinator (UNIFE) for inclusion in the DMP.

  2. **DATA ARCHIVING & PRESERVATION **

  

  

At the formal project closure, all the data material that has been collated or
generated within the project and registered on the Cooperation Tool (CT) shall
be copied and transferred to a digital archive.

This archive shall reside in the UNIFE premises located in Brussels, Belgium.

UNIFE provides an archive facility with structured systems for document query,
retrieval and longterm preservation.

###  2.2.1 Data Security & Integrity

The IT2Rail project will be subject to the same levels of data security as
applied to normal operations within UNIFE.

UNIFE relies upon its information and the systems that manage it to carry out
its business operations; hence protecting information is paramount in
supporting UNIFE activities in meeting both its objectives and regulatory
obligations.

Maintaining the security of information manages the risks more effectively
resulting in the prevention of operational activities interruption.

Without the correct protection measures, there is a risk of vulnerability to
those who are intent on harming or who wish to control or steal assets.

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

###  2.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 CT.

At the time of document creation (uploading to CT) the document will be
“flagged” as a candidate data set for future archiving.

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

###  2.2.3 Data Transfer

The data transfer mechanism between the CT and the data archive repository
shall be performed as a single transaction.

The physical means of data transfer shall be jointly reviewed between the
Project Coordinator (UNIFE) and the CT system provider.

**2.3 FILE NAMING CONVENTIONS**

All files irrespective of the data type shall be named in accordance with the
following document Code structure:

The identification code contains the six following sections: **[Project] -
[Domain] - [Type] - [Owner] - [Number] – [Version]**

Where:

  * [Project] is ITR for all IT2Rail documents; 

  

  * [Domain] is the relevant domain in the Cooperation 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 Cooperation Tool when the document is first created; 

  

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

  

Example shown below:  
  
<table>  
<tr>  
<th>

**Project**

**Code**

</th>  
<th>

**Domain**

**(3-5 char.)**

</th>  
<th>

**Type**

**(1 letter)**

</th>  
<th>

**Owner (3 letters)**

</th>  
<th>

**Number**

**(3 digits)**

</th>  
<th>

**Version**

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

ITR

</td>  
<td>

WP2

</td>  
<td>

D

</td>  
<td>

UNI

</td>  
<td>

001

</td>  
<td>

01

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

**2.4 IT2RAIL ARCHIVED DATA & SHIFT2RAIL **

The specific IT2Rail 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, intelligible and not subject to
possible future ambiguous interpretation.

It is anticipated that the synergetic parallel working between the two
projects will be further enhanced by having data available prior to the
conclusion of the IT2Rail project that is of a defined format in accordance
with this DMP.

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

During the life of IT2Rail data extraction from the CT will be supported.

**3\. DMP OF WP1: INTEROPERABILITY FRAMEWORK**

**3.1 DATA SETS**

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

**Code**

</th>  
<th>

**Description of Dataset/Digital Output**

</th>  
<th>

**Units and Format**

</th>  
<th>

**Size**

</th>  
<th>

**Provided by**

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

ITR-1.1

</td>  
<td>

Wikidata knowledge graph  1

</td>  
<td>

rdf,

accessed via sparql endpoint

</td>  
<td>

unlimited

</td>  
<td>

Wikidata (online)

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

ITR-1.2

</td>  
<td>

DBpedia knowledge graph  2

</td>  
<td>

rdf,

accessed via sparql endpoint

</td>  
<td>

unlimited

</td>  
<td>

Dbpedia (online)

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

ITR-1.3

</td>  
<td>

SNCF Rail Stations

</td>  
<td>

CSV

</td>  
<td>

422 KB

</td>  
<td>

SNCF

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

ITR-1.4

</td>  
<td>

SNCF Routes

</td>  
<td>

XML

</td>  
<td>

29 KB

</td>  
<td>

SNCF

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

ITR-1.5

</td>  
<td>

AMS Stations

</td>  
<td>

XML

</td>  
<td>

30 KB

</td>  
<td>

Oltis Group

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

ITR-1.6

</td>  
<td>

AMS Connections

</td>  
<td>

XML

</td>  
<td>

3.2 MB

</td>  
<td>

Oltis Group

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

ITR-1.7

</td>  
<td>

VBB Stops, Routes, Services

</td>  
<td>

GTFS

</td>  
<td>

54.5 MB

(compressed)

</td>  
<td>

HaCon

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

ITR-1.8

</td>  
<td>

TMB (Madrid) Stops, Routes, Services

</td>  
<td>

GTFS

</td>  
<td>

23.3 MB

(compressed)

</td>  
<td>

INDRA

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

ITR-1.9

</td>  
<td>

TMB (Barcelona) Stops, Routes, Services

</td>  
<td>

GTFS

</td>  
<td>

5.5 MB

(compressed)

</td>  
<td>

INDRA

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

ITR-1.10

</td>  
<td>

VAO Stops, Routes, Services

</td>  
<td>

GTFS

</td>  
<td>

67.3 MB

(compressed)

</td>  
<td>

HaCon

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

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

Data generated by this WP include the following data sets:  
  
<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>

ITR-1.11

</td>  
<td>

Barcelona Network Statistics

</td>  
<td>

XML

</td>  
<td>

273 KB

</td>  
<td>

Indra

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

ITR-1.12

</td>  
<td>

Madrid Cercanias Network

Statistics

</td>  
<td>

XML

</td>  
<td>

436 KB

</td>  
<td>

Indra

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

ITR-1.13

</td>  
<td>

Madrid Bus Network Statistics

</td>  
<td>

XML

</td>  
<td>

8.2 MB

</td>  
<td>

Indra

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

ITR-1.14

</td>  
<td>

Madrid Metro Ligero Network

Statistics

</td>  
<td>

XML

</td>  
<td>

97 KB

</td>  
<td>

Indra

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

ITR-1.15

</td>  
<td>

Madrid Metro Network Statistics

</td>  
<td>

XML

</td>  
<td>

507 KB

</td>  
<td>

Indra

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

ITR-1.16

</td>  
<td>

Berlin Network Statistics

</td>  
<td>

XML

</td>  
<td>

921 KB

</td>  
<td>

HaCon

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

ITR-1.17

</td>  
<td>

AMS Network Statistivs

</td>  
<td>

XML

</td>  
<td>

19 KB

</td>  
<td>

Oltis Group

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

ITR-1.18

</td>  
<td>

IndraRail Network Statistics

</td>  
<td>

XML

</td>  
<td>

9 KB

</td>  
<td>

Indra

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

ITR-1.19

</td>  
<td>

VAO (Wien) Network Statistics

</td>  
<td>

XML

</td>  
<td>

3.8 KB

</td>  
<td>

HaCon

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

ITR-1.20

</td>  
<td>

SNCF Network Statistics

</td>  
<td>

XML

</td>  
<td>

7.4 KB

</td>  
<td>

SNCF

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

ITR-1.21

</td>  
<td>

Trenitalia Network Statistics

</td>  
<td>

XML

</td>  
<td>

6 KB

</td>  
<td>

Trenitalia

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

ITR-1.22

</td>  
<td>

It2Rail semantic graph

</td>  
<td>

RDF

</td>  
<td>

1.6 M

triples,

</td>  
<td>

It2Rail (online)

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

ITR-1.23

</td>  
<td>

It2Rail ontology

</td>  
<td>

OWL

</td>  
<td>

11 K statements

</td>  
<td>

It2Rail (online)

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

**Table 2: Data Generated in WP1**

##  3.2 STANDARDS, METADATA AND QUALITY ISSUES

The data will be organised in databases and documented in a standardised way
that will be decipherable by all the participants of the WP1.

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

**Code**

</th>  
<th>

**Data sharing**

</th>  
<th>

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

ITR-1.11 to

ITR-1.21

</td>  
<td>

Network statistics data sets on SVN repository at

https://svn.ws.dei.polimi.it/IT2Rail-deib/XSDschemas/NetworkStatistics

</td>  
<td>

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

ITR-1.22

</td>  
<td>

It2Rail semantic graph accessible at SPARQL access point
http://accessmanagementdemo.cloud:70/graphdb-workbench-free/sparql

</td>  
<td>

at

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

ITR-1.23

</td>  
<td>

It2Rail ontology accessible at https://it2rail.ivi.fraunhofer.de/webprotege/

</td>  
<td>

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

###  Table 3: Data Sharing in WP1

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

**Code**

</th>  
<th>

**Archiving and preservation**

</th>  
<th>

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

ITR-1.11 to

ITR-1.21

</td>  
<td>

Network statistics data sets on SVN repository at

https://svn.ws.dei.polimi.it/IT2Rail-deib/XSDschemas/NetworkStatistics

</td>  
<td>

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

ITR-1.22

</td>  
<td>

It2Rail semantic graph accessible at SPARQL access point
http://accessmanagementdemo.cloud:70/graphdb-workbench-free/sparql

</td>  
<td>

at

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

ITR-1.23

</td>  
<td>

It2Rail ontology accessible at https://it2rail.ivi.fraunhofer.de/webprotege/

</td>  
<td>

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

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

  4. **DMP OF WP2: TRAVEL SHOPPING**

  

  

**4.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>

ITR-2.1

</td>  
<td>

Feeds for Indra’s Urban TSP with the planning data of the

urban transit in Madrid

(CRTM)

</td>  
<td>

GTFS

</td>  
<td>

NR

</td>  
<td>

CRTM (Consorcio

Regional de

Transportes de

Madrid)

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

ITR-2.2

</td>  
<td>

Feeds for Indra’s Urban TSP with the planning data of the urban transit in
Barcelona

(TMB)

</td>  
<td>

GTFS

</td>  
<td>

NR

</td>  
<td>

TMB (Transports

Metropolitans de

Barcelona)

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

###  Table 5: Existing Data used in WP2

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

**Code**

</th>  
<th>

**Description of Dataset/Digital Output**

</th>  
<th>

</th>  
<th>

**Units and**

**Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

ITR-

2.3

</td>  
<td>

Rail Itineraries between an origin and a destination:

</td>  
<td>

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

</td>  
<td>

**Output**

</td>  
<td>

origin

</td>  
<td>

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

destination

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

date

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

duration

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

numTransfers

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

price

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

departureTime

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

arrivalTime

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

travelEpisodes

</td>  
<td>

date

duration

travelEpisodeId trainCode

departureStation

destinationStation departureTime

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

arrivalTime

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

ITR-

2.4

</td>  
<td>

Train availability to find an available **Seat** in a **Train** from an
**Origin** **Station** to a **destination** **Station** at a specific **date**
.

</td>  
<td>

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

</td>  
<td>

**Output**

</td>  
<td>

ResponseCode

</td>  
<td>

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

ResponseDescription

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

TrainCode

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

ClassCode

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

Price

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

CoachCode

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

SeatCode

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

DepartureTime

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

ArrivalTime

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

ContractId

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

ITR-

2.5

</td>  
<td>

Lock Inventory info to lock/book a seat in a Train from an Origin Station to a
destination Station at a specific date.

</td>  
<td>

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

</td>  
<td>

**Output**

</td>  
<td>

ResponseCode

</td>  
<td>

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

ResponseDescription

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

SeatId

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

PurchaseCode

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

BookingCode

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

ITR-

2.6

</td>  
<td>

GetRoutes information for Madrid travel episodes:

  * Itineraries 

  

  * Legs 

  

  * Steps 

  

</td>  
<td>

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-

2.7

</td>  
<td>

Network Reference Resources

</td>  
<td>

</td>  
<td>

Amadeus ad hoc format

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-

2.8

</td>  
<td>

Itinerary offers

</td>  
<td>

</td>  
<td>

XML

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

**Table 6: Data Generated in WP2**

**4.2 STANDARDS, METADATA AND QUALITY ISSUES**

The data will be organised in databases and documented in a standardised way
that will be decipherable by all the participants of the WP2.

**4.3 DATA SHARING**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data sharing**

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

ITR-2.1

</td>  
<td>

Data has been obtained from the open data portal of the CRTM (
_http://datacrtm.opendata.arcgis.com/_ )  containing the GTFS files for Metro,
Buses, Coach,

Tram and Train in Madrid, and this information is imported in the Indra’s
Urban TSP.

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

ITR-2.2

</td>  
<td>

Data has been obtained from TMB containing the GTFS files for Metro, Buses,
Coach, Tram and Train in Barcelona, and this information is imported in the
Indra’s Urban TSP. Indra has received authorization of TMB to use them
specifically for project purposes.

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

IT2-2.3

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-2.4

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-2.5

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-2.6

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-2.7

</td>  
<td>

Data retrieved from the Networkgraph manager (WP1) through a XML endpoint

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

IT2-2.8

</td>  
<td>

Data retrieved dynamically from the Shopping Broker (WP1) through a XML
endpoint

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

###  Table 7: Data Sharing in WP2

**4.4 ARCHIVING AND PRESERVATION**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

ITR-2.1

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.2

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.3

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.4

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.5

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.6

</td>  
<td>

Data stored on Indra’ server

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

ITR-2.7

</td>  
<td>

Network Reference Resources are stored within Amadeus server. This data is

stored until the associated validity date is reached or until the Network
Reference Resources are refreshed with new data

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

ITR-2.8

</td>  
<td>

Itinerary offers details are stored within Amadeus server. This data is used
by the booking process (WP3) and its storage is temporary (1 week maximum)

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

###  Table 8: Archiving and preservation of the data in WP2

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

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

ITR-2.1

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.2

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.3

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.4

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.5

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.6

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-2.7

</td>  
<td>

Amadeus

</td>  
<td>

Amadeus maintains Network Reference Resources data up-to-date

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

ITR-2.8

</td>  
<td>

Amadeus

</td>  
<td>

Amadeus is in charge of the storage of the itinerary offers details

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

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

  5. **DMP OF WP3: BOOKING & TICKETING **

  

  

**5.1 DATA TYPES**

No existing data types were used in this WP. Data generated in this WP include
the following types:  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description of Dataset/Digital Output**

</th>  
<th>

</th>  
<th>

**Units and**

**Format**

</th>  
<th>

**Size**

</th>  
<th>

**Ownership**

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

ITR-3.1

</td>  
<td>

GetBooking with the booking information of a Seat on a Train from A to B on a
Date.

</td>  
<td>

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2R

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

</td>  
<td>

**Output**

</td>  
<td>

bookingCode

</td>  
<td>

JSON

</td>  
<td>

</td>  
<td>

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

status

</td>  
<td>

</td>  
<td>

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

trainCode

</td>  
<td>

</td>  
<td>

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

origin

</td>  
<td>

</td>  
<td>

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

destination

</td>  
<td>

</td>  
<td>

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

date

</td>  
<td>

</td>  
<td>

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

departureTime

</td>  
<td>

</td>  
<td>

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

arrivalTime

</td>  
<td>

</td>  
<td>

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

duration

</td>  
<td>

</td>  
<td>

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

price

</td>  
<td>

</td>  
<td>

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

coachCode

</td>  
<td>

</td>  
<td>

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

seatCode

</td>  
<td>

</td>  
<td>

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

classCode

</td>  
<td>

</td>  
<td>

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

passengerName

</td>  
<td>

</td>  
<td>

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

passengerSurname

</td>  
<td>

</td>  
<td>

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

passengerId

</td>  
<td>

</td>  
<td>

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

numStops

</td>  
<td>

</td>  
<td>

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

serviceList

</td>  
<td>

name code

descripti price

</td>  
<td>

on

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

ITR-3.2

</td>  
<td>

IssueToken with the Payload information of t token

</td>  
<td>

he

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2R

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

</td>  
<td>

**Output**

</td>  
<td>

ResponseCode

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

ResponseDescription

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

Payload

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

ITR-3.3

</td>  
<td>

Booking data

</td>  
<td>

</td>  
<td>

XML

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-3.4

</td>  
<td>

Confirmed booking data

</td>  
<td>

</td>  
<td>

XML

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

###  Table 10: Data Generated in WP3

**5.2 STANDARDS, METADATA AND QUALITY ISSUES**

The data will be organised in databases and documented in a standardised way
that will be decipherable by all the participants of the WP3.

**5.3 DATA SHARING**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data sharing**

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

IT2-3.1

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-3.2

</td>  
<td>

Data retrieved through a REST endpoint on Indra’s server

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

IT2-3.3

</td>  
<td>

Data retrieved dynamically from the Booking Broker (WP1) through a XML
endpoint

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

IT2-3.4

</td>  
<td>

Data retrieved dynamically from the Issuance Broker (WP1) through a XML
endpoint

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

###  Table 11: Data Sharing in WP3

**5.4 ARCHIVING AND PRESERVATION**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

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

ITR-3.1

</td>  
<td>

Data stored on Indra’ server

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

ITR-3.2

</td>  
<td>

Data stored on Indra’ server

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

ITR-3.3

</td>  
<td>

Booking and confirmed booking details are stored within Amadeus server. This
data is used by the booking and issuance orchestration and its storage is
temporary (1 week maximum)

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

###  Table 12: Archiving and preservation of the data in WP3

**5.5 DATA MANAGEMENT RESPONSIBILITIES**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

ITR-3.1

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-3.2

</td>  
<td>

Leyre Merle

Javier Saralegui

Verónica González Pérez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-3.3

</td>  
<td>

Amadeus

</td>  
<td>

Amadeus is in charge of the collection of this data

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

ITR-3.4

</td>  
<td>

Amadeus

</td>  
<td>

Amadeus is in charge of the collection of this data

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

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

  6. **DMP OF WP5: TRAVEL COMPANION**

  

  

**6.1 DATA TYPES**

There is no pre-existing data at WP5 level, all data is either generated by
the user (account creation, preferences, credit cards…) or received from other
modules of the IT2Rail project (booked offers, etc…).

There is no data base at WP5 level; all data are stored on Indra’s server.
APIs allow to receive/send the data.

Data generated or transiting through the TC Personal Application, and TC
Cloud, in this WP include the following types:

###  Table 14: Data Generated or transiting in WP5  
  
<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>

ITR-5.1

</td>  
<td>

User Identity data:

  * Login 

  

  * Password 

  

  * UserIdtoken 

  

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-5.1

</th>  
<th>

User Preferences data:

  * Preferred means of transportation 

  

  * Preferred carrier 

  

  * Loyalty/Reduction/Payment card 

  

  * PRM type 

  

  * Class  Seat 

  

  * Trip Tracker Behavior 

  

</th>  
<th>

JSON

</th>  
<th>

NR

</th>  
<th>

IT2Rail

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

ITR-5.1

</td>  
<td>

Entitlement data (allows the access of users to the Travel Companion
database):

  * UserIdToken 

  

  * User name 

  

  * Media Type 

  

  * Issue Date 

  

  * Departure Time 

  

  * Departure 

  

  * Arrival 

  

  * Token Id 

  

  * Payload State 

  

  * Trip Units 

  

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-5.1

</td>  
<td>

Token data (Tokens data allows the access of users to the Travel Companion
database):

  * Result Code 

  

  * Result Description 

  

  * Token Id 

  

  * Payload State  Trip Units 

  

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-5.1

</td>  
<td>

Booking data (allows accessing the information of the Booking Offer Item in
the Travel Companion Cloud Wallet):

  * Context (retailer, Travel 

  

Shopper, Device Info)

  * Passenger (Functionnal Id, 

  

Code, Personal Info,

Preference)

  * Stop Place (location) 

  

  * Travel Episode Endpoint 

  

(location)

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

</th>  
<th>

  * Travel Solution (departure, 

  

arrival)

  * Travel Episode: 

  

  * Departure 

  

  * Arrival 

  

  * Mileage 

  

  * Transportation Service (departure, arrival, Service Provider, 

  

Accessibility,

Emission, Route Link, Reference,

Equipment,

Customer

FeedBack,

Operating Partner Info, Validating Partner Info).

  * Booking: 

  

  * Booking Status 

  

  * Booking Provider 

  

  * Booking element 

  

(itinerary Offer Item)

  * Confirmed Booking: 

  

  * Booking Status 

  

  * Booking Provider 

  

  * Booking element 

  

(itinerary Offer Item)

  * Entitlement (tokens 

  

</th>  
<th>

</th>  
<th>

</th>  
<th>

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

ITR-5.1

</td>  
<td>

Payment data (contains data related to payment means, and access to payment
means):

  * User Id Token 

  

  * Credit card Id 

  

  * Card Display Name 

  

  * Card Number 

  

  * Card Validity End Month 

  

  * Card Validity End Year 

  

  * Card CVV 

  

  * Credit Card Type Id 

  

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

ITR-5.1

</td>  
<td>

Alert and Information messages (allow to receive and display different type of
messages to the user):

  * Booked Offer Ids 

  

  * Message Id 

  

  * Message Title 

  

  * Message Types 

  

  * Message Short Text 

  

  * Message Full Text 

  

  * Message Object 

  

  * MessageAsk For an 

  

Alternative

  * Message Time 

  

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail

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

  7. **DMP OF WP6: BUSINESS ANALYTICS**

    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>

ITR-6.1

</td>  
<td>

Current Weather Data

</td>  
<td>

MongoDB

</td>  
<td>

Size:

47.911.381 Byte

Record Count: 91.396 Record Size:

0,5 Kb

</td>  
<td>

OpenWeatherMap

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

ITR-6.2

</td>  
<td>

Forecast Weather Data

</td>  
<td>

MongoDB

</td>  
<td>

Size:

20.446.103 Byte

Record Count: 35.848 Record Size:

0,6 Kb

</td>  
<td>

OpenWeatherMap

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

ITR-6.3

</th>  
<th>

Itinerary Offers retrieved from

the Mobility Request

Manager

</th>  
<th>

MongoDB

</th>  
<th>

Size:

93.723.084 Byte

Record Count:

780

Record Size:

117,3 Kb

</th>  
<th>

IT2Rail – WP2

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

ITR-6.4

</td>  
<td>

TC User Feedbacks regarding Travel Questionnaire

</td>  
<td>

MySQL

</td>  
<td>

Size:

824 Byte

Record Count:

249

Record Size:

96 Kb

</td>  
<td>

IT2Rail – WP5

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

ITR-6.5

</td>  
<td>

ArrivalDelayEvent

</td>  
<td>

MySQL

</td>  
<td>

Size:

256 Byte

Record Count:

64

Record Size:

16 Kb

</td>  
<td>

IT2Rail – WP4

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

ITR-6.6

</td>  
<td>

DepartureDelayEvent

</td>  
<td>

MySQL

</td>  
<td>

Size:

260 Byte

Record Count:

63

Record Size:

16 Kb

</td>  
<td>

IT2Rail – WP4

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

ITR-6.7

</td>  
<td>

ArrivalRulesActivationReque st

</td>  
<td>

MySQL

</td>  
<td>

Size:

98 Byte

Record Count:

</td>  
<td>

IT2Rail – WP4

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

</th>  
<th>

</th>  
<th>

</th>  
<th>

166

Record Size:

16 Kb

</th>  
<th>

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

ITR-6.8

</td>  
<td>

DepartureRulesActivationRe

quest

</td>  
<td>

MySQL

</td>  
<td>

Size:

92 Byte

Record Count:

177

Record Size:

16 Kb

</td>  
<td>

IT2Rail – WP4

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

ITR-6.9

</td>  
<td>

RuleDeactivationRequest

</td>  
<td>

MySQL

</td>  
<td>

Size:

84 Byte

Record Count:

193

Record Size:

16 Kb

</td>  
<td>

IT2Rail – WP4

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

ITR-6.10

</td>  
<td>

User feedbacks for sentiment analysis

</td>  
<td>

File

</td>  
<td>

5 MB

</td>  
<td>

LDO-provided data

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

ITR-6.11

</td>  
<td>

Social Network Messages

</td>  
<td>

MongoDB/Spa

rksee

</td>  
<td>

UPC

</td>  
<td>

UPC-filtered Twitter feed

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

ITR-6.12

</td>  
<td>

Train Station Air Quality Data

</td>  
<td>

MongoDB

</td>  
<td>

Size : 704 Kb

Record

Count : 9397

Record

Size:78 b

(avg)

</td>  
<td>

CEA-provided data

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

ITR-6.13

</td>  
<td>

Travel Data Messages

</td>  
<td>

MongoDB

</td>  
<td>

Size : 25370 Kb

Record

Count : 67233

Record

Size :386 b

(avg)

</td>  
<td>

CEA-provided data

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

ITR-6.14

</td>  
<td>

Data mining information

</td>  
<td>

PostgreSQL

</td>  
<td>

NR

</td>  
<td>

Polimi-provided data

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

ITR-6.15

</td>  
<td>

Accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail – WP6

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

ITR-6.16

</td>  
<td>

Searches by BA users to the IT2Rail BA web platform

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail – WP6

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

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

Simulated 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>

ITR-6.17

</td>  
<td>

Happenings

</td>  
<td>

MySQL

</td>  
<td>

Size: 48.941

Byte

Record

Count : 133

Record

Size : 0,4

</td>  
<td>

IT2Rail – WP6

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

ITR-6.18

</td>  
<td>

KPIs concerning Transport Systems

</td>  
<td>

Pentaho

</td>  
<td>

A 50Kbyte

file of

simulated data

</td>  
<td>

IT2Rail – WP6

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

ITR-6.19

</td>  
<td>

KPIs concerning Booking & Ticketing of Travel Routes

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail – WP6

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

ITR-6.20

</td>  
<td>

KPIs concerning Travellers’

Preferences for Transport

Systems

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail – WP6

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

ITR-6.21

</td>  
<td>

KPIs concerning

Preferences of Travellers with Reduced Mobility

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail – WP6

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

**Table 16: Simulated 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>

ITR-6.22

</td>  
<td>

KPIs based on User

Preferences from the TC

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.23

</td>  
<td>

KPIs based on Trip Tracking Alternative Routes

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.24

</td>  
<td>

KPIs based on Trip Tracking

Complex Event Processing

Messages

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.25

</td>  
<td>

KPIs based on Social Network Messages

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.26

</td>  
<td>

Calculation of parameters of Train Station Air Quality Data based on
Meteorological Data

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.27

</td>  
<td>

Calculation of most Informative

Term from Travel data messages

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.28

</td>  
<td>

Calculation of number of cooccurring terms in Travel data

messages

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.29

</td>  
<td>

Calculation of a list of timelines of terms of interest from travel data
messages, given a metro line and a time window

</td>  
<td>

JSON

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.30

</td>  
<td>

Calculation of properties of preferred television programs in different
contexts

</td>  
<td>

PostgreSQL

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.31

</td>  
<td>

KPIs concerning accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

ITR-6.32

</td>  
<td>

KPIs concerning searches by BA users to the IT2Rail BA web platform

</td>  
<td>

MongoDB embedded

within Sofia2 platform

</td>  
<td>

NR

</td>  
<td>

IT2Rail-WP6

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

**Table 17: Data generated in WP6**

  2. **STANDARDS, METADATA AND QUALITY ISSUES**

  

  

The data will be organised in databases and documented in a standardised way
that will be decipherable by all the participants of the WP6.

  3. **DATA SHARING**

  

  

  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Description**

</th>  
<th>

**Mode of Data Sharing**

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

ITR-6.1

</td>  
<td>

Current Weather data

</td>  
<td>

OpenWeatherMap data retrieved through a REST endpoint and published to the
IT2Rail web

application or the mobile Travel

Companion

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

ITR-6.2

</td>  
<td>

Weather forecast data

</td>  
<td>

OpenWeatherMap data retrieved through a REST endpoint and published to the
public IT2Rail web

application

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

ITR-6.3

</td>  
<td>

Itinerary Offers retrieved from the Mobility Request Manager

</td>  
<td>

WP2 data retrieved dynamically from the Mobility Request Manager through a
REST endpoint and

saved on a WP6 MongoDB

database

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

ITR-6.4

</td>  
<td>

TC User Feedbacks regarding Travel Questionnaire

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.5

</td>  
<td>

ArrivalDelayEvent

</td>  
<td>

WP4 simulated train event data created and saved on a WP6

MySQL database for WP4-WP6 integration testing purposes

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

ITR-6.6

</td>  
<td>

DepartureDelayEvent

</td>  
<td>

WP4 simulated train event data created and saved on a WP6

MySQL database for WP4-WP6 integration testing purposes

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

ITR-6.7

</td>  
<td>

ArrivalRulesActivationRequest

</td>  
<td>

WP4 Travel Companion Trip

Tracking User Preferences retrieved from the WP4 database

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

</th>  
<th>

</th>  
<th>

and stored on a WP6 MySQL database for calculation of TT KPIs

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

ITR-6.8

</td>  
<td>

DepartureRulesActivationRequest

</td>  
<td>

WP4 Travel Companion Trip

Tracking User Preferences retrieved from the WP4 database and stored on a WP6
MySQL database for calculation of TT KPIs

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

ITR-6.9

</td>  
<td>

RuleDeactivationRequest

</td>  
<td>

WP4 Travel Companion Trip

Tracking User Preferences retrieved from the WP4 database and stored on a WP6
MySQL database for calculation of TT KPIs

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

ITR-6.10

</td>  
<td>

User feedbacks for sentiment analysis

</td>  
<td>

No sharing; demo data used for testing purposes

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

ITR-6.11

</td>  
<td>

Social Network Messages

</td>  
<td>

Data retrieved dynamically through the Twitter API, pre-processed to

conform to GDPR regulations (not

retrieving any personal information,

all the information is anonymised) and saved on a WP6 MongoDB

database for further calculation of

WP6 KPIs

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

ITR-6.12

</td>  
<td>

Train Station Air Quality Data

</td>  
<td>

No sharing; demo data used for testing purposes

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

ITR-6.13

</td>  
<td>

Travel Data Messages

</td>  
<td>

No sharing; demo data used for testing purposes

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

ITR-6.14

</td>  
<td>

Data mining information

</td>  
<td>

No sharing; demo data used for testing purposes

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

ITR-6.15

</td>  
<td>

Accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.16

</td>  
<td>

Searches by BA users to the IT2Rail BA web platform

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.17

</td>  
<td>

Happenings data

</td>  
<td>

Simulated happenings data stored on a WP6 MySQL database and

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

</th>  
<th>

</th>  
<th>

retrieved through a REST endpoint by the Travel Companion

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

ITR-6.18

</td>  
<td>

KPIs for Transport Systems

</td>  
<td>

Simulated transport systems data stored on a WP6 MySQL database and retrieved
through a REST

endpoint by the Travel Companion

stored on a WP6 MySQL database and retrieved through a REST endpoint by the
Travel Companion

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

ITR-6.19

</td>  
<td>

KPIs for Booking & Ticketing

</td>  
<td>

WP3 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.20

</td>  
<td>

KPIs for Preferences of Travellers with Reduced Mobility

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.21

</td>  
<td>

KPIs on user feedbacks concerning Travel Questionnaire

</td>  
<td>

KPIs calculated on Travel Companion Travel Questionnaire user feedbacks stored
on a WP6

MySQL database and retrieved through a REST endpoint by the

Travel Companion

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

ITR-6.22

</td>  
<td>

KPIs for Travellers’ Preferences

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.23

</td>  
<td>

KPIs based on Trip Tracking Alternative Routes

</td>  
<td>

WP4 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.24

</td>  
<td>

KPIs based on Trip Tracking

Complex Event Processing

Messages

</td>  
<td>

WP4 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.25

</td>  
<td>

KPIs based on Social Network Messages

</td>  
<td>

Information provided throught a RESTFul API viewed on a local IT2RAIL/CEA web
application.

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

ITR-6.26

</td>  
<td>

Calculation of parameters of Train

Station Air Quality Data based on

Meteorological Data

</td>  
<td>

No sharing; viewed through a REST API on a local IT2Rail/CEA web application.

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

ITR-6.27

</td>  
<td>

Calculation of most Informative Term from Travel data messages

</td>  
<td>

No sharing; viewed through a REST API on a local IT2Rail/CEA web application.

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

ITR-6.28

</td>  
<td>

Calculation of number of cooccurring terms in Travel data

messages

</td>  
<td>

No sharing; viewed through a REST API on a local IT2Rail/CEA web application.

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

ITR-6.29

</td>  
<td>

Calculation of a list of timelines of terms of interest from travel data
messages, given a metro line and a time window

</td>  
<td>

No sharing; viewed through a REST API on a local IT2Rail/CEA web application.

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

ITR-6.30

</td>  
<td>

Calculation of properties of preferred television programs in different
contexts

</td>  
<td>

WP6 data retrieved through a Java application provided by Polimi. No sharing;
the mined rules are the data generated by the application but are invisible to
the end user who can only check and acknowledge that application behaviour has
changed due to the generated rules.

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

ITR-6.31

</td>  
<td>

KPIs concerning accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

ITR-6.32

</td>  
<td>

KPIs concerning searches by BA users to the IT2Rail BA web platform

</td>  
<td>

WP5 data retrieved through a

REST endpoint and published to the IT2Rail web application or the mobile
Travel Companion

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

###  Table 18: Sharing of the data in WP6

**7.4 ARCHIVING AND PRESERVATION**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Archiving and preservation**

</th>  
<th>

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

ITR-6.1

</td>  
<td>

Current Weather data

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.2

</th>  
<th>

Weather forecast data

</th>  
<th>

Data stored within LEONARDO server

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

ITR-6.3

</td>  
<td>

Itinerary Offers retrieved from the Mobility Request Manager

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.4

</td>  
<td>

TC User Feedbacks regarding Travel Questionnaire

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.5

</td>  
<td>

ArrivalDelayEvent

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.6

</td>  
<td>

DepartureDelayEvent

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.7

</td>  
<td>

ArrivalRulesActivationRequest

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.8

</td>  
<td>

DepartureRulesActivationRequest

</td>  
<td>

Data stored within LEONARDO server

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

ITR-6.9

</td>  
<td>

RuleDeactivationRequest

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.10

</td>  
<td>

User feedbacks for sentiment analysis

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.11

</td>  
<td>

Social Network Messages

</td>  
<td>

Data stored temporary (1 day) within UPC Server.

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

ITR-

6.12

</td>  
<td>

Train Station Air Quality Data

</td>  
<td>

Data stored within IT2RAIL/CEA server.

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

ITR-

6.13

</td>  
<td>

Travel Data Messages

</td>  
<td>

Data stored within IT2RAIL/CEA server.

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

ITR-

6.14

</td>  
<td>

Data mining information

</td>  
<td>

Data stored within POLIMI server

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

ITR-

6.15

</td>  
<td>

Accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.16

</td>  
<td>

Searches by BA users to the IT2Rail BA web platform

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.17

</td>  
<td>

Happenings data

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.18

</td>  
<td>

KPIS for Transport Systems

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.19

</td>  
<td>

KPIs for Booking & Ticketing

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.20

</td>  
<td>

KPIs for Preferences of Travellers with Reduced Mobility

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.21

</td>  
<td>

KPIs on user feedbacks concerning Travel Questionnaire

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.22

</td>  
<td>

KPIs for Travellers’ Preferences

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.23

</td>  
<td>

KPIs based on Trip Tracking Alternative Routes

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.24

</td>  
<td>

KPIs based on Trip Tracking Complex Event Processing Messages

</td>  
<td>

Data stored within LEONARDO server

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

ITR-

6.25

</td>  
<td>

KPIs based on Social Network Messages

</td>  
<td>

Data stored anonymised within UPC Server

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

ITR-

6.26

</td>  
<td>

Calculation of parameters of Train Station Air Quality Data based on
Meteorological Data

</td>  
<td>

No preservation. Computed on demand.

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

ITR-

6.27

</td>  
<td>

Calculation of most Informative Term from Travel data messages

</td>  
<td>

No preservation. Computed on demand.

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

ITR-

6.28

</td>  
<td>

Calculation of number of co-occurring terms in Travel data messages

</td>  
<td>

No preservation. Computed on demand.

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

ITR-

6.29

</td>  
<td>

Calculation of a list of timelines of terms of interest from travel data
messages, given a metro line and a time window

</td>  
<td>

No preservation. Computed on demand.

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

ITR-

6.30

</td>  
<td>

Calculation of properties of preferred television programs in different
contexts

</td>  
<td>

Data stored within POLIMI server

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

ITR-

6.31

</td>  
<td>

KPIs concerning accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

ITR-

6.32

</td>  
<td>

KPIs concerning searches by BA users to the IT2Rail BA web platform

</td>  
<td>

Data stored within

Sofia2 Platform and

LEONARDO server

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

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

**7.5 DATA MANAGEMENT RESPONSIBILITIES**  
  
<table>  
<tr>  
<th>

**Code**

</th>  
<th>

**Data Description**

</th>  
<th>

**Name of Data Manager**

</th>  
<th>

**Description of Responsabilities**

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

ITR-6.1

</td>  
<td>

Current Weather data

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.2

</td>  
<td>

Weather forecast data

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.3

</td>  
<td>

Itinerary Offers retrieved from the Mobility Request Manager

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.4

</td>  
<td>

TC User Feedbacks regarding Travel Questionnaire

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.5

</td>  
<td>

ArrivalDelayEvent

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.6

</td>  
<td>

DepartureDelayEvent

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.7

</td>  
<td>

ArrivalRulesActivationRequest

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.8

</td>  
<td>

DepartureRulesActivationRequest

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.9

</td>  
<td>

RuleDeactivationRequest

</td>  
<td>

Guido Mariotta

Catherine Minciotti

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

</th>  
<th>

</th>  
<th>

Massimo Fratini

</th>  
<th>

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

ITR-6.10

</td>  
<td>

User feedbacks for sentiment analysis

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.11

</td>  
<td>

Social Network Messages

</td>  
<td>

Jordi Urmeneta

Carlos Balufo

Josep Lluís Larriba

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.12

</td>  
<td>

Train Station Air Quality Data

</td>  
<td>

Lorene Allano

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.13

</td>  
<td>

Travel Data Messages

</td>  
<td>

Lorene Allano

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.14

</td>  
<td>

Data mining information

</td>  
<td>

Matteo Rossi

Elisa Quintarelli

Letizia Tanca

</td>  
<td>

The data managers verify the availability of repositories storing data and
preferences.

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

ITR-6.15

</td>  
<td>

Accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.16

</td>  
<td>

Searches by BA users to the IT2Rail BA web platform

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.17

</td>  
<td>

Happenings data

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.18

</td>  
<td>

KPIS for Transport Systems

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.19

</th>  
<th>

KPIs for Booking & Ticketing

</th>  
<th>

Habib Deriu

Javier Saralegui

Sánchez

</th>  
<th>

The data managers verify the availability of the repositories storing data.

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

ITR-6.20

</td>  
<td>

KPIs for Preferences of Travellers with Reduced Mobility

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.21

</td>  
<td>

KPIs on user feedbacks concerning Travel Questionnaire

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.22

</td>  
<td>

KPIs for Travellers’ Preferences

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.23

</td>  
<td>

KPIs based on Trip Tracking Alternative Routes

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.24

</td>  
<td>

KPIs based on Trip Tracking

Complex Event Processing

Messages

</td>  
<td>

Guido Mariotta

Catherine Minciotti

Massimo Fratini

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.25

</td>  
<td>

KPIs based on Social Network Messages

</td>  
<td>

Jordi Urmeneta

Carlos Balufo

Josep Lluís Larriba

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.26

</td>  
<td>

Calculation of parameters of Train

Station Air Quality Data based on

Meteorological Data

</td>  
<td>

Lorene Allano

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

No computations saved.

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

ITR-6.27

</td>  
<td>

Calculation of most Informative Term from Travel data messages

</td>  
<td>

Lorene Allano

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

No computations saved.

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

ITR-6.28

</td>  
<td>

Calculation of number of cooccurring terms in Travel data

messages

</td>  
<td>

Lorene Allano

</td>  
<td>

No computations saved.

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

</td>  
<td>

</td>  
<td>

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

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

ITR-6.29

</td>  
<td>

Calculation of a list of timelines of terms of interest from travel data
messages, given a metro line and a time window

</td>  
<td>

Lorene Allano

Jacques-Henri Sublemontier

Fred Ngole Mboula

</td>  
<td>

No computations saved.

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

ITR-6.30

</td>  
<td>

Calculation of properties of preferred television programs in different
contexts

</td>  
<td>

Matteo Rossi

Elisa Quintarelli

Letizia Tanca

</td>  
<td>

The data managers verify the availability of repositories storing data and
contextual preferences.

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

ITR-6.31

</td>  
<td>

KPIs concerning accesses by BA users to the IT2Rail BA web platform

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

ITR-6.32

</td>  
<td>

KPIs concerning searches by BA users to the IT2Rail BA web platform

</td>  
<td>

Habib Deriu

Javier Saralegui

Sánchez

</td>  
<td>

The data managers verify the availability of the repositories storing data.

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

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

#  DMP OF WP8: DISSEMINATION

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

ITR-8.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 UNIFE to use images for dissemination

purposes of

IT2Rail.

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

ITR-8.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, .doc

</td>  
<td>

≈ 14 people in the contact

list

</td>  
<td>

The data will be kept in the UNIFE and UITP servers and is also included in
deliverable D8.9.

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

ITR-8.3

</td>  
<td>

Database of End Users Expert Group: This database contains data such as name,
e-mail, company, telephone and field of expertise of the partners
participating in the Expert Group.

</td>  
<td>

.xls, .doc

</td>  
<td>

≈ 15 people in the contact

list

</td>  
<td>

The data will be kept in the UNIFE and UITP servers and is also included in
deliverable D8.8.

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

ITR-8.4

</td>  
<td>

Database of Ethical Privacy and Security Expert Group: This database contains
data such as name, e-mail, company, telephone and field of expertise of the
partners participating in the Expert Group.

</td>  
<td>

.xls, .doc

</td>  
<td>

≈ 5 people in the contact

list

</td>  
<td>

The data will be kept in the UNIFE and UITP servers and is also included in
deliverable D8.8.

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

###  Table 21: Existing Data used in WP8

Please consult the UITP’s Privacy Policy (http://www.uitp.org/privacy-policy)
to find out more about how UITP handles personal data.

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

ITR-8.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>

ITR-8.2

</td>  
<td>

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

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

ITR-8.3

</td>  
<td>

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

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

ITR-8.4

</td>  
<td>

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

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

###  Table 22: Data Sharing in WP8

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

**Code**

</th>  
<th>

**Archiving and preservation**

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

ITR-8.1

</td>  
<td>

Data will be stored on the UNIFE server which is regularly backed up.

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

ITR-8.2, 8.3 and 8.4

</td>  
<td>

Data will be stored on the UITP server which is regularly backed up.

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

###  Table 23: Archiving and preservation of the data in WP8

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

**Code**

</th>  
<th>

**Name of Responsible**

</th>  
<th>

**Description**

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

ITR-8.1

</td>  
<td>

Stefanos Gogos (UNIFE)

</td>  
<td>

Update and maintenance of the data

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

ITR-8.2, 8.3 and

8.4

</td>  
<td>

Cristina Hernandez (UITP,

Project manager)

</td>  
<td>

Update and maintenance of the data

related to the project

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

**Table 24: Data Management Responsibilities in WP8**

#  CONCLUSIONS

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
IT2Rail project. The DMP is expected to be updated after the final review, to
fine-tune it to the data generated and the uses identified by the consortium
since not all data or potential uses might be considered before then.