ANNEX VI — Commission Implementing Regulation (EU) 2019/776 — Full Text

ANNEX VISupplementary provisions

ANNEX VI The Annex to Regulation (EU) 2016/919 is amended as follows: (1) Section 1.1 is amended as follows: (a) in the second subparagraph, the text ‘Annex I points 1.2 and 2.2 of Directive 2008/57/EC’ is replaced by the text ‘Annex I point 2 of Directive (EU) 2016/797’; (b) points (1) to (4) are replaced by the following: ‘(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. This list of vehicles shall include those which are specially designed to operate on the different types of high-speed lines described in point 1.2. (Geographical scope).’; (2) Section 1.2 is replaced by the following: ‘1.2. Geographical Scope The geographical scope of this TSI is the network of the whole rail system, as described in Annex I point 1 of Directive (EU) 2016/797 and excludes the infrastructure cases referred to in Articles 1(3) and 1(4) of Directive (EU) 2016/797. The TSI shall apply to networks with 1 435 mm, 1 520 mm, 1 524 mm, 1 600 mm and 1 668 mm track gauges. However, it shall not apply to short border crossing lines with 1 520 mm track gauges that are connected to the network of third countries.’; (3) Section 1.3 is amended as follows: (a) the text ‘Article 5(3) of Directive 2008/57/EC’ is replaced by the text ‘Article 4(3) of Directive (EU) 2016/797’; (b) points (8) and (9) are added after point (7) as follows: ‘(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).’; (c) the text ‘Article 5(5) of Directive 2008/57/EC’ is replaced by the text ‘Article 4(5) of Directive (EU) 2016/797’; (4) The first paragraph of section 2.1 is replaced by the following: ‘The Control-Command and Signalling Subsystems are defined in Annex II of Directive (EU) 2016/797 as: (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”.’; (5) Section 2.2 is amended as follows: (a) The first paragraph is replaced by the following: ‘The Control-Command and Signalling Subsystem TSI specifies only those requirements which are necessary to assure the interoperability of the Union rail system and the compliance with the essential requirements ( *1 ) . ( *1 ) Currently the CCS TSI does not specify any interoperability requirement for the interlockings, level crossings and certain other elements of the CCS.’;" (b) the text ‘Class B systems for the trans-European rail system network are a limited set of train protection limited set of train protection legacy systems that were in use in the trans-European rail network before 20 April 2001’ is replaced by ‘Class B systems for the trans-European rail system network are a limited set of train protection and voice radio legacy systems that were already in use in the trans-European rail network before 20 April 2001’; (c) the text ‘Class B systems for other parts of the network of the rail system in the European Union are a limited set of train protection legacy systems that were in use in that networks before 1 July 2015’ is replaced by ‘Class B systems for other parts of the network of the rail system in the European Union are a limited set of train protection and voice radio legacy systems that were already in use in those networks before 1 July 2015’; (d) the text ‘The list of Class B systems is established in the European Railway Agency technical documents “List of CCS Class B systems, ERA/TD/2011-11, version 3.0.”’ is replaced by ‘The list of Class B systems is established in the European Union Agency for Railways technical document “List of CCS Class B systems, ERA/TD/2011-11, version 4.0.”’; (e) the text ‘All Control-Command and Signalling Subsystems, even where not specified in this TSI, shall be assessed according with Commission Implementing Regulation (EU) No 402/2013.’ is added at the end of Section 2.2. (6) Section 2.3 is replaced by the following: ‘2.3 Trackside Application Levels (ETCS) The interfaces specified by this TSI define the means of data transmission to, and (where appropriate) from trains. The ETCS specifications referenced by this TSI provide application levels from which a trackside implementation may choose the means of transmission that meet its requirements. This TSI defines the requirements for all application levels. For the technical definition of the ETCS application levels see Annex A, 4.1 c.’; (7) Section 3.1 is amended as follows: (a) the text ‘Directive 2008/57/EC’ is replaced by the reference to ‘Directive (EU) 2016/797’; (b) a new point (6) is added after point 5 as follows: ‘(6) Accessibility.’; (8) Section 3.2.1 is replaced by the following: ‘3.2.1 Safety Every Control-Command and Signalling Subsystems project shall take the measures necessary to ensure that the level of risk of an incident occurring within the scope of the Control-Command and Signalling Subsystems, is not higher than the objective for the service. To ensure that the measures taken to achieve safety do not jeopardise interoperability, the requirements of the basic parameter defined in point 4.2.1 (Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability) shall be respected. For the ETCS Class A system the safety objective is apportioned between the Control-Command and Signalling On-board and Trackside Subsystems. The detailed requirements are specified in the basic parameter defined in point 4.2.1 (Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability). This safety requirement shall be met together with the availability requirements as defined in Point 3.2.2 (Reliability and Availability). For the ETCS Class A system: (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 ( *2 ) , as referred to in Article 6(1)(a) of Directive (EU) 2016/798 of the European Parliament and of the Council ( *3 ) . Additionally the correct application of the risk management process as set out in Annex I of Regulation (EU) No 402/2013, as well as the appropriateness of the results from this application, shall be independently assessed by a CSM assessment body according to Article 6 of that Regulation. The CSM Assessment Body shall be accredited or recognised according to the requirements in Annex II of Regulation (EU) No 402/2013 in the fields of “Control-command and signalling” and “System safe integration” as listed in item 5 “classification” of ERADIS database entry for Assessment Bodies. The application of the specifications as referred to in Annex A, Table A 3 is an appropriate means to fully comply to the risk management process as set out in Annex I of the Commission Implementing Regulation (EU) No 402/2013 for design, implementation, production, installation and validation (incl. Safety acceptance) of interoperability constituents and subsystems. When different specifications from the ones referred to in Annex A, Table 3 are applied, at least equivalence shall be demonstrated with the specifications in Annex A, Table 3. Whenever the specifications as referred to in Annex A, Table A 3 are used as an appropriate means to fully comply to the risk management process as set out in Annex I of the Commission Implementing Regulation (EU) No 402/2013, in order to avoid unnecessary duplication of independent assessment work, the independent safety assessment activities that are required by the specifications referred to in Annex A, Table A 3 shall be carried out by an Assessment Body accredited or recognized as specified in the section above instead of a CENELEC independent safety assessor. ( *2 ) 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 )." ( *3 ) 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 ).’;" (9) The second paragraph of section 3.2.2 is replaced by the following: ‘The level of risk caused by age and wear of constituents used within the subsystem shall be monitored. The requirements for maintenance stated in point 4.5 shall be respected.’; (10) Section 3.2.5.2 is deleted; (11) A new section 3.2.6 is added as follows: ‘3.2.6 Accessibility No requirements are mandated for the CCS subsystems for the essential requirement accessibility.’ (12) Section 4.1.1 is amended as follows: (a) in point (16) the text ‘points 4.2.16’ is replaced by ‘point 4.2.16’; (b) a new point (17) is added as follows: ‘(17) ETCS and Radio System Compatibility (point 4.2.17)’; (13) In section 4.1.2 the text ‘limiting the movement of TSI-compliant on-board subsystems.’ is replaced by ‘limiting the movement of vehicles with TSI-compliant on-board subsystems.’; (14) Table 4.1 in section 4.1.3 is replaced by: ‘ Table 4.1 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’ (15) The title of section 4.2.1 is replaced by ‘ Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability ’; (16) Section 4.2.2 is replaced by the following: ‘4.2.2. On-board ETCS functionality The basic parameter for ETCS on-board functionality describes all of the functions needed to run a train in a safe way. The primary function is to provide automatic train protection and cab signalling: (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. These functions shall be implemented in accordance with Annex A 4.2.2 b and their performance shall conform to Annex A 4.2.2 a. The requirements for tests are specified in Annex A 4.2.2 c. The main functionality is supported by other functions, to which Annex A 4.2.2 a and Annex A 4.2.2 b also apply, together with the additional specifications indicated below: (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.’; (17) Section 4.2.3 is replaced by the following: ‘4.2.3. Trackside ETCS functionality This Basic parameter describes the ETCS trackside functionality. It contains all ETCS functionality to provide a safe path to a specific train. The main functionality is: (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. These functions shall be implemented in accordance with Annex A 4.2.3 b and their performance shall conform to Annex A 4.2.3 a. The main functionality is supported by other functions, to which Annex A 4.2.3 a and Annex A 4.2.3 b also apply, together with the additional specifications indicated below: (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).’; (18) In section 4.2.6.3 the reference to ‘4.2.6f’ is deleted. (19) In section 4.2.11 the text ‘Control-Command and Signalling equipment.’ is replaced by ‘Control-Command and Signalling train detection equipment.’ (20) In section 4.2.16 the text ‘by Control-command and signalling On-board Subsystems’ is replaced by ‘by Control-command and signalling On-board Interoperability Constituents and Subsystems’; (21) A new section 4.2.17 is added as follows: ‘4.2.17. ETCS and Radio System Compatibility Due to the different possible implementations and the status of the migration to fully compliant CCS Subsystems, checks shall be performed in order to demonstrate the technical compatibility between the on-board and trackside CCS Subsystems. The necessity of these checks shall be considered as a measure to increase the confidence on the technical compatibility between the CCS subsystems. It is expected that these checks will be reduced until the principle stated in 6.1.2.1 is achieved. 4.2.17.1. ETCS System Compatibility ETCS System Compatibility (ESC) shall be the recording of technical compatibility between ETCS on-board and the trackside parts ETCS of the CCS subsystems within an area of use. ESC type shall be the value assigned to record the technical compatibility between an ETCS on-board and a section within the area of use. All sections of the Union network which require the same set of checks for the demonstration of ESC shall have the same ESC type. 4.2.17.2. Radio System Compatibility Radio System Compatibility (RSC) shall be the recording of technical compatibility between voice or data radio on-board and the trackside parts of GSM-R of the CCS subsystems. RSC type shall be the value assigned to record the technical compatibility between a voice or data radio and a section within the area of use. All sections of the Union network which require the same set of checks for the demonstration of RSC shall have the same RSC type.’; (22) Section 4.3 is amended as follows: (a) in the title of the tables, the text ‘Clause’ is replaced by ‘Point’; (b) section 4.3.1 is replaced by the following: ‘4.3.1 Interface to the Operation and Traffic Management Subsystem Interface with Operation and Traffic Management TSI Reference CCS TSI Reference Operation and Traffic Management TSI ( 1 ) Parameter Point Parameter Point Operating rules (normal and degraded conditions) 4.4 Rule book Operating rules 4.2.1.2.1 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 Use of sanding equipment On-board flange lubrication Use of composite brake blocks 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 (c) section 4.3.2 is replaced by the following: ‘4.3.2. Interface to the Rolling Stock Subsystem 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 ( 2 ) 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 ( 3 ) 4.2.3.3.1.1 LOC & PAS TSI ( 4 ) 4.2.3.3.1.1 Wagon TSI ( 5 ) 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 External visibility Head lights 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 4.2.2 4.2.3 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 (d) in section 4.3.4 the text ‘Phase separation points’ is replaced by ‘Phase separation sections’; (23) In section 4.4 the text ‘Traffic Operation and Management TSI’ is replaced by ‘Operation and Traffic Management TSI’. (24) In section 4.5.1 at the end of point (1) the following text is added ‘For equipment error corrections see point 6.5,’. (25) Section 4.8 is replaced by: ‘4.8 Registers The data to be provided for the registers provided for in Articles 48 and 49 of Directive (EU) 2016/797 are those indicated in Commission Implementing Decision 2011/665/EU ( *4 ) and Commission Implementing Regulation (EU) 2019/777 ( *5 ) . ( *4 ) Commission Implementing Decision 2011/665/EU of 4 October 2011 on the European register of authorised types of railway vehicles ( OJ L 264, 8.10.2011, p. 32 )." ( *5 ) Commission Implementing Regulation (EU) 2019/777 of 16 May 2019 on the common specifications for the register of railway infrastructure and repealing Implementing Decision 2014/880/EU ( OJ L 139 I, 27.5.2019, p. 312 ).’;" (26) A new section 4.9 is added below section 4.8 as follows: ‘4.9. Route compatibility checks before the use of authorised vehicles The parameters of the on-board CCS subsystem to be used by the railway undertaking, for the purpose of route compatibility check, are described in Appendix D1 of Commission Implementing Regulation (EU) 2019/773 ( *6 ) . ( *6 ) Commission Implementing Regulation (EU) 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and repealing Decision 2012/757/EU ( OJ L 139 I, 27.5.2019, p. 5 ).’;" (27) Section 5.1 is replaced by the following: ‘5.1 Definition In accordance with Article 2(7) of Directive (EU) 2016/797, interoperability constituents means any elementary component, group of components, subassembly or complete assembly of equipment incorporated or intended to be incorporated into a subsystem, upon which the interoperability of the rail system depends directly or indirectly, including both tangible objects and intangible objects.’; (28) In section 5.2.2 a new paragraph is added at the end of the section as follows: ‘Compliance of interfaces internal to the group of ICs to basic parameters of Chapter 4 does not have to be verified. Compliance of interfaces external to the group of ICs has to be verified to demonstrate conformity with the basic parameters related to the requirements of these external interfaces.’; (29) Section 5.3 is amended as follows: (a) Table 5.1.a is replaced by: ‘ Table 5.1.a Basic interoperability constituents in the Control-Command and Signalling On-board Subsystem 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) 4.2.1 4.5.1 On-board ETCS functionality (excluding odometry) 4.2.2 ETCS and GSM-R air gap interfaces — RBC (Radio data transmission optional) — Radio in-fill unit (functionality optional) — Eurobalise air gap — Euroloop air gap (functionality optional) 4.2.5 4.2.5.1 4.2.5.1 4.2.5.2 4.2.5.3 Interfaces — STM (implementation of interface K optional) — GSM-R ETCS Data Only Radio — Odometry — Key management system — ETCS ID Management — ETCS Driver-Machine Interface — Train interface — On-board recording device 4.2.6.1 4.2.6.2 4.2.6.3 4.2.8 4.2.9 4.2.12 4.2.2 4.2.14 Construction of equipment 4.2.16 2 Odometry equipment Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 On-board ETCS functionality: only Odometry 4.2.2 Interfaces — On-board ETCS 4.2.6.3 Construction of equipment 4.2.16 3 Interface of External STM Interfaces — On-board ETCS 4.2.6.1 4 GSM-R voice cab radio Note: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent Reliability, Availability, Maintainability, (RAM) 4.2.1.2 4.5.1 Basic communication functions 4.2.4.1 Voice and operational communication applications 4.2.4.2 Interfaces — GSM-R air gap — GSM-R Driver-Machine Interface 4.2.5.1 4.2.13 Construction of equipment 4.2.16 5 GSM-R ETCS Data only Radio Note: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent Reliability, Availability, Maintainability (RAM) 4.2.1.2 4.5.1 Basic communication functions 4.2.4.1 ETCS data communication applications 4.2.4.3 Interfaces — On-board ETCS — GSM-R air gap 4.2.6.2 4.2.5.1 Construction of equipment 4.2.16 6 GSM-R SIM card Note: it is the responsibility of the GSM-R network operator to deliver to railway undertakings the SIM cards to be inserted in GSM-R terminal equipment Basic communication functions 4.2.4.1 Construction of equipment 4.2.16’ (b) table 5.1.b is replaced by: ‘ Table 5.1.b Groups of interoperability constituents in the Control-Command and Signalling On-board Subsystem (This table is an example to show the structure. Other groups are allowed.) 1 2 3 4 No Group of Interoperability constituents Characteristics Specific requirements to be assessed by reference to Chapter 4 1 ETCS on-board Odometry equipment Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 On-board ETCS functionality 4.2.2 ETCS and GSM-R air gap interfaces — RBC (Radio data transmission optional) — Radio in-fill unit (functionality optional) — Eurobalise air gap — Euroloop air gap (functionality optional) 4.2.5 4.2.5.1 4.2.5.1 4.2.5.2 4.2.5.3 Interfaces — STM (implementation of interface K optional) — GSM-R ETCS Data Only Radio — Key management system — ETCS-ID Management — ETCS Driver Machine Interface — Train interface — On-board recording device 4.2.6.1 4.2.6.2 4.2.8 4.2.9 4.2.12 4.2.2 4.2.14 Construction of equipment 4.2.16’ (c) table 5.2.a is replaced by: ‘ Table 5.2.a Basic interoperability constituents in the Control-Command and Signalling Trackside Subsystem 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) 4.2.1 4.5.1 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 — Neighbouring RBC — Data radio communication — Key management system — ETCS-ID Management 4.2.7.1, 4.2.7.2 4.2.7.3 4.2.8 4.2.9 Construction of equipment 4.2.16 2 Radio in-fill unit Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 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 — Data radio communication — Key management system — ETCS-ID Management — Interlocking and LEU 4.2.7.3 4.2.8 4.2.9 4.2.3 Construction of equipment 4.2.16 3 Eurobalise Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 ETCS and GSM-R air gap interfaces: only Eurobalise communication with train 4.2.5.2 Interfaces — LEU — Eurobalise 4.2.7.4 Construction of equipment 4.2.16 4 Euroloop Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 ETCS and GSM-R air gap interfaces: only Euroloop communication with train 4.2.5.3 Interfaces — LEU – Euroloop 4.2.7.5 Construction of equipment 4.2.16 5 LEU Eurobalise Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 Trackside ETCS functionality (excluding communication via radio in-fill, Euroloop and level 2 and level 3 functionality) 4.2.3 Interfaces — LEU — Eurobalise 4.2.7.4 Construction of equipment 4.2.16 6 LEU Euroloop Reliability, Availability, Maintainability, Safety (RAMS) 4.2.1 4.5.1 Trackside ETCS functionality (excluding communication via radio in-fill, Eurobalise and level 2 and level 3 functionality) 4.2.3 Interfaces — LEU – Euroloop 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’ (30) Section 6.1 is replaced by the following: ‘6.1. Introduction 6.1.1. General principles 6.1.1.1. Compliance with basic parameters Fulfilment of the essential requirements set out in Chapter 3 of this TSI shall be ensured through compliance with the basic parameters specified in Chapter 4. This compliance shall be demonstrated by: (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). 6.1.1.2. Essential requirements fulfilled by National Rules In certain cases, some of the essential requirements may be met by national rules, because of: (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. In such cases, assessment of conformity with those rules shall be carried out under the responsibility of the Member States concerned according to notified procedures. See point 6.4.2. 6.1.1.3. Partial fulfilment of TSI requirements With regard to checking if essential requirements are fulfilled through compliance with the basic parameters, and without prejudice to the obligations set out in Chapter 7 of this TSI, control-command and signalling interoperability constituents and subsystems that do not implement all functions, performance and interfaces as specified in Chapter 4 (including the specifications referred to in Annex A), can obtain EC certificates of conformity or, respectively, certificates of verification, under the following conditions for issuing and using the certificates: (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 ( *7 ) that an operator needs to identify such conditions and limits of use. (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. If a control-command and signalling interoperability constituent or subsystem does not implement all functions, performance and interfaces specified in this TSI, the provisions of point 6.4.3 shall apply. 6.1.2. Principles for testing ETCS and GSM-R 6.1.2.1. Principle The principle is that a Control-Command and Signalling On-board Subsystem covered by an “EC” declaration of verification is able to run on every Control-Command and Signalling Trackside Subsystem covered by an “EC” Declaration of verification, under the conditions specified in this TSI, with no additional verifications. Achievement of this principle is facilitated by: (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. 6.1.2.2. Operational test scenarios For the purpose of this TSI, an “operational test scenario” means a sequence of trackside and on-board events related to or influencing the Control-command and Signalling subsystems (e.g. sending/receiving messages, exceeding a speed limit, actions of operators) and the specified timing between them in order to test the intended railway system operation in situations relevant for ETCS and GSM-R (e.g. entry of a train into an equipped area, awakening of a train, overriding a signal at stop). The operational tests scenarios are based on the engineering rules adopted for the project. Check of compliance of a real implementation with an operational tests scenario shall be possible gathering information through easily accessible interfaces (preferably the standard interfaces specified in this TSI). 6.1.2.3. Requirements for Operational test scenarios The set of engineering rules for the trackside parts of ETCS and GSM-R and related operational test scenarios for the Trackside Control-command and Signalling Subsystem shall be sufficient to describe all intended system operations relevant for the Trackside Control-command and Signalling Subsystem in normal and identified degraded situations, and: (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. 6.1.2.4. Requirements for ETCS System Compatibility The Agency shall set up and manage in a technical document the set of checks to demonstrate the technical compatibility of an on-board subsystem with the trackside subsystem. Infrastructure Managers, with the support of the ETCS suppliers for their network, shall submit to the Agency the definition of the necessary checks (as defined in 4.2.17) on their network by 16 January 2020 at the latest. Infrastructure Managers shall classify the ETCS lines according to ESC types in RINF. Infrastructure Managers shall submit to the Agency any changes on the referred checks for their network. The Agency shall update the technical document within 5 working days. 6.1.2.5. Requirements for Radio System Compatibility The Agency shall set up and manage in a technical document the set of checks to demonstrate the technical compatibility of an on-board subsystem with the trackside subsystem. Infrastructure Managers, with the support of the GSM-R suppliers for their network, shall submit to the Agency the definition of the necessary checks (as defined in 4.2.17) on their network by 16 January 2020 at the latest. Infrastructure Managers shall classify their lines according to RSC types for voice and, if applicable, ETCS data in RINF. Infrastructure Managers shall submit to the Agency any changes on the referred checks for their network. The Agency shall update the technical document within 5 working days. ( *7 ) The template to be used to provide this information will be defined in the Application Guide.’;" (31) Section 6.2 is amended as follows: (a) in section 6.2.1, the text ‘Article 13(1) and Annex IV to Directive 2008/57/EC’ is replaced by the text ‘Article 10(1) and Article 9(2) of Directive (EU) 2016/797’; (b) table 6.1 is replaced by the following: ‘ Table 6.1 Conformity assessment requirements of an interoperability constituent or a group of interoperability constituents 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) Check compliance with the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5, i.e. 1. respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures 2. the development process is able to detect and eliminate systematic failures 1. Calculations for the THRs caused by random failures, supported by reliability data. 2.1. The manufacturer's quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see note) 2.2. The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see note) 2.3. The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5 2.4. The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note) Note: The standard shall satisfy at least the following requirements: 1. be compliant with the requirements for code of practice, as stated in Annex I, point 2.3.2, of Regulation (EU) No 402/2013 2. be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the Notified Body; 3. be relevant for the control of the considered hazards in the system under assessment; 4. be publicly available for all actors who want to use it. 4 Check that the quantitative reliability target (related to random failures) indicated by the applicant is met Calculations 5 Elimination of systematic failures Tests of equipment (full Interoperability Constituent or separately for subassemblies) in operational conditions, with repair when defects are detected. Documentation accompanying the certificate which indicates which kind of verifications have been performed, which standards have been applied and criteria adopted to consider these tests completed (according to decisions of the applicant). 6 Check compliance with maintenance requirements – point 4.5.1 Document check’ (c) in section 6.2.4.1 point (2) is replaced by the following: ‘(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 ( *8 ) and the standards referred to in Annex A, Table A 4 to carry out tests with the use of the test architecture and the procedures specified in Annex A 4.2.2.c. ( *8 ) 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 ).’ " (d) sections 6.2.5 and 6.2.6 are deleted; (32) Section 6.3 is amended as follows: (a) section 6.3.1 is replaced by the following: ‘6.3.1. Assessment procedures for Control-Command and Signalling Subsystems This Chapter deals with the “EC” declaration of verification for the Control-Command and Signalling On-board Subsystem and the “EC” declaration of verification for the Control-Command and Signalling Trackside Subsystem. At the request of the applicant the Notified Body shall carry out an “EC” verification of a Control-Command and Signalling On-board or Trackside Subsystem in accordance with Annex IV to Directive (EU) 2016/797. The applicant shall draw up the “EC” declaration of verification for the Control-Command and Signalling On-board or Trackside Subsystem in accordance with Article 15(1) and Article 15(9) of Directive (EU) 2016/797. The content of the “EC” declaration of verification shall conform to Article 15(9) of Directive (EU) 2016/797. The assessment procedure shall be carried out using the modules specified in point 6.3.2 (Modules for Control-Command and Signalling Subsystems). The “EC” declarations of verification for a Control-Command and Signalling On-board Subsystem and of a Control-Command and Signalling Trackside Subsystem, together with the certificates of conformity, shall be deemed sufficient to ensure that the subsystems are compatible under the conditions specified in this TSI.’; (b) section 6.3.2.3 is replaced by the following: ‘6.3.2.3. Conditions for using modules for On-board and Trackside Subsystems With reference to point 4.2 of Module SB (type-examination), design review is requested. With reference to point 4.2 of Module SH1 (full quality management system with design examination), an additional type test is required.’; (c) in section 6.3.3, Table 6.2 is replaced by the following: ‘ Table 6.2 Conformity assessment requirements for an On-board Subsystem No Aspect What to assess Supporting evidence 1 Use of interoperability constituents Check whether the interoperability constituents to be integrated into the subsystem are all covered by an “EC” Declaration of conformity and a corresponding certificate. The Subsystem needs to be checked with a SIM card compliant with the requirements of this TSI. Changing the SIM card with another one compliant with the TSI is not a modification of the Subsystem. 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 ( 6 ) 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 Integration with Control-Command and Signalling Trackside Subsystems and other subsystems: tests under conditions representing the intended operation. Test the behaviour of the subsystem under as many different conditions as reasonably possible representing the intended operation (e.g line gradient, train speed, vibrations, traction power, weather conditions, design of Control-Command and Signalling trackside functionality). The test must be able to verify: 1. that odometry functions are correctly performed — basic parameter 4.2.2 2. that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16 These tests must also be such as to increase confidence that there will be no systematic failures. The scope of these tests excludes tests already carried out at different stages: tests performed on the interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. Tests under environmental conditions are not necessary for on-board GSM-R voice equipment. Note: Indicate in the certificate which conditions have been tested and which standards have been applied. Reports of test runs. (d) a new section 6.3.3.1 is added after table 6.2 as follows: ‘6.3.3.1. ETCS and radio system compatibility checks Particular attention shall be given to assessing the conformity of the on-board CCS subsystem regarding the Basic Parameter ETCS and radio system compatibility referred to in 4.2.17. Regardless of the module selected for the previous EC verification procedure for the on-board subsystem, the Notified Body shall check: (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. The Notified Body shall not check again any aspect covered during the already performed EC Verification procedure for the on-board subsystem. The Notified Body performing these checks may be a different one from the Notified Body performing the EC Verification procedure for the on-board subsystem. Performing these checks also at the level of Interoperability Constituent may reduce the amount of checks at the level of Control-command and Signalling Subsystem.’; (e) in section 6.3.4, table 6.3 is replaced by the following: ‘ Table 6.3 Conformity assessment requirements for a Trackside Subsystem 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 Check that the internal interfaces of the subsystem have been installed properly and function properly — Basic parameters 4.2.5, 4.2.7 and conditions specified by the manufacturer (N/A for IC axle counter) 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 (N/A for IC axle counter) Check of design specifications For IC axle counters (only): The integration of the IC in the subsystem has to be verified: Check index 77 document points 3.1.2.1, 3.1.2.4 and 3.1.2.5 only. Check the correct installation of equipment and conditions specified by the manufacturer and/or the Infrastructure manager. 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 Compatibility of train detection systems (Excluding axle counters) Check that the train detection systems comply with the requirements of this TSI — Basic parameters 4.2.10 and 4.2.11 Check the correct installation of equipment and conditions specified by the manufacturer and/or the Infrastructure manager. Evidence of compatibility of equipment from existing installations (for systems already in use); perform tests according to standards for new types. On-site measurements to prove correctness of installation. Document check of correct installation of equipment. 8 Reliability, Availability, Maintainability, Safety (RAMS) (excluding train detection) 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. Test the behaviour of the subsystem under many different conditions as reasonably feasible representing the intended operation (e.g. train speed, number of trains on the line, weather conditions). The test must be able to verify: 1. the performance of train detection systems — Basic parameters 4.2.10, 4.2.11, 2. that the Control-Command and Signalling Trackside subsystem is compatible with trackside environment – Basic parameter 4.2.16 These tests will also increase confidence in the absence of systematic failures. The scope of these tests excludes tests already done in different steps: tests performed at the level of interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. Note: Indicate in the certificate which conditions have been tested and which standards have been applied. 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.’ (33) Section 6.4 is replaced as follows: (a) section 6.4.1 is replaced by the following: ‘6.4.1. Assessment of parts of control-command and signalling subsystems Pursuant to Article 15(7) of Directive (EU) 2016/797, the Notified Body may issue certificates of verification for certain parts of a subsystem, if allowed to do so under the relevant TSI. As pointed out in point 2.2 (Scope) of this TSI, the trackside and on-board control-command and signalling subsystems contain parts, as specified in point 4.1 (Introduction). A certificate of verification may be issued for each part or for a combination of parts specified in this TSI; the Notified Body only checks if that particular part fulfils the TSI requirements. Regardless of which module is chosen, the Notified Body shall check that: (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.’; (b) in section 6.4.2, the text ‘certificate’ is replaced by the text ‘EC certificate’; (c) section 6.4.3.3 is replaced by the following: ‘6.4.3.3. Content of certificates In any event, notified bodies shall coordinate with the Agency the way in which conditions and restrictions of use of interoperability constituents and subsystems are managed in the relevant certificates and technical files in the working group set up under Article 24 of Regulation (EU) 2016/796 of the European Parliament and of the Council.’; (d) Section 6.4.4 is replaced by the following: ‘6.4.4. Intermediate Statement of Verification If conformity is assessed for parts of subsystems specified by the applicant and different from the parts allowed in Table 4.1 of this TSI, or if only certain stages of the verification procedure have been performed, only an intermediate statement of verification may be issued.’; (34) Section 6.5 is replaced by the following: ‘6.5. Management of errors Where deviations from intended functions and/or performance are detected during the tests or during the operational life of a subsystem, the applicants and/or operators shall inform without delay the Agency and the authorising entity that issued the authorisations for the concerned trackside subsystems or vehicles, to initiate the procedures set out in Article 16 of Directive (EU) 2016/797. As a result of the application of Article 16(3) of that Directive: (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. The Agency shall organise an efficient processing of all the information received in order to facilitate the Change Control Management process for improvement/further development of the specifications, including the test specifications.’; (35) Section 7.2 is amended as follows: (a) two new sections 7.2.1a and 7.2.1b are added below section 7.2.1 as follows: ‘7.2.1a Changes to an existing On-Board subsystem This point defines the principles to be applied by the entities managing the change and authorising entities in line with the EC verification procedure described in Article 15(9), Article 21(12) and Annex IV of Directive (EU) 2016/797. This procedure is further developed in Article 13, 15 and 16 of Commission Implementing Regulation (EU) 2018/545 ( 1* ) and in Commission Decision 2010/713/EU ( 2* ) . This point applies in case of any change(s) to an existing on-board subsystem or on-board subsystem type, including renewal or upgrade. It does not apply in case of changes covered by Article 15(1)(a) of Implementing Regulation (EU) 2018/545. 7.2.1a.1 Rules to manage changes in on-board CCS subsystems 1. Parts, as defined in Table 4.1 of this TSI, and basic parameters of the on-board subsystem that are not affected by the change(s) are exempt from conformity assessment against the provisions in this TSI. The list of parts and basic parameters affected by the change is to be provided by the entity managing the change. 2. A new assessment against the requirements of the applicable TSI shall only be needed for the basic parameters which may be affected by the change(s). 3. The entity managing the change shall inform a Notified Body of all changes affecting the conformity of the subsystem with the requirements of the relevant TSI(s) requiring new checks, in accordance with Articles 15 and 16 of Implementing Regulation (EU) 2018/545 and Decision 2010/713/EU and by application of modules SB, SD/SF or SH1 for the EC verification, and if relevant Article 15(5) of Directive (EU) 2016/797. 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. 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. 5. The changes impacting the Basic Design Characteristics of the on-board subsystem are defined in Table 7.1 Basic Design Characteristics and shall be classified as 15(1)(c) or 15(1)(d) of Implementing Regulation (EU) 2018/545, and in accordance with Table 7.1 Basic Design Characteristics changes not impacting but related to the Basic Design Characteristics shall be classified by the entity managing the change as 15(1)(b) of Implementing Regulation (EU) 2018/545. 6. Changes not covered by point 7.2.1a.1(5) above are deemed not to have any impact on the basic design characteristics. They will be classified by the entity managing the change as 15(1)(a) or 15(1)(b) of Implementing Regulation (EU) 2018/545. Note: The classification of the changes set out in points 7.2.1a.1(5) and 7.2.1a.1(6) above is performed by the entity managing the change without prejudice of the safety judgement mandated in Article 21(12)(b) of Directive (EU) 2016/797. 7. All changes shall remain compliant with the applicable TSIs ( 3* ) regardless its classification. Table 7.1 Basic Design Characteristics 1. TSI Point 2. Related basic design characteristic(s) 3. Changes not impacting the basic design characteristics according to 15(1)(b) of Regulation (EU) 2018/545 4. Changes impacting the basic design characteristic but inside the acceptable range of parameters therefore to be classified as Art 15.1(c) of Regulation (EU) 2018/545 5. Changes impacting the basic design characteristic and outside the acceptable range of parameters therefore to be classified as Art 15.1(d) of Regulation (EU) 2018/545 4.2.2 On-board ETCS functionality 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 4.2.17.1 ETCS System Compatibility ETCS System Compatibility Not applicable Adding or removing ESC statements, after checking by a NoBo Not applicable 4.2.4 Mobile communication functions for railways GSM-R 4.2.4.2 Voice and operational communication application 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 4.2.17.2 Radio System Compatibility Radio Voice System Compatibility Not applicable Adding or removing RSC statements, after checking by a NoBo Not applicable 4.2.4 Mobile communication functions for railways GSM-R 4.2.4.3 Data communication applications for ETCS 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) 4.2.17.2 Radio System Compatibility Radio Data System Compatibility Not applicable Adding or removing RSC statements, after checking by a NoBo Not applicable 4.2.4 Mobile communication functions for railways GSM-R 4.2.4.1 Basic communication function 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 4.2.6.1 ETCS and Class B train protection 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. Add or remove Class B train protection systems. The requirements for Class B system are the responsibility of the relevant Member State. 4.2.5.1 Radio communication with the train 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. Add or remove Class B radio legacy systems. The requirements for Class B system are the responsibility of the relevant Member State. 8. In order to establish the EC certificate, the Notified Body may 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. — 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. 9. In any case, the entity managing the change shall ensure that the technical documentation which is relating to the EC certificate is updated accordingly. 10. The updated technical documentation, related to the EC certificate is referred to in the technical file accompanying the EC declaration of verification issued by the entity managing the change for on-board subsystem declared as conformant to the modified type. 11. 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.2.1a.2 Conditions for a change in the On-board ETCS functionality that does not impact the basic design characteristics 1. The target functionality ( 4* ) remains unchanged or is set to the state already expected during the original certification or authorisation. 2. The interfaces relevant for safety & technical compatibility remain unchanged or are set to the state already expected during the original certification or authorisation. 3. The result of the safety judgement (e.g. safety case according to EN 50126) remains unchanged. 4. No new safety related application conditions (SRAC) or interoperability constraints have been added due to the change. 5. An Assessment Body (CSM RA) as specified in point 3.2.1 has independently assessed the applicant's risk assessment and within it the demonstration that the change does not adversely affect safety. The applicant's demonstration shall include the evidence that the change actually corrects the causes of the initial deviation of the functionality. 6. The change is performed under a quality management system approved by a notified body (e.g. according to modules CH1, SH1, CD, SD). For other modules (e.g. CF, SF) it shall be justified that the verification performed remains valid ( 5* ) . 7. The individual configuration management defines a “system identifier” (as defined in 7.2.1a.1.11) and the functional part has not been changed after the change. 8. The change shall be part of the configuration management required by Article 5 of Regulation (EU) 2018/545. 7.2.1a.3 Conditions for a change in the on-board mobile communication functions for railways that does not impact the basic design characteristics 1. The target functionality ( 6* ) remains unchanged or is set to the state already expected during the original certification or authorisation. 2. The interfaces relevant for technical compatibility remain unchanged or are set to the state already expected during the original certification or authorisation 3. The change is performed under a quality management system approved by a notified body (e.g. according to modules CH1, SH1, CD, SD). For other modules (e.g. CF, SF) it shall be justified that the verification performed remains valid ( 7* ) . 4. The change shall be part of the configuration management required by Article 5 of the Regulation (EU) 2018/545. 7.2.1b Changes to an existing trackside subsystem This point defines the principles to be applied by the entities managing the change and authorising entities in line with the EC verification procedure described in Article 15(9), Article 18(6) of Directive (EU) 2016/797 and in Decision 2010/713/EU. 7.2.1b.1 Rules to manage changes in trackside CCS subsystems In the event of upgrading or renewing the Control-Command and Signalling Subsystems bearing EC certificate of verification the following rules apply: 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. 7.2.1b.2 Conditions for a change in the trackside ETCS functionality that, if not fulfilled, requires new authorisation for placing in service 1. The target functionality ( 8* ) remains unchanged or is set to the state already expected during the original certification or authorisation. 2. The interfaces relevant for safety & technical compatibility remain unchanged or are set to the state already expected during the original certification or authorisation. 3. The result of the safety judgement (e.g. safety case according to EN 50126) remains unchanged. 4. No new safety related application conditions (SRAC) or interoperability constraints have been added due to the change. 5. When required in point 3.2.1, an Assessment Body (CSM RA) has independently assessed the applicant's risk assessment and within it the demonstration that the change does not adversely affect safety. The applicant's demonstration shall include the evidence that the change actually corrects the causes of the initial deviation of the functionality. 6. The change is performed under a quality management system approved by a notified body (e.g. according to modules CH1, SH1, CD, SD). For other modules (e.g. CF, SF, SG) it shall be justified that the verification performed remains valid ( 9* ) . 7. The individual configuration management defines a “system identifier” (as defined in 7.2.1b.1.6) and the functional part has not been changed after the change. 8. The change shall be part of the configuration management as defined in 7.2.1b.1.7. 7.2.1b.3 Conditions for a change in the trackside mobile communication functions for railways that if not fulfilled requires a new authorisation for placing in service 1. The target functionality ( 10* ) remains unchanged or is set to the state already expected during the original certification or authorisation. 2. The interfaces relevant for technical compatibility remain unchanged or are set to the state already expected during the original certification or authorisation. 3. The change is performed under a quality management system approved by a notified body (e.g. according to modules CH1, SH1, CD, SD). For other modules (e.g. CF, SF, SG) it shall be justified that the verification performed remains valid ( 11* ) . 4. The change shall be part of the configuration management as defined in 7.2.1b.1.7. 7.2.1b.4 Impact on the technical compatibility between on-board and trackside parts of the CCS subsystems Infrastructure managers shall ensure that changes to an existing trackside subsystem allow the continuation of the operation of TSI compliant ( 12* ) on-board subsystems in operation on the lines concerned by the changes. This requirement is not applicable when the changes are due to the implementation of a new level application trackside, by requirements defined in 7.2.6 (1) and (3), or of an incompatible application of the set of specifications referred to in Annex A to this TSI if the change is announced at least 3 years in advance unless a shorter period is agreed between the IM and the RU's who run services on these tracks ( 13* ) . ( 1* ) 1* Commission Implementing Regulation (EU) 2018/545 of 4 April 2018 establishing practical arrangements for the railway vehicle authorisation and railway vehicle type authorisation process pursuant to Directive (EU) 2016/797 of the European Parliament and of the Council ( OJ L 90, 6.4.2018, p. 66 ). " ( 2* ) 2* Commission Decision 2010/713/EU of 9 November 2010 on modules for the procedures for assessment of conformity, suitability for use and EC verification to be used in the technical specifications for interoperability adopted under Directive 2008/57/EC of the European Parliament and of the Council ( OJ L 319, 4.12.2010, p. 1 ). " ( 3* ) 3* According to Agency's Advice 2017/3 if there is no need for new authorisation the applicable TSI corresponds to the one used for the original certification. In case there is a need for new authorisation applicable TSI corresponds to the latest TSI. " ( 4* ) 4* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. " ( 5* ) 5* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. " ( 6* ) 6* Target functionality refers to the mobile communication functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. " ( 7* ) 7* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. " ( 8* ) 8* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. " ( 9* ) 9* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. " ( 10* ) 10* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. " ( 11* ) 11* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. " ( 12* ) 12* On-board subsystems with conditions and restrictions of use or non-detected deficiencies are not considered compliant regarding this clause. " ( 13* ) 13* An upgrade of tracks operated in mixed traffic to ETCS level 3 shall only be done if passenger and freight trains retain access to these tracks.’ " (b) in section 7.2.3, the text ‘Article 29(1) of Directive 2008/57/EC’ is replaced by ‘Article 51(1) of Directive (EU) 2016/797’; (c) section 7.2.6 is replaced by the following: ‘7.2.6. Conditions for mandatory and optional functions The applicant for EC verification of a Control-command and Signalling Trackside subsystem shall check whether Control-command and Signalling Trackside functions, which are defined “optional” in this TSI, are required by other TSIs or national rules or by the application of risk evaluation and assessment to ensure safe integration of subsystems. The trackside implementation of national or optional functions shall not prevent the use of that infrastructure by a train that complies only with the mandatory requirements of the On-board Class A system except as required for the following on-board optional functions: (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. An on-board subsystem, which incorporates a KER STM, may make it necessary to implement the K-interface.’; (36) Section 7.3.2 is amended as follows: (a) the text ‘point’ is replaced by ‘section’; (b) the text ‘already in service’ is replaced by ‘already on the market’; (37) Section 7.4.1 is replaced by: ‘7.4.1 Trackside installations Articles 1, 2 and Annex I to Commission Implementing Regulation (EU) 2017/6 ( *9 ) of 5 January 2017 on the European Rail Traffic Management System European deployment plan shall apply as referred to in Article 47 of Regulation (EU) No 1315/2013 ( *10 ) . Trackside shall not install and operate the Euroloop and radio infill data transmission, except on already existing installations or planned projects that use those data transmission. Such planned projects shall be notified to the European Commission by 30 June 2020. 7.4.1.1 High-speed network It is mandatory to fit ETCS trackside when: 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. ( *9 ) Commission Implementing Regulation (EU) 2017/6 of 5 January 2017 on the European Rail Traffic Management System European deployment plan ( OJ L 3, 6.1.2017, p. 6 )." ( *10 ) Regulation (EU) No 1315/2013 of the European Parliament and of the Council of 11 December 2013 on Union guidelines for the development of the trans-European transport network and repealing Decision No 661/2010/EU ( OJ L 348, 20.12.2013, p. 1 ).’;" (38) Section 7.4.2.1 is amended as follows: ‘7.4.2.1 New vehicles 1. In order to be placed on the market in accordance with Article 21 of Directive (EU) 2016/797, new vehicles, including vehicles authorised in conformity to a type shall be equipped with ETCS in accordance with Annex A of this TSI and shall comply with set of specifications #2 or #3 referred to in Table A 2 of Annex A ( *11 ) . 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 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. 3. All vehicle type authorisations granted based on conformity to set of specifications #1 referred to in Table A 2 of Annex A of this TSI shall not remain valid for authorising new vehicles in conformity to those vehicle types (without prejudice to the application of 7.4.2.3). All vehicles already authorised according to those vehicle types are not affected. ( *11 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable.’;" (39) New section 7.4.2.3 is added as follows: ‘7.4.2.3 Application of the TSI requirements for new vehicles during a transition phase 1. Some projects or contracts, which started before the date of application of this TSI, may lead to apply for an authorisation to put on the market ( *12 ) of new vehicles equipped with ETCS complying with specification #1 referred to in Table A 2.1 of Annex A of this TSI, and which do not fully comply with Section 7.4.2.1 of this TSI. For vehicles concerned by those projects or contracts, and in accordance with point (f) of Article 4(3) of Directive (EU) 2016/797, a transition phase is defined, during which the application of Section 7.4.2.1 of this TSI is not mandatory. 2. This transition phase applies to new vehicles authorised in conformity to a vehicle type ( *13 ) authorised before 1 January 2019 in any Member State on the basis of conformity to set of specifications #1 referred to in Table A 2 of Annex A of this TSI up to December 31 2020. 3. The transition phase is: (a) up to December 31 2020: In order to be placed on the market ( *12 ) in accordance with Article 21 of Directive 2016/797/EC, those new vehicles referred under 2 shall be equipped with ETCS in accordance with set of specifications #1, #2 or #3 referred to in Table A 2 of Annex A of this TSI. (b) If set of specification #1 is used, a condition for use shall be included in their authorisation to put on the market ( *12 ) enforcing compliance with set specifications #2 or #3 within a period of time not exceeding 1 July 2023. ( *12 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable." ( *13 ) Variants or versions of a vehicle type are considered to be authorised in conformity to an existing authorised type. Where the regime of Directive 2008/57/EC applies, changes which would give rise to variants or versions of a vehicle type under Implementing Regulation (EU) 2018/545 are also considered to be based upon an existing authorised type.’;" ( *12 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable." ( *12 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable." (40) In section 7.4.3, the text ‘placing in service’ is replaced by ‘placing on the market’; (41) Section 7.4.4 is amended as follows: (a) In the first paragraph the text ‘those lines with ETCS and decommissioning of class B systems’ is replaced by ‘those lines with ETCS and Class A Radio and decommissioning of class B systems’; (b) In point (1) the text ‘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.’ is replaced by ‘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)’; (c) In point (4)(i) the text ‘The dates of ETCS deployment’ is replaced by ‘The dates of ETCS and Class A Radio deployment’; (d) In point (4)(iii) the text ‘or other parts of the network.’ is replaced by ‘or other parts of the network, including service facilities’; (e) In the third paragraph the text ‘at least every five years.’ is replaced by ‘at least every five years. The update of the national implementation plans shall take into account the introduction of the next generation communication system(s), including but not limited to the date of start of operation and, when applicable, the date of decommissioning of GSM-R on (parts of) the Network.’; (f) the text ‘Article 29(1) of Directive 2008/57/EC’ is replaced by ‘Article 51(1) of Directive (EU) 2016/797’; (42) A new section 7.4a is added below section 7.4.4 as follows: ‘7.4a ETCS and radio system compatibility checks implementation rules Existing vehicles shall be deemed compatible with the ETCS and radio system compatibility types of the networks on which they are operating by 16 January 2020 without any further checks, maintaining the existing restrictions or conditions for use. Any subsequent modification of the vehicle or the infrastructure regarding the technical or route compatibility shall be managed according to the requirements specified for ETCS and Radio system compatibility.’; (43) In section 7.5 the fourth paragraph is replaced by the following: ‘Implementing a train detection system that is compliant with the requirements of this TSI can be done independently of the installation of ETCS or GSM-R.’; (44) In section 7.6.1, the text ‘points below should be read’ is replaced by ‘points below shall be read’; (45) In section 7.6.1, a new paragraph is added at the end as follows: ‘All specific cases and their relevant dates shall be re-examined in the course of future revisions of the TSI with a view to limiting their technical and geographical scope based on an assessment of their impact on safety, interoperability, cross border services, TEN-T corridors, and the practical and economic impacts of retaining or eliminating them. Special account shall be given to availability of EU funding. Specific cases shall be limited to the route or network where they are strictly necessary and taken account of through route compatibility procedures.’; (46) Section 7.6.2.1 is amended as follows: (a) the text ‘the vehicle should have’ is replaced by ‘the vehicle shall have’; (b) the text ‘Index 77, point 3.1.2.4’ is replaced by ‘Index 77, point 3.1.2.3’; (c) the text ‘Index 77, point 3.1.8’ is replaced by ‘Index 77, point 3.1.7’; (47) Section 7.6.2.2 is amended as follows: (a) the text ‘Index 77, point 3.1.2.4’ is replaced by ‘Index 77, point 3.1.2.3’; (48) In the last two rows in the third column of the table, the text ‘set of specifications 2’ is replaced by ‘set of specifications 2 or 3’; (49) Section 7.6.2.3 is amended as follows: (a) the text ‘Index 77, point 3.1.2.4’ is replaced by ‘Index 77, point 3.1.2.3’; (b) the text ‘Index 77, point 3.1.8’ is replaced by ‘Index 77, point 3.1.7’; (c) in the first row in the second column of the table; the text ‘T3’ is replaced by ‘P’; (d) in the first row in the third column of the table, the text ‘This Specific Case is linked with the use of TVM’ is replaced by ‘This Specific Case is linked with the use of track circuits using electrical joints’; (e) in the third row of the first column of the table, the text ‘the vehicle should have’ is replaced by ‘the vehicle shall have’; (f) a new row is added at the end of the table as follows: ‘4.2.10 Trackside Train Detection Systems Index 77, point 3.1.4.1. In addition to the TSI requirements, the allowed maximum amount of sand per unit and per rail within 30 s is: 750 g 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’ (50) Section 7.6.2.6 is replaced by the following: ‘7.6.2.6. Sweden Specific case Category Notes 4.2.4 Mobile communication functions for railways – GSM-R Index 33, statement 4.2.3: It is permissible to put on the market on-board Control-Command and Signalling Subsystems including 2 Watt GSM-R voice cab radios and ETCS data only radios. The subsystems shall be able to operate in networks with – 82 dBm. P No impact on interoperability 4.2.10 — Trackside Train Detection Systems Index 77, point 3.1.2.1: Maximum axle distance between two axles ≤ 17,5 m (ai in Fig. 1, point 3.1.2.1). P 4.2.10 — Trackside Train Detection Systems Index 77, point 3.1.2.3: Minimum axle distance between first and last axle ≥ 4,5 m (L-b1-b2 in Fig. 1, point 3.1.2.3). P 4.2.10 — Trackside Train Detection Systems Index 77, point 3.2.2.5: Frequency range: 0,0-2,0 Hz Interference current limit [rms value]: 25,0 A Evaluation method: Low-Pass filter Evaluation parameters: (Down sampling to 1 kHz, followed by) 2,0 Hz 4th order Butterworth low-pass filter, followed by an ideal rectifier to give the absolute value. The maximum interference current for a rail vehicle must not exceed 25,0 A in the frequency range 0,0-2,0 Hz. Inrush current may exceed 45,0 A for less than 1,5 seconds and 25 A for less than 2,5 seconds. P’ (51) In section 7.6.2.7 the text ‘Index 77, point 3.1.2.4’ is replaced by ‘Index 77, point 3.1.4.1’ (52) In section 7.6.2.8 a new row is added at the end of the table as follows: ‘4.2.10 Trackside Train Detection Systems Index 77, point 3.2.2.5: Frequency range: 93 - 110 Hz Interference current limit [rms value]: 2.8 A (for influencing unit) 2 A (for one traction unit) Evaluation method: Band Pass Filters Evaluation parameters: — BP filter characteristics: — Centre frequencies: 95, 96, 98, 100, 104, 106 and 108 Hz — 3dB-Bandwidth: 4 Hz — Butterworth, 6th order — RMS calculation: — Integration time: 0,5 s — Time overlap: 50 % 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.’ (53) A new section 7.6.2.9 is added after 7.6.2.8 as follows: ‘7.6.2.9 Italy Specific case Category Notes 4.2.10 — Trackside Train Detection Systems Index 77, point 3.2.2.4 and point 3.2.2.6: Frequency range: 82 - 86 Hz Interference current limit [rms value]: 1 125 A Evaluation method: Fast Fourier Transformation Evaluation parameters: Time window 1s, Hanning window, 50 % overlap, average on 6 consecutive windows P’ (54) A new section 7.6.2.10 is added after 7.6.2.9 as follows: ‘7.6.2.10 Czech Republic Specific case Category Notes 4.2.10 — Trackside Train Detection Systems Index 77, point 3.2.2.4 and point 3.2.2.6: Frequency range: 70,5 – 79,5 Hz Interference current limit [rms value]: 1 A Evaluation method: Band Pass Filters Evaluation parameters: — BP filter characteristics: — Centre frequencies: 73, 75, 77 Hz (continuous band) — 3dB-Bandwidth: 5 Hz — Butterworth, order 2*4 — RMS calculation: — Integration time: 0,5 s — Time overlap: min 75 % — Frequency range: 271,5 – 278,5 Hz — Interference current limit [rms value]: 0,5 A Evaluation method: Band Pass Filters Evaluation parameters: — BP filter characteristics: — Centre frequencies: 274, 276 Hz (continuous band) — 3dB-Bandwidth: 5 Hz — Butterworth, order 2*4 — RMS calculation: — Integration time: 0,5 s — Time overlap: min 75 % T3 This specific case is needed as long as track circuits type EFCP are used.’ (55) A new section 7.6.2.11 is added after 7.6.2.10 as follows: ‘7.6.2.11 The Netherlands Specific case Category Notes 4.2.10 — Trackside Train Detection Systems Index 77, point 3.2.2.6: Frequency range: 65-85 Hz (ATBEG limit) Interference current limit [rms value]: 0,5 A Evaluation method: Band Pass Filters Evaluation parameters: — BP filter characteristics — Centre frequency: 75 Hz — 3dB-Bandwith: 20 Hz — 20dB-Bandwith: 40 Hz — RMS calculation — Integration time: 5 s — Time overlap: 80 % Transient shorter than 1s only exceeding the ATBEG limit and not the GRS limit may be ignored. — Frequency range: 65-85 Hz (GRS TC limit) — Interference current limit [rms value]: 1,7 A Evaluation method: Band Pass Filters Evaluation parameters: — BP filter characteristics — Centre frequency: 75 Hz — 3dB-Bandwith: 20 Hz — 20dB-Bandwith: 40 Hz — RMS calculation — Integration time: 1,8 s — Time overlap: 80 % T3 This Specific Cases is needed in the context of the Class-B system ATBEG.’ (56) Annex A is replaced by the following: ‘ANNEX A References For each reference made in the basic parameters (Chapter 4 of this TSI) the following table indicates the corresponding mandatory specifications, via the Index in Table A 2 (Table A 2.1, Table A 2.2, Table A 2.3). Table A 1 Reference in Chapter 4 Index number (see Table A 2) 4.1 4.1 a Intentionally deleted 4.1 b Intentionally deleted 4.1 c 3 4.2.1 4.2.1 a 27, 78 4.2.2 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 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 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 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 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 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 4.2.8 a 11, 79, 83 4.2.9 4.2.9 a 23 4.2.10 4.2.10 a 77 (point 3.1) 4.2.11 4.2.11 a 77 (point 3.2) 4.2.12 4.2.12 a 6, 51 4.2.13 4.2.13 a 32, 33, 51, 80 4.2.14 4.2.14 a 5 4.2.15 4.2.15 a 38 Specifications One of the three tables in Table A 2 (Table A 2.1, Table A 2.2, Table A 2.3) of this Annex shall be applied for the trackside subsystem. For the on-board subsystem either Table A 2.2 or Table A 2.3 shall be applied, after the transition period defined in 7.4.2.3. When a document listed in Table A 2 incorporates, by copying or by reference to, a clearly identified point of another document, this point, and only this, shall be considered a part of the document listed in Table A 2. For the purposes of this TSI, when a document listed in Table A 2 makes a “mandatory” or “normative” reference to a document not listed in Table A 2, the referenced document shall always be understood as an acceptable means of compliance with basic parameters (that can be used for certification of Interoperability Constituents and Subsystems and not requiring future revisions of the TSI) and not as a mandatory specification. Note: specifications indicated as “Reserved” in Table A 2 are also listed as open points in Annex G when there is a need for notification of national rules to close the corresponding open points. Reserved documents not listed as open points are intended as improvements to the system. Table A 2.1 List of mandatory specifications Index No Set of specifications # 1 (only for trackside Subsystems. For on-board subsystems not to be applied after the transition period defined in 7.4.2.3) (ETCS Baseline 2 and GSM-R Baseline 1) 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 Table A 2.2 List of mandatory specifications Index No Set of specifications # 2 (ETCS Baseline 3 Maintenance Release 1 and GSM-R Baseline 1) 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 Table A 2.3 List of mandatory specifications Index No Set of specifications # 3 (ETCS Baseline 3 Release 2 and GSM-R Baseline 1) 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 Note 1: only the functional description of information to be recorded is mandatory, not the technical characteristics of the interface Note 2: the points of the specifications listed in point 2.1 of EN 301 515 which are referenced in Index 32 and Index 33 as “MI” are mandatory. Note 3: the change requests (CRs) listed in table 1 and 2 of TS 102 281 which affect points referenced in Index 32 and Index 33 as “MI” are mandatory. Note 4: Index 48 refers only to test cases for GSM-R mobile equipment. It is kept “reserved” for the time being. When agreed in a future revision of the TSI, the catalogue of available harmonised test cases for the assessment of mobile equipment and networks, according to the steps indicated in point 6.1.2 of this TSI, will be introduced in these tables. Note 5: the products which are on the market are already tailored to the needs of the RU related to GSM-R Driver Machine Interface and fully interoperable so there is no need for a standard in the TSI CCS. Note 6: information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 7: this document is ETCS and GSM-R baseline independent. Note 8: Intentionally deleted. Note 9: Intentionally deleted. Note 10: Only the (MI) requirements are mandated by TSI CCS. Note 11: Intentionally deleted. Note 12: Intentionally deleted. Note 13: Intentionally deleted. Note 14: Intentionally deleted. Table A 3 List of mandatory standards The application of the version of the standards listed in the table below, and their subsequent amendments when published as harmonised standard in the certification process is an appropriate means to fully comply to the risk management process as set out in Annex I of the Commission Implementing Regulation (EU) No 402/2013, without prejudice for the provisions of chapter 4 and chapter 6 of this TSI. 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 Note 1: this standard is harmonised, see “Commission Communication in the framework of the implementation of the Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community (recast)” ( OJ C 435, 15.12.2017 ), where also published editorial corrigenda are indicated. Note 2: this version of the standard may be used during the transitional period defined in the updated version of the standard. Note 3: To be used in combination with EN 50126-1 (2017). Table A 4 List of mandatory standards for accredited laboratories No Reference Document name and comments Version Note A6 ISO/IEC 17025 General requirements for the competence of testing and calibration laboratories 2017 (57) the Annex G is replaced by the following: ‘ANNEX G Open Points Open Point Notes Braking aspects It only applies to ETCS Baseline 2 (see Annex A, Table A 2, Index 15). Resolved for ETCS Baseline 3 (see Annex A, Table A 2, Indexes 4 and 13). 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 See Annex A, Table A 2, Index 77 This is not an open point for 1 520 mm. 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 Conducted interference: — Vehicle impedance — Substation impedance (for DC networks only) — Out-band limits — Interference current limits attributed to the substations and attributed to the rolling stock — Measurement, test and evaluation specification See Annex A, Table A 2, Index 77 ( *1 ) Currently the CCS TSI does not specify any interoperability requirement for the interlockings, level crossings and certain other elements of the CCS.’; ( *2 ) 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 ). ( *3 ) 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 ).’; ( *4 ) Commission Implementing Decision 2011/665/EU of 4 October 2011 on the European register of authorised types of railway vehicles ( OJ L 264, 8.10.2011, p. 32 ). ( *5 ) Commission Implementing Regulation (EU) 2019/777 of 16 May 2019 on the common specifications for the register of railway infrastructure and repealing Implementing Decision 2014/880/EU ( OJ L 139 I, 27.5.2019, p. 312 ).’; ( *6 ) Commission Implementing Regulation (EU) 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and repealing Decision 2012/757/EU ( OJ L 139 I, 27.5.2019, p. 5 ).’; ( *7 ) The template to be used to provide this information will be defined in the Application Guide.’; ( *8 ) 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* ) 1* Commission Implementing Regulation (EU) 2018/545 of 4 April 2018 establishing practical arrangements for the railway vehicle authorisation and railway vehicle type authorisation process pursuant to Directive (EU) 2016/797 of the European Parliament and of the Council ( OJ L 90, 6.4.2018, p. 66 ). ( 2* ) 2* Commission Decision 2010/713/EU of 9 November 2010 on modules for the procedures for assessment of conformity, suitability for use and EC verification to be used in the technical specifications for interoperability adopted under Directive 2008/57/EC of the European Parliament and of the Council ( OJ L 319, 4.12.2010, p. 1 ). ( 3* ) 3* According to Agency's Advice 2017/3 if there is no need for new authorisation the applicable TSI corresponds to the one used for the original certification. In case there is a need for new authorisation applicable TSI corresponds to the latest TSI. ( 4* ) 4* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. ( 5* ) 5* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. ( 6* ) 6* Target functionality refers to the mobile communication functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. ( 7* ) 7* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. ( 8* ) 8* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. ( 9* ) 9* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. ( 10* ) 10* Target functionality refers to the ETCS functionality that has been evaluated in the subsystem EC certificate. The Technical Opinions published by the Agency that correct errors in the TSI are considered to define the functionality state already expected during the original certification or authorisation. ( 11* ) 11* All activities required for a modification which are performed outside a quality management system approved by a notified body might require additional examinations or tests by the notified body. ( 12* ) 12* On-board subsystems with conditions and restrictions of use or non-detected deficiencies are not considered compliant regarding this clause. ( 13* ) 13* An upgrade of tracks operated in mixed traffic to ETCS level 3 shall only be done if passenger and freight trains retain access to these tracks.’ ( *9 ) Commission Implementing Regulation (EU) 2017/6 of 5 January 2017 on the European Rail Traffic Management System European deployment plan ( OJ L 3, 6.1.2017, p. 6 ). ( *10 ) Regulation (EU) No 1315/2013 of the European Parliament and of the Council of 11 December 2013 on Union guidelines for the development of the trans-European transport network and repealing Decision No 661/2010/EU ( OJ L 348, 20.12.2013, p. 1 ).’; ( *11 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable.’; ( *12 ) Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable. ( *13 ) Variants or versions of a vehicle type are considered to be authorised in conformity to an existing authorised type. Where the regime of Directive 2008/57/EC applies, changes which would give rise to variants or versions of a vehicle type under Implementing Regulation (EU) 2018/545 are also considered to be based upon an existing authorised type.’;’ ( 1 ) Commission Regulation (EU) 2015/995 of 8 June 2015 amending Decision 2012/757/EU concerning the technical specification for interoperability relating to the “operation and traffic management” subsystem of the rail system in the European Union ( OJ L 165, 30.6.2015, p. 1 ).’ ( 2 ) HS RS TSI is Commission Decision of 21 February 2008 concerning a technical specification for interoperability relating to the rolling stock sub-system of the trans-European high-speed rail system (2008/232/CE). ( 3 ) CR RS TSI is Commission Decision of 26 April 2011 concerning a technical specification for interoperability relating to the rolling stock subsystem — Locomotives and passenger rolling stock of the trans-European conventional rail system (2011/291/EU). ( 4 ) LOC & PAS TSI is Commission Regulation (EU) No 1302/2014 of 18 November 2014 concerning a technical specification for interoperability relating to the “rolling stock — locomotives and passenger rolling stock” subsystem of the rail system in the European Union. ( 5 ) Wagon TSI is Commission Regulation (EU) No 321/2013 of 13 March 2013 concerning the technical specification for interoperability relating to the subsystem rolling stock — freight wagons of the rail system in the European Union and repealing Decision 2006/861/EC.’ ( 6 ) In this case, the assessment of the management of transitions shall be according to national specifications.’

Compiled from an official source version. Later amendments or repeals may not be reflected; the official text prevails. · Read the official text ↗ · Data as of 2026-07-04

CitationANNEX VI of Commission Implementing Regulation (EU) 2019/776 (LawPlayer, data as of 2026-07-04)

Commission Implementing Regulation (EU) 2019/776 ANNEX VI

ANNEX VISupplementary provisions

Other provisions in Commission Implementing Regulation (EU) 2019/776

What to look at next