Commission Regulation (EU) 2016/919 of 27 May 2016 on the technical specification for interoperability relating to the ‘control-command and signalling’ subsystems of the rail system in the European Union (Text with EEA relevance)
Corrected by
- Corrigendum to Commission Regulation (EU) 2016/919 of 27 May 2016 on the technical specification for interoperability relating to the control-command and signalling subsystems of the rail system in the European Union, 32016R0919R(01), October 15, 2016
(a) the trans-European conventional rail system network as defined in Annex I, point 1.1 to Directive 2008/57/EC; (b) the trans-European high-speed rail system network as defined in Annex I, point 2.1 to Directive 2008/57/EC; (c) other parts of the network of the rail system in the Union, following the extension of scope as described in Annex I point 4 of Directive 2008/57/EC;
(a) the open points specified in Annex G; (b) the specific cases set out in point 7.6.2 of the Annex;
(1) installing the train protection part of a CCS subsystem for the first time; or (2) upgrading the train protection part of a CCS subsystem already in service, where upgrading changes the functions or the performance of the subsystem.
5 years after the end of the project, the date on which the section of the line is connected to another ETCS equipped line.
(1) self-propelling thermal or electric trains; (2) thermal or electric traction units; (3) passenger carriages, if equipped with a driving cab; (4) mobile railway infrastructure construction and maintenance equipment, if equipped with a driving cab and intended to be used in transport mode on its own wheels.
(1) the trans-European conventional rail system network as described in Annex I point 1.1 of Directive 2008/57/EC; (2) the trans-European high-speed rail system network as described in Annex I point 2.1 of Directive 2008/57/EC; (3) other parts of the network of the rail system in the Union, following the extension of scope as described in Annex I point 4 of Directive 2008/57/EC;
(1) indicates its intended scope — Chapter 2 (Subsystem Definition and Scope); (2) lays down essential requirements for the Control-Command and Signalling Subsystems and their interfaces vis-à-vis other subsystems — Chapter 3 (The Essential Requirements of the Control-Command and Signalling Subsystems); (3) lays down the functional and technical specifications to be met by the Subsystems and their interfaces vis-à-vis other subsystems — Chapter 4 (Characterisation of the Subsystem); (4) determines the interoperability constituents and interfaces which must be covered by European specifications, including European standards, and which are necessary to achieve interoperability within the Union rail system — Chapter 5 (Interoperability Constituents); (5) states, in each case under consideration, which procedures are to be used to assess the conformity or the suitability for use of the interoperability constituents and for the "EC" verification of the subsystems — Chapter 6 (Assessing the Conformity and/or Suitability For Use of the Constituents and Verifying the Subsystems); (6) indicates the strategy for implementing this TSI. — Chapter 7 (Implementing the Control-Command and Signalling Subsystems TSI); (7) indicates the professional competences and health and safety conditions at work required for the staff operating and maintaining these subsystems and implementing the TSI — Chapter 4 (Characterisation of the Subsystem).
(1) the functions that are essential for the safe control of railway traffic, and that are essential for its operation, including those required for degraded modes Degraded modes are modes of operation designed to deal with faults. They have been taken into account when designing the Control-Command and Signalling Subsystems (2) the interfaces; (3) the level of performance required to meet the essential requirements.
(1) train protection; (2) voice radio communication; (3) data radio communication; (4) train detection.
(1) the Class A radio network; (2) Class A train protection; (3) the interface requirements for train detection systems, to ensure their compatibility with rolling stock.
A train equipped with Class A on-board train protection for level 2 must be able to operate on that level and on level 1 lines. A train equipped with Class A on-board train protection for level 1 need not be equipped with a GSM-R ETCS Data Only Radio but must already implement all level 2 and level 3 functions so as to ensure that: the connection of a GSM-R ETCS Data Only Radio at a later stage will ensure it is equipped for level 2, the connection of a GSM-R ETCS Data Only Radio and of train integrity detection at a later stage will ensure it is equipped for level 3.
(1) Safety; (2) Reliability and Availability; (3) Health; (4) Environmental Protection; (5) Technical compatibility.
(1) the Control-Command and Signalling equipment, if subjected to excessive heat or fire, shall not exceed limits for the emission of fumes or gases which are harmful to the environment; (2) the Control-Command and Signalling equipment shall not contain substances which may abnormally contaminate the environment during their normal use; (3) the Control-Command and Signalling equipment shall be subject to the Union legislation in force controlling the limits to the emission of and the susceptibility to electromagnetic interference along the boundaries of railway property; (4) the Control-Command and Signalling equipment shall comply with existing regulations on noise pollution; (5) the Control-Command and Signalling equipment shall not give rise to any inadmissible level of vibration which could jeopardise the integrity of the infrastructure (when the infrastructure is in the correct state of maintenance).
(1) The first category sets out the general engineering requirements for interoperability namely environmental conditions, internal electromagnetic compatibility (EMC) within the railway boundaries, and installation. These compatibility requirements are defined in this chapter. (2) The second category describes how the Control Command and Signalling Subsystems have to be applied technically and what functions they have to perform to ensure interoperability. This category is defined in Chapter 4. (3) The third category describes how the Control Command and Signalling Subsystems have to be operated in order that interoperability is achieved. This category is defined in Chapter 4.
(1) Control-Command and Signalling safety characteristics relevant to interoperability (point 4.2.1) (2) On-board ETCS functionality (point 4.2.2) (3) Trackside ETCS functionality (point 4.2.3) (4) Mobile communication functions for railways — GSM-R (point 4.2.4) (5) ETCS and GSM-R air gap interfaces (point 4.2.5) (6) On-board interfaces Internal to Control-Command and Signalling (point 4.2.6) (7) Trackside interfaces Internal to Control-Command and Signalling (point 4.2.7) (8) Key management (point 4.2.8) (9) ETCS-ID management (point 4.2.9) (10) Train detection systems (point 4.2.10) (11) Electromagnetic compatibility between rolling stock and Control-Command and Signalling trackside equipment (point 4.2.11) (12) ETCS DMI (driver-machine interface) (point 4.2.12) (13) GSM-R DMI (driver-machine interface) (point 4.2.13) (14) Interface to data recording for regulatory purposes (point 4.2.14) (15) Visibility of trackside Control-Command and Signalling objects (point 4.2.15) (16) Construction of equipment used in CCS subsystems (points 4.2.16).
(1) functions, interfaces and performances of the Control-Command and Signalling On-board Subsystem are standardised, ensuring that every train will react in a predictable way to data received from trackside; (2) for the Control-Command and Signalling Trackside Subsystem, track-to-train and train-to-track communication are fully standardised in this TSI. The specifications referenced in the points below allow Control-Command and Signalling trackside functionality to be applied in a flexible way, so that it can be optimally integrated into the railway system. This flexibility shall be exploited without limiting the movement of TSI-compliant on-board subsystems.
| Subsystem | Part | Basic parameters |
|---|---|---|
| Control-Command and Signalling On-board | Train protection | 4.2.1, 4.2.2, 4.2.5, 4.2.6, 4.2.8, 4.2.9, 4.2.12, 4.2.14, 4.2.16 |
| Voice radio communication | 4.2.1.2, 4.2.4.1, 4.2.4.2, 4.2.5.1, 4.2.13, 4.2.16 | |
| Data radio communication | 4.2.1.2, 4.2.4.1, 4.2.4.3, 4.2.5.1, 4.2.6.2, 4.2.16 | |
| Control-Command and Signalling Trackside | Train protection | 4.2.1, 4.2.3, 4.2.5, 4.2.7, 4.2.8, 4.2.9, 4.2.15, 4.2.16 |
| Voice and data radio communication | 4.2.1.2, 4.2.4, 4.2.5.1, 4.2.7, 4.2.16 | |
| Train detection | 4.2.10, 4.2.11, 4.2.16 |
(1) The design, implementation and use of a Control-Command and Signalling On-board or Trackside subsystem shall not export any requirements: (a) across the interface between Control-Command and Signalling On-board and Trackside subsystems in addition to the requirements specified in this TSI; (b) to any other subsystem in addition to the requirements specified in the corresponding TSIs.
(2) The requirements set out in points 4.2.1.1 and 4.2.1.2 below shall be respected.
(1) Mean time of hours of operation between failures of a CCS on-board subsystem requiring the isolation of the train protection functions: (open point). (2) Mean time of hours of operation between failures of a CCS on-board subsystem preventing radio voice communication between traffic control and the train driver: (open point).
(1) setting the train characteristics (e.g. maximum train speed, braking performance); (2) selecting the supervision mode on the basis of information from trackside; (3) performing odometry functions; (4) locating the train in a coordinate system based on Eurobalise locations; (5) calculating the dynamic speed profile for its mission on the basis of train characteristics and of information from trackside; (6) supervising the dynamic speed profile during the mission; (7) providing the intervention function.
(1) Communication with the Control-Command and Signalling Trackside Subsystem. (a) Eurobalise data transmission. See point 4.2.5.2 (Eurobalise communication with the train). (b) Euroloop data transmission. See point 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed trackside in ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points). (c) Radio data transmission for radio infill. See Annex A, 4.2.2 d, point 4.2.5.1 (Radio communications with the train), point 4.2.6.2 (Interface between GSM-R Radio Data Communication and ETCS) and point 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio infill is installed trackside in ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points). (d) Radio data transmission. See point 4.2.5.1 (Radio communications with the train), point 4.2.6.2 (Interface between GSM-R Radio Data Communication and ETCS) and point 4.2.8 (Key Management). Only mandatory on-board for ETCS Level 2 or ETCS Level 3 applications.
(2) Communicating with the driver. See Annex A, 4.2.2 e and point 4.2.12 (ETCS DMI). (3) Communicating with the STM. See point 4.2.6.1 (Interface between ETCS and STM). This function includes: (a) managing the STM output; (b) providing data to be used by the STM; (c) managing STM transitions.
(4) Managing information about the completeness of the train (train integrity) — mandatory for level 3, not required for level 1 or 2. (5) Equipment health monitoring and degraded mode support. This function includes: (a) initialising the on-board ETCS functionality; (b) providing degraded mode support; (c) isolating the on-board ETCS functionality.
(6) Support data recording for regulatory purposes. See point 4.2.14 (Interface to Data Recording for Regulatory Purposes). (7) Forwarding information/orders and receiving state information from rolling stock: (a) to the DMI. See point 4.2.12 (ETCS DMI); (b) to/from the train interface unit. See Annex A, 4.2.2 f.
(1) locating a specific train in a coordinate system based on Eurobalise locations (level 2 and level 3); (2) translating the information from trackside signalling equipment into a standard format for the Control-Command and Signalling On-board Subsystem; (3) sending movement authorities including track description and orders assigned to a specific train.
(1) communicating with the Control-Command and Signalling On-board Subsystem. This includes: (a) Eurobalise data transmission. See point 4.2.5.2 (Eurobalise communication with the train) and point 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU)); (b) Euroloop data transmission. See point 4.2.5.3 (Euroloop communication with the train) and point 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional; (c) radio data transmission for radio infill. See Annex A, 4.2.3d, point 4.2.5.1 (Radio communications with the train), point 4.2.7.3 (GSM-R/trackside ETCS functionality) and point 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional; (d) radio data transmission. See point 4.2.5.1 (Radio communications with the train), point 4.2.7.3 (GSM-R/trackside ETCS functionality) and point 4.2.8 (Key Management). Radio data transmission is only relevant to level 2 and level 3;
(2) generating information/orders to the on-board ETCS, e.g. information related to closing/opening the air flaps, lowering/raising the pantograph, opening/closing the main power switch, changing from traction system A to traction system B. Implementation of this functionality is optional for trackside; it can however be required by other applicable TSIs or national rules or the application of risk evaluation and assessment to ensure safe integration of subsystems; (3) managing the transitions between areas supervised by different Radio Block Centres (RBCs) (only relevant for level 2 and level 3). See point 4.2.7.1 (Functional interface between RBCs) and point 4.2.7.2 (Technical interface between RBCs).
(1) ASCI features; Annex A 4.2.4b; (2) SIM card; Annex A 4.2.4c; (3) location-dependent addressing; Annex A 4.2.4e.
(1) confirmation of high priority calls; Annex A 4.2.4h; (2) functional addressing; Annex A 4.2.4j; (3) presentation of functional numbers; Annex A 4.2.4k; (4) User-to-User Signalling; Annex A 4.2.4d.
(1) the physical, electrical and electromagnetic values to be respected to allow safe functioning; (2) the communication protocol to be used; (3) the availability of the communication channel.
(1) Information from the "Handing Over" RBC to the "Accepting" RBC. (2) Information from the "Accepting" RBC to the "Handing Over" RBC.
(1) ergonomics (including visibility); (2) ETCS functions to be displayed; (3) ETCS functions triggered by driver input.
(1) ergonomics (including visibility); (2) GSM-R functions to be displayed; (3) call-related information outgoing; (4) call-related information incoming.
(1) data exchange between the on-board ETCS and the rolling stock recording device; (2) communication protocols; (3) physical interface.
(1) the characteristics of retro-reflecting signs to ensure correct visibility; (2) the characteristics of interoperable marker boards.
| Interface with Traffic Operation and Management TSI | |||
|---|---|---|---|
| Reference CCS TSI | Reference Traffic Operation and Management TSI | ||
| Parameter | Clause | Parameter | Clause |
| Operating rules (normal and degraded conditions) | 4.4 | Rule book | 4.2.1.2.1 |
| Operating rules | 4.4 | ||
| Visibility of trackside Control-Command and Signalling objects | 4.2.15 | Signal and line-side marker sighting | 4.2.2.8 |
| Train braking performance and characteristics | 4.2.2 | Braking performance | 4.2.2.6 |
| 4.2.10 | Rule book | 4.2.1.2.1 | |
| Interface to Data Recording for Regulatory Purposes | 4.2.14 | Data recording on board | 4.2.3.5 |
| ETCS DMI | 4.2.12 | Train running number | 4.2.3.2.1 |
| GSM-R DMI | 4.2.13 | Train running number | 4.2.3.2.1 |
| Interface with Rolling Stock TSIs | ||||
|---|---|---|---|---|
| Reference CCS TSI | Reference Rolling Stock TSIs | |||
| Parameter | Clause | Parameter | Clause | |
| Compatibility with trackside train detection systems: vehicle design | 4.2.10 | Rolling stock characteristics to be compatible with train detection systems based on track circuits |
| |
| Rolling stock characteristics to be compatible with train detection systems based on axle counters |
| |||
| Rolling stock characteristics to be compatible with loop equipment | ||||
| Electromagnetic compatibility between rolling stock and Control-Command and Signalling trackside equipment | 4.2.11 | Rolling stock characteristics to be compatible with train detection systems based on track circuits | ||
| Rolling stock characteristics to be compatible with train detection systems based on axle counters | ||||
| Train braking performance and characteristics | 4.2.2 | Emergency braking performance |
| |
| Position of Control-Command and Signalling on-board antennas | 4.2.2 | Kinematic gauge | ||
| Isolation of on-board ETCS functionality | 4.2.2 | Operating rules | ||
| Data interfaces | 4.2.2 | Monitoring and diagnostic concepts | ||
| Visibility of trackside Control-Command and Signalling objects | 4.2.15 | |||
| Driver’s external field of view |
| |||
| Interface to data recording for regulatory purposes | 4.2.14 | Recording device | ||
| Commands to rolling stock equipment | Phase separation | |||
| Emergency braking command | 4.2.2 | Emergency braking command | ||
| Construction of equipment | 4.2.16 | Material requirements | ||
| Interface with Infrastructure TSI | ||||
|---|---|---|---|---|
| Reference CCS TSI | Reference Infrastructure TSI | |||
| Parameter | Clause | Parameter | Clause | |
| Train detection systems (space for installation) | 4.2.10 | |||
| Eurobalise communication (space for installation) | 4.2.5.2 | |||
| Euroloop communication (space for installation) | 4.2.5.3 | |||
| Visibility of trackside Control-Command and Signalling objects | 4.2.15 | |||
| Interface with Energy TSI | ||||
|---|---|---|---|---|
| Reference CCS TSI | Reference Energy TSI | |||
| Parameter | Clause | Parameter | Clause | |
| Commands to rolling stock equipment | ||||
(1) all maintenance requirements and procedures (including health monitoring, diagnosis of events, test methods and tools and also the required professional competence) necessary for achieving essential requirements and values quoted in the mandatory requirements of this TSI throughout the equipment life-cycle (transport and storage before installation, normal operation, failures, repair work, checking and maintenance, decommissioning, etc.); (2) the health and safety risks that may affect the public and the maintenance staff; (3) the conditions for first line maintenance, i.e. the definition of Line Replaceable Units (LRUs), the definition of approved compatible versions of hardware and software, the procedures for replacing failed LRUs, the conditions for storing LRUs and for repairing failed LRUs; (4) the checks to be carried out if equipment is subject to exceptional stress (e.g. adverse environmental conditions or abnormal shocks); (5) the checks to be carried out when maintaining equipment other than Control-Command and Signalling equipment and which influences the Control-Command and Signalling Subsystems (e.g. changing the wheel diameter).
(1) ensure that the maintenance requirements as described in point 4.5.1 (Responsibility of the Manufacturer of Equipment) are defined for all components within the scope of this TSI regardless of whether or not they are interoperability constituents; (2) complete the above requirements taking into account the risks arising from interactions between different components of the subsystem and interfaces to other subsystems.
(1) Table 5.1.a for the Control-Command and Signalling On-board Subsystem; (2) Table 5.2.a for the Control-Command and Signalling Trackside Subsystem.
(1) Table 5.1.b lists the groups of interoperability constituents of the Control-Command and Signalling On-board Subsystem. (2) Table 5.2.b lists the groups of interoperability constituents of the Control-Command and Signalling Trackside Subsystem.
(1) in column 3, the functions and interfaces. Note that some interoperability constituents have functions and/or interfaces that are optional; (2) in column 4, the mandatory specifications for the conformity assessment of each function or interface (where applicable) by reference to the relevant point of Chapter 4.
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| N | Interoperability constituent IC | Characteristics | Specific requirements to be assessed by reference to Chapter 4 |
| 1 | ETCS on-board | Reliability, Availability, Maintainability, Safety (RAMS) | |
| On-board ETCS functionality (excluding odometry) | 4.2.2 | ||
| |||
| |||
| Construction of equipment | 4.2.16 | ||
| 2 | Odometry equipment | Reliability, Availability, Maintainability, Safety (RAMS) | |
| On-board ETCS functionality: only Odometry | 4.2.2 | ||
| 4.2.6.3 | ||
| Construction of equipment | 4.2.16 | ||
| 3 | Interface of External STM |
| 4.2.6.1 |
| 4 | |||
| Basic communication functions | 4.2.4.1 | ||
| Voice and operational communication applications | 4.2.4.2 | ||
| |||
| Construction of equipment | 4.2.16 | ||
| 5 | |||
| Basic communication functions | 4.2.4.1 | ||
| ETCS data communication applications | 4.2.4.3 | ||
| |||
| Construction of equipment | 4.2.16 | ||
| 6 | Basic communication functions | 4.2.4.1 | |
| Construction of equipment | 4.2.16 |
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| N | Group of Interoperability constituents | Characteristics | Specific requirements to be assessed by reference to Chapter 4 |
| 1 | Reliability, Availability, Maintainability, Safety (RAMS) | ||
| On-board ETCS functionality | 4.2.2 | ||
| |||
| |||
| Construction of equipment | 4.2.16 |
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| N | Interoperability constituent IC | Characteristics | Specific requirements to be assessed by reference to Chapter 4 |
| 1 | RBC | Reliability, Availability, Maintainability, Safety (RAMS) | |
| Trackside ETCS functionality (excluding communication via Eurobalises, radio in-fill and Euroloop) | 4.2.3 | ||
| ETCS and GSM-R air gap interfaces: only radio communication with train | 4.2.5.1 | ||
| |||
| Construction of equipment | 4.2.16 | ||
| 2 | Radio in-fill unit | Reliability, Availability, Maintainability, Safety (RAMS) | |
| Trackside ETCS functionality (excluding communication via Eurobalises, Euroloop and level 2 and level 3 functionality) | 4.2.3 | ||
| ETCS and GSM-R air gap interfaces: only radio communication with train | 4.2.5.1 | ||
| |||
| Construction of equipment | 4.2.16 | ||
| 3 | Eurobalise | Reliability, Availability, Maintainability, Safety (RAMS) | |
| ETCS and GSM-R air gap interfaces: only Eurobalise communication with train | 4.2.5.2 | ||
| 4.2.7.4 | ||
| Construction of equipment | 4.2.16 | ||
| 4 | Euroloop | Reliability, Availability, Maintainability, Safety (RAMS) | |
| ETCS and GSM-R air gap interfaces: only Euroloop communication with train | 4.2.5.3 | ||
| 4.2.7.5 | ||
| Construction of equipment | 4.2.16 | ||
| 5 | LEU Eurobalise | Reliability, Availability, Maintainability, Safety (RAMS) | |
| Trackside ETCS functionality (excluding communication via radio in-fill, Euroloop and level 2 and level 3 functionality) | 4.2.3 | ||
| 4.2.7.4 | ||
| Construction of equipment | 4.2.16 | ||
| 6 | LEU Euroloop | Reliability, Availability, Maintainability, Safety (RAMS) | |
| Trackside ETCS functionality (excluding communication via radio in-fill, Eurobalise and level 2 and level 3 functionality) | 4.2.3 | ||
| 4.2.7.5 | ||
| Construction of equipment | 4.2.16 |
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| N | Group of interoperability constituents | Characteristics | Specific requirements to be assessed by reference to Chapter 4 |
| 1 | Reliability, Availability, Maintainability, Safety (RAMS) | ||
| Trackside ETCS functionality (excluding communication via Euroloop and level 2 and level 3 functionality) | 4.2.3 | ||
| ETCS and GSM-R air gap interfaces: only Eurobalise communication with train | 4.2.5.2 | ||
| Construction of equipment | 4.2.16 | ||
| 2 | Reliability, Availability, Maintainability, Safety (RAMS) | ||
| Trackside ETCS functionality, (excluding communication via Eurobalise and level 2 and level 3 functionality) | 4.2.3 | ||
| ETCS and GSM-R air gap interfaces: only Euroloop communication with train | 4.2.5.3 | ||
| Construction of equipment | 4.2.16 |
(1) assessing the conformity of the interoperability constituents specified in Chapter 5 (see point 6.2.1, 6.2.2, 6.2.3, 6.2.4); (2) verifying the subsystems (see point 6.3 and point 6.4.1).
(1) the use of Class B systems; (2) open points in the TSI; (3) derogations under Article 9 of Directive 2008/57/EC; (4) specific cases described in point 7.6.
(1) the applicant for EC verification of a trackside control-command and signalling subsystem is responsible for deciding which functions, performance and interfaces need to be implemented to meet the objectives for the service and to ensure that no requirements contradicting or exceeding the TSIs are exported to the on-board control-command and signalling subsystems; (2) the operation of an on-board control-command and signalling subsystem, that does not implement all functions, performance and interfaces specified in this TSI, may be subject to conditions or restrictions due to compatibility and/or safe integration with trackside control-command and signalling subsystems. Without prejudice to the tasks of a notified body described in respective Union legislation and related documents the applicant for EC verification is responsible for ensuring that the technical file provides all the information that an operator needs to identify such conditions and restrictions; (3) the Member State may refuse for duly justified reasons the authorisation for placing in service, or place conditions and restrictions on the operation, of control-command and signalling subsystems that do not implement all functions, performance and interfaces specified in this TSI.
(1) rules for the design and installation of the Control-Command and Signalling On-board and the Trackside subsystems; (2) test specifications to prove that the Control-Command and Signalling On-board and Trackside Subsystems comply with the requirements of this TSI and are mutually compatible.
(1) shall be consistent with the specifications referenced in this TSI; (2) shall assume that functions, interfaces and performance of the Control-command and Signalling On-board Subsystems interacting with the Trackside Subsystem are compliant with the requirements of this TSI; (3) shall be the ones used in the EC Verification of the Trackside Control-command and Signalling Subsystem, to check that the implemented functions, interfaces and performance are able to ensure that the intended system operation in combination with the relevant modes and transitions between levels and modes of the Control-command and Signalling On-board Subsystems are respected.
(1) shall publish the engineering rules for the trackside parts of ETCS and GSM-R and the operational test scenarios. After publication of preliminary scenarios or of their subsequent modifications, all interested parties shall be allowed to comment on the consistency of the operational test scenarios with the conditions stated in the three intends above. The period for comments shall be defined with each publication and shall not exceed six months; this period shall not be a constraint on the continuation/finalisation of the EC Verification of the relevant Trackside subsystem(s); (2) shall, if the comments are negative, coordinate the efforts of the parties involved, in order to find an agreement, e.g. by changing the engineering rules for the trackside parts of ETCS and GSM-R and, consequently, the operational test scenarios, in case they are in contradiction with the requirements of this TSI; (3) shall publish and maintain the operational test scenarios that have successfully passed the steps described above and representing the situations which occur in different implementations; (4) shall use the received operational test scenarios to assess whether clarifications or improvements of the specifications referenced in this TSI are necessary; (5) shall, on the basis of the operational tests scenarios received, prepare and publish a standard format for future publications of operational test scenario.
(1) either the type-examination procedure (Module CB) for the design and development phase in combination with the production quality management system procedure (Module CD) for the production phase; or (2) the type-examination procedure (Module CB) for the design and development phase in combination with the product verification procedure (Module CF); or (3) the full quality management system with design examination procedure (Module CH1).
(1) with reference to Chapter 2 of the "Module CB", "EC"-type examination shall be carried out through a combination of production type and design type; (2) with reference to Chapter 3 of the "Module CF" (product verification) statistical verification is not allowed, i.e. all interoperability constituents shall be individually examined.
(1) the requirements stated in point 6.2.4.1 of this TSI shall be respected for the "On-board ETCS" interoperability constituent, (2) the activities shown in Table 6.1 shall be carried out when assessing the conformity of an interoperability constituent or a group of interoperability constituents as defined in Chapter 5 of this TSI. All verifications shall be carried out by reference to the applicable table in Chapter 5 and the basic parameters indicated there.
| Aspect | What to assess | Supporting evidence |
|---|---|---|
| Functions, interfaces and performances | Check that all mandatory functions, interfaces and performances as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI | Design documentation and running of test cases and test sequences, as described in the basic parameters referenced in the relevant table of Chapter 5 |
| Check which optional functions and interfaces as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI | Design documentation and running of test cases and test sequences, as described in the basic parameters referenced in the relevant table of Chapter 5 | |
| Check which additional functions and interfaces (not specified in this TSI) are implemented and that they do not lead to conflicts with implemented functions specified in this TSI | Impact analysis | |
| Construction of equipment | Check compliance with mandatory conditions, where specified in the basic parameters referenced in the relevant table of Chapter 5 | Documentation on material used and, where necessary, tests to ensure that the requirements of the basic parameters referenced in the relevant table of Chapter 5 are satisfied |
| In addition, check that the interoperability constituent functions correctly in the environmental conditions for which it is designed | Tests according to the applicant’s specifications | |
| Reliability, Availability, Maintainability, Safety (RAMS) |
|
|
| Check that the quantitative reliability target (related to random failures) indicated by the applicant is met | Calculations | |
| Elimination of systematic failures | ||
| Check compliance with maintenance requirements — point 4.5.1 | Document check |
(1) a representative specimen of the interoperability constituent has been submitted to a full set of test sequences including all test cases necessary to check the functions referenced in point 4.2.2 (on-board ETCS functionality). The applicant is responsible to define the test cases and their organisation in sequences, if this is not included in specifications referenced in this TSI; (2) these tests were carried out in a laboratory accredited in accordance with Regulation (EC) No 765/2008 of the European Parliament and of the Council Regulation (EC) No 765/2008 of the European Parliament and of the Council of 9 July 2008 setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93 (OJ L 218, 13.8.2008, p. 30 ).
(1) which optional and additional functions are implemented; (2) the applicable environmental conditions.
(1) the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or (2) the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or (3) the full quality management system with design examination procedure (Module SH1).
(1) the unit verification procedure (Module SG); or (2) the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or (3) the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or (4) the full quality management system with design examination procedure (Module SH1).
(1) verification shall demonstrate that the Control-Command and Signalling On-board Subsystem complies with basic parameters when it is integrated into the vehicle; (2) the functionality and performances of interoperability constituents already covered by their EC Declaration of conformity do not require additional verifications,
| Aspect | What to assess | Supporting evidence |
|---|---|---|
| Use of interoperability constituents | Existence and content of documents | |
| Check restrictions on the use of Interoperability Constituents against the characteristics of the subsystem and of the environment | Analysis by document check | |
| For interoperability constituents that have been certified against older versions of the CCS TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force. | Impact analysis by document checks | |
| Integration of interoperability constituents in the subsystem | Check the correct installation and functioning of the internal interfaces of the subsystem — Basic parameters 4.2.6 | Checks according to specifications |
| Check that additional functions (not specified in this TSI) do not impact the mandatory ones | Impact analysis | |
| Check that the values of ETCS IDs are within the allowed range and, if required by this TSI, have unique values — Basic parameter 4.2.9 | Check of design specifications | |
| Integration with rolling stock | Check the correct installation of equipment — Basic Parameters 4.2.2, 4.2.4, 4.2.14 and conditions for installation of equipment, as specified by the manufacturer | Results of checks (according to specifications referenced in the Basic Parameters and the manufacturer’s installation rules) |
| Check that the Control-Command and Signalling On-board Subsystem is compatible with the rolling stock environment — Basic parameter 4.2.16 | Document check (certificates of interoperability constituents and possible integration methods checked against characteristics of rolling stock) | |
| Check that parameters (e.g. braking parameters) are correctly configured and that they are within the allowed range | Document check (values of parameters checked against characteristics of rolling stock) | |
| Integration with Class B | Check that the external STM is connected to on-board ETCS with TSI-compliant interfaces | Nothing to test: there is a standard interface already tested at interoperability constituent level. Its functioning has already been tested when checking the integration of interoperability constituents in the subsystem |
| Check that Class B functions implemented in the on-board ETCS — Basic parameter 4.2.6.1 — create no additional requirements for the Control-Command and Signalling Trackside Subsystem due to transitions | Nothing to test: everything has already been tested at interoperability constituent level | |
| Check that separate Class B equipment which is not connected to the on-board ETCS — Basic Parameter 4.2.6.1 — creates no additional requirements for Control-Command and Signalling Trackside Subsystem due to transitions | Nothing to test: no interface | |
| Check that separate Class B equipment connected on-board ETCS using (partly) non-TSI-compliant interfaces — basic parameter 4.2.6.1 — creates no additional requirements for the Control-Command and Signalling Trackside Subsystem due to transitions. Also check that ETCS functions are not affected | Impact analysis | |
| Integration with Control-Command and Signalling Trackside Subsystems | Check that Eurobalise telegrams can be read (scope of this test is limited to checking that the antenna has been appropriately installed. The tests already carried out at Interoperability Constituent level should not be repeated) — Basic Parameter 4.2.5 | Test using a certified Eurobalise: the ability to read correctly the telegram is the supporting evidence. |
| Check that Euroloop telegrams (if applicable) can be read — Basic Parameter 4.2.5 | Test using a certified Euroloop: the ability to read correctly the telegram is the supporting evidence. | |
| Check that the equipment can handle a GSM-R call for voice and data (if applicable) — Basic Parameter 4.2.5 | Test with a certified GSM-R network. The ability to set up, maintain and disconnect a connection is the supporting evidence. | |
| Reliability, Availability, Maintainability, Safety (RAMS) | Check that the equipment complies with safety requirements — Basic Parameter 4.2.1 | Application of procedures specified in the Common Safety Method |
| Check that the quantitative reliability target is met — Basic Parameter 4.2.1 | Calculations | |
| Check the compliance with requirements about maintenance — point 4.5.2 | Documents check | |
|
(1) line characteristics such as gradients, distances, positions of route elements and Eurobalises/Euroloops, locations to be protected, etc.; (2) the signalling data and rules to be handled by the ETCS system.
(1) Table 6.3 shows the checks that shall be carried out to verify a Control-Command and Signalling Trackside Subsystem and the basic parameters that shall be respected; (2) functionality and performance that have already been checked at the level of the interoperability constituents do not require additional verification.
| Aspect | What to assess | Supporting evidence |
|---|---|---|
| Use of interoperability constituents | Check that all interoperability constituents to be integrated into the subsystem are covered by an EC declaration of conformity and the corresponding certificate. | Existence and content of documents |
| Check restrictions on the use of interoperability constituents against the characteristics of the subsystem and of the environment | Impact analysis by documents check | |
| For interoperability constituents that have been certified against older versions of the Control-Command and Signalling TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force | Impact analysis by comparison of specifications referenced in the TSI and certificates of the interoperability constituents | |
| Use of train detection systems | Check that the selected types comply with Control-Command and Signalling TSI requirements — Basic parameters 4.2.10, 4.2.11 | Document check |
| Integration of interoperability constituents in the subsystem | Check that the internal interfaces of the subsystem have been installed properly and function properly — Basic parameters 4.2.5, 4.2.7 | Checks according to specifications |
| Check that additional functions (not specified in this TSI) do not impact the mandatory ones | Impact analysis | |
| Check that the values of ETCS IDs are within the allowed range and, if required by this TSI, have unique values – Basic Parameter 4.2.9 | Check of design specifications | |
| Integration with infrastructure | Check that the equipment has been properly installed — Basic parameters 4.2.3, 4.2.4 and conditions for installation specified by the manufacturer | Results of checks (according to specifications referenced in the basic parameters and manufacturer’s installation rules) |
| Check that the Control-Command and Signalling Trackside subsystem equipment is compatible with the trackside environment — Basic parameter 4.2.16 | Document check (certificates of interoperability constituents and possible methods of integration checked against trackside characteristics) | |
| Integration with trackside signalling | Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI — Basic parameter 4.2.3 | Document check (applicant’s design specification and certificates of interoperability constituents) |
| Check the correct configuration of parameters (Eurobalise telegrams, RBC messages, marker boards positions, etc.) | Document check (values of parameters checked against characteristics of trackside and of signalling) | |
| Check that the interfaces are correctly installed and function properly. | Design verification and tests according to information supplied by the applicant | |
| Check that the Control-Command and Signalling Trackside subsystem operates correctly according to information at the interfaces with trackside signalling (e.g. appropriate generation of Eurobalise telegrams by a LEU or of message by RBC) | Design verification and tests according to the information supplied by the applicant | |
| Integration with Control-Command and Signalling On-board Subsystems and with rolling stock | Check the GSM-R coverage — Basic Parameter 4.2.4 | On site measurements |
| the compliance of the train detection systems with the requirements of this TSI — Basic Parameter 4.2.10 | On site measurements | |
| Check that the train detection systems comply with the requirements of this TSI — Basic parameters 4.2.10 and 4.2.11 | Check evidence from existing installations (for systems already in use); perform tests according to standards for new types | |
| Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI — basic parameters 4.2.3, 4.2.4 and 4.2.5 | Reports of the operational test scenarios specified in point 6.1.2 with different certified Control-Command and Signalling On-board Subsystems. The report shall indicate which operational scenarios have been tested, which on-board equipment has been used and whether tests have been performed in laboratories, test lines or real implementation. | |
| Reliability, Availability, Maintainability, Safety (RAMS) | Check compliance with safety requirements — Basic Parameter 4.2.1 | Application of procedures specified in the Common Safety Method |
| Check that quantitative reliability targets are respected — Basic Parameter 4.2.1 | Calculations | |
| Check the compliance with requirements about maintenance – point 4.5.2 | Document check | |
| Integration with Control-Command and Signalling On-board Subsystems and rolling stock: tests under operational conditions |
|
(1) the TSI requirements for the part in question have been fulfilled; and (2) the TSI requirements already assessed for other parts of the same subsystem are still fulfilled.
(1) the on-board ETCS interface to STM if the interoperability constituent is intended for installation on vehicles in which no external STM is needed; (2) the RBC interface to other RBCs, if the RBC is intended for use in an application for which no neighbouring RBCs are planned.
(1) it indicates which functions, interfaces or performance are not implemented; (2) it provides enough information to make it possible to identify the conditions under which the interoperability constituent can be used; (3) it provides enough information to make it possible to identify the conditions of and restriction on the use that will apply to the interoperability of a subsystem incorporating it.
(1) if the deviation is due to incorrect application of this TSI or to errors in design or installation of equipment, the applicant for the relevant certificates shall take the necessary corrective actions and the certificates affected (for interoperability constituents and/or subsystems) shall be updated; (2) if the deviation is due to errors in this TSI or in specifications referenced therein, the procedure set out in Article 7 of the Directive 2008/57/EC shall be initiated.
(1) using an STM operating via the standard interface ("external STM"); or (2) integrated within the ETCS equipment or connected via a non- standard interface; or (3) independently from the ETCS equipment, for example via a system that enables switching between equipment. The railway undertaking must then ensure that the transitions between Class A and Class B train protection are carried out in conformity with the requirements of this TSI and with the national rules for the Class B system.
(1) An ETCS Level 3 Trackside application requires train integrity supervision on-board; (2) An ETCS Level 1 Trackside application with infill requires corresponding in-fill functionality on-board if the release speed is set to zero for safety reasons (e.g. protection of danger points). (3) When ETCS needs data transmission by radio, the data radio communication part as specified in this TSI is required.
(1) installing for the first time the radio communication part of a Control-Command and Signalling Trackside Subsystem; (2) upgrading the radio communication part of a Control-Command and Signalling Trackside Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not include the modifications deemed necessary to mitigate safety-related defects in the legacy installation; (3) Implementation of ETCS level 2, level 3 or level 1 with radio in-fill needs data radio communication.
(1) installing for the first time the voice radio communication part of a Control-Command and Signalling On-board Subsystem; (2) upgrading the voice radio communication part of a Control-Command and Signalling On-board Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation; (3) Implementation of ETCS level 2, level 3 or level 1 with radio in-fill need data radio communication.
(1) New vehicles authorised to be placed in service for the first time shall be equipped with ETCS in accordance with Annex A of this TSI. (2) The requirement to be equipped with ETCS does not apply to: (1) new mobile railway infrastructure construction and maintenance equipment; (2) new shunting locomotives; (3) other new vehicles not intended for operating on high-speed lines: (a) if they are intended exclusively for national service operated outside the corridors defined in point 7.3.4 of Annex III of Decision 2012/88/EU and outside the lines ensuring the connections to the main European ports, marshalling yards, freight terminals and freight transport areas defined in point 7.3.5 of the Annex of Decision 2012/88/EU; or (b) if they are intended for off-TEN cross-border service, i.e. service until the first station in the neighbouring country or to the first station where there are connections further in the neighbouring country.
(3) From 1 January 2019 , the set of specifications # 1 listed in Table 2.1 of Annex A of this TSI is not applicable any more for new vehicles to be placed in service for the first time.
(1) Member States may introduce additional requirements at national level, in particular with a view to: (1) allowing only ETCS-equipped vehicles to access ETCS-equipped lines, so that existing national systems can be decommissioned; (2) requesting that new and upgraded or renewed mobile railway infrastructure construction and maintenance equipment, shunting locomotives and/or other vehicles, even if intended exclusively for national service, be equipped with ETCS.
(2) Member States may decide to exclude from the obligation set out in the first paragraph of point 7.4.2.1 all new vehicles intended exclusively for national service except when the area of use of those vehicles includes more than 150 km of a section currently equipped or to be equipped with ETCS within 5 years after the authorisation for placing in service of those vehicles. Member States shall publish their decision for implementing this provision, notify such decision to the Commission and include it in the National Implementation Plan referred to in point 7.4.4.
(1) General and context description, including facts and figures on existing train protection systems, such as capacity, safety, reliability performance, remaining economic lifetime of the installed equipment and cost benefit analysis of ETCS implementation. (2) Definition of the technical migration strategy (overlay on-board or overlay at trackside) and the financial migration strategy (both at infrastructure and rolling-stock side). (3) A description of the measures taken to ensure open market conditions for its legacy Class B train protection systems as set out in paragraph 7.2.3. (4) Planning which includes: (i) the dates of ETCS deployment on the different lines of the network (when services are allowed to operate with ETCS); (ii) the indicative dates of decommissioning of Class B systems on the different lines of the network (when services cannot operate anymore with legacy systems). If decommissioning of Class B systems is not foreseen within a period of 15 years, these indicative dates are not required; (iii) the dates when existing cross-border vehicles shall fully benefit from operation with "ETCS only equipped on-board" on the high-speed network, corridors or other parts of the network. For high-speed services, this date depends on ETCS deployment on the high-speed network and on other parts of the network (e.g. stations being used by these high-speed services); For freight services, this date depends on the ETCS deployment on the corridors and on other parts of the network (e.g. last miles).
(1) upgrading the train detection system; (2) renewing the train detection system, provided that respecting the requirements of this TSI does not imply unwanted modifications or upgrades of other trackside or on-board systems; (3) renewing the train detection system, where this is required by the upgrade or renewal of trackside systems that use information from the train detection system; (4) removing Class B train protection systems where the train detection and train protection systems are integrated.
| Specific case | Category | Notes |
|---|---|---|
| T3 | ||
| T3 |
| Specific case | Category | Notes |
|---|---|---|
| T3 | ||
| T3 | Applicable in Northern Ireland | |
| T3 | Applicable in Northern Ireland | |
| T3 | |
| T3 | ||
| T3 |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This Specific Case is linked with the use of TVM | |
| T3 | This specific case may be revised when the open point related to the frequency management for track circuits is closed |
| T3 | This Specific Case is linked with the use of TVM |
| T3 |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This specific case may be revised when the open point related to the frequency management for track circuits is closed |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This specific case is needed as long as ČME locomotives operate on | |
| T3 | This specific case is needed as long as ČME locomotives operate on |
| Specific case | Category | Notes |
|---|---|---|
| P | No impact on interoperability |
| Specific case | Category | Notes |
|---|---|---|
| T3 |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This specific case is needed as long as track circuits type WSSB are used. |
| T3 | This specific case is needed as long as EBUET 80 type of level crossing protection is used. |
Loading ...