Your MES is already a digital twin

I've been saying this for years: MES is a digital twin.

Not in the glossy, 3D-rendered, walk-through-the-factory-in-VR sense that gets shown at trade shows. In the sense that actually matters for running a factory.

What is a digital twin?

A digital twin is a virtual representation of a physical asset, process or entire factory, kept in sync with the real thing through live data.

There are different flavours. A twin of a single machine, used by engineers to model wear or tune performance. A twin of a production process, used to test changes before making them. A twin of a whole factory, used to plan layouts, capacity and investments.

What they share is the idea of a live, accurate digital picture of something physical.

Why MES/MOM already is one

Think about what a well-implemented MES/MOM knows at any moment:

• Every line and machine, and its current state: running, stopped, in changeover
• Which order is running where, and how far through it is
• Every lot of material, where it is, what state it's in and what it was made from
• Every quality result, linked to the product and process conditions at the time
• The condition and maintenance status of each asset
• Who is working where, and what they're qualified to do

That's a live digital representation of the operational factory. It's updated in real time from the equipment and the people. It's the closest thing most manufacturers have to a twin, and they often don't think of it that way.

What MES/MOM doesn't do on its own

Where a full digital twin goes further is simulation.

Running what-if scenarios before you change anything in the real world:

• What happens to throughput if we add a second shift on Line 2?
• Where's the new bottleneck if we speed up the filler by 10%?
• Should we buy another press, or fix the changeovers on the ones we've got?
• What does next month's schedule look like if this order slips a week?

That's where I find the future genuinely exciting. Data-driven decisions about investments, layouts and schedules, tested virtually first, instead of argued over in a meeting.

Simulation is only as good as the data behind it

Here's the catch. A simulation built on assumed cycle times, estimated downtime and a theoretical capacity model will give you very confident, very wrong answers.

The value comes from a twin that's fed by reality. Actual cycle times by product. Actual downtime patterns by machine and shift. Actual scrap rates. Actual changeover durations.

Which brings us back, again, to the data foundation. MES/MOM, historians, connected equipment and data platforms feeding a live, accurate picture. Build that, and simulation becomes trustworthy. Skip it, and your twin is a very attractive guess.

Don't buy a twin before you have the data

I'm wary of digital twin projects that start with the visualisation. The 3D model looks impressive in the boardroom. But if the data behind it is typed in at the end of each shift, it's a nice picture of a factory that doesn't really exist.

Start with the operational twin you probably already need: MES/MOM capturing what's actually happening, accurately and in context. Then add simulation on top, aimed at a real decision you need to make.

Is there a decision coming up in your factory that you'd love to test virtually before committing to it?