Commission Decision of 25 January 2012 on the technical specification for interoperability relating to the control-command and signalling subsystems of the trans-European rail system (notified under document C(2012) 172) (Text with EEA relevance) (2012/88/EU) (repealed)

6. ASSESSING THE CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFYING THE SUBSYSTEMS

6.1. Introduction

6.1.1. General principles

Fulfilment of the essential requirements set out in Chapter 3 of this TSI shall be ensured through compliance with the basic parameters specified in Chapter 4.

This compliance shall be demonstrated by:

1.

assessing the conformity of the interoperability constituents specified in Chapter 5 (see Section 6.2);

2.

verifying the subsystems (see Section 6.3).

In certain cases, however, some of the essential requirements may be met by national rules, because of:

1.

the use of Class B systems;

2.

open points in the TSI;

3.

derogations pursuant to Article 9 of the Railway Interoperability Directive;

4.

specific cases described in Section 7.2.9.

In such cases, assessment of conformity with those rules shall be carried out under the responsibility of the Member States concerned according to notified procedures.

6.1.2. Principles for testing ERTMS/ETCS and GSM-R

A Control-Command and Signalling On-board Subsystem covered by an ‘EC’ declaration of verification should be able to run on every Control-Command and Signalling Track-side Subsystem covered by an ‘EC’ Declaration of verification, under the conditions specified in this TSI, with no additional verifications.

Achievement of this goal is facilitated by:

1.

rules for the design and installation of the Control-Command and Signalling On-board and the Track-side subsystems;

2.

test specifications to prove that the Control-Command and Signalling On-board and Track-side Subsystems comply with the requirements of this TSI and are mutually compatible.

To make the conformity assessment of ERTMS/ETCS and GSM-R equipment more effective and to help achieve the goal mentioned above, each Member State shall make available to the Commission the operational test scenarios for checking the ERTMS/ETCS and GSM-R part of the Control-Command and Signalling Track-side Subsystem and its interaction with the corresponding part of the Control-Command and Signalling On-board Subsystem. The test scenarios in question:

1.

shall be consistent with the specifications referenced in this TSI and provide a technical description of functions and performances (e.g. reaction times) where these are relevant for the interaction between on-board and track-side subsystems;

2.

shall be submitted in a standard format. See Annex A 4.2.2.c;

3.

shall, unless otherwise specified in Annex A 4.2.2.c, cover at least the start of mission, the transition between levels, transition between modes that may be used on the line, the main identified degraded situations, the sending of emergency messages and any other relevant aspects specific to the line.

The European Railway Agency:

1.

shall make a preliminary publication of the operational test scenarios, allowing all interested parties to comment on the consistency of the test scenarios with the specifications referenced in this TSI and their impact on other implementations or developments. The period for comments shall be defined with each publication and shall not exceed 6 months;

2.

if the comments are negative, shall coordinate the efforts of the parties involved, in order to find an agreement, e.g. by changing the operational test scenarios;

3.

shall progressively build and make publicly available a database of test scenarios that have successfully passed the step described above and representing the situations which occur in different implementations;

4.

shall use the abovementioned data base to assess whether further mandatory test specifications are needed and whether it is necessary to draw up additional engineering rules for the Control-Command and Signalling On-board and Track-side subsystems.

6.2. Interoperability constituents

6.2.1. Assessment procedures for Control-Command and Signalling Interoperability Constituents

Before placing on the market an interoperability constituent and/or groups of interoperability constituents the manufacturer or his authorised representative established within the European Union shall draw up an ‘EC’ declaration of conformity in accordance with Article 13(1) and Annex IV to the Railway Interoperability Directive.

The assessment procedure shall be carried out using one of the modules specified in Section 6.2.2 (Modules for Control-Command and Signalling Interoperability Constituents).

An ‘EC’ declaration of suitability for use is not required for Control-Command and Signalling interoperability constituents, because they have to fully comply with all the relevant basic parameters. This compliance is demonstrated by the ‘EC’ Declaration of conformity and is sufficient for placing them on the market(1).

6.2.2. Modules for Control-Command and Signalling Interoperability Constituents

For assessing interoperability constituents within the Control-Command and Signalling Subsystems, the manufacturer or his authorised representative established within the European Union, may choose:

