Overview
ISO 13209-1:2011 - Road vehicles: Open Test sequence eXchange format (OTX) - Part 1: General information and use cases defines the rationale, document structure and real‑world use cases for the OTX concept. It introduces a tester‑independent, XML‑based data exchange format for the documentation and formal description of diagnostic test sequences. The aim is to enable uniform, machine‑readable transfer of diagnostic logic between electronic system suppliers, OEMs, service dealerships/repair shops and the aftermarket.
Key topics and technical requirements
- XML‑based format & data model: OTX is designed as a formal, machine‑readable representation suitable for visualization and automated processing. (Detailed core model and XSD/UML artifacts are specified in Part 2.)
- OTX Core vs OTX Extensions: The Core defines essential control structures (loops, branches, procedures, sequences). Extensions (otxIFD) provide interfaces for HMI, internationalization, diagnostic communication and other domain‑specific features.
- Use‑case driven design: Part 1 documents clustered use cases - documentation/specification, exchange/reusability, extensibility, localization and runtime execution - which guided the standard’s design.
- Interoperability & integration: OTX is intended to integrate with existing automotive diagnostic standards and infrastructures rather than replace them.
- Quality and lifecycle considerations: Emphasis on improving documentation quality, reducing redundant re‑implementation, enabling single‑source authoring workflows and ensuring long‑term availability of test sequences.
- Actors and processes: Definitions for roles (engineering, manufacturing, after‑sales, aftermarket) and authoring/runtime process chains are provided.
- Normative references: Relies on and complements standards such as ISO 14229 (UDS), ISO 22900 (MVCI) and ISO 22901 (ODX).
Applications and who uses it
- OEM engineering teams standardize and exchange diagnostic procedures across development, manufacturing and after‑sales.
- Electronic system suppliers deliver reusable test sequences that integrate into multiple OEM toolchains.
- Diagnostic tool vendors and VCI integrators implement runtime interpreters, toolchains and adapters (MVCI/GDI/HMI).
- Service dealerships and repair shops receive consistent, human‑readable and machine‑executable procedures for guided diagnostics, reprogramming and initialization.
- Aftermarket and legislative test providers use OTX for long‑term availability and localization of diagnostic content.
Related standards
- ISO 14229 (Unified Diagnostic Services - UDS)
- ISO 22900 (Modular Vehicle Communication Interface - MVCI)
- ISO 22901 (Open Diagnostic Data Exchange - ODX)
- ISO 13209 Parts 2 & 3 (Core data model; standard extensions)
Keywords: ISO 13209-1, OTX, Open Test sequence eXchange, diagnostic test sequences, XML‑based, vehicle diagnostics, OEM, UDS, MVCI, ODX, diagnostic authoring.