EUROPEAN COMMISSIO

DIRECTORATE-GENERAL FOR EN

DIRECTORATE E - Inland transport

Rail transport and interoperability

01/16-DV29
Ch7 CCS
25. 06.2004

Directive 2001/16/EC Interoperability of the

trans-European conventional rail system
Working group TSI Decisions
Working document on TSI Control-Command and
Signalling Chapter 7

1/30

Table of content

1.

INTRODUCTION........................................................................................................................... 4

2.

SUBSYSTEM DEFINITION AND SCOPE.....................................................................................4

3.

THE ESSENTIAL REQUIREMENTS OF THE CONTROL-COMMAND SUBSYSTEM.................4

4.

CHARACTERISATION OF THE SUBSYSTEM.............................................................................4

5.

INTEROPERABILITY CONSTITUENTS.......................................................................................4

6.
ASSESSMENT OF CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS
AND VERIFICATION OF THE SUBSYSTEM........................................................................................ 4
7.

IMPLEMENTATION OF THE TSI CONTROL-COMMAND............................................................4

7.1
GENERAL................................................................................................................................ 4
7.2
SPECIFIC ISSUES OF IMPLEMENTATION OF THE TSI CONTROL-COMMAND...................................4
7.2.1 General migration criteria.................................................................................................4
7.2.2 Timing Criteria.................................................................................................................. 8
7.2.3 Implementation: Infrastructure (stationary equipment)....................................................12
7.2.4 Implementation: Rolling Stock (on-board equipment).....................................................14
7.2.5 Particular Migration Paths............................................................................................... 16
7.2.6 Conditions under which optional functions are required.................................................17
7.3
MANAGEMENT OF CHANGE.................................................................................................... 17
7.3.1 Introduction..................................................................................................................... 17
7.3.2 Baselining....................................................................................................................... 18
7.3.3 The ERTMS consolidation phase...................................................................................19
7.3.4 Baseline release............................................................................................................. 19
7.3.5 Deployment of New Baselines........................................................................................ 20
7.3.6 Change Management Process The Requirements......................................................20
7.3.7 Configuration Management Plan The Requirements...................................................22
7.4
SPECIFIC CASES................................................................................................................... 22
7.4.1 Introduction..................................................................................................................... 22
7.4.2 List of specific cases....................................................................................................... 23
7.5
TRANSITIONAL PROVISIONS.................................................................................................... 24

ANNEX A............................................................................................................................................. 25
7.6
SPECIFIC ISSUES OF IMPLEMENTATION OF THE TSI CONTROL-COMMAND..................................29
7.6.1 General migration criteria............................................................................................... 29
7.6.2 Timing Criteria................................................................................................................ 33
7.6.3 Implementation Requirements: Infrastructure (stationary equipment)............................37
7.6.4 Implementation Requirements: Rolling Stock (on-board equipment)..............................38
7.6.5 Particular Migration Paths............................................................................................... 40
7.6.6 Conditions under which optional functions are required.................................................41
7.7
MANAGEMENT OF CHANGE.................................................................................................... 41
7.7.1 Introduction..................................................................................................................... 41
7.7.2 Baselining....................................................................................................................... 42
7.7.3 The ERTMS consolidation phase...................................................................................43
7.7.4 Baseline release............................................................................................................. 44
7.7.5 Deployment..................................................................................................................... 44
7.7.6 Change Management Process The Requirements......................................................44

2/30

7.7.7 Configuration Management Plan The Requirements...................................................45

7.8
SPECIFIC CASES................................................................................................................... 46
7.8.1 Introduction..................................................................................................................... 46
7.8.2 List of specific cases....................................................................................................... 46
7.9
TRANSITIONAL PROVISIONS.................................................................................................... 48
ANNEX A............................................................................................................................................. 49

3/30

1.INTRODUCTION
2.SUBSYSTEM DEFINITION AND SCOPE
3.THE ESSENTIAL
SUBSYSTEM

REQUIREMENTS

OF

THE

CONTROL-COMMAND

4.CHARACTERISATION OF THE SUBSYSTEM

5.INTEROPERABILITY CONSTITUENTS
6.ASSESSMENT OF CONFORMITY AND/OR SUITABILITY FOR USE OF THE
CONSTITUENTS AND VERIFICATION OF THE SUBSYSTEM
1.

IMPLEMENTATION OF THE TSI CONTROL-COMMAND

1.1

General

This chapter outlines the strategy and the associated technical solutions for implementation
of the TSI, notably the conditions underpinning the migration to Class A systems. Account
must be taken of the fact that the implementation of a TSI occasionally has to be coordinated with the implementation of other TSIs.
Account must be taken of the fact that implementation of a TSI occasionally has to be coordinated with the implementation of other TSIs.
Chapters 2 to 6 and any specific provisions in paragraph 7.3 below apply in full to ControlCommand Subsystem as defined by the Directive 2001/16/EC.

1.2

Specific issues of Implementation of the TSI Control-Command

1.2.1 General migration criteria

Within the Control-Command Subsystem two classes (A and B) of train protection and radio
communication systems are defined.
It is recognised that Class A cannot be installed on all existing conventional routes instantly
for reasons which include economic considerations and installation capacity aspects. In the
migration period between the current (pre-unified) situation (Class B) and the application of
Class A, there will be a number of possible interoperability solutions that might be
implemented in the framework of this TSI. These solutions apply to both the European
Conventional Infrastructure, including connecting lines, and to the European conventional rail
trains. A number of illustrative examples are given below:

Within ERTMS/ETCS provision is made for modules known as STMs (Specific

Transmission Modules) to be added to ETCS to enable a train fitted with appropriate
STMs to operate over existing pre-unified infrastructure. Another solution is that an
infrastructure may be equipped with both Class A and Class B systems.

The implementation of GSM-R systems on a nation-wide basis has already started in

a significant number of countries of the former EU15. The first inter-connections of
these national networks are expected during 2004. Other networks will follow shortly.
Some railways have chosen a solution where mobile equipment is designed in such a
way that it can work in both systems (Dual-mode = GSM-R and >=1 analogue radio),

4/30

others have taken the solution to have a double coverage on network-side but only
single equipment on the trains. GSM-R does not have STMs. Cab-radios that have
additional interface-units for Class B radio systems (Dual-mode) are able to work also
on lines in a Class B network if specially designed. This solution is only an interim
solution to allow early exchange of international trains.
.

1.2.1.1

Migration paths

