Directive (EU) 2016/797 of the European Parliament and of the Council of 11 May 2016 on the interoperability of the rail system within the European Union (recast) (Text with EEA relevance)

Type Directive
Publication 2016-05-26
Last updated 2026-08-02
State In force
Department Council of the European Union, European Parliament
Source EUR-Lex
articles 60
Reform history JSON API
2.4.3.   Technical compatibility

The electrical equipment must be compatible with the operation of the control-command and signalling installations.

In the case of electric traction, the characteristics of the current-collection devices must be such as to enable trains to travel under the energy-supply systems for the rail system.

The characteristics of the rolling stock must be such as to allow it to travel on any line on which it is expected to operate, taking account of relevant climatic conditions.

2.4.4.   Controls

Trains must be equipped with a recording device. The data collected by that device and the processing of the information must be harmonised.

2.4.5.   Accessibility

Rolling-stock subsystems to which the public has access must be accessible for persons with disabilities and persons with reduced mobility in accordance with point 1.6.

2.5.   Maintenance

2.5.1.   Health and safety

The technical installations and the procedures used in the centres must ensure the safe operation of the subsystem and not constitute a danger to health and safety.

2.5.2.   Environmental protection

The technical installations and the procedures used in the maintenance centres must not exceed the permissible levels of nuisance with regard to the surrounding environment.

2.5.3.   Technical compatibility

The maintenance installations for rolling stock must be such as to enable safety, health and comfort operations to be carried out on all stock for which they have been designed.

2.6.   Operation and traffic management

2.6.1.   Safety

Alignment of the network operating rules and the qualifications of drivers and on-board staff and of the staff in the control centres must be such as to ensure safe operation, bearing in mind the different requirements of cross-border and domestic services.

The maintenance operations and intervals, the training and qualifications of the maintenance and control centre staff and the quality assurance system set up by the operators concerned in the control and maintenance centres must be such as to ensure a high level of safety.

2.6.2.   Reliability and availability

The maintenance operations and periods, the training and qualifications of the maintenance and control centre staff and the quality assurance system set up by the operators concerned in the control and maintenance centres must be such as to ensure a high level of system reliability and availability.

2.6.3.   Technical compatibility

Alignment of the network operating rules and the qualifications of drivers, on-board staff and traffic managers must be such as to ensure operating efficiency on the rail system, bearing in mind the different requirements of cross-border and domestic services.

2.6.4.   Accessibility

Appropriate steps must be taken to ensure that operating rules provide for the necessary functionality required to ensure accessibility for persons with disabilities and persons with reduced mobility.

2.7.   Telematics applications for freight and passengers

2.7.1.   Technical compatibility

The essential requirements for telematics applications guarantee a minimum quality of service for passengers and carriers of goods, particularly in terms of technical compatibility.

Steps must be taken to ensure:

  • — that the databases, software and data communication protocols are developed in a manner allowing maximum data interchange between different applications and operators, excluding confidential commercial data,
  • — easy access to the information for users.
2.7.2.   Reliability and availability

The methods of use, management, updating and maintenance of these databases, software and data communication protocols must guarantee the efficiency of these systems and the quality of the service.

2.7.3.   Health

The interfaces between these systems and users must comply with the minimum rules on ergonomics and health protection.

2.7.4.   Safety

Suitable levels of integrity and dependability must be provided for the storage or transmission of safety-related information.

2.7.5.   Accessibility

Appropriate steps must be taken to ensure that telematics applications for passenger subsystems provide for the necessary functionality required to ensure accessibility for persons with disabilities and persons with reduced mobility.

ANNEX IV

‘EC’ VERIFICATION PROCEDURE FOR SUBSYSTEMS

1. GENERAL PRINCIPLES

‘ “EC” verification’ means a procedure carried out by the applicant within the meaning of Article 15 to demonstrate that the requirements of the relevant Union law and any relevant national rules relating to a subsystem have been fulfilled and the subsystem may be authorised to be placed in service.

2. CERTIFICATE OF VERIFICATION ISSUED BY A NOTIFIED BODY

2.1.   Introduction

For the purpose of this Directive, the verification by reference to TSIs is the procedure whereby a notified body checks and certifies that the subsystem complies with the relevant technical specifications for interoperability (TSI).

This is without prejudice to the obligations of the applicant to comply with the other applicable legal acts of the Union and any verifications by the assessment bodies required by the other rules.

2.2.   Intermediate statement of verification (ISV)

2.2.1   Principles

At the request of the applicant the verifications may be done for parts of a subsystem or may be limited to certain stages of the verification procedure. In these cases, the results of verification may be documented in an ‘intermediate statement of verification’ (ISV) issued by the notified body chosen by the applicant. The ISV must provide reference to the TSIs with which the conformity has been assessed.

2.2.2   Parts of the subsystem

The applicant may apply for an ISV for any part into which he decides to split the subsystem. Each part shall be checked at each stage as set out in point 2.2.3.

2.2.3   Stages of the verification procedure

The subsystem, or certain parts of the subsystem, shall be checked at each of the following stages:

  • (a) overall design;
  • (b) production: construction, including, in particular, civil-engineering activities, manufacturing, constituent assembly and overall adjustment;
  • (c) final testing.

The applicant may apply for an ISV for the design stage (including the type tests) and for the production stage for the whole subsystem or for any part into which the applicant decided to split it (see point 2.2.2).

2.3.   Certificate of verification

  • 2.3.1. The notified bodies responsible for the verification assess the design, production and final testing of the subsystem and draw up the certificate of verification intended for the applicant who in turn draws up the ‘EC’ declaration of verification. The certificate of verification must provide reference to the TSIs with which the conformity has been assessed.

Where a subsystem has not been assessed for its conformity with all relevant TSI(s) (e.g. in the case of a derogation, partial application of TSIs for upgrade or renewal, transitional period in a TSI or specific case), the certificate of verification shall give the precise reference to the TSI(s) or their parts whose conformity has not been examined by the notified body during the verification procedure.

  • 2.3.2. Where ISV have been issued, the notified body responsible for the verification of the subsystem takes these ISV into account, and, before issuing its certificate of verification:
  • (a) verifies that the ISV cover correctly the relevant requirements of the TSI(s);
  • (b) checks all aspects that are not covered by the ISV; and
  • (c) checks the final testing of the subsystem as a whole.
  • 2.3.3. In the case of a modification to a subsystem already covered by a certificate of verification, the notified body shall perform only those examinations and tests that are relevant and necessary, i.e. assessment shall relate only to the parts of the subsystem that are changed and their interfaces to the unchanged parts of the subsystem.
  • 2.3.4 Each notified body involved in the verification of a subsystem shall draw up a file in accordance with Article 15(4) covering the scope of its activities.

2.4.   Technical file accompanying the ‘EC’ declaration of verification.

The technical file accompanying the ‘EC’ declaration of verification shall be assembled by the applicant and must contain the following:

  • (a) technical characteristics linked to the design including general and detailed drawings with respect to execution, electrical and hydraulic diagrams, control-circuit diagrams, description of data-processing and automatic systems to the level of detail sufficient for documenting the verification of conformity carried out, documentation on operation and maintenance, etc., relevant for the subsystem concerned;
  • (b) a list of interoperability constituents, referred to in point (d) of Article 4(3), incorporated into the subsystem;
  • (c) the files referred to in Article 15(4), compiled by each of the notified bodies involved in the verification of the subsystem, which shall include:
  • — copies of the ‘EC’ declarations of verification and, where applicable, ‘EC’ declarations of suitability for use established for interoperability constituents referred to in point (d) of Article 4(3) and accompanied, where appropriate, by the corresponding calculation notes and a copy of the records of the tests and examinations carried out by the notified bodies on the basis of the common technical specifications,
  • — where available, the ISV that accompany the certificate of verification, including the result of verification by the notified body of the ISV validity,
  • — the certificate of verification, accompanied by corresponding calculation notes and signed by the notified body responsible for the verification, stating that the subsystem complies with the requirements of the relevant TSI(s) and mentioning any reservations recorded during performance of the activities and not withdrawn; the certificate of verification should also be accompanied by the inspection and audit reports drawn up by the same body in connection with its task, as specified in points 2.5.2 and 2.5.3;
  • (d) certificates of verification issued in accordance with other legal acts of the Union;
  • (e) when verification of safe integration is required pursuant to in point (c) of Article 18(4) and in point (c) of Article 21(3), the relevant technical file shall include the assessors' report(s) on the CSMs on risk assessment referred to in Article 6(3) of Directive 2004/49/EC ([^E0008]).

