← Back to catalogue
Published

Digital Thread

vr.wm-vrt-013 · wm-vrt-013-digital-thread

Define a governed pattern for tracing lifecycle information across separately mastered design, physical-item, operations and twin records.

World Models Information and virtual systems INF.VRT.THR

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 10 questions

Thread scope What the thread connects.

Subject and lifecycle span

The product or asset and the lifecycle stages covered.

Thread subject

The product, item or fleet the thread is about.

  1. Which product type, serial item or fleet does the thread cover?
  2. Which lifecycle stages from requirements to disposal are linked?

Authoritative sources

The systems of record for each stage.

  1. Which system is authoritative for each lifecycle stage?
  2. Who owns each linked source?
Links and configuration How records are connected and kept consistent.

Trace links

Links between requirements, design, build and operation records.

Link integrity

Whether links point to the right versions.

  1. Does each link point to a specific version of the target record?
  2. Which links are broken or point to superseded versions?

Configuration baseline

The as-designed, as-built and as-maintained baselines.

  1. Which as-designed baseline does the as-built item correspond to?
  2. Which changes after delivery are reflected in the as-maintained configuration?
Access and use Who may follow the thread and for what.

Access rights

Access across organizational boundaries.

Cross-party access

What suppliers, operators and authorities may see.

  1. Which parties may follow which links, under which agreement?
  2. Which linked data is export-controlled or confidential?

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
pattern
Navigation path
NAV.INF.VRT.THR
Domain
INF.VRT.THR
Industry
Cross-industry
Tags
digitalthreadinf.vrt.thr

What it is Filled

A digital thread is the set of authoritative links that connect the records of one product or asset across its lifecycle, from requirements and design through manufacturing and the as-built item to operation, maintenance and its digital twin. The individual records it links, and the digital twin as a live model of one asset, are separate subjects.

In scope

  • Thread application identity, subject class and lifecycle coverage contract
  • Endpoint references, semantic trace assertions, configuration selection and qualified evidence
  • Change-impact candidates, partial views, validation results, access, retention and governance

Out of scope

  • Engineering geometry, physical asset, bill-of-materials, maintenance and twin master data
  • Executing manufacturing, changing external masters, actuating equipment or certifying product safety
  • Universal domain ontology, universal access grant, implemented federation protocol or complete lifecycle history

Why it exists Filled

Define a governed pattern for tracing lifecycle information across separately mastered design, physical-item, operations and twin records.

Distinguishing features Filled

  • A federation of links across lifecycle records, not a single model or database.
  • Spans organizations and systems, from design tools to maintenance records.
  • Supports a digital twin but is not the live model of an asset.
  • Its value depends on links to specific versions, not just to documents.

What robots and AI may and may not do Filled

Must not

  • Change records in a source system through the thread without that system's authority.
  • Expose export-controlled or confidential design data to parties without access.
  • Fill gaps in traceability with assumed links presented as recorded.
  • Remove links needed for safety or airworthiness evidence.

Only with a human decision

  • Accepting a configuration baseline for certification or delivery.
  • Granting a new party access to the thread.

May

  • Follow thread links to trace a requirement to design, build and maintenance records.
  • Report broken links and version mismatches.
  • Assemble the configuration of a serial item from linked records.
  • Answer impact questions about a proposed change from the linked records.

Moral aspects Filled

  • Broken traceability can hide safety-critical deviations in products people rely on.
  • Sharing threads across companies exposes intellectual property and controlled technology.
  • Operational data linked to people, such as maintenance staff, needs protection.

Who is affected

  • Users and operators of the product
  • Manufacturers and suppliers
  • Maintenance organizations
  • Safety regulators

Owners Filled

Steward

The product owner or prime manufacturer that governs links across the lifecycle systems.

Roles

Thread steward
Own the local scope, namespace, coverage profile and cross-domain escalation.
Source custodian
Provide qualified authority, version behavior, retention and source access constraints.
Trace author
Submit attributed link claims with evidence and uncertainty.
Configuration reviewer
Review version selections, effectivity and baseline acceptance references.
Access and records reviewer
Assess disclosure, minimization, retention, holds and authorized disposal.
Assurance reviewer
Evaluate graph reports, coverage denominators and unresolved conflicts.

Master systems

  • Product lifecycle management system
  • Manufacturing execution system
  • Maintenance management system
  • Requirements management system

