8.9.2023
EN
Official Journal of the European Union
L 222/457
The trackside implementation of national or optional functions shall be technically compatible and 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 in point 7.2.9.1 and 7.2.9.3.
The trackside implementation of one of these optional functions which leads to a new mandatory on-board requirement on specific lines shall be notified minimum 5 years before the function can become a mandatory on-board requirement.
The notification of a new mandatory on-board requirement shall be done within the RINF and these changes in RINF shall be listed in the Network Statement according to Article 27 of the Directive 2012/34/EU of the European Parliament and of the Council (30).
A notification period shorter than 5 years is only allowed if this is agreed between the IM and RU’s who run services or intent to run services (at the time of establishing the agreement) on these lines.
This agreement on shortening the notification period shall be notified to the European Commission.
An on-board subsystem which incorporates a KER STM, may make it necessary to implement the K-interface.
7.2.9.1.
ETCS
(1)
An ETCS Level 2 Trackside application with no or reduced train detection (formerly ETCS level 3) relies on on-board information to determine track occupation and requires that the on-board is able to fulfil the requirements for confirmed train length information as specified in Appendix A, Table A 2, index 27.
(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.
(4)
When ETCS trackside needs a specific ETCS system version, the on-board shall be equipped according to the implementation requirements listed in 7.4.2.4.2.
7.2.9.2.
AT O
(1)
ATO Trackside: the trackside implementation of ATO is an optional function for interoperability which does technically not prevent the use of that infrastructure by a train that is not equipped with ATO on-board.
Where ATO GoA1/2 functionality is implemented over ETCS trackside, the specifications of ATO in Appendix A of this TSI shall be applied.
Note: Where ATO GoA1/2 functionality is implemented over Class B trackside, the specifications of ATO trackside in Appendix A of this TSI should be applied in order to facilitate the future migration to ATO on lines to be equipped with ETCS.
(2)
ATO on-board: the fitting of ATO in a CCS on-board Subsystem is mandatory (31) when implementing ETCS for the first time into the vehicle and the vehicle is also intended for use on a line including at least one section equipped with ATO where the IM has notified in RINF the services requiring mandatory ATO on-board implementation.
(30) Directive 2012/34/EU of the European Parliament and of the Council of 21 November 2012 establishing a single European railway area (recast) (OJ L 343, 14.12.2012, p. 32).
(31) The mandatory ATO on-board implementation requirement is not linked to technical compatibility, however linked to the regulatory need that no specific incentive mechanism for ATO on-board implementation shall be developed by Member States or Infrastructure Manager for vehicles implementing ETCS for the first time.