LegalizeCommission Implementing Regulation (EU) 2023/1695 of 10 August 2023 on the technical specification for interoperability relating to the control-command and signalling subsystems of the rail system in the European Union and repealing Regulation (EU) 2016/919 (Text with EEA relevance)
| Index No | ETCS Baseline 4 Release 1; RMR: GSM-R Baseline 1 Maintenance Release 1 + FRMCS Baseline 0; ATO Baseline 1 Release 1 | ETCS Baseline 4 Release 1; RMR: GSM-R Baseline 1 Maintenance Release 1 + FRMCS Baseline 0; ATO Baseline 1 Release 1 | ETCS Baseline 4 Release 1; RMR: GSM-R Baseline 1 Maintenance Release 1 + FRMCS Baseline 0; ATO Baseline 1 Release 1 | ETCS Baseline 4 Release 1; RMR: GSM-R Baseline 1 Maintenance Release 1 + FRMCS Baseline 0; ATO Baseline 1 Release 1 |
| --- | --- | --- | --- | --- | | Index No | Reference | Name of Specification | Version | Notes | | 1 | Intentionally deleted | | | | | 2 | Intentionally deleted | | | | | 3 | SUBSET-023 | Glossary of Terms and Abbreviations | 4.0.0 | | | 4 | SUBSET-026 | System Requirements Specification | 4.0.0 | | | 5 | SUBSET-027 | FIS Juridical Recording | 4.0.0 | | | 6 | ERA_ERTMS_015560 | ETCS Driver Machine interface | 4.0.0 | | | 7 | SUBSET-034 | Train Interface FIS | 4.0.0 | | | 8 | SUBSET-035 | Specific Transmission Module FFFIS | 4.0.0 | | | 9 | SUBSET-036 | FFFIS for Eurobalise | 4.0.0 | | | 10a | SUBSET-037-1 | EuroRadio FIS GSM-R – Part 1 [Communication layer and coordination function] | 4.0.0 | | | 10b | SUBSET-037-2 | EuroRadio FIS – Part 2 [Safety layer] | 4.0.0 | | | 10c | SUBSET-037-3 | EuroRadio FIS – Part 3 [FRMCS interface] | 4.0.0 | | | 10d | SUBSET-146 | ERTMS End-to-End Security | 4.0.0 | | | 11 | SUBSET-038 | Offline key management FIS | 4.0.0 | | | 12 | SUBSET-039 | FIS for the RBC/RBC handover | 4.0.0 | | | 13 | SUBSET-040 | Dimensioning and Engineering rules | 4.0.0 | | | 14 | SUBSET-041 | Performance Requirements for Interoperability | 4.0.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 | 4.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 | 4.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 | 4.0.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 on-board reference test facility | 4.0.0 | | | 32 | EIRENE FRS | GSM-R Functional requirements specification | 8.1.0 | Note 7 | | 33 | EIRENE SRS | GSM-R System requirements specification | 16.1.0 | Note 7 | | 34 | A11T6001 | (MORANE) Radio Transmission FFFIS for EuroRadio | 14.0.0 | | | 35 | Intentionally deleted | | | | | 36a | Intentionally deleted | | | | | 36b | Intentionally deleted | | | | | 36c | SUBSET-074-2 | FFFIS STM Test cases document | 4.0.0 | | | 37a | Intentionally deleted | | | | | 37b | SUBSET-076-5-2 | Test cases related to features | 4.0.0 | | | 37c | SUBSET-076-6-3 | Test sequences | 4.0.0 | | | 37d | SUBSET-076-7 | Scope of the test specifications | 4.0.0 | | | 37e | Intentionally deleted | | | | | 38 | EN 16494 | Railway applications. Requirements for ERTMS Trackside Boards | 2025 | | | 39 | SUBSET-092-1 | ERTMS EuroRadio Conformance Requirements | 4.0.0 | | | 40 | SUBSET-092-2 | ERTMS EuroRadio test cases safety layer | 4.0.0 | | | 41 | Intentionally deleted | | | | | 42 | Intentionally deleted | | | | | 43 | SUBSET-085 | Test specification for Eurobalise FFFIS | 4.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 3 | | 49 | SUBSET-059 | Performance requirements for STM | 4.0.0 | | | 50 | SUBSET-103 | Test specification for Euroloop | 1.1.0 | | | 51 | Intentionally deleted | | | | | 52 | SUBSET-058 | FFFIS STM Application layer | 4.0.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 | 4.0.0 | | | 61 | Intentionally deleted | | | | | 62 | Intentionally deleted | | | | | 63 | SUBSET-098 | RBC-RBC Safe Communication Interface | 4.0.0 | | | 64 | EN 301 515 | Global System for Mobile Communication (GSM); Requirements for GSM operation on railways | 3.0.0 | Note 1 | | 65 | TS 102 281 | Detailed requirements for GSM operation on railways | 3.1.1 | Note 2 | | 66 | TS 103 169 | ASCI Options for Interoperability | 1.1.1 | | | 67 | (MORANE) P 38 T 9001 | FFFIS for GSM-R SIM Cards | 6.0.0 | Note 7 | | 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 | | | 70 | (MORANE) F 12 T 6002 | FIS for Confirmation of High Priority Calls | 5 | | | 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 | 5.1 | Note 6 | | 78 | Intentionally deleted | | | Note 5 | | 79 | SUBSET-114 | KMC-ETCS Entity Off-line KM FIS | 4.0.0 | | | 80 | Intentionally deleted | | | Note 4 | | 81 | SUBSET-119 | Train Interface FFFIS | 4.0.0 | | | 82 | SUBSET-120 | Train Interface - Safety requirements | 4.0.0 | | | 83 | SUBSET-137 | On-line Key Management FFFIS | 4.0.0 | | | 84 | SUBSET-125 | ERTMS/ATO System Requirement Specification | 1.1.0 | | | 85 | SUBSET-126 | ATO-OB/ATO-TS FFFIS Application Layer | 1.1.0 | | | 86 | SUBSET-148 | ATO-OB/ATO-TS FFFIS Transport and Security Layers | 1.0.0 | | | 87 | SUBSET-130 | ATO-OB/ETCS-OB FFFIS Application Layer | 1.0.0 | | | 88 | SUBSET-139 | ATO OB/Rolling Stock FFFIS Application Layer | 1.0.0 | | | 89 | SUBSET-143 | Interface Specification Communication Layers for On-board Communication | 1.0.0 | | | 90 | SUBSET-147 | CCS Consist network communication Layers FFFIS | 1.0.0 | | | 91 | Intentionally deleted | | | | | 92 | FFFIS-7950 | FRMCS FFFIS | 1.0.0 | Note 8 | | 93 | FU-7120 | FRMCS FRS | 1.0.0 | Note 9 | | 94 | AT-7800 | FRMCS SRS | 1.0.0 | Note 9 | | 95 | FIS-7970 | FRMCS FIS | 1.0.0 | Note 8 | | 96 | Reserved | [FFFIS for FRMCS profile placeholder] | | | | 97 | Reserved | [FRMCS Test specifications placeholder] | | | | 98 | SUBSET-151 | ATO-OB/ATO-TS Test Specifications | 1.0.0 | | | 99 | TOBA-7510 | On-board FRMCS TOBA FRS | 1.0.0 | Note 9 | | 100 | Intentionally deleted | | | | | 101 | 21E089 | Engineering rules for harmonised marker boards | 2- | | | 102 | 13E154 | ERTMS/ATO Glossary | 2- | | | 103 | TD/011REC1028 | ESC/RSC technical document | Version published in ERA website | | | 104 | SUBSET-153 | ERTMS/ETCS & ERTMS/ATO Exceptions for on-board reduced envelopes of ETCS system versions | 1.0.0 | | | Note 1: 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 2: 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 3: 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 4: 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 5: Information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 6: This document is ETCS, RMR and ATO baseline independent. Note 7: Only the (MI) requirements are mandated by TSI CCS. Note 8: These specifications, as regards to ETCS and ATO on board equipment, shall be fully implemented. Note 9: These specifications, in their current version, as regards to FRMCS on-board equipment, are not considered complete for the purpose of tendering the on-board equipment. | Note 1: 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 2: 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 3: 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 4: 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 5: Information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 6: This document is ETCS, RMR and ATO baseline independent. Note 7: Only the (MI) requirements are mandated by TSI CCS. Note 8: These specifications, as regards to ETCS and ATO on board equipment, shall be fully implemented. Note 9: These specifications, in their current version, as regards to FRMCS on-board equipment, are not considered complete for the purpose of tendering the on-board equipment. | Note 1: 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 2: 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 3: 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 4: 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 5: Information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 6: This document is ETCS, RMR and ATO baseline independent. Note 7: Only the (MI) requirements are mandated by TSI CCS. Note 8: These specifications, as regards to ETCS and ATO on board equipment, shall be fully implemented. Note 9: These specifications, in their current version, as regards to FRMCS on-board equipment, are not considered complete for the purpose of tendering the on-board equipment. | Note 1: 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 2: 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 3: 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 4: 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 5: Information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 6: This document is ETCS, RMR and ATO baseline independent. Note 7: Only the (MI) requirements are mandated by TSI CCS. Note 8: These specifications, as regards to ETCS and ATO on board equipment, shall be fully implemented. Note 9: These specifications, in their current version, as regards to FRMCS on-board equipment, are not considered complete for the purpose of tendering the on-board equipment. | Note 1: 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 2: 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 3: 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 4: 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 5: Information that was intended for index 78 is now incorporated in Index 27 (SUBSET-091). Note 6: This document is ETCS, RMR and ATO baseline independent. Note 7: Only the (MI) requirements are mandated by TSI CCS. Note 8: These specifications, as regards to ETCS and ATO on board equipment, shall be fully implemented. Note 9: These specifications, in their current version, as regards to FRMCS on-board equipment, are not considered complete for the purpose of tendering the on-board equipment. |
Table A 3
List of 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 to the Implementing Regulation (EU) No 402/2013, without prejudice to the points 4 and 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 | 1 |
| A2 | EN 50716 | Railway Applications – Requirements for software development | 2023 | 3 |
| A3 | EN 50129 | Railway applications – Communication, signalling and processing systems – Safety related electronic systems for signalling | 2018 + AC:2019 | 1 |
| A4 | EN 50159 | Railway applications – Communication, signalling and processing systems | 2010 + A1:2020 | 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 | 1, 2 |
| Note 1: This standard is harmonised, see ‘Commission Communication in the framework of the implementation of 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)’ [^E0050] and ‘Commission Implementing Decision (EU) 2020/453 [^E0051] on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community’, where also published editorial corrigenda are indicated. Note 2: To be used in combination with EN 50126-1:2017. Note 3: Previous EN 50128 can still be used according to Table B1.1 and B2 table. | Note 1: This standard is harmonised, see ‘Commission Communication in the framework of the implementation of 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)’ [^E0050] and ‘Commission Implementing Decision (EU) 2020/453 [^E0051] on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community’, where also published editorial corrigenda are indicated. Note 2: To be used in combination with EN 50126-1:2017. Note 3: Previous EN 50128 can still be used according to Table B1.1 and B2 table. | Note 1: This standard is harmonised, see ‘Commission Communication in the framework of the implementation of 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)’ [^E0050] and ‘Commission Implementing Decision (EU) 2020/453 [^E0051] on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community’, where also published editorial corrigenda are indicated. Note 2: To be used in combination with EN 50126-1:2017. Note 3: Previous EN 50128 can still be used according to Table B1.1 and B2 table. | Note 1: This standard is harmonised, see ‘Commission Communication in the framework of the implementation of 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)’ [^E0050] and ‘Commission Implementing Decision (EU) 2020/453 [^E0051] on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community’, where also published editorial corrigenda are indicated. Note 2: To be used in combination with EN 50126-1:2017. Note 3: Previous EN 50128 can still be used according to Table B1.1 and B2 table. | Note 1: This standard is harmonised, see ‘Commission Communication in the framework of the implementation of 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)’ [^E0050] and ‘Commission Implementing Decision (EU) 2020/453 [^E0051] on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community’, where also published editorial corrigenda are indicated. Note 2: To be used in combination with EN 50126-1:2017. Note 3: Previous EN 50128 can still be used according to Table B1.1 and B2 table. |
OJ C 282, 10.8.2018.
[^E0051]: (2)
Commission Implementing Decision (EU) 2020/453 of 27 March 2020 on the harmonised standards for railway products drafted in support of Directive 2008/57/EC of the European Parliament and of the Council on the interoperability of the rail system within the Community (OJ L 95, 30.3.2020, ELI: http://data.europa.eu/eli/dec_impl/2020/453/oj).
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 | |
Appendix B
B1. Changes of requirements and transition regimes for On-Board Subsystems
The notified body shall apply point 7.2.4.1 when issuing the EC type or design examination certificate.
Table B1.1
Transition regime [^E0052] for CCS On-Board Subsystem
| No | TSI point(s) | TSI point(s) in previous version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Transition regime | Transition regime | Transition regime | Transition regime | |||
|---|---|---|---|---|---|---|---|---|---|---|
| No | TSI point(s) | TSI point(s) in previous version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Design phase started after 28 September 2023 | Design phase started before 28 September 2023 | Production phase | Vehicle in operation | |||
| CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | CCS On-Board Error corrections | |||
| 1 | TSI point(s) | TSI point(s) in previous version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Appendix A + point 7.2.10.3 | No mandatory implementation of error corrections published in technical opinions | CCS Subsystems with mandatory implementation of registered error corrections for functionality ETCS up to system version 2.1 and GSM-R. | For legal releases (with maintenance of specifications) published before 1 June 2026: If one or more registered errors in RINF are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the necessary error corrections at the latest 6 months after the update of the concerned interoperability constituents. Note: If one or more registered errors in RINF are identified for the area of use for which no new authorisation is required, the CCS subsystem integrated into a vehicle type is considered compliant with the update of the concerned interoperability constituents (as defined in Table B3). | For legal releases (with maintenance of specifications) published before 1 June 2026: If one or more registered errors in RINF are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the necessary error corrections at the latest 6 months after the update of the concerned interoperability constituents. Note: If one or more registered errors in RINF are identified for the area of use for which no new authorisation is required, the CCS subsystem integrated into a vehicle type is considered compliant with the update of the concerned interoperability constituents (as defined in Table B3). | For legal releases (with maintenance of specifications) published before 1 June 2026: If one or more registered errors in RINF are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the necessary error corrections the latest — 1 year after the update of the concerned interoperability constituents (as defined in Table B3) in the case no new authorisation is required; or — 1 year after the update of the vehicle type in the case a new authorisation is required. | For legal releases (with maintenance of specifications) published before 1 June 2026: If one or more registered errors in RINF are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the necessary error corrections the latest — 1 year after the update of the concerned interoperability constituents (as defined in Table B3) in the case no new authorisation is required; or — 1 year after the update of the vehicle type in the case a new authorisation is required. |
| For legal releases (with maintenance of specifications) published after 1 June 2026: If one or more registered errors in RINF are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the full maintenance package of error corrections at the latest 6 months after the update of the concerned interoperability constituents. Note: If one or more registered errors in RINF are identified for the area of use for which no new authorisation is required, the CCS subsystem integrated into a vehicle type is considered compliant with the update of the concerned interoperability constituents (as defined in Table B3). | For legal releases (with maintenance of specifications) published after 1 June 2026: If one or more registered errors in RINF are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the full maintenance package of error corrections at the latest 6 months after the update of the concerned interoperability constituents. Note: If one or more registered errors in RINF are identified for the area of use for which no new authorisation is required, the CCS subsystem integrated into a vehicle type is considered compliant with the update of the concerned interoperability constituents (as defined in Table B3). | For legal releases (with maintenance of specifications) published after 1 June 2026: If one or more registered errors in RINF are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the full maintenance package of error corrections the latest — 1 year after the update of the concerned interoperability constituents (as defined in Table B3) in the case no new authorisation is required; or — 1 year after the update of the vehicle type in the case a new authorisation is required. | For legal releases (with maintenance of specifications) published after 1 June 2026: If one or more registered errors in RINF are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the full maintenance package of error corrections the latest — 1 year after the update of the concerned interoperability constituents (as defined in Table B3) in the case no new authorisation is required; or — 1 year after the update of the vehicle type in the case a new authorisation is required. | |||||||
| ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | ETCS On-Board implementation | |||
| 2 | Points 7.4.2.1, and 7.4.3 | 7.4.2.1.2. and 7.4.3(2) grants exemptions for new vehicles to be equipped with ETCS | 7.4.2.1.2. and point 7.4.3(2) deleted. All newly built vehicles shall be equipped with ETCS. | Directly applicable Note: Design phase started after 28 September 2023 here relates to ‘RST design phase’ for any vehicles without ETCS. For special vehicles applicable from 1 January 2026 unless Member States have issued decisions in accordance with 7.4.3.2. | Applicable if design phase ends on or after 1 January 2028 Note: Design phase started before 28 September 2023 here relates to ‘RST design phase’ for any vehicles without ETCS. For special vehicles applicable if design phase ends on or after 1 January 2030 unless Member States have issued decisions in accordance with 7.4.3.2. | Applicable for newly built vehicles placed on the market on or after 1 January 2030 For special vehicles applicable for newly built vehicles placed on the market on or after 1 January 2030 unless Member States have issued decisions in accordance with 7.4.3.2. | Not applicable | |||
| 3 | Points 7.4.2.2 and 7.4.3. | 7.4.2.2 only applicable to upgrade of existing high-speed vehicles | 7.4.2.2 applicable to vehicle type and/or vehicles requiring a new authorisation | Directly applicable For special vehicles applicable unless Member States have issued decisions in accordance with 7.4.3.2: — if design phase starts on or after 1 January 2026; or — if design phase ends on or after 1 January 2030. | Applicable if design phase ends on or after 1 January 2028 Note: Remains directly applicable to high-speed vehicles according to previous CCS TSI. For special vehicles applicable if design phase ends on or after 1 January 2030 unless Member States have issued decisions in accordance with 7.4.3.2. | Not applicable Note: Remains directly applicable to high-speed vehicles according to previous CCS TSI. | Not applicable | |||
| 4 | Point 7.4.2.3 (3) | 7.4.2.4 extension area of use: exemptions to install ETCS in point (3) | 7.4.2.3 extension area of use: exemptions deleted in point (3) Note: the implementation requirements of CCS TSI established by Regulation (EU) 2016/919 in 7.4.2.4 point (3) remain directly applicable. | Not applicable | Not applicable | Not applicable | Applicable from 1 January 2030, if the installation of ETCS is indicated in RINF for the subsequent five years in the new area of use or if the area of use is at least three Member States | |||
| ETCS system versions | ETCS system versions | ETCS system versions | ETCS system versions | ETCS system versions | ETCS system versions | ETCS system versions | ETCS system versions | |||
| 5 | Intentionally deleted | |||||||||
| 6 | Appendix A – 7.4.2.4.1 and 7.4.2.4.2 for envelope of legally operated ETCS system versions from 1.0 up to 2.2. | Not applicable | On-board implementation of notified ETCS functions from system version 2.2. | Design phase started on or after notification from IM and notification is done on or after 1 January 2025: the ETCS system version 2.2 is directly applicable. | The ETCS system version 2.2 is applicable if the design phase is not ended within the latest date between following dates: — 1 January 2030; — 5 years after the date of the notification provided by the IM. | Not applicable | Not applicable | |||
| Design phase started before notification from IM or notification is done before 1 January 2025: the ETCS system version 2.2 is applicable if the design phase is not ended within the latest date between following dates: — 1 January 2030; — 5 years after the notification date from the IM. | ||||||||||
| 7 | Appendix A – 7.4.2.4.1, 7.4.2.4.2 and 7.4.1.3 for envelope of legally operated ETCS system versions from 1.0 up to 3.0 | Not applicable | On-board implementation of notified ETCS functions from system version 3.0 [^E0053]. | Not applicable. Note: Transition regime after entry into force of CCS TSI amendment [^E0054]: Design phase started after notification from IM and notification is done 2 years after entry into force of the CCS TSI amendment: the ETCS system version 3.0 is directly applicable. | Not applicable. Note: Transition regime after entry into force of CCS TSI amendment [^E0054]: The ETCS system version 3.0 is applicable if the design phase has not ended within the latest date between following dates: — 5 years after entry into force of the CCS TSI amendment containing the harmonised FRMCS specifications; — 5 years after the day of the notification provided by the IM. | Not applicable. Note: Transition regime after entry into force of CCS TSI amendment [^E0054]: the notified ETCS system version 3.0 is mandatory when required for compatibility with the ETCS trackside implementation of ETCS TS 3.0. | Not applicable. Note: Transition regime after entry into force of CCS TSI amendment [^E0054]: the notified ETCS system version 3.0 is mandatory when required for compatibility with the ETCS trackside implementation of ETCS TS 3.0. | |||
| Design phase started before notification from IM or notification is done before entry into force of CCS TSI amendment: see transition regime in column ‘Design phase started before 28 September 2023’. | ||||||||||
| 8 | Intentionally deleted | |||||||||
| Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | Former sets of specifications #2 and #3 | |||
| 9 | Appendix A – Table A 1 and Table A 2 7.4.2.4.1 and 7.4.2.4.2 7.4.2.3 (7) | Annex A – Table A 1 – Table A 2 2 – Set of specification #2 The minimum reduced on-board envelope is the envelope up to ETCS system version 2.0. | The specifications in Appendix A – Table A 1 and Table A 2 does not include ETCS system version 2.0, since the minimum reduced on-board envelope is the envelope up to ETCS system version 2.1. | Applicable — if design phase starts on or after 28 September 2026; or — if design phase ends on or after 1 January 2030. In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Applicable if design phase ends on or after 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Applicable on newly built vehicles placed on the market from 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Not applicable In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | |||
| 10 | Appendix A – Table A 1 and Table A 2 | Annex A – Table A 1 and Table A 2 3 – Set of specification #3 | The specifications in Appendix A - Table A 1 and Table A 2 have the agreed error corrected version of former set #3 | Applicable — if design phase starts on or after 28 September 2026; or — if design phase ends on or after 1 January 2030. In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Applicable if design phase ends on or after 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Applicable on newly built vehicles placed on the market from 1 January 2032 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | Not applicable In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. | |||
| CMD | CMD | CMD | CMD | CMD | CMD | CMD | CMD | |||
| 11 | 4.2.2 (b) – Cold Movement Detection | CMD Optional | CMD Mandatory | Directly applicable when ETCS is installed for the first time into a vehicle design. | Applicable if design phase ends after 1 January 2028 when ETCS is installed for the first time into a vehicle design. | Applicable on newly built vehicles placed on the market from 1 January 2030. | Not applicable | |||
| ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | ATO On-Board Implementation | |||
| 12 | 4.2.18 + Point 7.2.9.2 | Not applicable | ATO on-board specification and implementation requirements | Design phase started on or after notification from IM and notification is done on or after 1 January 2025: ATO on-board requirements are directly applicable. Design phase started before notification from IM or notification is done before 1 January 2025: ATO On-board requirements are applicable if the design phase is not ended within the latest date between following dates: — 1 January 2030; — 5 years after the notification date from the IM. | ATO on-board requirements are applicable if the design phase is not ended within the latest date between following dates: — 1 January 2030; — 5 years after the day of the notification provided by the the IM. | Not applicable | Not applicable | |||
| CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | CCS On-Board Modularity | |||
| 13 | 4.2.6.5.1 CCS Consist network communication layers Index 90 + point 5.2.2.2 | Not applicable | Mandatory implementation of Ethernet based platform New requirement in case of grouping of Interoperability Constituents defined in Table 5.1 | Applicable on newly developed vehicle designs requiring first authorisation — if design phase starts on or after 28 September 2025; or — if design phase ends on or after 28 September 2030. | Applicable on newly developed vehicle designs requiring first authorisation if design phase ends on or after 28 September 2030 | Not applicable | Not applicable | |||
| 14 | 4.2.2.2(7)-4.2.18 (3) Forwarding information/orders and receiving state information from rolling stock: 4.2.6.5.1 CCS Consist network communication layers Appendix A – CCS and RST interfaces Indexes 81, 82, 88, 90 | Not applicable | Mandatory implementation of on-board interfaces between CCS subsystem and RST subsystem | Applicable on newly developed vehicle designs requiring first authorisation — if design phase starts on or after 28 September 2025; or — if design phase ends on or after 28 September 2030. | Applicable on newly developed vehicle designs requiring first authorisation if design phase ends on or after 28 September 2030 | Not applicable | Not applicable | |||
| FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | FRMCS On-Board implementation: | |||
| 15 | Point 7.3.2.2 | Not applicable | FRMCS on-board implementation (3) | Not applicable. Note: Transition regime after TSI amendment: Design phase started after notification from IM and notification is done after 2 years of the entry into force of CCS TSI amendment: FRMCS on-board implementation is directly applicable. | Not applicable. Note: Transition regime after TSI amendment: FRMCS on-board is applicable if the design phase is not ended within the latest date between following dates: — 5 years after the CCS TSI amendment containing the FRMCS specifications; — 5 years after the day of the notification provided by the IM. | Not applicable. Note: The FRMCS on-board implementation is mandatory when required for compatibility with FRMCS only trackside implementation | Not applicable. Note: The FRMCS on-board implementation is mandatory when required for compatibility with FRMCS only trackside implementation | |||
| Design phase started before notification from IM: see transition regime in column ‘Design phase started before before 28 September 2023’. | ||||||||||
| Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | |||
| 16 | Point 6.1.1.2 | Points 6.1.1.3 and 6.4.3 are deleted. | With respect to 6.1.1.2 it is no longer possible to exclude mandatory functionalities, interfaces or performance except if listed in Appendix G. | Applicable — if design phase ends on or after 28 September 2030 In cases of partial fulfilment, a condition for use shall be included when authorising vehicles to be placed on the market, enforcing compliance at the next upgrade of the vehicle train protection part. Functions included in system versions 2.2 and 3.0 which are not implemented due to partial fulfilment and which are not essential for the intended area of use, shall be implemented at the earliest occurrence of one of the following: (a) At the next reauthorisation resulting from another change to the vehicle train protection (ETCS) system; (b) At the next upgrade to a higher system version of the ETCS train protection part. | Applicable — if design phase ends on or after 28 September 2030 In cases of partial fulfilment, a condition for use shall be included when authorising vehicles to be placed on the market, enforcing compliance at the next upgrade of the vehicle train protection part. Functions included in system versions 2.2 and 3.0 which are not implemented due to partial fulfilment and which are not essential for the intended area of use, shall be implemented at the earliest occurrence of one of the following: (a) At the next reauthorisation resulting from another change to the vehicle train protection (ETCS) system; (b) At the next upgrade to a higher system version of the ETCS train protection part. | Not applicable | Not applicable | |||
| DMI indication translation | DMI indication translation | DMI indication translation | DMI indication translation | DMI indication translation | DMI indication translation | DMI indication translation | DMI indication translation | |||
| 17 | Appendix E | No mandatory harmonised translation of DMI indications | Harmonised translation of DMI indications. | Directly applicable | Applicable if design phase ends on or after 28 September 2030. | Not applicable | Not applicable | |||
| ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | ESC/RSC Statements | |||
| 18 | 4.2.17 ETCS and radio system compatibility 6.2.4.3 ETCS and radio system compatibility checks for interoperability constituent 6.3.3.1 ETCS and radio system compatibility checks | First version of the requirements for ESC/RSC Statements. | Updated requirements for assessment of ESC/RSC Statements, including the ESC/RSC IC Statement. | Applicable if design phase ends after 28 March 2024. | Applicable if design phase ends after 28 March 2024. | Not applicable | Not applicable | |||
| System identifier | System identifier | System identifier | System identifier | System identifier | System identifier | System identifier | System identifier | |||
| 19 | 4.2.20.3 System identifier Table 6.2.1, row 2d | Not applicable | NoBo check for system identifier. | Applicable if design phase ends after 28 March 2024. | Applicable if design phase ends after 28 March 2024. | Not applicable | Not applicable | |||
| Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | Subsystem certificate and integration between parts | |||
| 20 | 4.2.6 On-board interfaces internal to CCS. Table 6.2.1, row 3 6.4 Provisions in cases of partial assessment of TSI requirements | Not explicitly addressed in the table. | Integration between parts of the subsystem. Structure of the subsystem certificates Note: Not a new requirement but clarification. | Directly applicable | Directly applicable | Not applicable | Not applicable | |||
| Appendix D template | Appendix D template | Appendix D template | Appendix D template | Appendix D template | Appendix D template | Appendix D template | Appendix D template | |||
| 21 | 6.5.1 Content of EC certificates 6.5.2 Content of EC declarations | Not applicable | Mandatory use of the Appendix D template in EC certificates and EC declarations. | Applicable if design phase ends after 28 March 2024. | Applicable if design phase ends after 28 March 2024. | Not applicable | Not applicable | |||
| Specific cases | Specific cases | Specific cases | Specific cases | Specific cases | Specific cases | Specific cases | Specific cases | |||
| 22 | Point 7.7.2 7.7.2.9 Italy 7.7.2.12 Ireland 7.7.2.14 Austria | 7.6.2 Previous version of specific cases. | Update of specific cases by introducing new requirements for the CCS on-board subsystem for certain Member States. | Directly applicable | Directly applicable | Applicable for newly built vehicles placed on the market as of 1 January 2030 | Not applicable | |||
| Standards | Standards | Standards | Standards | Standards | Standards | Standards | Standards | |||
| 23 | Appendix A Table A3 | Annex A Table A3 | New standard EN50716 has superseded EN50128 | Directly applicable | Applicable if design phase ends after 30th October 2026 | Not applicable | Not applicable |
Definition of phases provided in point 7.2.4.1.1.
Note: If a Member State has agreed with stakeholders to implement the new ETCS system version 3.0 after entry into force of the CCS TSI amendment (see clause 7.4.4), the IM shall notify the dates when the ETCS on-board system version 3.0 becomes a mandatory on-board requirement according to clause 7.4.1.3. All vehicles using these lines shall be required to implement the ETCS on-board system version 3.0.
This concerns the new legal release of the CCS TSI with FRMCS Baseline 1 Release 1.
[^E0055]: (4)
Note: If a Member State has agreed with stakeholders to implement FRMCS (see clause 7.4.4), the IM shall notify the dates when the FRMCS on-board system becomes a mandatory on-board requirement according to clause 7.3.1. All vehicles using these lines shall be required to implement the FRMCS on-board system.
Table B1.1b
Transition regime for CCS On-Board Subsystem
| No | TSI point(s) | TSI point(s) in the version before the change introduced by Implementing Regulation (EU) 2026/693 | Explanation on CCS TSI change introduced by Implementing Regulation (EU) 2026/693 | Transition regime | Transition regime | Transition regime | Transition regime | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | No | TSI point(s) | TSI point(s) in the version before the change introduced by Implementing Regulation (EU) 2026/693 | Explanation on CCS TSI change introduced by Implementing Regulation (EU) 2026/693 | Design phase started after 5 May 2026 | Design phase started before 5 May 2026 | Production phase | Vehicle in operation | | | | | Test specifications | Test specifications | Test specifications | Test specifications | Test specifications | Test specifications | Test specifications | Test specifications | | | | | 1 | TSI point(s) | TSI point(s) in the version before the change introduced by Implementing Regulation (EU) 2026/693 | Explanation on CCS TSI change introduced by Implementing Regulation (EU) 2026/693 | Appendix A, Table A 2, Index 98 | Index 98 was reserved. | The final version of the document is included. | Applicable if design phase ends after 1 January 2026 if ATO part (ATO Baseline 1 Release 1) is implemented. | Applicable if design phase ends after 1 January 2026 if ATO part (ATO Baseline 1 Release 1) is implemented. | Not applicable | Not applicable | | Reduced envelopes | Reduced envelopes | Reduced envelopes | Reduced envelopes | Reduced envelopes | Reduced envelopes | Reduced envelopes | Reduced envelopes | | | | | 2 | Appendix A, Table A 2, Indexes 104, 84, 85 | Index 104 was reserved. ATO on-board implementation based on index 84, 85 v1.0.0. | The final version of the document is included, and second row from Appendix G is removed. Table A1 references to index 104 are completed were necessary. ATO on-board implementation based on index 84, 85 v1.1.0. | Applicable if design phase ends after 1 January 2026 if ETCS Baseline 4 Release 1 or ATO Baseline 1 Release 1 is implemented. | Applicable if design phase ends after 1 January 2026 if ETCS Baseline 4 Release 1 or ATO Baseline 1 Release 1 is implemented. | Not applicable | Not applicable | | | | | DMI Indication translations | DMI Indication translations | DMI Indication translations | DMI Indication translations | DMI Indication translations | DMI Indication translations | DMI Indication translations | DMI Indication translations | | | | | 3 | Appendix E | Appendix E | Addition of missing terms | Same as Table B1.1, row 17 | Same as Table B1.1, row 17 | Same as Table B1.1, row 17 | Same as Table B1.1, row 17 | | | | | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | | | | | 4 | Appendix B. Table B1.1 | Appendix B, Table B1.1 clarifications | Clarifications and corrections regarding transition regime. | Directly applicable | Directly applicable | Directly applicable | Directly applicable | | | |
Table B1.2
Transition regime [^E0056] for RST Subsystem
| No | TSI point(s) | TSI point(s) in the version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Transition regime | Transition regime | Transition regime | Transition regime |
|---|---|---|---|---|---|---|---|
| No | TSI point(s) | TSI point(s) in the version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Design phase started after 28 September 2025 | Design phase started before 28 September 2025 | Production phase | Vehicle in operation |
| 1 | Index 77 | V4 – Frequency management not fully defined for the vehicle | V5 – Frequency management fully defined for the vehicle | Directly applicable with the exception of point 3.2.2. This point is applicable to newly developed vehicle designs requiring first authorisation as defined in Article 14(1)(a) of Commission Implementing Regulation (EU) 2018/545 if design phase starts on or after 28 September 2025 or if design phase ends on or after 28 September 2030; Applicable to modified vehicle designs requiring new authorisation as defined in Article 14(1)(d) of Commission Implementing Regulation (EU) 2018/545 if design phase ends on or after 28 September 2030. | Applicable if design phase ends on or after 28 September 2030. | Not applicable | Not applicable |
| 2 | Point 7.7.2 7.7.2.5 Lithuania, Latvia and Estonia 7.7.2.7 Luxembourg 7.7.2.9 Italy 7.7.2.12 Ireland 7.7.2.13 Bulgaria | 7.6.2 Previous version of specific cases. | Update of specific cases by introducing new requirements for the RST subsystem for certain Member States. | Directly applicable. | Applicable if design phase ends on or after 28 September 2030. | Not applicable | Not applicable |
[^E0056]: (1)
Definition of phases provided in point 7.2.4.1.1.
Table B1.2b
Transition regime for RST Subsystem
| No | TSI point(s) | TSI point(s) in previous version established by Regulation (EU) 2023/1695 | Explanation on CCS TSI change in Regulation (EU) 2026/693 | Transition regime | Transition regime | Transition regime | Transition regime |
| --- | --- | --- | --- | --- | --- | --- | --- | | No | TSI point(s) | TSI point(s) in previous version established by Regulation (EU) 2023/1695 | Explanation on CCS TSI change in Regulation (EU) 2026/693 | Design phase started after 5 May 2026 | Design phase started before 5 May 2026 | Production phase | Vehicle in operation | | 1 | Appendix B, Table B1.2 | Appendix B, Table B1.2 clarifications | Clarifications and corrections regarding transition regime. | Directly applicable | Directly applicable | Directly applicable | Directly applicable |
B2. Changes of requirements and transition regimes for CCS Trackside Subsystem
The notified body shall apply point 7.2.4.2 and 7.4.1.2 when issuing the EC type or design examination certificate.
Table B2
Transition regime for CCS Trackside Subsystem
| No | TSI point(s) | TSI point(s) in the version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Transition regime |
| --- | --- | --- | --- | --- | | CCS Trackside Error Corrections | CCS Trackside Error Corrections | CCS Trackside Error Corrections | CCS Trackside Error Corrections | CCS Trackside Error Corrections | | 1 | Appendix A + Points 7.4.1.2 and 7.2.10.3 | Set 1, 2 and 3 of specifications without error corrections | Table A2 includes the maintenance of the functions into 1 set of specifications. | CCS Trackside Subsystems, which are in advanced stage of development or in operation, shall implement the identified set of corrections for the unacceptable errors as described in point 7.2.10.1 within: — 2 years and 6 months after the publication by the Agency of the Baseline Compatibility Analysis (BCA) including the answers to the questionnaires in case no new authorisation is required: — 3 years after the publication by the Agency of the Baseline Compatibility Analysis (BCA) including the answers to the questionnaires in case a new authorisation is required: CCS Trackside Subsystems placed into service after 28 September 2023, which are not in advanced stage of development, shall directly comply with the maintained set of specifications of this TSI. | | CCS Trackside Enhancements | CCS Trackside Enhancements | CCS Trackside Enhancements | CCS Trackside Enhancements | CCS Trackside Enhancements | | 2 | ETCS: Appendix A; + point 7.4.1.3 | Not applicable | New ETCS functions from system version 2.2 to 3.0 | If implemented (optional trackside function), directly applicable for ETCS equipped lines | | 3 | ETCS: Point 4.2.1 Table 6.3 row 3 Appendix A; Table A.2 – Index 38, 101 | Marker-board definition based on 06E068 | EN 16494 and engineering rules for harmonised marker boards | Directly applicable if: — installing marker boards for the first time on a line on which ERTMS is being deployed (and is not in an advanced stage of development), even if a Class B system is also being installed at the same time; or — installing marker boards during a renewal or upgrade (which is not in an advanced stage of development) of the infrastructure subsystem on a line on which ERTMS has been deployed. Detailed provisions concerning the requirements for fitting harmonised marker boards are set out in Appendix A, Table A.2, Index 101. | | 4 | 4.2.19 | No specifications | ATO Trackside Implementation | If implemented (optional trackside function), directly applicable for ATO GoA1/2 implementation on ETCS equipped lines | | 5 | FRMCS radio system | No specifications | New set of FRMCS specifications | If implemented (optional trackside function), directly applicable for FRMCS projects when FRMCS specifications are completed and published with an amendment of this CCS TSI. | | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | Partial fulfilment: | | 6 | Not applicable | Points 6.1.1.3 and 6.4.3 are deleted. | When implemented, all functions, performance and interfaces or performance shall comply with the Chapter 4 (including the specifications referred to in Appendix A). | After the 28 September 2030. | | Former set of specifications set #1, #2 and #3 | Former set of specifications set #1, #2 and #3 | Former set of specifications set #1, #2 and #3 | Former set of specifications set #1, #2 and #3 | Former set of specifications set #1, #2 and #3 | | 7 | Appendix A - Table A 2 | Annex A - Table A 2 1 – Set of specification #1, Table A 2 2 – Set of specification #2 Table A 2 3 – Set of specification #3 | Table A 2 includes the maintenance of the functions into 1 set of specifications. | Requirements and deadlines defined in point 7.4.1.2. ‘Set of specifications from previous versions of the CCS TSI.’ of ANNEX I of this TSI. | | Standards | Standards | Standards | Standards | Standards | | 8 | Appendix A 3 | Annex A - Table A 3 | New standard EN50716 has superseded EN50128 | After the 30 October 2026. | | ESC/RSC definitions | ESC/RSC definitions | ESC/RSC definitions | ESC/RSC definitions | ESC/RSC definitions | | 9 | 4.2.17 ETCS and radio system compatibility Table 6.3, Row 10 | Agency analysis of IM submissions. | NoBo assessment of new or updated ESC/RSC definition | Applicable since 28 September 2024. | | System identifier | System identifier | System identifier | System identifier | System identifier | | 10 | 4.2.20.3 System identifier Table 6.3, row 2e | Not applicable | Check for system identifier | Applicable since 28 March 2024. | | Appendix D template | Appendix D template | Appendix D template | Appendix D template | Appendix D template | | 1 | 6.5.1 Content of EC certificates 6.5.2 Content of EC declarations | Not applicable | Mandatory use of Appendix D template. | Applicable since 28 March 2024. |
Table B2b
Transition regime for CCS Trackside Subsystem
| No | TSI point(s) | TSI point(s) in the version before the change introduced by Implementing Regulation (EU) 2026/693 | Explanation on CCS TSI change introduced by Implementing Regulation (EU) 2026/693 | Transition regime for TSI changes introduced by Implementing Regulation 2026/693 |
| --- | --- | --- | --- | --- | | Test specifications | Test specifications | Test specifications | Test specifications | Test specifications | | 1 | Appendix A, Table A 2, Index 98 | Index 98 was reserved. | The final version of the document is included. | Applicable as of 1 January 2026 if ATO part (ATO Baseline 1 Release 1) is implemented. | | ATO | ATO | ATO | ATO | ATO | | 2 | 4.2.19 | ATO Trackside implementation based on indexes 84, 85 v1.0.0 | ATO Trackside implementation based on indexes 84, 85 v1.1.0 | Applicable as of 1 January 2026 if ATO part (ATO Baseline 1 Release 1) is implemented. | | Harmonised Marker Boards | Harmonised Marker Boards | Harmonised Marker Boards | Harmonised Marker Boards | Harmonised Marker Boards | | 3 | ETCS: Appendix A, Table A.2, Indexes 38, 101 | EN 16494 2015 and engineering rules for harmonised marker boards v1- | EN 16494 2025 and engineering rules for harmonised marker boards v2- | Directly applicable if: — installing marker boards for the first time on a line on which ERTMS is being deployed (and is not in an advanced stage of development), even if a Class B system is also being installed at the same time; or — installing marker boards during a renewal or upgrade (which is not in an advanced stage of development) of the infrastructure subsystem on a line on which ERTMS has been deployed. Detailed provisions concerning the requirements for fitting harmonised marker boards are set out in Appendix A, Table A.2, Index 101. | | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | Transition regime clarification | | 4 | Appendix B, Table B2 | Appendix B, Table B2 clarifications | Clarifications and corrections regarding the transition regime. | Directly applicable |
B3. Changes of Interoperability Constituent requirements and transition regimes for CCS Subsystem
The notified body shall apply point 7.2.4.3 when issuing the EC type or design examination certificate.
- 7.2.4.3.Transition periods defined for CCS Subsystems are applicable for the Interoperability Constituents unless specified otherwise in these tables.
Table B3
Transition regime for CCS Interoperability Constituents
| No | TSI point(s) | TSI point(s) in the version established by Regulation (EU) 2016/919 | Explanation on CCS TSI change introduced by this Regulation | Transition regime |
| --- | --- | --- | --- | --- | | 1 | Appendix A + point 4.2.20.1 + point 7.2.10.2 | Technical opinions on Art. 10 errors are not legally binding | Implementation of error corrections into ERTMS on-board Interoperability Constituents for existing CCS subsystems for functionality ETCS up to system version 2.1 and GSM-R. | If one or more registered errors are identified for the area of use specified in the authorisation of the vehicle: (a) for legal releases (with error correction specifications) published before 1 January 2026: ERTMS on-board Interoperability Constituents integrated into a vehicle shall implement the necessary error corrections within the area of use specified in the authorisation, the latest 18 months after the registration in RINF of the applicable CR; (b) for legal releases (with error correction specifications) published after 1 January 2026 onwards: ERTMS on-board Interoperability Constituents integrated into a vehicle shall comply with the maintained set of specifications of this TSI 18 months after the registration in RINF of the applicable CR. This transition regime can be handled flexibly in agreement with the applicant for the EC verification of the on-board subsystem and the railway undertaking as long as the overall transition regime (as per Table B1.1 plus as per Table B3) is met. Note: If no errors are registered for the concerned area of use, error corrections will be mandatory implemented according to the transition regime linked to the point of partial fulfilment. | | 2 | Appendix A + point 4.2.20.1 + point 7.2.10.2 | Technical opinions on Art. 10 errors are not legally binding | Implementation of error corrections into ERTMS Trackside Interoperability Constituents for new CCS trackside projects for functionality, ETCS up to system version 2.1 and GSM-R. | ERTMS Trackside Interoperability Constituents, integrated into a CCS Trackside Subsystem for which the project is not in advanced stage of development, shall directly comply with the maintained set of specifications of this TSI. | | 3 | Appendix A + point 4.2.20.1 + point 7.2.10.2 | Technical opinions on Art. 10 errors are not legally binding | Implementation of error corrections into ERTMS Trackside Interoperability Constituents for existing CCS trackside projects (i.e. trackside subsystem in advanced stage of deployment or in operations) | ERTMS Trackside Interoperability Constituents, integrated into a CCS Trackside Subsystem for which the project is in advanced stage of development or being integrated in a CCS Trackside Subsystem in operation, shall implement the identified set of corrections for the unacceptable trackside errors within 2 years after the latest date between the entry into force of the TSI and the publication by the Agency of the Baseline Compatibility Analysis (BCA) including the answers to the questionnaires. | | 4 | Appendix A, Table A.2 Index 90, 92 + 5.2.2.2 + 4.2.2.2 (7) + 4.2.6 | N/A | Implementation of Ethernet based communication for integration with ATO On-Board IC and FRMCS On-Board IC | New ETCS On-Board Interoperability Constituents placed on the market within 2 years after entry into force of the TSI shall implement the Ethernet based connections required for ATO and FRMCS interfacing as specified in Index 90 (points 3.1.1.2 and 3.1.1.3) and as specified in Index 92 (point 7.2) | | 5 | 4.2.20.3 System identifier Table 5.1 row 1, 4, 5, 6. Table 5.2 row 1, 2, 3, 4, 5, 6. | Not applicable | NoBo check for system identifier. | Applicable since 28 March 2024. | | 6 | 6.5.1 Content of EC certificates 6.5.2 Content of EC declarations | Not applicable | Mandatory use of the Appendix D template. | Applicable since 28 March 2024. |
Table B3b
Transition regime for CCS Interoperability Constituents
| No | TSI point(s) | TSI point(s) in the version before the change introduced by Implementing Regulation (EU) 2023/1695 | Explanation on CCS TSI change introduced by Implementing Regulation (EU) 2023/1695 | Transition regime for TSI changes introduced by Implementing Regulation (EU) 2026/693 |
| --- | --- | --- | --- | --- | | 1 | Appendix B, Table B3 | Appendix B , Table B3 clarifications | Clarifications and corrections regarding the transition regime. | Directly applicable | | 2 | Appendix A, Table A 2, Indexes 31, 37b, 37c and 37d. | Appendix A, Table A 2, Indexes 31, 37b, 37c and 37d. | The updated versions of the document are included. | Applicable as of the latest 1 July 2026 or the availability of the new version Subset 76 as an Agency Thechnical Opinion | | 3 | Appendix A Table index 104 | Appendix A Table index 104 | Updated version of the document is included | Applicable six months after EiF |
Appendix C
In this appendix the templates for the different ESC/RSC (Interoperability Constituent) Statement are provided.
Appendix C.1: ESC Statement template
TEMPLATE FOR ETCS SYSTEM COMPATIBILITY STATEMENT
ETCS SYSTEM COMPATIBILITY STATEMENT
ETCS System Compatibility Statement document [Document number] ([^E0057])
We, Applicant:
[Business name]
[Complete postal Address]
Declare under our sole responsibility that the following subsystem ([^E0058]):
[Name/short description of the subsystem, relevant configuration, unique identification of the subsystem]
to which this statement refers has been subject to the relevant verifications that corresponds to the following ESC Type(s):
[Reference to: ESC Type Identifiers as published in the Agency Technical Document]
has been assessed by the following Notified body:
[Business name]
[Registration number]
[Full address]
In accordance with the following report(s):
[Report(s) number(s), date(s) of issue]
The following conditions of use and other restrictions apply ([^E0059]) ([^E0060]):
[Reference to document with the list of conditions of use and other restrictions]
The following ESC Interoperability Constituent Statements has been considered:
[Indicate use of ESC Interoperability Constituent Statements]
Reference to former ETCS System Compatibility Statement (where applicable)
[Yes/No]
Done on:
[date DD/MM/YYYY]
Signature of Applicant:
[First Name, Surname]
Appendix C.2: ESC Interoperability Constituent Statement template
TEMPLATE FOR ESC STATEMENT FOR INTEROPERABILITY CONSTITUENT
ESC STATEMENT FOR INTEROPERABILITY CONSTITUENT
ETCS System Compatibility Statement document for the Interoperability Constituent [Document number] ([^E0061])
We, Applicant:
[Business name]
[Complete postal Address]
Declare under our sole responsibility that the following Interoperability Constituent ([^E0062]):
[Name/short description of the interoperability constituent, relevant configuration, unique identification of the interoperability constituent]
to which this statement refers has been subject to the relevant verifications that corresponds to the following ESC Type(s):
[Reference to: ESC Type Identifiers as published in the Agency Technical Document]
has been assessed by the following Notified body:
[Business name]
[Registration number]
[Full address]
In accordance with the following report(s):
[Report(s) number(s), date(s) of issue]
The following conditions of use and other restrictions apply ([^E0063]) ([^E0064]):
[Reference to document with the list of conditions of use and other restrictions]
Reference to former ETCS Interoperability Constituent System Compatibility Statement (where applicable)
[Yes/No]
Done on:
[date DD/MM/YYYY]
Signature of Applicant:
[First Name, Surname]
Appendix C.3: RSC Statement template
TEMPLATE FOR RADIO SYSTEM COMPATIBILITY STATEMENT
RADIO SYSTEM COMPATIBILITY STATEMENT
Radio System Compatibility Statement document [Document number] ([^E0065])
We, Applicant:
[Business name]
[Complete postal Address]
Declare under our sole responsibility that the following subsystem ([^E0066]):
[Name/short description of the subsystem, relevant configuration, unique identification of the subsystem]
to which this statement refers has been subject to the relevant verifications that corresponds to the following RSC Type(s):
[Reference to: RSC Type Identifiers as published in the Agency Technical Document]
has been assessed by the following Notified body:
[Business name]
[Registration number]
[Full address]
In accordance with the following report(s):
[Report(s) number(s), date(s) of issue]
The following conditions of use and other restrictions apply ([^E0067]) ([^E0068]):
[Reference to document with the list of conditions of use and other restrictions]
Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.
This text is published under EUR-Lex's own terms of reuse, not a Legalize or public-domain licence.
EUR-Lex
Creative Commons Attribution 4.0 International (CC BY 4.0)
© European Union, https://eur-lex.europa.eu — Source: EUR-Lex (Publications Office of the European Union). Reused under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. Only EU legislation published in the printed Official Journal of the European Union is deemed authentic; consolidated texts are reproduced here for documentation purposes and have been reformatted to Markdown.