Processes and Responsibilities ERA ETCS Conference on Testing and Certification Lille March 29 th 2011
Overview The principles for authorisation The application of the principles How the CCS TSI supports the principles Lille, March 29 th 2011 2
The principles for authorisation Interoperability Directive, art. 15/1 the MS shall ensure that the subsystems meet the essential requirements and in particular the technical compatibility of subsystems with the system and the safe integration Safety Directive, art. 4 MS shall ensure that railway safety is maintained (art. 4) risk evaluation whenever a change of operating conditions or new material imposes new risks (Annex III) Lille, March 29 th 2011 3
The principles for authorisation The installation of ERTMS is normally a significant change in the meaning of the Safety Directive This means that both the Interoperability Directive and the Safety Directive shall be applied A problem or a help? The two Directives cooperate to define a complete reference framework for authorisation, but an appropriate mapping of the legal requirements of the two Directives on the development and certification process is necessary Lille, March 29 th 2011 4
The application of the principles Let s start from the beginning (and consider the case of a track-side implementation) The Safety Directive requires a system based approach System What do we expect from ERTMS in the specific application? (headway, train speed, tunnels, shunting areas, legacy systems, etc.) Constraints from TSIs and Regulation 352/2009 (e.g., being able to accept a TSI compliant train) Constraints from TSIs (e.g., Interoperability Constituents) and other regulations Subsystem Product Which functions do we have to implement and how? Do we need 1 or 2? Do we need Shunting? Reversing? Transitions to/from legacy systems? etc. Which are the characteristics of the products we need? Lille, March 29 th 2011 5
The application of the principles And now the complete cycle System Additional work to do? Safety Directive CSM for risk evaluation and assessment methods System Subsystem Duplication? Conflict? EC Declaration of Subsystem Verification Subsystem Product EC Declaration of Conformity Product TSIs (NNTRS) Lille, March 29 th 2011 6
The application of the principles Let try to summarise Art 15 of the Interoperability Directive does not require that products are developed and assembled delegating only to a final set of tests the verification, whether the subsystems fits in the system and works well Technical compatibility and safe integration shall be taken into account at the beginning of the project (this is the only possibility to test them at the end) For a track-side implementation, technical compatibility and safe integration include the obligation to design the subsystem for the acceptance of any TSI compliant vehicle Lille, March 29 th 2011 7
The application of the principles What is the final verification of technical compatibility and safe integration? DV 29, section 5.3: where relevant TSIs exist and apply, verification of technical compatibility is carried out by reference of TSIs ; safe integration is part of the essential requirements. Therefore it is covered, as a general rule, by TSIs or national rules Additional verifications (specific for a MS) are only required for aspects not (yet) covered by a TSI and shall be according to national rules Lille, March 29 th 2011 8
How the CCS TSI supports the principles Coordination between CSM and CCS TSI TSI requires the application of CSM, with no exported requirements across the interface between on-board and track-side (this is a mirror requirement of art. 2/2 of the CSM regulation) TSI contains full mandatory specification of the onboard functions and performance and of the interface between on-board and track-side In the context of the EC subsystem verification it has to be checked that the functions required by the application are implemented in accordance with the TSI Lille, March 29 th 2011 9
How the CCS TSI supports the principles Verifying technical compatibility and safe integration MSs are required to ensure that operational scenarios for the track-side ERTMS/ETCS implementation are made available Running such operational scenarios against certified on-board equipment will allow a progressive reduction of the risk that a track-side implementation is not compatible with authorised vehicles, going towards the target: Vehicles are authorised on the basis of compliance with rules authorisation of TSI compliant vehicles is valid in all MSs, without additional checks. Track-side is responsible of being interoperable Lille, March 29 th 2011 10