Digital Twin Standards: ISO 23247 vs ISO/IEC 30173 vs DTC Reference Architecture in 2026
Last Updated: April 29, 2026
Architecture at a glance
By 2026, digital twin standards have crystallized into a mature ecosystem. ISO 23247 (manufacturing), ISO/IEC 30173 (terminology), and the Digital Twin Consortium reference architecture have become the dominant frameworks across industry verticals. But they are not competitors—they are complementary layers: ISO 23247 provides the domain-specific reference architecture for manufacturing systems, ISO/IEC 30173 defines the shared terminology contract that other JTC 1 standards use, and the DTC Capabilities Periodic Table maps the cross-cutting services and intelligence layers that make twins operationally useful.
This article compares the leading digital twin standards, shows how they relate to Asset Administration Shell (AAS), ISA-95 operations models, and emerging frameworks like NIST IR 8356 and IEEE P2806, and gives you a decision matrix to pick the right standard(s) for your domain.
The Four Leading Standards Frameworks
1. ISO 23247: Digital Twin Framework for Manufacturing
ISO 23247 is the most prescriptive standard for industrial digital twins. Released in parts between 2021 and 2024, it defines a complete four-domain reference architecture:
| Domain | Role | Key Entities |
|---|---|---|
| Observable Manufacturing Element (OME) | The physical asset or process | Machines, production lines, supply chains |
| Digital Twin Engine (DTE) | The computational twin — simulation, optimization, prediction | Physics models, control algorithms, anomaly detection |
| Digital Twin Synchronization Entity (DTSE) | The bidirectional sync layer — ingests real-time data, updates virtual state, executes controls | IoT gateways, message queues, event processors |
| User Entity (UE) | Human operators, engineers, analysts | Mobile apps, dashboards, AR/VR visualization |
The four-domain model is hierarchical and recursive: each OME can spawn its own DTE, DTSE, and UE. A factory floor might have machine-level twins (CNC → motor twins), line-level twins (production line → product flow twins), and enterprise-level twins (supply chain → logistics twins).
ISO 23247 Parts:
– Part 1 (Framework): Core concepts, entities, relationships
– Part 2 (Data Format): XML schema for twins, property definitions
– Part 3 (Implementation Guidance): Patterns for manufacturing execution systems (MES), product lifecycle management (PLM), enterprise resource planning (ERP)
– Part 4 (Interoperability)**: Mapping to OPC UA, REST APIs, event streams
Key Advantages
- Domain-specific depth for manufacturing
- Clear entity roles reduce ambiguity
- Bridges MES, ERP, and PLC ecosystems
- ISA-95 friendly (see mapping below)
Limitations
- Manufacturing-focused; requires translation for AEC, healthcare, energy
- Parts 3–4 still maturing (2024–2026 refinement cycles)
- No formal capability taxonomy (unlike DTC)
2. ISO/IEC 30173:2023 — Digital Twin Concepts and Terminology
ISO/IEC 30173 is the terminology reference for the entire JTC 1 digital twin landscape. Published in 2023, it does not prescribe architecture—it defines the vocabulary contract that other standards, frameworks, and vendors must use.
Key definitions:
| Term | Definition | Scope |
|---|---|---|
| Digital Twin | A digital representation of a physical entity, process, or system in its operational context, synchronized with the real-world entity in real-time or near-real-time | Intentionally broad; applies to any domain |
| Digital Twin Model (DTM) | The set of digital models (physics, behavior, controls) that constitute the twin’s capabilities | Includes 3D CAD, simulation, ML models, rules engines |
| Lifecycle Synchronization | The continuous update cycle: physical → sensors → DTSE → DTE → visualization and decisions → control feedback → physical | Core loop; may be periodic or event-driven |
| Trustworthiness | The confidence that the twin’s outputs (predictions, recommendations) align with physical reality and ethical constraints | Includes accuracy, model explainability, data provenance |
ISO/IEC 30173 vs ISO 23247:
– ISO/IEC 30173 is the language layer (defines what “digital twin” means to JTC 1)
– ISO 23247 is the architecture layer (defines how to build one for manufacturing)
Both reference each other; ISO 23247’s OME/DTE/DTSE/UE terms are formally grounded in 30173’s definitions.
Key Advantages
- Non-prescriptive; allows flexibility across domains
- Acts as a standards interoperability bridge
- Enables cross-domain terminology alignment
- Published and stable; no major revisions expected until 2028
Limitations
- Does not recommend tools or architectures
- Requires supplementary standards (like 23247) for actionable guidance
- Terminology alone does not guarantee interoperability
3. Digital Twin Consortium (DTC) Capabilities Periodic Table
The DTC Periodic Table is a capability taxonomy—not a standard, but a de facto reference model used by enterprises to scope and procure digital twin solutions. Published in 2022 and updated through 2026, it organizes digital twin capabilities into six domains:
┌──────────────────────────────────────────────────────────────────┐
│ DTC Capabilities Periodic Table │
├──────────────────────────────────────────────────────────────────┤
│ │
│ Data Services │ Integration │ Intelligence │
│ • Ingestion │ • Data federation │ • Analytics │
│ • Time series DB │ • Semantic mapping │ • ML training │
│ • Event stream │ • API orchestration │ • Simulation │
│ • Data lake │ • Sync protocols │ • Optimization│
│ │ │ │
│ UX/Visualization │ Management │ Trustworthiness
│ • 2D dashboards │ • Lifecycle mgmt │ • Audit trail │
│ • 3D spatial │ • Version control │ • Explainability
│ • AR/VR immersion │ • Identity & access │ • Data quality
│ • Real-time alerts │ • SLA monitoring │ • Compliance │
│ │ │ │
└──────────────────────────────────────────────────────────────────┘
Each domain contains 6–10 capabilities; the full table spans ~50 distinct services. The DTC table answers: Which services must your platform stack provide to claim “digital twin” status?
Key Advantages
- Practical; vendors use it to market and scope solutions
- Agnostic to industry or technology stack
- Regularly updated (annual reviews)
- Widely recognized across manufacturing, AEC, energy, smart cities
Limitations
- Not a formal ISO/IEC standard
- No formal mapping to ISO 23247 or 30173 (though conceptual alignment exists)
- Capability granularity varies; some overlap between domains
- Requires human judgment to weight which capabilities matter for your use case
4. NIST IR 8356 and IEEE P2806 — Emerging Consensus
NIST Interagency Report 8356 (2021, updated 2024) provides a U.S. federal perspective on digital twin engineering practices. It emphasizes:
– Verification & validation (V&V) frameworks for twin accuracy
– Accreditation pathways for mission-critical twins (aerospace, energy, healthcare)
– Cybersecurity and data provenance
IEEE P2806 (under development; expected 2026–2027) aims to define a unified digital twin reference architecture that bridges ISO 23247, DTC, and domain-specific standards. It will likely become the canonical architectural framework for IEEE-coordinated industries (electrical, energy, telecommunications).
Comparative Standards Matrix
| Aspect | ISO 23247 | ISO/IEC 30173 | DTC Periodic Table | NIST IR 8356 | IEEE P2806 (draft) |
|---|---|---|---|---|---|
| Purpose | Manufacturing ref. arch. | Terminology contract | Capability taxonomy | V&V and accreditation | Unified reference arch. |
| Domain Coverage | Manufacturing | All domains | All domains | All domains | All domains (emphasis energy/electrical) |
| Maturity (2026) | Stable (Parts 1–3) | Stable & published | Mature; active updates | Mature guidance | In development |
| Prescriptiveness | High (entities, data flow) | Low (definitions only) | Medium (capability checklist) | Medium (V&V patterns) | High (expected) |
| Interoperability | OPC UA, REST, MQTT | Terminology alignment | Vendor-agnostic | Standards-agnostic | Alignment expected |
| Implementation Cost | Moderate–high | Low (vocabulary) | Low–medium (scoping) | Moderate (V&V adds overhead) | TBD; likely moderate |
How ISO 23247 Maps to ISA-95 Manufacturing Operations
ISA-95 (ANSI/ISA-95, “Enterprise-Control System Integration”) defines the hierarchical automation pyramid:
Level 4: Enterprise (ERP, PLM, supply chain)
Level 3: Manufacturing Operations (MES, scheduling)
Level 2: Supervisory (SCADA, HMI dashboards)
Level 1: Control (PLC, motion controllers)
Level 0: Field (sensors, actuators)
ISO 23247 aligns with ISA-95 as follows:
| ISA-95 Level | ISO 23247 Entity | Example |
|---|---|---|
| Level 4 (Enterprise) | User Entity (UE) + DTE optimization | ERP dashboards, supply chain simulation |
| Level 3 (MES) | DTSE (sync) + DTE (prediction) | Predictive maintenance, production scheduling |
| Level 2 (SCADA/HMI) | DTSE (real-time ingestion) | Data from PLCs, sensor aggregation |
| Levels 0–1 (Field) | Observable Manufacturing Element (OME) | Machines, sensors, actuators |
Practical implication: If your MES (Level 3) collects anomaly detection predictions from a digital twin, that twin’s DTE writes results back to the MES via the DTSE—a Level 3 ↔ DTE loop that ISO 23247 calls “synchronization.”
Asset Administration Shell (AAS) and ISO 23247: Complementary, Not Competing
Asset Administration Shell (AAS) is the Industry 4.0 data model—a hierarchical, standardized structure for representing asset metadata, capabilities, and lifecycle events. It is not a digital twin standard, but rather a data exchange format for twins.
The relationship:
| Aspect | AAS | ISO 23247 |
|---|---|---|
| What it is | Data structure for asset representation | Architecture for twin entities and flows |
| Where it lives | Asset properties, interfaces, submodels | Blueprints for DTE, DTSE, synchronization |
| Use together? | Yes, almost always | The Observable Manufacturing Element (OME) metadata often lives in an AAS submodel |
| Example | An AAS submodel “Maintenance” with historical failure modes | The DTE uses that AAS data to train predictive models |
Real-world pattern: A manufacturing facility using ISO 23247 will typically:
1. Define each asset’s static metadata in an AAS (submodels for geometry, materials, maintenance history)
2. Implement the DTSE to read AAS properties and real-time sensor data
3. Run the DTE (simulation, ML) on that fused data
4. Write predictions back to the AAS (or a linked database) via the DTSE
Read more: Asset Administration Shell AAS Industry 4.0
DTDL (Microsoft Digital Twins Definition Language): Language, Not Framework
DTDL is a JSON-LD schema language used primarily in Azure Digital Twins to model entity relationships and properties. It answers: “How do I formally describe a digital twin’s data structure?”
| Aspect | DTDL | ISO 23247 |
|---|---|---|
| Scope | Serialization format for twin definitions | Architecture and lifecycle framework |
| Level | Data model syntax | System-of-systems design |
| Use case | Define a “Pump” with properties (pressure, temperature, failure_rate) | Design how the pump’s OME ↔ DTE ↔ DTSE ↔ UE flow data |
Most common setup: Use ISO 23247 to architect your twin system, then use DTDL (or similar JSON schemas) to serialize the twin entities.
ISO 19650 (BIM) and Digital Twins in the Built Environment
ISO 19650 is the AEC (architecture, engineering, construction) standard for BIM (Building Information Modeling) and digital twins for built assets (buildings, infrastructure, utilities).
ISO 19650 vs ISO 23247:
| Aspect | ISO 19650 | ISO 23247 |
|---|---|---|
| Domain | Buildings, infrastructure, civils | Manufacturing systems |
| Scope | Lifecycle data management (design → construction → operations) | Real-time operational twins |
| Key focus | Information exchange protocols, document management | Synchronization, simulation, control loops |
| Typical use | BIM federated models, asset registers | Predictive maintenance, energy optimization for building systems |
Integration pattern: A smart building may use:
– ISO 19650 to govern design and asset data (architectural model, MEP system specs, maintenance protocols)
– ISO 23247 concepts to build operational twins (HVAC plant DTE, occupancy prediction, fault detection)
– ISO/IEC 30173 terminology to ensure both layers speak the same vocabulary
Read more: ISO 19650 BIM Digital Twins Construction
Domain Decision Matrix: Which Standard(s) to Adopt
The following matrix helps you choose the right standard(s) for your domain and scope:
| Domain | Primary Standard | Secondary Standards | Rationale |
|---|---|---|---|
| Discrete Manufacturing | ISO 23247 + AAS | ISA-95, DTDL | Direct alignment with MES/PLC; AAS for asset metadata |
| Process Manufacturing | ISO 23247 (Part 3 process variant) | ISA-95, NIST IR 8356 | Chemical, pharma, food: DTE emphasizes model fidelity; V&V critical |
| Building/Infrastructure | ISO 19650 (BIM base) + ISO 23247 concepts | ISO/IEC 30173, DTC | Asset-heavy; operational twins for systems (HVAC, lighting, security) |
| Energy/Utilities | IEEE P2806 (draft) + ISO 23247 | NIST IR 8356, DTC | Grid, microgrid, renewable: emphasizes control stability, resilience |
| Healthcare/Devices | ISO 13485 (quality) + ISO 23247 concepts | NIST IR 8356, DTC | Regulatory rigor; V&V and cybersecurity paramount; limited real-time control |
| Smart Cities/IoT | DTC Periodic Table (primary) + ISO/IEC 30173 | Domain-specific subsets | Multi-domain ecosystem; vocabulary alignment critical; lightweight architecture |
Interoperability Strategies: Implementing One Standard, Exposing Many
In practice, most large enterprises adopt one primary standard for architecture and crosswalk to secondary standards for integration.
Pattern 1: ISO 23247-Native with DTC Capability Crosswalk
- Architecture: ISO 23247 (OME, DTE, DTSE, UE)
- Capability Scoping: DTC Periodic Table (which of the 50 capabilities do we implement?)
- Vocabulary Alignment: ISO/IEC 30173 (ensure terminology consistency in APIs and documentation)
Pattern 2: AAS-Centric with ISO 23247 Runtime Architecture
- Asset Metadata: Asset Administration Shell submodels
- Operational Architecture: ISO 23247 entities around the AAS
- Data Exchange: OPC UA (standardized in ISO 23247 Part 4) with AAS semantic mapping
Pattern 3: DTC-Led Capability Roadmap, ISO 23247 Implementation Patterns
- Capability Roadmap: DTC Periodic Table (scopes what to build)
- Architecture Reference: ISO 23247 (shows how to build each capability)
- Terminology: ISO/IEC 30173 (ensures team and vendor alignment)
Maturity Heat Map: Stability and Adoption by 2026
| Standard | Parts | Stability | Adoption | Recommendation |
|---|---|---|---|---|
| ISO 23247 | 1, 2, 3 stable; 4 maturing | High (Parts 1–3) | Growing in manufacturing | Adopt now for manufacturing; ISO 23247 Part 4 interop guidance arriving mid-2026 |
| ISO/IEC 30173 | 1 stable | High; published & locked | High across JTC 1 | Adopt immediately for terminology; low cost, high value |
| DTC Periodic Table | v1.1 (2024) | Medium–high; annual updates | Very high across all sectors | Adopt for scoping and capability roadmapping; not architecture-binding |
| NIST IR 8356 | Updates ongoing | High (guidance, not mandate) | Growing in federal procurement | Adopt for V&V frameworks; critical for regulated industries (pharma, aerospace, energy) |
| IEEE P2806 | Early draft | Medium (expected 2026–2027) | Limited until publication | Monitor closely; likely to become canonical by 2027 |
Five-Step Implementation Roadmap
Step 1: Terminology Alignment (Weeks 1–2)
Adopt ISO/IEC 30173 vocabulary across your team and vendor RFPs. Low cost; enables clear communication.
Checklist:
– [ ] Share ISO/IEC 30173 glossary with architects, engineers, procurement
– [ ] Update RFP boilerplate to reference 30173 definitions
– [ ] Create a project glossary (e.g., “In our system, ‘synchronization’ means X”)
Step 2: Architecture Alignment (Weeks 3–4)
If manufacturing-focused: adopt ISO 23247 four-domain structure. If multi-domain: use DTC Periodic Table to scope capabilities.
Checklist:
– [ ] Map your current twin architecture to ISO 23247 entities (or DTC capabilities)
– [ ] Identify gaps (missing DTSE? No formal DTE? Limited UE analytics?)
– [ ] Rank gaps by business impact
Step 3: Data & Metadata Governance (Weeks 5–8)
Define how assets are represented (AAS submodels if industry 4.0; domain-specific schemas otherwise) and how synchronization occurs.
Checklist:
– [ ] Adopt Asset Administration Shell (AAS) or equivalent metadata structure
– [ ] Define synchronization frequency, latency, and trigger rules (event-driven vs. polling)
– [ ] Establish data quality and provenance tracking
Step 4: Capability Build-Out (Months 2–6)
Using DTC Periodic Table as a roadmap, implement missing capabilities in priority order.
Example:
– Month 2: Data Services (time-series ingestion, event streams)
– Month 3: Integration (data federation, semantic mapping)
– Months 4–5: Intelligence (analytics, initial ML models)
– Month 6: Trustworthiness (audit trails, model explainability)
Step 5: V&V and Accreditation (Months 6–12)
Apply NIST IR 8356 V&V patterns; if regulated, plan for formal audit.
Checklist:
– [ ] Define verification metrics (twin accuracy vs. physical reality)
– [ ] Document validation assumptions and model limitations
– [ ] Prepare for third-party audit (if required by regulation or customer contract)
FAQ: Digital Twin Standards in 2026
Q: Do I have to choose just one standard?
A: No. The best practice is to adopt one primary architecture (e.g., ISO 23247 for manufacturing) and use secondary standards (e.g., DTC, ISO/IEC 30173) for scoping and vocabulary. This keeps your system coherent while ensuring vendor flexibility.
Q: Which standard is “the best”?
A: There is no universally “best” standard. ISO 23247 dominates manufacturing. DTC Periodic Table dominates scoping and procurement. ISO/IEC 30173 is mandatory for terminology alignment. IEEE P2806 will likely become the universal default by 2027.
Q: Can I use ISO 23247 for non-manufacturing domains?
A: Yes, but with translation. The four-domain architecture (OME, DTE, DTSE, UE) is generic. You’ll need to:
1. Define what the OME represents in your domain (e.g., a building’s HVAC plant for smart buildings)
2. Map your domain-specific data to ISO 23247 concepts
3. Supplement with domain-specific standards (e.g., ISO 19650 for BIM) for metadata and lifecycle governance
Q: What’s the relationship between AAS and ISO 23247?
A: AAS is the data format (how assets are represented); ISO 23247 is the architecture (how twins move data and compute). Use both: represent your assets in AAS, then orchestrate them using ISO 23247 patterns.
Q: Should I wait for IEEE P2806 before adopting a standard?
A: No. IEEE P2806 (expected 2026–2027) will likely align with or build on ISO 23247 and DTC, not replace them. Adopting ISO 23247 now prepares you for a smooth transition. Use ISO/IEC 30173 terminology to future-proof your definitions.
Q: How do I handle legacy systems (SCADA, ERP) in an ISO 23247 architecture?
A: Map legacy components to ISO 23247 entities:
– Existing SCADA/HMI → DTSE (ingestion layer) + UE (visualization)
– Existing ERP data → OME metadata (asset properties)
– New predictive logic → DTE (simulation and ML)
– Use OPC UA or REST APIs (standardized in ISO 23247 Part 4) as the glue layer
Q: What is the cost of implementing these standards?
A:
– ISO/IEC 30173 (terminology): Minimal (~$5–10k for training and glossary)
– ISO 23247 architecture: Moderate (~$50–150k for design and initial implementation)
– DTC Periodic Table scoping: Low (~$10–20k for capability audit)
– NIST IR 8356 V&V (regulated industries): High (~$100–300k for formal accreditation)
– Total first-year cost for manufacturing: ~$100–300k depending on regulatory requirements
Q: Which standard applies to digital twins of digital systems (e.g., a twin of a software service)?
A: ISO/IEC 30173 and DTC Periodic Table apply (they are domain-agnostic). ISO 23247 is explicitly for manufacturing physical assets, so it would require significant translation. NIST IR 8356 has emerging guidance for cyber twins (twins of IT systems and digital services); expect formalization by 2027.
The ISO 23247 Four-Domain Architecture Visual
See diagram arch_01.mmd for a detailed view of how the Observable Manufacturing Element, Digital Twin Engine, Digital Twin Synchronization Entity, and User Entity interact.
The DTC Capabilities Periodic Table Visual
See diagram arch_02.mmd for the six capability domains and representative services in each.
Standards Crosswalk: ISO 23247 ↔ AAS ↔ DTDL ↔ ISA-95
See diagram arch_03.mmd for how terminology and entities map across all four frameworks.
Domain Decision Tree: Choosing the Right Standard(s)
See diagram arch_04.mmd for a flow-based guide to standard selection by domain and scope.
Multi-Standard Reference Architecture
See diagram arch_05.mmd for three real-world examples:
1. AEC Twin (building): ISO 19650 (BIM base) + ISO 23247 concepts (operational systems)
2. Factory Twin (discrete manufacturing): ISO 23247 + AAS (asset metadata)
3. Smart City Twin (IoT ecosystem): DTC Periodic Table (capability scoping) + ISO/IEC 30173 (terminology)
Next Steps: Your Digital Twin Standards Journey
- Start with ISO/IEC 30173: Adopt the terminology contract immediately. Share the glossary with your team and vendors. (Week 1)
- Assess your domain: Is your use case primarily manufacturing (ISO 23247), built environment (ISO 19650), or multi-domain (DTC + ISO 23247)? (Week 2)
- Map your current architecture: Where are your OME, DTE, DTSE, UE equivalents today? What’s missing? (Weeks 3–4)
- Choose your primary standard: ISO 23247 for manufacturing, IEEE P2806 (when available) for energy, or DTC Periodic Table for agile scoping across domains. (Week 4)
- Plan your interoperability layer: Decide on data formats (AAS, DTDL, OPC UA) and synchronization protocols (REST, MQTT, gRPC). (Weeks 5–8)
- Build and validate: Use ISO 23247 implementation patterns and NIST IR 8356 V&V practices. (Months 2–12)
Related Reading
Deepen your understanding with our other reference-architecture guides:
- Asset Administration Shell AAS Industry 4.0 — How AAS submodels represent asset metadata and lifecycle
- Digital Twin Unified Namespace UNS — Building a unified data fabric across domain twins
- ISO 19650 BIM Digital Twins Construction — AEC-specific twins and lifecycle governance
- ISA-95 ISA-99 Standards — Manufacturing operations and cybersecurity alignment
- OpenUSD Industrial Digital Twins — 3D representation and simulation engines for visual twins
About This Article
This reference architecture was authored by Riju and last updated April 29, 2026. It reflects:
– ISO 23247 Parts 1–3 (stable as of 2024)
– ISO/IEC 30173:2023 (published, locked)
– DTC Periodic Table v1.1 and evolving 2026 updates
– NIST IR 8356 (2021, 2024 refresh)
– IEEE P2806 early drafts (expected finalization 2026–2027)
This article is maintained as a living reference. Standards updates and vendor implementations are tracked quarterly.
