ISO/PAS 25090

• 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
• ICS: 43.040.15 - Car informatics. On board computer systems
• 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: 29-Aug-2026

Overview

ISO/PAS 25090: Road vehicles - Software update engineering - Vehicle configuration information is an ISO Publicly Available Specification (PAS) that delivers essential guidance for identifying relevant vehicle configuration information within the context of software update engineering, as referenced by ISO 24089:2023. This standard clarifies how to define key elements of vehicle configuration information (VCI), describes the relationships among these elements, and presents practical examples demonstrating selection and usage.

By focusing on the definitions and relationships of VCI elements, ISO/PAS 25090 supports consistent and effective software update processes across the automotive industry, enhancing the communication and understanding of vehicle configurations throughout the supply chain. Importantly, the standard does not define formats for VCI elements or prescribe how configuration information should be collected, stored, or exchanged.

Key Topics

• Elements of Vehicle Configuration Information: ISO/PAS 25090 lists core VCI elements, including hardware identifiers, software identifiers, ECU identifiers, vehicle identifiers (such as VIN), vehicle system identifiers, version identifiers, and supplemental data identifiers.
• Relationships between VCI Elements: The document outlines how different configuration elements connect, such as linking specific hardware and software versions to appropriate ECUs and vehicle systems, ensuring traceability and dependency management.
• Selection of Relevant VCI: ISO/PAS 25090 describes a process for determining which configuration elements are necessary for a specific software update project, package, or campaign, aiming for efficient and targeted update management.
• Organizational Responsibilities: The standard emphasizes the need for clear internal processes for assigning, managing, and documenting VCI elements, as well as ensuring reliable audit trails.
• Examples of Use: Annex A provides practical examples illustrating VCI selection and assignment as part of real-world software update projects, supporting understanding across different use cases.

Applications

ISO/PAS 25090 delivers practical value to a range of automotive stakeholders involved in vehicle software updates:

• OEMs & Vehicle Manufacturers: Streamline identification of configuration elements critical for software updates and maintain compliance with ISO 24089 requirements.
• Tier 1/Tier 2 Suppliers: Facilitate consistent assignment of identifiers for delivered hardware, software, and ECUs, simplifying integration and warranty management.
• Software Update Engineers: Use defined VCI elements when planning and executing software update campaigns, enhancing the traceability and compatibility checks needed for secure, effective updates.
• Aftermarket & Service Providers: Improve communication about vehicle configuration and update needs, reducing errors in the deployment of updates or diagnostics.
• Certification Bodies & Regulatory Authorities: Reference a harmonized approach for the determination and documentation of vehicle configuration information during audits and regulatory reviews.

Related Standards

To maximize practical impact and ensure compatibility, ISO/PAS 25090 should be used alongside related key standards, including:

• ISO 24089:2023 - Road vehicles - Software update engineering: Core reference for software update processes in the automotive domain.
• ISO 3779 - Road vehicles - Vehicle identification number (VIN): The basis for assigning unique vehicle identifiers as part of VCI.
• ISO 14229-1 - Unified Diagnostic Services (UDS): Supports ECU identification and diagnostic messaging, which can inform VCI element assignment.
• ISO/SAE 21434 - Road vehicles - Cybersecurity engineering: Provides context for secure handling and assignment of configuration information.

Adoption of ISO/PAS 25090 helps ensure consistency, traceability, and clarity of vehicle configuration data, supporting robust and efficient automotive software update engineering in compliance with international best practices.

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: [phone]
Email: [e-mail]
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: [e-mail]
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
...