INTEROPERABILITY UNIT

Transcription

1 EUROPEAN RAILWAY AGENCY INTEROPERABILITY UNIT TAF TSI - ANNEX A.5 :FIGURES AND SEQUENCE DIAGRAMS OF THE TAF TSI REFERENCE: ERA-TD-100 DOCUMENT TYPE: TECHNICAL DOCUMENT VERSION: 2.0 (DRAFT) TAF TSI DATE: Page 1/28

2 AMENDMENT RECORD Version Date Section number Modification/description Author All Initial version Mickael Varga All Version after TAF TSI Revision and TAF CCM cycle All Validated by the ERA TAF CCB on Rodrigo Gutiérrez Domínguez Rodrigo Gutiérrez Domínguez ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 2/28

3 Important note The present document belongs to the set of Technical Documents described in Annex A List of accompanying documents - List of mandatory specifications of the Commission Regulation EC/62/2006 and transformed in Annex A included in Annex II according Commission Regulation (EU) No 328/2012 amending Regulation (EC) No 62/2006 concerning the technical specification for interoperability relating to the telematics applications for freight subsystem of the trans-european conventional rail system. A new amendment was published on 22 April 2013, Commission Regulation (EU) No 280/2013, amending Regulation (EC) No 62/2006, due to the modification of Appendixes B, C, D and F, and the abolishment of Appendix B-1, concerning the technical specification for interoperability relating to the telematic applications for freight subsystem of the trans-european conventional rail system. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 3/28

4 The Trans-European Conventional Rail System TELEMATIC APPLICATIONS subsystem for Freight Services FIGURES AND SEQUENCE DIAGRAMS OF THE TAF TSI ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page /28

5 Intended Audience This document is one of the references to be used by designers and engineers responsible for the proper implementation of the TAF TSI requirements regarding message exchange according chapter.2 of the CR TSI Telematic Applications for Freight Services. Evolution of this Document Distribution: The Document will be delivered by electronic means in MS-Word format or in PDF Format and published on the ERA Web-site: era.europa.eu. New versions will be accessible electronically. Configuration Management: Any change requests on the content of this document shall be reported to the European Railway Agency. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 5/28

6 Table of Contents 0. INTRODUCTION Purpose References Regulatory References FIGURES Example of the critical points in Freight Transport Example for train Path request and RU / IM Communication Scenarios for path booking Examples for ETI calculation General Architecture Solution Overview Access method to the different types of Databases using the common interface SEQUENCE DIAGRAM: PATH REQUEST Sequence diagram path request Sequence diagram RU cancels a booked path Sequence Diagram: Path Not Available SEQUENCE DIAGRAM: TRAIN PREPARATION SEQUENCE DIAGRAM: TRAIN RUNNING FORECAST, EXAMPLE A SEQUENCE SHIPMENT ETI / ETA SEQUENCE DIAGRAM: WAGON MOVEMENT/INTERCHANGE REPORTING ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 6/28

7 0. INTRODUCTION 0.1. Purpose This document is the collection of the figures and sequence diagrams to which the TAF TSI refers. It gives support for the right understanding of the verbal description in the TAF TSI 0.2. References Regulatory References Id Title Doc ID, Edition Date Author / Publish er 1 Directive 2012/3/EU of The European Parliament and of The Council establishing a single European railway area. 2 On the interoperability of the rail system within the Community (Recast) Directive 2012/3/EU Directive 2008/57/EC 21/11/12 EC 17/06/08 EC 3 TSI OPE (repealed with Decision 12/05/20 EC effect from 2011/31/EU (in ) - force from Decision 2006/920/EC on) (as amended by 2009/107/EC and 2010/60/EU) Technical Specification for Interoperability subsystem«telematic Commission Regulation (EC) No 62/2006 concerning 23/12/05 EC ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 7/28

8 Id Title Doc ID, Edition Date Author / Publish er Applications for freight the technical specification for interoperability relating to the telematic applications for freight subsystem of the trans-european conventional rail system..1 TAF TSI - ANNEX A.5: Figures and Sequence Diagrams of the TAF TSI Messages ERA_FRS_TAF_A_In dex_5.doc 25/01/11 ERA.2 TAF TSI ANNEX D.2 : APPENDIX A (WAGON/ILU TRIP PLANNING).3 TAF TSI ANNEX D.2 : APPENDIX C REFERENCE FILES. TAF TSI ANNEX D.2 : APPENDIX D INFRASTRUCTURE RESTRICTION NOTICE DATA.5 TAF TSI ANNEX D.2: APPENDIX E COMMON INTERFACE.6 TAF TSI APPENDIX F Data and Message Model) Version /03/13 ERA Version /05/12 EC Version /05/12 EC Version /03/13 ERA Version /08/13 ERA 5 Amendment to Technical Specification COMMISSION REGULATION (EU) 17/0/12 EC ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 8/28

