Railcorp Operations Protocol Version 4.0 December 2017
Total Page:16
File Type:pdf, Size:1020Kb
Annexure G Operations Protocol Operations Protocol version 4.0 – December 2017 Contents 1 General matters ...................................................................................................... 4 1.1 Preamble .................................................................................................... 4 1.2 Scope of Operations Protocol ..................................................................... 4 1.3 Contacts ..................................................................................................... 4 1.4 Definitions................................................................................................... 5 2 Development of a new SWTT and variations to the SWTT .................................... 10 2.1 Overview of process ................................................................................. 10 2.2 Inputs to process ...................................................................................... 10 2.3 Roles and responsibilities ......................................................................... 11 2.3.1 Rail Operator .............................................................................. 11 2.3.2 Transport for NSW ...................................................................... 11 2.4 Output of process to develop new SWTT ................................................. 13 2.5 Output of process to vary the SWTT ......................................................... 14 3 Temporary modifications to the SWTT .................................................................. 15 3.1 Overview of process ................................................................................. 15 3.2 Inputs to process ...................................................................................... 15 3.3 Roles and responsibilities ......................................................................... 15 3.3.1 Rail Operator .............................................................................. 16 3.3.2 Sydney Trains ............................................................................. 16 3.4 Output of process ..................................................................................... 17 4 Daily Train Plan ..................................................................................................... 18 4.1 Overview of process ................................................................................. 18 4.2 Inputs to process ...................................................................................... 18 4.3 Roles and responsibilities ......................................................................... 18 4.3.1 Rail Operator .............................................................................. 18 4.3.2 Sydney Trains ............................................................................. 19 4.4 Communications timeframes .................................................................... 19 4.5 Outputs of process ................................................................................... 20 5 Daily train control (live program) ........................................................................... 21 5.1 Overview of process ................................................................................. 21 5.2 Inputs to process ...................................................................................... 21 5.3 Roles and responsibilities ......................................................................... 21 5.3.1 Rail operator ............................................................................... 21 5.3.2 Sydney Trains ............................................................................. 22 5.4 Communications timeframes .................................................................... 23 5.5 Outputs of process ................................................................................... 23 6 Train decision factors ............................................................................................ 24 Appendix 1 – Path application .................................................................................... 26 Appendix 2 – Train consist information ....................................................................... 29 Operations Protocol Final – version 4.0 – December 2017 2 Index of tables Table 6-1 Path priority principles ................................................................... 24 Table 6-2 Decision matrix .............................................................................. 25 Index of figures Figure 2-1 Development of a new Standard Working Timetable ................... 13 Figure 2-2 Variations to the SWTT ................................................................. 14 Figure 3-1 Temporary modifications to the SWTT ......................................... 17 Figure 4-1 Daily Train Planning ..................................................................... 20 Operations Protocol Final – version 4.0 – December 2017 3 1 General matters 1.1 Preamble This Operations Protocol forms part of a Track Access Agreement between: a. RailCorp, as owner of the infrastructure that forms the RailCorp Network; and b. a Rail Operator. 1.2 Scope of Operations Protocol The Operations Protocol describes the interfaces between RailCorp, its agents and Rail Operators as they affect the delivery of the Standard Working Timetable (SWTT), Train Planning, Train Programming and Train Control services on the Network. The Operations Protocol describes the following processes: Development of a new Standard Working Timetable (SWTT) and variations to the SWTT; Temporary modifications to the Standard Working Timetable for Special Events and Track Possessions; Daily train planning; Real-time Train Control, including the description and application of Train Decision Factors. This document is not a Safety Interface document. The document scope is limited to the processes outlined above. Indicative timeframes for the delivery of the processes outlined in Sections 2 to 5 of this document are contained in the process flowcharts that accompany each section. While RailCorp intends to adhere to these indicative timeframes, failure to achieve the timeframes shall not constitute a default by RailCorp of its obligations under this Operations Protocol or the Access Agreement. RailCorp will not be liable for any claims suffered or incurred by or made or brought by or against the Rail Operator as a result of or arising from not adhering to these timeframes. Issues which a Rail Operator has in relation to the implementation of the Operations Protocol that are not resolved through the processes in this document may be resolved in accordance with the dispute resolution processes in a Rail Operator’s Access Agreement. 1.3 Contacts Relevant contact details will be provided via a secure website. Operations Protocol Final – version 4.0 – December 2017 4 1.4 Definitions For the purposes of this Operations Protocol, the following terms are defined to mean: Ad hoc Train Path means a Train Path which is not a Timetabled Train Path in the Standard Working Timetable and which is made available to the Rail Operator on a specified day. Adjacent Network Manager means the Australian Rail Track Corporation (ARTC) and John Holland Rail (JHR) as manager of the Country Regional Network (CRN). Asset Standards Authority (ASA) means the independent unit established within Transport for NSW, and is the Network design and standards authority for NSW transport assets. Daily Train Plan means the documents comprising all of the advices which are prepared in accordance with the Operations Protocol by or on behalf of the Train Control Entity exercising Train Control on the Network on that day and which, taken together, show all of the Train Paths on the Network for that day. DTPOS (Daily Train Path Ordering System) means the system used by Rail Operators to make Path Requests and Path Amendments for inclusion in the Daily Train Plan and for Sydney Trains to validate and approve those Train Path Requests. DTPOS also provides visibility of all of the Rail Operator’s confirmed Train Paths in the Daily Train Plan. Freight Services means all freight trains operating on the RailCorp Network. Frequent-stop Passenger Services means those Passenger Services that stop at most or all stations along their Train Path. Healthy Train means a train that, having regard to the Daily Train Plan applicable on the day: a. presents to the Network On-time, is configured to operate to its schedule and operates in a way that it remains able to maintain its schedule; or b. is running late only due to causes within the RailCorp Network, where the root cause is outside the Rail Operator’s control; or c. is running On-time, regardless of previous delays. Incident means a localised event or occurrence, either accidental or deliberate including: an event that results in death or injury, damage to property, damage to the environment, a derailment or disablement; an event that requires (dependent on the Incident level) a particular response from RailCorp and/or Train Control Entity; an event which involves external organisations/agencies a Category A notifiable occurrence or a Category B notifiable occurrence as defined in the Rail Safety National Regulations; an Incident that requires or could require notification to the relevant authority under Rail Safety National Law; and Operations Protocol Final – version 4.0 – December 2017 5 an Incident that requires or could