1.

either the type-examination procedure (Module CB) for the design and development phase in combination with the production quality management system procedure (Module CD) for the production phase; or

2.

the type-examination procedure (Module CB) for the design and development phase in combination with the product verification procedure (Module CF); or

3.

the full quality management system with design examination procedure (Module CH1).

In addition, for checking the SIM card Interoperability Constituent, the manufacturer or his representative may choose module CA.

The modules are described in detail in Commission Decision 2010/713/EU of 9 November 2010 on modules for the procedures for assessment of conformity, suitability for use and ‘EC’ verification to be used in the technical specifications for interoperability adopted under Directive 2008/57/EC of the European Parliament and of the Council(2).

The following clarifications apply to the use of some of the modules:

1.

with reference to Chapter 2 of the ‘Module CB’, ‘EC’-type examination must be carried out through a combination of production type and design type;

2.

with reference to Chapter 3 of the ‘Module CF’ (product verification) statistical verification is not allowed, i.e. all interoperability constituents must be individually examined.

6.2.3. Assessment requirements

Independently of the selected module:

1.

the requirements stated in Section 6.2.4.1 of this TSI shall be respected for the ‘On-board ERTMS/ETCS’ interoperability constituent;

2.

the activities shown in Table 6.1 shall be carried out when assessing the conformity of an interoperability constituent or a group of interoperability constituents as defined in Chapter 5 of this TSI. All verifications shall be carried out by reference to the applicable table in Chapter 5 and the basic parameters indicated there.

Table 6.1

Aspect	What to assess	supporting evidence
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 scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
	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 scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
	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
Environment	Check compliance with mandatory environmental conditions, where specified in the basic parameters referenced in the relevant table of Chapter 5	Tests, to ensure that the requirements of the basic parameters referenced in the relevant table of Chapter 5 are satisfied
	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
Reliability, Availability, Maintainability, Safety (RAMS)	Check compliance with the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5, i.e.: 1. respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures; 2. the development process is able to detect and eliminate systematic failures.	1. Calculations for the THRs caused by random failures, based on supportable sources of reliability data. 2.1. The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note). 2.2. The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note). 2.3. The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5. 2.4. The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note). Note: The standard shall satisfy at least the following requirements: 1. be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body; 2. be relevant for the control of the considered hazards in the system under assessment; 3. be publicly available for all actors who want to use it. See Annex A, Table A 3.
	Check that the quantitative reliability target indicated by the applicant is met	Calculations
	Check compliance with maintenance requirements – Section 4.5.1	Document check

6.2.4. Special issues

6.2.4.1. The on-board ERTMS/ETCS

Particular attention shall be given to assessing the conformity of the on-board ERTMS/ETCS interoperability constituent, since it is complex and plays a key role in achieving interoperability.

Regardless of whether module CB or CH1 is chosen, the Notified Body shall check that a specimen of the interoperability constituent has passed the full set of mandatory test sequences referenced in Section 4.2.2 (on-board ERTMS/ETCS functionality) and that these tests were carried out in a laboratory accredited to carry out this type of tests in accordance with Regulation (EC) No 765/2008 of the European Parliament and of the Council of 9 July 2008 setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93(3).

In addition, to increase confidence that the on-board ERTMS/ETCS can be correctly operated with different track-side applications, it is recommended that the on-board ERTMS/ETCS be tested using scenarios from the data base managed by the Agency and which are not part of the mandatory test specifications; see Section 6.1.2 (Principles for testing ERTMS/ETCS and GSM-R). The documentation accompanying the certificate shall indicate the database scenarios against which the interoperability constituent has been checked.

6.2.4.2. The Specific Transmission Module (STM)

Each Member State shall be responsible for verifying that STMs conform to its national requirements.

Verification of the STM interface to the on-board ERTMS/ETCS requires a conformity assessment carried out by a Notified Body.

6.2.4.3. Content of the ‘EC’ Declaration of conformity

The ‘EC’ Declaration of conformity specified in Annex IV to the Railway Interoperability Directive shall include the following details concerning the interoperability constituent:

1.

which optional and additional functions are implemented;

2.

the applicable environmental conditions.