9 Id Title Doc ID, Edition Date Author / Publish er for Interoperability subsystem Telematics Applications for Freight 6 Amendment to Technical Specification for Interoperability subsystem«telematics Applications for Freight No 328/2012 of 17 April 2012 amending Regulation (EC) No 62/2006 concerning the technical specification for interoperability relating to the telematic applications for freight subsystem of the trans-european conventional rail system Commission Regulation (EU) No 280/2013 of 22 April 2013 amending Regulation (EC) No 62/2006 concerning the technical specification for interoperability relating to the telematic applications for freight subsystem of the trans-european conventional rail system. 22/03/13 EC ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 9/28

10 1. FIGURES 1.1 Example of the critical points in Freight Transport Key Interfaces in Freight Transport CONSIGNOR CONSIGNEE Pick Up Appointment Haulage 1 Driver with a Web Enabled Cell Phone Delivery Appointment Haulage 2 Intermodal Term Operator IntermodalTerm Operator RU 1 RU 3 Intermodal Gateway Oper;. RU 2 IM 1 IM 2 IM 3 The figure above shows the critical points (interfaces between the various partners involved) in freight transport on road compared with the critical points of freight transport on rail for a simplified scenario. 1.2 Example for train Path request and RU / IM Communication Origin A RU C RU E RU IM IM IM IM B D Destination F ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 10/28

11 With B, D and E as handover points between IMs and C and E as interchange points between RUs the situation is as follows: RU1 has to request a train path A-B from IM1 and B-C from IM2; RU2 has to request a train path C-D from IM2 and D-E from IM3; RU3 has to request a train path E-F from IM. The communication during the train running between RU and IM must always be based on train and path number, whereby the IM communicates with the RU, who has booked the train path on his infrastructure. This means for the example above: For the journey section A-B, IM1 communicates with RU1; For the journey section B-C, IM2 communicates with RU1; For the journey section C-D, IM2 communicates with RU2; For the journey section D-E, IM3 communicates with RU2; For the journey section E-F, IM communicates with RU3. If an RU provides the complete journey A F (Open Access by RU, no other RUs are involved), then each IM involved communicates directly with this RU only. This open access by the RU can be realised by booking the train path via One Stop Shop or in sections with each IM directly. The TSI takes account both cases. 1.3 Scenarios for path booking Scenario A: The RU contacts all involved IMs directly or via the OSS to organise the paths for the complete journey. In this case the RU has also to operate the train on the complete journey according to Article 13 of the Directive 2001/1/EC. a) Path booking via OSS by the RU for Transport Journey from A to F Path booking RU IMs internal arrangements IM IM IM IM m One RU is booking via OSS the complete path assembly from A to F. The train must be operated by the RU for the complete journey, therefore no interchange points exist. RU IMs A Handover Point B Handover point D Handover point E Hand-over point F ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 11/28

12 b) Direct path booking by the RU for Transport Journey from A to F RU Path booking IM IM IM IM m One RU is booking directly from the various IMs the several paths from A to F - section by section - between two handover points. The train must be operated by the RU for the complete journey, therefore no interchange points exist. RU IMs A Hand-over Point B Hand-over point D Hand-over point E Hand-over point F Scenario B: Each RU involved in the Transport Journey from A to F contacts the local IMs directly or via OSS to request a path for the journey section on which it operates the train. In this example: RU 1 is the LRU to co-ordinate the involved RUs RU internal Path booking RU 1 RU 2 RU n IM IM IM IM m Various RUs request from the various IMs or via OSS only the path(s) for a journey section between two interchange points of the complete journey for a train from A to F. The RUs operate the train on its booked path. A Handover Point B Handover point D Interchange Interchange and Handover Point F RUs IMs In this example RU1 is booking the paths from A to the interchange point C directly, whereas RU2 is booking the paths from the interchange point C to the next interchange point E via OSS. Interchange Point C and Handover Point E Remark: In the execution mode, the IM will always communicate with the RU which has booked the path. Therefore the path ownership is important for the message exchange during operation of the train. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 12/28

