Why it exists
A software update can change how a vehicle brakes, manages its battery or presents information to the driver. Successful installation alone does not show that the resulting vehicle still meets its approval requirements.
Manufacturers therefore need to answer practical questions before releasing software: Which vehicles can receive it? Which other software versions must be present? Does it change an approved function? Can the manufacturer later prove what was installed?
UN Regulation No. 156, usually called UN R156, connects these questions to organisational controls and vehicle type approval. It covers software updates beyond over-the-air delivery, including updates installed through workshop equipment.
What it is
The Software Update Management System (SUMS) is the manufacturer’s organised set of responsibilities, processes and procedures for managing software updates. It includes engineering, release decisions, supplier information, records and user communication. An update server is only part of its implementation.
The manufacturer must demonstrate these processes to the approval authority or its technical service to obtain a Certificate of Compliance for SUMS. A technical service performs assessments or tests on behalf of an approval authority. The certificate concerns the management system; the vehicle type must also satisfy R156’s vehicle requirements.
RX Software Identification Number (RXSWIN) is a manufacturer-defined identifier representing software relevant to approval under a particular UN Regulation. The X stands for that regulation’s number. It connects the software configuration to the characteristics covered by that approval.
| Item | What it establishes |
|---|---|
| SUMS certificate | The manufacturer has the required update management processes. |
| Vehicle type approval under R156 | The vehicle type meets the applicable update requirements. |
| RXSWIN | The identity of software relevant to a particular regulatory approval. |
| Software version | The identity of a particular software release or component. |
An RXSWIN can represent a combination of software versions across electronic control units. It is not a vehicle identification number, a package checksum or necessarily a single identifier covering all software in the vehicle.
How it works
The SUMS connects each release decision to a documented configuration and its supporting evidence.
- Identify the change and its targets. Record the update’s purpose, affected functions, software and hardware identifiers, and intended vehicles. Selection must account for the vehicles’ last known configurations.
- Check compatibility and dependencies. Establish which software, hardware, configuration parameters and connected systems the update requires. Reject unsupported combinations before making the update available.
- Assess approval and safety effects. Determine whether the update affects type-approved systems, changes approval-relevant parameters, adds functions or affects safe operation. Record the reasoning, including a justified conclusion that approval is unaffected.
- Control release and execution. Protect software authenticity and integrity, release permissions and update records. Provide the necessary user information and define installation conditions, recovery arrangements and any skilled intervention.
- Retain traceability. Preserve the configurations before and after the update, validation results, release decisions and installation outcomes.
For example, a central computer update may depend on a particular gateway version and sensor calibration. Selecting vehicles by model name alone could include incompatible vehicles. The release record should show how these dependencies were checked and which vehicles were excluded.
RXSWIN changes follow approval impact. Under R156, when a manufacturer modifies approval-relevant software, the RXSWIN must change if the modification leads to an approval extension or a new approval. A new build number alone does not establish that trigger. Engineering and homologation staff—the people responsible for regulatory approval—must agree and record the assessment.
Where RXSWIN is held on the vehicle, it must be readable through a standardised electronic communication interface, at least through the on-board diagnostics (OBD) port. Where it is not held on the vehicle, R156 provides for declared software versions linked to the relevant approvals. Those versions must be readable, and the declaration must be maintained. The applicable amendment series and related system regulation determine the detailed obligations.
The manufacturer must protect the identifiers or declared versions against unauthorised modification. An auditable register connects each RXSWIN to the relevant software versions and integrity validation data before and after updates.
The vehicle approval assessment also examines update protection and, for over-the-air (OTA) updates, capabilities such as adequate power, safe execution, recovery or transition to a safe state, and user information. A SUMS certificate does not replace these demonstrations.
When to use it — and when not
Use the SUMS whenever planning or releasing updates within the applicable R156 approval framework. Bring it into platform development early: configuration reporting, diagnostic readout and recovery support need vehicle engineering work.
Check the applicable market rules, vehicle category, amendment series and approval context with homologation staff. R156 is not a universal rule for every software product or every jurisdiction.
Use RXSWIN to maintain the connection between approval-relevant software and its regulatory approval. Keep ordinary component versions, package identifiers and configuration records alongside it. They provide the detail needed for debugging, service and compatibility checks.
UN R155’s Cyber Security Management System (CSMS) addresses cybersecurity risk management across the vehicle lifecycle. SUMS governs the update process. Their work intersects when a vulnerability triggers an update or an attacker could compromise software delivery. Share threat assessments, incident handling and supplier evidence, while maintaining the distinct approval evidence required by each regulation.
Best practices
- Make an update reconstructable. Start with a released package and demonstrate its target vehicles, compatible configurations, approval assessment, authorisation and resulting installation records.
- Keep a controlled software register. Link RXSWIN entries to component versions, hardware identifiers, configuration parameters and integrity validation data. Preserve historical mappings.
- Test diagnostic readout on representative vehicles. Compare actual responses with the register, including after interrupted installation, recovery and control-unit replacement.
- Assign decision owners. Name who approves compatibility, security, safety and homologation conclusions. Supplier evidence needs an identified manufacturer reviewer.
- Retain practical audit evidence. Keep controlled procedures, responsibility assignments, supplier deliverables, dependency checks, test reports, signed release decisions and user messages. Include rejected configurations and failed-update handling.
- Check the whole information path. Confirm that vehicle configuration reports, backend campaign records and workshop observations describe the same installed state.
A useful audit exercise is to select a completed campaign and follow its evidence from change request to vehicle readout. Missing links reveal weaknesses that a process manual alone may hide.
Common pitfalls
- Treating SUMS certification as approval of every update package.
- Assuming only OTA updates need controlled assessment and records.
- Equating an RXSWIN with every software build, or leaving it unchanged when an approval extension requires a change.
- Checking compatibility against the intended platform configuration instead of the target vehicles’ last known configurations.
- Recording that an update succeeded without retaining the resulting software configuration.
- Protecting package signatures while leaving release permissions or diagnostic identifiers open to unauthorised changes.
- Describing a change as a “security patch” or “bug fix” without assessing its effect on approved functions.
- Preparing audit documents after release, when the evidence behind the original decision is already missing.