6.3. Control-Command and Signalling Subsystems

6.3.1. Assessment procedures for Control-Command and Signalling Subsystems

This chapter deals with the ‘EC’ declaration of verification for the Control-Command and Signalling On-board Subsystem and the ‘EC’ declaration of verification for the Control-Command and Signalling Track-side Subsystem.

At the request of the applicant the Notified Body shall carry an ‘EC’ verification of a Control-Command and Signalling On-board or Track-side Subsystem in accordance with Annex VI to the Railway Interoperability Directive.

The applicant shall draw up the ‘EC’ declaration of verification for the Control-Command and Signalling On-board or Track-side Subsystem in accordance with Article 18(1) and Annex V to the Railway Interoperability Directive.

The content of the ‘EC’ declaration of verification shall conform to Annex V to the Railway Interoperability Directive.

The assessment procedure shall be carried out by using one of the modules as specified in Section 6.3.2 (Modules for Control-Command and Signalling Subsystems).

The ‘EC’ declarations of verification for a Control-Command and Signalling On-board Subsystem and of a Control-Command and Signalling Track-side Subsystem, together with the certificates of conformity, shall be deemed sufficient to ensure that the subsystems are compatible under the conditions specified in this TSI.

6.3.2. Modules for Control-Command and Signalling Subsystems

All modules indicated below are specified in the Decision 2010/713/EU.

6.3.2.1. On-board Subsystem

For verifying the Control-Command and Signalling On-board Subsystem, the applicant may choose either:

1.

the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or

2.

the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or

3.

the full quality management system with design examination procedure (Module SH1).

6.3.2.2. Track-side Subsystem

For verifying the Control-Command and Signalling Track-side Subsystem, the applicant may choose either:

1.

the unit verification procedure (Module SG); or

2.

the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or

3.

the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or

4.

the full quality management system with design examination procedure (Module SH1).

6.3.2.3. Conditions for using modules for On-board and Track-side Subsystems

With reference to Section 4.2 of Module SB (type-examination), design review is requested.

With reference to Section 4.2 of Module SH1 (full quality management system with design examination), a type test is required.

6.3.3. Assessment requirements for an On-board Subsystem

Table 6.2 shows the checks that must be carried out when verifying a Control-Command and Signalling On-board Subsystem and the basic parameters that must be respected.

Independently of the module chosen:

1.

verification shall demonstrate that the Control-Command and Signalling On-board Subsystem complies with basic parameters when it is integrated into the vehicle;

2.

the functionality and performances of interoperability constituents already covered by their EC Declaration of conformity do not require additional verifications.

Table 6.2

a In this case, the assessment of the management of transitions shall be according to national specifications.
Aspect	What to assess	supporting evidence
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.	Existence and content of documents
	Check restrictions on the use of Interoperability Constituents against the characteristics of the subsystem and of the environment	Analysis by document check
	For interoperability constituents that have been certified against older versions of the CCS TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force.	Impact analysis by document checks
Integration of interoperability constituents in the subsystem	Check the correct installation and functioning of the internal interfaces of the subsystem – Basic parameters 4.2.6	Checks according to specifications
	Check that additional functions (not specified in this TSI) do not impact the mandatory ones	Impact analysis
	Check that the values of ETCS IDs are within the allowed range – Basic parameter 4.2.9	Check of design specifications
Integration with rolling stock	Check the correct installation of equipment – Basic Parameters 4.2.2, 4.2.4, 4.2.14 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)
	Check that the Control-Command and Signalling On-board Subsystem is compatible with the rolling stock environment	Document check (certificates of interoperability constituents and possible integration methods checked against characteristics of rolling stock)
	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)
Integration with Class B	Check that the external STM is connected to on-board ERTMS/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
	Check that Class B functions implemented in the on-board ERTMS/ETCS – Basic parameter 4.2.6.1 – create no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions	Nothing to test: everything has already been tested at interoperability constituent level
	Check that separate Class B equipment which is not connected to the on-board ERTMS/ETCS – Basic Parameter 4.2.6.1 – creates no additional requirements for Control-Command and Signalling Track-side Subsystem due to transitions	Nothing to test: no interfacea
	Check that separate Class B equipment connected on-board ERTMS/ETCS using (partly) non-TSI compliant interfaces – basic parameter 4.2.6.1 – creates no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions. Also check that ERTMS/ETCS functions are not affected	Impact analysis
