TAF TSI – Master Plan Brussels, 25 September 2012 Information Workshop.

TAF TSI – Master Plan

Brussels, 25 September 2012

Information Workshop

2Telematic Applications for Freight

Agenda

• Introductions

• Master Plan– Master Plan Timelines– Consolidated Master Plan– Timeline

• Governance Structure– Merged RU/IM Governance– Expert Working Groups Roles and Responsibilities– RU Representation– Change Management Requirements

• The TAF TSI Functions Explained

• Common Components

• Questions and Answers


MASTER PLAN

Master Plan Timelines

Consolidated Master Plan

Timeline


Master Plan Responses

Infrastructure ManagersTrack-Kms

re-sponded

85%

no re-sponse

15%

Railway UndertakingsTonne-Kms

re-sponded

78%

no re-sponse

22%


Master Plan Status

• DT Produced and Delivered Master Plan – 10 May 2012– Launched in January 2012

• Preliminary Master Plan is now Published on ERA Website– http://www.era.europa.eu/Document-Register/Pages/CR-TAF

-TSI.aspx

• Database was updated and new Queries were developed

• Complete Corridor analysis has been prepared

http://www.era.europa.eu/Document-Register/Pages/CR-TAF-TSI.aspx



Functions Grouped

Joint IM-RU Functions• Train Running Information

• Train Forecast

• Service Disruption

• Train Enquiries

• Train Preparation

• Infrastructure Restrictions

• Adhoc Path Request

• Common Interface

• Reference Files

• (Train Identifiers)

RU Only Functions• Consignment Note Data

• WIMO

• Wagon Movement

• Shipment ETA


Master Plan Results

2010

2011

2012

2013

2014

2015

2016

2017

2018

2019

2020

2021

2022

2023

2024

2025

2026


Master Plan Target Implementation Dates

2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026

TID final

Train Composition

Train Ready

Service Disruption

Shipment ETA

Short term PR

Train Run

Consignment Data

WIMO

Wagon movement

RSRD

Reference files population

Common interface implementation


Consolidated Master Plan

• No company may be obligated to respect another date other than submitted

• Consolidation with application solutions to be delivered by 3rd Quarter 2012


THE TAF TSI FUNCTIONS EXPLAINED


Reference Documentation

