TrackFinch 2.0 — production planning is hereRead the notes

What is an MES (manufacturing execution system)? And do you need one?

A manufacturing execution system tracks and controls production as it happens on the machines. What an MES does, how it differs from MRP, and the honest small-shop answer.

Updated 2026-07-14 · 4 min read

A manufacturing execution system (MES) is software that tracks and controls production while it’s happening — dispatching work to specific machines, collecting machine and operator data in real time, enforcing routings and quality steps, and reporting exactly what got made, when, by whom, at what yield. If MRP decides what to make and when, an MES governs how it physically executes, minute by minute.

What an MES actually does

The classic MES functions: dispatching (this job, this machine, now), data collection (cycle counts, machine states, downtime reasons — often wired to the equipment), traceability (which lot, which operator, which parameters, for every unit), quality enforcement (can’t advance past a skipped inspection), and performance analytics (OEE — availability × performance × quality). Industries with genealogy requirements — aerospace, medical, automotive — run MES because a unit’s full birth certificate is a contractual object.

MES vs MRP vs ERP, in one breath

ERP runs the company. MRP plans materials and orders. MES runs the machines. A big plant stacks all three; the acronyms mostly describe altitude — dollars, days, and minutes respectively.

The honest small-shop answer

Search interest in MES is dominated by plants and their consultants, but small shops land on the term while asking a fair question: “do I need software watching the machines?” Almost always, no — and the reason is arithmetic. MES value scales with the cost of a lost machine-minute and the depth of traceability requirements. A 40-machine line bleeding 3% OEE pays for an MES; a six-person job shop does not, and the implementation would cost more attention than it returns.

What a small shop actually needs from the “execution” layer is much simpler:

  • Live job status from the floor — queued, running, done, tapped on a phone (work orders)
  • Honest consumption — materials logged as jobs run, so the plan stays true
  • A queryable history — what ran, how long it took, what it consumed

That’s the useful 80% of MES outcomes at roughly 2% of MES ceremony. If a customer contract someday demands unit-level genealogy or validated quality gates, you’ll know — the requirement arrives in writing, with a PO attached to justify it.

The one-sentence version: an MES micro-manages machines for plants that bill by the minute; a small shop needs its jobs visible and its materials honest — which is a work order system, not an MES.

Theory's done. Run the shop.

Everything in this article is a built-in behavior in TrackFinch. Free for 14 days.

Free for 14 days · Full access · Cancel anytime