Types of Digital Twins: A 2026 Technical Taxonomy
Last Updated: November 2026
Most articles on the types of digital twins hand you a flat list (component, asset, system, process) and stop, as if one dimension could classify a technology that spans a bearing’s stress field and an entire logistics network. That framing quietly misleads buyers. A team that wants a predictive-maintenance twin ends up with a 3D viewer, and a team that wants closed-loop optimization ends up with a dashboard, because the vocabulary never told them which question they were really answering.
A more useful view treats every twin as a point in a four-axis space: scope, lifecycle phase, integration level and fidelity. Each axis maps to a real decision, a real cost and a real governance burden. The integration axis in particular decides whether you are building a model, a shadow or a true twin, and it is the axis most vendor material blurs.
You will leave with a placement method for any twin on all four axes, a mapping to ISO 23247, ISO/IEC 30173 and Digital Twin Consortium language, and a decision tree that selects a type from a use case rather than a vendor pitch.
What this covers: the scope hierarchy, the lifecycle and digital-thread axis, the Model, Shadow, Twin integration ladder, the fidelity spectrum, how the axes combine, a worked selection example, failure modes and a checklist.
Context and Background
The phrase “digital twin” has been stretched until a CAD viewer and a closed-loop controller can both wear it. The concept’s engineering lineage runs through product lifecycle management and aerospace simulation work in the 2000s and 2010s; I have not re-verified the exact first-use attributions here, so treat origin stories as folklore unless you check the primary papers. What matters for a taxonomy is that the field later acquired usable vocabulary from three directions.
The first is the academic data-flow classification. Kritzinger and colleagues, in the 2018 IFAC-PapersOnLine paper “Digital Twin in manufacturing: A categorical literature review and classification”, separated a Digital Model, a Digital Shadow and a Digital Twin purely by whether data flows between the physical and digital object manually or automatically, and in one or both directions. The second is standards. ISO 23247 (“Automation systems and integration — Digital twin framework for manufacturing”) was published in four parts in 2021. Part 1, “Overview and general principles”, appeared on 22 October 2021, and the series gives manufacturing a reference architecture built around the observable manufacturing element (OME), the thing being twinned. ISO/IEC 30173:2023, “Digital twin: Concepts and terminology”, published on 8 November 2023, adds cross-domain terminology and explicitly covers types, life cycle and stakeholders in its 28 pages.
The third direction is consortium and policy work. The Digital Twin Consortium defines a digital twin as an integrated, data-driven virtual representation of real-world entities and processes, with synchronized interaction at a specified frequency and fidelity. The US National Academies report on digital twins, released in December 2023, insists on bidirectional interaction between virtual and physical and on built-in verification, validation and uncertainty quantification (VVUQ). Note what both definitions share: synchronization frequency and fidelity are parameters, not afterthoughts.
None of these sources, alone, tells you whether you need a part twin or a process twin. Scope is one axis, integration another, and each author picked one and presented it as complete. A vendor streaming telemetry to a dashboard describes twins by scope and omits that everything it sells is a shadow. A standards body focused on data flow barely discusses fidelity. For a standards walk-through see our guide to ISO 23247, ISO/IEC 30173 and DTC standards, and for the capability-oriented view the Digital Twin Consortium reference architecture and periodic table. The combination across axes is what a builder has to decide, and that is what this taxonomy supplies.
Two clarifications before the axes. First, a “type” here describes a design position, not a product category. One deployed system can hold different positions at different moments: an asset twin that is a shadow during commissioning and becomes advisory once its model is validated. Second, the axes are not independent. Raising integration from shadow to closed-loop twin forces a higher fidelity and a verification case, which is why the cost grows non-linearly along a diagonal of the space rather than along any single axis.
The Scope Axis: From Component to Enterprise
On the scope axis, digital twins come in five tiers: component or part, asset or product, system or unit, process, and enterprise or system of systems. The tiers differ in how much physical reality the twin represents, from one engineered element up to an interacting network of assets and workflows, and each tier up roughly multiplies integration effort.