The existing systems as well as the future unified system have system components
infrastructure-side and on-board. Therefore migration strategies have to be defined for both
assemblies. This paragraph deals with migration paths from Class B to Class A by giving
examples.
Migration strategies must pay special attention to the following distinction:
- train radio (from Class B to Class A),
- train protection (from Class B to Class A),
- the train detection system,
- the hot axle box detection system,
- EMC.
Each of the above can follow a different migration path.
Possible migration paths from Class B to Class A are explained by means of the following
examples for the train protection system.

TARGET
% Transition time

% Vehicles equipped
100
100

START

% Lines equipped
100

Figure 1
Error: Reference source not found depicts the starting state, where only non compatible
systems exist (denominated START) to the final state (denominated TARGET).
The following two figures describe the two possible extreme migration paths from the present
to the future state.

5/30

TARGET
% Transition time

% Vehicles equipped
100
100

START

% Lines equipped
100

Figure 2
Error: Reference source not found shows a migration process, where all the initial
investment is made on-board only. A possible technical solution is the so-called STM, which
can be linked to the kernel of the ETCS on-board and which translates information from
existing systems to a form that can be processed by the ETCS kernel. After the equipment of
all vehicles of a railway fleet under consideration with the combination of ETCS kernel and
respective Class B systems, the wayside equipment can be altered to ETCS or newly
equipped lines can be built based on the ETCS system. The existing class B system on
these lines can be removed.

TARGET
% Transition time

% Vehicles equipped
100
100

START

% Lines equipped
100

Figure 3
Error: Reference source not found shows the other extreme migration process. In this
case, the respective railway would double equip existing lines with the ETCS system. After all

6/30

lines have ETCS in addition to the national system, the on-board equipment of the rolling
stock can be changed to ETCS. When all vehicles under consideration are equipped with
ETCS, the wayside equipment for the national system can then be removed.

TARGET
% Transtion time

% Vehicles equipped
100
100

START

% Lines equipped
100

Figure 4
Error: Reference source not found shows the combination of both extremes described
above. The possible migration paths have to be between these two limits. In practical terms,
there should to be a mixture of both ways.

TARGET
% Transition time

% Vehicles equipped
100
100

START

% Lines equipped
100

Figure 5

7/30

Error: Reference source not found depicts an example, where ETCS on-board equipment
in vehicles and ETCS wayside equipment on parts of the lines is installed alternatively. This
method minimises the inception investment necessary to take advantage of the system as a
whole (i.e. the on-board and trackside equipment in the sections these are fitted). On the
other hand, it implies a certain restriction in usage of rolling stock on the network.
The selection of the appropriate migration strategy depends largely on the mix between lines
equipped, rolling stock equipped and planned purchase of new rolling stock and additional
equipment of lines.
Also international corridors and international use of rolling stock should be considered. In
case a line is not foreseen for migration and is only equipped with Class B the interoperable
operation can be ensured by a STM for the Class B system concerned.
The migration steps, however, have to enable access of other railway undertakings to the
network at any time. A vehicle equipped with the appropriate ETCS on-board equipment and
the existing system as described in annexes B and C must always be able to run on the line
under consideration.

1.2.2

Timing Criteria

1.2.2.1

Introduction

ETCS and GSM-R are computer-based systems with a faster technology evolution and
potentially a lower life expectancy than current traditional railway signalling and
telecommunication facilities. As such, they call for a pro-active rather than reactive
deployment strategy to avoid potential system obsolescence prior to system deployment
reaching maturity levels.
Notwithstanding this fact, the adoption of a too fragmented deployment throughout the
European rail network, mainly along the trans-European rail corridors, would give rise to
major cost and operational overheads resulting from the needs to ensure backward
compatibility and interconnection with a diversity of legacy facilities. Moreover, synergies in
terms of time, cost and risk reduction might be reached by the reconciliation of common
elements of different national implementation strategies viz. through joint procurement
initiatives, collaboration in system validation and certification activities.
Whereas such pro-active implementation strategy does appears a must to underpin the
whole of the migration process, the specific modalities to be adopted for the conventional rail
network have to account for the current level and planned rate of deployment of these
technologies as well as the relevant economic, operational, technical and financial factors
that influence such an implementation.
Within this context, it is evident that a clear distinction is to be made between ETCS and
GSM-R in view of the current status of migration throughout Europe and the magnitude and
extent of the barriers underlying such a migration, a fact that commands a different rationale
for the implementation of GSM-R and of ETCS on the conventional network. Such a distinct
rationale will be delineated in fuller detail within the next two paragraphs:

1.2.2.2

GSM-R Rationale for Deployment

8/30

The current magnitude of the GSM-R deployment activity throughout the whole of the
European rail network (circa 90000 km nowadays in 11 out of the 15 states of the former
EU15) and the 4 to 5 year time horizon that generally underpins the conclusion of such
deployment works indicates that any deployment rationale will have to confront three main
concerns:

o To ensure the continuity of GSM-R service across borders avoiding the establishment
of black spots within some regions of the Community;

o To reconcile the migration timings throughout Europe in order to significantly reduce

the cost and time overheads associated with the potential needs to sustain double
analogue/digital telecommunication infrastructures and on-board facilities.

o To avoid a two speed Europe between the former EU15 and the new Member
States. Convergence needs to be achieved a target that is facilitated by the on-going
programmes for major upgrading of the railway networks of the new Member States.

1.2.2.3

GSM-R Implementation Rules

Set against this background, and taking into account that a GSM-R infrastructure is a
telecommunication bearer for both high-speed and conventional rail applications, the
implementation criteria now in force for the former applications should equally apply for
conventional rail, viz.
Trackside installations:
The fitting of GSM-R in the case of:
o New installations of radio part of a CC assembly;
o An upgrade of radio part of a CC assembly already in service that changes the
functions or the performance of the subsystem.
On-board installations:
The fitting of GSM-R in Rolling Stock intended for use on a line including at least a section
equipped with Class A interfaces (even if superimposed to a Class B system), in the case
of:
o New installations of the radio part of a CC assembly;
o An upgrade of the radio part of a CC assembly already in service that changes the
functions or the performance of the subsystem.
Legacy systems:
Member States shall ensure that the functionality of the legacy systems referred to in Annex
B to the TSI as well as their interfaces is to remain as currently specified. Member States
shall make available the necessary information regarding their legacy systems that is
required for purposes of development and certification of apparatus allowing interoperability
of Class A equipment with their legacy Class B facilities.
In order to enable a pro-active implementation, Member States are also encouraged to
promote and support the fitting of GSM-R in any renewal or maintenance-related work

9/30

affecting the whole of an infrastructure already in service entailing an investment at least one
order of magnitude higher than those associated with the installation of GSM-R facilities.

