1 / 18

RAILWAY INDUSTRY TRAIN PLANNING LEVEL 2 TRAINING

RAILWAY INDUSTRY TRAIN PLANNING LEVEL 2 TRAINING. Module 9 - The TOCs and Network Rail. Train Operator Planning Process. Four Main Stages: Business Specification TOC Declaration Draft Timetable Final Timetable. Business Specification. Will take the form (for example):

huela
Download Presentation

RAILWAY INDUSTRY TRAIN PLANNING LEVEL 2 TRAINING

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAILWAY INDUSTRYTRAIN PLANNINGLEVEL 2 TRAINING Module 9 - The TOCs and Network Rail

  2. Train Operator Planning Process Four Main Stages: • Business Specification • TOC Declaration • Draft Timetable • Final Timetable

  3. Business Specification Will take the form (for example): • 1 train per hour between A & F calling at B & D. • 2 trains per hour between B & G calling at all stations. • Services for School Children to be provided between B & C, arriving at C at 08:10 +/- 5 minutes and departing from C at 16:15, or up to 10 minutes later

  4. TOC Declaration • Will be either in the form of a full detailed Timetable or a list of Amendments to the existing Timetable, or a combination of both. • Will include a set of Unit Balances. • The preparation requires a number of iterations, including matching train formations to anticipated passenger loadings and updated Revenue Forecasts.

  5. Draft Timetable • This is supplied by Network Rail by electronic transfer. Upon receipt, many processes commence. Some of the outputs are then re-input as part of an iterative process. • Where a need for change is identified, an appropriate Spot Bid is submitted to Network Rail.

  6. Final Timetable • This is the result at the end of the Spot Bid Processes. • There is an upload (by Network Rail) to TSDB whence a series of Outputs are derived. • There are also a series of Outputs direct within the TOC organisation.

  7. Inputs (1) • Passenger loadings data Input to the Business Specification and updates at all stages. • Rules of the Plan / Rules of the Route Input to preparation of TOC Declaration. • Previous Timetable(s) Input to Business Specification and TOC Declaration

  8. Inputs (2) • Revenue Data Input to Business Specification Process. • Performance Data Input to Business Specification & TOC Declaration. • Costs (both Fixed and Variable) Input to Business Specification.

  9. Inputs (3) • PSR/SLC and Franchise Commitments (if any) Input to the Business Specification and Updates added at all Stages. • “Stakeholders” – eg User Groups, PTEs and Passenger Focus Input to the Business Specification. • Other TOC ’s Requirements (eg connections) Input to the Business Specification.

  10. Inputs (4) • Other TOC’s Trains using Common Infrastructure Input to TOC Declaration. • Traincrew Conditions of Service Input to Business Specification and the Preparation of the Final Timetable. • Fleet Size and Characteristics – eg fuel range Input to the Business Specification and Updates added at all Stages.

  11. Inputs (5) • Planned Changes to Infrastructure, Fleet & Personnel – eg new Traincrew Depot Input to the Business Specification. • Catering Provision & Reservations Input to the Business Specification and a full Update made during the Preparation of the Final Timetable.

  12. Requests for Derogations from PSR Output from the Business Specification (for strategic derogations) and the Draft Timetable (for detailed derogations). Unit Diagrams Traincrew Diagrams Fuel Budget Train Miles Budget Station Access Budget Staff Budget Outputs from Draft Timetable

  13. From TSDB (NR) N R T RJIS CIS TRUST Delegates will recall earlier “Systems” slot From TOC Final Database N R S (Joint with TSDB) P T Ts V P I S Station Departure Posters Outputs

  14. Role of the Train Operator Owns or leases trains, runs them over Network Rail’s track and signalling infrastructure. Pays Network Rail for access to that infrastructure.

  15. Role of Network Rail Owns track and signalling infrastructure over which trains run. Manages timetable process ensuring equal opportunities and optimises allocation of line capacity.

  16. Responsibilities of the Train Operator • Determines train specification • Defines traction and rolling stock • Connectional arrangements • Train length • Platforming • Resource plans e.g. loco, stock, guards, drivers • Servicing, cleaning, water for toilets, catering vehicles

  17. Responsibilities of Network Rail • Validates plans • Determines headways and margins • Confliction resolution • Optimises track capacity to ensure robust plan = good performance • Engineering and contingency allowances • Signalbox openings • Production of accurate data and WTT

  18. Station Layouts again! • Number of platforms • Type of platforms (e.g. through, bay) • Platform occupation (number of trains) • Length of platforms • Crossing movement within or outwith platform • Additional running lines e.g. avoiding/through • Commercial need e.g. convenient to public • Turn Round times • Station Dwell times

More Related