Back to Suppliers

Customer Requirement Specification (CRS) suite

Background:
The aim of the Customer Requirement Specification (CRS) suite has been to deliver sets of requirements that constitute a suitable basis for scheme development, option selection and, in a deployment project, inclusion within ‘Invitation to Tender’ (ITT) and Contract documentation, while allowing scope for innovation and creativity in meeting the overall needs of the deploying organisation.

The CRS set out functional, non-functional and process requirements for the System of Systems, which comprises the European Train Control System (ETCS) Trackside, ETCS On-board, Traffic Management System (TMS) and Connected Driver Advisory System (C-DAS).

Intended Use:
Deployment projects will use relevant documents from the CRS suite to identify the differences between the proposed systems architecture and the generic national System of Systems (SoS) architecture, and then select the requirements necessary to form the basis of the deployment-specific requirements specifications.

The CRS is suitable for use by suppliers in developing their System Requirements Specifications (SRS) which can then be verified against the ITT requirements, providing evidence that the system has been delivered and functions correctly.

In the future, the CRS suite will be supported by a suite of National Engineering Rules and Standards. The Digital Railway System Requirements & Integration team will undertake a review of National Engineering and Operational Rules to assess their applicability and identify any gaps requiring further work.

However, the rules from the existing System and Sub-System specifications have yet to be entered into the Engineering Rules structure. Consequently, the ETCS, TMS and C-DAS System and Sub-System Requirement Specifications will need to be used to support early deployment projects in establishing and verifying what the appropriate Engineering Rules and Standards for implementing and operating digital technologies should be.

Downloadable documents

Item
Select the title of the item to download the document
Description
System of Systems Customer Requirements Specification The purpose of this document is to set out the generic System of Systems (SoS) Customer Requirements.

These Customer Requirements are intended as a generic baseline to ensure that the system solutions adopted on any individual Deployment Project will integrate and be compatible across route boundaries.

 

Customer Requirements Specification for ETCS Trackside The purpose of this document is to set out the generic Customer Requirements for the ETCS Trackside, including functional, non-functional and process requirements. The ETCS Trackside includes interlocking functions which monitor and control trackside equipment.

 

Customer Requirements Specification for ETCS Onboard The purpose of this document is to set out the generic Customer Requirements for the ETCS Onboard, including functional, non-functional and process requirements. The ETCS Onboard comprises the European Vital Computer (EVC), Driver Machine Interface (DMI), balise readers, GSM-R data radio, odometry devices, juridical recorder (JRU) and interfaces to other train systems.

 

Customer Requirements Specification for Traffic Management The purpose of this document is to set out the generic Customer Requirements that apply to the Traffic Management System (TMS) when it is deployed on the GB railway network. These generic Customer Requirements are intended as a baseline to ensure that the TMS solutions adopted on any individual deployment project will integrate and be compatible across route boundaries and with the generic ETCS trackside, using TMS in the context of the System of Systems Generic Baseline Architecture.

 

Customer Requirements Specification for C-DAS The purpose of this document is to set out the generic Customer Requirements that apply to the Connected Driver Advisory System (C-DAS) when it is deployed on the GB railway network.

 

Interface Requirements Specification The purpose of this document is to set out the generic Interface Requirements applicable to each component of the Digital Railway System of Systems.

 

SoS System Definition The purpose of the SoS System Definition is to complement the hazard record by bounding the scope of the hazard identification and risk assessment process and provide sufficient context to facilitate an assessment of the correct application of the process by an independent body (the Assessment Body, or AsBo).

 

ETCS Trackside System Definition Defines the key details of the ETCS Trackside, its purpose, functions and interfaces, and the existing safety measures that apply to it, so that it provides a generic application design in support of subsequent development and deployment (i.e. application-specific design and implementation).
ETCS Onboard System Definition Defines the key details of the ETCS Onboard, its purpose, functions and interfaces, and the existing safety measures that apply to it, so that it provides a generic application design in support of subsequent development and deployment (i.e. application-specific design and implementation).

 

Traffic Management System Definition Defines the key details of the Traffic Management System, its purpose, functions and interfaces, and the existing safety measures that apply to it, so that it provides a generic application design in support of subsequent development and deployment (i.e. application-specific design and implementation).

 

C-DAS System Definition The System Definition defines the key details of the C-DAS, its purpose, functions, interfaces and the existing safety measures that apply to it, so that it provides a generic application design in support of subsequent development and deployment (i.e. application specific design and implementation).