Figure 1: The scope hierarchy. Each tier aggregates the ones below it; higher tiers contextualize lower ones rather than replacing them.
The hierarchy is compositional. A bearing twin is a building block of a pump twin, which is a node in a pumping-station twin, whose behavior feeds a water-treatment process twin, all rolled into a utility-network twin. Higher tiers do not replace lower ones; they aggregate them. The practical consequence is that you rarely buy “a” twin. You assemble a stack, and the question is which tier carries your decision.
Component and asset twins
A component twin models one engineered element: a turbine blade, a battery cell, a circuit board. Its job is high-fidelity physics on a narrow boundary, such as fatigue, thermal stress or electrochemical degradation. The narrow boundary is the reason it can afford finite-element or electrochemical models that would be impossible plant-wide. The price is blindness to everything outside the boundary. A cell twin tracking state of health from impedance and temperature knows nothing about the pack’s cooling; our battery management system architecture post shows how cell-level estimators sit inside a pack-level one.
An asset twin steps up to a complete functional unit: a pump, a wind turbine, a CNC machine, a vehicle. It composes component models and adds the asset’s own control behavior. This is the tier most predictive-maintenance products target because an asset is the natural unit of ownership, warranty and maintenance contracts. Instrumentation differs sharply between the two. A component twin needs deep, specialized sensing on one boundary, such as strain gauges at a blade root. An asset twin needs broad sensing across the machine and a model of how parts interact under load.
A perfect set of component twins does not give you an asset twin. Emergent behavior, such as resonance between gearbox and tower or thermal coupling between motor and bearing, lives in the interactions, not in the parts. That emergence is why scope is a real axis and not merely a zoom level. It also explains why asset twins are commonly standardized through submodel catalogs; the Asset Administration Shell and its submodels are the most mature attempt at giving an asset twin an interoperable identity.
System and process twins
A system or unit twin represents many assets working toward a shared function: a wind farm, a production line, a building’s HVAC plant. Value moves from any single asset to the interactions, such as load sharing across turbines or bottlenecks on a line. It can answer “which asset should we throttle?”, a question no asset twin can see.
The engineering challenge changes character here. At the asset tier the hard part is physics; at the system tier it is semantics and synchronization. The twin must ingest from heterogeneous asset twins, often from different vendors and protocols, and reconcile them into one consistent state with a shared clock, coordinate frame and meaning. A wake-steering optimizer that receives each turbine’s yaw and wind reading misaligned in time will fight itself. Our post on event-time alignment and late-arriving sensor data covers the mechanics.
A process twin shifts the unit of analysis from things to flow. It models order-to-delivery, a chemical reaction sequence or a patient pathway, and optimizes throughput, yield and timing rather than machine health. Its native tooling is discrete-event simulation, queueing theory and constraint solvers rather than finite-element analysis or CFD. The same line can host an asset twin (is this filler healthy?) and a process twin (is order flow efficient?), and they rarely share a model. Conflating them is a frequent source of failed projects: the process twin’s accuracy is limited by how well it represents the resource states that the asset twins estimate, which is an interface to design, not an assumption.
Enterprise and system-of-systems twins
The top tier spans organizations or networks: a supply chain, a city, a utility grid, a fleet. Fidelity is deliberately coarse, since modeling every bolt in a city is neither possible nor useful. What the tier needs is federation: identity, ontology and governance across owners who do not share a database. Ontology work such as Brick Schema with RDF and SHACL matters more here than any solver. A sober observation from practice: the enterprise tier is where many programs stall, not for technical reasons, but because no one owns the cross-boundary model.
What each tier typically needs (illustrative)
| Tier | Boundary | Typical model | Dominant difficulty | Typical update cadence (illustrative) |
|---|---|---|---|---|
| Component | One element | FEA, electrochemical, empirical wear | Parameter identification | Seconds to hours |
| Asset | One machine | Multi-physics plus control logic | Interaction effects | Seconds to minutes |
| System | Line or plant section | Network or agent models | Semantics, time alignment | Seconds to minutes |
| Process | Workflow | Discrete-event, queueing, solver | Resource-state accuracy | Minutes to days |
| Enterprise | Many owners | Graph plus coarse simulation | Governance, federation | Hours to weeks |
The cadence column is illustrative of common practice, not a measured benchmark; your own latency requirement should come from the decision, a point developed in the selection section below.
The Lifecycle Axis and the Digital Thread
The lifecycle axis asks when in the physical object’s life the twin is useful. A design twin supports requirements and architecture trade-offs before anything exists, a validation twin supports virtual commissioning, an operational twin tracks the live asset, a maintenance twin forecasts degradation, and an end-of-life twin informs reuse and recycling. Many vendors treat only the operational phase as “the” twin, which discards most of the lifecycle value.