2.5.   Surveillance by notified bodies.

  • 2.5.1. The notified body responsible for checking production must have permanent access to building sites, production workshops, storage areas and, where appropriate, prefabrication or testing facilities and, more generally, to all premises which it considers necessary for its task. The notified body must receive from the applicant all the documents needed for that purpose and, in particular, the implementation plans and technical documentation concerning the subsystem.
  • 2.5.2. The notified body responsible for checking implementation must periodically carry out audits in order to confirm compliance with the relevant TSI(s). It must provide those responsible for implementation with an audit report. Its presence may be required at certain stages of the building operations.
  • 2.5.3. In addition, the notified body may pay unexpected visits to the worksite or to the production workshops. At the time of such visits the notified body may conduct complete or partial audits. It must provide those responsible for implementation with an inspection report and, if appropriate, an audit report.
  • 2.5.4. The notified body shall be able to monitor a subsystem on which an interoperability constituent is mounted in order to assess, where required by the corresponding TSI, its suitability for use in its intended railway environment.

2.6.   Submission

A copy of the technical file accompanying the ‘EC’ declaration of verification must be kept by the applicant) throughout the service life of the subsystem. It must be sent to any Member State or the Agency, upon request.

The documentation submitted for an application for an authorisation for placing in service shall be submitted to the authority where the authorisation is sought. The national safety authority or the Agency may request that part(s) of the documents submitted together with the authorisation is/are translated into its own language.

2.7.   Publication

Each notified body must periodically publish relevant information concerning:

  • (a) requests for verification and ISV received;
  • (b) request for assessment of conformity and suitability for use of ICs;
  • (c) ISV issued or refused;
  • (d) certificates of verification and ‘EC’ certificates for suitability for use issued or refused;
  • (e) certificates of verification issued or refused.

2.8.   Language

The files and correspondence relating to the ‘EC’ verification procedure must be written in a Union official language of the Member State in which the applicant is established or in a Union official language accepted by the applicant

3. CERTIFICATE OF VERIFICATION ISSUED BY A DESIGNATED BODY

3.1.   Introduction

In the case where national rules apply, the verification shall include a procedure whereby the body designated pursuant to Article 15(8), (the designated body) checks and certifies that the subsystem complies with the national rules notified in accordance with Article 14 for each Member State in which the subsystem is intended to be authorised to be placed in service.

3.2.   Certificate of verification

The designated body draws up the certificate of verification intended for the applicant.

The certificate shall contain a precise reference to the national rule(s) whose conformity has been examined by the designated body in the verification process.

In the case of national rules related to the subsystems composing a vehicle, the designated body shall divide the certificate into two parts, one part including the references to those national rules strictly related to the technical compatibility between the vehicle and the network concerned, and the other part for all other national rules.

3.3.   File

The file compiled by the designated body and accompanying the certificate of verification in the case of national rules must be included in the technical file accompanying the ‘EC’ declaration of verification referred to in point 2.4 and shall contain the technical data relevant for the assessment of the conformity of the subsystem with those national rules.

3.4.   Language

The files and correspondence relating to the ‘EC’ verification procedure must be written in a Union official language of the Member State in which the applicant is established or in a Union official language accepted by the applicant.

4. VERIFICATION OF PARTS OF SUBSYSTEMS IN ACCORDANCE WITH ARTICLE 15(7)

If a certificate of verification is to be issued for certain parts of a subsystem, provisions for this Annex shall apply mutatis mutandis for those parts.

ANNEX V

PART A

Repealed Directives with list of the successive amendments thereto

(referred to in Article 58)

Directive 2008/57/EC (OJ L 191, 18.7.2008, p. 1.)
Directive 2009/131/EC (OJ L 273, 17.10.2009, p. 12.)
Directive 2011/18/EU (OJ L 57, 2.3.2011, p. 21.)

PART B

Time limits for transposition into national law

(referred to in Article 57)

Directive Deadline for transposition
2008/57/EC 19 July 2010
2009/131/EC 19 July 2010
2011/18/EU 31 December 2011

ANNEX VI

Correlation table

