Why it exists
Delivering a software file is only part of updating a vehicle. The team must know which vehicles can accept it, which other software it depends on and what happens if installation stops halfway through. It also needs evidence of the final configuration.
Consider a central computer that needs a matching gateway release. Both files may pass their individual tests, yet installing only one can break communication. Preventing that failure requires coordination between release engineering, backend services and vehicle software.
ISO 24089 gives these teams a shared engineering framework. It helps turn an update from an isolated flashing task into a managed activity with responsibilities, checks and recorded outcomes.
What it is
ISO 24089:2023, Road vehicles — Software update engineering, specifies organizational and project requirements and recommendations. Its scope includes infrastructure, vehicles, vehicle systems, electronic control units (ECUs), and update package assembly and deployment after initial development. It covers workshop updates as well as over-the-air (OTA) delivery and does not prescribe a particular technology. ISO’s public scope and introduction describe these boundaries. Source: ISO 24089 public overview.
The relationship to regulation and cybersecurity is important:
| Document | Role in update engineering |
|---|---|
| ISO 24089 | Structures the engineering activities used to prepare and execute updates. |
| UN Regulation No. 156 | Sets applicable approval requirements for updates and the software update management system (SUMS). |
| ISO/SAE 21434 | Structures cybersecurity risk management across the vehicle lifecycle. |
ISO 24089 can support implementing a SUMS, but it is not UN R156 itself. Following it does not automatically establish regulatory compliance or grant approval. The manufacturer must address the applicable regulation and provide the required evidence. UNECE publishes R156 as a vehicle approval regulation covering software updates and their management system. Source: UN Regulation No. 156.
ISO/SAE 21434 complements the update framework. Its cybersecurity lifecycle work helps determine which threats and protections update engineering must address; ISO 24089 does not replace that assessment. Source: SAE’s ISO/SAE 21434 scope.
How it works
The standard connects organizational processes, project planning, supporting infrastructure and vehicle capabilities with package preparation and campaign execution. A package contains software and associated metadata. A project can encompass multiple campaigns; a campaign applies updates to a defined target population.
For practical implementation, map the standard’s requirements to existing processes. The examples below illustrate useful engineering decisions and work products; they are not a prescribed set of document titles.
Organizational level. Establish who owns update engineering, how suppliers participate and how records are controlled. Connect release approval, configuration management, safety and cybersecurity reviews, and incident handling.
Useful work products include a process map, responsibility assignments, supplier interface agreements and rules for retaining evidence. A small team can combine these records if ownership and traceability remain clear.
Project level. Define the update scope, affected configurations, dependencies, responsibilities and acceptance criteria. Decide which existing capabilities are sufficient and which need changes.
For the central-computer example, the project plan could identify the required gateway baseline, installation order and acceptable recovery states. Link those decisions to requirements and verification results.
Infrastructure. Treat backend services, release tools and workshop tooling as part of the update system. Define how they select eligible vehicles, control access, distribute approved packages and collect results.
For example, test whether an outdated vehicle inventory can cause an incorrect eligibility decision. Keep the approved release, targeting rules and campaign records traceable to each other.
Vehicle and ECU capabilities. Allocate responsibilities between the vehicle coordinator and target controllers. Define checks for compatibility, power, storage, operating state and dependencies. Specify how receipt, installation and activation are coordinated and how failures are reported.
Test the boundaries between components. A controller reporting successful programming does not by itself demonstrate that the vehicle activated a compatible configuration.
Update package. Define the software and metadata needed for the intended targets. In practice, metadata may describe compatible hardware, prerequisites, dependencies and installation instructions. Define integrity, authenticity and authorization checks from the security requirements.
Keep package identity stable so that approvals, verification results and deployment records all refer to the same artifact.
Update campaign. Prepare the target selection, execution conditions, user information and response to failures. After deployment, reconcile reported outcomes with the intended final configuration.
For example, a campaign plan can define an initial deployment group, conditions for expanding delivery and criteria for pausing it. These are implementation choices to justify for the project.
When to use it — and when not
Use ISO 24089 when establishing an update organization, introducing an update platform or coordinating suppliers across a vehicle program. Apply it early enough for findings to influence vehicle architecture and controller capabilities.
It is also useful when reviewing an existing update operation. Missing ownership, weak configuration records or unclear recovery behavior can become explicit improvement actions.
Do not use it as a flashing protocol specification, package-format definition or cloud architecture recipe. It also does not replace development and validation of the vehicle function being updated.
For a laboratory demonstration, adapt the engineering effort to its purpose. Keep any limitations visible before reusing the demonstration for production.
Best practices
- Map requirements to working processes. Record the applicable requirement, responsible owner, implementation location and supporting evidence. Review gaps and justify any tailoring.
- Reuse controlled work products. Connect existing release records, test reports and configuration data instead of maintaining a separate, inconsistent compliance archive.
- Agree supplier boundaries early. Specify who provides compatibility information, verifies installation behavior, approves packages and investigates failures.
- Exercise interrupted updates. Test power loss, communication loss, rejected packages and incomplete activation against defined recovery behavior.
- Connect security decisions to implementation. Carry threat analysis and risk assessment results into package protection, access control and verification.
- Define completion precisely. Distinguish delivery, installation, activation and confirmation of the resulting vehicle configuration.
Common pitfalls
- Treating a process checklist as proof of a working system. Review evidence from realistic vehicle and infrastructure behavior.
- Assuming OTA is the whole scope. Workshop tools and service procedures also need controlled update behavior.
- Confusing project and campaign. Reusing a platform does not remove the need to assess each campaign’s targets and prerequisites.
- Making rollback the default recovery answer. Returning to older software may conflict with data compatibility or security restrictions. Define and verify the permitted recovery path.
- Using download success as the final result. A received package can still fail installation or activation.
- Equating ISO alignment with regulatory approval. Maintain an explicit mapping to applicable R156 requirements and approval evidence.