A moving 3D machine is not proof of live operation
Every motion needs an identified basis: feedback, interpolation or demonstration. When its evidence becomes invalid, use an agreed degraded state rather than implying live operation.
On this page5 sections
A continuously rotating 3D fan does not prove that the physical fan is running. Motion may come from operational feedback, interpolation between observations, or a demonstration loop. A digital twin delivery should identify the evidence behind each motion and stop presenting it as current fact when that evidence becomes invalid.
Three motion types need different interpretations
| Motion basis | What it can show | What cannot be inferred |
|---|---|---|
| Verified operating feedback | The source reported operation at the stated time | The animation speed equals measured speed |
| Interpolation between observations | A calculated intermediate position for continuity | Every frame was measured on site |
| Demonstration loop | A process or operating concept | The equipment is executing that process now |
Even if an interface says “running,” an animation should not imply an actual rotational speed when no speed measurement exists. Similarly, objects moving along a virtual conveyor may explain a workflow without proving that a particular order has reached that location. The distinction matters whenever operators use the display to make a decision.
Keep the conditions behind each animation
For every movement, record the object identifier, driving field, source, timestamp, quality, unit and missing-data behavior. The mapping from state to animation can be simple, but it should explain which values start, stop or invalidate the movement. A previously unknown enumeration value should not automatically be interpreted as running.
The OPC UA Part 4 value-status clause requires clients to check quality severity before using a value, with Bad indicating an unusable value. Good quality does not itself mean that equipment is moving. It concerns the usability of the supplied value; the business state still depends on the actual field and its agreed meaning.
Define the display after evidence expires
The application can stop motion while retaining “last known running,” switch to a neutral representation, or hide trajectories that depend on invalid data. Choose behavior according to the consequences of misunderstanding it and define the accompanying wording and time label. Freezing a model while leaving “live operation” beside it remains misleading.
An event-based state may legitimately remain unchanged for a long period. Absence of change alone does not establish invalidity. Check whether the source supplies heartbeat, refresh-time or validity information. Agree thresholds for the device and data contract rather than giving every object the same arbitrary timeout. The visible state should explain uncertainty without inventing a physical shutdown.
Do not perform backfilled history as current motion
Imagine that equipment runs, stops and runs again during a disconnection, and all three records arrive together after reconnection. The current scene should recover the current state using the agreed ordering and time rules. Historical transitions belong in an explicitly historical view. Rapidly playing them on the live screen can make users believe the equipment has just performed those actions.
Interpolation may also need a correction when a new observation arrives. Specify whether the interface may transition, jump or interrupt the estimated movement, and retain the fact that intermediate positions were estimated. Do not fill an unsupported interval with indefinite extrapolation. A visual position should not become an assumption for physical control without a separately assessed control system.
Accept the boundary between evidence and illustration
In an authorized test environment, supply running, stopped, invalid-quality, missing, stale, reordered and backfilled samples. Check that movement, text, timestamps and details agree. Then switch to demonstration mode and verify that its status is clear and it does not write simulated results into live business records.
Industrial Real-Time Data Integration and Acceptance: PLC, SCADA, MES, and IoT covers quality along the industrial data chain, and How to Accept a Digital Twin Project covers broader project acceptance. This part of digital twin development services (Chinese) concerns motion and the evidence it communicates; it adds no equipment-control or physical-simulation promise. Retain the source table and failure samples for each motion so that a later model-animation change can be checked again under the same conditions.