Presentation gapeka (eng ver) 31 may 2011

470 views
394 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
470
On SlideShare
0
From Embeds
0
Number of Embeds
58
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentation gapeka (eng ver) 31 may 2011

  1. 1. Indonesian Timetabling Conference<br />Introducing Timetabling and Train Control where there a Multiple Operators<br />31 May 2011<br />
  2. 2. Introduction<br />Overview Paul Jerman<br />Overview of the last 30 years<br />Involved in rail since 1978<br />Train control management<br />Project management<br />The ARTC experience<br />Expansion of services in the outside world<br />
  3. 3. Australian Rail <br />Overview, Outside looking in<br />The Australian Rail experience overview<br />ARTC (Federal)<br />Vic (3 below rail operations)<br />NSW (3 below rail operations)<br />QR (2 below rail operations)<br />SA (3 below rail operations)<br />WA (below rail operations)<br />
  4. 4. Australian Rail<br /><ul><li>All states now have a ‘below rail operation and provide equitable access to above rail operators and share access at interfaces to create a seamless operation.</li></li></ul><li>The Annual Timetable<br />An Undertaking<br />What is the core business?<br />Provide fair and equitable access to the network for all rail operators<br />Maintaining capacity of the network<br />Encourage competition with Road, Air and Sea<br />Track Maintenance Management<br />Train Control Management<br />Revenue collection<br />
  5. 5. The Annual Timetable<br />The Responsibilities of the Service Provider in Brief<br />Rule Book Management<br />Systems and Standards to meet Regulatory compliance<br />Access rights<br />Train Control Management<br />Emergency Management<br />
  6. 6. The Annual Timetable<br />The Responsibilities of the User in brief<br />Rule Book Compliance<br />Systems and Standards compliance<br />Regulatory approval to operate<br />Maintaining the provided train path<br />Emergency Management<br />
  7. 7. The Annual Timetable<br />The Phases of the Timetable in Brief<br />Long Term Plan<br />12 months to 2 weeks prior to implementation<br />Forms the basis of network capacity with guaranteed paths<br />Short Term Plan<br />2 weeks to 24 hours prior to implementation<br />Deals with possessions, last minute changes and possessions<br />Current Operations<br />24 hours to implementation<br />Runs the plan (train control)<br />
  8. 8. The Annual Timetable<br />The Types of Paths<br />Premium<br />Highest flag fall and fee<br />Path is guaranteed to be available<br />Train will be prioritised<br />Used for Passenger and priority freight services<br />Regular<br />Lesser Flag fall and fee<br />Path is guaranteed to be available<br />Will be prioritised provided does not impact on Premium path<br />Used for low speed freight operations<br />Ad-Hoc<br />Lowest of all fees<br />Path is not Guaranteed to be available<br />All other service will be prioritised<br />Normally put on during the short term phase of the time table<br />
  9. 9. The Annual Timetable<br /><ul><li>Preliminary meetings and information exchange
  10. 10. User requirements
  11. 11. Must be Solvent
  12. 12. Must have regulatory approval to operate as a railway
  13. 13. Must have the necessary equipment required to operate on the railway
  14. 14. Must have roadworthy rolling stock to meet the network requirements
  15. 15. Must have the capacity to meet the schedules being requested</li></li></ul><li>The Annual Timetable<br /><ul><li>Preliminary meetings and information exchange
  16. 16. Provider requirements
  17. 17. Must be able to provide path length availability
  18. 18. Must have network capacity
  19. 19. Must of systems that detail corridor specifics such as axle loads and allowable speeds
  20. 20. Must provide track and network characteristics
  21. 21. Must be able to provide indicative costs (Flag fall plus Gross Tonne per Kilometre)</li></li></ul><li>The Annual Timetable<br />The Access Process<br />Preliminary Meeting and exchange of information<br />Submission for Access to the Network<br />Access Proposal <br />Negotiations to complete access agreement<br />Dispute procedures<br />
  22. 22. The Annual Timetable<br /><ul><li>Preparing the Access Proposal
  23. 23. Key Points
  24. 24. Train timetable should only be modified once or twice a year
  25. 25. The capacity of the network must continuously be monitored
  26. 26. Timetabling systems to assist in the modelling of the system and development of the plan must be utilised</li></ul>Example: Rail//Sys Management System<br /><ul><li>New users can have a permanent path but will not the integrated into the timetable until the next review
  27. 27. Impacts on other users require negotiation</li></li></ul><li>The Annual Timetable<br />Completing the Access Agreement<br />The rail operator will operate trains in line with the agreement and the conditions of the service provider<br />The service provider will ensure that the train operates to the train path provided with fair and equitable access<br />Running the train is detailed in Managing the Timetable (Current Operations)<br />
  28. 28. The Annual Timetable<br />Cyclic Maintenance<br />Reliant on the type of rail operations affected will determine the level of planning for disruption <br />Major cyclic maintenance that results in network shutdown should be planned as part of the timetable review and included into the train plan<br />Impact on rail operators requires to be well negotiated to get ‘best result’ for all<br />
  29. 29. The Annual Timetable<br />Regular and Emergency Maintenance<br />Part of the Short Term Train Plan development<br />Impacts still require negotiation with rail operators to allow timetable changes<br />Should be undertaken during lower peak periods where practicable reliant on urgency<br />
  30. 30. The Annual Timetable<br />Other Challenges<br />3rd party access requirements <br />New private sidings<br />Utilities<br />Interfacing service providers<br />Network change management<br />
  31. 31. The Annual Timetable<br />Questions<br />
  32. 32. Current Operations<br />Delivery of the Timetable<br />
  33. 33. Current Operations<br />Structure<br />Train control management requires a customer Current Operation liaison that is able to negotiate with train operators regarding train priorities and changes to the train plan.<br />That person is the person in charge of the delivery of the timetable, such as the train control shift manager.<br />Current operations is the ‘Cash Register’ of the below rail operations<br />
  34. 34. Current Operations<br />Conflicts<br />The manager allocated will resolve train schedule conflicts should they be encountered during the delivery of the train plan<br />Changes must be negotiated and relayed to the users to ensure that they are able to make required changes to their train operations<br />Decisions on changes to the schedule are made in line with the train running matrix which forms part of the access agreement regime. <br />
  35. 35. Current Operations<br />Train Prioritising<br />Objective of the train control provider is:<br />If a train enters the network early, to ensure the train exits on time<br />If a train exits the network on time, it is to exit the network on time<br />If a train enters the network late, it is classed as ‘unhealthy’ and will be operated ensuring it does not impact with on time services, however endeavours must be made for on time exit. <br />
  36. 36. Current Operations<br />If a train loses time en-route resultant from the rail operator it is classed as ‘unhealthy’ and will be operated ensuring it does not impact with on time services, however endeavours must be made for on time exit. <br />If a train loses time resultant from Network issues, it is considered to be healthy and endeavours must be made for on time exit. <br />Whilst the train timetable must be maintained en-route, it may be manipulated provided it can achieve on time exit<br />
  37. 37. Current Operations<br />Monitoring and Reporting<br />Customer meeting structure<br />Key Performance Indicators to be developed on:<br />On time running<br />Out of course running for both provider and user<br />Late entry and on-time exit<br />On-time entry and late exit<br />Train performance overall<br />And measured against the overall capabilities of the train plan <br />
  38. 38. Current Operations<br />Penalty Systems<br />Public expectations, establishing cause and ‘passing it on’<br />Impacts on a ‘Below Rail Operation’<br />Not the norm where there are high level of freight operations<br />Establishing processes as part of the Access Agreement negotiations<br />
  39. 39. Current Operations<br />Accidents and Insurance<br />Rail operators must have adequate insurance that ensures that all costs associated with an incident can be recovered<br />Accident investigation is performed by both the provider and the user of the network<br />The user of the network is responsible for clearing the network to allow repairs to the right of way<br />The provider of the network is responsible for restoring the right of way<br />
  40. 40. Current Operations<br />The two parties must have agreed ‘Incident Response 'plans to deal with such incidents<br />Resultant investigation outcomes will determine cause and responsibility of costs.<br />It is not uncommon to have the user on site searching for track faults, the provider of the network searching for wagon faults!!!!<br />
  41. 41. Current Operations<br />Managing Train Breakdowns<br />Rail operators are responsible for making arrangements to clear the network should a train become disabled<br />There is requirement for prompt recovery, and it is not uncommon for the user, and the rail operator to negotiate with an alternative rail operator to render assistance<br />The provider is responsible for make necessary network changes to recover the normal operations<br />
  42. 42. Current Operations<br />Managing Access to the Network<br />A rail operator must not be allowed network access unless <br />There is agreement to operate<br />That the provider has the required train details within the reporting systems<br />That the train is in position and will operate unhindered<br />That the provider is able to allow the train to effectively operate to its destination<br />That the train run can be captured in the revenue recording systems<br />
  43. 43. Revenue Collection<br />Revenue collection systems are used to capture all revenue rail services that operate over the network<br />RAMS is a common system used in Australia by most rail operators and has a multitude of capabilities<br />The selected system requires to allow the above rail users to enter their train details remotely and this should not be the task of the provider<br />Train running is progressively entered into the reporting system by the train controller<br />The system also captures train delays and forms part of the Reporting processes<br />
  44. 44. Current Operations<br />Details of the train run is then collated by the system and transferred to the respective revenue systems for invoicing to the rail operator<br />Fees work on a flag fall and gross tonne per kilometre rate.<br />
  45. 45. Other Challenges<br />Who actually runs the network, the provider or the rail operator??<br />When a train is on the network, it is meant to be moving <br />Trains should enter and exit promptly<br />Usage of Provider operated sidings (demurrage)<br />
  46. 46. The Annual Timetable<br />Questions<br />

×