1tap masterplanning kick-off25 september 2012 tap tsi masterplanning overview of ru/im obligations...
TRANSCRIPT
1TAP Masterplanning kick-off 25 September 2012
TAP TSI Masterplanning
Overview of RU/IM obligations
Masterplanning Kick-offBrussels, 25 September 2012
2TAP Masterplanning kick-off 25 September 2012
The goal of TAP RU/ IM standards is providing interoperability…
TAP RU/ IM functions take into account different stakeholders than TAF, with an overlap on the IM side
Providing passengers with important travel information on all rail journeys
This is different to TAF
Involved actors: - Infrastructure Managers - Passenger RUs - Station Managers
… for Passengers
Railway companies can – with the same standards for domestic and interoperable services -- order train paths- control and manage their train
services- improve passenger information
… for Rail Companies
Station Managers (SMs) in the sense of TAP are entities responsible for passenger information in the stations
SMs and Passenger RUs are actors that fall under TAP and have had limited or no implication by TAF
3TAP Masterplanning kick-off 25 September 2012
TAP RU/ IM functions are close to TAF RU/ IM Communication
Overview of TAP RU/ IM functions
Short Term Path
Requests
Train Preparation
Train Running Info + Forecast
Service Disruption
Very close to TAF
Close to TAF Other TAF functions not relevant1
Close to TAF Involving SMs Other TAF functions not relevant2
Relation to TAF
Close to TAF Triggers further communication
Dialogue between RU and IM to order or modify paths
Info from RU to IM that train is ready/not ready
Info from IM to RU and SM about punctuality
Content
Info from IM to RU/SM that train stopped and continuation is unclear
1) TAF functions for Train Preparation not relevant for TAP: Train Accepted, Train Composition, Train Not Suitable, Train Position, Train at Start
2) TAF functions for Train Running not relevant for TAP: all Enquiries and Enquiry Responses
Functions
4TAP Masterplanning kick-off 25 September 2012
TAP RU/ IM functions are clustered for the MasterplanningDescription in the Regulation and the Implementation Guide
Reference of TAP RU/ IM functions
Short Term Path
Requests
Train Preparation
Train Running Info + Forecast
Service Disruption
chapter 12
chapter 13
chapter 14, 18
RU/IM Implementation Guide1
chapter 15, 18
BP 4.2.17
BP 4.2.14
BP 4.2.15
TAP Regulation
BP 4.2.16
1) The RU/IM IG contains a “Who should read what”-section that is advised to be consulted. All general chapters (Part A and D) should be read for all clusters. The RU/IM Implementation Guide is available at http://tap-tsi.uic.org/IMG/pdf/20120629_tap_ru_im_implementation_guide_v53c.pdf
Reference
5TAP Masterplanning kick-off 25 September 2012
Some TAP RU/ IM functions are new and not relevant for TAF
Additional TAP RU/ IM functions
Change of Track
Train Journey Modified
Passenger information; not relevant for TAF
Relation to TAF
Info from IM to RU/ SM about platform
Info during operation from IM/ RU to SM that train is rerouted, cancelled etc.
Content
Passenger information; not relevant for TAF
Info in stations
Info in vehicles
Passenger information; not relevant for TAF
Passenger information; not relevant for TAF
Info from SM to customer (content only)
Info from RU to passenger (content only)
Functions
6TAP Masterplanning kick-off 25 September 2012
TAP RU/ IM functions are clustered for the MasterplanningDescription in the Regulation and the Implementation Guide
Reference to TAP RU/ IM functions
Change of Track
Train Journey Modified
BP 4.2.12 chapter 17, 19
chapter 16, 19
RU/IM Implementation Guide1
BP 4.2.12
TAP Regulation
1) The RU/IM IG contains a “Who should read what”-section that is advised to be consulted. All general chapters (Part A and D) should be read for all clusters.
Info in stations
Info in vehicles
chapter 19
chapter 19
BP 4.2.12
BP 4.2.13
Reference
7TAP Masterplanning kick-off 25 September 2012
Standard interfaces to allow communication between stakeholdersvia standard data networks
CI
CI CI
CI
Common Reference data. Location-ID Company-ID
IP Network
RU 1 RU 2
IM 1
CI
IM 2CI
SM 1
CI
CUS
illustrativ
CI = Common InterfaceCUS = Commonly Used System
IM = Infrastructure ManagerRU = Railway UndertakingSM= Station Manager
CIRU 3
General architecture of the RU/IM communication
8TAP Masterplanning kick-off 25 September 2012
TAP RU/ IM prerequisites are very close to TAF TSI
Overview of TAP RU/ IM prerequisites
Reference Files
Common Interface
Train Identifiers
Governance
Very close to TAF
CCG CI is available Individual solutions possible1
Phased approach using existing identifiers is developed in collaboration with TAF2
Relation to TAF
Not specified yet
Data on Locations, Countries, Companies
Tools to allow interoperable message exchange
Unambiguous identification for IT applications
Not replacing rail operational numbers
Content
Availability of rules for standards and common elements
1) Companies can implement own solutions conform to the reference CI, allowing the exchange of TAP messages2) Start using TAP messages with existing identifiers, move towards technical identifiers as developed by TAF, partners need to agree
on migration
Functions
9TAP Masterplanning kick-off 25 September 2012
TAP RU/ IM prerequisites are very close to TAF TSI
Reference to TAP RU/ IM prerequisites
Reference Files
Common Interface
Train Identifiers
Governance
chapter 9
chapter 6
chapter 8 and Train ID handbook2)
chapter 23
BP 4.2.19
BP 4.2.21
n/a
n/a
RU/IM Implementation Guide1TAP Regulation
1) The RU/IM IG contains a “Who should read what”-section that is advised to be consulted. All general chapters (Part A and D) should be read for all clusters.
2) The Train ID Handbook is available at http://www.uic.org/IMG/pdf/111122_wg_10_handbook_final.pdf
Reference
10TAP Masterplanning kick-off 25 September 2012
Reference data is technically centrally, but code allocation needs to be organised per country
Questions mainly for Infrastructure Managers and National Contact Points
When will your company/country
– identify the Code Allocation Entity in your country ?
proposed is that the largest IM in a country should execute this role or take care that this role is defined within their country
– be able to populate the reference file ?
– sign up to be registered on Reference File System (CRD) to execute tests ?https://crd.tsi-cc.eu/CRD/onlineUser/signUp.action
11TAP Masterplanning kick-off 25 September 2012
The RU/IM Implementation Guide together with the message catalogue is the main result of Phase One and the base for implementation
12TAP Masterplanning kick-off 25 September 2012
Commercial solutions outside the TAP legal frame are being prepared by some sector organisations
Availability of support from stakeholder groups
Commercial/voluntary support of activities outside the legal TSI frame
Related initiatives such as PCS1 can support IMs and RUs on a voluntary basis
Activities to implement TAP in these initiatives will take place after the final specifications and the ability of users become clear
The reference implementation of the Common Interface is available and can be used. More information: [email protected]
Specifications TAP RU/ IM standards have been finalised
by May 2012; going through CCM now
Usability Ability of companies to use the standards
needs to be known via TAP Masterplan
1) Path Co-ordination System
13TAP Masterplanning kick-off 25 September 2012
Future: Both mandatory RU/ IM work to fulfil the regulation as well as useful work to fulfil stakeholder requirements will start immediatly
Check the external specifications of the reference implementation of the CI (CCG CI). Relevant for TAF and TAP
Clarify stakeholder questions on deliverables
Check/enhance messages for Short Term Path Request for
– Annual Path Requests
– One Stop Shops
– Coach Group (through coaches) Code list maintenance
Create a wagon ordermessage for passenger information
– This is relevant for TAP only
Enhance work on Train Identification (see also previous slide)
– Create technical messages needed for TAF and TAP
– to accommodate passenger specific requirements
Regulation driven Sector driven
Most points are valid forboth TAF and TAP
A common TAP and TAF RU/ IM workstream will deal with these topics.The results will add to the existing baseline/standards.
14TAP Masterplanning kick-off 25 September 2012
Reference documents for RU/IM Communication
The following links host the reference documents for RU/IM communication
RU/IM Implementation Guidehttp://tap-tsi.uic.org/IMG/pdf/20120629_tap_ru_im_implementation_guide_v53c.pdf
Annexes to the RU/IM Implementation Guidehttp://tap-tsi.uic.org/What-s-new,4.html
Train ID handbookhttp://www.uic.org/IMG/pdf/111122_wg_10_handbook_final.pdf
The following links host additional information or orientation from TAF Masterplanning with RU/IM relevance
TAF Masterplan resultshttp://www.era.europa.eu/Document-Register/Documents/TAF-TSI%20Preliminary%20Master%20Plan.pdf
General TAF links and information
http://www.uic.org/spip.php?article446