What Is a Manufacturing Execution System (MES)?

An MES runs production execution in real time. Concretely: it issues a work order to a workstation, presents the operator the right SOP version and the right recipe step, enforces sequencing (you can't sign step 7 before step 6 is signed), captures the actual materials and quantities consumed, prompts in-process checks at the right moments, blocks release if any check fails, and assembles the batch or device history record from the live signed steps rather than from a clerk re-typing a paper traveller. The good ones do this with no paper at all and with every signature, weight, scan and reason-for-change written into an audit trail as it happens. The bad ones are a digital scrapbook of PDFs.

ERP (SAP, NetSuite, Dynamics, Odoo) owns demand, planning, inventory accounting, finance and purchasing. It tells you *what* to make and *when*. SCADA / historians (Ignition, Wonderware, OSIsoft) read sensors and PLCs — temperatures, pressures, flow rates — and store time-series telemetry. MES sits between them: it takes the work order down from ERP, drives the human + machine workflow on the floor, and reports back to ERP the actual yield, scrap, and lot consumption. Without an MES you typically see two failure patterns: ERP shows perfect plans that the floor silently deviates from, or SCADA dashboards full of numbers that nobody can tie back to a specific batch. The MES is the system of record for what actually happened.

An MES worth buying in 2026 has eight non-negotiables. (1) Live, paperless execution with mandatory e-signatures on regulated steps. (2) Recipe / BOM versioning with mandatory effective dates — operators see the right version, never a stale one. (3) Step-by-step enforcement: out-of-sequence operations are blocked, not warned. (4) Built-in deviation capture at the point of failure (not a separate ticket the operator forgets to file). (5) Live ERP inventory write-back, so finance sees actual consumption. (6) A 21 CFR Part 11-grade audit trail with reason-for-change. (7) Inspection-readiness exports — pull a complete eBR/eDHR in minutes, not days. (8) Mobile + scanner-friendly UX, because production happens with gloves on, not at a desk. Anything missing (5) or (6) is a 2010 product with a new logo.

The economic case for MES is rarely the licence cost — it's the operational losses an MES quietly stops. Three line items dominate. First, scrap and rework from out-of-sequence or wrong-material errors: a properly enforced MES typically removes 60–90% of these because the screen will not let the operator do the wrong thing. Second, batch-release cycle time: paper traveller review-by-exception takes days; a live signed eBR is reviewable in hours. Third, inspection / audit cost: companies that run paper or hybrid spend weeks assembling evidence; an MES-native plant exports the binder in a click. The CFO sees these three savings before they ever see a productivity number — and that's how MES gets funded.

Every MES vendor demo looks great because the demo is a curated 6-minute happy path. Force the vendor to break their own product in front of you: ask them to start a batch with an expired material, attempt an out-of-sequence step, sign as a user without the right role, and trigger a deviation mid-run. Watch how the system behaves under failure — that's where the difference between a 2008 MES with a new skin and a modern platform shows up. Also ask: how long from PO to first running batch, who configures the workflows (vendor PS or your team), what the API surface looks like, and how upgrades happen for customers on heavy customisation. The honest answers separate a buy-and-implement-in-90-days product from a 2-year SAP-grade project.

Boil the RFI down to a dozen questions you cannot get wrong. Does the audit trail capture before-and-after values with mandatory reason-for-change? Can a reviewer release a batch from the eBR alone, with no separate paper? Is the same product used for pharma, food, devices and supplements — or is each industry a fork? Does it run on-prem when a customer's regulator requires it? Is the implementation done by configuration or by code? Is the e-signature meaning structured (Author / Reviewer / Approver / QA Release) or a free-text checkbox? Is there a self-serve compliance score across Part 11, GMP, ISO, FSMA — or do you have to commission an audit to find out where you stand? A vendor that can't answer all of these crisply is not a 2026 MES.