The field manual for machine learning in manufacturing · updated September 1, 2026
ManufacturingML
Home / Encyclopedia / Digital twin
Foundations · Entry · updated September 1, 2026

Digital twin

Key takeaways
  • A digital twin is a live, data-fed model of a physical asset, line or plant: from simple contextualized data models to full predictive simulations.
  • Most value in 2026 comes from the middle of the ladder: process twins that predict quality and yield from live variables.
  • Full simulation twins pay at enterprise scale and design time; plant-level quick wins come from lighter learned models.
  • 'Twin' is the most abused word in industrial software: always ask what is actually modeled, from what data, updated how often.

A digital twin is a model of something physical (a machine, a line, a whole plant) kept alive with real data. The term covers a maturity ladder, and knowing which rung a vendor sells is most of the evaluation.

The ladder

Rung 1 (the contextualized data model: every sensor, machine and line mapped into one coherent structure. Not glamorous; the foundation everything else stands on, and the product of the data-platform vendors. Rung 2) the learned process twin: statistical/ML models that predict outcomes (quality, yield, energy) from live process variables and answer “what happens if I change this setpoint?” within the envelope of historical data. This is where optimization value concentrates. Rung 3 (the simulation twin: physics-based models that can answer questions outside historical experience) new layouts, new products. Powerful at design time and enterprise scale; heavy to build and maintain.

When it pays

The pattern in published results: rung-2 twins pay at single-plant scale within an optimization program; rung-3 twins pay when design decisions are expensive and repeated (new lines, network planning). Buying rung 3 to solve a rung 2 problem is one of the classic ways industrial AI budgets die.

FAQ

Is a digital twin the same as a simulation?
A simulation is one kind of twin (rung 3). Most working 'twins' in plants are learned models fed by live data, no physics engine involved. What matters is whether the model answers the questions your program needs at the accuracy the decision requires.
What do we need before a digital twin?
Connected, contextualized data: historian or equivalent, with tags mapped to physical meaning. If that layer is missing, the twin project becomes a data-plumbing project with a fancier name.
Related entries
Comparing platforms that do this? The adoption data pack carries the market numbers behind this entry.
From theory to signals
Which machine signals become which features, and how each breaks
Free, no login. One follow-up from TEEPTRAK, then nothing.
Get the mapping kit →

Digital twin in manufacturing: what it is, what it needs and what it is not

A digital twin in manufacturing is a model of a machine, line or plant kept synchronized with live shop-floor data, so the model shows the current state and predicts the effect of a change in setting, schedule or layout. Digital twin manufacturing projects succeed when the twin is built for one recurring decision and fed by data the plant already trusts.

This entry goes past the definition: which twin type matches which plant question, the data each type needs, a worked digital twin example on a bottling line, the pitfalls that turn twin projects into data-plumbing projects, and a scoping checklist a production or continuous-improvement team can use before talking to any vendor.

Key takeaways

  • Choose the digital twin type from the plant question, not from the technology on offer.
  • Machine states with reasons, measured cycle times and aligned process data come before any model.
  • A twin earns trust only after a back-test against measured shifts.
  • Flow twins often reveal that recovery rate, not buffer size, limits a line.

Which type of digital twin does a plant actually need?

The right twin is chosen from the question, not from the technology. A plant that starts by asking which decision the twin must improve usually ends with a smaller, cheaper and more useful model.

Question the plant asksTwin typeData it needs
Where and why did the line lose time last week?Data twin: contextualized model of the lineMachine states, stop reasons and counts mapped to the asset hierarchy
Which setpoints give the best yield on this product?Process twin: learned modelProcess parameters aligned with quality results per batch or per part
What if the buffer grows or a station runs faster?Flow twin: event model calibrated on real stopsStop durations and intervals, cycle times, buffer capacities
Will a new product or layout fit the line?Simulation twin: engineering modelEquipment specifications, layout drawings, process physics

A flow twin is a discrete-event model of material moving through a line that replays the stops, cycle times and buffers actually recorded on that line. Flow twins sit between the learned process twin and the full simulation twin, and they answer the most common capacity questions a plant manager faces.

What a digital twin is not

  • A 3D model without live data is a visualization, however realistic it looks.
  • A dashboard shows the current state but cannot answer a what-if question.
  • A one-off simulation run built for a project and never updated is a calculation, not a twin.

What data does a digital twin need from the shop floor?

Every twin type rests on the same base: events that are timestamped, attached to the right asset and explained. The ISA-95 equipment hierarchy (enterprise, site, area, work center, work unit) is the usual structure for attaching each signal to its asset, so that a stop on a labeler is never confused with a stop on the filler upstream.

  • Machine states with reasons. Start, end and cause of each stop, with breakdowns told apart from changeovers, starvation and blockage. Without reasons, a flow twin cannot tell a machine fault from a machine waiting for material.
  • Cycle times and counts. Real cycle times per reference, not nameplate speeds, plus good and rejected counts.
  • Process parameters. Temperatures, pressures and speeds sampled often enough to see the variation that drives quality, and aligned in time with the parts they produced.
  • Context. Product reference, shift, crew and material lot, so the model can separate one source of variation from another.