Figure 2: Lifecycle phases of a twin. The digital thread links the phases, and field data flows back to design as the feedback that makes the whole loop pay.
Two distinct things share the word “twin” across phases. Prototype-phase twins model a type, the design of all units that will be built. Operational twins model an instance, one serial-numbered machine with its own wear history and calibration. The type-versus-instance distinction is the most common gap in implementations: teams build an excellent type model, then discover they have no mechanism to bind it to instance data such as as-built configuration, firmware level and service history.
The digital thread as connective tissue
The digital thread is the traceable chain of data linking a product’s requirements, design, manufacturing, operation and service. It is not a separate twin; it is the identity-and-lineage substrate that lets one phase’s twin be reused by the next. Practically it is a set of keyed links between PLM (product lifecycle management), MES (manufacturing execution), ERP and operational data stores. Our digital twin and MES reference architecture shows one concrete linkage.
Why it matters for taxonomy: without the thread, each phase’s twin is a fresh build, and the lifecycle axis collapses to a sequence of disconnected projects. With it, a validation twin’s model parameters seed the operational twin, and operational failure modes feed back into the next design generation. That feedback arc in Figure 2 is where the compounding return comes from, and it is rarely costed in business cases because it pays off a product generation later.
Phase-specific fidelity and data
Each phase has a different data regime. Design twins run on synthetic and requirement data and tolerate coarse models because the goal is ranking alternatives. Validation twins need accurate controller and plant models because the point is to catch integration defects before hardware exists; tools for this commonly rely on standards such as FMI for model exchange, and the co-simulation master algorithms post explains where numerical stability bites. Operational twins live on streaming data and must handle gaps and drift. Maintenance twins need labelled failure history, which is chronically scarce, pushing teams toward physics-informed or hybrid models rather than pure machine learning.
The Integration Axis: Model, Shadow, Twin
On the integration axis, three types are distinguished by data flow. A digital model has no automatic data exchange with the physical object. A digital shadow receives automatic data from the physical object but pushes nothing back. A digital twin exchanges data automatically in both directions, so the digital state can drive a change in the physical one.