1.2.2.4

ERTMS/ETCS Rationale for Deployment

As it stands nowadays, the case of ERTMS/ETCS on conventional applications has to be

underlined by a different deployment rationale that accounts for the manifold complexity
associated to a migration of signalling systems, to its associated costs and to the expected
longer lifetime of the assets when compared to those of GSM-R. However, in no way such
barriers should detract from the generic deployment principles exposed above, in particular,
the necessity to keep the implementation momentum within acceptable levels notably on the
major corridors and trunk lines of the Trans-European rail Network (TEN).
In order to reconcile the apparent conflicting objectives of avoidance of fragmented approach
with the perceived constraints on investment it is deemed necessary to define a start-up
deployment kernel of rail projects where ERTMS/ETCS deployment can be indeed justified
on an end-to-end business/service perspective whereas not commanding unacceptable
barriers in terms of implementation costs. In particular, the latter applies to those projects that
are supported by significant Community funds well above the amounts that can be normally
earmarked for signalling works.
The set of rail related priority projects established within the TEN as well as all those major
rail construction/upgrading works funded under the framework of the Cohesion Funds are to
be considered as priority targets for inclusion within such a priority kernel.
Regarding rolling-stock a marginal cost approach is to be pursued, linking the fitment of onboard ERTMS/ETCS with major investment decisions. This applies notably to the
procurement of new rolling-stock or major retrofitting operations for which the value of the
signalling equipment and of its installation represent only a limited percentage of the whole
investment to be put in place. The adoption of such a policy will push in the longer-term for
the scenario of ETCS on-board equipment as a commodity asset in what regards new rollingstock.
The deployment kernel as identified above is to constitute a steppingstone for the inception
of the deployment of ERTMS/ETCS on the conventional rail system. The scope of this kernel
will be extended if deemed necessary to make it fuller compliant with the forthcoming EU
implementation plan for ERTMS. The latter is to be set-up as a co-ordination and financing
instrument to contribute to an accelerated and wider-ranging deployment of ERTMS across
the whole of the trans-European rail network. Whilst such a plan will be broader in scope that
the priority applications already included herein (see figure below) it will ultimately evolve
from the deployment rationale and guiding principles referred to above.
EU Conventional Rail System
EU Deployment
Plan

ETCS Inception
Kernel

10/30

The ultimate goal is for the EU deployment plan to complement the deployment kernel in
reaching the critical mass conditions for ERTMS/ETCS to impose itself as the preferred
solution for all new and upgrade signalling projects across Europe.

1.2.2.5

ERTMS/ETCS Implementation Rules

All the implications enumerated in the previous paragraph are to be eventually qualified as
follows:
1

Trackside installations:
The fitting of ERTMS/ETCS in the case of:
o New installations of signalling part of a CC assembly;
o An upgrade of signalling part of a CC assembly already in service that changes the
functions or the performance of the subsystem.
for the set of railway infrastructure projects falling within one of the following criteria:

o Be part of the set of new priority projects established under the Trans-European
Network orientations, notably those that are classified under the Quick Start
initiative (Decision of the Council and EP 884/2004/EC);
o Command a financial support from Structural Funds (EC Regulation 1260/1999)
and/or Cohesion Funds (EC Regulation 1264/1999) in excess of 30% of the total
project costs.
For any other new or upgrade projects not encompassed under these latter criteria the prefitting of equipment as defined under Paragraph 7.2.3.2 should be performed.
In order to enable a pro-active implementation, Member States are also encouraged to
promote and support the fitting of ERTMS/ETCS in any renewal or maintenance-related
work of the infrastructure that entails investments at least one order of magnitude higher
than those associated with the installation of ERTMS/ETCS facilities.
On-board installations:
The fitting of ERTMS/ETCS, complemented where necessary by the relevant Specific
Transmission Modules (STM) to enable operation on Class B systems, on.
o New installations of the signalling part of a CC assembly;
o An upgrade of the signalling part of a CC assembly already in service that changes
the functions or the performance of the subsystem;
o Any major retrofitting of rolling stock already in service.
Legacy systems:
Member States shall ensure that the functionality of the legacy systems referred to in Annex
B to the TSI as well as their interfaces is to remain as currently specified. Member States
shall make available the necessary information regarding their legacy systems that is
required for purposes of development and safety-certification of apparatus allowing
interoperability of Class A equipment with their legacy Class B facilities.

1 For purposes of fitment of ETCS equipment major retrofitting is defined as those maintenance operations that
entail an investment at least one order of magnitude higher than the value of fitting the ETCS equipment on that
specific type of rolling-stock.

11/30

1.2.2.6

National ERTMS Deployment Plans

Set against the deployment rationale and its implementation rules identified in the previous
paragraphs, Member States are deemed to prepare a formal national ERTMS
implementation plan. Such formal plans should provide an appropriate knowledge base for
decision support to the different stakeholders in particular, to the Commission in the
allocation of its financial support to railway projects. Any non-adherence to the general EU
deployment principles in the elaboration of a national ERTMS implementation plan should be
justified by the Member State concerned on the basis of the procedure foreseen under Article
7 of the Directive 2001/16/EC.
Once a national ERTMS implementation plan is completed, all activities related to installation
of Control-command subsystems have to be justified by the awarding entities against this
implementation plan in addition to all other applicable legislative requirements that are in
force. Necessarily, the EU and national ERTMS implementation plans will be evolving
documents that will have to be updated in order to reflect the real evolution of the
deployment in each Member State and throughout the European rail network.

1.2.3

Implementation: Infrastructure (stationary equipment)

The following requirements apply to the categories of lines defined in Article 5c of the
Directive 2001/16/EC:

Lines intended for passenger services;

Lines intended for mixed traffic (passengers and freight);
Lines specially designed or upgraded for freight services;
Passenger hubs;
Freight hubs including intermodal terminals;
Lines connecting the above mentioned components.

The Control-Command Subsystem concerns two classes (A and B) of train protection and
radio communication systems. The lines mentioned above presently not equipped with
Class A shall be equipped either:
with Class A functions and interfaces according to the specifications referenced in
Annex A, or
with Class A functions and interfaces according to the specifications referenced in
Annex A and with Class B functions and interfaces according to Annex B or,
with Class B functions and interfaces according to Annex B and pre-fitting for Class A
or
only with Class B functions and interfaces according to Annex B.
- In case lines under the scope of the present TSI will not be equipped with Class A
systems, the Member State shall be responsible to ensure that the relevant external STM for
its Class B system or systems is available in the open market at fair commercial conditions.
-

