humanoidsdata.com

Search

Search datasets, articles, and glossary terms for humanoids and embodied AI.

← All glossary terms

Simulation & transfer

Digital twin

A digital twin is a fit-for-purpose digital representation of a specific physical robot, asset or process that is kept synchronised with its real counterpart through operational data. It may contain geometry, dynamics and simulation models, but the maintained link to an identified real system distinguishes it from an ordinary, standalone simulator.

Updated

ISO 23247-1 defines a manufacturing digital twin around a fit-for-purpose representation and synchronisation with an observable physical element. Applied to robotics, the represented element might be one identified robot, its workcell or a deployed process. Sensor readings, calibration results, controller logs and maintenance records can update the representation at a cadence suited to its purpose.

The twin may combine a robot description, scene geometry, kinematics, dynamics, software state and learned models. It does not need to reproduce every property of the physical system. “Fit for purpose” means that a collision-checking twin and a predictive-maintenance twin can legitimately contain different information.

How it differs from a simulator

An ordinary simulator can model a generic robot or an imagined environment without corresponding to any particular physical instance. A digital twin has an identity relationship with a real counterpart and a maintained data path that keeps relevant properties aligned.

Simulation can therefore be one capability inside a twin, but simulation alone is insufficient. A static CAD model or one-off scene copy is better described as a digital model unless it is synchronised with the real asset for a defined use.

Robotics uses and limits

Digital twins can support calibration, monitoring, virtual commissioning, fault analysis and testing proposed controller changes. NIST's ISO 23247 use cases illustrate how operational data, modelling and simulation can be combined for machine health, scheduling and virtual commissioning.

Synchronisation does not guarantee physical fidelity. Unmodelled contact, wear, sensor noise or latency can still make predictions wrong, so claims about a twin should state what is updated, how often and against which real measurements it has been validated.

Sources