ISO/PAS 25090
(Main)Road vehicles — Software update engineering — Vehicle configuration information
- Abstract
This document will provide guidance on how to determine the relevant vehicle configuration information for software update engineering, according to ISO 24089:2023. This guidance will contain definitions of elements of vehicle configuration information, relationships between such elements, and examples of usage. ■ Out of Scope: • Formats for elements of vehicle configuration information. • How such information can be collected, stored, and exchanged.
- Status
- Not Published
- Technical Committee
- ISO/TC 22/SC 32 - Electrical and electronic components and general system aspects
- Drafting Committee
- ISO/TC 22/SC 32/WG 12 - Software update
- Current Stage
- 6000 - International Standard under publication
- Start Date
- 06-Aug-2026
- Completion Date
- 10-Oct-2026
Buy Documents
ISO/DPAS 25090 - Road vehicles — Software update engineering — Vehicle configuration information
REDLINE ISO/DPAS 25090 - Road vehicles — Software update engineering — Vehicle configuration information
ISO/PAS 25090 is an ISO document for road vehicles that gives guidance on vehicle configuration information for software update engineering. It defines the main elements of vehicle configuration information, shows how those elements relate to each other, and explains how to select the relevant vehicle configuration information for a software update activity. The document is aimed at organizations working under ISO 24089, including the teams that plan, package, campaign, and audit vehicle software updates.
What does ISO/PAS 25090 specify?
ISO/PAS 25090 specifies guidance for determining the relevant vehicle configuration information for software update engineering according to ISO 24089. It also defines the elements of vehicle configuration information, their relationships, and examples of use.
The scope is narrow and practical: the document helps users decide what configuration data matters for a given software update task. It does not prescribe data formats or methods for collecting, storing, or exchanging that information.
| Clause / annex | What it covers |
|---|---|
| 4 | Organizational responsibilities and process requirements |
| 5 | Elements of VCI and how they are managed and assigned |
| 6 | Relationships between VCI elements and an example information model |
| 7 | How to select relevant VCI for software update work |
| Annex A | Informative examples for selecting relevant VCI at different levels |
What are the key requirements of ISO/PAS 25090?
ISO/PAS 25090 focuses on traceable identifier management, relationship modeling, and choosing the right configuration data for each software update step. In practice, that means the organization needs controlled identifiers and documented rules so it can determine targets, dependencies, compatibility, and affected vehicles consistently.
Organizational responsibilities
Clause 4 requires the organization to establish, implement, and maintain software update engineering activities in accordance with ISO 24089. It also requires processes that are needed to meet this document’s requirements and recommendations, and it requires audits to include them.
For a reader, this means vehicle software update work cannot be ad hoc. The organization must be able to show that its process covers the configuration information used in updates and that internal audits check it.
Managing elements of VCI
Clause 5 requires processes for managing the elements of VCI, including how they are named, what data they identify, and how changes are handled. It also requires processes for assigning vehicle system identifiers, hardware identifiers, software identifiers, and supplemental data identifiers.
Clause 5 also says the organization may reuse VCI elements assigned by suppliers. That matters in supply chains, because update engineering often depends on identifiers created outside the organization but still needs a consistent internal view.
Assigning identifiers
Clause 5 requires a vehicle identifier for each vehicle, and that identifier shall be immutable once assigned. It also allows vehicle group identifiers for groups of vehicles, which can be used to describe shared characteristics such as model or trim package.
The same clause requires an ECU identifier for each ECU in a vehicle, including virtual ECUs, and says it shall be immutable once assigned. It also requires ECU version identifiers, hardware identifiers and version identifiers, software identifiers and version identifiers, and vehicle system identifiers and version identifiers as applicable.
In practice, this gives the organization a stable way to tell which vehicle, ECU, hardware, software, or system version is involved in an update. That stability matters when you need to determine whether a package applies to a vehicle and whether a change affects compatibility.
Supplemental data
Clause 5 requires supplemental data identifiers for data the organization has identified as supplemental data. The document lists examples such as metadata in a software update package, conditions or dependencies, serial numbers, configuration parameters, and calibration data.
For update work, this means not only major identifiers but also supporting data must be controlled. That helps when the update decision depends on a parameter, a dependency rule, or another non-software item.
Relationships between VCI elements
Clause 6 gives an example information model and recommends identifying relationships between VCI elements. The clause says these relationships can be used to identify dependencies and compatibility, and to communicate those relationships to relevant parties.
In practice, this is what turns a list of identifiers into an engineering model. The relationships show what depends on what, what must move together, and what needs to be checked before an update is released.
Selecting relevant VCI
Clause 7 requires the organization responsible for a software update project to select the relevant VCI. It also requires identification of changes to immutable identifiers during project activities and identification of the relevant VCI before campaign execution.
At software update package level, the organization shall determine the relevant VCI for targets, dependencies, and compatibility with existing software and hardware. At campaign level, it shall identify the relevant VCI for resolving targets into recipients, determining dependency implications, confirming compatibility, and documenting the VCI changed by the campaign.
That is the practical core of the document: the organization must decide which configuration data matters at each stage, and it must use that data to avoid applying the wrong update or missing a necessary companion change.
What terms does ISO/PAS 25090 define?
ISO/PAS 25090 defines a small set of key terms for software update engineering. These definitions anchor the rest of the document.
- vehicle configuration information (VCI) - a comprehensive accounting of hardware versions, software versions, and configuration parameters in a vehicle.
- relevant VCI - the subset of VCI needed to meet ISO 24089 and this document for a specific software update campaign.
- vehicle identifier - the unique designation for an individual vehicle.
- vehicle group identifier - the unique designation for a group of vehicles with shared characteristics.
- ECU identifier - the unique designation for an electronic control unit, including a virtual ECU.
- supplemental data identifier - the unique designation for data used to support software update engineering that is not covered by other VCI elements.
Who uses ISO/PAS 25090?
ISO/PAS 25090 is used by organizations that perform software update engineering for road vehicles. That includes vehicle manufacturers, system integrators, suppliers, and teams responsible for update planning, configuration management, release management, and campaign execution.
It is also relevant for auditors and quality managers who need to check that software update activities include the right configuration information. In practice, the document supports tasks such as assigning identifiers, tracing dependencies, confirming compatibility, resolving targets into recipients, and documenting what changed in a campaign.
Which standards are used with ISO/PAS 25090?
ISO/PAS 25090 is built on ISO 24089, which is the normative reference and the software update engineering framework it extends. The document repeatedly uses ISO 24089 clauses when explaining responsibilities, campaign planning, dependency checking, and compatibility checking.
Other standards are cited in examples and notes:
- ISO 3779 - used for the VIN example under vehicle identifier assignment.
- ISO/SAE 21434 - cited in an example of a supplier-built component that has a supplier-assigned ECU identifier.
- ISO 14229-1 - cited in examples linked to ECU and vehicle system identification.
What does the ISO/PAS 25090 document contain?
ISO/PAS 25090 contains a short clause structure plus one informative annex. Clause 6 includes an example information model and a relationship model for VCI, with figures that show how vehicle groups, vehicle identifiers, vehicle systems, ECUs, hardware, and software relate to each other.
Annex A gives worked examples for a vehicle with a Steering system and an Automated Lane Keeping System (ALKS). It shows how identifiers are assigned, how dependencies and compatibility are described, and how relevant VCI is selected at software update project, package, and campaign levels.
The annex also illustrates what happens when an update changes functionality, including how affected elements of VCI are identified. For readers, that makes the document useful as a practical guide for design reviews, update planning, and campaign preparation rather than only as a terminology list.
Buy Documents
ISO/DPAS 25090 - Road vehicles — Software update engineering — Vehicle configuration information
REDLINE ISO/DPAS 25090 - Road vehicles — Software update engineering — Vehicle configuration information
Get Certified
Connect with accredited certification bodies for this standard
TÜV Rheinland
TÜV Rheinland is a leading international provider of technical services.
TÜV SÜD
TÜV SÜD is a trusted partner of choice for safety, security and sustainability solutions.
DEKRA Certification Inc.
DEKRA US certification services.
Sponsored listings
Frequently Asked Questions
ISO/PAS 25090 is a draft published by the International Organization for Standardization (ISO). Its full title is "Road vehicles — Software update engineering — Vehicle configuration information". This standard covers: This document will provide guidance on how to determine the relevant vehicle configuration information for software update engineering, according to ISO 24089:2023. This guidance will contain definitions of elements of vehicle configuration information, relationships between such elements, and examples of usage. ■ Out of Scope: • Formats for elements of vehicle configuration information. • How such information can be collected, stored, and exchanged.
This document will provide guidance on how to determine the relevant vehicle configuration information for software update engineering, according to ISO 24089:2023. This guidance will contain definitions of elements of vehicle configuration information, relationships between such elements, and examples of usage. ■ Out of Scope: • Formats for elements of vehicle configuration information. • How such information can be collected, stored, and exchanged.
ISO/PAS 25090 is classified under the following ICS (International Classification for Standards) categories: 43.040.15 - Car informatics. On board computer systems. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO/PAS 25090 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
FINAL DRAFT
Publicly
Available
Specification
ISO/DPAS 25090
ISO/TC 22/SC 32
Road vehicles — Software
Secretariat: JISC
update engineering — Vehicle
Voting begins on:
configuration information
2026-06-10
Véhicules routiers — Ingénierie de mise à jour du logiciel —
Voting terminates on:
Informations sur la configuration des véhicules
2026-08-05
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/DPAS 25090:2026(en) © ISO 2026
FINAL DRAFT
ISO/DPAS 25090:2026(en)
Publicly
Available
Specification
ISO/DPAS 25090
ISO/TC 22/SC 32
Road vehicles — Software
Secretariat: JISC
update engineering — Vehicle
Voting begins on:
configuration information
Véhicules routiers — Ingénierie de mise à jour du logiciel —
Voting terminates on:
Informations sur la configuration des véhicules
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/DPAS 25090:2026(en) © ISO 2026
ii
ISO/DPAS 25090:2026(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 General terminology .1
3.2 Terms related to vehicle configuration information .2
3.3 Abbreviated terms .3
4 Organizational level responsibilities. 3
4.1 General .3
4.2 Requirements and recommendations .3
4.2.1 Software update engineering responsibilities .3
4.2.2 Organizational processes .3
5 Elements of VCI . 3
5.1 General .3
5.2 Requirements and recommendations .3
5.2.1 Element management . .3
5.2.2 Element assignments .4
6 Relationships between elements of VCI. 6
6.1 General .6
6.2 Information model .6
6.3 Recommendations .7
6.3.1 Identification of relationships between elements of VCI .7
6.3.2 Communication of relationships between elements of VCI .7
7 Selection of relevant VCI . 7
7.1 General .7
7.2 Requirements and recommendations . .7
7.2.1 Software update project level . .7
7.2.2 Software update package level .8
7.2.3 Software update campaign level .8
Annex A (informative) Examples of selection of relevant VCI . 9
Bibliography .13
iii
ISO/DPAS 25090:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 32,
Electrical and electronic components and general system aspects.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
ISO/DPAS 25090:2026(en)
Introduction
ISO 24089 requires the use of vehicle configuration information when performing software update
engineering activities. Vehicle configuration information is essential for software update engineering.
ISO 24089 does not define elements of vehicle configuration information or describe any relationships
between such elements. ISO 24089 does not mention how to determine relevant vehicle configuration
information for a given software update engineering activity.
This document extends ISO 24089 by providing:
— definitions of elements of vehicle configuration information;
— relationships between elements;
— selection of relevant vehicle configuration information;
— examples of usage of elements of vehicle configuration information.
This document will also facilitate communications about software update engineering activities that involve
vehicle configuration information throughout the supply chain.
v
FINAL DRAFT Publicly Available Specification ISO/DPAS 25090:2026(en)
Road vehicles — Software update engineering — Vehicle
configuration information
1 Scope
This document provides guidance on how to determine the relevant vehicle configuration information for
software update engineering according to ISO 24089. This document contains definitions of elements of
vehicle configuration information, relationships between such elements and examples of usage.
This document does not prescribe formats for elements of vehicle configuration information or how such
information can be collected, stored and exchanged.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 24089, Road vehicles — Software update engineering
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 24089 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 General terminology
3.1.1
hardware
material physical part of a vehicle system
[SOURCE: NIST Special Publication 800-53 rev 5, modified — Term "vehicle" has been added and term
"component" has been deleted.]
3.1.2
relevant VCI
relevant vehicle configuration information
subset of vehicle configuration information (3.1.3) necessary to conform to ISO 24089 and this document
during a specific software update campaign
3.1.3
vehicle configuration information
VCI
comprehensive accounting of hardware versions, software versions and configuration parameters in a
vehicle
[SOURCE: ISO 24089:2023, 3.1.24, modified — The preferred term "VCI" has been added.]
ISO/DPAS 25090:2026(en)
3.2 Terms related to vehicle configuration information
3.2.1
ECU identifier
electronic control unit identifier
unique designation for an electronic control unit
Note 1 to entry: An ECU can be virtual.
Note 2 to entry: See ISO 24089:2023, 3.1.7 for a definition of "ECU".
3.2.2
ECU version identifier
electronic control unit version identifier
unique designation for a version of an electronic control unit
3.2.3
hardware identifier
unique designation for hardware (3.1.1)
3.2.4
hardware version identifier
unique designation for a version of hardware (3.1.1)
3.2.5
software identifier
unique designation for software
3.2.6
software version identifier
unique designation for a version of software
3.2.7
supplemental data identifier
unique designation assigned to any piece of data that is used to support or that is necessary for software
update engineering and is not covered by other defined vehicle configuration information elements
3.28
vehicle group identifier
unique designation that represents characteristics about a set of vehicles
3.2.9
vehicle identifier
unique designation for an individual instance of a vehicle
3.2.10
vehicle system identifier
unique designation for a vehicle system
Note 1 to entry: See ISO 24089:2023, 3.1.25 for a definition of "vehicle system".
3.2.11
vehicle system version identifier
unique designation for a version of a vehicle system
Note 1 to entry: See ISO 24089:2023, 3.1.25 for a definition of "vehicle system".
ISO/DPAS 25090:2026(en)
3.3 Abbreviated terms
App application
ECU electronic control unit
MCU microcontroller unit
SoC system on a chip
SUV sport utility vehicle
VCI vehicle configuration information
VDS vehicle descriptor section
VIN vehicle identification number
4 Organizational level responsibilities
4.1 General
This clause details requirements and recommendations for organizational responsibilities and processes
for achieving the requirements and recommendations of this document while engaging in software update
engineering.
4.2 Requirements and recommendations
4.2.1 Software update engineering responsibilities
4.2.1.1 The organization shall establish, implement, and maintain software update engineering activities in
accordance with ISO 24089.
4.2.2 Organizational processes
4.2.2.1 The organization shall establish, implement and maintain processes necessary to conform to the
requirements of this document.
4.2.2.2 An audit of organizational processes for soft
...
Style Definition
...
Style Definition
...
Style Definition
...
ISO /DPAS 25090:####(X)
Style Definition
...
ISO /TC 22/SC 32/WG 12
Style Definition
...
Style Definition
Secretariat: JISC
...
Style Definition
...
Date: YYYY-MM-DD2026-05-27
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
Road Vehiclesvehicles — Software Update Engineeringupdate
...
Style Definition
engineering — Vehicle Configuration Informationconfiguration .
Style Definition
information .
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
DPAS stage
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Warning for WDs and CDs
Style Definition
...
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to
Style Definition
...
change without notice and may not be referred to as an International Standard.
Style Definition
...
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of
Style Definition
...
which they are aware and to provide supporting documentation.
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Style Definition
...
Formatted
...
© ISO #### – All rights reserved Formatted
...
Formatted
...
Formatted
...
ISO #####-#:####(X)
Véhicules routiers — Ingénierie de mise à jour du logiciel — Informations sur la configuration des véhicules
2 © ISO #### – All rights reserved
ISO/DPAS 25090:(en)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
Formatted: Indent: Left: 0 cm, Right: 0 cm, Adjust
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
space between Latin and Asian text, Adjust space
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
between Asian text and numbers
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Formatted: French (Switzerland)
EmailE-mail: copyright@iso.org
Formatted: French (Switzerland)
Website: www.iso.orgwww.iso.org
Formatted: French (Switzerland)
Published in Switzerland
Formatted: English (United Kingdom)
Formatted: English (United Kingdom)
iii
ISO/DPAS 25090:(en)
Contents Formatted: Space Before: 48 pt
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 General terminology . 1
3.2 Terms related to vehicle configuration information . 2
3.4 Abbreviated terms . 3
4 Organizational level responsibilities. 3
4.1 General. 3
4.2 Requirements and recommendations . 3
5 Elements of VCI . 4
5.1 General. 4
5.2 Requirements and recommendations . 4
6 Relationships between elements of VCI . 6
6.1 General. 6
6.2 Information model . 6
6.3 Recommendations . 8
7 Selection of relevant VCI. 8
7.1 General. 8
7.2 Requirements and recommendations . 8
Annex A (informative) Examples of selection of relevant VCI . 11
Bibliography . 18
Foreword . 3
Introduction . 4
1 Scope . 4
2 Normative references . 4
3 Terms and definitions . 4
3.1 General terminology . 5
3.2 Definition of elements of vehicle configuration information . 5
3.3 Abbreviated terms . 6
4 Organizational level responsibilities. 6
4.1 General. 6
4.2 Requirements and recommendations . 7
5 Elements of VCI . 7
5.1 General. 7
5.2 Requirements and Recommendations . 7
6 Relationships between elements of VCI . 9
6.1 General. 9
6.2 Information model (Informative) . 9
6.3 Recommendations . 10
iv
ISO/DPAS 25090:(en)
7 Selection of relevant VCI. 11
7.1 General. 11
7.2 Requirements and recommendations . 11
Annex A (informative) Examples of selection of relevant VCI . 13
A.1 General. 13
A.2 Examples . 13
A.2.1 General. 13
A.2.2 A vehicle configuration and assignments of elements of VCI. 13
A.2.3 Software update project level . 14
A.2.4 Software update package level . 15
A.2.5 Software update campaign level . 16
Bibliography . 17
v
ISO/DPAS 25090:(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directiveswww.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
Formatted: English (United Kingdom)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights
Formatted: Font color: Auto, English (United Kingdom)
in respect thereof. As of the date of publication of this document, ISO [had/had not] received notice of (a)
Formatted: Font: Not Italic, Font color: Auto, English
patent(s) which may be required to implement this document. However, implementers are cautioned that this
(United Kingdom)
may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents.www.iso.org/patents. ISO shall not be held responsible for identifying any or all such
Formatted: Font color: Auto, English (United Kingdom)
patent rights.
Formatted: English (United Kingdom)
Formatted: English (United Kingdom)
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
Formatted: Font color: Auto
www.iso.org/iso/foreword.htmlwww.iso.org/iso/foreword.html.
This document was prepared by Technical Committee [or Project Committee] ISO/TC [or ISO/PC] ###, [name
Formatted: Font color: Auto
of committee],22, Road vehicles, Subcommittee SC ##, [name of subcommittee].
Formatted: Font color: Auto
Formatted: Font color: Auto
This second/third/… edition cancels32, Electrical and replaces the first/second/… edition (ISO #####:####),
which has been technically revised.
Formatted: Font: Italic, Font color: Auto
The main changes are as follows:
— xxx xxxxxxx xxx xxxx
A list of all parts in the ISO ##### series can be found on the ISO websiteelectronic components and general
system aspects.
Formatted: Font color: Auto
Formatted: Font: Cambria
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.htmlwww.iso.org/members.html.
vi
ISO/DPAS 25090:(en)
Introduction
ISO 24089, Road Vehicle — Software update engineering requires the use of vehicle configuration information
when performing software update engineering activities. Vehicle configuration information is essential for
software update engineering.
Formatted: Font: 11 pt, Not Bold
ISO 24089 does not define elements of vehicle configuration information or describe any relationships
between such elements. The standardISO 24089 does not mention how to determine relevant vehicle
configuration information for a given software update engineering activity.
This document extends ISO 24089 by providing:
•— definitions of elements of vehicle configuration information;
Formatted: List Continue 1, No bullets or numbering
•— relationships between elements;
•— selection of relevant vehicle configuration information;
•— examples of usage of elements of vehicle configuration information.
This document will also facilitate communications about software update engineering activities that involve
vehicle configuration information throughout the supply chain.
vii
ISO/DPAS 25090:(en)
Formatted: Font: Bold
Formatted: HeaderCentered
Formatted: Font: Bold
Road vehicles — Software update engineering — vehicle — Vehicle
Formatted: Font: Bold
configuration information
Formatted: Font: Bold
1 Scope
Formatted: Main Title 1, Space After: 0 pt
Formatted: Right: 1.5 cm, Bottom: 1 cm, Gutter: 0 cm,
This document provides guidance on how to determine the relevant vehicle configuration information for
Section start: New page, Header distance from edge:
software update engineering according to ISO 24089. This document contains definitions of elements of
1.27 cm, Footer distance from edge: 0.5 cm
vehicle configuration information, relationships between such elements, and examples of usage.
This document does not prescribe formats for elements of vehicle configuration information or how such
information can be collected, stored, and exchanged.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 24089, Road Vehicle vehicles — Software update engineering
Formatted: RefNorm
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 24089 and the following apply.
Formatted: Font color: Auto
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obphttps://www.iso.org/obp
Formatted: No underline, Font color: Auto
Formatted: List Continue 1, No bullets or numbering,
— IEC Electropedia: available at https://www.electropedia.org/https://www.electropedia.org/
Don't keep with next
3.1 General terminology Formatted: No underline, Font color: Auto
Formatted: Font color: Auto
3.1.1
Formatted: TermNum3
hardware
material physical part of a vehicle system.
Formatted: Font: Not Bold, Font color: Auto
Formatted: Font color: Auto
[SOURCE: NIST Special Publication 800-53 rev 5 edited by adding 'vehicle', modified — Term "vehicle" has
been added and eliminating 'component']term "component" has been deleted.]
Formatted: Font: Font color: Auto
Formatted: Font color: Auto
3.1.2
Formatted: TermNum3
relevant VCI
Formatted: Font: French (Switzerland)
relevant vehicle configuration information
subset of VCI (3.1.3)vehicle configuration information (3.1.3) necessary to conform to the requirements of ISO
Formatted: Definition
24089 and this document during a specific software update campaign.
Formatted: Font: 10 pt
Formatted: Font: 10 pt
Formatted: Font: 11 pt
Formatted: FooterPageNumber, Space After: 0 pt, Line
spacing: single
© ISO #### 2026 – All rights reserved
Formatted
...
Formatted
...
ISO #####-#:####(X/DPAS 25090:(en)
Formatted
...
Formatted
...
Formatted
...
3.1.3
vehicle configuration information
Formatted
...
VCI
Formatted
...
comprehensive accounting of hardware versions, software versions and configuration parameters in a vehicle.
Formatted
...
[SOURCE: ISO 24089:2023, 3.1.24], modified — The preferred term "VCI" has been added.]
Formatted
...
Formatted
...
Formatted
...
3.2 Definition of elements ofTerms related to vehicle configuration information
Formatted
...
Formatted
3.2.1
...
ECU identifier
Formatted
...
electronic control unit identifier
Formatted
...
unique designation for an ECU (ISO 24089:2023, 3.1.7).electronic control unit
Formatted
...
Note 1 to entry: An ECU can be virtual.
Formatted
...
Note 2 to entry: See ISO 24089:2023, 3.1.7 for a definition of "ECU". Formatted
...
Formatted
...
3.2.2
Formatted
ECU version identifier .
electronic control unit version identifier
Formatted
...
unique designation for a version of an ECU.electronic control unit
Formatted
...
3.2.3 Formatted
...
hardware identifier
Formatted
...
unique designation for hardware (3.1.1).(3.1.1)
Formatted
...
3.2.4
Formatted
...
hardware version identifier
Formatted
...
unique designation for a version of hardware (3.1.1). (3.1.1)
Formatted
...
3.2.5
Formatted
...
software identifier
Formatted
unique designation for software. .
Formatted
...
3.2.6
Formatted
software version identifier .
unique designation for a version of software.
Formatted
...
Formatted
...
3.2.7
supplemental data identifier Formatted
...
unique designation assigned to any piece of data that is used to support or that is necessary for software
Formatted
...
update engineering and is not covered by other defined VCIvehicle configuration information elements.
Formatted
...
3.2.83.3
Formatted
...
vehicle group identifier
Formatted
...
unique designation that represents characteristics about a set of vehicles.
Formatted
...
3.2.93.3.1
Formatted
...
vehicle identifier
Formatted
...
unique designation for an individual instance of a vehicle.
Formatted
...
3.2.103.3.2
Formatted
...
vehicle system identifier
Formatted
unique designation for a vehicle system (
...
Formatted
...
2 © ISO #### 2026 – All rights reserved
ISO/DPAS 25090:(en)
Formatted: Font: Bold
Formatted: HeaderCentered
Note 1 to entry: See ISO 24089:2023, 3.1.25). for a definition of "vehicle system".
Formatted: Note
3.2.113.3.3
Formatted: TermNum3, Tab stops: Not at 1.98 cm
vehicle system version identifier
Formatted: Term(s)
unique designation for a version of a vehicle system (
Note 1 to entry: See ISO 24089:2023, 3.1.25). for a definition of "vehicle system".
Formatted: Note
3.33.4 Abbreviated terms
App application
ECU electronic control unit
MCU microcontroller unit
SoC system on a chip
SUV sport utility vehicle
VCI vehicle configuration information
VDS vehicle descriptor section
VIN vehicle identification number
App application
ECU electronic control unit
MCU microcontroller unit
SoC system on a chip
SUV sport utility vehicle
VCI vehicle configuration information
VDS vehicle descriptor section
VIN vehicle identification number
4 Organizational level responsibilities
Formatted: Space Before: 12 pt
4.1 General
This clause details requirements and recommendations for organizational responsibilities and processes for
Formatted: Body Text
achieving the requirements and recommendations of this document while engaging in software update
engineering.
4.2 Requirements and recommendations
Formatted: Body Text
Formatted: Font: 10 pt
4.2.1 Software update engineering responsibilities
Formatted: Font: 10 pt
4.2.1.1 4.2.1.1 The organization shall establish, implement, and maintain software update
Formatted: Font: 11 pt
engineering activities in accordance with ISO 24089.
Formatted: FooterPageNumber, Space After: 0 pt, Line
spacing: single
© ISO #### 2026 – All rights reserved
ISO #####-#:####(X/DPAS 25090:(en)
Formatted: Font: Bold
Formatted: Font: Bold
Formatted: HeaderCentered, Line spacing: single
4.2.2 Organizational processes
4.2.2.1 4.2.2.1 The organization shall establish, implement and maintain processes necessary
Formatted: Body Text
to conform to the requirements of this document.
4.2.2.2 4.2.2.2 An audit of organizational processes for software update engineering shall
include the requirements and recommendations of this document.
NOTE Such audits include audits under ISO 24089:2023, 4.3.5.
5 Elements of VCI
5.1 General
This clause describes the requirements and recommendations for management and assignment of elements
Formatted: Body Text
of VCI.
5.2 Requirements and Recommendationsrecommendations
Formatted: Font: Cambria, Not Expanded by /
Condensed by
5.2.1 Element management
Formatted: Font: Cambria, Not Expanded by /
Condensed by
5.2.1.1 The organization shall establish, implement and maintain processes for the management of
elements of VCI.
Formatted: p4
NOTE 1 These processes include how to name VCI elements, what data they identify, and how to manage changes.
NOTE 2 Such processes can be part of the configuration management process required under ISO 24089:2023 4.3.4.4.
5.2.1.2 The organization shall establish, implement and maintain processes for assigning vehicle system
Formatted: p4
identifiers to support software update engineering.
5.2.1.3 The organization shall establish, implement and maintain processes for assigning hardware
identifiers to support software update engineering.
5.2.1.4 The organization shall establish, implement and maintain processes for assigning software
identifiers to support software update engineering.
NOTE These processes include how to name software and how to assign identifiers.
5.2.1.5 The organization shall establish, implement and maintain processes for assigning supplemental
Formatted: p4
data identifiers.
NOTE These processes include how to name supplemental data and how to assign identifiers.
5.2.1.6 The organization may reuse elements of VCI assigned by suppliers.
Formatted: p4
EXAMPLE 1 Supplier-assigned ECU identifier for a supplier-built component (ISO/SAE 21434:2021, 3.1.7) of a vehicle
system.
EXAMPLE 2 Supplier combines different elements of VCI to create a software identifier.
5.2.1.7 The organization shall identify and document any additions, deletions or changes to elements of
VCI during software update engineering activities.
Formatted: Font: 10 pt
NOTE Documentation can be in the software update project plan (ISO 24089:2023, 5.4.1) or the documentation of
Formatted: Font: 10 pt
the software update project (ISO 24089:2023, 5.4.2).
Formatted: Font: 11 pt
Formatted: FooterPageNumber, Space After: 0 pt, Line
spacing: single
4 © ISO #### 2026 – All rights reserved
ISO/DPAS 25090:(en)
Formatted: Font: Bold
Formatted: HeaderCentered
5.2.2 Element assignments
5.2.2.1 A vehicle identifier shall be assigned to each vehicle.
Formatted: p4
EXAMPLE VIN as defined in ISO 3779.
5.2.2.2 A vehicle identifier shall be immutable once it has been assigned.
5.2.2.3 The organization may assign vehicle group identifiers to a group of vehicles.
NOTE 1 A vehicle can have multiple vehicle group identifiers assigned.
EXAMPLE 1 Models, trim packages, year manufactured.
Formatted: Example
NOTE 2 Definitions of the vehicle group identifiers are developed and maintained by the organization responsible for
software
...