Commission Implementing Regulation (EU) 2019/776 of 16 May 2019 amending Commission Regulations (EU) No 321/2013, (EU) No 1299/2014, (EU) No 1301/2014, (EU) No 1302/2014, (EU) No 1303/2014 and (EU) 2016/919 and Commission Implementing Decision 2011/665/EU as regards the alignment with Directive (EU) 2016/797 of the European Parliament and of the Council and the implementation of specific objectives set out in Commission Delegated Decision (EU) 2017/1474 (Text with EEA relevance.)

• (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
1	Use of interoperability constituents	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
1	Use of interoperability constituents	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
2	Integration of interoperability constituents in the subsystem	Check that additional functions (not specified in this TSI) do not impact the mandatory ones	Impact analysis
2	Integration of interoperability constituents in the subsystem	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
2	Integration of interoperability constituents in the subsystem	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)
4	Integration with infrastructure	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)
5	Integration with trackside signalling	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)
5	Integration with trackside signalling	Check that the interfaces are correctly installed and function properly.	Design verification and tests according to information supplied by the applicant
5	Integration with trackside signalling	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
6	Integration with Control-Command and Signalling On-board Subsystems and with rolling stock	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
8	Reliability, Availability, Maintainability, Safety (RAMS) (excluding train detection)	Check that quantitative reliability targets are respected — Basic Parameter 4.2.1.2	Calculations
8	Reliability, Availability, Maintainability, Safety (RAMS) (excluding train detection)	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[^ntr1-LI2019139EN.01023801-E0015] and in Commission Decision 2010/713/EU[^ntr2-LI2019139EN.01023801-E0016].

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[^ntr3-LI2019139EN.01023801-E0017] 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[^ntr4*-LI2019139EN.01023801-E0018] 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[^ntr5*-LI2019139EN.01023801-E0019].

	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[^ntr6*-LI2019139EN.01023801-E0020] 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[^ntr7*-LI2019139EN.01023801-E0021].

	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	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	Not fulfilling all the conditions in point 7.2.1b.3
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	Not fulfilling all the conditions in point 7.2.1b.3

• 1. 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.

• 1. 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.

• 1. 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.

• 1. In any case, the entity managing the change shall ensure that the technical documentation which is relating to the EC certificate is updated accordingly.

• 1. 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.

• 1. “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[^ntr8*-LI2019139EN.01023801-E0022] 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[^ntr9*-LI2019139EN.01023801-E0023].

	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[^ntr10*-LI2019139EN.01023801-E0024] 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[^ntr11*-LI2019139EN.01023801-E0025].

	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[^ntr12*-LI2019139EN.01023801-E0026] 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[^ntr13*-LI2019139EN.01023801-E0027].

[^ntc1*-LI2019139EN.01023801-E0015]

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).

"

[^ntc2*-LI2019139EN.01023801-E0016]

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).

"

[^ntc3*-LI2019139EN.01023801-E0017]

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.

"

[^ntc4*-LI2019139EN.01023801-E0018]

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.

"

[^ntc5*-LI2019139EN.01023801-E0019]

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.

"

[^ntc6*-LI2019139EN.01023801-E0020]

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.

"

[^ntc7*-LI2019139EN.01023801-E0021]

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.

"

[^ntc8*-LI2019139EN.01023801-E0022]

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.

"

[^ntc9*-LI2019139EN.01023801-E0023]

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.

"

[^ntc10*-LI2019139EN.01023801-E0024]

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.

"

[^ntc11*-LI2019139EN.01023801-E0025]

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.

"

[^ntc12*-LI2019139EN.01023801-E0026]

12* On-board subsystems with conditions and restrictions of use or non-detected deficiencies are not considered compliant regarding this clause.

"

[^ntc13*-LI2019139EN.01023801-E0027]

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[^ntr9-LI2019139EN.01023801-E0028] 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[^ntr10-LI2019139EN.01023801-E0029].

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

• 1. 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.

[^ntr*9-LI2019139EN.01023801-E0028]: 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)."

[^ntr*10-LI2019139EN.01023801-E0029]: 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[^ntr*11-LI2019139EN.01023801-E0030].

	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.

[^ntr*11-LI2019139EN.01023801-E0030]: 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[^ntr*12-LI2019139EN.01023801-E0031] 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[^ntr*13-LI2019139EN.01023801-E0032] 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[^ntr12-LI2019139EN.01023801-E0031] 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[^ntr12-LI2019139EN.01023801-E0031] enforcing compliance with set specifications #2 or #3 within a period of time not exceeding 1 July 2023.

[^ntr*12-LI2019139EN.01023801-E0031]: Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable."

[^ntr*13-LI2019139EN.01023801-E0032]: 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.’;"

[^ntc*12-LI2019139EN.01023801-E0031]  Or placed into service in accordance with Directive 2008/57/EC, if Directive (EU) 2016/797 is not yet applicable."

