Skip to content

SMART Measuring Instruments · Story

From the admin shell to the SMART twin

Industry already has a digital-twin interface idea: the asset administration shell, an API to a device. But a command surface is not a twin — it answers "what can I ask this device to do?" and nothing about "what is this device, and does it still hold its certified type?" The gap is the difference between remote control and legal metrology.

The SMART Measuring Instrument takes the other path: the twin is the instrument's model, live. The Recommendation declares what it governs of an instrument — its identity, its metrological characteristics, its indication process — and the twin serves exactly that surface, in the Recommendation's own vocabulary. A load cell's twin serves the indication a calibrated weight produces; a gas analyzer's twin serves each channel's concentration. The twin is a tailored projection of whatever fuller twin the manufacturer runs, and the Recommendation's model is what makes the projection certifiable.

Why a projection, not the whole twin

A manufacturer's full digital twin may simulate, predict, and decorate far beyond the Recommendation. Legal metrology needs a smaller, harder surface: what the Recommendation measures, at the uncertainty it allows, with the provenance it demands. The SMART twin is that surface — declared per Recommendation, so an evaluator anywhere in the world reads the same registers with the same meaning.

Simulation included

Because the twin's surface is standardized, it can be simulated honestly: the SST for Measuring Instruments simulates SMART twins for training and development, with realistic physics. Testers learn the workflow without hardware; developers integrate without a lab.

The SMI documentation walks each surface →