Rail Operating Centre

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:66130 at Didcot.jpg
66130 is seen passing the TSVC/ROC at Didcot with an MoD service from Bicester. The ROC is the building on the left with the black Network Rail logo

A Rail Operating Centre (ROC) is a building that will house all signallers, signalling equipment, ancillaries and operators for a specific region or route on the United Kingdom's main rail network. The ROC supplants the work of several other signal boxes which will then become redundant. Network Rail announced the creation of 14[1][2] ROCs situated throughout Great Britain that will eventually control all railway signalling over the British Railways network. This has been revised to 12 ROCs[3] with responsibilities at two (Saltley and Ashford) being transferred to other ROCs (Rugby and Gillingham respectively).[4]

Nationally this will mean the removal of 800 mechanical lever signal boxes[5] and around 200 Panel and IECC boxes.[6] Some are listed buildings and will be left in situ.[7]

The ROCs are being built under private contracts for Network Rail and as such will only apply to the rail routes controlled by Network Rail. Railways in Northern Ireland, various heritage railways and other tramways are not subject to control by an ROC. Ashford IECC will still control the UK stretch of the Eurotunnel Rail Link (HS1/CTRL).[4]

The ROCs will function as signalling and control centres with signalling staff, Train Operating Company (TOC) staff and Network Rail controllers all working under one roof. This will enable quick solutions to signalling problems and less delays to trains and passengers. Network Rail envisage the 12 ROCs to be controlling the entire network by 2058.[8]

Signalling History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Originally, the early railways employed policemen to time the intervals between trains and to give a 'stop' signal if a train had passed in the previous ten minutes.[9] Developments led to many everyday workings (such as interlocking points)[10] and signal boxes to house the levers that allowed signallers to change the points and signals over a given stretch of railway.[11] These signalboxes were often elevated above the railway due to the locking mechanisms of the signals and points being accommodated on the lower storey.[12] This also allowed the signaller to keep an eye on things from a good vantage point.[13]

At the end of the Second World War, the United Kingdom network was host to over 10,000 mechanical lever signalboxes.[14] When British Rail was created from the Big Four private railway companies[15][16] under the 1947 Transport Act,[17] they began to install Power Signal Boxes (PSB) at strategic locations such as Euston, Crewe, Doncaster, Rugby and Carlisle.[18] The PSBs would remove the necessity for lots of individual boxes along a particular route and would pass control to one centralized location. Carlisle's PSB took over the responsibility of 44 signal boxes alone in the north west area.[19]

A step on from the PSBs was the IECC, Integrated Electronic Control Centre, a forerunner of the ROCs. The first IECC panel was installed at London Liverpool Street in 1989.[20]

When the railways in Britain were privatized in 1994,[16][note 1][21] staff from the then operating company, Railtrack, paid a visit to the Union Pacific Operating Centre, USA in 1999.[22] After viewing the facilities and seeing the control they decided that a handful of major operating centres was the way forward for UK operations. Just one centre was approved and built in 2003 at Saltley, near to Birmingham, as part of the West Coast Route Modernisation.[23] However this building was not connected for some time and whilst it was used by Network Rail Staff, no signalling equipment was installed until 2006.[24]

European Rail Traffic Management System (ERTMS)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

With the advent of the 'Digital Railway',[25] signalling methods such as ERTMS have been adopted as a way forward by Network Rail. There are two components of ERTMS; ECTS - European Train Control System and TMS - Traffic Management system. Whereas lineside signals operated by a signaller would control train movements, ETCS will signal trains via a computer without lineside apparatus. In effect, the train creates its own 'buffer zone' through a digital signal transmitted from the cab.[26] An onboard computer on the train will inform the driver of the 'allowable speed and movement of the train.'[27] TMS allows delays to be minimised through a computer running algorithms and deciding how best to return traffic patterns to normal.

These systems mean the removal of traditional signalling infrastructure and the signal boxes that go with them.

Antecedents

York IECC (Integrated Electronic Control Centre) is an example of an early version of a ROC. York IECC was opened in 1989[28] and controlled a large region in Yorkshire bounded by Gargrave, South Emsall, Selby, Northallerton, Cottingley (Leeds), Bramley and the Harrogate loop .[29][30] The ROC, which opened in York on 12 September 2014,[31] superseded the York IECC in January 2015[32] and will eventually control the East Coast Main Line and associated lines in Lincolnshire, Yorkshire and the Humber and the North East of England.[33] This means a Kings Cross to Edinburgh train will be signalled from York ROC all the way from Kings Cross to the Scottish Borders.[34]

