UNECE WP.29 R156
The UN type approval regulation for vehicle software updates: the manufacturer holds a certified Software Update Management System whose processes identify software and RXSWINs, judge every update's effect on type approvals and safety, protect and verify updates and keep auditable records, and each vehicle type verifies update authenticity, keeps RXSWINs readable and protected and handles over-the-air updates safely with the user informed. Rebuilt on the 01 series paragraphs (in force 4 June 2026) from the original text, the 01 series amendment and the WP.29 Interpretation Document.
UNECE WP.29 R156 is a compliance framework from International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation) with 7 domains and 46 controls. The largest domains are Paragraph 7.1.1: SUMS processes verified at initial assessment – UNECE WP.29 R156 (13 controls), Paragraph 7.2: Requirements for the vehicle type – UNECE WP.29 R156 (11 controls), Paragraphs 7.1.3 to 7.1.5: Security, the RXSWIN precondition and over-the-air processes – UNECE WP.29 R156 (6 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (7)
Paragraph 7.1.1: SUMS processes verified at initial assessment – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::7.1.1.1 | 7.1.1.1 Information documented, securely held and available to the authority |
| unece-wp-29-r156::7.1.1.10 | 7.1.1.10 Assess whether an update adds, alters or enables functions or changes legislated parameters |
| unece-wp-29-r156::7.1.1.11 | 7.1.1.11 Assess effects on other systems needed for safe operation and on functionality since registration |
| unece-wp-29-r156::7.1.1.12 | 7.1.1.12 Process to inform the vehicle user about updates |
| unece-wp-29-r156::7.1.1.13 | 7.1.1.13 Make RXSWIN register and target vehicle records available to authorities |
| unece-wp-29-r156::7.1.1.2 | 7.1.1.2 Unique identification of software versions, integrity data and hardware of type approved systems |
| unece-wp-29-r156::7.1.1.3 | 7.1.1.3 Assign a dedicated RXSWIN to every approval whose relevant software is updated |
| unece-wp-29-r156::7.1.1.4 | 7.1.1.4 Access and update RXSWIN information before and after an update |
| unece-wp-29-r156::7.1.1.5 | 7.1.1.5 Verify that software on a component matches its RXSWIN |
| unece-wp-29-r156::7.1.1.6 | 7.1.1.6 Identify interdependencies of the updated system with other systems |
| unece-wp-29-r156::7.1.1.7 | 7.1.1.7 Identify target vehicles for a software update |
| unece-wp-29-r156::7.1.1.8 | 7.1.1.8 Confirm compatibility with the target vehicles' last known configuration before issue |
| unece-wp-29-r156::7.1.1.9 | 7.1.1.9 Assess, identify and record whether an update affects type approved systems |
Paragraph 7.1.2: Records kept for each update – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::7.1.2.1 | 7.1.2.1 Documentation of the update processes and standards used |
| unece-wp-29-r156::7.1.2.2 | 7.1.2.2 Configuration of type approved systems before and after an update |
| unece-wp-29-r156::7.1.2.3 | 7.1.2.3 Auditable register of all software relevant to each RXSWIN |
| unece-wp-29-r156::7.1.2.4 | 7.1.2.4 Target vehicle list and compatibility confirmation |
| unece-wp-29-r156::7.1.2.5 | 7.1.2.5 Documentation for every update: purpose, effects, approval status, conditions, safety, security and V&V |
Paragraph 7.2: Requirements for the vehicle type – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::7.2.1.1 | 7.2.1.1 Protect the authenticity and integrity of software updates on the vehicle |
| unece-wp-29-r156::7.2.1.2.1 | 7.2.1.2.1 Each RXSWIN uniquely identifiable and updated on extension or new approval |
| unece-wp-29-r156::7.2.1.2.2 | 7.2.1.2.2 RXSWIN or software versions readable through a standard interface |
| unece-wp-29-r156::7.2.1.2.3 | 7.2.1.2.3 Protect RXSWINs and software versions on the vehicle against unauthorised modification |
| unece-wp-29-r156::7.2.2.1.1 | 7.2.2.1.1 Restore the previous version or reach a safe state after a failed or interrupted update |
| unece-wp-29-r156::7.2.2.1.2 | 7.2.2.1.2 Execute updates only with enough power to complete or recover |
| unece-wp-29-r156::7.2.2.1.3 | 7.2.2.1.3 Technical means ensure safe execution where an update may affect safety |
| unece-wp-29-r156::7.2.2.2 | 7.2.2.2 Inform the user before execution: purpose, changes, duration, unavailable functions, instructions |
| unece-wp-29-r156::7.2.2.3 | 7.2.2.3 Prevent driving and unsafe functions where execution while driving may be unsafe |
| unece-wp-29-r156::7.2.2.4 | 7.2.2.4 Inform the user after execution of success or failure and of changes |
| unece-wp-29-r156::7.2.2.5 | 7.2.2.5 Vehicle checks preconditions before executing an update |
Paragraphs 3 and 4: Application for approval and marking – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::3.3 | 3.3 Application documents: vehicle type description and the SUMS certificate |
| unece-wp-29-r156::3.4 | 3.4 Sufficient information despite intellectual property or know-how |
| unece-wp-29-r156::3.6 | 3.6 Submit a vehicle representative of the type for testing |
| unece-wp-29-r156::3.7 | 3.7 Documentation package and material open for inspection, kept ten years |
| unece-wp-29-r156::4.1 | 4.1 International approval mark on every conforming vehicle |
Paragraphs 5 and 6: Approval and Certificate of Compliance for SUMS – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::6.3 | 6.3 SUMS certificate application: SUMS documents and signed declaration |
| unece-wp-29-r156::6.4 | 6.4 Declare and demonstrate the necessary SUMS processes |
| unece-wp-29-r156::6.8 | 6.8 Inform the authority of changes affecting the SUMS certificate |
Paragraphs 7.1.3 to 7.1.5: Security, the RXSWIN precondition and over-the-air processes – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::7.1.3.1 | 7.1.3.1 Protect software updates against manipulation before the update process starts |
| unece-wp-29-r156::7.1.3.2 | 7.1.3.2 Protect the update processes and the development of the delivery system |
| unece-wp-29-r156::7.1.3.3 | 7.1.3.3 Appropriate verification and validation of vehicle software |
| unece-wp-29-r156::7.1.4 | 7.1.4 No updates to registered 01 series vehicles unless every assessed approval has an RXSWIN |
| unece-wp-29-r156::7.1.5.1 | 7.1.5.1 Assess that over-the-air updates will not impact safety if conducted during driving |
| unece-wp-29-r156::7.1.5.2 | 7.1.5.2 Updates needing skilled or complex action proceed only with a skilled person present or in control |
Paragraphs 8 to 13: Modification, conformity of production, discontinuation and transitional provisions – UNECE WP.29 R156
| Code | Title |
|---|---|
| unece-wp-29-r156::11.1 | 11.1 Inform the authority when production is definitively discontinued |
| unece-wp-29-r156::8.1 | 8.1 Notify modifications of the vehicle type |
| unece-wp-29-r156::9.1.1 | 9.1.1 Conformity of production: record test results and keep the documents |
What is UNECE WP.29 R156 and who does it apply to?
UNECE WP.29 R156 is a compliance framework from International (Contracting Parties to the UNECE 1958 Agreement that apply the Regulation) with 7 domains and 46 controls. The UN type approval regulation for vehicle software updates: the manufacturer holds a certified Software Update Management System whose processes identify software and RXSWINs, judge every update's effect on type approvals and safety, protect and verify updates and keep auditable records, and each vehicle type verifies update authenticity, keeps RXSWINs readable and protected and handles over-the-air updates safely with the user informed. Rebuilt on the 01 series paragraphs (in force 4 June 2026) from the original text, the 01 series amendment and the WP.29 Interpretation Document. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does UNECE WP.29 R156 actually require?
UNECE WP.29 R156 has 46 controls organised across 7 domains. The largest domains are Paragraph 7.1.1: SUMS processes verified at initial assessment – UNECE WP.29 R156 (13 controls), Paragraph 7.2: Requirements for the vehicle type – UNECE WP.29 R156 (11 controls), Paragraphs 7.1.3 to 7.1.5: Security, the RXSWIN precondition and over-the-air processes – UNECE WP.29 R156 (6 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of UNECE WP.29 R156 do I already cover?
UNECE WP.29 R156 does not currently have cross-framework mappings in our system. Check back as we continuously expand our mapping database.
How do I implement UNECE WP.29 R156?
Start your UNECE WP.29 R156 compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about UNECE WP.29 R156 requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 46 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,120 frameworks.
Get Started Free →Free forever, no credit card required