Crossrail Central Operating Section (CCOS) Access Arrangements

Closed 4 Aug 2017

Opened 7 Jul 2017


Transport for London (TfL) is seeking your views on further elements of its template contractual documentation for the Crossrail Central Operating Section (CCOS) track.


Crossrail will connect Reading and Heathrow to the west of London with Shenfield and Abbey Wood to the east, running through a new 13 mile (21km) twin-bore tunnel under central and east London. The tunnel under London (and associated infrastructure) will be the Crossrail Central Operating Section (or the CCOS). The CCOS has been designed to facilitate high capacity metro passenger rail services, moving high numbers of people more easily, more quickly and more directly across London. It will add ten per cent. to the overall capacity of London’s rail network and will offer crowding relief on the Underground and DLR networks, as well as at congested stations.

Transport for London (TfL) is currently the ultimate owner of the majority of the land comprising the CCOS and the infrastructure affixed to it. TfL has established a new wholly-owned subsidiary, Rail for London (Infrastructure) Limited (RfL(I)), which it intends to be responsible for the day-to-day operation and management of the CCOS. Services through the CCOS are expected to commence from 2018, with a full service across London expected to be from 2019.

Why are we consulting?

Train operators who wish to use the CCOS will be required to enter into a track access contract with RfL(I). This sets out the terms on which that train operator will be allowed to access the track. TfL consulted on most of its proposed template track access documentation for the CCOS in a consultation launched on March 31st 2017 (closed 26th May 2017). The track access agreement will incorporate a number of other documents which set out some of the day-to-day practical arrangements. At the time of the consultation above two of these documents were outstanding, namely The Performance Data Accuracy Code and The Railway Operational Code and it was noted that these documents would be the subject of a later consultation. TfL is now launching a consultation on to seek views on these documents, a brief description of each of which is set out below.

RfL(I) has considered existing equivalent documents from the railway industry, such as those used by Network Rail in preparing these draft documents.

CCOS Performance Data Accuracy Code
The CCOS Track Access Agreement and CCOS Network Code set out how RfL(I) will monitor the journey of each train on the CCOS and where performance payments may become due for delays. The CCOS Performance Data Accuracy Code supports the operation of this: it sets out the level to which RfL(I) will maintain performance information and the arrangements which will be put in place if the performance monitoring system does not work as expected.

CCOS Performance Data Accuracy Code (PDF)

CCOS Railway Operations Code
The CCOS Railway Operations Code sets out how RfL(I) intends to operate the CCOS. The key priority will be to ensure that trains are operated in accordance with the timetable – whether during normal operations or times of disruption affecting the CCOS (so it will include steps RfL(I) will take to restore normal operations). This requirement comes from Part H of the CCOS Network Code and the document is intended to be practical in nature.

CCOS Railway Operations Code (PDF)

Other consultations

TfL/RfL(I) has previously consulted on designating the CCOS as specialised infrastructure (which has now been designated as such), the draft Network Statement for the CCOS and draft track access documentation for the CCOS. The feedback from these consultations has been taken into account in preparing the draft documents for this consultation.

Have your say

We would like to know what you think about our proposals. Please give us your views before 17:00 on Friday 4 August 2017 by completing the online consultation survey below. Alternatively, you can:


  • All Areas


  • Train operators


  • Crossrail