02 / Connected engineering

A digital twin needs synchronization, purpose and credibility.

A dashboard becomes a digital twin only when a fit-for-purpose digital representation remains meaningfully synchronized with an identifiable physical asset or process.

01Identifiable physical counterpart02Purpose-driven representation03Controlled synchronization04Validated decision logic
01

Define the observable element and purpose

Start with the physical asset, process or system being represented and the decisions the twin must support. The scope determines required signals, model fidelity, synchronization and authority.

  • Give each observable element a persistent identity.
  • Define diagnostic, predictive or control use cases separately.
  • Identify users, decisions and response time.
  • State where the twin has no authority.
02

Design the information path

The useful architecture connects sensing, edge processing, communication, contextualization, storage, models and applications. Data quality and asset context must survive every interface.

  • Record units, timestamps and quality status.
  • Associate telemetry with configuration and operating state.
  • Handle missing, late and contradictory data.
  • Preserve lineage from source signal to displayed decision.
03

Establish model credibility

A twin can contain physics models, statistical models, rules or combinations. Each model needs a stated validity range, calibration history and evidence appropriate to the consequence of its output.

  • Verify model implementation and transformations.
  • Validate against relevant operating behaviour.
  • Quantify uncertainty and detect invalid operating regions.
  • Monitor model and sensor degradation after deployment.
04

Close the lifecycle loop safely

Recommendations or commands flowing back to the physical system require explicit authority, interlocks, fallback behaviour and traceable change control.

  • Separate advisory, supervisory and autonomous modes.
  • Define human approval and safe-state behaviour.
  • Version models, rules and asset configuration together.
  • Measure whether interventions improve the intended outcome.
Use boundary

Apply the method to the decision—not as a checklist.

The appropriate evidence depends on intended use, technical risk, operating environment, contractual obligations and the authority responsible for acceptance. This guide is educational and does not replace project-specific analysis, applicable standards or independent review.

Primary references

Sources used for this guide.

01ISO 23247-1: Digital twin framework for manufacturingInternational Organization for Standardization02NIST: Digital Twins for Advanced ManufacturingNational Institute of Standards and Technology03NIST: Digital Twin StandardizationNational Institute of Standards and Technology