DFRS & Euro NCAP
Supporting the exchange of Safety-Related Traffic Information through a common framework
In 2025, DFRS and Euro NCAP formalised their cooperation to enhance vehicle safety assessments through the integration of real-time road hazard data and Safety-Related Traffic Information.
The collaborationWhat the agreement changes
This partnership marks a major step forward in enhancing vehicle safety assessments by integrating real-time road hazard data into Euro NCAP’s vehicle performance protocols.
Read the press release
The joint announcement from DFRS and Euro NCAP.
The signed MoU
The Memorandum of Understanding in full.
The self-declarationsTemplates and guidance
Following Euro NCAP’s 2026 Protocol, vehicle manufacturers are encouraged to complete self-declaration forms developed by DFRS and Euro NCAP. These forms confirm that vehicles with Local Hazard data sharing capabilities properly transmit, receive, and process safety data within the DFRS ecosystem.
Completing these self-declarations is essential for validating compliance with the protocol’s requirements. This section provides step-by-step guidance and templates to support vehicle manufacturers in accurately completing their self-declarations.
Forms are hosted by ERTICO and open in a new tab.
Frequently asked questionsCommon questions about the declarations
Q1Can a DFRS Service Provider / Creator charge an OEM (DFRS member) for a feed with DFRS data?
Yes, but the fee must not be higher than for a feed without DFRS data.
Q2Can a DFRS Service Provider / Creator sell a feed with DFRS data to a non-DFRS OEM?
Yes. The provider acts on behalf of the non-DFRS OEM to meet DFRS obligations, including reciprocity and required documentation (SD1, SD2, SD3). Reporting duties remain with the provider.
Q3How to fulfil obligations in Q2?
The OEM’s L2 / L3 data must be accessible via DFRS Data Space Broker (currently MDS) to all DFRS members, as if the OEM were a member. The provider acts as a data access interface and may monetise this service — but not by charging extra for feeds containing DFRS data.
Q4Does a non-DFRS OEM (Q2/Q3) get access to DFRS L2 / L3 data?
No. They only receive the processed feed licensed from their provider.
Q5Can an OEM use a contractor as Service Provider / Creator?
Yes, but only for OEM-specific systems serving that OEM. Data processed under this contract must remain separate from the provider’s other activities.
Q6Must the provider disclose the non-DFRS OEM’s name (Q2)?
Yes. It must be included in the OEM’s SD1 submitted to DFRS.
Vision ZeroThe wider goal
This collaborative effort aligns with the broader vision of Vision Zero, aiming to reduce road fatalities close to zero by 2050 through enhanced technology and cooperation across the automotive and infrastructure sectors.
TTi podcast: connected vehicles are now rated safer
TTi editor Tom Stone talks to Joost Vantomme (ERTICO), Richard Schram (Euro NCAP) and Mohanad Ismail (WSP) about how connectivity became part of a European vehicle’s safety rating.