Rail for London (Infrastructure) (RfL(I)), a wholly-owned TfL subsidiary, manages the CCOS infrastructure. These documents show how RfL(I) does business with customers, including potential operators of other train services.
Use this information to understand how to apply for access to operate train services through the CCOS.
The Network Statement is designed to provide prospective users of the CCOS with information about the infrastructure and how they would be able to gain access to the CCOS to operate trains.
The Framework Capacity Statement is intended to give prospective users of the CCOS an indication of how much capacity is likely to be available on the CCOS, giving them a first impression of how likely it is that their applications for capacity will be approved.
RfL(I) has developed a template form which can be used by train operators or prospective train operators when making capacity requests.
The latest annual data on the performance of the CCOS infrastructure:
(Performance data will be available here in 2019 after passenger services have started to run on the CCOS.)
The CCOS connects both in the east and the west to the Network Rail Infrastructure Limited (NR) network. To access the CCOS, potential train operators must also request access from the NR network and should do this before approaching RfL(I). Relevant information is on the Network Rail website.
The Track Access Contract sets out the terms and conditions under which a train operator can access the track forming part of the CCOS.
Track Access Contract - passenger services (Word template)
Track Access Contract - passenger services (PDF template)
Track Access Contract - testing services (Word template)
Track Access Contract - testing services (PDF template)
In Track Access Contracts entered into by RfL(I), certain information may be redacted for commercial confidentiality.
The CCOS Network Code is a common set of rules which will apply across every train operator accessing 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.
These standard forms are for requesting, issuing and responding to Vehicle Change proposals under Part F and Network Change proposals under Part G of the CCOS Network Code:
Occasionally, RfL(I) and a train operator or train operators may have a disagreement which cannot be resolved by discussion, negotiation and agreement. The CCOS Access Dispute Resolution Rules set out formal processes to resolve any disputes which may come up. These rules are appended to the CCOS Network 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.
Responsibility for delays to train services on the CCOS will be allocated in line with the Delay Attribution Principles and Rules (DAPR) (PDF 1.4MB).
This is issued by the Delay Attribution Board.
The CCOS Railway Operational Code sets out how RfL(I) intends to operate the CCOS. The key priority will be to ensure that trains operate according to 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 - the document is meant to be practical.
On rare occasions, an emergency may affect the CCOS and/or the Network Rail network. In these situations, train operators who do not otherwise use particular sections of the track or particular stations on the CCOS may need access - for example, access to stations other than those normally called at. The CCOS Emergency Access Code sets out the terms and conditions for granting emergency access.
RfL(I) will use a number of IT systems to operate the CCOS which train operators and others may wish to access. We expect some of these systems to be common to Network Rail's IT systems but some specific systems for the CCOS itself are likely.
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 CCOS Railway Systems Code refers to this list of systems - includes a brief description of each system.
The Timetable Planning Rules (TPR) and the Engineering Access Statement (EAS) are collectively referred to as the Operational Rules. These documents set out how RfL(I) will develop the timetable for the operation of trains on the CCOS. They are updated for each timetable year.
The TPR sets out the standard timings trains will take to run between locations such as stations and junctions, how much time there needs to be between trains and how trains will be timetabled to ensure appropriate performance.
The EAS describes the arrangements for engineering access to the CCOS. It sets out the location, number, date and duration of possession access required to deliver inspection, maintenance, renewal and enhancement activities on the infrastructure which may mean the CCOS is not available for train services.
Sunday 9 December 2018 to Saturday 14 December 2019:
Sunday 15 December 2019 to Saturday 12 December 2020:
The RfL(I) Station Access Agreement sets out the terms and conditions under which a train operator has permission to use an RfL(I) station.
The RfL(I) Station Access Conditions are a common set of rules which will apply across every train operator which accesses an RfL(I) station. The RfL(I) Station Access Conditions form part of the RfL(I) Station Access Agreement. For example, they set out how charges are determined and allocated between operators, and how they may be varied and how changes can be made to the RfL(I) station.
The RfL(I) Station Access Conditions Annexes contain specific information about individual stations such as plans, details of facilities at the station and charges for access to that station.