13 1. Examples for ETI calculation Example 1 for calculation of an ETI for LRU 1 and LRU 2 based on TETA from IM2 for interchange point C: LRU 1 LRU 2 ETI For wagon No 1&2 RU1 ETI C For wagon No 3,,5 5 3 RU RU2 A TETA Relevant ETI point F IM1 B IM2 D IM3 E IM Example 2 for calculation ETI for LRU 1 and LRU 2 based on TETA from IM2 for interchange point C: LRU 1 LRU 2 Relevant interchange point for LRU 1 (wagon 1 and 2) is E, therefore no ETI calculation related to point C. ETI C For wagon No 3,,5 5 3 RU3 RU RU2 A TETA Relevant ETI point F IM1 B IM2 D IM3 E IM ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 13/28

14 1.5 General Architecture Solution Overview ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 1/28

15 1.6 Access method to the different types of Databases using the common interface Each instance of the Common Interface will have access to all the data required according the TSI within each RU, IM, etc, whether the relevant Databases are central or individual. Central Access to all Databases via Reference DB 1 Common Interface (see.2.1.1) DB 3 Distributed Database RU Individual databases DB 2a 2 1 DB 2b 3 IM IM IM ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 15/28

16 New Path Request European Railway Agency 2. SEQUENCE DIAGRAM: PATH REQUEST 2.1 Sequence diagram path request This Diagram is also valid for Open Access (RU is LRU) and OSS with IM 1 as OSS RU IM 1 IM N Path Request Receipt Confirmation The RU sends train path request to the relevant IMs. The IMs send the receipt confirmation to the RU, if the required response cannot be made available in real-time. Path Details Each IM sends to the requested RU the path details for its section Path Confirmed RU confirms the Train Path Details to each relevant IM. Path Details Refused RU can refuse the path details from some IMs and sends a new path request to them. Alternatives 2.2 Sequence diagram RU cancels a booked path RU IM 1 IM N Path Cancelled RU cancels previously booked paths on the Infrastructure of various IMs. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 16/28

17 Only in case of not Open Access European Railway Agency 2.3 Sequence Diagram: Path Not Available This Diagram is also valid for Open Access (RU is LRU) and OSS with IM as OSS. RU IM Path Not The IM sends Path Not Available to the RU. Path Details Together with the message Path Not Available or as soon as possible the IM sends a proposal for the booked path, which is not available. This is done with the Path Details message. Receipt The RU sends the Receipt Confirmation to the IM, if the required response cannot be made available in real-time. Path Confirmed Path Details Refused RU confirms the Train Path Details to the IM, if it agrees. RU can refuse the path details from the IM and sends a new path request to them. Path Alternatives RU cancels the previously booked path with reference to IM s Path Not Available message. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 17/28

18 3. SEQUENCE DIAGRAM: TRAIN PREPARATION This Diagram is also valid for Open Access (RU n is LRU) and OSS with IM 1 as OSS RU n+1 RU n IM 1 IM N Only in case of not Open Access Train Composition RU sends the train composition message to the neighbouring RU and to all relevant IMs, with which the RU has a path contract for a journey section of the path. Train ready RU indicates to the IM of the first section, that the train is ready for access to the network. Train running IM to RU to indicate that he has taken over the control of the train. Remark: During the train preparation also a Train Path Not Available message can occur, since this message can be send at any time between the moment the train path is contracted and the departure of the train. This is not included in this diagram. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 18/28

19 . SEQUENCE DIAGRAM: TRAIN RUNNING FORECAST, EXAMPLE A Example A according Path request scenario A(a) and A(b) (see chapter 1.3) RU 1 IM 1 IM 2 IM 3 IM B A Handover C D Handover Point Point Handling Handling and Point Handover Points E F RU IMs ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 19/28

20 Handling at Point C Handling at Point Handling at Point European Railway Agency With: 3 =Train Running Forecast = Train Running Information RU 1 IM 1 IM IM IM Train preparation at station A 3 3 After leaving A: IM1 sends train running information to RU1 And IM1 sends train running forecast ETH for B to IM2 and RU1. 3 When arriving at B IM1 sends train running information to RU1 After leaving B: IM2 sends train running information to RU1 And IM2 sends train running forecast for C to RU1. When arriving at C IM2 sends train running information to RU1. Train preparation at Handling point C. 3 3 When leaving C: IM2 sends train running information to RU1 And IM2 sends train running forecast ETH for D to IM3 and RU1. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 20/28

21 At Destination Handling at Point E Handling at Point D European Railway Agency RU 1 IM 1 IM IM IM When arriving at D: IM2 sends train running information to RU1 3 3 When leaving D: IM3 sends train running information to RU1 And IM3 sends train running forecast ETH for E to IM and RU1. When arriving at E: IM3 sends train running information to RU1. Train preparation at Handling Point E. 3 When leaving E: IM sends train running information to RU1 And IM sends train running forecast TETA for F to RU1 When arriving at F: IM sends train running information to RU1 With: 3 =Train Running Forecast = Train Running Information ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 21/28

