What it is
ISO 24089 is an engineering standard for managing software updates in road vehicles. It connects organisational processes with project activities so that responsibilities remain clear across the update life cycle. The full standard is paid; ISO provides a public description and preview. ISO catalogue and scope.
For a beginner, the key idea is that delivering new software requires more than transferring a file. Teams need a controlled way to decide what can be updated, prepare the release, establish suitable execution conditions and determine what happened afterwards.
Who it applies to
The standard addresses organisations involved in vehicle software updates, including vehicle manufacturers, suppliers and their partners. Its scope reaches vehicles, vehicle systems, electronic control units (ECUs), supporting infrastructure and update packages.
It applies to updateable road vehicles and is relevant to workshop updates as well as over-the-air delivery. Developing the vehicle function itself is outside its scope, except where that work concerns update engineering. It does not prescribe a particular technical solution. ISO scope and preview.
What it covers
ISO 24089 provides requirements and recommendations at organisational and project levels. It gives teams a shared framework for coordinating update engineering across company boundaries and technical systems.
A useful way to organise implementation discussions is:
| Working level | Practical question |
|---|---|
| Organisation | Who owns release decisions and supplier coordination? |
| Project | What evidence makes this update ready? |
| Vehicle and infrastructure | Can the intended targets receive and execute it? |
| Update package | Is the software appropriate for the target configuration? |
These questions translate the framework into engineering conversations; the table is not a reproduction of the standard’s clauses.
How it fits with other documents
UN R156 addresses regulatory software update management and vehicle approval where it applies. ISO 24089 provides an engineering framework that can support that work. Applying the standard does not itself grant regulatory approval or replace the applicable approval requirements.
Safety and cybersecurity activities also need to feed into update decisions. Teams should coordinate their ISO 26262 and ISO/SAE 21434 work with update engineering so that a release’s functional changes and installation behaviour receive appropriate assessment.
Implementation choices such as A/B storage, delta packages and rollback sit beneath this process framework. Their suitability depends on the system: choosing one does not establish conformity with ISO 24089.
In practice
Consider a campaign that updates a central computer and a dependent ECU. The team should establish which existing configurations are eligible, whether installation order matters and what conditions must hold before activation.
Useful project artefacts might include a responsibility map, compatibility records, package verification results, release decisions and campaign outcome records. Their exact form should follow the organisation’s processes and applicable requirements.
Before release, exercise interruption and failure scenarios: lost connectivity, insufficient power, rejected packages and incomplete installation. Decide how the vehicle reports its resulting configuration and how service teams handle an unsuccessful attempt. Recovery may involve retrying, restoring software or workshop intervention; automatic rollback should be an explicit engineering decision.