Software Update Management System (SUMS)

A Software Update Management System is the certified organisational counterpart to the CSMS for software change: the processes through which a vehicle manufacturer plans, assesses, protects, delivers, and records software updates for type-approved vehicles. UNECE R156 defines what a SUMS must demonstrate. Key components include an inventory of initial and updated software versions per vehicle type, tied to RXSWIN identifiers where regulated software is affected; an impact assessment for every update — whether the change touches a type-approved system, affects safe operation, or alters parameters documented in the approval; protection of update packages against manipulation, with integrity and authenticity verified before installation; defined behaviour when an update fails, including rollback or another safe state; user information where an update requires action; and records that let an authority reconstruct what software any given vehicle should be running. The SUMS Certificate of Compliance is issued after assessment by an approval authority or its technical service and is valid for up to three years. The obligation applies to vehicle manufacturers seeking type approval in markets adopting R156, but the evidence reaches down the supply chain: ECU suppliers implement the Secure Flashing, rollback, and version-reporting behaviour the manufacturer's SUMS depends on. In relation to adjacent standards, R156 is the regulation, ISO 24089 is the software-update engineering standard used to implement it, UNECE R155 and the CSMS govern the security-risk side of the same lifecycle, and the update channel itself appears in the TARA as an attack surface. India's AIS 190 derives from R156.