The first implementation of TAF RU-IM: Czechia, ČD CARGO and SŽDC experience

Transcription

1 The first implementation of TAF RU-IM: Czechia, ČD CARGO and SŽDC experience Petr Červinka (ČDC) Miloš Futera (SŽDC) TAF/TAP TSI Plenary Praha

2 Content SŽDC and ČDC introductions TAF Czech milestones, implemented functions IT systems at SŽDC andčdc RU-IM process flows Path request, Train preparation, Train running Experiences to share Next steps, intentions 2

3 SŽDC introduction SŽDC, state organisation - Správa železniční dopravní cesty Infrastructure manager in Czech Republic on railway tracks in state ownership Established Main SŽDC functions: operation of the railway infrastructure and its operability, maintenance and repair of the railway infrastructure, development and modernization of railway infrastructure, allocation of capacity on SŽDC infrastructure to its customers Staff: ca Rail network: 9468 km of tracks Number of RUs: 102 (17 with data exchange) 3

4 ČD Cargo introduction Freight RU and wagon keeper Owned by Czech Railways (ČD) Established: Dec 2007 (division from ČD) Operating in Czechia and via daugters also in PL and SK Main ČDC services: Wagon load transports (1000 locations) Block train transports Logistic services, wagon rental etc. Staff: 7000 Volumes: wagons, 900 engines 65 mil tons goods Large portion of international transports 4

5 TAF milestones in Czechia First intentions: 2006 First implementation: 2008 web app using TSI structure First TAF data communication 2010 New IT systems atčdc: , link to SŽDC ČDC upgrade for TAF: end 2013-mid 2015 Ongoing improvements and extensions TAF considered as useful and successful! All above is for RU-IM Feasible specifications for RU-RU are still pending 5

6 Implemented functions: Path request Train preparation Train running + Train Identification Communications Reference files Infrastructure restrictions 6

7 TAF related systems at ČDC PROBIS - set of IS for planning & operations DISC-EMAN (path management) DISC-OŘ (traffic management) PRIS (wagons operations) PDV (wagon tech data base) ZEVO-K (own wagons data) 7

8 RU/IM applications at SŽDC COMPOST (TSI) - train composition, train ready - to be WIMO DOMIN (TSI) database of infra restrictions (IRNDB) ISOŘ (TSI) traffic management KADR (TSI) - ad hoc request, path allocation, Path activation REVOZ (TSI) - vehicle register - to be RSRD MIMOZA special consingment ETD - source of electronic TT for loc driver GRAPP - train movement display in map KAPO use of infrastructure fee KAFR (TSI) company register, CRD companies KANGO (TSI) - yearly TT process, KANGO KMEN - description of infrastructrure, CRD locations + RNE PCS - Path coordination system owned by RNE RNE TIS Train information system owned by RNE 8

9 Process flows PCS RNE TIS Train plan DISC EMAN Path request for yearly timetable (TAF: 2019) IRN_DatasetMessage IRN_DatasetMessage Path details (TAF: 2019) DOMIN Infra restrictions (IRNDB) KANGO Yearly paths IRN_DatasetMessage DISC OŘ Ad hoc Path Request Activation / Deactivation (Path Section Notification) Ad hoc Path Details KADR Planned trains (12 hours ahead PRIS Train ready Train composition Paths Activation Train composition Train Ready Paths Activation COMPOST Train running info Paths Activation Train Composition Train Ready ISOŘ Train running info IT station level 9

10 Path Request Timetable Paths: DISC-EMAN KANGO Uses specific xml messages (TAF: 2019) Ad-hoc Paths: TAF messages & scenarios (9 message types) above 10 days: DISC-EMAN KADR up to 10 days: DISC-OŘ KADR SŽDC web alternative: KADR (web interface) 10

11 Train preparation Train composition After train completion or change With TCM message to COMPOST from PRIS for freight trains from DISC-OŘ for locomotive trains All train changes in all stations covered COMPOST ISOŘ IT station level SŽDC station staff has info about actual TC SŽDC web alternative: WEBCOMPOST 11 11

12 Train preparation Train ready When train is ready to go (+ after TCM change) ČDC driver sends SMS to DISC-OŘ (to be changed 2018/IX, driver will use tablet) DISC-OŘ checks + sends TRM to COMPOST COMPOST ISOŘ IT station level (station staff has info about TRM incl. contact to driver) SŽDC web alternative: WEBCOMPOST, APORT 12

13 Train running info Source: SŽDC systems at station level SŽDC collects on-line data into ISOŘ ISOŘ sends train events to DISC-OŘ + RNE TIS SŽDC can send in TAF or legacy format SŽDC web alternative: GRAPP 13

14 Communications SŽDC offers: web services / IP sockets / CI WithČDC are web services used in both directions Not CI - from historical and technical reasons SŽDC uses common TAF messagges in older version of data catalogue with network specific parameters and selected sector messages. Schema used: used (some 5.3.1) Description of interface: provoz.szdc.cz 14

15 Train/Path/Request identification IMPLEMENTED IN OPERATION SINCE 2014! TRain Transport ID + PAth ID + Path Request ID RU assigns TRID and PRID, SŽDC assigns PAIDs TRID and PAID used for planned and day objects PRID is not used on train preparation and Train runnning phase Displayed in applications, used in messages Well accepted by staff both SŽDC and ČDC Case Reference ID to be implemented

16 Aspects of successful implementation 1 TAF came in right time: split CD to IM and RU Both needed redesign processes and IT anyway SŽDC andčdc active in TAF revision WGs Strong team at SŽDC and partners atčdc Historically high level of telematics Experienced and capable suppliers Supported from CZ transport ministry State funds fundamental 16

17 Aspects of success (2) TAF specs for RU-IM from WGs good base But it was necessary to complete & refine!!! Covered needed and useful functions Re-use existing interfaces with same function Lead by SŽDC and coordinated with RUs Only IM has power to push RUs Condition to access rail network SŽDC used non-strict approach not each RU has IS: web alternatives! 17

18 Other side of the coin If you walk first, you face issues which others even do not see necessity to tune specs. Further changes of TAF and xsd would require to modify your systems costs. With TAF, all processes are digital high IT coverage is complex and costly to maintain RU competitors with no IS have lower costs. Island effect: SŽDC requires from RUs info about trains before they enter, but how ČDC can get it from non-taf partner RUs? 18

19 Next steps SŽDC plans: Process Path alteration a Path modification finalization SŽDC Grant agreement to CEF Call 2016: Implementation of TSI TAF and TSI TAP in information systems of SZDC stage 3 o Train running forecast sophisticated solution of forecast calculation and data communication with RUs and IMs o Service disruption - complex solution of process o TSI communication among IMs in CZ (TAF/TAP data communication among national (small) IMs and RUs. o Implementation of TSI TAP (PRM, information to passengers ) o Finalization of RU functions at SŽDC RSRD, WIMO 19

20 Thank for your attention! Ing. Petr Červinka ČD Cargo, a.s. Generální ředitelství, Odbor informatiky (O20) M: Vídeňská 15, Olomouc Czech Republic Ing. Miloš Futera SŽDC, s.o. Generální ředitelství, Odbor informatiky (O12) M: Křižíkova 2, Praha Czech Republic 20