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)
Article 1
Subject matter
Article 2
Scope
Article 3
Open points
Article 4
Specific cases
Article 5
Implementation
Article 6
Availability of ETCS, ATO and FRMCS on-board products
Article 7
Class-B systems
Article 8
Union funded projects
Article 9
Error corrections
Article 10
Future Railway Mobile Communication System
Article 11
Innovative solutions
Article 12
ERTMS compatibility and future revision
Article 13
Train-detection compatibility
Article 14
Repeal and transitional provisions
Article 15
Entry into force
ANNEX I
1. INTRODUCTION
1.1.
Technical scope
1.2.
Geographical Scope
1.3.
Content of this TSI
2. SUBSYSTEM DEFINITION AND SCOPE
2.1.
Introduction
2.2.
Scope
2.3.
Trackside Application Levels (ETCS)
3. THE ESSENTIAL REQUIREMENTS FOR THE CONTROL-COMMAND AND SIGNALLING SUBSYSTEMS
3.1.
General
|
Basic Parameter Point |
Basic Parameter Title |
Safety |
Reliability-Availability |
Health |
Environmental protection |
Technical compatibility |
|
4.2.1 |
Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability |
1.1.1 1.1.3 2.3.1 |
1.2 |
|
|
|
|
4.2.2 |
On-Board ETCS functionality |
1.1.1 |
|
|
|
1.5 2.3.2 |
|
4.2.3 |
Trackside ETCS functionality |
1.1.1 |
|
|
|
1.5 2.3.2 |
|
4.2.4 |
Mobile communication functions for railways RMR |
|
|
|
1.4.3 |
1.5 2.3.2 |
|
4.2.5 |
RMR, ETCS and ATO air gap interfaces |
|
|
|
|
1.5 2.3.2 |
|
4.2.6 |
On-Board Interfaces Internal to Control-Command and Signalling |
|
|
|
|
1.5 2.3.2 |
|
4.2.7 |
Trackside Interfaces Internal to Control-Command and Signalling |
|
|
|
|
1.5 2.3.2 |
|
4.2.8 |
Key Management |
|
|
|
|
1.5 2.3.2 |
|
4.2.9 |
ETCS-ID Management |
|
|
|
|
1.5 2.3.2 |
|
4.2.10 |
Trackside Train Detection Systems |
|
|
|
|
1.5 2.3.2 |
|
4.2.11 |
Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling trackside equipment |
|
|
|
1.4.3 |
1.5 2.3.2 |
|
4.2.12 |
ETCS DMI (Driver-Machine Interface) |
|
|
|
|
1.5 2.3.2 |
|
4.2.13 |
RMR DMI (Driver-Machine Interface) |
|
|
|
|
1.5 2.3.2 |
|
4.2.14 |
Interface to Data Recording for Regulatory Purposes |
1.1.1 |
|
|
|
1.5 2.3.2 |
|
4.2.15 |
Trackside Control-Command and Signalling objects |
|
|
|
|
1.5 2.3.2 |
|
4.2.16 |
Construction of equipment used in CCS subsystems |
1.1.3 1.1.4 |
|
1.3.2 |
1.4.2 |
|
|
4.2.17 |
ETCS and Radio System Compatibility |
|
|
|
|
1.5 2.3.2 |
|
4.2.18 |
On-Board ATO functionality |
|
|
|
|
1.5 2.3.2 |
|
4.2.19 |
Trackside ATO functionality |
|
|
|
|
1.5 2.3.2 |
|
4.2.20 |
Technical documentation for Maintenance |
1.1.5 1.1.1 |
|
|
|
|
3.2.
Specific Aspects of the Control-Command and Signalling Subsystems
3.2.1.
Safety
3.2.2.
Reliability and Availability
3.2.3.
Technical Compatibility
3.2.3.1.
Engineering Compatibility
3.2.3.1.1.
Physical environmental conditions
3.2.3.1.2.
Railway Internal Electromagnetic Compatibility
3.3.
Essential requirements not directly covered by this TSI
3.3.1.
Safety
3.3.2.
Health
3.3.3.
Environmental Protection
3.3.4.
Technical Compatibility
3.3.4.1.
Railway Internal Electromagnetic Compatibility
3.3.5.
Accessibility
4. CHARACTERISATION OF THE SUBSYSTEMS
4.1.
Introduction
4.1.1.
Basic parameters
4.1.2.
Overview of the requirements
4.1.3.
Parts of Control-command and Signalling Subsystems
|
Subsystem |
Part |
Basic parameters |
|
Control-Command and Signalling On-board |
Train protection |
4.2.1, 4.2.2, 4.2.5, 4.2.6, 4.2.8, 4.2.9, 4.2.12, 4.2.14, 4.2.16, 4.2.17, 4.2.20 |
|
Voice radio communication |
4.2.1.2, 4.2.4.1, 4.2.4.2, 4.2.5.1, 4.2.13, 4.2.16, 4.2.17, 4.2.20 |
|
|
Data radio communication |
4.2.1.2, 4.2.4.1, 4.2.4.3, 4.2.5.1, 4.2.6.2, 4.2.16, 4.2.17, 4.2.20 |
|
|
Automated Train Operation |
4.2.1.2, 4.2.5.1, 4.2.6, 4.2.12, 4.2.16, 4.2.18, 4.2.20 |
|
|
Control-Command and Signalling Trackside |
Train protection |
4.2.1, 4.2.3, 4.2.5, 4.2.7, 4.2.8, 4.2.9, 4.2.15, 4.2.16, 4.2.17, 4.2.20 |
|
Voice radio communication |
4.2.1.2, 4.2.4, 4.2.5.1, 4.2.7, 4.2.16, 4.2.17, 4.2.20 |
|
|
Data radio communication |
4.2.1.2, 4.2.4, 4.2.5.1, 4.2.7, 4.2.16, 4.2.17, 4.2.20 |
|
|
Train detection |
4.2.10, 4.2.11 |
|
|
Automated Train Operation |
4.2.1.2, 4.2.5.1, 4.2.7, 4.2.16, 4.2.19, 4.2.20 |
4.2.
Functional and technical specifications of the Subsystems
4.2.1.
Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability
4.2.1.1.
Safety
4.2.1.2.
Availability/Reliability
4.2.2.
On-Board ETCS functionality
4.2.3.
Trackside ETCS functionality
4.2.4.
Mobile communication functions for railways RMR
4.2.4.1.
Basic communication function
4.2.4.1.1.
GSM-R Basic communication function
4.2.4.1.2.
FRMCS Basic communication function
4.2.4.2.
Voice and operational communication applications
4.2.4.2.1.
GSM-R Voice and operational communication applications
4.2.4.2.2.
FRMCS Voice and operational communication applications
4.2.4.3.
Data communication applications for ETCS and ATO
4.2.4.3.1.
Data communication for ETCS
4.2.4.3.1.1. GSM-R data communication for ETCS
4.2.4.3.1.2. FRMCS data communication for ETCS
4.2.4.3.2.
Data communication for ATO
4.2.4.3.2.1. GSM-R data communication for ATO
4.2.4.3.2.2. FRMCS data communication for ATO
4.2.5.
RMR, ETCS and ATO air gap interfaces
4.2.5.1.
RMR air gap interface
4.2.5.1.1.
RMR general air gap interface
4.2.5.1.1.1. GSM-R air gap interface
4.2.5.1.1.2. FRMCS air gap interface
4.2.5.1.2.
RMR air gap interface for ETCS application
4.2.5.1.2.1. GSM-R air gap interface for the ETCS application
4.2.5.1.2.2. FRMCS air gap interface for the ETCS application
4.2.5.1.3.
RMR air gap interface for ATO application
4.2.5.1.3.1. GSM-R air gap interface for ATO application
4.2.5.1.3.2. FRMCS air gap interface for ATO application
4.2.5.2.
Eurobalise communication with the train for ERTMS applications
4.2.5.3.
Euroloop communication with the train for ERTMS applications
4.2.6.
On-Board Interfaces Internal to Control-Command and Signalling
4.2.6.1.
ETCS and Class B train protection
4.2.6.2.
Interface between RMR Data Communication and ETCS/ATO-applications
4.2.6.2.1.
Interface between RMR Data Communication and ETCS
4.2.6.2.1.1. Interface between GSM-R Data Communication and ETCS
4.2.6.2.1.2. Interface between FRMCS Data Communication and ETCS
4.2.6.2.2.
Interface between RMR Data Communication and ATO
4.2.6.2.2.1. Interface between GSM-R Data Communication and ATO
4.2.6.2.2.2. Interface between FRMCS Data Communication and ATO
4.2.6.2.3.
Interface between FRMCS on-board voice application and on-board FRMCS
4.2.6.3.
Odometry
4.2.6.4.
Interface between ATO and ETCS
4.2.6.5.
Additional CCS On-Board Internal Interfaces
4.2.6.5.1.
CCS Consist network communication layers
4.2.7.
Trackside Interfaces Internal to Control-Command and Signalling
4.2.7.1.
Functional interface between RBCs
4.2.7.2.
RBC/RBC
4.2.7.3.
RMR/trackside ETCS and RMR/trackside ATO
4.2.7.3.1.
RMR/trackside ETCS
4.2.7.3.1.1. GSM-R/trackside ETCS
4.2.7.3.1.2. FRMCS/trackside ETCS
4.2.7.3.2.
RMR/trackside ATO
4.2.7.3.2.1. GSM-R/trackside ATO
4.2.7.3.2.2. FRMCS/trackside ATO
4.2.7.4.
Eurobalise/LEU
4.2.7.5.
Euroloop/LEU
4.2.8.
Key Management
4.2.9.
ETCS-ID Management
4.2.10.
Trackside Train Detection Systems
4.2.11.
Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling trackside equipment
4.2.12.
ETCS DMI (Driver-Machine Interface)
4.2.13.
RMR DMI (Driver-Machine Interface)
4.2.13.1.
GSM-R DMI (Driver Machine Interface)
4.2.13.2.
FRMCS DMI (Driver Machine Interface)
4.2.14.
Interface to Data Recording for Regulatory Purposes
4.2.15.
Trackside Control-Command and Signalling objects
4.2.16.
Construction of equipment used in CCS subsystems
4.2.17.
ETCS and Radio System Compatibility
4.2.17.1.
ETCS System Compatibility
4.2.17.2.
Requirements for ETCS System Compatibility
4.2.17.3.
Radio System Compatibility
4.2.17.4.
Requirements for Radio System Compatibility
4.2.18.
On-Board ATO functionality
4.2.19.
Trackside ATO functionality
4.2.20.
Technical documentation for Maintenance
4.2.20.1.
Responsibility of the manufacturer of equipment
4.2.20.2.
Responsibility of the applicant for subsystem verification
4.2.20.3.
System identifier
4.3.
Functional and technical specifications of the interfaces to other Subsystems
4.3.1.
Interface to the Operation and Traffic Management Subsystem
|
Interface with Operation and Traffic Management TSI |
|||
|
Reference CCS TSI |
|
Reference Operation and Traffic Management TSI(10) |
|
|
Parameter |
Point |
Parameter |
Point |
|
Operating rules List of harmonised text indications and messages displayed on the ETCS Driver Machine Interface |
4.4 Appendix E |
Driver’s Rule book Operating rules ERTMS trackside engineering information relevant to operation |
4.2.1.2.1 4.4 Appendix D3 |
|
Trackside Control-Command and Signalling objects |
4.2.15 |
Requirements for signal and line-side marker sighting |
4.2.2.8 |
|
Train braking performance and characteristics |
4.2.2 |
Train braking |
4.2.2.6 |
|
Use of sanding equipment On-board flange lubrication Use of composite brake blocks |
4.2.10 |
Driver’s Rule book |
4.2.1.2.1 |
|
Interface to Data Recording for Regulatory Purposes |
4.2.14 |
Data recording |
4.2.3.5 |
|
ETCS DMI (Driver-Machine Interface) |
4.2.12 |
Format of train running number |
4.2.3.2.1 |
|
RMR DMI (Driver-Machine Interface) |
4.2.13 |
Format of train running number |
4.2.3.2.1 |
|
Key Management |
4.2.8 |
Ensuring that the train is in running order |
4.2.2.7 |
|
Route compatibility checks before the use of authorised vehicles |
4.9 |
Parameters for the vehicle and train compatibility over the route intended for operation |
Appendix D1 |
4.3.2.
Interface to the Rolling Stock Subsystem
|
Interface with Rolling Stock TSIs |
||||
|
Reference CCS TSI |
Reference Rolling Stock TSIs |
|||
|
Parameter |
Point |
Parameter |
|
Point |
|
Compatibility with trackside train detection systems: vehicle design |
4.2.10 |
Rolling stock characteristics to be compatible with train detection systems based on track circuits |
LOC & PAS TSI |
4.2.3.3.1.1 |
|
Wagon TSI(11) |
4.2.3.2 |
|||
|
Rolling stock characteristics to be compatible with train detection systems based on axle counters |
LOC & PAS TSI |
4.2.3.3.1.2 |
||
|
Wagon TSI |
4.2.3.3 |
|||
|
Rolling stock characteristics to be compatible with loop equipment |
LOC & PAS TSI |
4.2.3.3.1.3 |
||
|
Wagon TSI |
4.2.3.3 |
|||
|
Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling trackside equipment |
4.2.11 |
Rolling stock characteristics to be compatible with train detection systems based on track circuits |
LOC & PAS TSI |
4.2.3.3.1.1 |
|
Wagon TSI |
4.2.3.3 |
|||
|
Rolling stock characteristics to be compatible with train detection systems based on axle counters |
LOC & PAS TSI |
4.2.3.3.1.2 |
||
|
Wagon TSI |
4.2.3.3 |
|||
|
Train braking performance and characteristics |
4.2.2 4.2.18 |
Braking performance |
LOC & PAS TSI Emergency braking |
4.2.4.5.2 |
|
LOC & PAS TSI Service braking |
4.2.4.5.3 |
|||
|
Wagon TSI |
4.2.4.1.2 |
|||
|
Position of Control-Command and Signalling on-board antennas |
4.2.2 |
Kinematic gauge |
LOC & PAS TSI |
4.2.3.1 |
|
Wagon TSI |
None |
|||
|
Isolation of on-board ETCS functionality |
4.2.2 |
Operating rules |
LOC & PAS TSI |
4.2.12.3 |
|
Wagon TSI |
None |
|||
|
Trackside Control-Command and Signalling objects |
4.2.15 |
External visibility Head lights |
LOC & PAS TSI |
4.2.7.1.1 |
|
Wagon TSI |
None |
|||
|
Driver’s external field of view |
LOC & PAS TSI Line of sight |
4.2.9.1.3.1 |
||
|
LOC & PAS TSI Windscreen |
4.2.9.2 |
|||
|
Wagon TSI |
None |
|||
|
Interface to Data Recording for Regulatory Purposes |
4.2.14 |
Recording device |
LOC & PAS TSI |
4.2.9.6 |
|
Wagon TSI |
None |
|||
|
ETCS on-board: Forwarding information/orders and receiving state information from rolling stock |
4.2.2 |
Separation sections |
LOC & PAS TSI |
4.2.8.2.9.8 |
|
Wagon TSI |
None |
|||
|
Dynamic braking command |
LOC&PAS TSI |
4.2.4.4.4 |
||
|
Wagon TSI |
None |
|||
|
Magnetic track brake |
LOC&PAS TSI |
4.2.4.8.2 |
||
|
Wagon TSI |
None |
|||
|
Eddy current track brake |
LOC&PAS TSI |
4.2.4.8.3 |
||
|
Wagon TSI |
None |
|||
|
Maximum power and current from the overhead contact line |
LOC&PAS TSI |
4.2.8.2.4 |
||
|
Wagon TSI |
None |
|||
|
Door opening |
LOC&PAS TSI |
4.2.5.5.6 |
||
|
Wagon TSI |
None |
|||
|
Requirements on performance |
LOC&PAS TSI |
4.2.8.1.2 |
||
|
Wagon TSI |
None |
|||
|
Smoke control |
LOC&PAS TSI |
4.2.10.4.2 |
||
|
Wagon TSI |
None |
|||
|
Radio Remote control function by staff for shunting operation |
LOC&PAS TSI |
4.2.9.3.6 |
||
|
Wagon TSI |
None |
|||
|
Driver's desk – Ergonomics |
LOC&PAS TSI |
4.2.9.1.6 |
||
|
Wagon TSI |
None |
|||
|
Requirements for management of ETCS modes: sleeping mode |
LOC&PAS TSI |
4.2.9.3.7.1 |
||
|
Wagon TSI |
None |
|||
|
Requirements for management of ETCS modes: passive shunting |
LOC&PAS TSI |
4.2.9.3.7.2 |
||
|
Wagon TSI |
None |
|||
|
Requirements for management of ETCS modes: non leading |
LOC&PAS TSI |
4.2.9.3.7.3 |
||
|
Wagon TSI |
None |
|||
|
Type of brake system |
LOC&PAS TSI |
4.2.4.3 |
||
|
Wagon TSI |
None |
|||
|
Traction Status |
LOC&PAS TSI |
4.2.9.3.8 |
||
|
Wagon TSI |
None |
|||
|
Running dynamic behaviour |
LOC&PAS TSI |
4.2.3.4.2 |
||
|
Wagon TSI |
None |
|||
|
ATO on-board: Forwarding information/orders and receiving state information from rolling stock |
4.2.18 |
Interface requirements with Automated Train Operation onboard |
LOC & PAS TSI |
4.2.13 |
|
Wagon TSI |
None |
|||
|
Emergency braking command |
4.2.2 |
Emergency braking command |
LOC & PAS TSI |
4.2.4.4.1 |
|
Wagon TSI |
None |
|||
|
Construction of equipment used in CCS subsystems |
4.2.16 |
Material requirements |
LOC&PAS TSI |
4.2.10.2.1 |
|
Wagon TSI |
None |
|||
|
Service braking command |
4.2.2 |
Service braking command |
LOC & PAS TSI |
4.2.4.4.2 |
|
Wagon TSI |
None |
|||
4.3.3.
Interfaces to Infrastructure Subsystem
|
Interface with Infrastructure TSI |
||||
|
Reference CCS TSI |
|
Reference Infrastructure TSI |
|
|
|
Parameter |
Point |
Parameter |
|
Point |
|
Eurobalise communication (space for installation) |
4.2.5.2 |
Structure gauge |
INF TSI(12) |
4.2.3.1 |
|
Euroloop communication (space for installation) |
4.2.5.3 |
Structure gauge |
INF TSI |
4.2.3.1 |
|
Trackside Control-Command and Signalling objects |
4.2.15 |
Structure gauge |
INF TSI |
4.2.3.1 |
4.3.4.
Interfaces to Energy Subsystem
|
Interface with Energy TSI |
||||
|
Reference CCS TSI |
|
Reference Energy TSI |
|
|
|
Parameter |
Point |
Parameter |
|
Point |
|
Commands to rolling stock equipment |
4.2.2 4.2.3 |
Phase separation sections System separation sections |
ENE TSI(13) |
4.2.15 4.2.16 |
4.4.
Operating rules
4.5.
Maintenance rules
4.6.
Professional competences
4.7.
Health and safety conditions
4.8.
Registers
4.9.
Route compatibility checks before the use of authorised vehicles
5. INTEROPERABILITY CONSTITUENTS
5.1.
Definition
5.2.
List of interoperability constituents
5.2.1.
Basic interoperability constituents
5.2.2.
Grouping of interoperability constituents
5.3.
Constituents’ performance and specifications
|
No |
Interoperability constituent (IC) |
Characteristics |
Specific requirements to be assessed by reference to Chapter 4 |
||||||||||||||||||||
|
1 |
ETCS on-board |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
On-board ETCS functionality (excluding odometry) System identifier |
4.2.2 4.2.20.3 |
||||||||||||||||||||||
|
ETCS air gap interfaces
|
4.2.5 4.2.5.1.2 4.2.5.1.2.1 4.2.5.2 4.2.5.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.6.1 4.2.6.2.1.1 4.2.6.2.1.2 4.2.8 4.2.9 4.2.12 4.2.2 4.2.14 4.2.6.4 4.2.6.5.1 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
ETCS System Compatibility (ESC) (optional) |
4.2.17.1 4.2.17.2 |
||||||||||||||||||||||
|
2 |
Odometry equipment |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
On-board ETCS functionality: only Odometry |
4.2.2 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
3 |
Standardised interface STM |
Interfaces
|
4.2.6.1 |
||||||||||||||||||||
|
4 |
GSM-R voice cab radio
|
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
Basic communication functions |
4.2.4.1.1 |
||||||||||||||||||||||
|
Voice and operational communication applications System identifier |
4.2.4.2.1 4.2.20.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.5.1.1.1 4.2.13.1 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
||||||||||||||||||||||
|
5 |
GSM-R data radio
|
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
Basic communication functions |
4.2.4.1.1 |
||||||||||||||||||||||
|
ETCS data communication applications System identifier |
4.2.4.3.1.1 4.2.20.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.6.2.1.1 4.2.6.2.2.1 4.2.5.1.1.1 4.2.5.1.2.1 4.2.5.1.3.1 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
||||||||||||||||||||||
|
6 |
GSM-R SIM card
|
Basic communication functions System identifier |
4.2.4.1.1 4.2.20.3 |
||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
||||||||||||||||||||||
|
7 |
ATO On-Board |
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
On-board ATO functionality (excluding communication) System identifier |
4.2.18 4.2.20.3 |
||||||||||||||||||||||
|
ATO air gap interfaces |
4.2.5.1.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.6.2.2.1 4.2.6.2.2.2 4.2.18 4.2.6.4 4.2.6.5.1 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
8 |
FRMCS On-Board voice application |
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
Basic communication functions |
4.2.4.1.2 |
||||||||||||||||||||||
|
Voice and operational communication applications System identifier |
4.2.4.2.2 4.2.20.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.6.2.3 4.2.13.2 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
||||||||||||||||||||||
|
9 |
On-board FRMCS |
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||||||||||||||
|
Basic communication functions System identifier |
4.2.4.1.2 4.2.20.3 |
||||||||||||||||||||||
|
Interfaces
|
4.2.6.2.3 4.2.5.1.1.2 4.2.5.1.2.2 4.2.5.1.3.2 4.2.6.2.1.2 4.2.6.2.2.2 4.2.6.5.1 |
||||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
||||||||||||||||||||||
|
10 |
FRMCS Profile
|
Basic communication functions System identifier |
4.2.4.1.2 4.2.20.3 |
||||||||||||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||||||||||||||
|
Radio System Compatibility (RSC) (optional) |
4.2.17.3 4.2.17.4 |
|
1 |
2 |
3 |
4 |
||||||||
|
No |
Interoperability Constituent (IC) |
Characteristics |
Specific requirements to be assessed by reference to Chapter 4 |
||||||||
|
1 |
RBC |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
Trackside ETCS functionality (excluding communication via Eurobalises, radio infill and Euroloop) System identifier |
4.2.3 4.2.20.3 |
||||||||||
|
RMR, ETCS and ATO air gap interfaces: only radio communication with train
|
4.2.5.1.2.1 4.2.5.1.2.2 |
||||||||||
|
Interfaces
|
4.2.7.1, 4.2.7.2 4.2.7.3.1.1 4.2.7.3.1.2 4.2.8 4.2.9 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
2 |
Radio infill unit |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
Trackside ETCS functionality (excluding communication via Eurobalises, Euroloop and level 2 functionality) System identifier |
4.2.3 4.2.20.3 |
||||||||||
|
RMR, ETCS and ATO air gap interfaces: only radio communication with train
|
4.2.5.1.2.1 |
||||||||||
|
Interfaces
|
4.2.7.3 4.2.8 4.2.9 4.2.3 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
3 |
Eurobalise |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
ETCS and RMR air gap interfaces: only Eurobalise communication with train System identifier |
4.2.5.2 4.2.20.3 |
||||||||||
|
Interfaces
|
4.2.7.4 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
4 |
Euroloop |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
ETCS and RMR air gap interfaces: only Euroloop communication with train System identifier |
4.2.5.3 4.2.20.3 |
||||||||||
|
Interfaces
|
4.2.7.5 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
5 |
LEU Eurobalise |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
Trackside ETCS functionality (excluding communication via radio infill, Euroloop and level 2 functionality) System identifier |
4.2.3 4.2.20.3 |
||||||||||
|
Interfaces
|
4.2.7.4 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
6 |
LEU Euroloop |
Reliability, Availability, Maintainability, Safety (RAMS):
|
4.2.1.1 4.2.1.2 4.2.20.1 |
||||||||
|
Trackside ETCS functionality (excluding communication via radio infill, Eurobalise and level 2 functionality) System identifier |
4.2.3 4.2.20.3 |
||||||||||
|
Interfaces
|
4.2.7.5 |
||||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
7 |
Axle Counter |
Trackside train detection systems (only parameters relevant for axle counters) |
4.2.10 |
||||||||
|
Electromagnetic compatibility (only parameters relevant for axle counters) |
4.2.11 |
||||||||||
|
8 |
Marker Board |
Trackside Control-Command and Signalling objects (only points 1 and 2) |
4.2.15 |
||||||||
|
Construction of equipment |
4.2.16 |
||||||||||
|
9 |
ATO Trackside |
Reliability, Availability, Maintainability (RAM):
|
4.2.1.2 4.2.20.1 |
||||||||
|
Trackside ATO functionality System identifier |
4.2.19 4.2.20.3 |
||||||||||
|
RMR, ETCS and ATO air gap interfaces: only radio communication with train
|
4.2.5.1.3.1 4.2.5.1.3.2 |
||||||||||
|
Interfaces:
|
4.2.7.3.2.1 4.2.7.3.2.2 |
||||||||||
|
Construction of equipment |
4.2.16 |
6. ASSESSING THE CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFYING THE SUBSYSTEMS
6.1.
Introduction
6.1.1.
General principles
6.1.1.1.
Compliance with basic parameters
6.1.1.2.
Partial fulfilment of TSI requirements
6.1.2.
Principles for testing ETCS, ATO and RMR
6.1.2.1.
Principle
6.1.2.2.
Operational test scenarios
6.1.2.3.
Requirements for Operational test scenarios
6.2.
Interoperability constituents
6.2.1.
Assessment procedures for Control-Command and Signalling Interoperability Constituents
6.2.2.
Modules for Control-Command and Signalling Interoperability Constituents
6.2.3.
Assessment requirements
|
No |
Aspect |
What to assess |
Supporting evidence |
||||||||||||||||||||||||
|
1a |
Functions, interfaces and performances |
Check that all mandatory functions, interfaces and performances as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI. |
Design documentation and running of test cases and test sequences, as described in the basic parameters referenced in the relevant table of Chapter 5. |
||||||||||||||||||||||||
|
1b |
Check which optional functions and interfaces as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI. |
Design documentation and running of test cases and test sequences, as described in the basic parameters referenced in the relevant table of Chapter 5. |
|||||||||||||||||||||||||
|
1c |
Check which additional functions and interfaces (not specified in this TSI) are implemented and that they do not lead to conflicts with implemented functions specified in this TSI. |
Impact analysis. |
|||||||||||||||||||||||||
|
2a |
Construction of equipment |
Check compliance with mandatory conditions, where specified in the basic parameters referenced in the relevant table of Chapter 5. |
Documentation on material used and, where necessary, tests to ensure that the requirements of the basic parameters referenced in the relevant table of Chapter 5 are satisfied. |
||||||||||||||||||||||||
|
2b |
In addition, check that the interoperability constituent functions correctly in the environmental conditions for which it is designed. |
Tests according to the applicant’s specifications. |
|||||||||||||||||||||||||
|
3 |
Reliability, Availability, Maintainability, Safety (RAMS) |
Check compliance with the safety requirements where specified in the basic parameters referenced in the relevant table of Chapter 5, i.e.
|
|
||||||||||||||||||||||||
|
4 |
Check that the quantitative reliability target (related to random failures) indicated by the applicant is met. |
Calculations |
|||||||||||||||||||||||||
|
5 |
Elimination of systematic failures. |
Tests of equipment (full Interoperability Constituent or separately for subassemblies) in operational conditions, with repair when defects are detected. Documentation accompanying the certificate which indicates which kind of verifications have been performed, which standards have been applied and criteria adopted to consider these tests completed (according to decisions of the applicant). |
|||||||||||||||||||||||||
|
6 |
Technical documentation for maintenance |
Check compliance with maintenance requirements – point 4.2.20.1. |
Document check |
6.2.4.
Special issues
6.2.4.1.
Mandatory tests for the on-board ETCS
6.2.4.2.
Class B interfaces
6.2.4.3.
ETCS and radio system compatibility checks for Interoperability Constituent
|
No |
Aspect |
What to assess |
Supporting evidence |
|
1 |
Availability of the results |
Assess that the check report gives reference to the checks according to the definition of the ESC/RSC types in the technical document published by ERA(19). Assess that the Interoperability Constituent check report clearly indicates which checks have been verified for the ESC/RSC Type. |
Evaluation of the ESC/RSC Check Report. |
|
2 |
Availability of the results |
Assess that ESC/RSC results indicate for every ESC/RSC Check whether the ESC/RSC Check was passed as specified or not. |
Evaluation of the ESC/RSC Check Report. |
|
3 |
Incompatibilities and errors reported |
Assess that for every ESC/RSC Check which was not passed as specified, the incompatibilities and errors reported during ESC/RSC Checks are stated. |
Evaluation of the ESC/RSC Check Report. |
|
4 |
Impact analysis |
Assess that for every ESC/RSC Check which was not passed as specified, an impact analysis of the effects on ESC/RSC has been performed and recorded using the template provided in the Appendix D. |
Evaluation of the ESC/RSC Check Report. |
6.3.
Control-Command and Signalling Subsystems
6.3.1.
Assessment procedures for Control-Command and Signalling Subsystems
6.3.2.
Modules for Control-Command and Signalling Subsystems
6.3.2.1.
On-board Subsystem
6.3.2.2.
Trackside Subsystem
6.3.2.3.
Conditions for using modules for On-board and Trackside Subsystems
6.3.3.
Assessment requirements for an On-board Subsystem
|
No |
Aspect |
What to assess |
Supporting evidence |
||||
|
1a |
Use of interoperability constituents |
Check whether the interoperability constituents to be integrated into the subsystem are all covered by an ‘EC’ Declaration of conformity and a corresponding certificate. The Subsystem needs to be checked with a SIM card compliant with the requirements of this TSI. Changing the SIM card with another one compliant with the TSI is not a modification of the Subsystem. |
Existence and content of documents. |
||||
|
1b |
Check conditions and limits of use on the use of Interoperability Constituents against the characteristics of the subsystem and of the environment |
Analysis by document check. |
|||||
|
1c |
For interoperability constituents that have been certified against a version of the CCS TSI, which is different from the version applied for the ‘EC’ Verification of the subsystem and/or against a set of specifications which is different from the set of specifications applied for the ‘EC’ Verification of the subsystem, check that the certificate still ensures subsystem compliance with the requirements of the TSI currently in force. |
Impact analysis by document checks. |
|||||
|
2a |
Integration of interoperability constituents in the subsystem |
Check the correct installation and functioning of the internal interfaces of the subsystem – Basic parameter 4.2.6. |
Checks according to specifications. |
||||
|
2b |
Check that additional functions (not specified in this TSI) do not impact the mandatory ones. |
Impact analysis. |
|||||
|
2c |
Check that the values of ETCS IDs are within the allowed range and, if required by this TSI, have unique values – Basic parameter 4.2.9. |
Check of design specifications. |
|||||
|
2d |
Check that there is a system identifier for ETCS part of the subsystem. In case of modification of the functional or realisation part of the system identifier, that the modification corresponds to the definition – Basic Parameter 4.2.20.3. |
Document check. |
|||||
|
3 |
Integration of parts in the subsystem |
Check the interfaces and integration between the different parts of the subsystem – Table 4.1 and Basic parameter 4.2.6. |
Impact analysis by document checks. |
||||
|
4a |
Integration with rolling stock |
Check the correct installation of equipment – Basic Parameters 4.2.2, 4.2.4, 4.2.14, 4.2.18 and conditions for installation of equipment, as specified by the manufacturer. |
Results of checks (according to specifications referenced in the Basic Parameters and the manufacturer's installation rules). |
||||
|
4b |
Check that the Control-Command and Signalling On-board Subsystem is compatible with the rolling stock environment – Basic parameter 4.2.16. |
Document check (certificates of interoperability constituents and possible integration methods checked against characteristics of rolling stock). |
|||||
|
4c |
Check that parameters (e.g. braking parameters) are correctly configured and that they are within the allowed range. |
Document check (values of parameters checked against characteristics of rolling stock). |
|||||
|
5a |
Integration with Class B, depending on ETCS on-board and Class B interface |
Check that the standardised interface STM is connected to on-board ETCS with TSI-compliant interfaces. |
Nothing to test: there is a standard interface already tested at interoperability constituent level. Its functioning has already been tested when checking the integration of interoperability constituents in the subsystem. |
||||
|
5b |
Check that Class B functions implemented in the on-board ETCS– Basic parameter 4.2.6.1 – create no additional requirements for the Control-Command and Signalling Trackside Subsystem due to transitions. |
Nothing to test: everything has already been tested at interoperability constituent level. |
|||||
|
5c |
Check that separate Class B equipment which is not connected to the on-board ETCS– Basic Parameter 4.2.6.1 – creates no additional requirements for Control-Command and Signalling Trackside Subsystem due to transitions. |
Nothing to test: no interface(20). |
|||||
|
5d |
Check that separate Class B equipment connected on-board ETCS using (partly) non TSI compliant interfaces – basic parameter 4.2.6.1 – creates no additional requirements for the Control-Command and Signalling Trackside Subsystem due to transitions. Also check that ETCS functions are not affected. |
Impact analysis by document check and integration tests report. |
|||||
|
6a |
Integration with Control-Command and Signalling Trackside Subsystems |
Check that Eurobalise telegrams can be read (scope of this test is limited to checking that the antenna has been appropriately installed. The tests already carried out at Interoperability Constituent level shall not be repeated) – Basic Parameter 4.2.5. |
Test using a certified Eurobalise: the ability to read correctly the telegram is the supporting evidence. |
||||
|
6b |
Check that Euroloop telegrams (if applicable) can be read – Basic Parameter 4.2.5. |
Test using a certified Euroloop: the ability to read correctly the telegram is the supporting evidence. |
|||||
|
6c |
Check that the equipment can handle a RMR call for voice and data (if applicable) – Basic Parameter 4.2.5. |
Test with a certified RMR network. The ability to set up, maintain and disconnect a connection is the supporting evidence. |
|||||
|
7a |
Reliability, Availability, Maintainability, Safety (RAMS) |
Check that the equipment complies with safety requirements – Basic Parameter 4.2.1. |
Application of procedures specified in the Common Safety Method for Risk Evaluation and Assessment. |
||||
|
7b |
Check that the quantitative reliability target is met – Basic Parameter 4.2.1. |
Calculations. |
|||||
|
7c |
Check the compliance with requirements about maintenance – point 4.2.20.2. |
Documents check. |
|||||
|
8 |
Integration with Control-Command and Signalling Trackside Subsystems and other subsystems: tests under conditions representing the intended operation. |
Test the behaviour of the subsystem under as many different conditions as reasonably possible representing the intended operation (e.g. line gradient, train speed, vibrations, traction power, weather conditions, design of Control-Command and Signalling trackside functionality). The test must be able to verify:
These tests must also be such as to increase confidence that there will be no systematic failures. The scope of these tests excludes tests already carried out at different stages: tests performed on the interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. Tests under environmental conditions are not necessary for on-board RMR voice equipment. Note: Indicate in the certificate which conditions have been tested and which standards have been applied. |
Reports of test runs. |
6.3.3.1.
ETCS and radio system compatibility checks
|
No |
Aspect |
What to assess |
Supporting evidence |
|
1 |
Availability of the results |
Assess that the check report gives reference to the checks according to the definition of the ESC/RSC types in the technical document published by ERA(21). Assess that all required ESC/RSC checks of that ESC/RSC type have been evaluated. |
Evaluation of the ESC/RSC Check Report. |
|
2 |
Availability of the results |
Assess that ESC/RSC results indicate for every ESC/RSC Check whether the ESC/RSC Check was passed as specified or not. |
Evaluation of the ESC/RSC Check Report. |
|
3 |
Incompatibilities and errors reported |
Assess that for every ESC/RSC Check which was not passed as specified, the incompatibilities and errors reported during ESC/RSC Checks are stated. |
Evaluation of the ESC/RSC Check Report. |
|
4 |
Impact analysis |
Assess that for every ESC/RSC Check which was not passed as specified, an impact analysis of the effects on ESC/RSC has been performed and recorded using the template provided in the Appendix D. |
Evaluation of the ESC/RSC Check Report. |
|
5 |
Conditions |
Assess that all conditions are referred to in the check report. |
Evaluation of the ESC/RSC Check Report. |
|
6 |
Integration of ESC/RSC Interoperability Constituent Statements |
Assess that if the ESC/RSC statement is based on ESC/RSC Interoperability Constituent statements, the results from ESC/RSC Interoperability Constituent Statement are applicable to the concerned subsystem. |
Evaluation of the ESC/RSC Check Report. |
6.3.4.
Assessment requirements for a Trackside Subsystem
|
No |
Aspect |
What to assess |
Supporting evidence |
||||||
|
1a |
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. |
||||||
|
1b |
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. |
|||||||
|
1c |
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. |
|||||||
|
2a |
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 Interoperability Constituent axle counter and Marker Boards) |
Checks according to specifications. |
||||||
|
2b |
Check that additional functions (not specified in this TSI) do not impact the mandatory ones. (N/A for Interoperability Constituent axle counter and Marker Boards) |
Impact analysis. |
|||||||
|
2c |
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 Interoperability Constituent axle counter and Marker Boards) |
Check of design specifications. |
|||||||
|
2d |
For Interoperability Constituent axle counters (only): The integration of the Interoperability Constituent in the subsystem has to be verified: Check index 77 document Chapter 4, table 16 ‘conformity assessment’. Check the correct installation of equipment and conditions specified by the manufacturer and/or the infrastructure manager. |
Document check. |
|||||||
|
2e |
Check that there is a system identifier for the ETCS part of the subsystem. In case of modification of the functional or realisation part of the system identifier, that the modification corresponds to the definition – Basic Parameter 4.2.20.3. |
Document check. |
|||||||
|
3 |
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, the positioning of interoperable marker boards to meet their intended operational purpose) – Basic parameter 4.2.15. |
Design documentation, results of tests or test runs with TSI compliant rolling stock. |
||||||
|
4a |
Integration with infrastructure |
Check that the ETCS, RMR and ATO equipment has been properly installed – Basic parameters 4.2.3, 4.2.4, 4.2.19 and conditions for installation specified by the manufacturer. |
Results of checks (according to specifications referenced in the basic parameters and manufacturer's installation rules). |
||||||
|
4b |
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). |
|||||||
|
5a |
Integration with trackside signalling (not applicable for train detection part) |
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). |
||||||
|
5b |
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). |
|||||||
|
5c |
Check that the interfaces are correctly installed and function properly. |
Design verification and tests according to information supplied by the applicant. |
|||||||
|
5d |
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. |
|||||||
|
6a |
Integration with Control-Command and Signalling On-board Subsystems |
Check the RMR coverage – Basic Parameter 4.2.4. |
On site measurements. |
||||||
|
6b |
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 index 77 document Chapter 4. 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. |
||||||
|
8a |
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. |
||||||
|
8b |
Check that quantitative reliability targets are respected – Basic Parameter 4.2.1.2. |
Calculations. |
|||||||
|
8c |
Check the compliance with requirements about maintenance – point 4.2.20.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:
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.
|
Reports of test runs. |
||||||
|
10 |
ETCS and radio System Compatibility |
The proposed ESC and RSC checks are only covering TSI requirements and are in line with the specifications – Basic Parameter 4.2.17. |
Document check of the envisaged ESC/RSC types in case they are new or modified. OR The technical compatibility checks for ESC and RSC Type(s) are published as ‘Valid’ in the Agency ESC/RSC technical document, if they remain unchanged. |
6.4.
Provisions in case of the partial assessment of TSI requirements
6.4.1.
Assessment of parts of control-command and signalling subsystems
6.4.2.
Intermediate Statement of Verification
6.5.
Management of errors
6.5.1.
Content of EC certificates
6.5.2.
Content of EC declarations
7. IMPLEMENTING THE TSI CONTROL-COMMAND AND SIGNALLING
7.1.
Introduction
7.2.
Generally applicable rules
7.2.1.
Upgrading or renewing the Control-Command Subsystems or parts of them
7.2.2.
Changes to an existing On-Board subsystem
7.2.2.1.
Rules to manage changes in on-board CCS subsystems
|
|
|
|
|
||||||||||
|
ETCS equipment on-board and the set of specification of CCS TSI Appendix A |
Not applicable |
Not applicable |
Use another Appendix A set of specifications. |
||||||||||
|
|
Envelope of legally operated ETCS system versions |
Not applicable |
Not applicable |
Installation or start the operational use of ETCS; Modification of the envelope of legally operated ETCS system versions from set of specifications in Appendix A. |
||||||||||
|
|
ETCS On-board implementation |
Fulfilling all the conditions in point 7.2.2.2 (change of realisation identifier) |
Not applicable |
Not fulfilling all the conditions in point 7.2.2.2 (change of functional identifier) |
||||||||||
|
|
Managing information about the completeness of the train (not from driver) |
Not applicable |
Adding or removing train integrity supervision |
Not applicable |
||||||||||
|
|
Safe consist length information from on-board necessary to access the line and SIL |
Not applicable |
Adding or removing safe consist length information |
Not applicable |
||||||||||
|
ETCS System Compatibility |
Not applicable |
Adding or removing an ESC statement fulfilling all the conditions in point 7.2.2.4. |
Adding or removing an ESC statement not fulfilling all the conditions in point 7.2.2.4. |
||||||||||
|
GSM-R Radio voice on board and its Baseline |
Usage of another Baseline fulfilling all the conditions in point 7.2.2.3 |
Not applicable |
Installation or start the operational use of GSM-R cab radio; Usage of another Baseline not fulfilling all the conditions in point 7.2.2.3. |
||||||||||
|
GSM-R Voice and operational communication implementation |
Fulfilling all the conditions in point 7.2.2.3 (change of realisation identifier) |
Not applicable |
Not fulfilling all the conditions in point 7.2.2.3 (change of functional identifier) |
|||||||||||
|
GSM-R Voice SIM Card support of Group ID 555 |
Not applicable |
Change the SIM Card support of Group ID 555 |
Not applicable |
|||||||||||
|
Radio Voice System Compatibility |
Not applicable |
Adding or removing an RSC statement fulfilling all the conditions in point 7.2.2.4. |
Adding or removing an RSC statement not fulfilling all the conditions in point 7.2.2.4. |
||||||||||
|
GSM-R Radio Data communication on board and its Baseline |
Usage of another Baseline fulfilling all the conditions in point 7.2.2.3. |
Not applicable |
Installation or start the operational use of GSM-R EDOR; Usage another Baseline not fulfilling all the conditions in point 7.2.2.3. |
||||||||||
|
GSM-R Data communication for ETCS and ATO implementation |
Fulfilling all the conditions in point 7.2.2.3 (change of realisation identifier) |
Not applicable |
Not fulfilling all the conditions in point 7.2.2.3 (change of functional identifier) |
|||||||||||
|
Radio Data System Compatibility |
Not applicable |
Adding or removing an RSC statement fulfilling all the conditions in point 7.2.2.4. |
Adding or removing an RSC statement not fulfilling all the conditions in point 7.2.2.4. |
||||||||||
|
Voice 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 |
||||||||||
|
Data 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 |
|||||||||||
|
On-board ATO system version |
Not applicable |
Change of the ATO system version fulfilling all the conditions in point 7.2.2.3. |
Add or remove the ATO part of the CCS on-board subsystem; Start the operational use of ATO. Or change of the ATO system version not fulfilling all the conditions in point 7.2.2.3. |
||||||||||
|
On-board ATO implementation |
Fulfilling all the conditions in point 7.2.2.3 (change of realisation identifier) |
Not applicable |
Not fulfilling all the conditions in point 7.2.2.3 (change of functional identifier) |
|||||||||||
|
Class B or other train protection, control and warning legacy systems installed (system and, if applicable, version) |
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. |
||||||||||
|
Class B or other radio legacy systems installed (system and, if applicable, version) |
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. |
7.2.2.2.
Conditions for a change in the On-board ETCS functionality that does not impact the basic design characteristics
7.2.2.3.
Conditions for a change in the on-board mobile communication functions for railways or in the ATO on-board functionality that does not impact the basic design characteristics
7.2.2.4.
Conditions for a change in the on-board subsystem regarding ETCS or Radio system compatibility that does not impact the basic design characteristics
7.2.3.
Upgrade or renewal of existing trackside subsystem
7.2.3.1.
Rules to manage upgrade or renewal of existing trackside CCS subsystems
|
Basic Parameter |
Modification which requires a new authorisation |
|
|
4.2.3 |
Trackside ETCS functionality |
Not fulfilling all the conditions in point 7.2.3.2 |
|
4.2.4 4.2.4.2 |
Mobile communication functions for railways RMR Voice and operational communication applications |
Not fulfilling all the conditions in point 7.2.3.3 |
|
4.2.4 4.2.4.3 |
Mobile communication functions for railways RMR Data communication applications for ETCS and ATO |
Not fulfilling all the conditions in point 7.2.3.3 |
|
4.2.19 |
Trackside ATO functionality |
Not fulfilling all the conditions in point 7.2.3.3 |
7.2.3.2.
Conditions for an upgrade or renewal in the trackside ETCS functionality that, if not fulfilled, requires new authorisation for placing in service
7.2.3.3.
Conditions for an upgrade or renewal in the trackside mobile communication for railways or trackside ATO functionality that, if not fulfilled, requires a new authorisation for placing in service
7.2.3.4.
Impact on the technical compatibility between on-board and trackside parts of the CCS subsystems
7.2.4.
EC type or design examination certificates
7.2.4.1.
CCS On-Board Subsystem
7.2.4.1.1.
Definitions
7.2.4.1.2.
Rules related to the EC type or design examination certificate
7.2.4.1.3.
Validity of the EC type or design examination certificate
7.2.4.2.
CCS Trackside Subsystem
7.2.4.3.
Interoperability constituents
7.2.5.
Legacy systems
7.2.6.
Availability of Specific Transmission Modules and interfaces to Class B on-board
7.2.7.
Additional Class B equipment on a line equipped with Class A
7.2.8.
Vehicle with Class A and Class B equipment
7.2.9.
Conditions for mandatory and optional functions
7.2.9.1.
ETCS
7.2.9.2.
ATO
7.2.9.3.
RMR
7.2.10.
Specifications maintenance (error corrections)
7.2.10.1.
Responsibilities during the Change Control Management process
7.2.10.2.
On-board and Trackside Manufacturer responsibilities
7.2.10.3.
Infrastructure Manager and Railway Undertaking responsibilities
7.2.10.3.1.
Infrastructure Manager responsibilities
7.2.10.3.2.
Railway Undertakings responsibilities
7.3.
RMR specific implementation rules
7.3.1.
Trackside installations
7.3.1.1.
The fitting of GSM-R or FRMCS is mandatory when:
7.3.1.2.
GSM-R may only be taken out of operation when the following conditions are fulfilled:
7.3.1.3.
The trackside implementation of FRMCS only, without pre-existing GSM-R, is allowed if the following condition is fulfilled:
7.3.2.
On-board installations
7.4.
ETCS specific implementation rules
7.4.1.
Trackside installations
7.4.1.1.
High-speed network
7.4.1.2.
Set of specifications from previous versions of the CCS TSI.
7.4.1.3.
ETCS System Version implementation rules
7.4.2.
On-board installations
7.4.2.1.
Newly built vehicles
7.4.2.2.
Existing vehicles
7.4.2.3.
Rules for the extension of the area of use for existing vehicle
7.4.2.4.
ETCS System Version implementation rules
7.4.3.
National requirements
7.4.4.
National Implementation Plans
7.5.
ETCS and radio system compatibility checks implementation rules
7.6.
Train detection systems specific implementation rules
7.7.
Specific cases
7.7.1.
Introduction
7.7.2.
List of specific cases
7.7.2.1.
Belgium
|
Specific case |
Category |
Notes |
||
|
T |
Applicable on HS L1 Applicable on vehicles This Specific Case is linked with the use of TVM. |
||
|
T |
Applicable on HS L1, L2, L3, L4 Applicable on vehicles This Specific Case is linked with the use of TVM. |
7.7.2.2.
UK for Northern Ireland
|
Specific case |
Category |
Notes |
||||||
|
T |
Applicable in Northern Ireland |
||||||
|
T |
Applicable in Northern Ireland |
||||||
|
T |
|
||||||
|
T |
There is no impact on interoperability. |
||||||
|
T |
There is no impact on interoperability. |
7.7.2.3.
France
|
Specific case |
Category |
Notes |
||||
|
T2 |
Applicable on infrastructure Applicable on vehicles This Specific Case is linked with the use of track circuits using electrical joints. |
||||
|
T2 |
Applicable on infrastructure Applicable on vehicles This specific case may be revised when the open point related to the frequency management for track circuits is closed. |
||||
|
T |
Applicable on infrastructure Applicable on vehicles This Specific Case is linked with the use of TVM. |
||||
|
T |
Applicable on infrastructure Applicable on vehicles. |
||||
|
T2 |
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. |
7.7.2.4.
Poland
|
Specific case |
Category |
Notes |
||
Index 77, point 3.1.9: The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit). In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. |
T |
Applicable on infrastructure Applicable on vehicles This specific case may be revised when the open point related to the frequency management for track circuits is closed. |
7.7.2.5.
Lithuania, Latvia and Estonia
|
Specific case |
Category |
Notes |
|||
|
T |
Applicable on infrastructure Applicable on vehicles This specific case is needed as long as ČME locomotives operate on 1 520 mm network. |
|||
|
T |
Applicable on infrastructure Applicable on vehicles This specific case is needed as long as ČME locomotives operate on 1 520 mm network. |
|||
|
T |
Applicable on vehicles This specific case is linked with the use of ALSN on the 1 520 mm network. |
|||
|
Frequency range |
Interference current limit [rms value] |
||||
|
15 — 21 Hz 21 — 29 Hz 29 — 35 Hz 65 — 85 Hz 167 — 184 Hz 408 — 432 Hz 468 — 492 Hz 568 — 592 Hz 708 — 732 Hz 768 — 792 Hz 4 462,5 — 4 537,5 Hz 4 507,5 — 4 582,5 Hz 4 962,5 — 5 037,5 Hz 5 462,5 — 5 537,5 Hz 5 517,5 — 5 592,5 Hz |
4,1 A 1,0 A 4,1 A 4,1 A 0,4 A 0,35 A 0,35 A 0,35 A 0,35 A 0,35 A 0,2 A 0,2 A 0,2 A 0,2 A 0,2 A |
||||
|
T |
Applicable on vehicles This specific case is linked with the use of ALSN on the 1 520 mm network |
|||
|
Frequency range |
Interference current limit [rms value] |
||||
|
19 — 21 Hz 21 — 29 Hz 29 — 31 Hz 40 — 46 Hz 46 — 54 Hz 54 — 60 Hz 167 — 184 Hz 408 — 432 Hz 468 — 492 Hz 568 — 592 Hz 708 — 732 Hz 768 — 792 Hz 4 507,5 — 4 582,5 Hz 4 962,5 — 5 037,5 Hz 5 517,5 — 5 592,5 Hz |
11,6 A 1,0 A 11,6 A 5,0 A 1,3 A 5,0 A 0,4 A 0,35 A 0,35 A 0,35 A 0,35 A 0,35 A 0,2 A 0,2 A 0,2 A |
||||
7.7.2.6.
Sweden
|
Specific case |
Category |
Notes |
||||||
|
P |
No impact on interoperability |
||||||
|
P |
Applicable on vehicles |
||||||
|
P |
Applicable on vehicles |
||||||
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 |
Applicable on infrastructure Applicable on vehicles |
7.7.2.7.
Luxembourg
|
Specific case |
Category |
Notes |
||||||||||
|
T |
|
||||||||||
|
T |
Applicable on vehicles This specific case is needed as long as track circuits (operating frequency 83,3 Hz) are used. Document GI.II.STC.VF is available on the website of the NSA LU(48). |
||||||||||
|
T |
Applicable on vehicles This specific case is needed as long as track circuits (operating frequency 125 Hz) are used. Document GI.II.STC.VF is available on the website of the NSA LU. |
7.7.2.8.
Germany
|
Specific case |
Category |
Notes |
||||||||||||||||||||||
|
T |
Applicable on vehicles This specific case is needed as long as track circuits type WSSB are used. |
||||||||||||||||||||||
|
T |
Applicable on vehicles This specific case is needed as long as EBUET 80 type of level crossing protection is used. |
||||||||||||||||||||||
Evaluation method: Band Pass Filters Evaluation parameters:
|
T |
Applicable on infrastructure Applicable on vehicles 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. |
7.7.2.9.
Italy
|
Specific case |
Category |
Notes |
||||||||||||||||||||||||
|
T |
The national values for dispensing sand will remain valid until harmonized test specifications (currently non-existent) are available for demonstrating that different modes for dispensing sand are safety-acceptable for train detection systems operating in Italy. |
||||||||||||||||||||||||
Granulometry ≥ 85% of the sand mixture, with grains' diameters between 0,1 mm and 0,6 mm; and in particular:
|
T |
The national values of sand mixture will remain valid until harmonized test specifications (currently non-existent) are available for demonstrating that different kinds of sand mixture are safety-acceptable for train detection systems operating in Italy. |
||||||||||||||||||||||||
|
T2 |
Applicable on infrastructure Applicable on vehicles |
||||||||||||||||||||||||
|
P |
This is applicable for the projects notified to the European Commission by 30 June 2020. |
7.7.2.10.
Czech Republic
|
Specific case |
Category |
Notes |
||||||||||||||||||||||||||||||||||||||||||||||
|
T |
Applicable on infrastructure Applicable on vehicles This specific case is needed as long as track circuits type EFCP are used. |
7.7.2.11.
The Netherlands
|
Specific case |
Category |
Notes |
||||||||||||||||||||||||||||||||||||||||
|
P |
Applicable on infrastructure Applicable on vehicles This Specific Case is needed in the context of the Class-B system ATBEG. Alternative demonstration, leading to presumption of conformity, is permissible by compliance with the national rules related to rail return current notified for this purpose. |
7.7.2.12.
Ireland
|
Specific case |
Category |
Notes |
||||||
|
T |
This specific case is linked with the IE Class B system and certain train detection systems that require the first axle of a train having a good electric contact with the track. |
||||||
|
T |
This augments but does not replace the other TSI requirements for management of train running numbers, so that all new equipment shall remain also fully compatible with the interoperability requirements. A transition to pure numeric train numbers shall thus become possible and is envisaged as soon as the train management systems in Ireland are all equipped for pure numeric train running numbers. |
||||||
|
T |
This augments but does not replace the other TSI requirements for management of the driver interface, so that all new equipment shall remain also fully compatible with the interoperability requirements. A transition to the pure km/h speed dial shall thus become possible and is envisaged as soon as the Irish network is fully fitted with ETCS, or all lineside speed restriction signs can be changed to km/h (i.e. all existing trains present a km/h speedometer). |
7.7.2.13.
Bulgaria
|
Specific case |
Category |
Notes |
||
|
T |
Applicable on vehicles |
7.7.2.14.
Austria
|
Specific case |
Category |
Notes |
||||
|
T |
This is applicable for the projects notified to the European Commission by 30 June 2020. |
||||
|
T2 |
Applicable to lowfloor Wagon |
Appendix A (49)
References
|
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, 102 |
|
4.2.1 |
|
|
4.2.1 a |
27 |
|
4.2.2 |
|
|
4.2.2 a |
14 |
|
4.2.2 b |
4, 13, 60, 104 |
|
4.2.2 c |
31, 37 b, 37 c, 37 d |
|
4.2.2 d |
20 |
|
4.2.2 e |
6 |
|
4.2.2 f |
7, 81, 82 |
|
4.2.2 g |
Intentionally deleted |
|
4.2.2 h |
87 |
|
4.2.3 |
|
|
4.2.3 a |
14 |
|
4.2.3 b |
4, 13, 60 |
|
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 i |
Intentionally deleted |
|
4.2.4 j |
71, 72 |
|
4.2.4 k |
75, 76 |
|
4.2.4 l |
93, 94, 95, 99 |
|
4.2.4 m |
93, 94, 95 |
|
4.2.4 n |
96 |
|
4.2.4 o |
97 |
|
4.2.5 |
|
|
4.2.5 a |
64, 65 |
|
4.2.5 b |
10a, 10b, 10d, 34, 39, 40 |
|
4.2.5 c |
19, 20 |
|
4.2.5 d |
9, 43 |
|
4.2.5 e |
16, 50 |
|
4.2.5 f |
93, 94, 95 |
|
4.2.5 g |
Intentionally deleted |
|
4.2.5 h |
86, 10a, 10d, 33, 34 |
|
4.2.5 i |
86, 10a, 10c, 10d, 92, 94, 95 |
|
4.2.5 j |
10a, 10b, 10c, 10d, 39, 40, 92, 94, 95 |
|
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 |
10a,10b, 10d, 34 |
|
4.2.6 e |
10a, 20 |
|
4.2.6 f |
Intentionally deleted |
|
4.2.6 g |
92, 10a, 10b, 10c, 10d |
|
4.2.6 h |
87, 89 |
|
4.2.6 i |
90 |
|
4.2.6 j |
10a, 10d, 34 |
|
4.2.6 k |
92, 10a, 10c, 10d |
|
4.2.6 l |
92, 93, 99, 94, 95 |
|
4.2.7 |
|
|
4.2.7 a |
12 |
|
4.2.7 b |
63 |
|
4.2.7 c |
34, 10a, 10b, 10d |
|
4.2.7 d |
9 |
|
4.2.7 e |
16 |
|
4.2.7 f |
92, 10a, 10b, 10c, 10d |
|
4.2.7 g |
34, 10a, 10d |
|
4.2.7 h |
92, 10a, 10c, 10d |
|
4.2.8 |
|
|
4.2.8 a |
10d, 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 |
|
4.2.13 |
|
|
4.2.13 a |
32, 33 |
|
4.2.13 b |
93, 94 |
|
4.2.14 |
|
|
4.2.14 a |
5 |
|
4.2.15 |
|
|
4.2.15 a |
38 |
|
4.2.15 b |
101 |
|
4.2.17 |
|
|
4.2.17 a |
103 |
|
4.2.18 |
|
|
4.2.18 a |
84, 85 |
|
4.2.18 b |
98 |
|
4.2.18 c |
88 |
|
4.2.18 d |
87 |
|
4.2.19 |
|
|
4.2.19 a |
84, 85 |
|
4.2.19 b |
98 |
Specifications
|
Index No |
ETCS Baseline 4 Release 1; RMR: GSM-R Baseline 1 Maintenance Release 1 + FRMCS Baseline 0; ATO Baseline 1 Release 1 |
|||||||||||||||||||||
|
Reference |
Name of Specification |
Version |
Notes |
|||||||||||||||||||
|
1 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
2 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
3 |
SUBSET-023 |
Glossary of Terms and Abbreviations |
4.0.0 |
|
||||||||||||||||||
|
4 |
SUBSET-026 |
System Requirements Specification |
4.0.0 |
|
||||||||||||||||||
|
5 |
SUBSET-027 |
FIS Juridical Recording |
4.0.0 |
|
||||||||||||||||||
|
6 |
ERA_ERTMS_015560 |
ETCS Driver Machine interface |
4.0.0 |
|
||||||||||||||||||
|
7 |
SUBSET-034 |
Train Interface FIS |
4.0.0 |
|
||||||||||||||||||
|
8 |
SUBSET-035 |
Specific Transmission Module FFFIS |
4.0.0 |
|
||||||||||||||||||
|
9 |
SUBSET-036 |
FFFIS for Eurobalise |
4.0.0 |
|
||||||||||||||||||
|
10a |
SUBSET-037-1 |
EuroRadio FIS GSM-R – Part 1 [Communication layer and coordination function] |
4.0.0 |
|
||||||||||||||||||
|
10b |
SUBSET-037-2 |
EuroRadio FIS – Part 2 [Safety layer] |
4.0.0 |
|
||||||||||||||||||
|
10c |
SUBSET-037-3 |
EuroRadio FIS – Part 3 [FRMCS interface] |
4.0.0 |
|
||||||||||||||||||
|
10d |
SUBSET-146 |
ERTMS End-to-End Security |
4.0.0 |
|
||||||||||||||||||
|
11 |
SUBSET-038 |
Offline key management FIS |
4.0.0 |
|
||||||||||||||||||
|
12 |
SUBSET-039 |
FIS for the RBC/RBC handover |
4.0.0 |
|
||||||||||||||||||
|
13 |
SUBSET-040 |
Dimensioning and Engineering rules |
4.0.0 |
|
||||||||||||||||||
|
14 |
SUBSET-041 |
Performance Requirements for Interoperability |
4.0.0 |
|
||||||||||||||||||
|
15 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
16 |
SUBSET-044 |
FFFIS for Euroloop |
2.4.0 |
|
||||||||||||||||||
|
17 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
18 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
19 |
SUBSET-047 |
Trackside-Trainborne FIS for Radio infill |
4.0.0 |
|
||||||||||||||||||
|
20 |
SUBSET-048 |
Trainborne FFFIS for Radio infill |
3.0.0 |
|
||||||||||||||||||
|
21 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
22 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
23 |
SUBSET-054 |
Responsibilities and rules for the assignment of values to ETCS variables |
4.0.0 |
|
||||||||||||||||||
|
24 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
25 |
SUBSET-056 |
STM FFFIS Safe time layer |
3.0.0 |
|
||||||||||||||||||
|
26 |
SUBSET-057 |
STM FFFIS Safe link layer |
3.1.0 |
|
||||||||||||||||||
|
27 |
SUBSET-091 |
Safety Requirements for the Technical Interoperability of ETCS |
4.0.0 |
|
||||||||||||||||||
|
28 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
29 |
SUBSET-102 |
Test specification for interface ‘K’ |
2.0.0 |
|
||||||||||||||||||
|
30 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
31 |
SUBSET-094 |
Functional requirements for an on-board reference test facility |
3.1.0 |
|
||||||||||||||||||
|
32 |
EIRENE FRS |
GSM-R Functional requirements specification |
8.1.0 |
Note 7 |
||||||||||||||||||
|
33 |
EIRENE SRS |
GSM-R System requirements specification |
16.1.0 |
Note 7 |
||||||||||||||||||
|
34 |
A11T6001 |
(MORANE) Radio Transmission FFFIS for EuroRadio |
14.0.0 |
|
||||||||||||||||||
|
35 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
36a |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
36b |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
36c |
SUBSET-074-2 |
FFFIS STM Test cases document |
4.0.0 |
|
||||||||||||||||||
|
37a |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
37b |
SUBSET-076-5-2 |
Test cases related to features |
3.3.0 |
|
||||||||||||||||||
|
37c |
SUBSET-076-6-3 |
Test sequences |
3.2.0 |
|
||||||||||||||||||
|
37d |
SUBSET-076-7 |
Scope of the test specifications |
3.3.0 |
|
||||||||||||||||||
|
37e |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
38 |
EN 16494 |
Railway applications. Requirements for ERTMS Trackside Boards |
2015 |
|
||||||||||||||||||
|
39 |
SUBSET-092-1 |
ERTMS EuroRadio Conformance Requirements |
4.0.0 |
|
||||||||||||||||||
|
40 |
SUBSET-092-2 |
ERTMS EuroRadio test cases safety layer |
4.0.0 |
|
||||||||||||||||||
|
41 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
42 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
43 |
SUBSET-085 |
Test specification for Eurobalise FFFIS |
4.0.0 |
|
||||||||||||||||||
|
44 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
45 |
SUBSET-101 |
Interface ‘K’ Specification |
2.0.0 |
|
||||||||||||||||||
|
46 |
SUBSET-100 |
Interface ‘G’ Specification |
2.0.0 |
|
||||||||||||||||||
|
47 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
48 |
Reserved |
Test specification for mobile equipment GSM-R |
|
Note 3 |
||||||||||||||||||
|
49 |
SUBSET-059 |
Performance requirements for STM |
4.0.0 |
|
||||||||||||||||||
|
50 |
SUBSET-103 |
Test specification for Euroloop |
1.1.0 |
|
||||||||||||||||||
|
51 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
52 |
SUBSET-058 |
FFFIS STM Application layer |
4.0.0 |
|
||||||||||||||||||
|
53 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
54 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
55 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
56 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
57 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
58 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
59 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
60 |
SUBSET-104 |
ETCS System Version Management |
4.0.0 |
|
||||||||||||||||||
|
61 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
62 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
63 |
SUBSET-098 |
RBC-RBC Safe Communication Interface |
4.0.0 |
|
||||||||||||||||||
|
64 |
EN 301 515 |
Global System for Mobile Communication (GSM); Requirements for GSM operation on railways |
3.0.0 |
Note 1 |
||||||||||||||||||
|
65 |
TS 102 281 |
Detailed requirements for GSM operation on railways |
3.1.1 |
Note 2 |
||||||||||||||||||
|
66 |
TS 103 169 |
ASCI Options for Interoperability |
1.1.1 |
|
||||||||||||||||||
|
67 |
(MORANE) P 38 T 9001 |
FFFIS for GSM-R SIM Cards |
6.0.0 |
Note 7 |
||||||||||||||||||
|
68 |
ETSI TS 102 610 |
Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways |
1.3.0 |
|
||||||||||||||||||
|
69 |
(MORANE) F 10 T 6002 |
FFFS for Confirmation of High Priority Calls |
5 |
|
||||||||||||||||||
|
70 |
(MORANE) F 12 T 6002 |
FIS for Confirmation of High Priority Calls |
5 |
|
||||||||||||||||||
|
71 |
(MORANE) E 10 T 6001 |
FFFS for Functional Addressing |
4.1 |
|
||||||||||||||||||
|
72 |
(MORANE) E 12 T 6001 |
FIS for Functional Addressing |
5.1 |
|
||||||||||||||||||
|
73 |
(MORANE) F 10 T6001 |
FFFS for Location Dependent Addressing |
4 |
|
||||||||||||||||||
|
74 |
(MORANE) F 12 T6001 |
FIS for Location Dependent Addressing |
3 |
|
||||||||||||||||||
|
75 |
(MORANE) F 10 T 6003 |
FFFS for Presentation of Functional Numbers to Called and Calling Parties |
4 |
|
||||||||||||||||||
|
76 |
(MORANE) F 12 T 6003 |
FIS for Presentation of Functional Numbers to Called and Calling Parties |
4 |
|
||||||||||||||||||
|
77 |
ERA/ERTMS/033281 |
Interfaces between CCS trackside and other subsystems |
5.0 |
Note 6 |
||||||||||||||||||
|
78 |
Intentionally deleted |
|
|
Note 5 |
||||||||||||||||||
|
79 |
SUBSET-114 |
KMC-ETCS Entity Off-line KM FIS |
4.0.0 |
|
||||||||||||||||||
|
80 |
Intentionally deleted |
|
|
Note 4 |
||||||||||||||||||
|
81 |
SUBSET-119 |
Train Interface FFFIS |
4.0.0 |
|
||||||||||||||||||
|
82 |
SUBSET-120 |
Train Interface – Safety requirements |
4.0.0 |
|
||||||||||||||||||
|
83 |
SUBSET-137 |
On-line Key Management FFFIS |
4.0.0 |
|
||||||||||||||||||
|
84 |
SUBSET-125 |
ERTMS/ATO System Requirement Specification |
1.0.0 |
|
||||||||||||||||||
|
85 |
SUBSET-126 |
ATO-OB/ATO-TS FFFIS Application Layer |
1.0.0 |
|
||||||||||||||||||
|
86 |
SUBSET-148 |
ATO-OB/ATO-TS FFFIS Transport and Security Layers |
1.0.0 |
|
||||||||||||||||||
|
87 |
SUBSET-130 |
ATO-OB/ETCS-OB FFFIS Application Layer |
1.0.0 |
|
||||||||||||||||||
|
88 |
SUBSET-139 |
ATO OB/Rolling Stock FFFIS Application Layer |
1.0.0 |
|
||||||||||||||||||
|
89 |
SUBSET-143 |
Interface Specification Communication Layers for On-board Communication |
1.0.0 |
|
||||||||||||||||||
|
90 |
SUBSET-147 |
CCS Consist network communication Layers FFFIS |
1.0.0 |
|
||||||||||||||||||
|
91 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
92 |
FFFIS-7950 |
FRMCS FFFIS |
1.0.0 |
Note 8 |
||||||||||||||||||
|
93 |
FU-7120 |
FRMCS FRS |
1.0.0 |
Note 9 |
||||||||||||||||||
|
94 |
AT-7800 |
FRMCS SRS |
1.0.0 |
Note 9 |
||||||||||||||||||
|
95 |
FIS-7970 |
FRMCS FIS |
1.0.0 |
Note 8 |
||||||||||||||||||
|
96 |
Reserved |
[FFFIS for FRMCS profile placeholder] |
|
|
||||||||||||||||||
|
97 |
Reserved |
[FRMCS Test specifications placeholder] |
|
|
||||||||||||||||||
|
98 |
SUBSET-151 |
ATO-OB/ATO-TS Test Specifications |
Reserved |
|
||||||||||||||||||
|
99 |
TOBA-7510 |
On-board FRMCS TOBA FRS |
1.0.0 |
Note 9 |
||||||||||||||||||
|
100 |
Intentionally deleted |
|
|
|
||||||||||||||||||
|
101 |
21E089 |
Engineering rules for harmonised marker boards |
1- |
|
||||||||||||||||||
|
102 |
13E154 |
ERTMS/ATO Glossary |
2- |
|
||||||||||||||||||
|
103 |
TD/011REC1028 |
ESC/RSC technical document |
Version published in ERA website |
|
||||||||||||||||||
|
104 |
SUBSET-153 |
Exceptions for on-board reduced envelopes of system versions |
Reserved |
|
||||||||||||||||||
|
||||||||||||||||||||||
|
No |
Reference |
Document name and comments |
Version |
Note |
||||
|
A1 |
EN 50126-1 |
Railway applications – The specification and demonstration of reliability, availability, maintainability and safety (RAMS) – Part 1: Generic RAMS Process |
2017 |
1 |
||||
|
A2 |
EN 50128 |
Railway applications – Communication, signalling and processing systems – Software for railway control and protection systems |
2011 +A2:2020 |
|
||||
|
A3 |
EN 50129 |
Railway applications – Communication, signalling and processing systems – Safety related electronic systems for signalling |
2018 +AC:2019 |
1 |
||||
|
A4 |
EN 50159 |
Railway applications – Communication, signalling and processing systems |
2010 +A1:2020 |
1 |
||||
|
A5 |
EN 50126-2 |
Railway Applications – The specification and demonstration of reliability, availability, maintainability and safety (RAMS) – Part 2: Systems Approach to Safety |
2017 |
1, 2 |
||||
|
||||||||
|
No |
Reference |
Document name and comments |
Version |
Note |
|
A6 |
ISO/IEC 17025 |
General requirements for the competence of testing and calibration laboratories |
2017 |
|
Appendix B
B1.
Changes of requirements and transition regimes for On-Board Subsystems
|
No |
TSI point(s) |
TSI point(s) in previous version |
Explanation on TSI change |
Transition regime |
|||||||||||||||||||||
|
Design phase started after TSI enters into force |
Design phase started before TSI enters into force |
Production phase |
Vehicle in operation |
||||||||||||||||||||||
|
CCS On-Board Error corrections |
|||||||||||||||||||||||||
|
1 |
Appendix A + point 7.2.10.3 |
No mandatory implementation of error corrections published in technical opinions |
CCS Subsystems with mandatory implementation of registered error corrections for functionality ETCS up to system version 2.1 and GSM-R. |
For legal releases (with maintenance of specifications) published before 1 January 2026: If one or more registered errors are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the necessary error corrections at the latest 6 months after the update of the concerned interoperability constituents.
|
For legal releases (with maintenance of specifications) published before 1 January 2026: If one or more registered errors are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the necessary error corrections the latest
|
||||||||||||||||||||
|
|
|
|
|
For legal releases (with maintenance of specifications) published after 1 January 2026: If one or more registered errors are identified for the area of use for which a new authorisation is required: the CCS subsystem integrated into a vehicle type shall implement the full maintenance package of error corrections at the latest 6 months after the update of the concerned interoperability constituents.
|
For legal releases (with maintenance of specifications) published after 1 January 2026: If one or more registered errors are identified for the area of use: the CCS subsystem integrated into a vehicle shall implement the full maintenance package of error corrections the latest
|
||||||||||||||||||||
|
ETCS On-Board implementation |
|||||||||||||||||||||||||
|
2 |
Points 7.4.2.1, and 7.4.3 |
7.4.2.1.2. and 7.4.3(2) grants exemptions for new vehicles to be equipped with ETCS |
7.4.2.1.2. and point 7.4.3(2) deleted. All newly built vehicles shall be equipped with ETCS. |
Directly applicable
For special vehicles applicable from 1 January 2026 with respect to 7.4.3.2. |
Applicable from 1 January 2028
For special vehicles applicable from 1 January 2030 with respect to 7.4.3.2. |
Applicable from 1 January 2030
|
Not applicable |
||||||||||||||||||
|
3 |
Point 7.4.2.2 |
7.4.2.2 only applicable to upgrade of existing high-speed vehicles |
7.4.2.2 applicable to vehicle type and/or vehicles requiring a new authorisation |
Directly applicable For special vehicles applicable from 1 January 2026. |
Applicable from 1 January 2028
For special vehicles applicable from 1 January 2030. |
Not applicable |
Not applicable |
||||||||||||||||||
|
4 |
Point 7.4.2.3 (3) |
7.4.2.4 extension area of use: exemptions to install ETCS in point (3) |
7.4.2.4 extension area of use: exemptions deleted in point (3) |
Not applicable |
Not applicable |
Not applicable |
Applicable from 1 January 2030 |
||||||||||||||||||
|
ETCS system versions |
|||||||||||||||||||||||||
|
5 |
Appendix A – 7.4.2.4.1 and 7.4.2.4.2 for envelope of legally operated ETCS system versions from 1.0 up to 2.1 inclusive. |
The minimum reduced on-board envelope is the envelope up to ETCS system version 2.0. |
The minimum reduced on-board envelope is the envelope up to ETCS system version 2.1. |
Applicable 3 years after entry into force of the TSI |
Applicable from 1 January 2030 |
Applicable on newly built vehicles from 1 January 2030 |
Not applicable |
||||||||||||||||||
|
6 |
Appendix A – 7.4.2.4.1 and 7.4.2.4.2 for envelope of legally operated ETCS system versions from 1.0 up to 2.2 inclusive. |
Not applicable |
On-board implementation of notified ETCS functions from system version 2.2. |
Design phase started after notification from IM and notification is done after 1 January 2025: the ETCS system version 2.2 is directly applicable. |
The ETCS system version 2.2 is applicable if the design phase is not ended within the latest date between following dates:
|
Not applicable |
Not applicable |
||||||||||||||||||
|
|
|
|
|
Design phase started before notification from IM or notification is done before 1 January 2025: the ETCS system version 2.2 is applicable if the design phase is not ended within the latest date between following dates:
|
|
|
|
||||||||||||||||||
|
7 |
Appendix A – 7.4.2.4.1, 7.4.2.4.2 and 7.4.1.3 for envelope of legally operated ETCS system versions from 1.0 up to 3.0 inclusive. |
Not applicable |
On-board implementation of notified ETCS functions from system version 3.0(52) . |
Not applicable.
|
Not applicable.
|
Not applicable.
|
Not applicable.
|
||||||||||||||||||
|
|
|
|
|
Design phase started before notification from IM or notification is done before entry into force of CCS TSI amendment:
|
|
|
|
||||||||||||||||||
|
8 |
Appendix A – 7.4.2.3 (7) |
Mandatory use of system version 2.0 or higher in case of extension of area of use |
Legal enforcement to mandate usage of system version 2.1 or higher in case of extension of area of use only when the extending area of use is combined with a request for new authorisation |
Directly applicable |
Directly applicable |
Not applicable |
Not applicable |
||||||||||||||||||
|
Former sets of specifications #2 and #3 |
|||||||||||||||||||||||||
|
9 |
Appendix A – Table A 2 |
Appendix A – Table A 2 2 – Set of specification #2 |
The specifications in Appendix A – Table A 2 does not include ETCS system version 2.0, since the minimum reduced on-board envelope is the envelope up to ETCS system version 2.1. |
Applicable 3 years after entry into force of the TSI In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Applicable from 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Applicable on newly built vehicles from 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Not applicable In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
||||||||||||||||||
|
10 |
Appendix A – Table A 2 |
Appendix A – Table A 2 3 – Set of specification #3 |
The specifications in Appendix A – Table A 2 have the agreed error corrected version of former set #3 |
Applicable 3 years after entry into force of the TSI In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Applicable from 1 January 2030 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Applicable on newly built vehicles from 1 January 2032 In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
Not applicable In any case the error correction provisions in point 7.2.10 shall be respected with its corresponding transition period. No constraint shall be exported to the other subsystem. |
||||||||||||||||||
|
CMD |
|||||||||||||||||||||||||
|
11 |
4.2.2 (b) – Cold Movement Detection |
CMD Optional |
CMD Mandatory |
Directly applicable when ETCS is installed for the first time into a vehicle design. |
Applicable from 1 January 2028 when ETCS is installed for the first time into a vehicle design. |
Applicable on newly built vehicles placed on the market from 1 January 2030. |
Not applicable |
||||||||||||||||||
|
ATO On-Board Implementation |
|||||||||||||||||||||||||
|
12 |
4.2.18 + Point 7.2.9.2 |
Not applicable |
ATO on-board specification and implementation requirements |
Design phase started after notification from IM and notification is done after 1 January 2025: ATO on-board requirements are directly applicable. Design phase started before notification from IM or notification is done before 1 January 2025: ATO On-board requirements are applicable if the design phase is not ended within the latest date between following dates:
|
ATO on-board requirements are applicable if the design phase is not ended within the latest date between following dates:
|
Not applicable |
Not applicable |
||||||||||||||||||
|
CCS On-Board Modularity |
|||||||||||||||||||||||||
|
13 |
Index 90 + point 5.2.2.2 |
Not applicable |
Mandatory implementation of Ethernet based platform New requirement in case of grouping of Interoperability Constituents defined in table 5.1 |
Applicable 2 years after entry into force of the TSI on newly developed vehicle designs requiring first authorisation |
Applicable 7 years after entry into force of the TSI on newly developed vehicle designs requiring first authorisation |
Not applicable |
Not applicable |
||||||||||||||||||
|
14 |
Appendix A – CCS and RST interfaces Indexes 81, 82, 88, 90 |
Not applicable |
Mandatory implementation of on-board interfaces between CCS subsystem and RST subsystem |
Applicable 2 years after entry into force of the TSI on newly developed vehicle designs requiring first authorisation |
Applicable 7 years after entry into force of the TSI on newly developed vehicle designs requiring first authorisation |
Not applicable |
Not applicable |
||||||||||||||||||
|
FRMCS On-Board implementation |
|||||||||||||||||||||||||
|
15 |
Point 7.3.2.2 |
Not applicable |
FRMCS on-board implementation(54) |
Not applicable.
|
Not applicable.
|
Not applicable.
|
Not applicable.
|
||||||||||||||||||
|
|
|
|
|
Design phase started before notification from IM: see transition regime in column ‘Design phase started before TSI set into force’. |
|
|
|
||||||||||||||||||
|
Partial fulfilment |
|||||||||||||||||||||||||
|
16 |
Point 6.1.1.2 |
Points 6.1.1.3 and 6.4.3 are deleted. |
With respect to 6.1.1.2 it is no longer possible to exclude mandatory functionalities, interfaces or performance except if listed in Appendix G. |
3 years after the entry into force of the TSI. If partial fulfilment is used, a condition for use shall be included in their authorisation for placing on the market enforcing compliance at the next upgrade of the vehicle train protection part. |
7 years after the entry into force of the TSI. |
Not applicable |
Not applicable |
||||||||||||||||||
|
DMI indication translation |
|||||||||||||||||||||||||
|
17 |
Appendix E |
No mandatory harmonised translation of DMI indications |
Harmonised translation of DMI indications. |
Directly applicable |
7 years after the entry into force of the TSI. |
Not applicable |
Not applicable |
||||||||||||||||||
|
No |
TSI point(s) |
TSI point(s) in previous version |
Explanation on TSI change |
Transition regime |
|||
|
Design phase started after TSI enters into force |
Design phase started before TSI enters into force |
Production phase |
Vehicle in operation |
||||
|
1 |
Index 77 |
V4 – Frequency management not fully defined for the vehicle |
V5 – Frequency management fully defined for the vehicle |
Directly applicable with the exception of point 3.2.2. This point is applicable 2 years after the entry into force of the TSI on newly developed vehicle designs requiring a first authorisation as defined in Article 14 point 1(a) of Commission Implementing Regulation (EU) 2018/545; Applicable 7 years after the entry into force of the TSI on modified vehicles designs requiring a new authorisation as defined in Article 14 point 1(d) of Commission Implementing Regulation (EU) 2018/545; |
Applicable 7 years after the entry into force of the TSI |
Not applicable |
Not applicable |
B2.
Changes of requirements and transition regimes for CCS Trackside Subsystem
|
No |
TSI point(s) |
TSI point(s) in previous version |
Explanation on TSI change |
Transition Regime |
||||
|
CCS Trackside Error Corrections |
||||||||
|
1 |
Appendix A + Points 7.4.1.2 and 7.2.10.3 |
Set 1, 2 and 3 of specifications without error corrections |
Table A2 includes the maintenance of the functions into 1 set of specifications. |
CCS Trackside Subsystems, which are in advanced stage of development or in operation, shall implement the identified set of corrections for the unacceptable errors as described in point 7.2.10.1 within:
CCS Trackside Subsystems placed into service after the entry into force of this TSI, which are not in advanced stage of development, shall directly comply with the maintained set of specifications of this TSI. |
||||
|
CCS Trackside Enhancements |
||||||||
|
2 |
ETCS: Appendix A; + point 7.4.1.3 |
Not applicable |
New ETCS functions from system version 2.2 to 3.0 |
If implemented (optional trackside function), directly applicable for ETCS equipped lines |
||||
|
3 |
ETCS: Appendix A; Table A.2 – Index 38, 101 |
Marker-board definition based on 06E068 |
EN 16494 and engineering rules for harmonised marker boards |
Directly applicable if:
Detailed provisions for applicable requirements for fitting the harmonised Marker Boards are stated in the Appendix A – Table A.2 – Index 101 document. |
||||
|
4 |
4.2.19 |
No specifications |
ATO Trackside Implementation |
If implemented (optional trackside function), directly applicable for ATO GoA1/2 implementation on ETCS equipped lines. |
||||
|
5 |
FRMCS radio system |
No specifications |
New set of FRMCS specifications |
If implemented (optional trackside function), directly applicable for FRMCS projects when FRMCS specifications are completed and published with an amendment of this CCS TSI. |
||||
|
Partial fulfilment |
||||||||
|
6 |
Not applicable |
Points 6.1.1.3 and 6.4.3 are deleted. |
When implemented, all functions, performance and interfaces or performance shall comply with the Chapter 4 (including the specifications referred to in Appendix A). |
7 years after the entry into force of the TSI. |
||||
|
Former set of specifications set #1, #2 and #3 |
||||||||
|
7 |
Appendix A — Table A 2 |
Appendix A – Table A 2 1 – Set of specification #1, Table A 2 2 – Set of specification #2 Table A 2 3 – Set of specification #3 |
Table A 2 includes the maintenance of the functions into 1 set of specifications. |
Requirements and deadlines defined in point 7.4.1.2. |
||||
B3.
Changes of Interoperability Constituent requirements and transition regimes for CCS Subsystem
|
No |
TSI point(s) |
TSI point(s) in previous version |
Explanation on TSI change |
Transition Regime |
||||||
|
1 |
Appendix A + point 4.2.20.1 + point 7.2.10.2 |
Technical opinions on Art. 10 errors are not legally binding |
Implementation of error corrections into ERTMS on-board Interoperability Constituents for existing CCS subsystems for functionality ETCS up to system version 2.1 and GSM-R. |
If one or more registered errors are identified for the area of use specified in the authorisation of the vehicle:
This transition regime can be handled flexibly in agreement with the applicant for the EC verification of the on-board subsystem and the railway undertaking as long as the overall transition regime (as per Table B1.1 plus as per Table B3) is met.
|
||||||
|
2 |
Appendix A + point 4.2.20.1 + point 7.2.10.2 |
Technical opinions on Art. 10 errors are not legally binding |
Implementation of error corrections into ERTMS Trackside Interoperability Constituents for new CCS trackside projects for functionality, ETCS up to system version 2.1 and GSM-R. |
ERTMS Trackside Interoperability Constituents, integrated into a CCS Trackside Subsystem for which the project is not in advanced stage of development, shall directly comply with the maintained set of specifications of this TSI. |
||||||
|
3 |
Appendix A + point 4.2.20.1 + point 7.2.10.2 |
Technical opinions on Art. 10 errors are not legally binding |
Implementation of error corrections into ERTMS Trackside Interoperability Constituents for existing CCS trackside projects (i.e. trackside subsystem in advanced stage of deployment or in operations) |
ERTMS Trackside Interoperability Constituents, integrated into a CCS Trackside Subsystem for which the project is in advanced stage of development or being integrated in a CCS Trackside Subsystem in operation, shall implement the identified set of corrections for the unacceptable trackside errors for the area of use specified in the authorisation within 18 months year after the publication of the IM-decision. |
||||||
|
4 |
Appendix A, Table A.2 Index 90, 92 + 5.2.2.2 |
N/A |
Implementation of Ethernet based communication for integration with ATO On-Board IC and FRMCS On-Board IC |
New ETCS On-Board Interoperability Constituents placed on the market within 2 years after entry into force of the TSI shall implement the Ethernet based connections required for ATO and FRMCS interfacing as specified in Index 90 (points 3.1.1.2 and 3.1.1.3) and as specified in Index 92 (point 7.2) |
Appendix C
Appendix C.1:
ESC Statement template
TEMPLATE FOR ETCS SYSTEM COMPATIBILITY STATEMENT
ETCS SYSTEM COMPATIBILITY STATEMENT
Appendix C.2:
ESC Interoperability Constituent Statement template
TEMPLATE FOR ESC STATEMENT FOR INTEROPERABILITY CONSTITUENT
ESC STATEMENT FOR INTEROPERABILITY CONSTITUENT
Appendix C.3:
RSC Statement template
TEMPLATE FOR RADIO SYSTEM COMPATIBILITY STATEMENT
RADIO SYSTEM COMPATIBILITY STATEMENT
Appendix C.4:
RSC Statement for Interoperability Constituent template
TEMPLATE FOR RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT
RSC STATEMENT FOR INTEROPERABILITY CONSTITUENT
Appendix C.5:
Combined ESC/RSC Statement template
TEMPLATE FOR ETCS AND RADIO SYSTEM COMPATIBILITY STATEMENT
ETCS AND RADIO SYSTEM COMPATIBILITY STATEMENT
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
Appendix D
Appendix E
List of harmonised text indications and messages displayed on the ETCS Driver Machine Interface
|
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 |
|
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 |
|
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 |
|
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 (81)
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
|
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). |
||||||
|
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:
The following on-board functionalities impacting the ETCS on-board system version are excluded in the reduced on-board envelope up to 2.2:
|
||||||
|
Subset 34: options available at subsystem level are also available at interoperability constituent level. |
The functionality will not be required for the fully interoperable operations of the vehicle. |
Interoperability constituents are not required to include functionalities related to electrical traction if these interoperability constituents are designed for vehicles equipped with catenary independent engines. |
Appendix H
ISSUANCE YEAR
NATIONAL IMPLEMENTATION PLAN
[MEMBER STATE]
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
—
Current status of deployment for Class A train protection system
Figure 1
Current status of ETCS deployment
|
ID |
Line |
Current status of deployment |
Mandatory deadline of ETCS application |
Additional information |
Note |
|||
|
Current status |
Date when ETCS was placed in service |
Length |
Level(s) |
Baseline and system version |
||||
|
[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
Figure 2
Current status of ATO deployment
|
ID |
Line |
Current status of ATO deployment |
Additional information |
Note |
|||
|
Current status |
Date when ATO was placed in service |
Length |
Baseline |
Other relevant aspects for ATO deployments (For example GoA) |
|||
|
[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
Figure 3
Current status of GSM-R deployment
Figure 4
Current status of FRMCS deployment
|
|
|
Current status of GSM-R deployment |
Additional information |
Note |
|||
|
ID |
Line |
Current status |
Date when GSM-R was placed in service |
Length |
GSM-R voice/GSM-R data |
Baseline |
|
|
[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] |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Current status of FRMCS deployment |
Additional information |
Note |
|||
|
ID |
Line |
Current status |
Date when FRMCS was placed in service |
Length |
GSM-R condition |
Baseline |
|
|
[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] |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
—
Current status of deployment for TSI compliant train detection system
Figure 5
Current status of TSI COMPLIANT TRAIN DETECTION deployment
|
ID |
Line |
Current status of TSI compliant train detection deployment |
Additional information |
Note |
||
|
Current status |
Date when TSI compliant train detection was placed in service |
Length |
[Other relevant aspects for TSI Compliant train detection deployments] |
|||
|
[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
|
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] |
|
… |
… |
… |
|
2.1.3.
Current mandatory onboard requirements
|
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] |
|
|
|
|
|
|
|
|
|
|
|
|
|
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
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
—
Current status for Class B train protection system
Figure 6
Class B train protection system 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
Figure 7
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
3. TECHNICAL MIGRATION STRATEGY
3.1.
Technical migration strategy for ETCS part
—
Description of the solution implemented
—
Deployment strategy for the implementation of ETCS
—
Planning for ETCS deployment and Class B decommissioning
|
ID |
Line |
Planning for ETCS deployment |
Planning for Class B train protection decommissioning |
Additional deployment information |
Note |
|||||||
|
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 |
|||
|
[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
3.2.
Technical migration strategy for Radio part
—
Strategy for the introduction of GSM-R
—
Strategy for the introduction of the next generation communication system(s).
—
Planning for GSM-R deployment and Class B radio system decommissioning
|
ID |
Line |
Planning for GSM-R deployment |
Planning for Class B radio decommissioning |
Additional information |
Note |
|||||||
|
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 |
|||
|
[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
|
ID |
Line |
Planning for FRMCS deployment |
Planning for GSM-R decommissioning |
Additional information |
Note |
||||||
|
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 |
|||
|
[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 GSM-R 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
—
Deployment strategy for ATO
—
Planning for ATO deployment
|
ID |
Line |
Planning for ATO deployment |
Additional information |
Note |
|||
|
Current status |
Date when ATO is placed in service |
Length |
Baseline |
Other relevant aspects for ATO deployments (For example GoA) |
|||
|
[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
—
Deployment strategy for TSI compliant train detection system
—
Planning for TSI compliant train detection system deployment
|
ID |
Line |
Planning for TSI compliant train detection deployment |
Additional information |
Note |
|||
|
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] |
|||
|
[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
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
Figure 8
Network map. dates when ETCS is placed in service
5.1.2.
Decommissioning of Class B train protection systems
Figure 9
Network map. dates when Class B operation is not allowed anymore
Figure 10
Network map. Dates where Class B train protection system is taken out of service
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
Figure 11
Network map. Dates when GSM-R is placed in service
5.2.2.
Decommissioning of Class B radio systems
Figure 12
Network map. Dates when Class B radio operation is not allowed anymore
Figure 13
Network map. Dates where Class B radio system is taken out of service
5.2.3.
Dates when FRMCS is placed in service
Figure 14
Network map. Dates when FRMCS is placed in service
5.2.4.
Decommissioning of GSM-R
Figure 15
Network map. Dates when GSM-R radio operation is not allowed anymore
Figure 16
Network map. Dates where GSM-R system is taken out of service
5.2.5.
Information on cross-border lines
5.2.6.
Information on nodes
5.3.
Planning for ATO part
Figure 17
Network map. Dates when ATO is placed in service
5.3.1.
Information on cross-border lines
5.3.2.
Information on nodes
5.4.
Planning for train detection part
Figure 18
Network map. Dates when TSI compliant train detection system is placed in service
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
|
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
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
|
Member State |
Name of the legacy system(1) |
Scope |
Version identification |
Date of latest authorisation to placing into service |
|
Austria |
INDUSI I 60(2) |
Whole network |
|
|
|
PZB 90(3) |
Whole network |
AT/DE |
|
|
|
LZB (LZB L72, LZB L72 CE I and LZB L72 CE II) |
Whole network |
|
|
|
|
Belgium |
Crocodile |
Whole network |
|
|
|
TBL 1 |
Whole network |
|||
|
TBL 2 |
Whole network |
|||
|
TVM 430 |
Whole network |
|||
|
TBL1+ |
Off-TEN only |
|||
|
KVB |
Access to high speed line 1 |
|||
|
Bulgaria |
EBICAB 700 |
Whole network |
BU |
|
|
Croatia |
INDUSI I 60(2) |
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 |
|
|
|
KVB |
Whole network |
|||
|
TVM 300 |
High speed lines |
|||
|
TVM 430 |
High speed lines |
|||
|
KVBP |
(sub)urban area of Paris |
|||
|
KCVP |
(sub)urban area of Paris |
|||
|
KCVB |
(sub)urban area of Paris |
|||
|
NEXTEO |
(sub)urban area of Paris |
|||
|
DAAT |
Whole network |
|||
|
Germany |
PZB 90 |
Whole network |
AT/DE |
|
|
LZB (LZB L72, LZB L72 CE I and LZB L72 CE II)(4) |
Whole network |
|
||
|
GNT (Geschwindigkeitsüberwachung für NeiTech-Züge)(5) |
Whole network (routes with higher lateral acceleration for tilting trains) |
|
||
|
Hungary |
EVM |
Whole network |
|
|
|
Ireland |
CAWS |
Whole network |
|
|
|
ATP |
Whole network |
|||
|
Italy |
SCMT + RSC |
Whole network |
|
|
|
SCMT |
Whole network |
|||
|
SSC |
Off-TEN only |
|||
|
Latvia |
ALSN |
Whole network |
|
|
|
Lithuania |
ALSN |
Whole network |
|
|
|
Norway(6) |
ATC(7) |
Whole network |
2 |
1993 |
|
Poland |
SHP |
Whole network |
|
|
|
PKP radio system with Radiostop function |
Whole network |
|||
|
Portugal |
INDUSI I 60 |
Cascais line Off-TEN |
PT |
|
|
EBICAB 700 (CONVEL) |
Whole network |
|
||
|
Romania |
INDUSI I 60(2) |
Whole network |
|
|
|
Slovak Republic |
LS |
Whole network |
LS04, LS05, LS06 |
|
|
Slovenia |
INDUSI I 60(2) |
All main lines and also 3 regional lines |
|
|
|
Spain |
ASFA |
Whole network |
|
|
|
EBICAB 900 |
Mediterranean Corridor. Section ‘La Encina – Barcelona Sants’ |
ES |
||
|
LZB |
High Speed Line ‘Madrid – Sevilla/Toledo/Málaga’ C5 Commuter Line (Madrid). Section ‘Humanes – Mostoles el Soto’ |
ES |
||
|
Sweden |
ATC(7) |
Whole network except Linköping-Västervik/Kisa |
2 |
|
|
|
Linköping-Västervik/Kisa |
R |
|
|
|
Switzerland(6) |
EuroSIGNUM(8) |
Whole network |
|
|
|
EuroZUB(6) |
Whole network |
|||
|
The Netherlands |
ATB First generation |
Whole network |
|
|
|
ATB new generation |
Whole network |
|||
|
UK for Northern Ireland |
GW ATP |
limited to specific routes only |
|
|
|
RETB |
limited to specific routes only |
|||
|
TPWS/AWS |
Whole network |
|||
|
Chiltern-ATP |
limited to specific routes only |
|||
|
Mechanical Trainstops |
limited to specific routes only |
3.4.
List of Class B voice radio systems
(9)
|
Member State |
Name of the legacy system(10) |
Scope |
Version identification |
Date of latest authorisation to placing into service |
||||||||||
|
Austria |
UIC Radio Chapter 1-4+6 |
|
|
|
||||||||||
|
Bulgaria |
UIC Radio Chapter Bulgaria |
|
|
|
||||||||||
|
Croatia |
Analogue railway radio system (RDU) – in compliance with UIC 751-3 |
|
|
|
||||||||||
|
Czechia |
SRD |
|
|
|
||||||||||
|
Estonia |
The Estonian Railways train communication network |
Whole network |
|
|
||||||||||
|
Germany |
Analogue Radio Germany - in compliance with UIC 751-3 (all chapters): |
|
|
|
||||||||||
|
Lines of the former GDR installed before 1990 |
|||||||||||||
|
Low frequency traffic routes |
|||||||||||||
|
Routes not covered by the GSM-R network |
|||||||||||||
|
Greece |
CH — Greek Railways radio system (VHF) |
Whole network except Kiato-Athens airport section and Egio-Kiato (open line). |
|
|
||||||||||
|
Hungary |
UIC Radio Chapter 1-4 |
|
|
|
||||||||||
|
UIC Radio Chapter 1- 4 + 6 (Irish system) |
||||||||||||||
|
Ireland |
UIC Radio Chapter 1- 4 + 6 (Irish system) |
|
|
|
||||||||||
|
Italy |
GSM-P |
On lines not covered with GSM-R |
|
|
||||||||||
|
Latvia |
LDZ radio system DMR |
Whole network |
|
|
||||||||||
|
Lithuania |
The Lithuanian Railways train radio system |
All line sections between stations in border areas |
|
|
||||||||||
|
Shunting Radio Communication System |
Whole network (for manoeuvring) |
|||||||||||||
|
Poland |
PKP radio system |
Whole network |
|
|
||||||||||
|
Portugal |
UIC Radio Chapter 1-4 (TTT radio system installed at Cascais line) |
Cascais line Off TEN |
|
|
||||||||||
|
TTT radio system CP_N (RSC – Rádio Solo-Comboio) |
Whole network |
|||||||||||||
|
Romania |
Radio Network of CFR |
|
|
|
||||||||||
|
Slovakia |
450 Mhz UIC (Channel C) Multikom (160 MHz and 450 MHz) BOSCH (160 MHz) OMEGA (160 MHz) SRO (160 MHz) |
|
|
|
||||||||||
|
Slovenia |
Analogue railway radio system called RDZ – in compliance with UIC 751-3 |
All main lines and 5 regional lines |
|
|
||||||||||
|
Spain |
UIC Radio Chapter 1-4+6 |
|
|
|
||||||||||
|
UK for Northern Ireland |
RETB (voice) |
RETB lines only |
|
|
Feedback