Manufacturing Execution Systems (MES): A Buyer's Guide

A manufacturing execution system (MES) is software that manages and records production as it happens on the shop floor. It turns ERP orders into dispatched work, tracks materials, labor and equipment in real time, enforces quality steps and creates a genealogy of every lot. In the ISA-95 model, MES sits at Level 3, between ERP and machine controls.

Key takeaways

  • ERP plans what to make; MES manages how it gets made, minute by minute, and records what actually happened.
  • Core MES functions include dispatching, data collection, quality, traceability, labor tracking and performance analysis.
  • The ISA-95 standard is the common language for defining the boundary between MES and ERP.
  • Most MES projects succeed or fail on process definition and integration, not on the software screens.

Where does MES fit in the manufacturing technology stack?

The ISA-95 standard (also published as IEC 62264) organizes manufacturing systems into levels. Levels 0 to 2 cover the physical process, sensors and control systems such as PLCs and SCADA. Level 3 is manufacturing operations management, where MES lives. Level 4 is business planning and logistics, where ERP lives. ISA-95 mainly defines the interface between Levels 3 and 4: what information flows down (orders, product definitions, schedules) and what flows up (production performance, material consumption, quality results).

That boundary matters because many companies try to stretch ERP onto the shop floor or push planning logic into MES. If you are still choosing or replacing a planning system, our guide to choosing an ERP covers that side of the decision.

What does an MES actually do?

Industry definitions vary, but most MES products cover a common set of activities:

  • Product definition management: versioned bills of material, routings, recipes and work instructions.
  • Resource management: knowing which machines, tools and qualified operators are available for an order.
  • Scheduling and dispatching: sequencing work orders and releasing them to work centers.
  • Execution and data collection: guiding operators through steps and capturing counts, scrap, parameters and downtime.
  • Quality management: in-process checks, holds, nonconformance records and statistical process control.
  • Traceability: lot and serial genealogy showing which materials, machines and people touched each unit.
  • Performance analysis: work in process, yield and overall equipment effectiveness (OEE).
  • Labor tracking: who worked on which job, for how long, often feeding payroll and costing.

MES vs ERP vs other plant systems

SystemMain question it answersTime horizonTypical users
ERPWhat should we make, buy and ship?Days to monthsPlanners, finance, purchasing
MESWhat is happening on the floor right now, and what happened?Seconds to shiftsSupervisors, operators, quality
SCADA / PLCHow is the machine or process behaving?Milliseconds to minutesControls engineers, operators
WMSWhere is the inventory and how does it move?Minutes to daysWarehouse staff
CMMSWhich assets need maintenance and when?Days to yearsMaintenance teams
LIMSWhat did the lab test results show?Hours to daysQuality labs

When does a manufacturer need an MES?

Paper travelers and spreadsheets work until they do not. Common triggers include:

  • Customer or regulatory requirements for full lot genealogy, such as in food, medical devices, aerospace or pharmaceuticals.
  • Recalls or quality escapes that took days to trace because records were on paper.
  • No reliable view of downtime, scrap or OEE by line and shift.
  • Labor and job costing that depends on manual timesheets entered after the fact.
  • Multiple plants running the same products with different, undocumented processes.

A frequent hidden cost is fragmented data: each plant or line keeps its own database, and corporate reporting becomes a reconciliation exercise. Our piece on why a unified data layer matters describes the same problem in enterprise apps.

How to evaluate and implement an MES

Evaluation checklist

  • Fit for your production model: discrete, batch, process or mixed.
  • Out-of-the-box ERP integration aligned with ISA-95 messages, and a clear owner for master data.
  • Connectivity to your machines and historians (for example OPC UA support).
  • Configurable workflows and electronic work instructions without custom code for every change.
  • Electronic records, signatures and audit trails if you are in a regulated industry.
  • Deployment model (cloud, on premises or hybrid) and plant-floor resilience when the network drops.
  • Reporting that supervisors use daily, not only executive dashboards.

Implementation approach

  1. Map current processes on one line, including the informal steps operators really follow.
  2. Define the ERP and MES boundary in writing: which system owns orders, BOMs, inventory and labor.
  3. Pilot on one line with clear success measures, such as traceability time or data completeness.
  4. Train supervisors first, since they decide whether operators trust the system.
  5. Template and roll out to other lines and plants, keeping local variations deliberate and documented.

Once data flows reliably, analytics become possible. Our article on big data analytics for enterprise decisions covers what to do with it.

Frequently Asked Questions

Is MES the same as MOM?

Not exactly. Manufacturing operations management (MOM) is the broader ISA-95 Level 3 category covering production, quality, maintenance and inventory operations. MES is usually the production core of MOM. Some vendors sell suites that include quality, warehouse and maintenance modules and call the whole suite MES, so check exactly which functions are included.

Can a small manufacturer justify an MES?

Often yes, if traceability, quality or labor costing problems are costing time or customers. Smaller plants can start with cloud MES products that focus on data collection, work instructions and OEE, then add scheduling and quality later. Begin with one painful problem and measure whether the system solves it before expanding.

How long does an MES implementation take?

Timelines depend on scope, number of plants, integration complexity and regulatory validation needs. A single-line pilot can be quick, while a validated multi-plant rollout takes much longer. Ask vendors for reference customers with similar production models and plant counts, and plan time for process definition, not only software configuration.

Next steps

  • List the three shop-floor questions you cannot answer today without manual effort.
  • Document which system should own each data object between ERP and the floor.
  • Shortlist vendors with references in your production model and run a scripted demo on your own process.
  • Pick one pilot line and define success measures before signing a multi-plant deal.

Last reviewed: October 2026.

Sources

Comments

Popular Posts

Why Workday Onboarding Breaks Down for Frontline Employees

How to Improve the Customer Experience (CX)

How Do I Log In and Sign In to Workday HCM

UKG Union Contract and Overtime Rules for Multi-Site Food Plants

Infor HCM Software Engineer Jobs: Salary Factors and Skills

How to Search in Workday: Find Reqs, Reports, People and Tasks

ERP Solution Guide: How to Choose the Best ERP for You

The End of Remote Work: Why Companies Want You Back

The Future of Employee Healthcare Key Concerns and Strategies for 2024

How Digital Marketing Helps Your Business Grow: A Practical Plan