1. ČD Cargo TAF Implementation
CDC = Czech „national“ freight RU
since 2007, owned by Czech Railways holding
block trains + single wagons
65% CZ market share
66 mil tons (5th in EU)
7 200 people
900 engines
wagons

2. Implemented functions RU-IM:
Path request
Train preparation
Train running info +
Train Identification
Reference data
Communications
In production
since Feb 2013
1st in Europe !!!

3. Basic process flows KANGO KADR ISOŘ ComposT PCS TIS DISC EMAN DISC OŘ
Path request for yearly timetable
DISC EMAN
KANGO
Path details
DOMIN
Yearly paths
Trains plan
Infra restriction
(IRNDB)
DISC OŘ
Ad hoc Path Request
KADR
Ad hoc Path Details
Activation / Deactivation
Train ready
Planned trains (12 hours ahead
Paths
ComposT
PRIS
Train composition
Train composition
Train Ready
Paths
ISOŘ
Train running info) 3

4. Functions RU-RU: internally covered
Consignment Data: ECN in operation
Train preparation: Hermes 30 used
Shipment ETI/ETA: internally done
Wagon Movement: via ISR - Raildata
Interchange reporting: Hermes 30
WIMO: own wagons database exists
But any realization with other RUs waits for feasible specifications.

5. Experienced impacts Now only impacts for CDC-SZDC and internally
Interface with SZDC was needed anyway
Set of new & modified IS, new processes
Investment with subsidy from EU/CZ
Everything is done via IS (& more complex)
Need to maintain and run much more IT
Unique identification of trains with Idents
No real expectations from TAF RU/RU (some functions not needed, some unrealistic, some covered by existing tools)

6. Implementation issues:
If you go ahead, you face problems others have no idea about…
Quality of RU-RU specifications is not optimal
Possible to build core functions, not interfaces
RU-IM well specified but needed adaptations, many things not defined in TAF yet
CZ is a TAF island … issue with data at borders for incoming trains
Not happy to invest in new versions…

7. Recommendations:
Regulation should not request implementation of functions, which are useless or with no ROI
If IM sets TAF as condition, then it has to apply to all RUs (messages vs. just IM web capture)
Revise TAF specs for RU-RU to support real needs and delete all useless functions
Avoid TAF implemented differently at each IM (current approach goes this way)
Constant maintenance of the specification by someone concrete would be of an asset