Transcript Folie 1 - TAP-TSI

TAP TSI Masterplanning
Overview of RU/IM obligations
Masterplanning Kick-off
Brussels, 25 September 2012
TAP Masterplanning kick-off
1
25 September 2012
TAP RU/ IM functions take into account different stakeholders than
TAF, with an overlap on the IM side
The goal of TAP RU/ IM standards is providing interoperability…
… for Passengers
… for Rail Companies
 Providing passengers with important
travel information on all rail journeys
 This is different to TAF
 Railway companies can – with the
same standards for domestic and
interoperable services - order train paths
- control and manage their train
services
- improve passenger information
 Involved actors:
- Infrastructure Managers
- Passenger RUs
- Station Managers
 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
TAP Masterplanning kick-off
2
25 September 2012
TAP RU/ IM functions are close to TAF RU/ IM Communication
Overview of TAP RU/ IM functions
Content
Relation to TAF
 Dialogue between RU and
IM to order or modify paths
 Very close to TAF
 Info from RU to IM that
train is ready/not ready
 Close to TAF
 Other TAF functions not relevant1
Train Running
Info + Forecast
 Info from IM to RU and SM
about punctuality
 Close to TAF
 Involving SMs
 Other TAF functions not relevant2
Service
Disruption
 Info from IM to RU/SM that
train stopped and
continuation is unclear
 Close to TAF
 Triggers further communication
Short Term
Path Requests
Train
Preparation
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
TAP Masterplanning kick-off
3
25 September 2012
TAP RU/ IM functions are clustered for the Masterplanning
Description in the Regulation and the Implementation Guide
Reference of TAP RU/ IM functions
1)
TAP Regulation
RU/IM Implementation Guide1
Short Term
Path Requests
 BP 4.2.17
 chapter 12
Train
Preparation
 BP 4.2.14
 chapter 13
Train Running
Info + Forecast
 BP 4.2.15
 chapter 14, 18
Service
Disruption
 BP 4.2.16
 chapter 15, 18
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
TAP Masterplanning kick-off
4
25 September 2012
Some TAP RU/ IM functions are new and not relevant for TAF
Additional TAP RU/ IM functions
Content
Relation to TAF
 Info from IM to RU/ SM
about platform
 Passenger information; not
relevant for TAF
Train Journey
Modified
 Info during operation from
IM/ RU to SM that train is
rerouted, cancelled etc.
 Passenger information; not
relevant for TAF
Info in stations
 Info from SM to customer
(content only)
 Passenger information; not
relevant for TAF
Info in vehicles
 Info from RU to passenger
(content only)
 Passenger information; not
relevant for TAF
Change of
Track
TAP Masterplanning kick-off
5
25 September 2012
TAP RU/ IM functions are clustered for the Masterplanning
Description in the Regulation and the Implementation Guide
Reference to TAP RU/ IM functions
TAP Regulation
RU/IM Implementation Guide1
Change of
Track
 BP 4.2.12
 chapter 16, 19
Train Journey
Modified
 BP 4.2.12
 chapter 17, 19
Info in stations
 BP 4.2.12
 chapter 19
Info in vehicles
 BP 4.2.13
 chapter 19
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.
TAP Masterplanning kick-off
6
25 September 2012
Standard interfaces to allow communication between stakeholders
via standard data networks
General architecture of the RU/IM communication
illustrativ
RU 1
RU 2
CI
CI
CUS
CI
IM 1
IM = Infrastructure Manager
RU = Railway Undertaking
SM= Station Manager
CI = Common Interface
CUS = Commonly Used System
CI
IP Network
CI
Common Reference data.
 Location-ID
 Company-ID
TAP Masterplanning kick-off
CI
CI
RU 3
CI
IM 2
SM 1
7
25 September 2012
TAP RU/ IM prerequisites are very close to TAF TSI
Overview of TAP RU/ IM prerequisites
Content
Relation to TAF
Reference Files
 Data on Locations,
Countries, Companies
 Very close to TAF
Common
Interface
 Tools to allow
interoperable message
exchange
 CCG CI is available
 Individual solutions possible1
 Unambiguous identification
for IT applications
 Not replacing rail
operational numbers
 Phased approach using existing
identifiers is developed in
collaboration with TAF2
 Availability of rules for
standards and common
elements
 Not specified yet
Train Identifiers
Governance
1) Companies can implement own solutions conform to the reference CI, allowing the exchange of TAP messages
2) Start using TAP messages with existing identifiers, move towards technical identifiers as developed by TAF, partners need to agree on migration
TAP Masterplanning kick-off
8
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
1)
2)
TAP Regulation
RU/IM Implementation Guide1
 BP 4.2.19
 chapter 9
 BP 4.2.21
 chapter 6
 n/a
 chapter 8 and Train ID
handbook2)
 n/a
 chapter 23
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 Train ID Handbook is available at http://www.uic.org/IMG/pdf/111122_wg_10_handbook_final.pdf
TAP Masterplanning kick-off
9
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
TAP Masterplanning kick-off
10
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
TAP Masterplanning kick-off
11
25 September 2012
Commercial solutions outside the TAP legal frame are being prepared
by some sector organisations
Availability of support from stakeholder groups
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
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]
1) Path Co-ordination System
TAP Masterplanning kick-off
12
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
Sector driven
Regulation driven
 Create a wagon order
message for passenger information
 Check the external specifications of the
reference implementation of the CI (CCG
CI). Relevant for TAF and TAP
– This is relevant for TAP only
 Clarify stakeholder questions on
deliverables
 Enhance work on Train Identification
(see also previous slide)
 Check/enhance messages for Short
Term Path Request for
– Create technical messages needed for
TAF and TAP
– Annual Path Requests
– One Stop Shops
– to accommodate passenger specific
requirements
– Coach Group (through coaches)
 Code list maintenance
Most points are valid for
both 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.
TAP Masterplanning kick-off
13
25 September 2012
Reference documents for RU/IM Communication
The following links host the reference documents for RU/IM communication
 RU/IM Implementation Guide
http://tap-tsi.uic.org/IMG/pdf/20120629_tap_ru_im_implementation_guide_v53c.pdf
 Annexes to the RU/IM Implementation Guide
http://tap-tsi.uic.org/What-s-new,4.html
 Train ID handbook
http://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 results
http://www.era.europa.eu/Document-Register/Documents/TAFTSI%20Preliminary%20Master%20Plan.pdf
 General TAF links and information
http://www.uic.org/spip.php?article446
TAP Masterplanning kick-off
14
25 September 2012