Have your say on the Crossrail Central Operating Section (CCOS) Access Arrangements

Closed 26 May 2017

Opened 31 Mar 2017

Overview

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

Background

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. The track access agreement will incorporate a number of other documents which set out some of the day-to-day practical arrangements. This consultation seeks views on the following draft documents:

  1. CCOS Track Access Agreement
  2. CCOS Network Code
  3. CCOS Access Dispute Resolution Rules
  4. CCOS Emergency Access Code
  5. CCOS Railway Systems Code
  6. CCOS Systems Catalogue
  7. CCOS Timetable Planning Rules
  8. CCOS Engineering Access Statement

A brief outline of the purpose of each document set out below. More detail is included in the accompanying consultation document. RfL(I) has considered existing equivalent documents from the railway industry, such as those used by Network Rail and HS1 Limited, in preparing these draft documents. In most cases, RfL(I)'s draft document has been modelled on Network Rail's equivalent document.

The CCOS Railway Operations Code, which is a document referred to in the CCOS Network Code, will form part of a separate consultation.

CCOS Track Access Contract
The CCOS Track Access Agreement sets out the terms and conditions under which a train operator can access the track forming part of the CCOS. For example, it sets out the number of train movements a train operator is entitled to, how much a train operator will pay RfL(I) for those train movements and how those charges can be modified in future. It also describes what happens when there is disruption – either as a result of planned engineering work or delays – and when other things go wrong. Every CCOS Track Access Agreement must be approved by the Office of Rail and Road.

CCOS Network Code
The CCOS Network Code is a common set of rules which will apply across every train operator which accesses the CCOS. This document forms part of the CCOS Track Access Agreement. It sets out, for example, how changes can be made to the CCOS infrastructure and the trains operating on the CCOS, how a timetable is developed by RfL(I) and how the environment is protected. It also describes the process for monitoring performance and the limited circumstances in which access rights can be lost.

CCOS Access Dispute Resolution Rules
Occasionally, disagreements may arise between RfL(I) and a train operator or train operators which cannot be resolved by discussion, negotiation and agreement. The CCOS Access Dispute Resolution Rules set out formal processes for the resolution of any disputes which may arise. These rules are appended to the CCOS Network Code – but are important in their own right. At the time of this consultation, RfL(I)'s current intention is to use the Access Disputes Committee to provide the services but this remains subject to agreement. The Access Disputes Committee also provides services to Network Rail. It is worth noting that the CCOS Access Dispute Resolution Rules are specific to access to the CCOS and are therefore separate to Network Rail's equivalent document.

CCOS Emergency Access Code
On rare occasions, it is possible that an emergency could affect the CCOS and/or the Network Rail network. In these emergency situations, it may become necessary for train operators who do not otherwise use particular sections of the track or particular stations on the CCOS to be granted access – for example, access to stations other than those normally called at. It also sets out what train operators who do use the CCOS may be required to do in such an emergency (each train operator using the CCOS will be required to comply with it). The CCOS Emergency Access Code sets out the terms and conditions upon which emergency access will be granted.

CCOS Railway Systems Code
RfL(I) will use a number of information technology systems in the operation of the CCOS, which train operators and others may wish to access. It is currently envisaged that some of these systems will be common to Network Rail's information technology systems but there is likely to be some specific systems for the CCOS itself. The CCOS Railway Systems Code sets out the scope of those systems, how users can access them and the circumstances where modifications can be made to the systems. Each train operator using the CCOS will be required to comply with the CCOS Railway Systems Code. The proposed Catalogue of Railway Systems, which is referred to in the CCOS Railway Systems Code, also forms part of this consultation.

CCOS Timetable Planning Rules
The CCOS Timetable Planning Rules are intended to set out the rules by which RfL(I) will develop the timetable for the operation of trains on the CCOS. They include, for example, the amount of time RfL(I) expects it to take for a train to move from one location to another on the CCOS, how much time there needs to be between trains and how trains will be timetabled to ensure performance can be kept at an appropriate level.

This consultation seeks initial views only and is not intended to replace the formal consultation processes set out in Part D of the draft CCOS Network Code.

CCOS Engineering Access Statement
From time to time, RfL(I) will need to gain access to the CCOS to undertake vital engineering work, including inspections and maintenance. This may mean that trains cannot operate on the CCOS at those times. The CCOS Engineering Access Statement sets out the dates and locations where RfL(I) proposes to undertake this engineering work in the relevant period – which may restrict the availability of the CCOS for train services.

This consultation seeks initial views only is not intended to replace the formal consultation processes set out in Part D of the draft CCOS Network Code.

Other consultations

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

Click here to view details of the consultation to designate the Crossrail Central Operating Section (CCOS) as Specialised Infrastructure

Click here to view our draft CCOS Network Statement consultation

Have your say

We would like to know what you think about our proposals. Please give us your views before midnight on Friday 26 May 2017 by completing the online consultation survey below.

Alternatively, you can:

Areas

  • All Areas

Audiences

  • Train operators

Interests

  • Crossrail