Transcript SEDP Report - TAP-TSI

TAF TSI – Master Plan
Brussels, 25 September 2012
Information Workshop
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
Telematic Applications for Freight
2
Master Plan Timelines
Consolidated Master Plan
Timeline
MASTER PLAN
Telematic Applications for Freight
3
Master Plan Responses
Infrastructure Managers
Track-Kms
Railway Undertakings
Tonne-Kms
no
response
15%
no
response
22%
responde
d
85%
Telematic Applications for Freight
responde
d
78%
4
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/CRTAF-TSI.aspx
• Database was updated and new Queries were
developed
• Complete Corridor analysis has been prepared
Telematic Applications for Freight
5
Functions Grouped
Joint IM-RU Functions
RU Only Functions
•
Train Running Information
•
Consignment Note Data
•
Train Forecast
•
•
WIMO
Service Disruption
•
Train Enquiries
•
Wagon Movement
•
Train Preparation
•
Shipment ETA
•
Infrastructure Restrictions
•
Adhoc Path Request
•
Common Interface
•
Reference Files
•
(Train Identifiers)
Telematic Applications for Freight
6
Master Plan Results
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
Telematic Applications for Freight
7
Master Plan Target Implementation Dates
Common interface implementation
Reference files population
RSRD
Wagon movement
WIMO
Consignment Data
Train Run
Short term PR
Shipment ETA
Service Disruption
Train Ready
Train Composition
TID final
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026
Telematic Applications for Freight
8
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
Telematic Applications for Freight
9
THE TAF TSI FUNCTIONS
EXPLAINED
Telematic Applications for Freight
10
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://eurlex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexapi!prod!CELE
Xnumdoc&numdoc=32001L0016&model=guichett&lg=en
• TAF TSI Regulation
– http://ec.europa.eu/transport/rail/interoperability/interoperability/tel
ematic_applications_en.htm#top
• Strategic European Deployment Plan (SEDP)
– http://www.era.europa.eu/Document-Register/Pages/CR-TAFTSI.aspx
Telematic Applications for Freight
11
Implementation Guidelines
• CRD
• Train Monitoring
• Train Preparation
• Short Term path request
• Wagon Order
• Wagon Movement
• Reference files (not in CRD)
• RSRD
• Train IDent
• The Implementation
Guidelines are available on
the UIC site :
– > eBusiness > TAF TSI >
TAF Deployment
– http://www.uic.org/spip.php?
article447
Telematic Applications for Freight
12
Source Documents
Content
Source
TAF TSI
http://www.uic.org/spip.php?article446
Masterplan
http://www.era.europa.eu/DocumentRegister/Documents/TAFTSI%20Preliminary%20Master%20Plan.pdf
TAF Implementation
Guides
http://www.uic.org/spip.php?article447
Implementation Guide
Reference Files
http://tap-tsi.uic.org/What-snew,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
Telematic Applications for Freight
13
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
Telematic Applications for Freight
14
GOVERNANCE STRUCTURE
Telematic Applications for Freight
15
Governance Evolution - Proposed
TAF SteCo
Joint SteCo
TAP SteCo
(like today)
(as agreed by SteCos)
(like today)
Member
of JSG
TAF Joint
Sector
Group
TAF
Deployment
Manager
UIC PMO1
input 2 and support
TAF Deploym. &
Impl. Activities
…
…
Jointly staffed
TAF-TAP
RU/IM
activities as
agreed by
TAF & TAP
TAP Project
Manager
Joint RU/IM
Stream Lead
advice
TAP Common
Support Group
input and support
Planning
Masterplan
Operations
Phase 3
gov. devpt.
IT & Ref.
Data
Retail IT
procurement
Train ID
Full-Service
Model
Telematic Applications for Freight
16
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
Telematic Applications for Freight
17
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
Telematic Applications for Freight
18
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
Telematic Applications for Freight
19
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
Telematic Applications for Freight
20
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
Telematic Applications for Freight
21
Realisation of the Reference File Function
Master Plan
Requirements
90%
81%
80%
• Location Ident
70%
60%
57%
• Company Ident
50%
40%
34%
• (Country Code)
30%
20%
16%
10%
5%
4%
1%
2%
0%
2011
2012
2013
2014
2015
Reference files population IM
2016
2017
2018
2019
2020
2021
Reference files population RU
Telematic Applications for Freight
22
Reference File Country
• Identified by the
Country Code ISO
3166-1 alpha-2
• optional attribute
– UIC Country Code
(leaflet 920-14)
Telematic Applications for Freight
23
Reference File Company
• Companies
– Railway Companies
– Other Transport bodies
– Any company involved
in the rail transport
chain
• Identified by a 4
numeric number
• Centrally allocated
and managed
• http://www.uic.org/spip
.php?article311
Telematic Applications for Freight
24
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
Telematic Applications for Freight
25
Primary Location Identifier
• Primary Location
– 2AN ISO country code
– 5N LocationPrimaryCode
Telematic Applications for Freight
26
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.
Telematic Applications for Freight
27
Subsidiary Location Identifier
• Country Code (2AN)
• LocationPrimaryCode (5N)
• LocationSubsidiaryType Code (2AN)
• LocationSubsidiaryCode (10AN)
• AllocationCompany (4N)
Telematic Applications for Freight
28
Location Subsidiary Type Code
• This element details a Subsidiary Location by its
LocationSubsidiary Type Code.
Telematic Applications for Freight
29
LocationIdent (XML)
Telematic Applications for Freight
30
Realisation of the Common Interface Function
Master Plan
Requirements
100%
89%
90%
• Implementation of CI
80%
70%
60%
– Installation
– Configuration
– Ready for Message Exchange
57%
50%
40%
28%
30%
20%
10%
10%
7%
5%
2%
2%
0%
2011
2012
2013
2014
2015
Common interface implementation IM
2016
2017
2018
2019
2020
2021
• End to End
• Legacy System Configuration
Common interface implementation RU
Telematic Applications for Freight
31
Realisation of the Train Identifier(s)
Master Plan
Requirements
60%
• Train Identifiers
52%
50%
39%
40%
30%
20%
19%
16%
16%
16%
11%
11%
10%
6%
3%
0%
0%
2011
2012
2013
3%
2%
1%
2014
2015
TID final IM
2016
TID final RU
2017
2018
2019
2020
2021
– 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
Telematic Applications for Freight
32
Realisation of Path Requests
Master Plan
Requirements
• The following messages used
for Path request must be sent
70%
61%
60%
– Path Request RU to IM
50%
– Path Details IM to RU
40%
– Path Confirmed RU to IM
30%
23%
24%
22%
– Path Details Refused RU to IM
20%
16%
11%
11%
9%
10%
3%
7%
5%
4%
2%
1%
0%
2011
2012
2013
2014
2015
Short term PR IM
2016
2017
2018
2019
2020
2021
– PathDossier RU to IM (New
Requirement)
Short term PR RU
• Implementation Guide
Available
Telematic Applications for Freight
33
Realisation of Train Preparation
Master Plan
Train Ready
70%
• This message is sent from
an RU to IM indicating that
the train is ready for access
to the network.
59%
60%
50%
40%
30%
24%
19%
20%
14%
16%
9%
10%
10%
9%
6%
3%
9%
7%
7%
4%
2%
1%
0%
2011
2012
2013
2014
2015
Train Ready IM
2016
2017
2018
2019
2020
2021
Train Ready RU
Telematic Applications for Freight
34
Realisation of Train Preparation
Master Plan
Train Composition
45%
42%
• This message is sent from
an RU to an IM defining the
composition of the proposed
train
40%
35%
30%
27%
25%
22%
22%
20%
14%
15%
12%
10%
9%
9%
7%
5%
3%
7%
5%
4%
3%
2%
1%
0%
2011
2012
2013
2014
2015
Train Composition IM
2016
2017
2018
2019
2020
2021
Train Composition RU
Telematic Applications for Freight
35
Realisation of Train Running Function
Master Plan
Train Running Function
60%
• Train Running Message
52%
50%
• Train Running Forecast
Message
40%
35%
30%
23%
24%
20%
11%
12%
10%
6%
7%
8%
7%
3%
7%
3%
2%
• Train Delay Cause
Message
1%
0%
2011
2012
2013
2014
2015
Train Run IM
2016
2017
2018
2019
2020
2021
Train Run RU
Telematic Applications for Freight
36
Realisation of Service Disruption
Master Plan
Service Disruption
• Train Running Interrupted
Message
70%
– 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.
59%
60%
50%
40%
32%
30%
24%
19%
20%
13%
11%
10%
3%
10%
7%
6%
5%
5%
3%
0%
1%
0%
2011
2012
2013
2014
2015
Service Disruption IM
2016
2017
2018
2019
2020
2021
Service Disruption RU
Telematic Applications for Freight
37
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
Telematic Applications for Freight
38
COMMON COMPONENTS
Telematic Applications for Freight
39
What are the Common Components?
• Central Repository Domain (CRD)
– Reference Files (Locations, Companies)
– Certificate Authority
– Common Metadata
• Common Interface (CI)
Telematic Applications for Freight
40
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),
Telematic Applications for Freight
41
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.
Telematic Applications for Freight
42
Architecture Supporting Peer2Peer
PCS
TIS
ISR
Orfeus
HMI
CI
CI
Reference files
• Location ID
• Company ID
Common Meta Data
C.A. PKI
RU
CI
CI
IP
Network
Wagon
Ref. Files
CI
Wagon
Ref. Files
CI
RU
CI
CI
CI
IM 1
IM 2
IM 3
IM
= Infrastructure Manager
RU = Railway Undertaking
HMI = Human Machine Interface
CI
CI
CI
RU
RU
Telematic Applications for Freight
CI
R
U
R
U
R
U
43
Common Interface
Reference Implementation
Supported protocols
Time Table
systems
Production
systems
……
……
SOAP (HTTP) , JMS, FTP, File
SMTP, JMS-MQ, „IP-Socket“
Common Interface (Software)
Connectors
FTP
WS
WS
•Preprocessing
•Normalization
•Translation
•Validation
WS
WS
WS
•Message• Compression
• Signature
• Encryption
•Routing
•Security
•Transport
Supported formats
XML, Text, CSV,
UIC Leaflet 407-1
WMQ
WS
WS
…
WS
WS
Specific
ConnectorConfiguration
IP
Network
•Metadata
• Private
• Common
• Shared
•Mappings
•(Reference files)
Remote LI
Configuration
•Host
•Protocol
•Company ID
SOAP (Https)
xml (UTF8)
MySQL
Java EE, CI Application components, Java PKI APIs
Jboss Application Server, Jboss ESB, Struts2
Telematic Applications for Freight
44
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
Telematic Applications for Freight
45
Reference Implementation
Hardware to be provided by Companies
Win 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.x
Java 1.6.14
JBoss AS 6 with ESB
CI application components
All Administration screens are running in a Web browser
Language of all documentation and user guide is English
Telematic Applications for Freight
46
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?
Telematic Applications for Freight
47
QUESTIONS AND ANSWERS
Telematic Applications for Freight
48