Digital Twin
The product, kept in step
The model that produced the hardware does not stop when the hardware exists. It stays live beside it.
What it holds
Four things a drawing cannot carry
A 3D model tells you the shape of a thing. A twin tells you why the thing is that shape.
Design intent, preserved.
Not just the geometry — the requirement each part was chosen to satisfy, and the trade-off that was made. The reason survives alongside the result.
Change, with its consequences visible.
Alter a requirement and you see what it touches. The question stops being “what else does this break?” and becomes a list you can read.
What was designed, beside what was built.
The twin holds the intended behaviour. When a real unit behaves differently, the difference is a comparison rather than an argument.
A record that outlives the project.
Two years later, someone who was not there can open the twin and understand why the product is the way it is.
The distinction
A 3D model is not a digital twin
The phrase gets used for anything that spins in a browser. A rotating model is a picture. It knows its own geometry and nothing else.
A twin knows what the product was supposed to do, which decisions produced it, and what it is doing now. That is three kinds of knowledge a picture does not have, and it is the difference between a demonstration and a working record.
The distinction matters commercially: a picture is made once and goes stale. A twin is worth more in year three than in month one.
The test
Ask what happens when a requirement changes. A picture does nothing. A twin tells you what is affected. If the answer is “nothing happens”, it is a picture.
Who it is for
Four people, one record
- The engineer who inherits it
- The team taking it to manufacture
- The people supporting it in the field
- The next version
Joins in month nine and needs to change something without breaking a decision nobody wrote down. The twin is the person who was there.
Needs to know which tolerances are real constraints and which were convenient choices. Those look identical on a drawing and different in a twin.
A unit misbehaves. They compare it to what it was designed to do rather than to what someone remembers it should do.
Version two starts from the reasoning behind version one instead of from its output. That is the difference between improving a product and redrawing it.
Questions
Straight answers
Is this just a 3D viewer?
No. Geometry is part of it. The rest is the requirement each part satisfies, the trade-offs made, and how the built product compares to the designed one.
Does it need our engineers to keep it updated by hand?
It is produced by the same work that produces the design, rather than maintained beside it. A twin that needs manual upkeep stops being true within weeks, which is why most of them do.
Can we export it?
Yes. Geometry leaves in neutral interchange formats and the record leaves as ordinary documents. Nothing needs our software to read.
Who can see our twin?
Your project is yours. Access is set out in the agreement you sign before onboarding, and you read it before you commit to anything.
See it on a product you know
Bring something you have already built. Comparing the twin to a product you understand is the fastest way to judge whether this is useful.