12/30

1.2.3.1
line

Additional Class-B equipment on a Class A equipped

On a line equipped with ETCS and/or GSM-R, additional Class B equipment is possible in
order to allow the operation of rolling stock not compatible with Class A during the migration
phase. It is allowed to use existing Class B equipment on-board as a fallback arrangement to
Class A system: this does not allow an infrastructure manager to require Class B systems
onboard the interoperable trains for running on such a line.
Where dual fitment and operation of Class A and B systems occurs, then both systems may
be active simultaneously onboard, provided that national technical requirements and
operating rules support this manner and that interoperability is not compromised. The
national technical requirements and operating rules will be provided by the Member State.

1.2.3.2

Pre-fitting for Class A

The track side pre-fitting is defined as the installation of any ETCS and GSM-R equipment or
other enabling equipment for ETCS and GSM-R (e.g. interlocking interfaces, LEU or fibre
optic backbones) which is fitted but not necessarily put in service aimed at reducing the
implementation cost of full-fledged ERTMS/ETCS or GSM-R facilities complying with Class A
requirements at a later stage. For ETCS the scope of the pre-fitting should adhere with the
requirements set out in Index 59 of Annex A (pending).
The extent of the pre-fitting to be performed should be established during the implementation
planning of the signalling or telecommunication facilities that are to be deployed. In particular,
the network planning for GSM-R has to take into account at the earliest stage the inclusion of
all services that have to be foreseen also in the future (voice, non safety critical data, ETCS).

1.2.3.3
Upgrading or renewal of the Control-Command Track-side
Assembly or parts of it
Upgrading or renewal of the track-side assembly may concern separately:

radio-system (for class B, only renewal is possible) ,

train protection system,

train detection system interface,

hot axle box detection system,
EMC characteristics.

Therefore different parts of the Control-Command Track-side Assembly may be upgraded or

renewed separately (if interoperability is not prejudiced) and concern:
EIRENE functions and interfaces (see sections Error: Reference source not found
and Error: Reference source not found);
ETCS/ERTMS functions and interfaces (see sections Error: Reference source not
found, Error: Reference source not found, Error: Reference source not found,
Error: Reference source not found, Error: Reference source not found);
Train detection system (see sections Error: Reference source not found);
Hot axle box detector (see section Error: Reference source not found);
EMC characteristics (see section Error: Reference source not found).
After the upgrade to Class A system, the existing Class B equipment may remain in use
simultaneously with Class A.

13/30

1.2.3.4

Registers of Infrastructure

The Infrastructure Register shall provide Railway Undertakings with Class A and Class B
information, following Annex C requirements. The Infrastructure Register indicates if
Mandatory or Optional (2) functions are concerned; the constraints on onboard configuration
have to be identified.
In case European specifications for some interface(s) between Control-Command and
Signalling and other sub-systems are not available at the moment of installation (e.g.,
electromagnetic compatibility between train detection and Rolling Stock), the corresponding
characteristics and the standards applied shall be indicated in the Registers of Infrastructure.
This shall be possible, in any case, only for the items listed in Annex C.

1.2.4

Implementation: Rolling Stock (on-board equipment)

According to the 2001/16/EC Directive each of the categories of rolling stock which are likely
to travel on all or part of the trans-European conventional rail network must be subdivided
into:
- rolling stock for international use,
- rolling stock for national use,
taking due account of the local, regional or long-distance use of the stock.
Rolling stock mentioned above shall be equipped either:
with Class A functions and interfaces according to the specifications referenced in
Annex A, or
with Class A functions and interfaces according to the specifications referenced in
Annex A and with Class B functions and interfaces according to Annex B or,
with Class B functions and interfaces according to Annex B and pre-fitment for
Class A or
only with Class B functions and interfaces according to Annex B or,
as in section Error: Reference source not found (Error: Reference source not
found),
-

such as to allow it to travel on any line on which it is expected to operate.

-

1.2.4.1

Rolling stock with Class A equipment only

The Class A assembly shall ensure that the onboard functions, interfaces and minimum
performance required by this TSI are matched to the lines concerned as described in
Annex C. Installation of Class A equipment may take advantage from additional interface
specifications between rolling stock and control-command.

1.2.4.2

Rolling stock with Class B equipment only

The Class B equipment shall ensure that the onboard functions, interfaces and minimum
performance required by this TSI are matched to the lines concerned as described in
Annex C.

2 function classification: see section 4

14/30

1.2.4.3

Rolling stock with Class A and Class B equipment

Rolling stock may be equipped with both Class A and Class B systems to enable operations
on several lines. The Class B systems may be implemented
using an STM that may be plugged into the Class A assembly (external STM), or
built into the Class A assembly.
Also, the Class B system could be implemented independently (or, in case of upgrade or
renewal, be left as is), in case of Class B systems for which an STM is not an economically
viable alternative, from the rolling stock owners point of view. However, if a STM is not used,
the Railway Undertaking must ensure that the absence of a handshake (= handling, by
ETCS, of transitions between Class A and Class B on track-side) nevertheless is properly
managed. The Member State may put requirements on this in the Infrastructure Register.
When running on a line which is equipped with both Class A and Class B systems, the
Class B systems may act as fallback arrangement for the Class A system if the train is
equipped with both Class A and Class B systems. This cannot be a requirement for
interoperability and is not valid for GSM-R.

1.2.4.4

Pre-fitting for Class A

The on-board pre-fitting is defined as the installation of any ETCS and GSM-R equipment or
other enabling equipment for ETCS and GSM-R (e.g. installation of cabling and wiring,
antennas, sensors, power supply or installation fixtures) which is fitted but not necessarily put
in service aimed at reducing the implementation cost of full-fledged ERTMS/ETCS or GSM-R
facilities complying with the Class A requirements at a later stage. For ETCS the scope of the
pre-fitting should adhere with the requirements set out in Index 57 of Annex A (pending).
The extent of the pre-fitting to be performed should be established during the engineering
phase of the on-board signalling or telecommunication facilities. Pre-fitting may take
advantage from additional interface specifications between the sub systems rolling stock and
control-command.

1.2.4.5

Reverse STM

See section Error: Reference source not found (Error: Reference source not found)