22 At Handover point B At Departure Point A European Railway Agency Example B according Path request scenario B (see chapter 1.3) In this example: RU 1 is the LRU to co-ordinate the involved RUs. RU 1 RU 2 RU 3 Each RU must know its neighbour RU. This information must be given by the LRU IM IM IM IM B D RUs IMs A Handover Point C Interchange Point Handover point E Interchange and Hand-over Points F RU 1 IM 1 IM RU IM IM RU Train preparation at departure point A done After leaving A: IM1 sends train running information to RU1 And 3 3 IM1 sends a train running forecast ETH for B to IM2 and RU1 When arriving at B: IM1 sends train running information to RU1. 3 When leaving B: IM2 sends train running information to RU1 and IM2 sends train running forecast for C to RU1. With: 3 =Train Running Forecast = Train Running Information ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 22/28

23 At Destination At Interchange / Handover At Handover Point D At Interchange Point C European Railway Agency RU 1 IM 1 IM RU IM IM RU When arriving at C: IM2 sends train running information to RU1 Train preparation at Interchange Point C done. 3 3 When leaving C: IM2 sends train running information to RU2 And IM2 sends train running forecast ETH for D to IM3 and RU2 3 3 When arriving at D: IM2 sends train running information to RU2. When leaving D: IM3 sends train running information to RU2 When arriving at E: IM3 sends train running information to RU2 Train preparation at Interchange Point E When leaving E: IM sends train running information to RU3 And IM sends train running forecast TETA for F to RU3 3 When arriving at F: IM sends train running information to RU3 With: 3 =Train Running Forecast = Train Running Information ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 23/28

24 5. SEQUENCE SHIPMENT ETI / ETA This Sequence is based on the following example for the interchange point C. LRU 1 LRU 2 ETI For wagon No 1&2 RU1 ETI C For wagon No 3,,5 5 3 RU RU2 A TETA IM1 B Relevant ETI point IM2 D IM3 E IM F IM 2 RU 1 RU RU Lead Lead TETA For C ETI for and C ETI for C and Wagon 1&2 ETA for F and Wagon 1&2 ETI for C and Wagon 3,,5 ETI for C and Wagon 3,,5 ETA for E and Wagon 3,,5 ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 2/28

25 Remark: ETA for the wagons 1&2 is the ETI at F plus the time for delivery at customer siding according to commitment. ETA for the wagons 3,,5 is the ETI at E plus the time for delivery at customer siding according to commitment. ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 25/28

26 6. SEQUENCE DIAGRAM: WAGON MOVEMENT/INTERCHANGE REPORTING The following Sequence diagram refers to figure 1 (Example 1, ETI Calculation) and considers the handling for the wagon Numbers 1 and 2. IM 2 RU 1 RU LRU Release Notice Departure Notice LRU tells RU1 wagon is ready for pick up. RU1 informs LRU, that wagon has been picked up Train Yard arrival RU1 informs LRU: wagon arrived at the yard point A Running Only as remind Information Train running forecast for C Yard departure Wagon ETI for C Wagon ETA for F After receipt of the train running information, the RU1 informs the LRU, that the wagon has left the yard point A. Train running information Wagon interchange Notice Yard arrival After receipt of the train running information with train arrived at C, RU1 sends yard arrival to LRU and wagon interchange notice to RU2, RU2 accepts the wagon with wagon receipt notice. Train Running Information Wagon receive notice Possible Exception message After receipt of the train running information, the RU2 informs the LRU, that the wagon has left the yard point C. Yard departure Only as remind Train running forecast Train running forecast Wagon ETA for F Wagon ETA for F After receipt of each train forecast message from IM 2, 3 and, RU 2 must recalculate the ETA for LRU1. Train forecast running Wagon ETA for F When arriving destination F: Wagon arrival notice Wagon delivery notice When the wagon has arrived at the yard of the RU2 at point F, the RU2 informs the LRU. When the wagon has been placed at consignee s sidings, the RU2 informs the LRU. This delivery may be confirmed by the RU2 sending the wagon delivery notice a second time with the customer identification ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 26/28

27 E N D O F D O C U M E N T ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 27/28

28 Warning European Railway Agency 2013 ERA_TECHNICAL_DOCUMENT_TAF_A_INDEX_5 Version 2.0 (DRAFT) Page 28/28