Figure 3: The integration ladder after Kritzinger et al. The distinguishing feature is the direction and automation of data flow, not the sophistication of the model.
This is the most consequential axis, because it determines safety exposure, cybersecurity surface and engineering cost. A model is a document that happens to execute. A shadow is a read-only mirror: if it is wrong, someone makes a bad decision, but nothing acts on its output without a human. A twin closes the loop: if it is wrong, something moves.
Where the word “twin” is overused
In practice, most products marketed as digital twins are shadows. Telemetry flows up; dashboards and alerts flow to people; people decide. That is valuable, and a shadow is often the right answer, but calling it a twin sets the wrong expectation about autonomy, validation effort and cost. The Digital Twin Consortium wording and the National Academies definition both require interaction between the virtual and the physical, and the latter requires VVUQ, which many shadows never do. Our myth-checking post on the real-time connection claim takes the same stance from the latency angle.
A useful nuance: “bidirectional” does not have to mean autonomous. The return path can be a recommendation a human approves (an advisory twin), a setpoint written within bounded limits (a supervised twin), or unattended actuation (an autonomous twin). Splitting the top rung into these three gives the practical ladder you will actually budget against:
- Digital model. Offline simulation or CAD. Cost is mostly modeling labor.
- Digital shadow. Adds data acquisition, ingestion, and state synchronization. Cost grows with sensor count and data quality work.
- Advisory twin. Adds a decision layer and a human approval path. Cost adds integration to work-order or control-room tooling.
- Supervised twin. Adds bounded write-back with guardrails. Cost adds safety analysis and rollback.
- Autonomous twin. Adds unattended closed-loop control. Cost is dominated by verification, validation and assurance.
The jump between rungs 2 and 3 is cheap relative to the jump between 4 and 5, which is why autonomy should be earned. An agentic layer on top of a twin, as discussed in our post on agentic digital twins, makes rungs 3 to 5 easier to build and harder to trust, so the verification burden rises with the convenience.
What synchronization actually requires
Moving from model to shadow is not “connect a sensor.” The twin needs a state estimate, not raw readings. Sensors are noisy, sparse and sometimes lying; the twin’s internal state (a temperature field, a wear level, a tank inventory) must be inferred. That is the domain of observers and filters, covered in Kalman filter versus particle filter and EnKF for twin synchronization. A shadow that simply plots sensor values is a monitor. A shadow that maintains an estimated state with uncertainty is the minimum credible foundation for anything above it on the ladder.
The Fidelity Axis: How Wrong Can It Be
Fidelity is the degree to which the twin reproduces the physical counterpart’s behavior, and it should be set by the consequence of the decision, not by what the modeling tool can do. The spectrum runs from descriptive (geometry and metadata), through empirical and statistical models, to reduced-order surrogates, to full physics-based models, and finally hybrid physics plus data models that are continuously recalibrated.
Higher fidelity is not automatically better. A high-fidelity model costs more to build, more to run, more to calibrate and more to validate, and it can be slower than the process it mirrors. A twin that computes a plant-wide CFD solution in six hours cannot support a decision needed in six minutes. The correct question is the smallest model whose error is acceptable for the decision, with that acceptance made explicit.
The five practical fidelity bands
| Band | What it reproduces | Typical technique | Best for |
|---|---|---|---|
| Descriptive | Structure, geometry, metadata | CAD, BIM, asset registry | Navigation, inventory |
| Empirical | Input-output correlation | Regression, ML on history | Anomaly detection, forecasting in-distribution |
| Reduced-order | Dominant dynamics, fast | POD, surrogates, lumped models | Real-time estimation and control |
| Physics-based | First-principles behavior | FEA, CFD, multi-body, Modelica | What-if outside observed data |
| Hybrid | Physics plus learned residual | Grey-box, PINN, recalibrated | Long-lived assets with drift |
Reduced-order models deserve emphasis because they bridge offline physics and online use. A full model is calibrated and trusted offline, then distilled into a fast surrogate that runs at the twin’s update rate; the reduced-order and surrogate models post covers POD and physics-informed neural networks. A pure empirical model, by contrast, interpolates well and extrapolates poorly: it will confidently mispredict a regime it never saw, which is precisely where a what-if twin is wanted.
Fidelity needs a credibility argument
Because the National Academies definition makes VVUQ integral, fidelity is not claimed, it is demonstrated. The ASME V&V 40 approach scales the evidence required to the model’s risk: the more a decision depends on the model and the worse the consequence of error, the stronger the credibility evidence. Our post on V&V 40 credibility evidence and fidelity levels works through this, and the companion piece on verification, validation and uncertainty quantification covers the methods. The taxonomy implication: fidelity and integration are coupled by risk. An advisory twin with a human checking each recommendation can live with a moderate-fidelity model; an autonomous twin cannot. For the business side, the maturity model and ROI framework ties these levels to expected return.
How the Four Axes Combine
Each axis is a separate question, and a complete description of a twin gives all four answers. Writing the four-tuple down is the single most effective hygiene step in a twin program, because it exposes mismatches that a product name hides. Consider three illustrative cases, labelled as constructed examples rather than reported deployments.
| Twin | Scope | Lifecycle | Integration | Fidelity |
|---|---|---|---|---|
| Pump bearing health monitor | Component | Operate and maintain | Shadow | Empirical, hybrid later |
| Line virtual commissioning model | System | Validate | Digital model | Physics-based |
| Building HVAC supervisory optimizer | System | Operate | Supervised twin | Reduced-order plus empirical |
| Fleet-level supply network planner | Enterprise | Operate | Advisory twin | Descriptive plus coarse simulation |
Read the table for mismatches. The virtual-commissioning model is a “digital model” on the integration axis, yet vendors routinely sell it as a twin; that is fine as long as the buyer knows nothing will be live. The HVAC optimizer is the interesting case: supervised write-back means a defensible safety case and bounded setpoints, not just a good model. And the supply-network planner has the coarsest fidelity but the widest scope, which is correct for its decisions.
Mapping to standards language
Placing your four-tuple against standards helps when writing requirements or procurement language. ISO 23247 is manufacturing-specific and is most naturally a scope-and-integration reference: its architecture identifies the observable manufacturing element, data collection and device control on the physical side, and the digital twin entity and its services in between, which implies the bidirectional exchange of a full twin. ISO/IEC 30173:2023 provides cross-domain terminology including types, so use it to define terms in a contract. The DTC periodic table of capabilities is capability-oriented and useful for checking which functions (data services, integration, intelligence, UX, management, trustworthiness) a candidate system actually provides. I recommend not claiming “ISO 23247 compliant” unless you have checked the precise parts and clauses against the text; the standards are reference frameworks and compliance claims vary in what they mean.
Two axes people forget
Two further dimensions sometimes appear, which I treat as secondary rather than primary. The first is the domain (manufacturing, building, grid, health, city); it changes vocabulary and standards but not the structural placement. The second is the time basis: a twin can be real-time, near-real-time or batch-synchronized, and it can look backward (replay), forward (prediction) or sideways (what-if scenario). Time basis is a property you derive from the decision latency, not a separate type, and I fold it into fidelity and integration when sizing.
Choosing a Type: A Decision-First Selection Framework
Select by starting from the decision the twin will inform, working through four questions, and stopping at the cheapest type that answers it. Does the decision repeat and carry cost? Does it need live state? Does an action close the loop? Does the physics matter enough that an empirical model will not do?

