1

TAF Regional workshopParis, 22 February 2016

CommonComponents

211 February 2016

11 February, 2016 3

CCS contentCRD - Central Reference File Database Reference files for locations Reference files for companies TAF TSI Metadata (self contained schemas)

CI - Common Interface TAF/TAP TSI Common Interface (CI) for data exchange between IMs/RUs and

between RU Locally installed Could be used also for messages outside the regulation

CA - Certification Authority All actors require a X509 certificate for secure communication

CA is established RNE provides the X509 certificates for TLS/SSL

Regulation 1305/2014 and 454/2011

Telematics Application for Freight Services and Telematics Application for Passenger Services

Both Regulation requires from Rail Industry to support certain business processesby exchanging of standardized messages.

Involved Actors are: Infrastructure Manager (IM) Railway Undertakings (RU)Waggon keeper (WK) Station Master (SM)

11 February 2016 4

Legal background

Joint IM-RU Functions

Reference Files Common Interface Short Term Path Request Train Preparation Train Running Information Train Forecast Service Disruption Deviations from plan (TAP) (Train Identifiers)

RU (fright) Only Functions *

Consignment Note DataWIMOWagon Movement Shipment ETA

* Commercial part of TAP is notconsidered in the table

11 February 2016 5

TAF TSI Functions Grouped

11 February 2016 6

TAF TSI Business Process & RNE Applications

Reference Files and Common Interface

Short Term Path Request

Train Run & Service disruption?

11 February 2016 7

TAF TSI Business Process & RNE Applications

4.2.11.1 Reference Files

For the operation of freight trains on the European network the followingreference files must be available and accessible to all service providers (IMs,RUs, logistic providers and fleet managers)...

Centrally stored and administrated: Reference File of the Coding for all IMs, RUs, Service provider companies; Reference File of the Coding for Freight Transport Customers; Reference File of the Coding of Locations (Primary and subsidiary).

11 February 2016 8

Regulation 1305/2014

4.4.1 Data Quality

For data quality assurance purposes, the originator of any TSI message willbe responsible for the correctness of the data content of the message at thetime when the message is sent.Where the source data for data quality assurance purposes is available from

the databases provided as part of the TSI, the data contained within thosedatabases must be used for data quality assurance.….

11 February 2016 9

Regulation 1305/2014

11 February 2016 10

Allocation of Company Codes

Companies Passenger Freight Infrastructure Others

527 196 328 105 68

subscribe check,register

maintainCRD

Access tocompany

codes

Companies UIC(Allocation Entity)

CRD(operated by RNE ) TAF / TAP Actors

Subscription +Maintenance Fee

UIC – RNEMaintenance Agreement

CCSUser Agreement

Status of registered Companies December 2015

http://www.uic.org/rics

Apply for a Company code at European central entity

At the time being this is UIC, independent if company is UIC member or not

It is the same as known by “RICS” code

Apply at http://www.uic.org/rics

After registration the company code will be maintained in the CentralReference File Database (CRD)

11 February 2016 11

Get registered as Company

Location is a place, a geographic point, inside or outside the rail network, which is needed to

be identified for operational, technical, administrative or statistical purposes. This canbe either a Railway or a Customer location

Primary Location This location is a network rail point managed by an Infrastructure Manager (IM). Code is managed nationally by an allocation entity

• May be an Infrastructure Manager• May be a national Location entity

11 February 2016 12

Reference File Location

Trains can start, end, stop, change line and time needs to be provided.

11 February 2016 13

Primary Location Examples

Subsidiary Location identifies a location as a part of primary location e.g. ajunction, a signal, a marker point, etc. This may be a non-rail point or a railpoint that is not managed by an Infrastructure Manager (IM).

Subsidiary location without Primary location is not possible. It is always in combination with a Primary Location.

Subsidiary locations have “subsidiary type code”

11 February 2016 14

Subsidiary Location

11 February 2016 15

Subsidiary Location Examples

11 February 2016 16

Subsidiary Location Type

CommonComponents System

1711 February 2016

Central Reference Files Database (CRD) * Coding of Locations and Companies Common Metadata

Certificate Authority * which provides X509 certificates for secure communication

Common Interface (CI) a software package which is locally installed within the user’s IT environment

*) In the regulation also mentioned as Central Repository Domain

11 February 2016 18

What is the Common Components System?

11 February, 2016 19

Who developed CCS?The TAF TSI Common Components Group (CCG) a Special Group of UIC havedeveloped the CC and are in roll-out since January 2012.

50 Stakeholders Main European Infrastructure Managers and some smaller ones

o DB Netz, RFF, RFI, Infrabel, ProRail, PLK, MAV, NetworkRail, Eurotunnel, etc. Largest Freight Railway Undertakings and some smaller ones