Integration with Control-Command and Signalling Track-side 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 should not be repeated) – Basic Parameter 4.2.5	Test using a certified Eurobalise: the ability to read correctly the telegram is the supporting evidence.
	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.
	Check that the equipment can handle a GSM-R call for voice and data (if applicable) – Basic Parameter 4.2.5	Test with a certified GSM-R network. The ability to set up, maintain and disconnect a connection is the supporting evidence.
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
	Check that the quantitative reliability target is met – Basic Parameter 4.2.1	Calculations
	Check the compliance with requirements about maintenance – Section 4.5.2	Documents check
Integration with Control-Command and Signalling Track-side Subsystems and other subsystems: tests under operational conditions	Test the behaviour of the subsystem under as many different operational conditions as reasonably possible (e.g. line gradient, train speed, vibrations, traction power, weather conditions, design of Control-Command and Signalling track-side functionality). The test must be able to verify: 1. that odometry functions are correctly performed – basic parameter 4.2.2 2. that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16 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 earlier stages: tests performed on the interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. Tests under operational conditions are not necessary for on-board GSM-R voice equipment.	Reports of test runs. Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated

6.3.4. Assessment requirements for a Track-side Subsystem

The purpose of assessments carried out within the scope of this TSI is to verify that the equipment complies with the requirements stated in Chapter 4.

However, for the design of the ERTMS/ETCS part of the Control-Command and Signalling Track-side Subsystem, application-specific information is needed; This should include:

1.

line characteristics such as gradients, distances, positions of route elements and Eurobalises/Euroloops, locations to be protected, etc;

2.

the signalling data and rules to be handled by the ERTMS/ETCS system.

This TSI does not cover checks to assess whether the application-specific information is correct:

Regardless of the module chosen:

1.

Table 6.3 shows the checks that must be carried out to verify a Control-Command and Signalling Track-side Subsystem and the basic parameters that must be respected;

2.

functionality and performances that have already been checked at the level of the interoperability constituents do not require additional verification.

Table 6.3

Aspect	What to assess	supporting evidence
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
	Check restrictions on the use of interoperability constituents against the characteristics of the subsystem and of the environment	Impact analysis by documents check
	For interoperability constituents that have been certified against older versions of the Control-Command and Signalling TSI, 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
Use of train detection systems	Check that the selected types comply with Control-Command and Signalling TSI requirements – Basic parameters 4.2.10, 4.2.11	Document check
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	Checks according to specifications
	Check that additional functions (not specified in this TSI) do not impact the mandatory ones	Impact analysis
	Check that the values of ETCS IDs are within the allowed range – Basic Parameter 4.2.9	Check of design specifications
Integration with infrastructure	Check that the equipment has been properly installed – Basic parameters 4.2.3, 4.2.4 and conditions for installation specified by the manufacturer	Results of checks (according to specifications referenced in the basic parameters and manufacturer’s installation rules)
	Check that the Control-Command and Signalling Track-side subsystem equipment is compatible with the track-side environment	Document check (certificates of interoperability constituents and possible methods of integration checked against track-side characteristics)
Integration with track-side signalling	Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI – Basic parameter 4.2.3	Document check (applicant’s design specification and certificates of interoperability constituents)
	Check the correct configuration of parameters (Eurobalise telegrams, RBC messages, marker boards positions, etc.)	Document check (values of parameters checked against characteristics of track-side and of signalling)
	Check that the interfaces are correctly installed and function properly.	Design verification and tests according to information supplied by the applicant
	Check that the Control-Command and Signalling Track-side subsystem operates correctly according to information at the interfaces with track-side 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
Integration with Control-Command and Signalling On-board Subsystems and with rolling stock	Check the GSM-R coverage – Basic Parameter 4.2.4	On-site measurements
	Check the compliance of the train detection systems with the requirements of this TSI – Basic Parameter 4.2.10	On-site measurements
	Check that the train detection systems comply with the requirements of this TSI – Basic parameters 4.2.10 and 4.2.11	Check evidence from existing installations (for systems already in use); perform tests according to standards for new types
	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 tests of the operational scenarios specified in Section 6.1.2 with different certified Control-Command and Signalling On-board Subsystems. The report shall indicate which operational scenarios have been tested, which on-board equipment has been used and whether tests have been performed in laboratories, test lines or real implementation.