Saltley ROC will become a remote signalling centre of Rugby. The facility at Saltley was opened as a bomb-proof[35] signalling centre for the West Coast Route Modernisation.[36] However, the inability to achieve a workable Traffic Management System (TMS)[37] without lineside signalling, meant an increased budget of £1.4 billion[38] and the building became a white elephant.[39] The structure was slowly integrated into an ROC function with signalling upgrades transferring responsibility to Saltley starting in 2006.[40] Because the interlocking mechanisms are in place, they will be left at Saltley and operated remotely from the Rugby ROC. What Saltley cannot do, that Rugby can, is host the human space needed for the signallers and Train Operating Company (TOC) staff to work together.[24]

File:Network Rail Regions 18 November 2015.png
Network Rail Regions map with Rail Operating Centres (ROCs) annotated. This representational only and is not to scale.

ROC locations

No Region Name Date opened Route Notes
1 Ashford 1993[4] Kent Responsibility for control of Ashford IECC will be divided between Three Bridges and Gillingham.[41]
2 Basingstoke April 2016[42][note 2] Wessex
3 Cardiff 24 October 2010[43] Wales
4 Cowlairs December 2008[44] Scotland (West) Was originally opened as the West of Scotland Signalling Centre (WSSC).[45]
5 Derby 3 April 2008[46] East Midlands Was formerly known as the EMCC (East Midlands Control Centre)[47]
6 Didcot March 2010[48] Western Also known as the Thames Valley Signalling Centre (TVSC).[49]
7 Edinburgh 1976[50] Scotland (East) Originally opened as a PSB, then transferred to IECC in 2006.[51]
8 Gillingham 1994.[52] Kent Opened in 1994 as the East Kent Signalling Centre, but not used. Became Railtrack Archive.[53]
9 Manchester 21 July 2014[54] LNW Will control all lines in the north west in addition to West Coast Main Line from Crewe to Carlisle.[55]
10 Romford February 2015[56][note 3][57] East Anglia
11 Rugby 13 November 2015[58] LNW
12 Saltley 13 March 2003[59] LNW First ROC Opened in 2003.[note 4] Functions will be transferred to Rugby ROC by 2019.[60]
13 Three Bridges 7 January 2014[61] Sussex
14 York 12 September 2014[62] LNE Projected last signal box transfer on the network will be to York in 2056 when Morpeth box closes.[63]

Benefits of the ROCs

Whilst the drive for the ROCs has been one of signalling upgrades, there are other benefits and detractions to the scheme. Around 4000 staff will lose their jobs over the course of the implementation programme leaving 2000 signallers in the ROCs.[64] The benefits of centralised control will be that the Train Operating Company (TOC) staff will work alongside the Network Rail staff to allow cohesive problem solving such as resolving late running and last minute platform changes. Network Rail have said that 'The ROC is a key part of our strategy to improve reliability whilst driving down the cost of running and maintaining the railway.'[65]

Acronym confusion

ROC is mostly referred to as the Rail Operating Centre.[66] Even in Network Rail's own documentation it is sometimes referred to as a Railway Operating Centre.[67] Some of the railway press have referred to them as Route Operating Centre[68][note 5] and even Regional Operating Centre.[69][70]

This issue is further clouded by Network Rail having another ROC, the Railway Operational Code[71] and the signalling industry in the United Kingdom having a Remote Override Control.[72]

Notes

  1. This date refers to the privatization of the infrastructure under Railtrack. The Train operating Companies would not see final privatization until 1997.
  2. This is a projected opening date and so the actual date of opening may vary.
  3. This date is from Network Rail's own documentation. However, in April 2015, UMC Architects published a news article on their website that suggested the building was not finished. See next citation.
  4. Originally opened as the West Coast Route Modernisation Control Centre (WCRMCC), then as the Network Management Centre, then as IECC and finally moved to ROC.
  5. Whilst this is a direct quote from an interview, the interviewer does not make use of a [sic] modifier to correct this error.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  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. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. 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. 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. 16.0 16.1 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. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.