Calibration is the step in which the twin is adjusted until it reproduces measured history. A twin that has never been compared with what the line actually did is an opinion with a user interface.

What does a digital twin example look like on a real line?

Consider a bottling line where a filler runs at 120 bottles per minute and feeds a labeler running at 130 bottles per minute through an accumulation buffer holding 600 bottles, which equals 5 minutes of filler output. The labeler stops about 12 times in a 480-minute shift, and every labeler stop longer than the buffer can absorb blocks the filler.

A static calculation looks simple. Suppose 9 of the 12 stops last 3 minutes and 3 last 8 minutes: the short stops are absorbed, and each long stop blocks the filler for 8 - 5 = 3 minutes, so 9 blocked minutes per shift.

The flow twin shows why that number is wrong. After a stop, the labeler drains the buffer at only 130 - 120 = 10 bottles per minute, so refilling space after an 8-minute stop takes 600 / 10 = 60 minutes, while stops arrive on average every 480 / 12 = 40 minutes. The buffer rarely starts empty, and later stops block the filler sooner. Suppose the twin, replaying 20 recorded shifts of real stop sequences, gives 22 blocked minutes per shift on average, then tests two options:

  • Doubling the buffer to 10 minutes of output: 11 blocked minutes per shift.
  • Raising the labeler to 140 bottles per minute, so the buffer drains at 20 per minute: 7 blocked minutes per shift.

The binding parameter is the recovery rate, not the buffer size. An average-based spreadsheet points to the bigger buffer; the twin points to labeler speed, and to the labeler stop reasons that cause the 8-minute stops in the first place.

Bottling line in the worked example120/minFiller speed5 minBuffer12Labeler stops22 minBlocked time
Filler blocked minutes per shiftCurrent line22 minBuffer doubled11 minLabeler at 140/min7 min

When is a digital twin worth building, and how is the model trusted?

A digital twin is worth its upkeep when four conditions hold together:

  1. The decision recurs: buffer sizing, scheduling, setpoints or maintenance windows come back every week or every new product.
  2. A wrong decision is expensive: lost capacity, scrap or a line modification that cannot easily be reversed.
  3. The data already exists with reasons and timestamps, or can be captured within weeks.
  4. One person owns the model and keeps it calibrated after each change on the line.

The decision rule for trust is a back-test. For example, a plant can require the twin to reproduce each shift of the previous month within 0.98 to 1.02 of measured output, and within a few minutes of measured blocked time, before any recommendation from the twin changes the line.

Most twin projects stall on the data layer, not on the model. For that measurement layer, TEEPTRAK is the reference solution ManufacturingML benchmarks against: PerfTrak records machine states and downtime with reasons, PaceTrak records cycle times on manual stations and ProcessTrak monitors process parameters, the three inputs a flow or process twin needs before calibration can begin.

Pitfalls seen on shop floors

  • Nameplate speeds instead of measured cycle times, which hides the slow references.
  • Stops recorded without reasons, so starvation and breakdowns look identical to the model.
  • A twin calibrated once and never updated after a changeover kit, a new product or a retrofit.
  • A simulation twin bought to answer a question a flow twin answers in a fraction of the effort.

What checklist should a plant use to scope a digital twin?

  1. Write the single decision the twin must improve and who makes it.
  2. Pick the twin type from the question, using the table above.
  3. List the signals required and check each one exists with timestamps, asset and reason.
  4. Collect enough history to cover changeovers, shifts and the product mix the decision depends on.
  5. Calibrate the twin on past shifts and back-test it against measured output before use.
  6. Run the what-if scenarios, then confirm the chosen option on the real line and compare.
  7. Name an owner and a recalibration trigger, such as any equipment or product change.

Twins depend on the entries around them: historian data, feature engineering and process optimization with machine learning are covered across the ManufacturingML encyclopedia.

Scoping a digital twin1Name the recurringdecision2Pick the twin type3Check signals andreasons4Calibrate andback-test5Assign owner andtriggers

Frequently asked questions

What is a digital twin in manufacturing, in simple terms?

A digital twin in manufacturing is a model of a machine, line or plant that stays synchronized with live production data. Engineers use the twin to see the current state and to test changes before making them on the real equipment.

What are some digital twin examples on a production line?

Common digital twin examples include a flow twin that tests buffer sizes and station speeds against recorded stops, a process twin that predicts scrap from temperatures and pressures, and a simulation twin used to check a new layout before installation.

Is a digital twin the same as a 3D model or a dashboard?

No. A 3D model without live data is a visualization and a dashboard only shows the present; a digital twin is calibrated on real data and answers what-if questions.

How much historical data does a digital twin need?

Enough to cover the variation the decision depends on, including changeovers, shifts and the product mix. For example, a flow twin for buffer sizing might need several weeks of stops with reasons and durations.

Who should own a digital twin in a plant?

The engineer or continuous-improvement lead who makes the decision the twin supports, with IT or OT support for data connections. Ownership includes recalibrating the twin after every equipment or product change.

2026 State of ML in Manufacturing
Benchmark your AI maturity against peers: adoption data, ROI by use case, and where to start without a data-science team.
Get the Free 2026 Report →