Directive 2008/57/EC This Directive
Article 1 Article 1
Article 2(a) to (z) Article 2(1) to (5), (7) to (17) and (19) to (28)
- Article 2(6), (18) and (29) to (45)
Article 3 -
Article 4 Article 3
Article 5(1) to (3)(g) Article 4(1) to (3)(g)
- Article 4(3)(h) and (i)
Article 5(4) to (8) Article 4(4) to (8)
Article 6 Article 5
Article 7 Article 6
Article 8 -
Article 9 Article 7
Article 10 Article 8
Article 11 Article 9
Article 12 -
Article 13 Article 10
Article 14 Article 11
Article 15(1) Articles 18(2)
Article 15(2) and (3) -
Article 16 Article 12
Article 17 Articles 13 and 14
Article 18 Article 15
Article 19 Article 16
- Article 17
- Article 18 (except 18(3))
- Articles 19, 20, 21, 22 and 23
Article 20 -
Article 21 -
Articles 22 to 25 -
Article 26 Article 24
Article 27 Article 14(10)
- Article 26
Article 28 and Annex VIII Articles 27 to 44
- Article 45
Article 29 Article 51
Articles 30 and 31 -
Article 32 Article 46
Article 33 Article 47(3), (4), (6) and (7)
- Article 47(1), (2) and (5)
Article 34 Article 48
Article 35 Article 49
Article 36 -
- Article 50-
Article 37 Article 52
Article 38 Article 57
Article 39 Article 53
- Articles 54 and 55
- Article 56
Article 40 Article 58
Article 41 Article 59
Article 42 Article 60
Annex I to III Annex I to III
Annex IV Article 9(2)
Annex V Article 15(9)
Annex VI Annex IV
Annex VII Article 14(10)
Annex VIII Articles 30, 31 and 32
Annex IX Article 7(5)
Annex X Annex V
Annex XI Annex VI

[^E0001]: Directive 2012/34/EU of the European Parliament and of the Council of 21 November 2012 establishing a single European railway area (OJ L 343, 14.12.2012, p. 32).

[^E0002]: Commission Decision 2010/713/EU of 9 November 2010 on modules for the procedures for assessment of conformity, suitability for use and ‘EC’ verification to be used in the technical specifications for interoperability adopted under Directive 2008/57/EC of the European Parliament and of the Council (OJ L 319, 4.12.2010, p. 1).

[^E0003]: Commission Decision 98/500/EC of 20 May 1998 on the establishment of Sectoral Dialogue Committees promoting the Dialogue between the social partners at European level (OJ L 225, 12.8.1998, p. 27).

[^E0004]: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act) (OJ L, 2024/1689, 12.7.2024, ELI: http://data.europa.eu/eli/reg/2024/1689/oj).

[^E0005]: Directive (EU) 2015/1535 of the European Parliament and of the Council of 9 September 2015 laying down a procedure for the provision of information in the field of technical regulations and rules on Information Society services (OJ L 241, 17.9.2015, p. 1).

[^E0006]: Decision No 768/2008/EC of the European Parliament and of the Council of 9 July 2008 on a common framework for the marketing of products, and repealing Council Decision 93/465/EEC (OJ L 218, 13.8.2008, p. 82).

[^E0007]: Council Directive 96/48/EC of 23 July 1996 on the interoperability of the trans-European high-speed rail system (OJ L 235, 17.9.1996, p. 6).

[^E0008]: Directive 2004/49/EC of the European Parliament and of the Council of 29 April 2004 on safety on the Community's railways and amending Council Directive 95/18/EC on the licensing of railway undertakings and Directive 2001/14/EC on the allocation of railway infrastructure capacity and the levying of charges for the use of railway infrastructure and safety certification (Railway Safety Directive) (OJ L 164, 30.4.2004, p. 44).

Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.

This text is published under EUR-Lex's own terms of reuse, not a Legalize or public-domain licence. EUR-Lex
Creative Commons Attribution 4.0 International (CC BY 4.0)
© European Union, https://eur-lex.europa.eu — Source: EUR-Lex (Publications Office of the European Union). Reused under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. Only EU legislation published in the printed Official Journal of the European Union is deemed authentic; consolidated texts are reproduced here for documentation purposes and have been reformatted to Markdown.