Figure 4: A decision-first selection tree. Each “no” exits to a cheaper type; only a repeated, costly, live, loop-closing decision justifies a verified twin.
The tree’s first exit is the most important and the least used. If the decision is rare or cheap, build neither a twin nor a shadow; use ordinary analytics or a spreadsheet. A twin is an ongoing operating cost (data pipelines, model recalibration, ontology upkeep), so it needs a recurring decision to amortize against.
A worked example
Take a mid-sized food plant with a batch pasteurizer line that occasionally overshoots temperature, causing product loss. All numbers below are illustrative.
Step 1, the decision: whether to adjust holding time and steam valve position per batch. It repeats several times per shift, and an overshoot costs product and risks a hold, so it passes the first test. Step 2, live state: yes, because the right adjustment depends on current inlet temperature and flow. Step 3, close the loop: the plant’s quality system requires an operator to approve changes to critical process parameters, so the loop closes through a human. That points to an advisory twin, rung 3 on the ladder, not an autonomous one.
Step 4, physics: the heat-exchange dynamics are well understood and the plant has two years of historian data across seasons. A reduced-order thermal model plus a residual correction learned from history fits. The four-tuple is therefore: system scope (the pasteurizer unit), operate phase, advisory integration, reduced-order hybrid fidelity. The team can now estimate the build: an estimator for fluid temperature (see the state-estimation post), a surrogate, a recommendation service and an approval screen. They skip the 3D visualization the vendor demo led with because no decision uses it. That is the point of the framework: it removes components, not only adds them.
Procurement questions that follow from the tuple
Turn the four-tuple into questions for a vendor. What is the integration level, and where precisely does the write-back path go? Which phase and which instance data does the model bind to? What is the validated error bound, on what data, and how is drift detected? What scope boundary does it stop at, and how does it exchange state with the tiers above and below? Vendors who answer in terms of dashboards and “AI” rather than these terms are selling a shadow.
Trade-offs, Gotchas, and What Goes Wrong
The taxonomy exposes failure modes that a flat list hides. Most trace back to a mismatch between axes, so they are easiest to catch at the design review.
Integration claimed, shadow delivered. The product is sold as a closed-loop twin but only streams data to screens. The failure appears as an unmet autonomy expectation and, worse, as a safety case that was never written because nobody thought anything acted. Name the write-back path in the requirements, or state that none exists.
High fidelity, low integration. A beautifully calibrated physics model sits offline because nobody built the data path, so it answers last quarter’s questions. The mirror failure is low fidelity with high integration: an empirical model drives write-back and fails outside its training regime. Because risk couples the two axes, close the gap on whichever side lags.
Instance blindness. The type model is excellent, but the twin cannot tell unit 14 from unit 15, so it applies fleet-average wear to a machine with a rebuilt gearbox. The cure is identity management and as-built configuration in the digital thread; asset identity standards such as the Asset Administration Shell help here.
Scope creep upward. Teams start with an asset twin and keep adding neighboring assets until they have an accidental system twin without a data contract, a shared clock or an owner. Integration cost rises faster than value. Promote scope deliberately, with an interface agreement at each boundary.
Synchronization drift. Sensors recalibrate, firmware changes sampling, a valve is replaced. The twin keeps running with a silently wrong state. Monitor the residual between twin prediction and measurement as a first-class health signal, and treat a growing residual as a recalibration trigger, not a curiosity.
Cost asymmetry. The up-front build is visible and budgeted; the recurring cost of model upkeep, ontology maintenance and re-validation is not. Plan for it explicitly. A rule I use, which is opinion rather than a measured benchmark, is that a twin without a named owner and a recalibration budget is already decaying.
Security surface grows with integration. A model has almost no attack surface; a shadow adds an outbound data path; a twin with write-back adds an inbound control path, which is an operational technology security issue. Do not inherit shadow-grade security for a twin-grade function.
A final limit on the taxonomy itself: it is a design aid, not a certification scheme. Boundaries blur, since a supervised twin that auto-applies changes under a threshold is partly autonomous, and different authors split the integration ladder differently. Use the axes to force explicit decisions, not to win a classification argument.
Practical Recommendations
Start from the decision, not the technology. Write the four-tuple of scope, lifecycle phase, integration level and fidelity band for every proposed twin, and reject any proposal that cannot state all four in one line. Build the cheapest type that serves the decision, and make promotion between rungs a deliberate, reviewed event.
Treat the shadow as the foundation. A well-instrumented shadow with a proper state estimator and uncertainty is useful in itself and is a prerequisite for everything above it. Many programs should stop here for a year and collect residual data before adding a return path. When you do add write-back, begin with an advisory path and a human approval, measure the acceptance rate of recommendations, and move to bounded autonomy only when evidence supports it.
Tie fidelity to risk and write the credibility argument down. Reduced-order surrogates are usually the right online model, with the full physics model kept offline for calibration and what-if work. Plan the digital thread early, since retrofitting identity and as-built binding is expensive.
A short checklist for your next design review:
- [ ] The decision the twin informs is named, with its frequency and cost of error.
- [ ] Scope tier and boundary are stated, with interface agreements to adjacent tiers.
- [ ] Lifecycle phase is stated, and type versus instance binding is defined.
- [ ] Integration level is stated, and the write-back path (or its absence) is explicit.
- [ ] Fidelity band and acceptable error bound are stated and tied to a validation plan.
- [ ] A state estimator, residual monitoring and recalibration trigger exist.
- [ ] An owner and a recurring budget are named.
- [ ] Terms in the contract follow ISO/IEC 30173, and any ISO 23247 claim cites specific parts.
Frequently Asked Questions
What are the main types of digital twins?
The most common listing is by scope: component or part, asset or product, system or unit, process, and enterprise or system of systems. That list describes only one dimension. A complete classification also records lifecycle phase (design, validation, operation, maintenance, end of life), integration level (model, shadow, twin) and fidelity (descriptive through hybrid physics plus data). Describing a twin with all four attributes avoids buying the wrong type for a use case.
What is the difference between a digital model, a digital shadow and a digital twin?
The difference is data flow, following Kritzinger et al. (2018). A digital model exchanges data with the physical object manually or not at all. A digital shadow receives data from the physical object automatically but sends nothing back. A digital twin exchanges data automatically in both directions, so the digital state can influence the physical object. Many products marketed as twins are, strictly, shadows.
Is a digital twin the same as a simulation?
No. A simulation is a model you run on chosen inputs, usually offline. A digital twin is bound to a specific physical counterpart and kept synchronized with it, at a stated frequency and fidelity, so its state reflects the real object now. A twin typically contains simulation models, but the synchronization and the link to a real instance are what make it a twin. Our post on digital twin versus simulation covers the decision in depth.
Which standards define digital twin types?
ISO/IEC 30173:2023 gives cross-domain digital twin concepts and terminology, including types and life cycle. ISO 23247, published in four parts in 2021, defines a digital twin framework for manufacturing with a reference architecture. The Digital Twin Consortium supplies a definition and a capabilities-based periodic table. None is a complete taxonomy alone; use them together and cite specific clauses rather than claiming blanket compliance.
How do I choose the right type of digital twin?
Start from the decision. Ask whether it repeats and costs enough to justify a recurring system, whether it needs live state, whether an action closes the loop, and whether physics matters or empirical models suffice. The answers lead to a model, a shadow, an advisory twin or an autonomous twin. Choose the lowest integration rung and smallest fidelity band that meet the decision, and promote only with evidence.
Do I need a high-fidelity physics model for a digital twin?
Not necessarily. Fidelity should match the consequence of the decision. For anomaly detection within observed operating ranges, an empirical model may suffice. For real-time control, a reduced-order surrogate is usually the practical choice. Full physics models earn their cost for what-if analysis outside observed data and for calibrating surrogates. Whatever the choice, document the error bound and how the model was verified and validated.
Further Reading
- Digital twin standards: ISO 23247, ISO/IEC 30173 and the Digital Twin Consortium
- Digital twin versus simulation: an architecture decision
- Digital twin maturity model, fidelity levels and ROI framework
- Digital twin pillar overview
- ISO/IEC 30173:2023 Digital twin: Concepts and terminology (catalog record)
- Digital Twin Consortium: definition of a digital twin
- National Academies: Foundational Research Gaps and Future Directions for Digital Twins
By Riju — about

Pingback: Power Grid Digital Twin: CIM, CGMES and State Estimation