• All references can be found on the UIC site– eBusiness > TAF TSI > CR TAF TSI (

http://www.uic.org/spip.php?article446)

• Directive 2001-16– http://eur-lex.europa.eu/smartapi/cgi/sga_doc?smartapi!cele

xapi!prod!CELEXnumdoc&numdoc=32001L0016&model=guichett&lg=en

• TAF TSI Regulation– http://ec.europa.eu/transport/rail/interoperability/interoperabil

ity/telematic_applications_en.htm#top

• Strategic European Deployment Plan (SEDP)– http://www.era.europa.eu/Document-Register/Pages/CR-TA

F-TSI.aspx

http://www.uic.org/spip.php?article446

http://eur-lex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexapi!prod!CELEXnumdoc&numdoc=32001L0016&model=guichett&lg=en



http://ec.europa.eu/transport/rail/interoperability/interoperability/telematic_applications_en.htm#top

http://ec.europa.eu/transport/rail/interoperability/interoperability/telematic_applications_en.htm#top




Implementation Guidelines

• The Implementation Guidelines are available on the UIC site :– > eBusiness > TAF TSI >

TAF Deployment– http://www.uic.org/spip.php?

article447

• CRD

• Train Monitoring

• Train Preparation

• Short Term path request

• Wagon Order

• Wagon Movement

• Reference files (not in CRD)

• RSRD

• Train IDent




Source Documents

Content Source

TAF TSI http://www.uic.org/spip.php?article446

Masterplan http://www.era.europa.eu/Document-Register/Documents/TAF-TSI%20Preliminary%20Master%20Plan.pdf

TAF Implementation Guides


Implementation Guide Reference Files

http://tap-tsi.uic.org/What-s-new,4.html#outil_sommaire_7

Import template http://www.uic.org/spip.php?article447

Company Code http://www.uic.org/spip.php?article311

Sign up for CRD https://crd.tsi-cc.eu/CRD/Login.action


http://www.era.europa.eu/Document-Register/Documents/TAF-TSI%20Preliminary%20Master%20Plan.pdf

http://www.era.europa.eu/Document-Register/Documents/TAF-TSI%20Preliminary%20Master%20Plan.pdf






https://crd.tsi-cc.eu/CRD/Login.action


Source Documents - Metadata

• Catalogue Version 5-2 will be published by ERA 4Q 2012 as draft version

• To be submitted to RISC for final approval

• DT Working Draft 5.2.1 shall be used for implementation and will be published on the ERA website as ‘Developer Version’

• Impacted issues– Timetable and Path Request messages (WG5 – Joint Planning)– Train composition (WG 3 – Joint Operations)

• DT will provide ‘self-contained’ schemas by Message also so to be published by ERA


GOVERNANCE STRUCTURE


Governance Evolution - Proposed

……

TAF SteCo(like today)

TAP SteCo(like today)

Joint SteCo(as agreed by SteCos)

TAP ProjectManager

UIC PMO1

Masterplan

Phase 3 gov. devpt.

Retail ITprocurement

Full-Service Model

Member of JSG

Planning

Operations

IT & Ref.Data

Train ID

TAF Joint Sector Group

TAF Deployment

Manager

Jointly staffedTAF-TAP

RU/IMactivities asagreed byTAF & TAP

Joint RU/IMStream Lead

input2 and support

TAF Deploym. & Impl. Activities

TAP CommonSupport Group

advice

input and support


EG 1 - Planning

• EG 1 – Planning - Deliverables

• Change Requests for message catalogue concerning path request

• Change Requests for path request related code lists

• Updated implementation guidelines especially to reflect Change Requests

• If necessary, proposal of modification for TAP TSI and TAF TSI core text


EG 2 - Operations

• EG 2 – Operations - Deliverables

• Change Request for message catalogue and updated implementation guidelines concerning operations

• Change requests for new messages and new chapters for implementation guidelines for passenger train composition

• Change Request for operations related code lists

• If necessary, proposal of modification for TAP TSI and TAF TSI core text


EG3 – IT and Reference Data

• EG 3 – IT and Reference data - Deliverables

• Change requests for message catalogue and update implementation guidelines concerning reference data (if required)

• Change request for reference data related code lists


EG 4 – Train ID

• EG4 – Train ID - Deliverables

• Change Requests for message catalogue and updated implementation guidelines concerning the identifiers

• Change Requests for new messages and new chapters for implementation guidelines for creation/updating identifiers

• Review document of the current state of the stakeholder impact analysis

• Pilot plan for use of new identifiers, including identification of stakeholders able for transmitting messages containing Train ID for testing/piloting


5.2 Short-term workplan (6-months)

• Consolidated plan– Due six months after publication, proposed delivery end of November– Set up the necessary expert groups– DT to visit the outliers – see if there is any room to speed up

implementation or find interim approaches– Develop detailed workplan for implementation

• Work in cooperation with the established working groups (RU and IM)

• Consolidation of TAF and TAP plans for RU and IM…

• Change Control Management – Consolidated input to ERA

• Workshops


Realisation of the Reference File Function

Master Plan

16%

81%

1% 2%

57%

34%

4% 5%

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Reference files population IM Reference files population RU

Requirements

• Location Ident

• Company Ident

• (Country Code)


Reference File Country

• Identified by the Country Code ISO 3166-1 alpha-2

• optional attribute – UIC Country Code

(leaflet 920-14)


Reference File Company

• Companies– Railway Companies– Other Transport bodies– Any company involved

in the rail transport chain

• Centrally allocated and managed

• http://www.uic.org/spip.php?article311

• Identified by a 4 numeric number


Reference File Location

• 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 can be either a Railway or a Customer location

• Primary Location – This location is a network rail point managed by an

Infrastructure Manager (IM).– Managed nationally by an allocation entity


Primary Location Identifier

• Primary Location– 2AN ISO country code– 5N LocationPrimaryCode


Subsidiary Location

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

• It is unique and is always used in combination with a Primary Location.


Subsidiary Location Identifier

• Country Code (2AN)

• LocationPrimaryCode (5N)

• LocationSubsidiaryType Code (2AN)

• LocationSubsidiaryCode (10AN)

• AllocationCompany (4N)


Location Subsidiary Type Code

• This element details a Subsidiary Location by its LocationSubsidiary Type Code.


LocationIdent (XML)


Realisation of the Common Interface Function

Master Plan Requirements

• Implementation of CI– Installation– Configuration– Ready for Message Exchange

• End to End• Legacy System Configuration

7%

89%

2% 2%

57%

28%

10%

5%

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Common interface implementation IM Common interface implementation RU


Realisation of the Train Identifier(s)

Master Plan

0%

16%

19%

6%

16%

39%

2%

11%

1%

52%

16%

3% 3%

11%

0%

10%

20%

30%

40%

50%

60%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

TID final IM TID final RU

Requirements

• Train Identifiers– unique ID for all trains over the

complete lifecycle of the train Configuration

– Includes Pathident, Dossier numbers, path request id, etc

– Implementation Guide– Phased approach with pilot


Realisation of Path Requests

Master Plan Requirements • The following messages used

for Path request must be sent– Path Request RU to IM– Path Details IM to RU– Path Confirmed RU to IM– Path Details Refused RU to IM– PathDossier RU to IM (New

Requirement)

• Implementation Guide Available

3%

16%

23% 24%

5%

22%

7%

4%

11% 11%

61%

9%

2%1%

0%

10%

20%

30%

40%

50%

60%

70%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Short term PR IM Short term PR RU


Realisation of Train Preparation

Master Plan Train Ready

• This message is sent from an RU to IM indicating that the train is ready for access to the network.

3%2%

16%

9%10%

24%

9%

19%

7%

4%

14%

9%

6%7%

59%

1%

0%

10%

20%

30%

40%

50%

60%

70%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Train Ready IM Train Ready RU


Realisation of Train Preparation

Master Plan Train Composition

• This message is sent from an RU to an IM defining the composition of the proposed train

3%

7%

22%

14%

7%

9%

27%

4%

42%

22%

9%

3%

5%

12%

2%1%

0%

5%

10%

15%

20%

25%

30%

35%

40%

45%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Train Composition IM Train Composition RU


Realisation of Train Running Function

Master Plan Train Running Function

• Train Running Message

• Train Running Forecast Message

• Train Delay Cause Message23%

35%

7% 7%

11%

8%

2%

7%

24%

6%

3%

52%

12%

3%1%

0%

10%

20%

30%

40%

50%

60%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Train Run IM Train Run RU


Realisation of Service Disruption

Master Plan Service Disruption• Train Running Interrupted

Message– This message is issued by the

IM to the neighbouring IM and to the RU that has contracted the path if the train run is interrupted.

3%

13%

32%

5%

11% 10%

19%

7%

24%

6%

3%5%

59%

0% 1%

0%

10%

20%

30%

40%

50%

60%

70%

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021

Service Disruption IM Service Disruption RU


Conclusions/Experience

• IM’s may indicate that they wish to have their common IM/RU Functions aligned with TAF submission – data and response is on file

• Please try to provide as much information as possible so that the evaluation team is able to identify any dependencies

• Have a good uderstanding of the functional requirements

• Realistically address the effort in your own company

• Get buy-in on strategic level in your company


COMMON COMPONENTS


What are the Common Components?

• Central Repository Domain (CRD)

– Reference Files (Locations, Companies)– Certificate Authority– Common Metadata

• Common Interface (CI)


Regulation 62 / 2006

4.2.14.6 Central repository

– The central repository must be able to handle:

– metadata — structured data describing the content of messages,– Public Key Infrastructure (PKI),

– Certification Authority (CA),


Regulation 62 / 2006

• 4.2.14.7. 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.


ISR

CI

PCS TIS

CI

IP

Network

Reference files• Location ID• Company ID

Common Meta Data

C.A. PKI

IM 1

CI

IM 2

CI

IM 3

CIRU

CI

RU

CIRU

CIRU R

U

CI

HMI

CI

CI

IM = Infrastructure ManagerRU = Railway Undertaking

HMI = Human Machine Interface

RU

CI

RU

CI

Orfeus

Wagon Ref. Files

Wagon Ref. Files

Architecture Supporting Peer2Peer


Common InterfaceReference Implementation

Time Table systems

Production systems

• Preprocessing• Normalization• Translation

• Validation

Remote LIConfiguration

• Host• Protocol

• Company ID

WS

• Metadata•Private

•Common•Shared

• Mappings• (Reference files)

IP Network

• Message-•Compression

•Signature•Encryption

• Routing• Security

• Transport

SOAP (HTTP) , JMS, FTP, File SMTP, JMS-MQ, „IP-Socket“

Supported protocols

Supported formatsXML, Text, CSV, UIC Leaflet 407-1

Connectors

WSFTP

WSWSWS

WSWSWMQ

WSWS…

SpecificConnector-

Configuration

Common Interface (Software)

MySQLJava EE, CI Application components, Java PKI APIs

Jboss Application Server, Jboss ESB, Struts2

……

…… SOAP (Https)xml (UTF8)


What You Can Expect

• Multiple Instances, if desired

• Installation Support

• Documentation and User Manuals

• Service Desk– On-line Ticket Support– Telephone Support – Working Hours– Hot-line Support – 24hour incident management


Reference Implementation

Hardware to be provided by CompaniesWin OS, Linux RedHat Enterprise

LI Installation is automated using Install Jammer and bundled as executable .

Separate installable for Windows and Linux platforms.

It include following software :

MySQL 5.xJava 1.6.14JBoss AS 6 with ESB CI application components

All Administration screens are running in a Web browserLanguage of all documentation and user guide is English


Common Interface Function

• Common Interface Reference implementation delivered 2nd January 2012

• When will your company (As established in the Master Plan?)– Be able to install the Common Interface?

• Common Components Group just define the registration rules to use the Reference Implmentation– ….. in a way which is satisfactory both for above stakeholders and for the “new

comers” in particular with view to fair cost sharing.

– Be able to connect it to the TAF-TSI Legacy Systems?

– Start communications with other TAF-TSI Stakeholders using the TAF formats?


QUESTIONS AND ANSWERS

TAF TSI – Master Plan Brussels, 25 September 2012 Information Workshop.

Documents

Transcript of TAF TSI – Master Plan Brussels, 25 September 2012 Information Workshop.