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)
Modified by
- Commission Implementing Regulation (EU) 2019/776of 16 May 2019amending Commission Regulations (EU) No 321/2013, (EU) No 1299/2014, (EU) No 1301/2014, (EU) No 1302/2014, (EU) No 1303/2014 and (EU) 2016/919 and Commission Implementing Decision 2011/665/EU as regards the alignment with Directive (EU) 2016/797 of the European Parliament and of the Council and the implementation of specific objectives set out in Commission Delegated Decision (EU) 2017/1474(Text with EEA relevance), 32019R0776, May 27, 2019
- Commission Implementing Regulation (EU) 2020/387of 9 March 2020amending Regulations (EU) No 321/2013, (EU) No 1302/2014 and (EU) 2016/919 as regards the extension of the area of use and transition phases(Text with EEA relevance), 32020R0387, March 10, 2020
- Commission Implementing Regulation (EU) 2020/420of 16 March 2020correcting the German language version of Regulation (EU) 2016/919 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), 32020R0420, March 20, 2020
- Commission Implementing Regulation (EU) 2023/1695of 10 August 2023on the technical specification for interoperability relating to the control-command and signalling subsystems of the rail system in the European Union and repealing Regulation (EU) 2016/919(Text with EEA relevance), 32023R1695, September 8, 2023
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 subsystem is subject to renewal or upgrading in accordance with Section 7 of the Annex to this Regulation; or (b) the area of use is extended in accordance with Article 54(3) of Directive (EU) 2016/797, in which case the provisions of Section 7.4.2.4 of the Annex to this Regulation shall apply.
(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.
(a) trackside projects which are at an advanced stage of development at the date of entry into force of this Regulation; and (b) on-board projects developed in accordance with ERTMS specifications #2 or #3 listed in Table A.2 of Annex A which are at an advanced stage of development at the date of entry into force of this Regulation.
(1) locomotives and passenger rolling stock, including thermal or electric traction units, self-propelling thermal or electric passenger trains, and passenger coach, if equipped with a driving cab. (2) special vehicles, such as on-track machines, if equipped with a driving cab and intended to be used in transport mode on its own wheels.
(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); (8) indicates the provisions applicable to the existing subsystems, in particular in the event of upgrading and renewal and, in such cases, the modification work which requires an application for a new authorisation for the vehicle or trackside subsystem — Chapter 7 (Implementing the Control-Command and Signalling Subsystems TSI); (9) indicates the parameters of the subsystems to be checked by the railway undertaking and the procedures to be applied to check those parameters after the delivery of the vehicle authorisation for placing on the market and before the first use of the vehicle to ensure compatibility between vehicles and the routes on which they are to be operated — Chapter 4 (Characterisation of the Subsystems).
(a) Trackside control-command and signalling as: "all the trackside equipment required to ensure safety and to command and control movements of trains authorised to travel on the network." (b) On-board control-command and signalling as "all the on-board equipment required to ensure safety and to command and control movements of trains authorised to travel on the network".
(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.
(1) Safety; (2) Reliability and Availability; (3) Health; (4) Environmental Protection; (5) Technical compatibility; (6) Accessibility.
(a) the changes made by railway undertakings and infrastructure managers shall be managed in compliance with the processes and procedures of their safety management system; (b) the changes made by other actors (e.g. manufacturers or other suppliers) shall be managed according to the risk management process set out in Annex I to the Commission Implementing Regulation (EU) No 402/2013 Commission Implementing Regulation (EU) No 402/2013 of 30 April 2013 on the common safety method for risk evaluation and assessment and repealing Regulation (EC) No 352/2009 (OJ L 121, 3.5.2013, p. 8 ).Directive (EU) 2016/798 of the European Parliament and of the Council of 11 May 2016 on railway safety (OJ L 138, 26.5.2016, p. 102 ).
(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 (point 4.2.16). (17) ETCS and Radio System Compatibility (point 4.2.17).
(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 vehicles with 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, 4.2.17 |
| 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, 4.2.17 | |
| 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, 4.2.17 | |
| 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, 4.2.17 |
| Voice radio communication | 4.2.1.2, 4.2.4, 4.2.5.1, 4.2.7, 4.2.16, 4.2.17 | |
| Data radio communication | 4.2.1.2, 4.2.4, 4.2.5.1, 4.2.7, 4.2.16, 4.2.17 | |
| 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 in-fill 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). This radio data transmission is optional unless operating on an ETCS level 2 or level 3 lines.
(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) — Supplying the train integrity to the on-board subsystem, is optional unless it is required by trackside. (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.3 d, 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 Operation and Traffic Management TSI | ||||
|---|---|---|---|---|
| Reference CCS TSI | Reference Operation and Traffic Management TSI | |||
| Parameter | Point | Parameter | Point | |
| Operating rules (normal and degraded conditions) | 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 | |
| Key Management | 4.2.8 | Ensuring that the train is in running order | 4.2.2.7 | |
| Route compatibility checks before the use of authorised vehicles | 4.9 | Parameters for the vehicle and train compatibility over the route intended for operation | Appendix D1 | |
| Interface with Rolling Stock TSIs | |||||
|---|---|---|---|---|---|
| Reference CCS TSI | Reference Rolling Stock TSIs | ||||
| Parameter | Point | Parameter | Point | ||
| 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 | HS RS TSI | wheelset location | 4.2.7.9.2 |
| axle load | 4.2.3.2 | ||||
| sanding | 4.2.3.10 | ||||
| electrical resistance between wheels | 4.2.3.3.1 | ||||
| CR RS TSI | 4.2.3.3.1.1 | ||||
| LOC & PAS TSI | 4.2.3.3.1.1 | ||||
| Wagon TSI | 4.2.3.2 | ||||
| Rolling stock characteristics to be compatible with train detection systems based on axle counters | HS RS TSI | wheelset geometry | 4.2.7.9.2 | ||
| wheels | 4.2.7.9.3 | ||||
| CR RS TSI | 4.2.3.3.1.2 | ||||
| LOC & PAS TSI | 4.2.3.3.1.2 | ||||
| Wagon TSI | 4.2.3.3 | ||||
| Rolling stock characteristics to be compatible with loop equipment | HS RS TSI | None | |||
| CR RS TSI | 4.2.3.3.1.3 | ||||
| LOC & PAS TSI | 4.2.3.3.1.3 | ||||
| Wagon TSI | 4.2.3.3 | ||||
| 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 | HS RS TSI | 4.2.6.6.1 | |
| CR RS TSI | 4.2.3.3.1.1 | ||||
| LOC & PAS TSI | 4.2.3.3.1.1 | ||||
| Wagon TSI | 4.2.3.3 | ||||
| Rolling stock characteristics to be compatible with train detection systems based on axle counters | HS RS TSI | 4.2.6.6.1 | |||
| CR RS TSI | 4.2.3.3.1.2 | ||||
| LOC & PAS TSI | 4.2.3.3.1.2 | ||||
| Wagon TSI | 4.2.3.3 | ||||
| Train braking performance and characteristics | 4.2.2 | Emergency braking performance | HS RS TSI | Emergency braking | 4.2.4.1 |
| Service braking | 4.2.4.4 | ||||
| CR RS TSI | Emergency braking | 4.2.4.5.2 | |||
| Service braking | 4.2.4.5.3 | ||||
| LOC & PAS TSI | Emergency braking | 4.2.4.5.2 | |||
| Service braking | 4.2.4.5.3 | ||||
| Wagon TSI | 4.2.4.1.2 | ||||
| Position of Control-Command and Signalling on-board antennas | 4.2.2 | Kinematic gauge | HS RS TSI | 4.2.3.1 | |
| CR RS TSI | 4.2.3.1 | ||||
| LOC & PAS TSI | 4.2.3.1 | ||||
| Wagon TSI | none | ||||
| Isolation of on-board ETCS functionality | 4.2.2 | Operating rules | HS RS TSI | 4.2.7.9.1 | |
| CR RS TSI | 4.2.12.3 | ||||
| LOC & PAS TSI | 4.2.12.3 | ||||
| Wagon TSI | none | ||||
| Data interfaces | 4.2.2 | Monitoring and diagnostic concepts | HS RS TSI | 4.2.7.10 | |
| CR RS TSI | 4.2.1.1 | ||||
| LOC & PAS TSI | 4.2.1.1 | ||||
| Wagon TSI | None | ||||
| Visibility of trackside Control-Command and Signalling objects | 4.2.15 | HS RS TSI | 4.2.7.4.1.1 | ||
| CR RS TSI | 4.2.7.1.1 | ||||
| LOC & PAS TSI | 4.2.7.1.1 | ||||
| Wagon TSI | None | ||||
| Driver's external field of view | HS RS TSI | line of sight | 4.2.2.6 b | ||
| windscreen | 4.2.2.7 | ||||
| CR RS TSI | line of sight | 4.2.9.1.3.1 | |||
| windscreen | 4.2.9.2 | ||||
| LOC & PAS TSI | line of sight | 4.2.9.1.3.1 | |||
| windscreen | 4.2.9.2 | ||||
| Wagon TSI | None | ||||
| Interface to data recording for regulatory purposes | 4.2.14 | Recording device | HS RS TSI | 4.2.7.10 | |
| CR RS TSI | 4.2.9.6 | ||||
| LOC & PAS TSI | 4.2.9.6 | ||||
| Wagon TSI | none | ||||
| Commands to rolling stock equipment | Phase separation | HS RS TSI | 4.2.8.3.6.7 | ||
| CR RS TSI | 4.2.8.2.9.8 | ||||
| LOC & PAS TSI | 4.2.8.2.9.8 | ||||
| Wagon TSI | none | ||||
| Emergency braking command | 4.2.2 | Emergency braking command | HS RS TSI | none | |
| CR RS TSI | 4.2.4.4.1 | ||||
| LOC & PAS TSI | 4.2.4.4.1 | ||||
| Wagon TSI | none | ||||
| Construction of equipment | 4.2.16 | Material requirements | HS RS TSI | 4.2.7.2.2 | |
| CR RS TSI | 4.2.10.2.1 | ||||
| LOC&PAS TSI | 4.2.10.2.1 | ||||
| Wagon TSI | none | ||||
| 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.). For equipment error corrections see point 6.5; (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 |
|---|---|---|---|
| No | 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 | ||
| |||
| Interfaces | |||
| |||
| Construction of equipment | 4.2.16 | ||
| 2 | Odometry equipment | Reliability, Availability, Maintainability, Safety (RAMS) | |
| On-board ETCS functionality: only Odometry | 4.2.2 | ||
| Interfaces | |||
| 4.2.6.3 | |||
| Construction of equipment | 4.2.16 | ||
| 3 | Interface of External STM | Interfaces | |
| 4.2.6.1 | |||
| 4 | Reliability, Availability, Maintainability, (RAM) | ||
| Basic communication functions | 4.2.4.1 | ||
| Voice and operational communication applications | 4.2.4.2 | ||
| Interfaces | |||
| |||
| Construction of equipment | 4.2.16 | ||
| 5 | Reliability, Availability, Maintainability (RAM) | ||
| Basic communication functions | 4.2.4.1 | ||
| ETCS data communication applications | 4.2.4.3 | ||
| Interfaces | |||
| |||
| Construction of equipment | 4.2.16 | ||
| 6 | Basic communication functions | 4.2.4.1 | |
| Construction of equipment | 4.2.16 |
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| No | 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 | ||
| |||
| Interfaces | |||
| |||
| Construction of equipment | 4.2.16 |
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| No | 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 | ||
| Interfaces | |||
| |||
| 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 | ||
| Interfaces | |||
| |||
| 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 | ||
| Interfaces | |||
| 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 | ||
| Interfaces | |||
| 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 | ||
| Interfaces | |||
| 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 | ||
| Interfaces | |||
| 4.2.7.5 | |||
| Construction of equipment | 4.2.16 | ||
| 7 | Axle Counter | Trackside train detection systems (only parameters relevant for axle counters) | 4.2.10 |
| Electromagnetic compatibility (only parameters relevant for axle counters) | 4.2.11 | ||
| 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) the use of Class B systems; (2) open points in the TSI; (3) non-application of TSIs (derogations) under Article 7 of Directive (EU) 2016/797; (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 and limits of use 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 The template to be used to provide this information will be defined in the Application Guide. (3) The authorising entity may refuse for duly justified reasons the authorisation for placing in service or on the market, or place conditions and limits of use 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) 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.
| No | Aspect | What to assess | Supporting evidence |
|---|---|---|---|
| 1 | 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 | ||
| 2 | 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 | ||
| 3 | Reliability, Availability, Maintainability, Safety (RAMS) |
|
|
| 4 | Check that the quantitative reliability target (related to random failures) indicated by the applicant is met | Calculations | |
| 5 | Elimination of systematic failures | ||
| 6 | 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 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,
| No | Aspect | What to assess | Supporting evidence |
|---|---|---|---|
| 1 | Use of interoperability constituents | Existence and content of documents | |
| Check conditions and limits of use 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 a version of the CCS TSI, which is different from the version applied for the "EC" Verification of the subsystem and/or against a set of specifications which is different from the set of specifications applied for the "EC" Verification of the subsystem, check that the certificate still ensures subsystem compliance with the requirements of the TSI currently in force. | Impact analysis by document checks | ||
| 2 | Integration of interoperability constituents in the subsystem | Check the correct installation and functioning of the internal interfaces of the subsystem — Basic parameter 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 | ||
| 3 | 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) | ||
| 4 | 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 | ||
| 5 | 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 shall 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. | ||
| 6 | 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 for Risk Evaluation and Assessment. |
| 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 | ||
| 7 |
| Reports of test runs. |
(a) the availability of the result of the technical compatibility checks for the selected area of use of the vehicle. (b) That the technical compatibility checks have been performed in accordance with the technical document published by the Agency, referred in points 6.1.2.4 and 6.1.2.5. (c) Based on the report of the checks, that the technical compatibility checks results indicate all the incompatibilities and errors encountered during the technical compatibility checks.
(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.
| No | Aspect | What to assess | Supporting evidence |
|---|---|---|---|
| 1 | 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 conditions and limits of use 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 a version of the Control-Command and Signalling TSI, which is different from the version applied for the "EC" Verification of the subsystem and/or against a set of specifications which is different from the set of specifications applied for the "EC" Verification of the subsystem, 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 | ||
| 2 | Integration of interoperability constituents in the subsystem | Checks according to specifications | |
| Check that additional functions (not specified in this TSI) do not impact the mandatory ones | Impact analysis | ||
| Check of design specifications | |||
| Document check | |||
| 3 | Visibility of trackside Control-Command objects | Check that requirements for marker boards specified in this TSI are fulfilled (characteristics, compatibility with the infrastructure requirements (gauge, …), compatibility with the driver's field of view) – Basic parameter 4.2.15 | Design documentation, results of tests or test runs with TSI compliant rolling stock |
| 4 | 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) | ||
| 5 | 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 | ||
| 6 | 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 |
| 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 at least two certified Control-Command and Signalling On-board Subsystems from different suppliers. The report shall indicate which operational test scenarios have been tested, which on-board equipment has been used and whether tests have been performed in laboratories, test lines or real implementation. | ||
| 7 | |||
| 8 | Check compliance with safety requirements — Basic Parameter 4.2.1.1 | Application of procedures specified in the Common Safety Method for Risk Evaluation and Assessment | |
| Check that quantitative reliability targets are respected — Basic Parameter 4.2.1.2 | Calculations | ||
| Check the compliance with requirements about maintenance – point 4.5.2 | Document check | ||
| 9 | Integration with Control-Command and Signalling On-board Subsystems and rolling stock: tests under conditions representing the intended operation. |
| Reports of test runs. |
| 10 | ETCS and radio System Compatibility | The necessary ESC and RSC check definition is made available to the Agency – Basic Parameter 4.2.17. | Technical compatibility checks for ESC and RSC published and maintained by the Agency. |
(1) the TSI requirements for the part in question have been fulfilled; and (2) the fulfilment of the TSI requirements already assessed for other parts of the same subsystem has not been modified.
(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 and/or the corresponding technical files (for interoperability constituents and/or subsystems), together with the corresponding EC Declarations, 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 6 of the Directive (EU) 2016/797 shall be initiated.
| Set of specification of Annex A | Not Applicable | Not Applicable | Use another Annex A set of specifications | |
| On-board ETCS implementation | Fulfilling all the conditions in point 7.2.1a.2 (change of realisation) | Not Applicable | Not fulfilling all the conditions in point 7.2.1a.2 (Functional change) | |
| Managing information about the completeness of the train | Not applicable | Adding or removing train integrity supervision | Not applicable | |
| ETCS System Compatibility | Not applicable | Adding or removing ESC statements, after checking by a NoBo | Not applicable | |
| GSM-R Baseline | Use another Baseline fulfilling all the conditions in point 7.2.1a.3. | Not Applicable | Use another Baseline not fulfilling all the conditions in point 7.2.1a.3. | |
| Voice and operational communication implementation | Fulfilling all the conditions in point 7.2.1a.3 (change of realisation) | Not Applicable | Not fulfilling all the conditions in point 7.2.1a.3 (Functional change) | |
| SIM Card support of Group ID 555 | Not applicable | Change the SIM Card support of Group ID 555 | Not applicable | |
| Radio Voice System Compatibility | Not applicable | Adding or removing RSC statements, after checking by a NoBo | Not applicable | |
| GSM-R Baseline | Use another Baseline fulfilling all the conditions in point 7.2.1a.3. | Not Applicable | Use another Baseline not fulfilling all the conditions in point 7.2.1a.3. | |
| Data communication for ETCS implementation | Fulfilling all the conditions in point 7.2.1a.3 (change of realisation) | Not Applicable | Not fulfilling all the conditions in point 7.2.1a.3 (Functional change) | |
| Radio Data System Compatibility | Not applicable | Adding or removing RSC statements, after checking by a NoBo | Not applicable | |
| SIM Card GSM-R Home Network | Not applicable | Replacement of a TSI compliant GSM-R SIM Card by another TSI compliant GSM-R SIM Card with a different GSM-R Home Network | Not applicable | |
| Class B train protection legacy system | The requirements for Class B system are the responsibility of the relevant Member State. | The requirements for Class B system are the responsibility of the relevant Member State. | ||
| Class B radio legacy system | The requirements for Class B system are the responsibility of the relevant Member State. | The requirements for Class B system are the responsibility of the relevant Member State. |
The original EC certificate for parts of the design that are unchanged or those that are changed but do not affect the conformity of the subsystem, as far as it is still valid. Amendments to the original EC certificate for modified parts of the design that affect the conformity of the subsystem with the applicable TSI version used for the EC verification.
1. The changes require new authorisation if they impact basic parameters as defined in table 7.2. Table 7.2 Trackside basic parameters modifications which requires a new authorisation Basic Parameter Modification which requires a new authorisation 4.2.3 Trackside ETCS functionality Not fulfilling all the conditions in point 7.2.1b.2 4.2.4 Mobile communication functions for railways GSM-R Not fulfilling all the conditions in point 7.2.1b.3 4.2.4.2 Voice and operational communication application 4.2.4 Mobile communication functions for railways GSM-R Not fulfilling all the conditions in point 7.2.1b.3 4.2.4.3 Data communication applications for ETCS 2. The changes are permitted to be dealt with by only re-assessing those modifications that affect the conformity of the subsystem with the applicable TSIs version used for the EC verification. The entity managing the change has to justify and document that applicable requirements remain consistent at subsystem level, and this has to be assessed by a Notified Body. 3. The entity managing the change shall inform the Notified Body of all changes that may affect the conformity of the subsystem with the requirements of the relevant TSI(s) or the conditions for validity of the certificate. This information shall be provided by the entity managing the change with corresponding references to the technical documentation relating to the existing EC certificate. 4. In order to establish the EC certificate, the Notified Body may to refer to: The original EC certificate for parts of the design that are unchanged or those that are changed but do not affect the conformity of the subsystem, as far as it is still valid. Additional EC certificate (amending the original certificate) for modified parts of the design that affect the conformity of the subsystem with the applicable TSI version used for the EC verification.
5. In any case, the entity managing the change shall ensure that the technical documentation which is relating to the EC certificate is updated accordingly. 6. The "system identifier" is as a numbering scheme to identify the system version of a CCS subsystem and distinguish between a functional and a realization identifier. The "functional identifier" is part of the system identifier and means a figure or a number of figures defined by the individual configuration management, which represents a reference of the basic design characteristics for CCS implemented in a CCS subsystem. The "Realization identifier" is part of the system identifier and means a figure or a number of figures defined by the individual configuration management of a supplier, which represents a specific configuration (e.g. HW and SW) of a CCS subsystem. The "system identifier", "functional identifier" and "realization identifier" shall be defined by each supplier. 7. "Configuration management" means a systematic organisational, technical and administrative process to ensure that the consistency of the documentation and the traceability of the changes are established and maintained so that: (a) requirements from relevant Union law and national rules are met; (b) changes are controlled and documented either in the technical files or in the file accompanying the issued authorisation; (c) information and data is kept current and accurate; (d) relevant parties are informed of changes, as required.
(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 that the on-board is able to confirm the train integrity; (2) An ETCS Level 1 Trackside application with infill requires that the on-board is equipped with the corresponding in-fill data transmission (Euroloop or radio) 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 on the market 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. installing for the first time the train protection part of a Control-Command and Signalling Trackside Subsystem (with or without a Class B system); or 2. upgrading the existing train protection part of a Control-Command and Signalling Trackside Subsystem, where this would change the functions, performance and/or interoperability-relevant interfaces (air gaps) of the existing legacy system. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation.
(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 Annex I of Implementing Regulation (EU) 2017/6 and outside the lines ensuring the connections to the main European ports, marshalling yards, freight terminals and freight transport areas defined in Article 2(1) of Implementing Regulation (EU) 2017/6; 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 utilising only lines outside of the TEN.
(a) up to December 31 2020 : In order to be placed on the marketOr placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable. (b) If set of specification #1 is used, a condition for use shall be included in their authorisation to put on the market Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable. 1 July 2023 .
(1) Vehicles shall comply with relevant special provisions applicable in the specific cases referred to in clause 7.6 of this Annex and with relevant national rules referred to in points (a), (c) and (d) of Article 13(2) of Directive (EU) 2016/797 notified in accordance with Article 14 of that Directive. In addition, in cases of partial fulfilment of the requirements in this TSI, provisions in point 6.1.1.3(3) shall apply. (2) Vehicles already equipped with ETCS or GSM-R do not need to be upgraded, except where required for technical compatibility. (3) Vehicles that are not already equipped with ETCS shall install ETCS and comply with sets of specifications #2 or #3 referred to in Tables A 2.2 and A 2.3 of Annex A. Except where required for technical compatibility, the requirement to be equipped with ETCS shall not apply to: (a) vehicles not specially designed for operation on high-speed lines As set out in Annex I of Directive (EU) 2016/797. 1 January 2015 ;(b) vehicles not specially designed for operation on high-speed lines, authorised as of 1 January 2015 , in either of the following situations:(i) if they are intended exclusively for operations in one Member State outside the corridors specified in Annex I to Implementing Regulation (EU) 2017/6 and outside the lines ensuring the connections to the main European ports, marshalling yards, freight terminals and freight transport areas as referred to in Annex II to Regulation (EU) No 1315/2013; (ii) if they are intended for off-TEN cross-border service, namely service until the first station in the neighbouring country or to the first station where there are connections further in the neighbouring country utilising only lines outside of the TEN;
(c) vehicles in Member States applying Article 7.4.3(2), where the area of the use following the Extension of Area of Use is exclusively within the same Member State, except when the area of use following the Extension of Area of Use includes more than 150 km of a section equipped with ETCS at the time of the Extension of Area of Use or to be equipped with ETCS within 5 years after the Extension of the Area of Use of those vehicles; (d) mobile railway infrastructure construction and maintenance equipment; (e) shunting locomotives.
(4) Vehicles that are not yet equipped with GSM-R voice radio shall install GSM-R voice cab radio and comply with the specifications referred to in Tables A 2.1, A 2.2 and A 2.3 of Annex A when the vehicle is intended for use on a network including at least one point equipped with GSM-R, except if superimposed to a legacy radio communication system compatible with the class B already installed in the vehicle. (5) Vehicles that are not yet equipped with GSM-R for ETCS data shall install GSM-R ETCS Data only Radio and comply with the specifications referred to in Tables A 2.1, A 2.2 and A 2.3 of Annex A when the vehicle is required to install ETCS in accordance with point 3 and it is intended to operate in a network in the extended area of use that is equipped with only ETCS Level 2 or 3. (6) Where an authorised vehicle benefited from non-application of TSIs or part of them pursuant to Article 9 of Directive 2008/57/EC, the applicant shall seek derogation(s) in the Member States of the extended area of use in accordance to Article 7 of Directive (EU) 2016/797.
(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 on the market 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: (1) facts and figures on existing train protection systems, such as capacity, safety, reliability performance; (2) remaining economic lifetime of the installed equipment and cost benefit analysis of ETCS and Class A Radio implementation; (3) national requirements relevant for Baseline 3 on-board units; (4) information on communication systems between on-board units and track side installations (e.g. radio circuit switching or packet switching, in-fill options for ETCS; Class B communication systems).
(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 and Class A Radio 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, including service facilities. 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 |
|---|---|---|
| P | This Specific Case is linked with the use of track circuits using electrical joints | |
| 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 | ||
| P | This specific case is linked to the use of track circuits with a higher sensitivity regarding the isolation layer between wheels and rails due to sanding on the French Network |
| 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 | |
| P | ||
| P | ||
| P |
| 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. |
| T3 | This specific case is needed because these track circuits may be modified by shifting the centre frequency from 100 Hz to 106,7 Hz. This would make obsolete a vehicle related National Technical Rule requiring a 100 Hz monitoring system. |
| Specific case | Category | Notes |
|---|---|---|
| P |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This specific case is needed as long as track circuits type EFCP are used. |
| Specific case | Category | Notes |
|---|---|---|
| T3 | This Specific Cases is needed in the context of the Class-B system ATBEG. |
| Reference in Chapter 4 | Index number (see Table A 2) |
|---|---|
| 4.1 a | Intentionally deleted |
| 4.1 b | Intentionally deleted |
| 4.1 c | 3 |
| 4.2.1 a | 27, 78 |
| 4.2.2 a | 14 |
| 4.2.2 b | 1, 4, 13, 15, 60 |
| 4.2.2 c | 31, 37b, c, d |
| 4.2.2 d | 18, 20 |
| 4.2.2 e | 6 |
| 4.2.2 f | 7, 81, 82 |
| 4.2.3 a | 14 |
| 4.2.3 b | 1, 4, 13, 15, 60 |
| 4.2.3 c | Intentionally deleted |
| 4.2.3 d | 18, 21 |
| 4.2.4 a | 64, 65 |
| 4.2.4 b | 66 |
| 4.2.4 c | 67 |
| 4.2.4 d | 68 |
| 4.2.4 e | 73, 74 |
| 4.2.4 f | 32, 33 |
| 4.2.4 g | 48 |
| 4.2.4 h | 69, 70 |
| 4.2.4 j | 71, 72 |
| 4.2.4 k | 75, 76 |
| 4.2.5 a | 64, 65 |
| 4.2.5 b | 10, 39, 40 |
| 4.2.5 c | 19, 20 |
| 4.2.5 d | 9, 43 |
| 4.2.5 e | 16, 50 |
| 4.2.6 a | 8, 25, 26, 36 c, 49, 52 |
| 4.2.6 b | 29, 45 |
| 4.2.6 c | 46 |
| 4.2.6 d | 34 |
| 4.2.6 e | 20 |
| 4.2.6 f | Intentionally deleted |
| 4.2.7 a | 12 |
| 4.2.7 b | 62, 63 |
| 4.2.7 c | 34 |
| 4.2.7 d | 9 |
| 4.2.7 e | 16 |
| 4.2.8 a | 11, 79, 83 |
| 4.2.9 a | 23 |
| 4.2.10 a | 77 (point 3.1) |
| 4.2.11 a | 77 (point 3.2) |
| 4.2.12 a | 6, 51 |
| 4.2.13 a | 32, 33, 51, 80 |
| 4.2.14 a | 5 |
| 4.2.15 a | 38 |
| Index No | ||||
|---|---|---|---|---|
| Reference | Name of Specification | Version | Notes | |
| 1 | ERA/ERTMS/003204 | ERTMS/ETCS Functional requirement specification | 5.0 | |
| 2 | Intentionally deleted | |||
| 3 | SUBSET-023 | Glossary of Terms and Abbreviations | 2.0.0 | |
| 4 | SUBSET-026 | System Requirements Specification | 2.3.0 | |
| 5 | SUBSET-027 | FFFIS Juridical recorder-downloading tool | 2.3.0 | Note 1 |
| 6 | SUBSET-033 | FIS for man-machine interface | 2.0.0 | |
| 7 | SUBSET-034 | FIS for the train interface | 2.0.0 | |
| 8 | SUBSET-035 | Specific Transmission Module FFFIS | 2.1.1 | |
| 9 | SUBSET-036 | FFFIS for Eurobalise | 2.4.1 | |
| 10 | SUBSET-037 | EuroRadio FIS | 2.3.0 | |
| 11 | SUBSET-038 | Offline key management FIS | 2.3.0 | |
| 12 | SUBSET-039 | FIS for the RBC/RBC handover | 2.3.0 | |
| 13 | SUBSET-040 | Dimensioning and Engineering rules | 2.3.0 | |
| 14 | SUBSET-041 | Performance Requirements for Interoperability | 2.1.0 | |
| 15 | SUBSET-108 | Interoperability related consolidation on TSI Annex A documents | 1.2.0 | |
| 16 | SUBSET-044 | FFFIS for Euroloop | 2.3.0 | |
| 17 | Intentionally deleted | |||
| 18 | SUBSET-046 | Radio infill FFFS | 2.0.0 | |
| 19 | SUBSET-047 | Trackside-Trainborne FIS for Radio infill | 2.0.0 | |
| 20 | SUBSET-048 | Trainborne FFFIS for Radio infill | 2.0.0 | |
| 21 | SUBSET-049 | Radio infill FIS with LEU/interlocking | 2.0.0 | |
| 22 | Intentionally deleted | |||
| 23 | SUBSET-054 | Responsibilities and rules for the assignment of values to ETCS variables | 2.1.0 | |
| 24 | Intentionally deleted | |||
| 25 | SUBSET-056 | STM FFFIS Safe time layer | 2.2.0 | |
| 26 | SUBSET-057 | STM FFFIS Safe link layer | 2.2.0 | |
| 27 | SUBSET-091 | Safety Requirements for the Technical Interoperability of ETCS in Levels 1 and 2 | 2.5.0 | |
| 28 | Intentionally deleted | |||
| 29 | SUBSET-102 | Test specification for interface "K" | 1.0.0 | |
| 30 | Intentionally deleted | |||
| 31 | SUBSET-094 | Functional requirements for an onboard reference test facility | 2.0.2 | |
| 32 | EIRENE FRS | GSM-R Functional requirements specification | 8.0.0 | Note 10 |
| 33 | EIRENE SRS | GSM-R System requirements specification | 16.0.0 | Note 10 |
| 34 | A11T6001 | (MORANE) Radio Transmission FFFIS for EuroRadio | 13.0.0 | |
| 35 | Intentionally deleted | |||
| 36 a | Intentionally deleted | |||
| 36 b | Intentionally deleted | |||
| 36 c | SUBSET-074-2 | FFFIS STM Test cases document | 1.0.0 | |
| 37 a | Intentionally deleted | |||
| 37 b | SUBSET-076-5-2 | Test cases related to features | 2.3.3 | |
| 37 c | SUBSET-076-6-3 | Test sequences | 2.3.3 | |
| 37 d | SUBSET-076-7 | Scope of the test specifications | 1.0.2 | |
| 37 e | Intentionally deleted | |||
| 38 | 06E068 | ETCS Marker-board definition | 2.0 | |
| 39 | SUBSET-092-1 | ERTMS EuroRadio Conformance Requirements | 2.3.0 | |
| 40 | SUBSET-092-2 | ERTMS EuroRadio test cases safety layer | 2.3.0 | |
| 41 | Intentionally deleted | |||
| 42 | Intentionally deleted | |||
| 43 | SUBSET 085 | Test specification for Eurobalise FFFIS | 2.2.2 | |
| 44 | Intentionally deleted | |||
| 45 | SUBSET-101 | Interface "K" Specification | 1.0.0 | |
| 46 | SUBSET-100 | Interface "G" Specification | 1.0.1 | |
| 47 | Intentionally deleted | |||
| 48 | Reserved | Test specification for mobile equipment GSM-R | Note 4 | |
| 49 | SUBSET-059 | Performance requirements for STM | 2.1.1 | |
| 50 | SUBSET-103 | Test specification for Euroloop | 1.0.0 | |
| 51 | Reserved | Ergonomic aspects of the DMI | ||
| 52 | SUBSET-058 | FFFIS STM Application layer | 2.1.1 | |
| 53 | Intentionally deleted | |||
| 54 | Intentionally deleted | |||
| 55 | Intentionally deleted | |||
| 56 | Intentionally deleted | |||
| 57 | Intentionally deleted | |||
| 58 | Intentionally deleted | |||
| 59 | Intentionally deleted | |||
| 60 | Intentionally deleted | |||
| 61 | Intentionally deleted | |||
| 62 | Reserved | RBC-RBC Test specification for safe communication interface | ||
| 63 | SUBSET-098 | RBC-RBC Safe Communication Interface | 1.0.0 | |
| 64 | EN 301 515 | Global System for Mobile Communication (GSM); Requirements for GSM operation on railways | 2.3.0 | Note 2 |
| 65 | TS 102 281 | Detailed requirements for GSM operation on railways | 3.0.0 | Note 3 |
| 66 | TS 103 169 | ASCI Options for Interoperability | 1.1.1 | |
| 67 | (MORANE) P 38 T 9001 | FFFIS for GSM-R SIM Cards | 5.0 | Note 10 |
| 68 | ETSI TS 102 610 | Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways | 1.3.0 | |
| 69 | (MORANE) F 10 T 6002 | FFFS for Confirmation of High Priority Calls | 5.0 | |
| 70 | (MORANE) F 12 T 6002 | FIS for Confirmation of High Priority Calls | 5.0 | |
| 71 | (MORANE) E 10 T 6001 | FFFS for Functional Addressing | 4.1 | |
| 72 | (MORANE) E 12 T 6001 | FIS for Functional Addressing | 5.1 | |
| 73 | (MORANE) F 10 T6001 | FFFS for Location Dependent Addressing | 4 | |
| 74 | (MORANE) F 12 T6001 | FIS for Location Dependent Addressing | 3 | |
| 75 | (MORANE) F 10 T 6003 | FFFS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 76 | (MORANE) F 12 T 6003 | FIS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 77 | ERA/ERTMS/033281 | Interfaces between CCS trackside and other subsystems | 4.0 | Note 7 |
| 78 | Reserved | Safety requirements for ETCS DMI functions | ||
| 79 | Not applicable | Not applicable | ||
| 80 | Not applicable | Not applicable | ||
| 81 | Not applicable | Not applicable | ||
| 82 | Not applicable | Not applicable | ||
| Index No | ||||
|---|---|---|---|---|
| Reference | Name of Specification | Version | Notes | |
| 1 | Intentionally deleted | |||
| 2 | Intentionally deleted | |||
| 3 | SUBSET-023 | Glossary of Terms and Abbreviations | 3.1.0 | |
| 4 | SUBSET-026 | System Requirements Specification | 3.4.0 | |
| 5 | SUBSET-027 | FIS Juridical Recording | 3.1.0 | |
| 6 | ERA_ERTMS_015560 | ETCS Driver Machine interface | 3.4.0 | |
| 7 | SUBSET-034 | Train Interface FIS | 3.1.0 | |
| 8 | SUBSET-035 | Specific Transmission Module FFFIS | 3.1.0 | |
| 9 | SUBSET-036 | FFFIS for Eurobalise | 3.0.0 | |
| 10 | SUBSET-037 | EuroRadio FIS | 3.1.0 | |
| 11 | SUBSET-038 | Offline key management FIS | 3.0.0 | |
| 12 | SUBSET-039 | FIS for the RBC/RBC handover | 3.1.0 | |
| 13 | SUBSET-040 | Dimensioning and Engineering rules | 3.3.0 | |
| 14 | SUBSET-041 | Performance Requirements for Interoperability | 3.1.0 | |
| 15 | Intentionally deleted | |||
| 16 | SUBSET-044 | FFFIS for Euroloop | 2.4.0 | |
| 17 | Intentionally deleted | |||
| 18 | Intentionally deleted | |||
| 19 | SUBSET-047 | Trackside-Trainborne FIS for Radio infill | 3.0.0 | |
| 20 | SUBSET-048 | Trainborne FFFIS for Radio infill | 3.0.0 | |
| 21 | Intentionally deleted | |||
| 22 | Intentionally deleted | |||
| 23 | SUBSET-054 | Responsibilities and rules for the assignment of values to ETCS variables | 3.0.0 | |
| 24 | Intentionally deleted | |||
| 25 | SUBSET-056 | STM FFFIS Safe time layer | 3.0.0 | |
| 26 | SUBSET-057 | STM FFFIS Safe link layer | 3.0.0 | |
| 27 | SUBSET-091 | Safety Requirements for the Technical Interoperability of ETCS in Levels 1 and 2 | 3.4.0 | |
| 28 | Intentionally deleted | |||
| 29 | SUBSET-102 | Test specification for interface "K" | 2.0.0 | |
| 30 | Intentionally deleted | |||
| 31 | SUBSET-094 | Functional requirements for an onboard reference test facility | 3.0.0 | |
| 32 | EIRENE FRS | GSM-R Functional requirements specification | 8.0.0 | Note 10 |
| 33 | EIRENE SRS | GSM-R System requirements specification | 16.0.0 | Note 10 |
| 34 | A11T6001 | (MORANE) Radio Transmission FFFIS for EuroRadio | 13.0.0 | |
| 35 | Intentionally deleted | |||
| 36 a | Intentionally deleted | |||
| 36 b | Intentionally deleted | |||
| 36 c | SUBSET-074-2 | FFFIS STM Test cases document | 3.0.0 | |
| 37 a | Intentionally deleted | |||
| 37 b | SUBSET-076-5-2 | Test cases related to features | 3.2.0 | |
| 37 c | SUBSET-076-6-3 | Test sequences | 3.1.0 | |
| 37 d | SUBSET-076-7 | Scope of the test specifications | 3.2.0 | |
| 37 e | Intentionally deleted | |||
| 38 | 06E068 | ETCS Marker-board definition | 2.0 | |
| 39 | SUBSET-092-1 | ERTMS EuroRadio Conformance Requirements | 3.0.0 | |
| 40 | SUBSET-092-2 | ERTMS EuroRadio test cases safety layer | 3.0.0 | |
| 41 | Intentionally deleted | |||
| 42 | Intentionally deleted | |||
| 43 | SUBSET 085 | Test specification for Eurobalise FFFIS | 3.0.0 | |
| 44 | Intentionally deleted | |||
| 45 | SUBSET-101 | Interface "K" Specification | 2.0.0 | |
| 46 | SUBSET-100 | Interface "G" Specification | 2.0.0 | |
| 47 | Intentionally deleted | |||
| 48 | Reserved | Test specification for mobile equipment GSM-R | Note 4 | |
| 49 | SUBSET-059 | Performance requirements for STM | 3.0.0 | |
| 50 | SUBSET-103 | Test specification for Euroloop | 1.1.0 | |
| 51 | Intentionally deleted | |||
| 52 | SUBSET-058 | FFFIS STM Application layer | 3.1.0 | |
| 53 | Intentionally deleted | |||
| 54 | Intentionally deleted | |||
| 55 | Intentionally deleted | |||
| 56 | Intentionally deleted | |||
| 57 | Intentionally deleted | |||
| 58 | Intentionally deleted | |||
| 59 | Intentionally deleted | |||
| 60 | SUBSET-104 | ETCS System Version Management | 3.2.0 | |
| 61 | Intentionally deleted | |||
| 62 | Intentionally deleted | |||
| 63 | SUBSET-098 | RBC-RBC Safe Communication Interface | 3.0.0 | |
| 64 | EN 301 515 | Global System for Mobile Communication (GSM); Requirements for GSM operation on railways | 2.3.0 | Note 2 |
| 65 | TS 102 281 | Detailed requirements for GSM operation on railways | 3.0.0 | Note 3 |
| 66 | TS 103 169 | ASCI Options for Interoperability | 1.1.1 | |
| 67 | (MORANE) P 38 T 9001 | FFFIS for GSM-R SIM Cards | 5.0 | Note 10 |
| 68 | ETSI TS 102 610 | Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways | 1.3.0 | |
| 69 | (MORANE) F 10 T 6002 | FFFS for Confirmation of High Priority Calls | 5.0 | |
| 70 | (MORANE) F 12 T 6002 | FIS for Confirmation of High Priority Calls | 5.0 | |
| 71 | (MORANE) E 10 T 6001 | FFFS for Functional Addressing | 4.1 | |
| 72 | (MORANE) E 12 T 6001 | FIS for Functional Addressing | 5.1 | |
| 73 | (MORANE) F 10 T6001 | FFFS for Location Dependent Addressing | 4 | |
| 74 | (MORANE) F 12 T6001 | FIS for Location Dependent Addressing | 3 | |
| 75 | (MORANE) F 10 T 6003 | FFFS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 76 | (MORANE) F 12 T 6003 | FIS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 77 | ERA/ERTMS/033281 | Interfaces between CCS trackside and other subsystems | 4.0 | Note 7 |
| 78 | Intentionally deleted | Note 6 | ||
| 79 | SUBSET-114 | KMC-ETCS Entity Off-line KM FIS | 1.0.0 | |
| 80 | Intentionally deleted | Note 5 | ||
| 81 | Reserved | Train Interface FFFIS | ||
| 82 | Reserved | FFFIS TI – Safety Analysis | ||
| Index No | ||||
|---|---|---|---|---|
| Reference | Name of Specification | Version | Notes | |
| 1 | Intentionally deleted | |||
| 2 | Intentionally deleted | |||
| 3 | SUBSET-023 | Glossary of Terms and Abbreviations | 3.3.0 | |
| 4 | SUBSET-026 | System Requirements Specification | 3.6.0 | |
| 5 | SUBSET-027 | FIS Juridical Recording | 3.3.0 | |
| 6 | ERA_ERTMS_015560 | ETCS Driver Machine interface | 3.6.0 | |
| 7 | SUBSET-034 | Train Interface FIS | 3.2.0 | |
| 8 | SUBSET-035 | Specific Transmission Module FFFIS | 3.2.0 | |
| 9 | SUBSET-036 | FFFIS for Eurobalise | 3.1.0 | |
| 10 | SUBSET-037 | EuroRadio FIS | 3.2.0 | |
| 11 | SUBSET-038 | Offline key management FIS | 3.1.0 | |
| 12 | SUBSET-039 | FIS for the RBC/RBC handover | 3.2.0 | |
| 13 | SUBSET-040 | Dimensioning and Engineering rules | 3.4.0 | |
| 14 | SUBSET-041 | Performance Requirements for Interoperability | 3.2.0 | |
| 15 | Intentionally deleted | |||
| 16 | SUBSET-044 | FFFIS for Euroloop | 2.4.0 | |
| 17 | Intentionally deleted | |||
| 18 | Intentionally deleted | |||
| 19 | SUBSET-047 | Trackside-Trainborne FIS for Radio infill | 3.0.0 | |
| 20 | SUBSET-048 | Trainborne FFFIS for Radio infill | 3.0.0 | |
| 21 | Intentionally deleted | |||
| 22 | Intentionally deleted | |||
| 23 | SUBSET-054 | Responsibilities and rules for the assignment of values to ETCS variables | 3.0.0 | |
| 24 | Intentionally deleted | |||
| 25 | SUBSET-056 | STM FFFIS Safe time layer | 3.0.0 | |
| 26 | SUBSET-057 | STM FFFIS Safe link layer | 3.1.0 | |
| 27 | SUBSET-091 | Safety Requirements for the Technical Interoperability of ETCS in Levels 1 and 2 | 3.6.0 | |
| 28 | Intentionally deleted | |||
| 29 | SUBSET-102 | Test specification for interface "K" | 2.0.0 | |
| 30 | Intentionally deleted | |||
| 31 | SUBSET-094 | Functional requirements for an onboard reference test facility | 3.1.0 | |
| 32 | EIRENE FRS | GSM-R Functional requirements specification | 8.0.0 | Note 10 |
| 33 | EIRENE SRS | GSM-R System requirements specification | 16.0.0 | Note 10 |
| 34 | A11T6001 | (MORANE) Radio Transmission FFFIS for EuroRadio | 13.0.0 | |
| 35 | Intentionally deleted | |||
| 36 a | Intentionally deleted | |||
| 36 b | Intentionally deleted | |||
| 36 c | SUBSET-074-2 | FFFIS STM Test cases document | 3.1.0 | |
| 37 a | Intentionally deleted | |||
| 37 b | SUBSET-076-5-2 | Test cases related to features | 3.3.0 | |
| 37 c | SUBSET-076-6-3 | Test sequences | 3.2.0 | |
| 37 d | SUBSET-076-7 | Scope of the test specifications | 3.3.0 | |
| 37 e | Intentionally deleted | |||
| 38 | 06E068 | ETCS Marker-board definition | 2.0 | |
| 39 | SUBSET-092-1 | ERTMS EuroRadio Conformance Requirements | 3.1.0 | |
| 40 | SUBSET-092-2 | ERTMS EuroRadio test cases safety layer | 3.1.0 | |
| 41 | Intentionally deleted | |||
| 42 | Intentionally deleted | |||
| 43 | SUBSET 085 | Test specification for Eurobalise FFFIS | 3.0.0 | |
| 44 | Intentionally deleted | |||
| 45 | SUBSET-101 | Interface "K" Specification | 2.0.0 | |
| 46 | SUBSET-100 | Interface "G" Specification | 2.0.0 | |
| 47 | Intentionally deleted | |||
| 48 | Reserved | Test specification for mobile equipment GSM-R | Note 4 | |
| 49 | SUBSET-059 | Performance requirements for STM | 3.1.0 | |
| 50 | SUBSET-103 | Test specification for Euroloop | 1.1.0 | |
| 51 | Intentionally deleted | |||
| 52 | SUBSET-058 | FFFIS STM Application layer | 3.2.0 | |
| 53 | Intentionally deleted | |||
| 54 | Intentionally deleted | |||
| 55 | Intentionally deleted | |||
| 56 | Intentionally deleted | |||
| 57 | Intentionally deleted | |||
| 58 | Intentionally deleted | |||
| 59 | Intentionally deleted | |||
| 60 | SUBSET-104 | ETCS System Version Management | 3.3.0 | |
| 61 | Intentionally deleted | |||
| 62 | Intentionally deleted | |||
| 63 | SUBSET-098 | RBC-RBC Safe Communication Interface | 3.0.0 | |
| 64 | EN 301 515 | Global System for Mobile Communication (GSM); Requirements for GSM operation on railways | 2.3.0 | Note 2 |
| 65 | TS 102 281 | Detailed requirements for GSM operation on railways | 3.0.0 | Note 3 |
| 66 | TS 103 169 | ASCI Options for Interoperability | 1.1.1 | |
| 67 | (MORANE) P 38 T 9001 | FFFIS for GSM-R SIM Cards | 5.0 | Note 10 |
| 68 | ETSI TS 102 610 | Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways | 1.3.0 | |
| 69 | (MORANE) F 10 T 6002 | FFFS for Confirmation of High Priority Calls | 5.0 | |
| 70 | (MORANE) F 12 T 6002 | FIS for Confirmation of High Priority Calls | 5.0 | |
| 71 | (MORANE) E 10 T 6001 | FFFS for Functional Addressing | 4.1 | |
| 72 | (MORANE) E 12 T 6001 | FIS for Functional Addressing | 5.1 | |
| 73 | (MORANE) F 10 T6001 | FFFS for Location Dependent Addressing | 4 | |
| 74 | (MORANE) F 12 T6001 | FIS for Location Dependent Addressing | 3 | |
| 75 | (MORANE) F 10 T 6003 | FFFS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 76 | (MORANE) F 12 T 6003 | FIS for Presentation of Functional Numbers to Called and Calling Parties | 4 | |
| 77 | ERA/ERTMS/033281 | Interfaces between CCS trackside and other subsystems | 4.0 | Note 7 |
| 78 | Intentionally deleted | Note 6 | ||
| 79 | SUBSET-114 | KMC-ETCS Entity Off-line KM FIS | 1.1.0 | |
| 80 | Intentionally deleted | Note 5 | ||
| 81 | Reserved | Train Interface FFFIS | ||
| 82 | Reserved | FFFIS TI – Safety Analysis | ||
| 83 | SUBSET-137 | On-line Key Management FFFIS | 1.0.0 | |
| No | Reference | Document name and comments | Version | Note |
|---|---|---|---|---|
| A1 | EN 50126-1 | Railway applications —The specification and demonstration of reliability, availability, maintainability and safety (RAMS) – Part 1: Generic RAMS Process | 2017 | |
| 1999 | 1,2 | |||
| A2 | EN 50128 | Railway applications — Communication, signalling and processing systems — Software for railway control and protection systems | 2011 | |
| A3 | EN 50129 | Railway applications — Communication, signalling and processing systems — Safety related electronic systems for signalling | 2003 | 1 |
| A4 | EN 50159 | Railway applications — Communication, signalling and processing systems | 2010 | 1 |
| A5 | EN 50126-2 | Railway Applications — The specification and demonstration of reliability, availability, maintainability and safety (RAMS) – Part 2: Systems Approach to Safety | 2017 | 3 |
| No | Reference | Document name and comments | Version | Note |
|---|---|---|---|---|
| A6 | ISO/IEC 17025 | General requirements for the competence of testing and calibration laboratories | 2017 |
| Open Point | Notes |
|---|---|
| Braking aspects | |
| Reliability/availability requirements | Frequent occurrences of degraded situations caused by failures of control-command and signalling equipment will decrease the system safety. |
| Characteristics of sand applied to tracks | |
| Characteristics of flange lubricators | See Annex A, Table A 2, Index 77 |
| Combination of rolling stock characteristics influencing shunting impedance | See Annex A, Table A 2, Index 77 |
| See Annex A, Table A 2, Index 77 |
Loading ...