o DB Schenker Group, SNCF fret, Trenitalia, RCA, Green Cargo, etc.

Current Supplier (contractor) EVRY - largest IT supplier in Nordic countries

The CCG General Assembly on 9 December 2014 approved the transfer of theCommon Components to RNE with all the verification transfer conditionssuccessfully implemented.

The CCG was dissolved on 31 December 2014.

What was Transferred?: Software IP Rights (IPR) Service Contracts

As of 1 January 2015, RNE is now in charge of further development, maintenanceand on-going operations of the TAF–TAP Common Components.

11 February 2016 20

Transfer of the CC to RNE

11 February 2016

How to feed the Reference files

Common Interface

Routingand

Security

A

B

C

D

Configuration

Mapping

Metadata

CRD

1)

2)

3)

Https

CSV file

WEB GUI(Browser)

Legacy locationdatabase

(messaging)

Maintenance of location reference files by national entities(or registered companies for defined subsidiary type codes)

Central ReferenceFile Database (CRD)

Location codes:- Primary- Subsidiary

11 February 2016 22

Reference file distribution

CRD

CI local Instance

Company

Legacy System

• Reference file download via authenticated WSdirectly to a legacy system

• Filter parameters• Search Export via HMI

• Filter parameters (e.g. last modified date,country, subsidiary type code)

• Search and export via Browser on Local Instance• Reference file download via WS to Legacy System

• Filter parameters (e.g. last modified date,country, subsidiary type code)

• Scheduler to be defined by Legacy System

• Replication Reference files via Web Service (WS) to Local Instance• Filter parameters (e.g. last modified date,

country, subsidiary type code)• Scheduler defined by Local Instance of CI

11 February 2016 23

Status of Location Codes

At least 1 large IM published

Not populated yet

Non ex CCG IM

~ 57.000 Primary Locations for 39 IM~ 330 Subsidiary Location Type 36~ 330 Subsidiary Location Type 42~ 17.000 Subsidiary Location Type 41

In Progress

01/2016

Common Interface

2411 February 2016

4.2.12.6. Common interface

The common interface is mandatory for each actor in order to join the rail interoperability community

The common interface has to be able to handle: message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of the outgoing messages, authenticity verification of the incoming messages decryption of incoming messages conformity checks of incoming messages according to metadata, handling the single common access to various databases

Where a Common Interface is in common use with the TAP TSI, the development and changes must be in linewith TAP TSI, in order to achieve optimum synergies.

11 February 2016 25

Regulation 1305/2014

11 February 2016 26

Architecture Supporting Peer2Peer

IP Network

CRDCI

ISR

CI

Orfeus

RU

CI

RU

CI

IM 1

CI

IM 2

CI

SM

CI

RU

CI

RU

CI

RU

CI

RU RU

CI

CI

Reference files• Location ID• Company ID

Common Meta Data

Certificate Authority

WagonRef. Files

WagonRef. Files

CI - Common InterfaceIM - Infrastructure ManagerRU - Railway UndertakingHMI - Human Machine InterfaceSM - Station MasterCRD – Central Reference File Database

HMI

11 February 2016 27

Common Interface Reference Implementation

11 February 2016 28

Communications

11 February 2016 29

Certificate Authority (CA)RNE acts as a Certificate Authority (CA) and provides X-509 certificates tosupport secure communication between partners, along with message-basedencryption and signature.

X-509 certificates are requested for: SSL/TLS communication on Https between CI A and CI B, and between CI A /

CI B and CRD Encryption of messages Signature of messages.Only certificates from the RNE Certificate Authority (with the same root) willtrust each other.

The Common Interface Reference Implementation was build by the TAF TSICommon Components Group based on Requirements

TAF 4.2.14.7. Common interface TAP 4.2.21.7. Common Interface for RU / IM Communication TAF Appendix E : TAF TSI Appendix D.2:

Appendix E COMMON INTERFACE

European public tender Stakeholder funding EU Commission funding

11 February 2016 30

CI Reference Implementation

11 February 2016 31

Mapping Definition

11 February 2016 32

Message Processing Graphical Overview

33

Status on Common Interface implementation

10 CI in Test

26 CI with Data exchange

CI = Common Interface

01/2016

Adapted Price Model from 1st January 2016

Common Interface One off Registration Fee – € 4.000

• Yearly Maintenance Fee – € 2.400

Reference Files One off Registration Fee – € 1.400

• Yearly Maintenance Fee – € 900

11 February 2016 34

Price Model

Access to CCS for TAF and TAP actors is based on a user agreement that needsto be signed beforehand:

In order to become a CCS User Please provide the following information tosupport.ccs@rne.eu:

Name, company and department Contact details (phone, e-mail, postal address)

More information about CCS can be found on our website at:http://ccs.rne.eu

11 February 2016 35

How to become a CCS user?

36

Thank you!