The Digital-Twin User Interface
A digital-twin interface binds a live or simulated model of a machine to interactive views so users can inspect, query, and reason about state.
What a twin interface must do
A digital twin is a computational model kept in correspondence with a real or planned system. Its interface has to let a user move between a spatial view of the machine, the data attached to each component, and the models that predict behavior. The interface is where the model becomes usable knowledge rather than a database.
Linked spatial and data views
The central pattern is coordinated linking: selecting a component in the 3D scene filters the plots, tables, and documents to that component, and vice versa. This turns navigation into inquiry. See Coordinated Views for the mechanics.
- Every geometric part carries an identity so it can be selected, measured, and annotated.
- Measurements and physics values are shown in context, with units and provenance.
- The interface distinguishes design intent, simulation output, and (once built) measured data.
Levels of detail and access
A public build exposes overview geometry and vetted numbers; a private engineering build exposes full detail. The interface must enforce this split cleanly so that sensitive geometry never leaks into a public view. Rendering large geometry in a browser relies on WebGL and level-of-detail.
Honest state
Because the Kronos machines are simulated and not yet built, the twin interface labels every field as design or simulation output and never presents a modeled quantity as a measurement. Construction begins Q2 2027; until first hardware, the twin is a design instrument.
Interaction
Good twin interfaces reward exploration; see Interactive Exploration and 3D Navigation.