1.2.4.6
Upgrading or renewal the Control-Command On-board
Assembly or parts of it
Upgrading or renewal of the on-board assembly may concern separately:
radio-system (Class B to Class A),
train protection system (Class B to Class A).
Therefore different parts of the Control-Command On-board Assembly may be performed or
upgraded separately (if interoperability is not prejudiced) and concern:
EIRENE functions and interfaces (see sections Error: Reference source not found
and Error: Reference source not found);
ETCS/ERTMS functions and interfaces (see sections Error: Reference source not
found, Error: Reference source not found, Error: Reference source not found,
Error: Reference source not found, Error: Reference source not found);
After the upgrade to Class A system, the existing Class B equipment may remain in use
simultaneously with Class A.

15/30

1.2.4.7

Registers of Rolling Stock

The Rolling Stock Register shall provide information following Annex C requirements.
In case TSI requirements for some interface(s) between Control-Command and Signalling
and other sub-systems are not available at the moment of installation (e.g., electromagnetic
compatibility between train detection and Rolling Stock, climatic conditions and physical
conditions in which the train can work, geometric parameters of the train like length, maximal
distance of axles in the train, length of the nose of the first and of the last car of the train,
braking parameters), the corresponding characteristics and the standards applied shall be
indicated in the Registers of Rolling Stock. This shall be possible, only for the items listed in
Annex C.
Remark: for every implementation of Control-Command Subsystem on a given line, Annex C
gives the list of the requirements for the onboard, to be addressed in the Registers of
Infrastructure, indicating if these requirements concern Mandatory or Optional ( 3) functions
and identifying constraints on train configuration.

1.2.5
1.2.5.1

Particular Migration Paths

Specific solution for partial additional use of Class A system

In a migration phase when only part of the fleet is equipped with an onboard system able to
handle Class A, it may be necessary to have both systems fully or partially installed on a
line.
For ETCS there is no functional link between the two onboard systems except to manage
transitions during train operation (and with exception to satisfy the needs of the STMs for
Class B systems when STMs are used).
For ETCS from a purely functional point, a system may also be built combining components
from the unified and a pre-unified system. An example is the combination of an ETCS Level 1
using Eurobalise as a spot transmission means and an infill function not based on a unified
solution, but on a national system. This solution requires an on-board data link between the
unified and the pre-unified system. Therefore, the solution is not in accordance with either
Class A or Class B and is not interoperable.
There is, however, the possibility to use the combination as a national enhancement of an
interoperable line. This is only permitted if trains not equipped with the data link between
both systems can operate either on the unified or on the pre-unified system without
information from the other system. If this is not possible, the line cannot be declared
interoperable for the Control-Command Subsystem.

1.2.5.2

Specific solution for partial alternative use of ETCS Class A airgap

An infrastructure may also be used for the movement of trains not compliant with the
requirements of this TSI, according to Article 5(6) of Directive 2001/16/EC, provided this does
not create prejudice to the fulfilment of essential requirements.
Such trains receive information from a Class B signalling infrastructure via Class A track-totrain communication.

3 function classification: see section 4

16/30

1.2.5.3

Competition criteria

Any action to allow the movement of interoperable trains on other infrastructures or the
movement of not interoperable trains on interoperable infrastructures shall ensure that free
competition between suppliers is not prejudiced.
Specially, knowledge about relevant interfaces between already installed equipment and new
equipment to be purchased shall be put at the disposal of all the interested suppliers.

1.2.6

Conditions under which optional functions are required

According to the characteristics of the track-side Control-Command Track-side Assembly and

its interfaces with other sub-systems, some track-side functionality not classified as
mandatory, may have necessarily to be implemented in certain applications to comply with
the essential requirements.
The track-side implementation of National or Optional-functions must not prevent the entry
onto that infrastructure for a train that complies only with the mandatory requirements of
Onboard Class A system except as required for the following on-board optional functions:
an ETCS Level 3 Track-side application requires train integrity supervision onboard;
an ETCS Level 1 Track-side application with infill requires corresponding in-fill
functionality onboard if the release speed is set to zero for safety reasons (e.g.,
protection of danger points).
When ETCS requires data transmission by radio, the data transmission services of
GSM-R must fulfil the ETCS data transmission requirements.
An onboard assembly, which incorporates a KER STM, may require to implement the
K-interface.

1.3

Management of Change

1.3.1 Introduction
Change is a facet inherent to any kind of computer-based systems used in real-world
environments. It is prompted by the emergence of new requirements or by changes to
existing requirements either due to errors reported in operation or the need of improvements
in performance or other non-functional characteristics.
But change has to be managed as it is underpinned by safety-critical considerations and by
backward compatibility objectives so as to provoke minimal time and cost overheads to the
operation of already deployed ERTMS4 equipment (i.e. legacy ERTMS facilities). It is
therefore crucial to define a clear strategy of how to implement and manage change to
legacy ERTMS equipment to avoid disruption to railway operations without undermining the
underlying objectives of guaranteeing safety and interoperability. Two main issues underpin
the definition of such a strategy:

o The establishment of a Configuration Management framework defining the standards

and procedures for managing system evolution. This should include how to record
and process proposed system changes, how to relate these changes to system
components and how to track system releases.

4 Both ERTMS/ETCS and GSM-R.

17/30

o A policy for release of system baselines.

1.3.2

Baselining

System stability is essential so that actual implementation and deployment can be realistic.
This need for stability is akin to all parties:

o the infrastructure managers and the railway operators that will have to handle various
versions of ERTMS/ETCS or GSM-R.

o the industry that needs time to specify, develop and prove continued interoperability.
A baseline in essence embodies the concept of a stable kernel in terms of system
functionality, performance and other non-functional characteristics (e.g. RAMS) 5. However,
past experience with this type of systems has shown that a number of version releases 6 are
needed to achieve a stable and implementation-suitable baseline. This can be illustrated as a
cascade process as follows:

Through its feedback loops such a process is highly intertwined. This precludes putting
several of those processes in parallel an approach that would lead to unstable and confusing
and operationally hampering situations. Baselines have then to be processed in a series
rather than in a parallel manner as illustrated below for the specific case of ERTMS/ETCS7:

5 A baseline acts as a reference starting point for a controlled management of the system evolution.
6 A version release is a version of the system that is distributed to railway customers. Versions of the
system may have different functionality, performance or may repair system faults or safety or security
shortcomings.
7 Additional elements regarding this issue are included in the paragraphs below.

18/30

1.3.3

The ERTMS consolidation phase

The first baseline of the ERTMS specifications (both ETCS and GSM-R) was appended to
the TSI Command/Control and Signalling for high-speed (reference Commission Decision
2002/731). A new version release of these specifications was issued recently (Commission
Decision 2004/447). It included minor functional and system changes whereas laying down
the foundation of a structured approach for conformity assessment of the on-board
command/control equipment.
The current on-going consolidation process for ERTMS (both ETCS and GSM-R) is clearly
focused on two main issues:

