Member Portal Join Now Resources
AutoID™ Programme

Scope & Coverage

AutoID™ is designed to cover the full automotive ecosystem — but always through a clearly declared scope. This page explains what can receive an AutoID™, what the record can cover, and what is intentionally out of scope.

Scope Rules (Quick)
  • Declared: scope is visible by design
  • Bounded: no vague “everything” claims
  • Comparable: scope enables consistent interpretation
AutoID™ is a reference layer — not homologation, not market access.
Framework & Principles Use Cases & Value

Scope Makes Identity Comparable

The same “AutoID™” cannot mean different things for different users. That’s why scope is always declared: what is covered, at what level, and under which boundaries — so the ecosystem can interpret identity consistently.

What Can Receive an AutoID™?

AutoID™ can be applied across multiple layers of the automotive ecosystem. Each layer has a different purpose, but all share the same logic: declared scope, evidence references and lifecycle-aware status.

Models, Variants & Vehicles

Model, variant, frozen configuration or individual-vehicle identity, with each object class kept distinct.

Components & Energy Systems

Components such as battery systems, recorded at type, batch or individual-instance granularity as authorised.

Software & Defined Functions

Software releases, supported hardware, safety-relevant functions and controlled update relationships.

Organizations & Facilities

Verified legal organizations and facilities, separated from any technical assessment or vehicle approval.

AutoID™ can be applied broadly, but only through declared boundaries that keep records meaningful.

Scope Levels (How Precise Can It Be?)

AutoID™ scope can be defined at different levels, depending on the intended clarity and available evidence. Precision improves comparability, reduces confusion and strengthens traceability.

Model / Variant / Configuration
A stable engineering family, defined variant or frozen approval-relevant hardware and software baseline.
Component Level
A component type, batch or individual instance with declared relationships and evidence scope.
Software Level
A software component or release scope with version logic.
Vehicle / Organization / Facility
An individual vehicle binding or a verified legal organization or facility record under declared boundaries.
Scope definition determines what “verification” means — it prevents unclear claims.

What AutoID™ Can Cover — and What It Will Not

AutoID™ focuses on identity and traceability. It can document technical scope, evidence logic and lifecycle status. It intentionally avoids commercial or regulatory judgments.

AutoID™ can cover
  • Declared scope boundaries
  • Evidence references and trace markers
  • Versioned lifecycle status
  • Change history visibility
  • Public summary + restricted layers
AutoID™ will not cover
  • Market access / permission decisions
  • Replacement of legal compliance
  • Commercial quality or brand ranking
  • Unbounded “everything” claims
  • Confidential detail without access rules
AutoID™ is designed to prevent misuse: it is a reference layer, not a regulatory or commercial tool.

Scope Examples (Mock-up)

Below are simplified examples to show how scope changes what the AutoID™ record represents. The structure is designed to be readable and comparable.

Example
Vehicle Variant Scope
Typical
  • Scope: Model / variant / configuration boundaries
  • Identity: linked to a declared vehicle variant scope
  • Lifecycle: versioned updates and status changes
  • Transparency: public summary + restricted layers
Example
ADAS / Software Scope
Common
  • Scope: specific system module and release boundaries
  • Identity: linked to version logic and change history
  • Status: identity, assessment, legal-source status and currency shown separately
  • Transparency: appropriate access and summary rules
Scope is what keeps AutoID™ honest: it ensures statements remain bounded, technical and comparable.

AutoID First Edition Documents

Open the controlled First Edition documents for complete requirements, procedures and working records.

Vehicle Identity and Homologation Evidence Standard
The 120 mandatory controls, defined claims, object boundaries and lifecycle rules.
33 pagesOpen PDF
Registry Data and Interface Specification
Identifier syntax, state logic, data contracts, security boundaries and implementation acceptance.
15 pagesOpen PDF

Next: Framework & Principles

Learn how AutoID™ maintains neutrality and credibility — through transparency, safeguards and a trust model that avoids market access decisions.

Framework & Principles Use Cases & Value

IAF’s Global Member Network

From regional OEMs to global tech pioneers, IAF unites a diverse community committed to shaping tomorrow’s mobility.

  • Active global outreach across key mobility regions
  • Strategic onboarding of founding corporate & expert members
  • Monthly roundtables, knowledge-sharing & draft consultations
  • Early-stage collaborations with research & policy networks

…and many more benefits designed to amplify your impact in the evolving mobility ecosystem.

Join the Federation
Explore Network

Join Us in Shaping the Future of Global Mobility

Be part of a powerful movement driving safer, smarter, and more sustainable transportation systems worldwide. Connect with leaders, influence policies, and co-create the automotive innovations of tomorrow with the International Automotive Federation.

Become a Member Explore Membership