[^ntc*12-LI2019139EN.01023801-E0031]  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 24 — 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 24 — 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)	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)	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)	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)
Index No	Reference	Name of Specification	Version	Notes
1	ERA/ERTMS/003204	ERTMS/ETCS Functional requirement specification	5.0
2	Intentionally deleted
3	SUBSET-023	Glossary of Terms and Abbreviations	2.0.0
4	SUBSET-026	System Requirements Specification	2.3.0
5	SUBSET-027	FFFIS Juridical recorder-downloading tool	2.3.0	Note 1
6	SUBSET-033	FIS for man-machine interface	2.0.0
7	SUBSET-034	FIS for the train interface	2.0.0
8	SUBSET-035	Specific Transmission Module FFFIS	2.1.1
9	SUBSET-036	FFFIS for Eurobalise	2.4.1
10	SUBSET-037	EuroRadio FIS	2.3.0
11	SUBSET-038	Offline key management FIS	2.3.0
12	SUBSET-039	FIS for the RBC/RBC handover	2.3.0
13	SUBSET-040	Dimensioning and Engineering rules	2.3.0
14	SUBSET-041	Performance Requirements for Interoperability	2.1.0
15	SUBSET-108	Interoperability related consolidation on TSI Annex A documents	1.2.0
16	SUBSET-044	FFFIS for Euroloop	2.3.0
17	Intentionally deleted
18	SUBSET-046	Radio infill FFFS	2.0.0
19	SUBSET-047	Trackside-Trainborne FIS for Radio infill	2.0.0
20	SUBSET-048	Trainborne FFFIS for Radio infill	2.0.0
21	SUBSET-049	Radio infill FIS with LEU/interlocking	2.0.0
22	Intentionally deleted
23	SUBSET-054	Responsibilities and rules for the assignment of values to ETCS variables	2.1.0
24	Intentionally deleted
25	SUBSET-056	STM FFFIS Safe time layer	2.2.0
26	SUBSET-057	STM FFFIS Safe link layer	2.2.0
27	SUBSET-091	Safety Requirements for the Technical Interoperability of ETCS in Levels 1 and 2	2.5.0
28	Intentionally deleted
29	SUBSET-102	Test specification for interface “K”	1.0.0
30	Intentionally deleted
31	SUBSET-094	Functional requirements for an onboard reference test facility	2.0.2
32	EIRENE FRS	GSM-R Functional requirements specification	8.0.0	Note 10
33	EIRENE SRS	GSM-R System requirements specification	16.0.0	Note 10
34	A11T6001	(MORANE) Radio Transmission FFFIS for EuroRadio	13.0.0
35	Intentionally deleted
36 a	Intentionally deleted
36 b	Intentionally deleted
36 c	SUBSET-074-2	FFFIS STM Test cases document	1.0.0
37 a	Intentionally deleted
37 b	SUBSET-076-5-2	Test cases related to features	2.3.3
37 c	SUBSET-076-6-3	Test sequences	2.3.3
37 d	SUBSET-076-7	Scope of the test specifications	1.0.2
37 e	Intentionally deleted
38	06E068	ETCS Marker-board definition	2.0
39	SUBSET-092-1	ERTMS EuroRadio Conformance Requirements	2.3.0
40	SUBSET-092-2	ERTMS EuroRadio test cases safety layer	2.3.0
41	Intentionally deleted
42	Intentionally deleted
43	SUBSET 085	Test specification for Eurobalise FFFIS	2.2.2
44	Intentionally deleted
45	SUBSET-101	Interface “K” Specification	1.0.0
46	SUBSET-100	Interface “G” Specification	1.0.1
47	Intentionally deleted
48	Reserved	Test specification for mobile equipment GSM-R		Note 4
49	SUBSET-059	Performance requirements for STM	2.1.1
50	SUBSET-103	Test specification for Euroloop	1.0.0
51	Reserved	Ergonomic aspects of the DMI
52	SUBSET-058	FFFIS STM Application layer	2.1.1
53	Intentionally deleted
54	Intentionally deleted
55	Intentionally deleted
56	Intentionally deleted
57	Intentionally deleted
58	Intentionally deleted
59	Intentionally deleted
60	Intentionally deleted
61	Intentionally deleted
62	Reserved	RBC-RBC Test specification for safe communication interface
63	SUBSET-098	RBC-RBC Safe Communication Interface	1.0.0
64	EN 301 515	Global System for Mobile Communication (GSM); Requirements for GSM operation on railways	2.3.0	Note 2
65	TS 102 281	Detailed requirements for GSM operation on railways	3.0.0	Note 3
66	TS 103 169	ASCI Options for Interoperability	1.1.1
67	(MORANE) P 38 T 9001	FFFIS for GSM-R SIM Cards	5.0	Note 10
68	ETSI TS 102 610	Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways	1.3.0
69	(MORANE) F 10 T 6002	FFFS for Confirmation of High Priority Calls	5.0
70	(MORANE) F 12 T 6002	FIS for Confirmation of High Priority Calls	5.0
71	(MORANE) E 10 T 6001	FFFS for Functional Addressing	4.1
72	(MORANE) E 12 T 6001	FIS for Functional Addressing	5.1
73	(MORANE) F 10 T6001	FFFS for Location Dependent Addressing	4
74	(MORANE) F 12 T6001	FIS for Location Dependent Addressing	3
75	(MORANE) F 10 T 6003	FFFS for Presentation of Functional Numbers to Called and Calling Parties	4
76	(MORANE) F 12 T 6003	FIS for Presentation of Functional Numbers to Called and Calling Parties	4
77	ERA/ERTMS/033281	Interfaces between CCS trackside and other subsystems	4.0	Note 7
78	Reserved	Safety requirements for ETCS DMI functions
79	Not applicable	Not applicable
80	Not applicable	Not applicable
81	Not applicable	Not applicable
82	Not applicable	Not applicable

Table A 2.2

List of mandatory specifications