o the consolidation of the current baseline in order it becomes a more robust reference
for interoperability; and

o the closure of a number of still standing operational and technical open points.
This work relies on the feedback from current pilots, early commercial applications as well as
on structured program of cross-tests with products from different suppliers. It should
eventually lead to the release of a new baseline to be put under configuration management
during the first half of 2005.
During this phase it may be necessary to make special, mutual agreements between
Infrastructure Managers and Railway Undertakings for using Class A systems.

1.3.4

Baseline release

Based on current experience the timing between different baselines can be estimated to be
circa four to five years for ETCS and circa two years for GSM-R.

19/30

A new baseline should in principle be linked with significant modifications of the system
functionality or system performance. This could include aspects such as:

o The incorporation of set of todays national functions, where these can be

generalized, within the interoperable kernel

o The set-up of additional interoperability constituents on the ETCS on-board and

trackside
o GSM-R-based value-added services
Each baseline should also embrace the functionality of the previous baseline. Debugging
versions to repair system faults or safety shortcomings should be handled as a version
release of a particular baseline. Unless prevented by safety implications such version
releases within the same baseline are to be backward compatible.
The added functionality that might be embodied in different baselines necessarily implies that
different baselines are not backward compatible. However, in order to facilitate migration and
in the extent possible from a technical view point, different baselines should encompass a
common core of functionality for which backward compatibility should be ensured. Such a
common core should provide a minimum kernel to enable interoperable operation under
acceptable performance.

1.3.5

Deployment of New Baselines

Infrastructure managers and railway operators will never be in a position to switch from one
baseline to the next over night. Henceforth, each baseline has to developed hand-in-hand
with an appropriate migration strategy. This is to address problems such as co-existence of
ETCS and GSM-R facilities compliant with different versions of the ETCS or GSM-R
specifications, preferred paths of migration (viz. trackside priority, rolling-stock priority or
simultaneous) as well as the indicative timeframes and the priorities for the migration.

1.3.6

Change Management Process The Requirements

As discussed earlier change is a fact of life for large software based systems. Henceforth,
change management procedures should be designed to ensure that the costs and benefits of
change are properly analyzed and that changes are implemented in a controlled way. This
requires the defined change management process and associated tools to ensure that
changes are recorded and applied to the specifications in a cost-effective manner. Whatever
the specific details of such a process might eventually be the latter should be broadly
mapped on a structured approach as follows:

20/30

Formalisation
of CR

Analysis
of CR

CCB

Approval
of CR

y
Changes to
Specifications

Traceability
of Changes

CR valid

CR rejected

y
Implementation
Strategy

Cost of
Changes

File CR in DB

Quality
Approval

New Version
of Specifications

CR Change Request
CCB Change Control Board

A configuration management plan embodying the set of standards and procedures for
change management should underpin the whole of the change management process as
described above. The generic requirements for such a plan are described in paragraph 1.3.7
below. The implementation strategy for the approved changes should be formalised (on the
basis of due process and due documentation) into a change management plan that includes
notably

o
o
o
o

The identification of the technical constraints underpinning the change;

A statement of who takes responsibility for the change implementation procedures;
The validation procedure for the changes to be implemented;
The policy for change management, release, migration and roll-out.

An important part of the change management process is the definition of the responsibilities
for the delivery of the specifications and for both its quality assurance and configuration
management. Nowadays these tasks are split as follows:
Responsibility
Delivery of specifications
Quality assurance
Configuration management

ERTMS/ETCS
GSM-R
ERTMS Users Group, UIC andEIRENE group, ERIG and
UNISIG
GSM-R Industry Group
ERTMS Users Group
EIRENE group, ERIG and
ERTMS Users Group
AEIF

It is planned that most of these tasks will revert to or will be supervised by the European
Railway Agency (established by the EC Regulation 881/2004) when this will begin operation.
A period of transition between these two structures has to be foreseen. For this transition to
happen in a smooth manner it is deemed essential to formalise and document the current

21/30

change management process within the set of documentation referred to in Annex A in order
this is taken as the reference to ensure the continuity and the quality of the change
management work.
Finally, it is essential that the Change Control Board (CCB) which eventually will act as
overall system authority is composed of a representative cross-section of the all interested
parties viz. infrastructure managers, railway undertakings, supply industry, notified bodies
and safety authorities alike. Such affiliation of the parties should ensure a system perspective
on the changes that are to be made and a global assessment of their implications. The CCB
ultimately will be put under the aegis of the European Railway Agency. A coordinated
handover needs to be ensured between the current AEIF-led change management structure
(based on a threetier CCB structured) and the future Agency-led CCB.

1.3.7

Configuration Management Plan The Requirements

The configuration management plan should describe the set of standards and procedures for
change management encompassing notably:

o The definition of what entities are to be managed and a formal scheme for identifying
these entities;

o A statement of who takes responsibility for the configuration management

o
o
o
o

procedures and for submitting controlled entities to the configuration management

decision structure;
The configuration management policies that are to be used for change control and
version management;
A description of the records of the configuration management process which should
be maintained;
A description of the tools to be used for configuration management and the process
to be applied when using these tools;
A definition of the configuration database which will be used to record configuration
information.

The specific details of the Configuration Management processes for ETCS and GSM-R are
to be formalised through specifications to be incorporated in the list of specifications included
under Annex A to this TSI, respectively, under index 60 (for ETCS) and index 61 (for GSM-R).

1.4 Specific Cases

1.4.1 Introduction
The following special provisions are permitted in the specific cases below.
These specific cases belong to two categories: the provisions apply either permanently (case
"P"), or temporarily (case "T"). In temporary cases, it is recommended that the Member
States concerned should conform with the relevant subsystem either by 2010 (case "T1"),
an objective set out in Decision No 1692/96/EC of the European Parliament and of the
Council of 23 July 1996 on Community guidelines for the development of the trans-European
transport network, or by 2020 (case "T2")8.
In this TSI temporary case "T3" is defined as temporary cases which will still exists after
2020.

8Other dates (Tx) may be specified depending on the TSI and the specific case.
22/30

1.4.2

List of specific cases

1.4.2.1
. Category of each specific case is given in Annex A,
Appendix 1.
Nr.
1

