ISO 22901-1-2008 PDF

Full title and description

Road vehicles — Open diagnostic data exchange (ODX) — Part 1: Data model specification. This part defines the ODX data model and file format (UML model and XML representation) to describe vehicle and ECU diagnostic information so that diagnostic tool applications can interpret ECU messages without protocol‑ or vendor‑specific programming.

Abstract

ISO 22901-1:2008 specifies the concept and data model for Open Diagnostic Data Exchange (ODX). It models diagnostic data (DTCs, data parameters, identification data, ECU configuration/variant coding, communication parameters and protocol specification) using UML and prescribes XML for data exchange. The goal is to make diagnostic data independent of test hardware and protocol software, enabling MVCI devices to interpret exchanged messages and present technician‑readable information without per‑tool software conversion.

General information

• Status: Published — International Standard (confirmed stage).
• Publication date: November 2008 (2008-11).
• Publisher: International Organization for Standardization (ISO).
• ICS / categories: 43.180 — Diagnostic, maintenance and test equipment.
• Edition / version: Edition 1 (2008).
• Number of pages: 486 pages (approx.).

(General publication and bibliographic details above are taken from the ISO bibliographic record for ISO 22901-1:2008.)

Scope

Defines the ODX data model and data exchange format to describe all diagnostic information of a vehicle and its ECUs so that external diagnostic equipment and tools can access, interpret and present diagnostic content independent of vendor‑specific implementations. It covers protocol specifications, communication parameters for protocols and data link layers, ECU programming (flash) data, vehicle interface descriptions (connectors/pinouts), functional descriptions of ECU network diagnostic capabilities and ECU configuration/variant coding. The model is expressed in UML and exchanged in XML.

Key topics and requirements

• ODX data model expressed in UML to describe diagnostic content (DTCs, parameters, IDs, configuration, communication settings).
• XML‑based file format for exchange of ODX diagnostic data between suppliers, vehicle manufacturers and tool vendors.
• Compatibility/interop expectations with MVCI (Modular Vehicle Communication Interface) implementations (see ISO 22900 series).
• Specification of protocol descriptions and communication parameter sets for multiple diagnostic protocols and data link layers.
• Support for ECU programming (flash) data, vehicle interface descriptions (connectors/pinouts) and variant/selection mechanisms for ECU configurations.
• Use cases for aftermarket tool support, cross‑platform ECU diagnostic development and franchise/aftermarket dealer diagnostic tool support.

Typical use and users

Used by vehicle manufacturers (OEMs), ECU and component suppliers, diagnostic tool and software vendors, aftermarket service providers, test and calibration tool developers, and organizations implementing MVCI‑compliant diagnostic systems. Typical applications include creation and delivery of diagnostic databases, tool configuration files, ECU programming exchanges and automated generation of repair/maintenance documentation from machine‑readable diagnostic descriptions.

Related standards

Closely related to other parts of the ISO 22901 series (for example ISO 22901-2 — emissions‑related diagnostic data — and ISO 22901-3 — fault symptom exchange description/FXD). It is intended to work with the MVCI family (ISO 22900 series, e.g., ISO 22900-2 and ISO 22900-3) and references OBD/diagnostic protocol standards such as parts of ISO 15031 and ISO 15765 where applicable.

Keywords

ODX, Open Diagnostic Data Exchange, automotive diagnostics, ECU, MVCI, XML, UML, diagnostic trouble codes, DTC, OBD, diagnostic data model, vehicle interfaces, ECU programming, variant coding.

FAQ

Q: What is this standard?

A: ISO 22901-1:2008 is Part 1 of the Open Diagnostic Data Exchange (ODX) series; it specifies the data model and exchange format for vehicle and ECU diagnostic information so that diagnostic tools can interpret messages without vendor‑specific software.

Q: What does it cover?

A: It covers the ODX conceptual model and technical representation (UML and XML) for diagnostic trouble codes, data parameters, identification and configuration data, communication parameters, protocol specifications and ECU programming/flash information — essentially the structured description of diagnostic content for exchange between suppliers, OEMs and tool vendors.

Q: Who typically uses it?

A: Vehicle OEMs, ECU/supplier developers, diagnostic tool manufacturers, aftermarket service providers, and teams building MVCI‑compliant diagnostic systems or diagnostic databases use this standard to share and implement diagnostic data.

Q: Is it current or superseded?

A: ISO 22901-1:2008 remains the published Part 1 edition from 2008 and is listed as an ISO International Standard in the ISO bibliographic record; other parts of the series (for example Parts 2 and 3) were published later. Users should confirm the standard's review/confirmation status or any national adoptions before relying on it for procurement or compliance.

Q: Is it part of a series?

A: Yes — ISO 22901 is a multi‑part series for Open Diagnostic Data Exchange (ODX). Notable related parts include ISO 22901-2 (emissions‑related diagnostic data) and ISO 22901-3 (fault symptom exchange description / FXD); the ODX concept is also designed to interoperate with the ISO 22900 MVCI family.

Q: What are the key keywords?

A: ODX, XML, UML, ECU, diagnostic trouble code (DTC), MVCI, OBD, diagnostic data model, vehicle diagnostics, fault symptom exchange, variant coding.