Reliability, Availability, Maintainability, Safety (RAMS)	Check compliance with safety requirements – Basic Parameter 4.2.1	Application of procedures specified in the Common Safety Method
	Check that quantitative reliability targets are respected – Basic Parameter 4.2.1	Calculations
	Check the compliance with requirements about maintenance – Section 4.5.2	Document check
Integration with Control-Command and Signalling On-board Subsystems and rolling stock: tests under operational conditions	Test the behaviour of the subsystem under such different operational conditions as reasonably feasible (e.g. train speed, number of trains on the line, weather conditions). The test must be able to verify: 1. the performance of train detection systems – Basic parameters 4.2.10, 4.2.11, 2. that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16 These tests will also increase confidence in the absence of systematic failures. The scope of these tests excludes tests already done in previous 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. Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated.

6.4. Provisions for partial conformity

6.4.1. Introduction

Pursuant to Article 18(4) of the Railway Interoperability Directive, ‘the Notified Body may issue Intermediate Statement Verifications (ISVs) to cover certain stages of the verification procedure or certain parts of the subsystem’.

As pointed out in Section 2.2 (Scope) of this TSI, the Control-Command and Signalling Subsystems include three parts, which are specified in Section 4.1 (Introduction).

Section 6.4.2 deals with the verification of these parts of the Control-Command and Signalling Subsystems.

Section 6.4.3 deals with the verification of partial conformity of Control-Command and Signalling Subsystems when there are restricted conditions of use of its interoperability constituent(s).

6.4.2. Assessment of parts of Control-Command and Signalling Subsystems

Assessing whether a Control-Command and Signalling Track-side or On-board Subsystem complies with the requirements of this TSI is a process that may be performed in successive steps – one for each of the three parts. At each step, the assessor checks only whether that particular part complies with the TSI requirements.

Regardless of which module is chosen, the Notified Body shall verify that:

1.

the TSI requirements for the part in question have been respected;

2.

the TSI requirements already assessed are not prejudiced.

Functions already assessed and unchanged and which are not affected by this step do not need to be checked again.

6.4.3. Partial conformity of Control-Command and Signalling Subsystems due to restricted conditions of use of its interoperability constituent(s)

A partial certificate of conformity for an interoperability constituent can be issued even if some function, interface or performance has not been implemented, provided that:

1.

The non-implemented function, interface or performance is not required for integrating the interoperability constituent into a subsystem because of specific conditions of use, for example(4):

(a)

the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;

(b)

the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.

2.

The certificate indicates which functions, interfaces or performance are not implemented and states the corresponding restrictions on the use of the interoperability constituent. This information will make it possible to identify the conditions under which the interoperability constituent can be used and the restrictions that will apply to the interoperability of a subsystem incorporating it.

In any event, the conditions for issuing such certificates with restrictions shall be coordinated between the Notified Bodies and the Agency in a working group set up pursuant to Article 21a(5) of Regulation (EC) No 881/2004 of the European Parliament and of the Council of 29 April 2004 establishing a European Railway Agency (Agency Regulation)(5).

When the interoperability constituent is integrated into a Control-Command and Signalling On-board or Track-side Subsystem, if the missing functions, interfaces, or performances do not allow to assess whether the subsystem fully complies with the requirements of this TSI, only an Intermediate Statement of Verification may be issued. It shall indicate which requirements have been assessed and shall state the corresponding restrictions on the use of the subsystem and its compatibility with other subsystems.

(1)

Checking that an Interoperability Constituent is used appropriately is part of the overall EC verification of Control-Command and Signalling On-board and Track-side Subsystems, as explained in 6.3.3 and 6.3.4.

(2)

OJ L 319, 4.12.2010, p. 1.

(3)

OJ L 218, 13.8.2008, p. 30.

(4)

The procedures described in this Chapter do not prejudice the possibility of grouping constituents together.

(5)

OJ L 164, 30.4.2004, p. 1.