Specific Case
Justification
Duration
Interdependence
between
axleExisting
axle
counterP
distance and wheel diameter ofequipment, identified in the
vehicles operating in Germany isinfrastructure register.
given
in
Annex A,
Appendix 1
paragraph Error: Reference source
not found
Maximum length of vehicle overhangExisting geometry of trackT3
(nose) operating in Poland is given incircuit equipment
Annex A,
Appendix 1
paragraph
Error: Reference source not found
Minimum distances between first 5Relevant on lines with levelT3
axles of trains operating in Germanycrossing
according
to
is given in Annex A, Appendix 1infrastructure register.
paragraph Error: Reference source
not found
Minimum distance between the firstExisting
track
circuitFrance
and last axle of a lone vehicle orequipment, identified in theBelgium
trainset operating on high speed linesinfrastructure register.
in France and Belgium is given in
Annex A,
Appendix 1
paragraph
Error: Reference source not found.
Minimum diameter of wheels ofExisting
axle
counterT3
vehicles operating in France is givenequipment, identified in the
Annex A,
Appendix 1
paragraphinfrastructure register.
Error: Reference source not found.
Minimum axle load for vehiclesMinimum axle load necessaryT3
operating in Germany, Austria,to shunt certain track circuits
Sweden is given in Annex A, Appendixis
determined
in
a
1
paragraph Error:
Referencerequirement
of
EBA
source not found
(Eisenbahn-Bundesamt),
relevant on some main lines
in Germany in the area of
former
DR
(Deutsche
Reichsbahn) with 42 Hz and
100 Hz
track
circuits
according to the infrastructure
register. No renewal.
To be completed for Austria
and Sweden
Minimum mass of a lone vehicle or Existing
track
circuitFrance
trainset operating on high speed linesequipment
Belgium
in France and Belgium is given in
Annex A,
Appendix 1
paragraph
Error: Reference source not found.

23/30

T3
T3

T3
T3

10

11

12

13

Minimum dimension of metal massRelevant on lines with levelGermany

and approval conditions of vehiclescrossing with detection loopsPoland
operating in Germany and Poland areaccording to infrastructure
given in Annex A, Appendix
register.
paragraph Error: Reference source
not found
Maximum reactance between runningExisting
track
circuitT3
surfaces of a wheelset of vehiclesequipment
operating in Poland is given in
Annex A,
Appendix 1
paragraph
Error: Reference source not found.
Maximum reactance between runningExisting
track
circuitT3
surfaces of a wheelset of vehiclesequipment
operating in France is given in
Annex A,
Appendix 1
paragraph
Error: Reference source not found.
Additional requirements on shuntingExisting low voltage trackT3
parameters of a vehicle operating incircuit equipment, identified in
Netherlands are given in Annex A,the infrastructure register.
Appendix 1
paragraph
Error:
Reference source not found.
Minimum
impedance
betweenExisting Class B equipment T3
pantograph and wheels of vehicles
operating in Belgium is given in
Annex A,
Appendix 1
paragraph
Error: Reference source not found.
The magnetic brake and eddy currentRelevant on lines with levelT3
brake is not permitted at the first bogiecrossing
according
to
of a leading vehicle operating ininfrastructure register.
Germany,
defined
in
Annex A,
Appendix 1
paragraph
Error:
Reference source not found.

1.4.2.2

P
P

Specific case for Greece

Category T1- temporary: rolling stock for track gauge 1000 mm or less, and lines with track
gauge 1000 mm or less
To be completed by AEIF.

1.5

Transitional provisions

The open points indicated in this TSI will be managed in the revision process.

24/30

7.

ANNEX A

LIST OF MANDATORY SPECIFICATIONS **

Index N

Reference

Document Name

Version

UIC ETCS FRS

ERTMS/ETCS Functional Requirement Specification

4.29 *

99E 5362

ERTMS/ETCS Functional Statements

2.0.0

UNISIG SUBSET-023

Glossary of Terms and Abbreviations

2.0.0

UNISIG SUBSET-026

System Requirement Specification

2.2.2

UNISIG SUBSET-027

FFFIS Juridical Recorder-Downloading Tool

2.0.0

UNISIG SUBSET-033

FIS for Man-Machine Interface

2.0.0

UNISIG SUBSET-034

FIS for the Train Interface

2.0.0

UNISIG SUBSET-035

Specific Transmission Module FFFIS

2.1.1

UNISIG SUBSET-036

FFFIS for Eurobalise

2.2.1

10

UNISIG SUBSET-037

Euroradio FIS

2.2.5

11

UNISIG SUBSET-038

Key Management FIS

2.0.0

12

UNISIG SUBSET-039

FIS for the RBC/RBC Handover

2.0.0

13

UNISIG SUBSET-040

Dimensioning and Engineering rules

2.0.0

14

UNISIG SUBSET-041

Performance Requirements for Interoperability

2.0.0

15

UNISIG SUBSET-043

FFFS for Euroloop subsystem

2.0.0

16

UNISIG SUBSET-044

FFFIS `AL Euroloop sub-system

2.0.0

17

UNISIG-SUBSET-045

FFFIS `CL Euroloop sub-system

2.0.0

18

UNISIG SUBSET-046

Radio In-fill FFFS

2.0.0

19

UNISIG SUBSET-047

Track-side-Trainborne FIS for Radio In-Fill

2.0.0

20

UNISIG SUBSET-048

Trainborne FFFIS for Radio In-Fill

2.0.0

21

UNISIG SUBSET-049

Radio In-fill FIS with LEU/Interlocking

2.0.0

22

UNISIG SUBSET-093

GSM-R Interfaces Class 1 requirements

2.2.6

23

UNISIG SUBSET-054

Assignment of Values to ETCS variables

2.0.0

24

UNISIG SUBSET-055

Clarification and amendment specification

2.2.2

25

UNISIG SUBSET-056

STM FFFIS Safe Time Layer

2.2.0

26

UNISIG SUBSET-057

STM FFFIS Safe Link Layer

2.2.0

27

UNISIG SUBSET-091

Safety Requirements for the Technical Interoperability of ETCS in 2.2.2

Levels 1 & 2

28

Reserved

Reliability Availability Requirements

29

Intentionally deleted

Environmental Physical Conditions

30

Intentionally deleted

Essential requirements for data recording

31

Intentionally blank

32

EIRENE FRS

GSM-R Functional Requirements Specification

33

EIRENE SRS

GSM-R System Requirements Specification

14

34

A11T6001 12

(MORANE) Radio Transmission FFFIS for EuroRadio

12

35

ECC/DC(02)05

ECC Decision of 5 July 2002 on the designation and availability

of frequency bands for railway purposes in the 876-880 and 921925 MHz bands.

36

Intentionally deleted

37a

UNISIG SUBSET-076-5-1

ERTMS ETCS Class 1 Feature List

2.2.1