Links to other meta-models Filled

aligned

  • WM-VRT-001 - Candidate conceptual relationship to Digital Twin; no subtype, required twin or mandatory containment.

references

  • WM-OBJ-018 - Optional engineering definition endpoint with externally governed revision and applicability.
  • WM-OBJ-012 - Optional realized assembly configuration endpoint with independent physical-unit identity.

neighbor

  • WM-VRT-001 Digital Twin - Registry parent is treated as candidate conceptual alignment, not inheritance or required containment. A thread can support one or more twins, or none; simulation and state estimation remain twin-owned.
  • WM-OBJ-018 Engineering Design / Product Definition - References a definition revision and its applicability; the thread does not own design content or prove a physical item conforms to it.
  • WM-OBJ-012 Assembly Instance / As-built BOM - References a separately identified physical configuration. Product type, unit, lot and population must remain distinct; as-designed and as-maintained views cannot overwrite as-built evidence.
  • Operations, maintenance, requirements and evidence records - Local links can relate these records with typed, attributed claims. Workflow authority, measurement truth, approvals and source retention remain with their domain masters.
  • Data catalog and provenance graph - Discovery and derivation are supporting concerns. This pattern additionally declares the lifecycle question, subject scope, configuration selection and gaps of each traversal.

parent

  • WM-VRT-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by the product or serial item identifier it threads, together with the owning organization.
  • Each link is identified by the identifiers and versions of the two records it connects.

Direct properties not applicable Not applicable

Not applicable

The subject is an information or institutional record, not a physical object, so it has no physical properties to measure.

Recognition optional Filled

  • Recognized as a navigable set of version-specific links across lifecycle records of one subject.
  • Often confused with a digital twin, a product lifecycle management database or a document archive.

Capabilities and actions required Filled

  • Supports traceability from requirement to as-built and as-maintained item.
  • Supports change impact analysis across lifecycle stages.
  • Feeds digital twins with authoritative configuration data.

Hazards and failure modes required Filled

  • Unsafe products from broken or wrong traceability.
  • Leaks of controlled technology across organizations.
  • Decisions based on superseded versions.

Standards and interfaces required Filled

  • ISO 10303 STEP, including AP242, for product data exchange.
  • OASIS OSLC for lifecycle tool integration.
  • ISO 23247 digital twin framework for manufacturing.

Context of use required Filled

  • Used in aerospace, defence, automotive and complex manufacturing.
  • Configuration management duties come from certification and contract requirements.

Sources Filled

  1. Digital Thread for Manufacturing - National Institute of Standards and Technology
  2. OSLC Core Version 3.0 Part 1: Overview - OASIS Open
  3. OSLC Configuration Management Version 1.0 Part 2: Versioned Resources - OASIS Open
  4. OSLC Configuration Management Version 1.0 Part 3: Configuration Specification - OASIS Open
  5. PROV-O: The PROV Ontology - World Wide Web Consortium
  6. Shapes Constraint Language (SHACL) - World Wide Web Consortium
  7. ISO 10303-242:2025 - Managed model-based 3D engineering - International Organization for Standardization
  8. ISO 23247-1:2021 - Digital twin framework for manufacturing, overview and general principles - International Organization for Standardization
  9. ISO 10303-242 Industrial automation systems and integration - Product data representation and exchange, ISO
  10. Open Services for Lifecycle Collaboration (OSLC), OASIS

Open questions

  • Run the supplied source checker outside the sandbox and independently review current versions, errata, claim support and full normative ISO materials where licensed access is available.
  • Develop domain profiles and executable mappings with fixtures for multiple subject classes, mutable version endpoints, ambiguous selection, inaccessible dependencies, cycles, late updates and lawful disposal.
  • Restore independent external review before any canonical or publishable-draft promotion.
  • Independent external review under the single-provider waiver.
  • Live HTTP status, current-version applicability and full normative ISO text verification.
  • Nested executable instance schemas, domain vocabularies, pinned neighbor revisions and adapter mappings.
  • Operational tests of partial access, mutable endpoints, distributed consistency, clock errors and large graph traversal.
  • Sector-specific safety, contractual, retention, privacy and controlled-information policy review.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-vrt-013-digital-thread/spec.yaml, ver-cy/world-models/card-supplements/wm-vrt-013-digital-thread.json