Reconciling Models with the As-Built Machine
Hardware never matches the drawing exactly; measuring the real machine and updating the models keeps the digital twin honest.
The gap between design and hardware
A design specifies a machine, but fabrication and assembly introduce tolerances, so the built machine differs from the design in small but real ways. Coil positions, dimensions, and material properties all vary. A model that still describes the design, not the hardware, will predict the wrong behavior.
Measuring the as-built
- Metrology captures actual dimensions and component positions.
- Material tests record the properties of the parts actually used.
- Sensor calibrations tie measurements to physical units.
- Assembly records document what was built where.
Updating the models
These measurements update the digital twin so it reflects the machine that exists, not the one that was drawn. This reconciliation is a form of calibration using construction data, and it happens before first operation so the twin is accurate from the start.
Why it matters for control
Control and state estimation depend on the twin being right. A coil a few millimeters from its nominal position changes the field, and control tuned to the nominal machine will be slightly wrong. Reconciling the model to the as-built machine removes that error before it matters.
In the Kronos timeline
Construction of the Hyperion breeder begins Q2 2027, so as-built reconciliation is a defined step between construction and first tritium around 2030. It is where the design-phase models meet reality and become operational tools.
Feeding the flywheel
As-built data is the first turn of the build phase of the intelligence flywheel, and differences found here inform the design of later units through fleet learning.