37b

UNISIG SUBSET-076-5-2

Test cases related to features

2.2.1

37c

UNISIG SUBSET-076-6-3

Test sequences

1.0.0

37d

UNISIG SUBSET-076-7

Scope of the test specifications

1.0.0

38

Intentionally deleted

39

UNISIG SUBSET-092-1

ERTMS EuroRadio Conformance Requirements

2.2.5

40

UNISIG SUBSET-092-2

ERTMS EuroRadio Test cases Safety Layer

2.2.5

25/30

41

Reserved
028)

(UNISIG SUBSETJRU Test Specification

42

Reserved

Requirements for vigilance

43

UNISIG SUBSET 085

Test Specification for Eurobalise FFFIS

44

Reserved

Odometry FIS

45

Reserved

K interface

46

Intentionally deleted

47

04E085

Requirements on risk and hazard analysis for interoperability

48

Reserved

Test specification for mobile equipment GSM-R

49

Intentionally deleted

50

Reserved (UNISIG SUBSET ?) Test specification for EUROLOOP

51

Reserved (EEIG)

Ergonomic aspects of the DMI

52

UNISIG SUBSET-058

FFFIS STM Application Layer

53

Reserved (L-TR-001)

ETCS values of variables controlled by UIC

54

Reserved
(provisionally))

55

Reserved

Juridical recorder baseline requirements

56

Reserved

Characteristics of retro-reflecting signs

57

Reserved

Requirements on pre-fitting of ERTMS on-board equipment

58

Reserved

RBC safety communication interface

59

Reserved

Requirements on pre-fitting of ERTMS track side equipment

60

Reserved

ETCS version management

(04E117Quality of Service user requirements (provisionally)

61
Reserved
GSM-R version management
* Version to be updated (TSI Control-Command CR change requests on FRS forwarded to CCM)
** ERTMS references are to be reviewed after the consolidation phase.

26/30

2.1.2

2.1.1

LIST OF MANDATORY EN STANDARDS

Index N

Reference

Document Name and comments

A1

EN 50126

Railway applications The specification and demonstration of 1999

reliability, availability, maintainability and safety (RAMS)

A2

EN 50128

Railway applications Communication, signalling and processing 2001

systems Software for railway control and protection systems

A3

EN 50129

Railway applications Communication, signalling and processing 2003

systems Safety related electronic systems for signalling

A4

EN 50125-1

Railway applications Environmental conditions for equipment 1999

Part 1: equipment on board rolling stock

A5

EN 50125-3

Railway applications Environmental conditions for equipment 2003

Part 3: equipment for signalling and telecommunications

A6

EN 50121-3-2

Railway applications Electromagnetic compatibility - Part 3-2: 2000

Rolling stock Apparatus

A7

EN 50121-4

Railway applications - Electromagnetic compatibility - Part 4:2000

Emission and immunity of the signalling and telecommunications
apparatus

A8

EN 310 515

Global System for Mobile communication (GSM); Requirements2.1.0

for GSM operation in railways.

A9
A10
A11
A12
A13
A14
A15

27/30

Version

LIST OF INFORMATIVE SPECIFICATIONS

Note:
Type 1 specifications represent the current state of the work for the preparation of a
mandatory specification still reserved
Type 2 specifications give additional information, justifying the requirements in mandatory
specifications and providing help for their application

Index N Reference

Document Name

Version Type

B1

EEIG 02S126

RAM requirements (chapter 2 only)

2 (index 28)

B2

EEIG 97S066

Environmental conditions

2 (index A5)

B3

EEIG 97E832

Degraded Situations

B4

EEIG 97E267

ODOMETER FFFIS

1 (Index 44)

B5

O_2475

ERTMS GSM-R QoS Test Specification

1.0.0

B6

UNISIG SUBSET 050

Description of Euroloop subsystem

2.0.0

2 (Index 15)

B7

intentionally deleted

B8

UNISIG SUBSET 059

STM performance requirements

2.0.0

B9

UNISIG SUBSET 076_0

ERTMS/ETCS Class 1, Test plan

2.2.2

2 (Index 37)

B10

UNISIG SUBSET 076_2

Methodology to prepare features

2.2.1

2 (Index 37)

B11

UNISIG SUBSET 076_3

Methodology of testing

2.2.1

2 (Index 37)

B12

UNISIG SUBSET 076_4_1 Test sequence generation: Methodology and Rules

1.0.0

2 (Index 37)

B13

UNISIG SUBSET 076_4_2 ERTMS ETCS Class 1 States for Test Sequences

1.0.0

2 (Index 37)

B14

UNISIG SUBSET 076_5_3 On-Board Data Dictionary

2.2.0

2 (Index 37)

B15

UNISIG SUBSET 076_5_4 SRS v.2.2.1 Traceability

2.2.1

2 (Index 37)

B16

UNISIG SUBSET 076_6_1 UNISIG test data base

1.0.0

2 (Index 37)

B17

UNISIG SUBSET 076_6_4 Test Cases Coverage

1.0.0

2 (Index 37)

B18

UNISIG SUBSET 076_6_5 Test data base

1.0.0

2 (Index 37)

B19

UNISIG SUBSET 077

UNISIG Causal Analysis Process

2.2.2

2 (Index 27)

B20

UNISIG SUBSET 078

RBC interface: Failure modes and effects analysis

2.2.2

2 (Index 27)

B21

UNISIG SUBSET 079

MMI: Failure Modes and Effects Analysis

2.2.2

2 (Index 27)

B22

UNISIG SUBSET 080

TIU: Failure Modes and Effects Analysis

2.2.2

2 (Index 27)

B23

UNISIG SUBSET 081

Transmission system: Failure Modes and Effects Analysis 2.2.2

2 (Index 27)

B24

UNISIG SUBSET 088

ETCS Application Levels 1&2 -Safety Analysis

2 (Index 27)

B25

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 1 - Ergonomic principles of ERTMS/ETCS/GSM-R
Information

2 (Index 51)

B26

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 2 - Ergonomic arrangements of ERTMS/ETCS
Information

2 (Index 51)

B27

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 3 - Ergonomic arrangements of ERTMS/GSM-R
Information

2 (Index 51)

B28

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 4 - Data Entry Procedure

2 (Index 51)

B29

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 5 - Symbols

2 (Index 51)

B30

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 6 - Audible Information

2 (Index 51)

B31

EN50xxx

Railway applications -European Rail Traffic Management

System
Driver
Machine
Interface"
part 7 - Specific Transmission Modules

2(Index 51)

28/30

2.2.2

29/30

30/30