- Latest available (Revised)
- Original (As adopted by EU)
Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed technical requirements and test procedures for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards (Text with EEA relevance)
When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.
Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).
This is the original version as it was originally adopted in the EU.
This legislation may since have been updated - see the latest available (revised) version
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Regulation (EU) 2015/758 of the European Parliament and of the Council of 29 April 2015 concerning type-approval requirements for the deployment of the eCall in-vehicle system based on the 112 service and amending Directive 2007/46/EC(1), and in particular Article 2(2), Article 5(8) and (9) and Article 6(12) thereof,
Whereas:
(1) Regulation (EU) 2015/758 lays down a general obligation for new types of vehicles of categories M1 and N1 to be equipped with 112-based eCall in-vehicle systems as of 31 March 2018.
(2) It is necessary to set out the detailed technical requirements and test procedures for the approval of motor vehicles with respect to their 112-based eCall in-vehicle systems. The test procedures also allow for testing and approval of 112-based eCall in-vehicle separate technical units (‘STUs’) and components intended for fitment in motor vehicles or for integration in 112-based eCall in-vehicle systems.
(3) Tests should be carried out by technical services in their capacity as foreseen in Directive 2007/46/EC of the European Parliament and of the Council(2) that establishes the general framework for the EC type-approval of motor vehicles and defines the roles and responsibilities of all the actors involved at different stages of the approval process.
(4) Tests and requirements should be designed in such a way that duplicated testing is avoided. In addition, some flexibility is required regarding special purpose vehicles that are built in multiple stages in accordance with Directive 2007/46/EC as they are exempted from the frontal and lateral collision requirements under UNECE Regulations 94 and 95. For that reason, the approval granted at a previous stage of the process to the base vehicle with respect to the 112-based eCall in-vehicle system should remain valid, unless the system or its sensors were modified after the approval.
(5) There are cases where certain classes of vehicles cannot for technical reasons be fitted with an appropriate eCall triggering mechanism and should be exempted from the requirements of Regulation (EU) 2015/758. Following an assessment of the costs and benefits carried out by the Commission and taking into account the relevant safety and technical aspects, those classes of vehicles are identified and included in a list established in Annex IX.
(6) The 112-based eCall in-vehicle system needs to remain functional after a severe accident. An automatic eCall is most beneficial in a high-severity collision where the risk of occupants of the vehicle being incapacitated and not able to call for assistance without an eCall system is highest. The 112-based eCall in-vehicle systems, components and STUs should therefore be tested to verify their sustained functionality after being subjected to inertial loads similar to those that may occur during a severe vehicle crash.
(7) The post-crash functioning and automatic triggering of the 112-based eCall in-vehicle system should also be ensured at vehicle level. A full-scale impact test procedure should therefore be set out to verify that the vehicle is constructed in such a way that its 112-based eCall in-vehicle system survives a frontal and side collision in its original mounting situation and configuration.
(8) The core functionality of a 112-based eCall in-vehicle system is not only to notify the Public Safety Answering Point (‘PSAP’) of an accident, but also to establish a voice connection between occupants of the vehicle and a PSAP operator. The audio equipment of the 112-based eCall in-vehicle system should therefore be tested after the full-scale crash tests to guarantee that it does not suffer loudness reduction or distortions that make voice communication impossible.
(9) Where a 112-based eCall in-vehicle system is approved for use in conjunction with a system providing third party services (‘TPS system’), it should be ensured that only one of those systems is active at a time and that the 112-based eCall in-vehicle system is triggered automatically when the TPS system does not function. The manufacturer of vehicles fitted with 112-based eCall in-vehicle system and TPS system should explain the fall-back procedure built-in the TPS system and describe the principles of the changeover mechanism between the TPS system and the 112-based eCall in-vehicle system.
(10) To ensure the provision of accurate and reliable position information, the 112-based eCall in-vehicle system should be able to use the positioning services provided by the Galileo and the EGNOS systems.
(11) The 112-based eCall in-vehicle system should warn the occupants of a vehicle in the event the system is unable to execute an emergency call. A procedure should therefore be set out for the verification of the self-testing of the system and of its compliance with the malfunction indication requirements.
(12) Manufacturers should ensure that the 112-based eCall in-vehicle systems are not traceable and not subject to any constant tracking. For that purpose, a test procedure should be set out to verify that the 112-based eCall in-vehicle system is not available for communication with the PSAP before the eCall is triggered.
(13) Any data processed through the 112-based eCall in-vehicle system must be adequate, relevant and proportionate to the purposes for which those data are collected and processed. To that end, appropriate procedures should be laid down to verify that the data in the internal memory of the system are automatically and continuously removed and are not retained longer than necessary for the purpose of handling the emergency call.
(14) The versions of the applicable standards on which the requirements for eCall are based should be updated.
(15) Vehicle manufacturers should be given sufficient time to adapt to the technical requirements for the approval of 112-based eCall in-vehicle systems. The Member States should also be given sufficient time to deploy on their territory the PSAP infrastructure required for the proper receipt and handling of emergency calls. For that reason, the date of application of this Regulation should be the same as the date of compulsory application of the 112-based eCall in-vehicle systems in accordance with Regulation (EU) 2015/758,
HAS ADOPTED THIS REGULATION:
Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles (Framework Directive) (OJ L 263, 9.10.2007, p. 1).
The Whole Regulation you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
The Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: