UN R171 Supplement 1 (01 series) · UNECE Regulation No. 171 (ECE R171) — Uniform Provisions Concerning the Approval of Vehicles with regard to Driver Control Assistance Systems.
UN R171 — Supplement 1 to the 01 series of amendments
Base text → Supplement 1
- What changed
- If the manufacturer is to take remedial action addressing DCAS design, the Type Approval Authority must upload the information to DETA. Paragraph 7.2.2.2. now says “without undue delay but no later than 14 days after receipt”.
- New Annex 6 gives guidance to the approval authorities on the use of DETA for the implementation of paragraph 7.2.2.2.
- Under Annex 6, the authority that granted the type approval uploads the information to DETA and enters a notification in the tab “News”. It must complete these actions as soon as possible but at least within 14 days on receiving the information on the remedial action.
- Why
- The proposal was created to implement the amended provisions of paragraph 7.2.2.2. on the use of DETA to exchange information on incidents with DCAS operation.
- The 14-day period is set as a backstop, to make sure that the information is uploaded in DETA in a timely manner by all authorities.
- Annex 6 also makes clear that any non-conformity found still needs to be notified under the 1958 Agreement. The notification in DETA does not replace that.
Q1What changed20 changes
Upload of remedial action information to DETA within 14 days (para. 7.2.2.2.)
Paragraph 7.2.2.2. applies if remedial action addressing DCAS design is to be taken by the manufacturer. The Type Approval Authority must then upload the information received from the manufacturer in English to the secure internet database “DETA”. The text now adds “but no later than 14 days after receipt” after “without undue delay”. The paragraph now also says that Annex 6 contains the guidance for uploading the information to “DETA”.
New Annex 6: guidance for data exchange through DETA (Introduction)
New Annex 6 gives guidance to the approval authorities on the use of DETA for the implementation of paragraph 7.2.2.2. In the general use case it describes, the approval authority that granted the type approval (the “notifying authority”) uploads the required information to DETA. It also notifies this to the other authorities by adding a notification message onto DETA. The uploaded information is only available to the Contracting Parties applying this Regulation, but the notification message will be available to all DETA users. Information obtained through DETA for this information sharing scheme must be protected in a secure manner. It must not be used for purposes other than preventing negative consequences of DCAS operation.
Annex 6: general guidance on the use of DETA for incidents with DCAS
The notifying authority must communicate with the manufacturer to understand fully the nature of the incident, the role of DCAS, its cause and remedial actions. It must put all required information together as one or more pdf files and upload them to the type-approval number concerned. It then enters a notification in the tab “News”, with as a minimum the standard text and the approval number. It must complete these actions as soon as possible but at least within 14 days on receiving the information on the remedial action. This does not absolve it from reporting non-conformities to other Contracting Parties, as outlined in Article 4 and Schedule 6 of the 1958 Agreement. Other approval authorities applying this Regulation that take note of the notification message may submit queries on the incident to the notifying authority by e-mail.
Q2Why it changed
- Proposed by
- Experts from the Task Force on Advanced Driver Assistance System
- Working party
- GRVA, 22nd session (June 2025)
Reasons
The proposal was created to implement the amended provisions of paragraph 7.2.2.2. These provisions involve the use of the secure internet database DETA to exchange information on incidents with DCAS operation between type approval authorities.
Sources (2)
“This proposal was created to implement the amended provisions of UN Regulation No. 171, paragraph 7.2.2.2., which involve the use of the secure internet database "DETA" for the purpose of exchanging the information regarding incidents with DCAS operation”
“between type approval authorities of the Contracting Parties”
The initial proposal was based on the guidelines adopted by WP.29 for the implementation of UN Regulation No. 155 on cybersecurity. The IWG on DETA then modified the proposal at its fifty-second session.
Sources (2)
“The initial proposal was based on the guidelines adopted by WP.29 (document ECE/TRANS/WP.29/2022/61) provided for implementation of UN Regulation No. 155 on cybersecurity.”
“Further on, the proposal was modified by the IWG on DETA at its fifty-second session”
Proposer's reason (informal document GRVA-22-18)
Paragraph 7.2.2.2. sets a 14-day period as a backstop, to make sure that all authorities upload the information in DETA in a timely manner.
Submitted by Task Force on ADAS. Working party adoption: ECE/TRANS/WP.29/GRVA/22, para. 49.
Source
“Paragraph 7.2.2.2.: Sets a specific period [14 days] that need to be included as a backstop to ensure that the information is uploaded in DETA in a timely manner by all authorities.”
Proposer's reason (informal document GRVA-22-18)
In Annex 6, a specific period of 14 days is also set as a backstop. The text also makes clear that any non-conformity found still needs to be notified under the 1958 Agreement. The notification in DETA does not replace that.
Submitted by Task Force on ADAS. Working party adoption: ECE/TRANS/WP.29/GRVA/22, para. 49.
Sources (2)
“Sets a specific period [14 days] that need to be included as a backstop to ensure that the information is uploaded in DETA in a timely manner by all authorities and”
“clarifies that any non-conformity found still needs to be notified as per the’58 Agreement and the notification in DETA does not substitute that”
Document trail
- 2025-04ProposalECE/TRANS/WP.29/GRVA/2025/30Proposal by the experts from the Task Force on Advanced Driver Assistance System
- —Amended in sessionGRVA-22-18Proposal for amendments transmitted by the Task Force on ADAS
- —Working party adoptsECE/TRANS/WP.29/GRVA/22Session report, para. 49
- 2025-08Sent to WP.29ECE/TRANS/WP.29/2025/144Text that GRVA sent to WP.29 and AC.1
- 2025-11WP.29 adoptsECE/TRANS/WP.29/1188Adopted at the 197th session (session report, para. 110)
- 2026-06-04In forceC.N.239.2026.TREATIES-XI.B.16.171UN depositary notification
Q3Who is affected
Vehicle manufacturer
- Be ready for the notifying authority to communicate with you about the incident and the remedial actions (Annex 6).
Component supplier
- No direct action for this role.
Technical service / Approval authority
- As approval authority, upload remedial action information to DETA without undue delay but no later than 14 days after receipt.
- As notifying authority, upload the information as pdf files and enter a notification in the DETA tab “News”.
- Upload and notify as soon as possible but at least within 14 days on receiving the remedial action information.
- As approval authority, protect information obtained through DETA for this Regulation's information sharing scheme in a secure manner.
- As approval authority, check the “News” section of DETA on a daily basis, as the guidance in Annex 6 recommends.
See every change side by side
RegVault customers compare every version of UN regulations, read the consolidated text and download the PDF.
ⓘ This report gives advice only. It is not legal or type-approval advice.