European Rail Traffic Management System in Great Britain

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The European Rail Traffic Management System (ERTMS) is an initiative backed by the European Union to enhance cross-border interoperability and the procurement of signalling equipment by creating a single Europe-wide standard for train control and command systems.

Its main components are European Train Control System (ETCS) and GSM-R communications system.[1] ETCS is a standard for track-train radio communications using balises (Eurobalises) and associated in-cab train control[2] while GSM-R is the GSM mobile communications standard for railway operations. ERTMS can operate at different levels depending on specific local requirements.[3][4][Note 1] Under ERTMS speeds are displayed in the driver's cab in km/h and at Level 2, lineside speed indicators are optional.[5]

History

In 2007 the British Government published its response to a European Union directive[6][7] requiring the use of ERTMS on High Speed (TEN-R)and Conventional Trans-European Railway Network (TEN) routes. The response proposed a roll-out plan of ERTMS equipment on existing lines that would be completed by 2044 though the actual timing of the programme will depend on changing circumstances – new trains will be ordered with ERTMS equipment on board and ERTMS would be installed during any electrification programs.[8] In 2009, the Rail Safety and Standards Board confirmed that km/h would be used on ERTMS lines in the United Kingdom.[9] With the ongoing introduction of ERTMS, it is foreseen that the metrication of British rail transport will be completed over the next few decades.[10]

The Uff/Cullen inquiry (2001) following the Southall and Ladbroke Grove rail crashes identified a need for in-cab signalling on high-speed trains and recommended that ERTMS should be installed onto all of Britain's high-speed lines by the year 2010. However, this timescale was not viable because of the time required to develop the technology.[11]

Features and current implementation

A standard feature of the speedometers used by ERTMS/ETCS systems is the use of the metric system.[12] At a Railway Conference in 2002, it was argued that a changeover to using metric units for speed in advance of the introduction of ERTMS was unlikely to be financially viable unless the decision is taken to adopt Level 2 ERTMS without lineside signalling. There would however still be a need to handle dual both mph and km/h.[5] A 2010 voluntary standards document published by the Rail Safety and Standards Board addressed this issue when it recommended that the speedometer of a ETCS system be designed so that it switches automatically between mph and km/h depending on the route being traversed. The speedometer would display "mph" when the speedometer was displaying "miles per hour", otherwise would display nothing. Its graduations would be chosen such that the angle of the needle would not change when the system switched from one scale to the other. The conversion between metric and imperial units would be a function of the speedometer, not of any other on-board equipment.[13] In 2012 a technical specification matching this proposal was published.[14]

The Cambrian Line, a low volume 215 km (134 mi) rail link between Shrewsbury in the east and Aberystwyth and Pwllheli in the west, was chosen as Britain's first ERTMS line. This line was chosen as its signalling system had reached the end of its useful life, and because it is a low capacity line almost separate from the national network, making it an ideal site on which to gain ERTMS experience.[8][15] All speeds in the Cambrian Line Rule book are in km/h."[16][17] ERTMS will be rolled out on the Great Western Route as part of the electrification and resignalling work[18] which is expected[Note 2] to reach Oxford and Newbury by 2016 and Cardiff by 2017.[19]

Future use

Other early mainline conversions to the ERTMS standards are expected to include[8] 251 km (156 mi) of the East Coast Main Line from London (Kings Cross) to Doncaster by 2020 and 158 km (98 mi) of the Midland Main Line from London (St Pancras) to Leicester by 2022[20][21] while the specification for the proposed High Speed 2 (HS2) link from London to Manchester, Leeds and beyond assumes a minimum of Level 2 ERTMS control and signalling for the "day one service".[22] The Crossrail project in London will also implement ERTMS technology.[23]

In February 2016, Network Rail announced that it was considering a trial of ERTMS on the route from Norwich to Lowestoft and Great Yarmouth in East Anglia. This will be followed by a national roll-out, which will be carried out in stages with each of the twelve Rail Operating Centres being upgraded at a different time.[24]

See also

Notes

  1. Three levels have been identified for ERTMS:
    • Level 1 – ERTMS is added to or overlaid on lineside signals and train detectors. Communication is via balises (Eurobalises) of an existing railway system.
    • Level 2 – ERTMS uses balises to communicate with the driver, thereby dispensing with lineside signalling equipment. The location of each block is fixed (as with traditional railway systems).
    • Level 3 – Level 3 is an enhancement on Level 2 whereby the block will move with the train.
  2. As of 2012, the rebuilding of bridges to accommodate the overhead wires was in progress

References

  1. 'ERTMS in 10 questions,' http://ec.europa.eu/transport/rail/interoperability/ertms/doc/ertms_10_questions_en.pdf
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.