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

The following RSC Interoperability Constituent Statements has been considered:

[Indicate use of RSC Interoperability Constituent Statements]

Reference to former Radio System Compatibility Statement (where applicable)

[Yes/No]

Done on:

[date DD/MM/YYYY]

Signature of Applicant:

[First Name, Surname]

Appendix C.4: RSC Statement for Interoperability Constituent template

TEMPLATE FOR RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT

RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT

Radio System Compatibility Statement document for the Interoperability Constituent [Document number] ([^E0069])

We, Applicant:

[Business name]

[Complete postal Address]

Declare under our sole responsibility that the following Interoperability Constituent ([^E0070]):

[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 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 ([^E0071]) ([^E0072]):

[Reference to document with the list of conditions of use and other restrictions]

Reference to former Radio Interoperability Constituent System Compatibility Statement (where applicable)

[Yes/No]

Done on:

[date DD/MM/YYYY]

Signature of Applicant:

[First Name, Surname]

Appendix C.5: Combined ESC/RSC Statement template

TEMPLATE FOR ETCS AND RADIO SYSTEM COMPATIBILITY STATEMENT

ETCS AND RADIO SYSTEM COMPATIBILITY STATEMENT

ETCS and RSC System Compatibility Statement document [Document number] ([^E0073])

We, Applicant:

[Business name]

[Complete postal Address]

Declare under our sole responsibility that the following subsystem ([^E0074]):

[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 and RSC Types:

[Reference to: ESC Type and 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 ([^E0075]) ([^E0076]):

[Reference to document with the list of conditions of use and other restrictions]

The following ESC and RSC Interoperability Constituent Statements has been considered:

[Indicate use of ESC and RSC Interoperability Constituent Statements]

Reference to former ETCS and RSC System Compatibility Statement (where applicable)

[Yes/No]

Done on:

[date DD/MM/YYYY]

Signature of Applicant:

[First Name, Surname]

Appendix C.6: Combined ESC/RSC Interoperability Constituent Statement template

TEMPLATE FOR COMBINED ESC AND RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT

COMBINED ESC AND RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT

ETCS and Radio System Compatibility Statement document for Interoperability Constituent [Document number] ([^E0077])

We, Applicant:

[Business name]

[Complete postal Address]

Declare under our sole responsibility that the following Interoperability Constituent ([^E0078]):

[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 and RSC Type:

[Reference to: ESC Type and 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 ([^E0079]) ([^E0080]):

[Reference to document with the list of conditions of use and other restrictions]

Reference to former ESC and Radio Interoperability Constituent System Compatibility Statement (where applicable)

[Yes/No]

Done on:

[date DD/MM/YYYY]

Signature of Applicant:

[First Name, Surname]

Appendix D

In this appendix the template for description of conditions, restrictions and added functions is provided.

The document describing the template and its use is in the Agency Web page in the ERTMS section.

Appendix E

List of harmonised text indications and messages displayed on the ETCS Driver Machine Interface

Table E1

List of harmonised text indications and messages displayed on the ETCS Driver Machine Interface

Note:  The entries with parts in brackets (Ack(nowledgement), Del(ete), Max(imum), Spec(ial)), are meant to cover both uses of the respective terms: as a full word (where applicable) or as an abbreviation.

| Id. Number | Text indication/message |

| --- | --- | | 1 | Ack(nowledgement) | | 2 | Adhesion | | 3 | Airtight | | 4 | ATO data | | 5 | ATO data entry complete? | | 6 | ATO data view | | 7 | ATO needs data | | 8 | ATO selector | | 9 | Axle load category | | 10 | Balise read error | | 11 | BMM reaction inhibition | | 12 | Brake percentage | | 13 | Brightness | | 14 | Communication error | | 15 | Contact last RBC | | 16 | Continue in SM | | 17 | Data | | 18 | Data view | | 19 | Del(ete) | | 20 | Driver ID | | 21 | Emergency stop | | 22 | End of data entry | | 23 | Enter data | | 24 | Enter RBC data | | 25 | Entering FS | | 26 | Entering OS | | 27 | Entering SM | | 28 | Exit Shunting | | 29 | Exit SM | | 113 | FRMCS network registration failed | | 114 | GSM-R network ID | | 115 | GSM-R network registration failed | | 30 | Initiate SM | | 31 | Language | | 32 | Length (m) | | 33 | Level | | 34 | Level crossing not protected | | 35 | Loading gauge | | 36 | Main | | 37 | Maintain Shunting | | 38 | Max(imum) speed | | 116 | Mission with one radio system | | 39 | NL no longer permitted | | 40 | No | | 41 | No MA received at level transition | | 42 | No track description | | 43 | Non slippery rail | | 44 | Non-Leading | | 45 | Odometer impaired | | 46 | On | | 47 | Operated system version | | 48 | Out of GC | | 49 | Override | | 50 | PT distance exceeded | | 51 | Radio data | | 52 | Radio network ID | | 53 | Radio network registration failed | | 117 | Radio network type | | 54 | RBC data | | 55 | RBC data entry complete? | | 56 | RBC ID | | 57 | RBC phone number | | 58 | Revoke BMM reaction inhibition | | 59 | Remove VBC | | 60 | Remove VBC entry complete? | | 61 | Route unsuitable – axle load category | | 62 | Route unsuitable – loading gauge | | 63 | Route unsuitable – traction system | | 64 | Runaway movement | | 65 | RV distance exceeded | | 66 | Safe consist length no longer available | | 67 | Select type | | 68 | Set VBC | | 69 | Set VBC entry complete? | | 70 | Settings | | 71 | SH refused | | 72 | SH request failed | | 73 | SH stop order | | 74 | Shunting | | 75 | Slippery rail | | 76 | SM refused | | 77 | SM request failed | | 78 | Spec(ial) | | 79 | Specific data entry selection | | 80 | SR distance exceeded | | 81 | SR speed / distance | | 82 | SR speed / distance entry complete? | | 83 | SR stop order | | 84 | Stand-by | | 85 | Start | | 86 | System version | | 87 | Trackside malfunction | | 88 | Trackside not compatible | | 89 | Train category | | 90 | Train data | | 91 | Train data changed | | 92 | Train data entry complete? | | 93 | Train integrity | | 94 | Train is rejected | | 95 | Train running number | | 96 | Train type | | 97 | Unauthorized passing of EOA / LOA | | 98 | Use short number | | 99 | Validate ATO data | | 100 | Validate [name of NTC] data | | 101 | Validate remove VBC | | 102 | Validate set VBC | | 103 | Validate train data | | 104 | VBC[n] set code | | 105 | VBC code | | 106 | Volume | | 107 | Yes | | 108 | [name of NTC] brake demand | | 109 | [name of NTC] data entry complete? | | 110 | [name of NTC] failed | | 111 | [name of NTC] is not available | | 112 | [name of NTC] needs data |

Appendix F ([^E0081])

Open Points

| Open Point | Notes |

| --- | --- | | Reliability/availability requirements | Frequent occurrences of degraded situations caused by failures of control-command and signalling equipment will decrease the system safety. See point 4.2.1.2 |

Appendix G

Partial Fulfilment

Notwithstanding the options allowed in this TSI, e.g. under point 7.3.2 or in subset 34, it is possible to deviate from this TSI provided that compliance with provisions of point 6.1.1.2 and the deviation fulfils one of the categories below and limited to the defined cases in the table underneath:

- (1) Functions requiring upgrades of existing installations which would compromise the economic viability of a project regarding upgrades of already authorized hardware installed in the vehicles

Partial fulfilment of TSI Requirement Conditions and mitigation measures Scope of application of partial fulfilment SUBSET-091: safety requirements leading to DMI SIL 2 may not be implemented. The associated hazards linked to the safety requirements leading to DMI SIL 2 shall be mitigated by appropriate measures. Only allowed in case of upgrading an existing ETCS part (with DMI SIL 0). Intentionally deleted [^E0082]. Intentionally deleted. Intentionally deleted [^E0083] [^E0084]. Intentionally deleted Intentionally deleted Intentionally deleted (¹) Some new functionalities included in this TSI are excluded from the on-board envelopes up to 2.1 and 2.2. These reduced envelopes will be specified in SUBSET-153. (²) The following on-board functionalities impacting the ETCS on-board system version are excluded in the reduced on-board envelope up to 2.1 as specified in SS-153: CR968;CR988;CR1238;CR1244; CR1302;CR1344;CR1346;CR1350;CR1359;CR1363;CR1367;CR1374;CR1375;CR1379; CR1397. (³) The following on-board functionalities impacting the ETCS on-board system version are excluded in the reduced on-board envelope up to 2.2 as specified in SS-153: CR968;CR988;CR1244;CR1302; CR1344;CR1346;CR1350;CR1359;CR1363;CR1367;CR1374;CR1375;CR1379;CR1397.

Appendix H

In this appendix the template for the National Implementation Plan is provided.

ISSUANCE YEAR

NATIONAL IMPLEMENTATION PLAN

[MEMBER STATE]

| | |

| --- | --- | | Table of contents | Table of contents | | 1. | GENERAL MIGRATION STRATEGY INTRODUCTION | | 2. | GENERAL CONTEXT DESCRIPTION OF THE CURRENT STATUS | | 2.1. | Context description of the Class A systems, ATO and train detection part | | 2.1.1. | Current status of deployment for Class A systems, ATO and train detection part | | 2.1.2. | Benefit for capacity, safety, reliability and performance aspects | | 2.1.3. | Current mandatory onboard requirements | | 2.1.4. | Current status of deployment for on-board CCS subsystems. | | 2.1.5. | Information on the ESC/RSC Type linked with lines and activities for trackside/on-board integration. | | 2.1.6. | Information on cross-border lines | | 2.1.7. | Information on nodes | | 2.2. | Context description of Class B systems | | 2.2.1. | Current status for Class B systems | | 2.2.2. | Measures taken to ensure open market conditions | | 3. | TECHNICAL MIGRATION STRATEGY | | 3.1. | Technical migration strategy for ETCS part | | 3.1.1. | Baseline and levels update strategy | | 3.2. | Technical migration strategy for Radio part | | 3.3. | Technical migration strategy for ATO part | | 3.4. | Technical migration strategy for Train Detection part | | 3.5. | Migration strategy of specific cases | | 3.6. | Technical migration strategy for on-board CCS subsystems | | 4. | TRACKSIDE AND ON-BOARD FINANCIAL INFORMATION | | 5. | PLANNING | | 5.1. | Planning for train protection part | | 5.1.1. | Dates when ETCS is placed in service | | 5.1.2. | Decommissioning of Class B train protection systems | | 5.1.3. | Information on cross-border lines | | 5.1.4. | Information on nodes | | 5.2. | Planning for radio part | | 5.2.1. | Dates when GSM-R is placed in service | | 5.2.2. | Decommissioning of Class B radio systems | | 5.2.3. | Dates when FRMCS is placed in service | | 5.2.4. | Decommissioning of GSM-R | | 5.2.5. | Information on cross-border lines | | 5.2.6. | Information on nodes | | 5.3. | Planning for ATO part | | 5.3.1. | Information on cross-border lines | | 5.3.2. | Information on nodes | | 5.4. | Planning for train detection part | | 5.4.1. | Information on cross-border lines | | 5.4.2. | Information on nodes | | 5.5. | Planning for on-board CCS subsystems. | | 5.5.1. | Information on cross-border vehicles | | 6. | NEW MANDATORY ON-BOARD REQUIREMENTS |

[This section is open for the Member State to describe the general strategy for the deployment.]

2. GENERAL CONTEXT DESCRIPTION OF THE CURRENT STATUS

2.1.   Context description of the Class A systems, ATO and train detection part

2.1.1.   Current status of deployment for Class A systems, ATO and train detection part

[This section shall include facts and figures on the current status of installed Class A (both train protection and radio), ATO and train detection systems.

This information shall be provided including a map and a table of relevant information with the current deployment situation for each of the systems.

The template to be filled in to provide the information in this section is given below.]

—   Current status of deployment for Class A train protection system

[If relevant, include here an explanatory text in relation to the current status of ETCS deployment.]

Figure 1

Current status of ETCS deployment

| |

| --- | | [Include in this gap the map that shows the current status of ETCS deployment. The map included shall clearly identify whether the ETCS is already in operation or only installed but not yet in operation. Even if only those lines that are at least already installing ETCS are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Table 1

Current status of ETCS deployment

| ID | Line | Current status of deployment | Current status of deployment | Mandatory deadline of ETCS application | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when ETCS was placed in service | Mandatory deadline of ETCS application | Length | Level(s) | Baseline and system version | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the ETCS deployment on the line. ETCS in operation/ ETCS installed] | [For lines with ETCS already in operation. Include here the date when ETCS was placed in service.] | [Include here the latest deadline for equipment of the line with ETCS established by EU regulations] | [Include here the total length of the line] | [Include here the ETCS level(s) implemented] | [Include here the baseline and the system version of the ETCS implemented] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

—   Current status of deployment for ATO system

[This point is only mandatory in case the ATO deployment has already started]

[If relevant, include here an explanatory text in relation to ATO deployment.]

Figure 2

Current status of ATO deployment

| |

| --- | | [Include in this gap the map that shows the current status of ATO deployment. The map included shall clearly identify whether the ATO is already in operation or only installed but not yet in operation. Even if only those lines that are at least already installing ATO are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Table 2

Current status of ATO deployment

| ID | Line | Current status of ATO deployment | Current status of ATO deployment | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when ATO was placed in service | Length | Baseline | Other relevant aspects for ATO deployments (For example GoA) | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the ATO deployment on the line. ATO in operation/ ATO installed] | [For lines with ATO already in operation. Include here the date when ATO was placed in service.] | [Include here the total length of the line] | [Include here the baseline of the ATO implemented] | [Include here …] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | |

—   Current status of deployment for Class A radio system

[If relevant, include here an explanatory text in relation to the current status of Class A radio system.]

Figure 3

Current status of GSM-R deployment

[Include in this gap the map that shows the current status GSM-R deployment. The map included shall clearly identify whether the GSM-R is already in service or only installed but not yet in service. Even if only those lines that are at least already installing GSM-R are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.]

Figure 4

Current status of FRMCS deployment

| |

| --- | | [Include in this gap the map that shows the current status of FRMCS deployment. The map included shall clearly identify whether the FRMCS is already in service or only installed but not yet in service. Even if only those lines that are at least already installing FRMCS are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible. Including this map is only mandatory in case the FRMCS deployment has already started.] |

Table 3

Current status of GSM-R deployment

| | | Current status of GSM-R deployment | Current status of GSM-R deployment | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when GSM-R was placed in service | Length | GSM-R voice/ GSM-R data | Baseline | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of GSM-R deployment on the line. GSM-R in service/ GSM-R installed] | [For lines with GSM-R radio system already in operation. Include here the date when Class A radio system was placed in service.] | [Include here the total length of the line] | [Specify here whether GSM-R voice or data is installed] | [Include here the baseline of the GSM-R implemented] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

Table 4

Current status of FRMCS deployment

		Current status of FRMCS deployment	Current status of FRMCS deployment	Additional information	Additional information	Additional information	Note
ID	Line	Current status	Date when FRMCS was placed in service	Length	GSM-R condition	Baseline	Note
[Include here the line identification number]	[Include here the name of the line]	[Include here the current status of FRMCS deployment on the line. FRMCS in service/ FRMCS installed]	[For lines with FRMCS radio system already in operation. Include here the date when Class A radio system was placed in service.]	[Include here the total length of the line]	[Specify here the condition of the line in relation to GSM-R. GSM-R in service/ GSM-R not in service]	[Include here the baseline of the FRMCS implemented]	[If relevant, include here additional comments]

[Including Table 4 Current status of FRMCS deployment is only mandatory in case the FRMCS deployment has already started]

—   Current status of deployment for TSI compliant train detection system

[If relevant, include here an explanatory text in relation to TSI compliant train detection deployment.]

Figure 5

Current status of TSI compliant train detection deployment

| |

| --- | | [Include in this gap the map that shows the current status of TSI compliant train detection deployment. The map included shall clearly identify whether the TSI compliant train detection is already in service, only installed but not yet in service. Even if only those lines that are at least already installing TSI compliant train detection are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Table 5

Current status of TSI compliant train detection deployment

| ID | Line | Current status of TSI compliant train detection deployment | Current status of TSI compliant train detection deployment | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when TSI compliant train detection was placed in service | Length | [Other relevant aspects for TSI Compliant train detection deployments] | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the TSI compliant train detection deployment on the line. TSI compliant train detection in service/ TSI compliant train detection installed] | [For lines with TSI compliant train detection already in service. Include here the date when TSI compliant train detection was placed in service.] | [Include here the total length of the line] | [Include here …] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | |

2.1.2.   Benefit for capacity, safety, reliability and performance aspects

[This section shall include information of the benefits provided by TSI compliant Class A (both train protection and radio), ATO and train detection systems in relation to capacity, safety, reliability and performance.

For completeness, the section shall include both the method used to measure the benefits and the facts and figures of the impact.

The template to be filled in to provide the information in this section is given below]

| |

| --- | | [Include here the description of the methods/indicators used to measure benefits in capacity, safety, reliability and performance.] |

Table 6

Expected benefits in capacity. safety, reliability and performance

Benefits in:	System impact	Social impact	Stakeholder
Capacity	[Include here the indicators of the impact in the system regarding capacity. For example: % driving time reduction per train, % interval time reduction…]	[Include here the indicators of the social impact regarding capacity. For example: hours of travel time in a year saved by all passengers]	[Include here the stakeholder expressing the need and agreements made within the MS for the expressed needs]
Safety	[Include here the indicators of the impact in the system regarding safety. For example: % decrease SPAD]	[Include here the indicators of the social impact regarding safety. For example: Reduction of number of fatalities per year]	[Include here the stakeholder expressing the need and agreements made within the MS for the expressed needs]
Reliability	[Include here the indicators of the impact in the system regarding reliability. For example: % reduction of train delay due to malfunctions]	[Include here the indicators of the social impact regarding reliability. For example: reduction of expected number of passengers lost hours.]	[Include here the stakeholder expressing the need and agreements made within the MS for the expressed needs]
Performance	[Include here the indicators of the impact in the system regarding performance.]	[Include here the indicators of the social impact regarding performance.]	[Include here the stakeholder expressing the need and agreements made within the MS for the expressed needs]
…	…	…

[The list of benefits and impacts can be adapted depending on the analysis realized by the MS]

2.1.3.   Current mandatory onboard requirements

[This section shall include the current legal national reference to the CCS onboard requirements. In case these requirements differ between the different lines of the network, it has to be clearly defined which requirements are applicable in each case.

The template to be filled in to provide the information in this section is given below]

| |

| --- | | [If relevant, include here an explanatory text in relation to the current legal national reference to the CCS onboard requirements.] |

Table 7

Investment plan information

| Year | Stakeholder | Action |

| --- | --- | --- | | [Include here the year when the investment will be done] | [Include here which stakeholder(s) will realise the investment] | [Include here which are the action(s) foreseen with this investment] | | | | | | | | | | | | |

Table 8

Current CCS on-board requirements

| Geographical scope | Legal national reference to the CCS onboard requirements |

| --- | --- | | [Include here the geographical scope in which the specific requirements are currently applicable. For example: Complete network or specific lines.] | [Include here the legal reference to the CCS on-board requirements or specify here the applicable requirement.] | | | | | | | | | |

2.1.4.   Current status of deployment for on-board CCS subsystems

[This section shall include facts and figures on the current status of on-board CCS subsystems based on available information]

2.1.5.   Information on the ESC/RSC Type linked with lines and activities for trackside/on-board integration

[This section shall include the current status of the ESC/RSC types as long as they exist.]

2.1.6.   Information on cross-border lines

[This section shall provide the current status on cross-border lines]

2.1.7.   Information on nodes

[This section shall provide the current status on nodes]

2.2.   Context description of Class B systems

[This section will not be mandatory in those Member States that have already completed Class B decommissioning.]

2.2.1.   Current status for Class B systems

[This section shall include a context description of Class B systems current status and their economic lifetime. For completeness, it shall include at least:

• — Context description of installed Class B systems.

• — Remaining economic lifetime of existing Class B systems.

The information of the Class B system currently installed in each line shall be provided including a map and a table of relevant information.

The template to be filled in to provide the information in this section is given below]

—   Current status for Class B train protection system

[Include here explanatory text of the different Class B train protection systems currently installed and the remaining economic lifetime of each of them.]

Figure 6

Class B train protection system installed

| |

| --- | | [Include in this gap the map that shows which lines currently remain with Class B train protection system installed. The map included shall clearly identify whether the Class B train protection system is still in operation, installed but not in operation or already being decommissioned. If there is more than one existing Class B train protection system, the map shall also identify the Class B installed in each line. Even if only those lines that still have a Class B train protection system installed are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Table 9

Class B train protection systems installed

| ID | Line | Current status | Length | Class B train protection system installed | Note |

| --- | --- | --- | --- | --- | --- | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the Class B train protection system on the line. In operation/ Installed but not in operation/ Being decommissioned] | [Include here the total length of the line] | [Include here the Class B train protection system installed] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | |

—   Current status for Class B radio system

[Include here explanatory text of the different Class B radio systems currently installed and the remaining economic lifetime of each of them.]

Figure 7

Class B radio systems installed

| |

| --- | | [Include in this gap the map that shows which lines currently remain with Class B radio system installed. The map included shall clearly identify whether the Class B radio system is still in service, installed but not in service or already being decommissioned. If there is more than one existing Class B radio system, the map shall also identify the Class B installed in each line. Even if only those lines that still have a Class B radio system installed are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Table 10

Class B radio systems installed

| ID | Line | Current status | Length | Class B radio system installed | Note |

| --- | --- | --- | --- | --- | --- | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the Class B radio system on the line. In operation/ Installed but not in operation/ Being decommissioned] | [Include here the total length of the line] | [Include here the Class B radio system installed] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | |

2.2.2.   Measures taken to ensure open market conditions

[This section shall include the description of the measure taken to ensure open market conditions for its legacy Class B systems as set out in point 7.2.3

The template to be filled in to provide the information in this section is given below]

| |

| --- | | [Include here the specific measures taken to ensure open market conditions for the legacy Class B systems installed in the network as set out in point 7.2.3. In the information provided it shall be clearly defined the specific measure for each of the Class B systems installed, i.e. at least the following information shall be included: — Type of Class B product and/or specifications that are openly available for integration with any ETCS onboard in existing rolling stock. — Measure taken to ensure availability of the Class B product and/or specification. — Confirmation of availability of functional and interface specifications. Including link to the specifications — If for technical or commercial reasons the availability cannot be ensured, specify the mitigation measures.] |

3. TECHNICAL MIGRATION STRATEGY

3.1.   Technical migration strategy for ETCS part

[This section shall include information and planning of technical migration strategy of ETCS part, including ETCS Level and system version required per line and per network.

For completeness at least the following information shall be included:

• — Reasons for the decision on the ETCS level and system version in each line or type of line.

• — Deployment strategy. Overlay on-board or overlay at trackside.

• — Table which includes for each line the planning dates of deployment, ETCS level, System version, planning dates for Class B decommissioning on the line and other relevant information. The table shall provide the complete information of changes in the following 20 years.

The lines included in this table together with the lines included in Table 1 Current status of ECTS deployment shall cover all network lines in scope of the TSI including the nodes and last mile connections.

The template to be filled in to provide the information in this section is given below.]

—   Description of the solution implemented

| |

| --- | | [Include here the different solutions implemented and the specific reasons for selecting this solution for the network or for each type of line.] |

—   Deployment strategy for the implementation of ETCS

| |

| --- | | [Include here the details of the migration strategy for the implementation of ETCS. For example: Overlay onboard or overlay at trackside, foreseen dates when ETCS only equipped vehicles operation will be allowed…] |

—   Planning for ETCS deployment and Class B decommissioning

| |

| --- | | [If relevant, include here an explanatory text in relation to planning of ETCS deployment and Class B decommissioning.] |

Table 11

Planning for ETCS deployment and Class B train protection decommissioning

| ID | Line | Planning for ETCS deployment | Planning for ETCS deployment | Planning for ETCS deployment | Planning for Class B train protection decommissioning | Planning for Class B train protection decommissioning | Planning for Class B train protection decommissioning | Additional deployment information | Additional deployment information | Additional deployment information | Additional deployment information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when ETCS will be placed in service | Mandatory deadline of ETCS application | Dates when ETCS-only equipped vehicles are allowed to run | Dates when Class B operation is not allowed any more | Dates when Class B is taken out of service | Length | Level(s) | Baseline and system version | Type of action | Note | | [Include here the line identification number] | [Include here the name of the line.] | [Include here the current status of the ETCS deployment on the line. Under construction/ not yet under construction] | [Include here the date when ETCS will be placed in service.] | [Include here the latest deadline for equipment of the line with ETCS established by EU regulations] | [include when the vehicles with ETCS only are allowed to run on the line] | [If the line is equipped with a Class B train protection system, include here the date when Class B operation is not allowed anymore.] | [If not similar to the previous column, include here the date when Class B system is taken out of service] | [Include here the total length of the line] | [Include here the ETCS level(s) that will be implemented] | [Include here the baseline and the system version of the ETCS that will be implemented] | [Include here the type of ETCS action. New/ renew/ upgrade] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

3.1.1.   Baseline and levels update strategy

[If applicable, this section shall include information and planning of technical migration strategy for ETCS Baselines, for example from Baseline 2 to Baseline 3 and/or from Level 1 to Level 2]

3.2.   Technical migration strategy for Radio part

[This section shall include information and planning of the technical migration strategy for Radio part, including information on radio systems (e.g radio circuit switching or packet switching, radio infill options for ETCS).

For completeness at least the following information shall be included:

• — Strategy for the introduction of GSM-R. Overlay on-board or overlay at trackside for Class A radio part introduction.

• — Strategy for the introduction of the next generation communication system(s).

• — Table which includes for each line the planning dates of GSM-R deployment and Class B radio part decommissioning, radio circuit switching implemented or only packet switching and other relevant information. The table shall provide the complete information of changes in the following 20 years.

• — Table which includes for each line the planning dates of FRMCS deployment, if applicable radio infill options, planning for GSM-R decommissioning and other relevant information. The table shall provide the complete information of changes in the following 20 years.

The lines included in these tables together with the lines included in Table 3

Current status of GSM-R deployment and Table 4

Current status of FRMCS deployment shall cover all network lines in scope of the TSI including the nodes and last mile connections.

The template to be filled in to provide the information in this section is given below.]

—   Strategy for the introduction of GSM-R

| |

| --- | | [Include here the information of the strategy followed for the introduction of GSM-R. For example: Migration strategy (overlay onboard or at trackside) in relation to the Class B radio part, radio circuit switching implementation or only packet switching…] |

—   Strategy for the introduction of the next generation communication system(s)

| |

| --- | | [Include here the details of the migration strategy for the introduction of the next generation of communication systems.] |

—   Planning for GSM-R deployment and Class B radio system decommissioning

| |

| --- | | [If relevant, include here an explanatory text in relation to planning of GSM-R deployment and Class B radio part decommissioning.] |

Table 12

Planning for GSM-R deployment and Class B radio part decommissioning

| ID | Line | Planning for GSM-R deployment | Planning for GSM-R deployment | Planning for GSM-R deployment | Planning for Class B radio decommissioning | Planning for Class B radio decommissioning | Additional information | Additional information | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Realization | Date when GSM-R is placed in service | Dates when Class B operation is not allowed any more | Dates when Class B is taken out of service | Length | GSM-R voice/ GSM-R data | Baseline | Circuit switching/ Packet switching | Type of action | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the GSM-R deployment on the line. Under construction/ not yet under construction] | [Include here the date when the construction started or is expected to start.] | [Include here the date when GSM-R will be placed in service.] | [If the line is equipped with a Class B radio system, include here the date when Class B operation is not allowed anymore.] | [If not similar to the previous column, include here the date when Class B system is taken out of service] | [Include here the total length of the line] | [Specify here whether GSM-R voice or data is installed] | [Include here the baseline of the GSM-R to be implemented] | [Include here if radio circuit switching is implemented or only packet switching] | [Include here the type of Radio part action. New/ renew/ upgrade] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

—   Planning for FRMCS deployment and GSM-R decommissioning

| |

| --- | | [If relevant, include here an explanatory text in relation to planning of FRMCS deployment and GSM-R decommissioning.] |

Table 13

Planning for FRMCS deployment and GSM-R decommissioning

| ID | Line | Planning for FRMCS deployment | Planning for FRMCS deployment | Planning for FRMCS deployment | Planning for GSM-R decommissioning | Planning for GSM-R decommissioning | Additional information | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Realization | Date when FRMCS is placed in service | Dates when GSM-R operation is not allowed any more | Dates when GSM-R is taken out of service | Length | Baseline | Pre-existing GSM-R condition | Type of action | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the FRMCS deployment on the line. Under construction/ not yet under construction] | [Include here the date when the construction started or is expected to start.] | [Include here the date when FRMCS will be placed in service.] | [If the line is equipped with GSM-R system, include here the date when Class B operation is not allowed anymore.] | [If not similar to the previous column, include here the date when GSM-R system is taken out of service] | [Include here the total length of the line] | [Include here the baseline of the FRMCS to be implemented] | [Specify here the condition of the line in relation to GSM-R. GSM-R in service/ GSM-R will be in service before FRMCS/ Pre-existing GSM-R not foreseen] | [Include here the type of Radio part action. New/ renew/ upgrade] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

3.3.   Technical migration strategy for ATO part

[This section shall include information and planning of technical migration strategy of ATO part, including information on the need for deployment of ATO.

For completeness at least the following information shall be included:

• — Deployment strategy. Reason for deployment of ATO.

• — Table which includes for each line the planning dates of ATO deployment and other relevant information. The table shall provide the complete information of changes in the following 20 years. Including this table is only mandatory if the ATO is expected to be implemented in the next 20 years.

The template to be filled in to provide the information in this section is given below.]

—   Deployment strategy for ATO

| |

| --- | | [Include here the details of the deployment strategy of ATO, including information on the reason for deployment.] |

—   Planning for ATO deployment

| |

| --- | | [If relevant, include here an explanatory text in relation to planning of ATO deployment.] |

Table 14

Planning for ATO deployment

| ID | Line | Planning for ATO deployment | Planning for ATO deployment | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when ATO is placed in service | Length | Baseline | Other relevant aspects for ATO deployments (For example GoA) | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the ATO deployment on the line. Under construction/ not yet under construction] | [Include here the date when ATO will be placed in service.] | [Include here the total length of the line] | [Include here the baseline of the ATO to be implemented] | [Include here …] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | |

3.4.   Technical migration strategy for Train Detection part

[This section shall include information and planning of the technical migration strategy of TSI compliant train detection part.

For completeness at least the following information shall be included:

• — Deployment strategy. Information on the migration to the TSI compliant train detection system.

• — Table which includes for each line the planning dates of TSI compliant train detection system deployment and other relevant information. The table shall provide the complete information of changes in the following 20 years.

The template to be filled in to provide the information in this section is given below]

—   Deployment strategy for TSI compliant train detection system

| |

| --- | | [Include here the details of the migration strategy to the TSI compliant train detection system.] |

—   Planning for TSI compliant train detection system deployment

| |

| --- | | [If relevant, include here an explanatory text in relation to planning of the TSI compliant train detection system deployment.] |

Table 15

Planning for TSI compliant train detection deployment

| ID | Line | Planning for TSI compliant train detection deployment | Planning for TSI compliant train detection deployment | Additional information | Additional information | Additional information | Note |

| --- | --- | --- | --- | --- | --- | --- | --- | | ID | Line | Current status | Date when TSI compliant train detection is placed in service | Length | Type of action | [Other relevant aspects for TSI Compliant train detection deployments] | Note | | [Include here the line identification number] | [Include here the name of the line] | [Include here the current status of the TSI compliant train detection deployment on the line. Under construction/ not yet under construction] | [Include here the date when TSI compliant train detection will be placed in service.] | [Include here the total length of the line] | [Include here the type of train detection part action. New/ renew/ upgrade] | [Include here …] | [If relevant, include here additional comments] | | | | | | | | | | | | | | | | | | | | | | | | | | | |

3.5.   Migration strategy of specific cases

[This section shall include information and planning of the technical migration strategy for specific cases state on section 7.6 of the CCS TSI.

The template to be filled in to provide the information in this section is given below]

| |

| --- | | [Include here the details of the migration strategy of the specific cases stated on section 7.6 of CCS TSI. It shall be clearly defined in the information provided to which specific route or networks are each specific case limited to and if applicable, the relevant dates for the migration.] |

3.6.   Technical migration strategy for on-board CCS subsystems

[This section shall include information and planning of the technical migration strategy for on-board CCS subsystems.]

[This section shall provide information about available funds, sources of financing and necessary financial needs]

[For all the network maps to be included in this section, the map shall provide a planning overview of changes in the next 20 years.]

5.1.   Planning for train protection part

5.1.1.   Dates when ETCS is placed in service

[This section shall include a network map providing an overview with dates when ETCS is placed in service.

This section is not mandatory for those Member States which have already completed the ETCS deployment in all lines in scope of the TSI including the nodes and last mile connections and do not foresee any upgrade, renew or new line in the next 20 years.

The template to be filled in to provide the information in this section is given below.]

Figure 8

Network map. Dates when ETCS is placed in service

| |

| --- | | [Include in this gap the network map providing the overview of dates when ECTS is placed in service in the next 20 years. The map included shall clearly identify the dates when ECTS is placed in service, the level and the system version. Even if only those lines on which new, upgraded or renewed ETCS implementation of ETCS is foreseen are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

5.1.2.   Decommissioning of Class B train protection systems

[This section shall include a network map providing an overview with dates when Class B operation is not allowed anymore. If not similar, this section shall also include a network map providing and overview with dates where Class B system is taken out of service.

This section is not mandatory for those Member States which have already completed the decommissioning of its Class B protection systems or which have never used a Class B train protection system.

The template to be filled in to provide the information in this section is given below.]

Figure 9

Network map. Dates when Class B operation is not allowed anymore

| |

| --- | | [Include in this gap the network map providing the overview of dates when Class B operation is not allowed anymore in the next 20 years. Even if only those lines on which is planned to not allow Class B operation anymore are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Figure 10

Network map. Dates where Class B train protection system is taken out of service

| |

| --- | | [Include in this gap the network map providing the overview of dates where Class B system is taken out of service in the next 20 years. Even if only those lines on which is planned to take out of service Class B train protection are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible. Including this map is not mandatory if similar to the previous one] |

5.1.3.   Information on cross-border lines

[This section shall provide detailed information on the planning on cross-border lines]

5.1.4.   Information on nodes

[This section shall provide detailed information on the planning on nodes]

5.2.   Planning for radio part

5.2.1.   Dates when GSM-R is placed in service

[This section shall include a network map providing an overview with dates when GSM-R is placed in service.

This section is not mandatory for those Member States that have already completed the GSM-R deployment in all lines in scope of the TSI including the nodes and last mile connections.

The template to be filled in to provide the information in this section is given below.]

Figure 11

Network map. Dates when GSM-R is placed in service

| |

| --- | | [Include in this gap the network map providing an overview with dates when GSM-R is placed in service in the next 20 years. The map included shall clearly identify the dates when GSM-R is placed in service and if GSM-R voice or data is implemented. Even if only those lines on which GSM-R implementation is foreseen are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

5.2.2.   Decommissioning of Class B radio systems

[This section shall include a network map providing an overview with dates when Class B radio operation is not allowed anymore. If not similar, this section shall also include a network map providing and overview with dates where Class B radio system is taken out of service.

This section is not mandatory for those Member States which have already completed the decommissioning of its Class B radio systems.

The template to be filled in to provide the information in this section is given below.]

Figure 12

Network map. Dates when Class B radio operation is not allowed anymore

| |

| --- | | [Include in this gap the network map providing an overview with dates when Class B radio operation is not allowed anymore in the next 20 years. Even if only those lines on which is planned to not allow Class B radio operation anymore are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Figure 13

Network map. Dates where Class B radio system is taken out of service

| |

| --- | | [Include in this gap the network map providing and overview with dates where Class B radio system is taken out of service in the next 20 years. Even if only those lines on which is planned to take out of service Class B radio are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible. Including this map is not mandatory if similar to the previous] |

5.2.3.   Dates when FRMCS is placed in service

[This section shall include a network map providing an overview with dates when FRMCS is placed in service.

This section is not mandatory for those Member States that do not foresee FRMCS implementation in the next 20 years.

The template to be filled in to provide the information in this section is given below.]

Figure 14

Network map. Dates when FRMCS is placed in service

| |

| --- | | [Include in this gap the network map providing an overview with dates when FRMCS is placed in service in the next 20 years. The map included shall clearly identify the dates when FRMCS is placed in service. Even if only those lines on which FRMCS implementation is foreseen are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

5.2.4.   Decommissioning of GSM-R

[This section shall include a network map providing an overview with dates when GSM-R radio operation is not allowed anymore. If not similar, this section shall also include a network map providing an overview with dates where GSM-R system is taken out of service.

This section is not mandatory for those Member States which do not foresee GSM-R decommissioning in the next 20 years.

The template to be filled in to provide the information in this section is given below]

Figure 15

Network map. Dates when GSM-R radio operation is not allowed anymore

| |

| --- | | [Include in this gap the network map providing an overview with dates when GSM-R radio operation is not allowed anymore in the next 20 years. Even if only those lines on which is planned to not allow GSM-R operation anymore are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

Figure 16

Network map. Dates where GSM-R system is taken out of service

| |

| --- | | [Include in this gap the network map providing an overview with dates where GSM-R system is taken out of service in the next 20 years. Even if only those lines on which is planned to take out of service GSM-R radio are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible. Including this map is not mandatory if similar to the previous one] |

5.2.5.   Information on cross-border lines

[This section shall provide detailed information on the planning on cross-border lines]

5.2.6.   Information on nodes

[This section shall provide detailed information on the planning on nodes]

5.3.   Planning for ATO part

[This section shall include a network map providing an overview with dates when ATO is placed in service.

This section is not mandatory for those Member States that do not foresee to put ATO into service in the next 20 years.]

The template to be filled in to provide the information in this section is given below.]

Figure 17

Network map. Dates when ATO is placed in service

| |

| --- | | [Include in this gap the network map providing an overview with dates when ATO is placed in service in the next 20 years. The map included shall clearly identify the dates when ATO is placed in service. Even if only those lines on which ATO implementation is foreseen are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

5.3.1.   Information on cross-border lines

[This section shall provide detailed information on the planning on cross-border lines]

5.3.2.   Information on nodes

[This section shall provide detailed information on the planning on nodes]

5.4.   Planning for train detection part

[This section shall include a network map providing an overview with dates when TSI compliant train detection system is placed in service.

The template to be filled in to provide the information in this section is given below.]

Figure 18

Network map. Dates when TSI compliant train detection system is placed in service

| |

| --- | | [Include in this gap the network map providing an overview with dates when TSI compliant train detection system is placed in service in the next 20 years. The map included shall clearly identify the dates when TSI compliant train detection system is placed in service. Even if only those lines on which TSI compliant train detection system implementation is foreseen are outlined on the map, the map shall show all network lines in scope of the TSI including the nodes and last mile connections. The map and its key legend shall be clearly visible.] |

5.4.1.   Information on cross-border lines

[This section shall provide detailed information on the planning on cross-border lines]

5.4.2.   Information on nodes

[This section shall provide detailed information on the planning on nodes]

5.5.   Planning for on-board CCS subsystems.

[This section shall include a description of the planning and dates for the installation of the on-board CCS subsystems.]

5.5.1.   Information on cross-border vehicles

[This section is optional and shall provide detailed information on the planning on cross-border vehicles]

[This section shall include information of new mandatory onboard requirements that will be required for operating on the network, ensuring that notifications to RUs are provided at least 5 years in advance.

The template to be filled in to provide the information in this section is given below]

| |

| --- | | [If relevant, include here an explanatory text in relation to new mandatory onboard requirements that will be required for operating on the network.] |

Table 16

New mandatory on-board requirements

| Geographical scope | New CCS on-board requirements | Date of application |

| --- | --- | --- | | [Include here the geographical scope in which the specific requirements will be applicable. For example: Complete network or specific lines. | [Include here the legal reference to the new CCS on-board requirements or specify here the new CCS onboard requirements | [Include here date of application of the new CCS on-board requirement. At the earliest, a 5-year period is required. | | | | | | | | | | | | |

ANNEX II

| | |

| --- | --- | | Table of contents | Table of contents | | 1. | INTRODUCTION | | 2. | ABBREVIATIONS, ACRONYMS | | 3. | CLASS B SYSTEMS | | 3.1. | CONDITIONS FOR CLASS B SYSTEMS | | 3.2. | USE OF THIS ANNEX | | 3.3. | LIST OF CLASS B TRAIN PROTECTION SYSTEMS | | 3.4. | LIST OF CLASS B VOICE RADIO SYSTEMS |

This Annex contains the list of train protection and voice radio legacy systems referred in the Control-Command and Signalling TSI.

The acronyms used as names of legacy systems are explained in the tables in Sections 3.3 and 3.4.

RDD: Reference Document Database (https://rdd.era.europa.eu/RDD/).

3. CLASS B SYSTEMS

3.1.   CONDITIONS FOR CLASS B SYSTEMS

Class B systems for the trans-European rail system network are a limited set of train protection and voice radio legacy systems that were already in use in the trans-European rail network before 20 April 2001.

Class B systems for other parts of the network of the rail system in the European Union are a limited set of train protection and voice radio legacy systems that were already in use in those part of the network before 1 July 2015.

3.2.   USE OF THIS ANNEX

This is an Annex based on information received from Member States, Norway, Switzerland and the United Kingdom, and in accordance with the provisions of this TSI.

As stated in point 3.1 of the Annex I of this Regulation, ‘The requirements for Class B systems are the responsibility of the relevant Member State’. Details on the technical specifications can be found in the RDD.

3.3.   LIST OF CLASS B TRAIN PROTECTION SYSTEMS

Member State	Name of the legacy system [^E0085]	Scope	Version identification	Date of latest authorisation to placing into service
Austria	INDUSI I 60 [^E0086]	Whole network
Austria	PZB 90 [^E0087]	Whole network	AT/DE
Austria	LZB L72 LZB CE I LZB CE II	Whole network Whole network Whole network
Belgium	Crocodile	Whole network
Belgium	TBL 1	Whole network
Belgium	TBL 2	Whole network
Belgium	TVM 430	Whole network
Belgium	TBL1+	Off-TEN only
Belgium	KVB	Access to high speed line 1
Bulgaria	EBICAB 700	Whole network	BU
Croatia	INDUSI I 60 [^E0086]	Whole network
Czechia	LS	Whole network
Denmark	ZUB 123	Whole network	SW02A (version 1.37 edition 04)	2.2.2004
Estonia	ALSN	Whole network
Finland	ATP-VR/RHK	Whole network
France	Crocodile	Whole network
France	KVB	Whole network
France	TVM 300	High speed lines
France	TVM 430	High speed lines
France	KVBP	(sub)urban area of Paris
France	KCVP	(sub)urban area of Paris
France	KCVB	(sub)urban area of Paris
France	NEXTEO	(sub)urban area of Paris
France	DAAT	Whole network
Germany	PZB 90	Whole network	AT/DE
Germany	LZB CE I LZB CE II [^E0088]	Whole network Whole network	AT/DE
Germany	GNT (Geschwindigkeitsüberwachung für NeiTech-Züge) [^E0089]	Whole network (routes with higher lateral acceleration for tilting trains)	AT/DE
Hungary	EVM	Whole network
Ireland	CAWS	Whole network
Ireland	ATP	Whole network
Italy	SCMT + RSC	Whole network
Italy	SCMT	Whole network
Italy	SSC	Off-TEN only
Latvia	ALSN	Whole network
Lithuania	ALSN	Whole network
Norway [^E0090]	ATC [^E0091]	Whole network	2	1993
Poland	SHP	Whole network
Poland	PKP radio system with Radiostop function	Whole network
Portugal	INDUSI I 60	Cascais line Off-TEN	PT
Portugal	EBICAB 700 (CONVEL)	Whole network	PT
Romania	INDUSI I 60 [^E0086]	Whole network
Slovakia	LS	Main lines
Slovenia	INDUSI I 60 [^E0086]	All main lines and also 3 regional lines
Spain	ASFA	Conventional network and rest of the network equipped with third rail tracks	CONV
Spain	ASFA	High Speed Lines except sections equipped with third rail tracks	AV
Spain	ASFA	Metric gauge lines	RAM
Spain	LZB	High Speed Line ‘Madrid – Sevilla/Toledo/Málaga’ C5 Commuter Line (Madrid). Section ‘Humanes – Mostoles el Soto’	ES
Sweden	ATC [^E0091]	Whole network except Linköping-Västervik/Kisa	2
		Linköping-Västervik/Kisa	R
Switzerland [^E0090]	EuroSIGNUM [^E0092]	Whole network
Switzerland [^E0090]	EuroZUB [^E0092]	Whole network
The Netherlands	ATB First generation	Whole network
The Netherlands	ATB new generation	Whole network
UK for Northern Ireland	GW ATP	Limited to specific routes only
UK for Northern Ireland	RETB	Limited to specific routes only
UK for Northern Ireland	TPWS/AWS	Whole network
UK for Northern Ireland	Chiltern-ATP	Limited to specific routes only
UK for Northern Ireland	Mechanical Trainstops	Limited to specific routes only

The fact that two or more Member States use the same system does not imply that they are compatible: the versions shall be taken into account.

Rolling stock equipped with higher versions (eg PZB 90) is accepted.

All new authorised vehicles must be equipped with PZB 90.

LZB 72 no longer in operation in Germany, since end of 2023.

GNT can only work in connection with PZB 90.

For information.

Formerly referred to as ‘EBICAB 700’

[^E0092]: (⁸)

Swiss Class B system is only allowed for ETCS B2 vehicles.

3.4.   LIST OF CLASS B VOICE RADIO SYSTEMS ([^E0093])