{
  "id": "COMP-DT-001",
  "slug": "digital-twin",
  "status": "Normative Comparison",
  "subject": "OCOM",
  "target": "Digital Twin",
  "targetShort": "Digital Twin",
  "summary": "OCOM and Digital Twins both represent things over time, but with different intent. A Digital Twin is a live, synchronized representation of a specific asset's state, optimized for fidelity to that asset. OCOM is a governance-first operating model of organizational objects — physical or abstract — optimized for identity, ownership, lifecycle and evidence. A Digital Twin asks 'what is the current state of this thing'; OCOM asks 'how is this thing governed across its life'. A Digital Twin can be modelled as an OCOM Object.",
  "scope": {
    "compared": [
      "How each represents an asset and its state",
      "How each treats identity and lifecycle",
      "How governance and ownership are handled"
    ],
    "notCompared": [
      "Real-time telemetry pipelines or sensor integration",
      "Physics simulation or 3D visualization",
      "Specific IoT platforms"
    ]
  },
  "mappings": [
    {
      "ocom": "Object",
      "target": "Twin / asset model",
      "equivalent": "Partial"
    },
    {
      "ocom": "Identity",
      "target": "Asset identifier",
      "equivalent": "Similar"
    },
    {
      "ocom": "Metadata",
      "target": "Telemetry / properties",
      "equivalent": "Partial"
    },
    {
      "ocom": "Lifecycle",
      "target": "Asset lifecycle",
      "equivalent": "Similar"
    },
    {
      "ocom": "Evidence",
      "target": "Sensor history",
      "equivalent": "Partial"
    },
    {
      "ocom": "Ownership",
      "target": "—",
      "equivalent": "None"
    }
  ],
  "differences": [
    {
      "aspect": "Intent",
      "ocom": "Governance of objects across their life",
      "target": "Fidelity to a physical asset's current state"
    },
    {
      "aspect": "Subject",
      "ocom": "Any object, physical or abstract",
      "target": "A specific physical (or virtual) asset"
    },
    {
      "aspect": "Time",
      "ocom": "Governed history and evidence",
      "target": "Real-time or near-real-time state sync"
    },
    {
      "aspect": "Governance",
      "ocom": "First-class: ownership, policy, contract",
      "target": "Not defined by the model"
    }
  ],
  "capabilities": [
    {
      "capability": "Real-time state sync",
      "ocom": "—",
      "target": "✓"
    },
    {
      "capability": "Identity",
      "ocom": "✓",
      "target": "✓"
    },
    {
      "capability": "Lifecycle",
      "ocom": "✓",
      "target": "✓"
    },
    {
      "capability": "Governance",
      "ocom": "✓",
      "target": "—"
    },
    {
      "capability": "Ownership",
      "ocom": "✓",
      "target": "—"
    },
    {
      "capability": "Evidence",
      "ocom": "✓",
      "target": "Partial"
    },
    {
      "capability": "AI retrieval",
      "ocom": "✓",
      "target": "Partial"
    }
  ],
  "interoperability": [
    "A Digital Twin MAY be modelled as an OCOM Object with an identity and a lifecycle.",
    "OCOM MAY govern a fleet of Digital Twins — assigning ownership, policy and evidence around them — without replacing the twin's real-time state.",
    "The recommended composition is the Digital Twin for live state and OCOM for governance around that state."
  ],
  "references": [
    {
      "label": "OCOM Object",
      "url": "/vocabulary/object"
    },
    {
      "label": "OCOM Identity",
      "url": "/vocabulary/identity"
    },
    {
      "label": "OCOM Ownership",
      "url": "/vocabulary/ownership"
    },
    {
      "label": "Digital Twin concepts (e.g. ISO 23247)",
      "url": null
    }
  ],
  "canonical": "https://ocom.uno/comparisons/digital-twin",
  "url": "https://ocom.uno/comparisons/digital-twin"
}