International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation)

UNECE WP.29 R156

81 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

81 controls 0 frameworks share controls with it International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
R156-MARKET-SURVCooperation with market surveillance authorities0
R156-OTA-WIRELESSAdditional requirements for OTA updates0
R156-PRIVACYData minimisation in update telemetry0
R156-RECORDSRecords of updates per vehicle0
R156-RXSWIN-MGMTRXSWIN management and traceability0
R156-SUMS-GOVSoftware Update Management System governance0
R156-SUPPLIERSupplier-delivered software management0
R156-SW-COMPATPre-update compatibility and dependency check0
R156-SW-EXECUTIONSafe and reliable update execution0
R156-SW-IMPACTAssessment of impact on type approval and safety0
R156-SW-INTEGRITYIntegrity and authenticity of software updates0
R156-SW-INVENTORYSoftware identification and documentation0
R156-SW-USERINFOInformation to the user before and after the update0
UNECER156-1Software Updates Management System (SUMS)0
UNECER156-2Type Approval and RxSWIN0
UNECER156-3Update Process and Vehicle Owner Information0
UNECER156-4Cyber Linkage to R155 and Lifecycle0
1010 and 12 Penalties for non-conformity and authority contacts0
11.111.1 Inform the authority when production is definitively discontinued0
1313 Transitional provisions of the 01 series0
33 Application for approval0
3.33.3 Application documents: vehicle type description and the SUMS certificate0
3.43.4 Sufficient information despite intellectual property or know-how0
3.63.6 Submit a vehicle representative of the type for testing0
3.73.7 Documentation package and material open for inspection, kept ten years0
4.14.1 International approval mark on every conforming vehicle0
55 Approval: authority verification and notification0
66 Certificate of Compliance for Software Update Management System0
6.36.3 SUMS certificate application: SUMS documents and signed declaration0
6.46.4 Declare and demonstrate the necessary SUMS processes0
6.56.1, 6.5 to 6.7, 6.9 and 6.10 Authority grant, validity, withdrawal and renewal of the SUMS certificate0
6.86.8 Inform the authority of changes affecting the SUMS certificate0
77 General specifications0
7.1.17.1.1 Processes to be verified at initial assessment0
7.1.1.17.1.1.1 Information documented, securely held and available to the authority0
7.1.1.107.1.1.10 Assess whether an update adds, alters or enables functions or changes legislated parameters0
7.1.1.117.1.1.11 Assess effects on other systems needed for safe operation and on functionality since registration0
7.1.1.127.1.1.12 Process to inform the vehicle user about updates0
7.1.1.137.1.1.13 Make RXSWIN register and target vehicle records available to authorities0
7.1.1.27.1.1.2 Unique identification of software versions, integrity data and hardware of type approved systems0
7.1.1.37.1.1.3 Assign a dedicated RXSWIN to every approval whose relevant software is updated0
7.1.1.47.1.1.4 Access and update RXSWIN information before and after an update0
7.1.1.57.1.1.5 Verify that software on a component matches its RXSWIN0
7.1.1.67.1.1.6 Identify interdependencies of the updated system with other systems0
7.1.1.77.1.1.7 Identify target vehicles for a software update0
7.1.1.87.1.1.8 Confirm compatibility with the target vehicles' last known configuration before issue0
7.1.1.97.1.1.9 Assess, identify and record whether an update affects type approved systems0
7.1.27.1.2 Records kept for each update applied to a vehicle type0
7.1.2.17.1.2.1 Documentation of the update processes and standards used0
7.1.2.27.1.2.2 Configuration of type approved systems before and after an update0
7.1.2.37.1.2.3 Auditable register of all software relevant to each RXSWIN0
7.1.2.47.1.2.4 Target vehicle list and compatibility confirmation0
7.1.2.57.1.2.5 Documentation for every update: purpose, effects, approval status, conditions, safety, security and V&V0
7.1.37.1.3 Security: what the manufacturer demonstrates0
7.1.3.17.1.3.1 Protect software updates against manipulation before the update process starts0
7.1.3.27.1.3.2 Protect the update processes and the development of the delivery system0
7.1.3.37.1.3.3 Appropriate verification and validation of vehicle software0
7.1.47.1.4 No updates to registered 01 series vehicles unless every assessed approval has an RXSWIN0
7.1.57.1.5 Additional requirements for software updates over the air0
7.1.5.17.1.5.1 Assess that over-the-air updates will not impact safety if conducted during driving0
7.1.5.27.1.5.2 Updates needing skilled or complex action proceed only with a skilled person present or in control0
7.27.2 Requirements for the vehicle type0
7.2.1.17.2.1.1 Protect the authenticity and integrity of software updates on the vehicle0
7.2.1.27.2.1.2 Requirements for RXSWIN0
7.2.1.2.17.2.1.2.1 Each RXSWIN uniquely identifiable and updated on extension or new approval0
7.2.1.2.27.2.1.2.2 RXSWIN or software versions readable through a standard interface0
7.2.1.2.37.2.1.2.3 Protect RXSWINs and software versions on the vehicle against unauthorised modification0
7.2.27.2.2 Additional requirements for over-the-air updates0
7.2.2.1.17.2.2.1.1 Restore the previous version or reach a safe state after a failed or interrupted update0
7.2.2.1.27.2.2.1.2 Execute updates only with enough power to complete or recover0
7.2.2.1.37.2.2.1.3 Technical means ensure safe execution where an update may affect safety0
7.2.2.27.2.2.2 Inform the user before execution: purpose, changes, duration, unavailable functions, instructions0
7.2.2.37.2.2.3 Prevent driving and unsafe functions where execution while driving may be unsafe0
7.2.2.47.2.2.4 Inform the user after execution of success or failure and of changes0
7.2.2.57.2.2.5 Vehicle checks preconditions before executing an update0
8.18.1 Notify modifications of the vehicle type0
9.1.19.1.1 Conformity of production: record test results and keep the documents0
ANNEXESAnnexes 1 to 4: information document, communication, approval mark, SUMS certificate model0
INTERPRETATIONThe Interpretation Document for UN Regulation No. 1560
STANDARDUN Regulation No. 156: the Regulation, its scope and definitions0
STATUSStatus: the 01 series in force from 4 June 2026 beside the original version0

Tell me when UNECE WP.29 R156 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for UNECE WP.29 R156, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition