A manufacturing execution system (MES) is the layer that connects planning and scheduling (typically ERP/MRP) to what actually happens on the shop floor. It coordinates, constrains, and records production in real time so you know what was made, how, by whom, and under which conditions.
Core functions of an MES
Most MES platforms in regulated, brownfield environments cover some or all of the following, with scope shaped by what is already handled in ERP, SCADA, LIMS, PLM, or QMS:
- Production dispatching and work orchestration
Directing operators and machines on what to run next, based on released orders and routings. This includes work order release, operation start/complete, move tickets, holds, and rework routing. In many plants, MES is the practical system of record for WIP location and status.
- Work-in-progress (WIP) visibility
Tracking material, subassemblies, and units as they move through operations and work centers. MES maintains current status (e.g., queued, running, on hold, complete) and often the count and identifiers of units or lots at each step.
- Enforcement of process steps and sequencing
Guiding operators through the approved sequence of steps, checks, and sign-offs, and preventing unauthorized shortcuts. This can include routing logic, interlocks with machines or test equipment, and rule-based checks such as “do not proceed until torque result is within spec.”
- Digital work instructions and data capture
Presenting the right version of work instructions, specifications, and reference data at the right step, and capturing required data (measurements, readings, checklists, photos, test results) as structured records tied to the specific unit, lot, or order.
- Traceability and genealogy
Building an end-to-end record of which materials, components, tools, equipment, parameters, and people were involved in producing each unit or lot. This typically includes serial/lot tracking, as-built/as-maintained genealogy, and linkage to test data and nonconformances.
- Electronic batch records / eDHR / eBR support
In regulated sectors, MES often provides the execution backbone for electronic device history records, batch records, and other production records by enforcing required signatures, data fields, and step completion logic, and by generating the compiled record for review.
- Data collection from equipment and test systems
Interfacing with machines, PLCs, test stands, and inspection systems to pull process and quality data in real time. This may be direct (OPC, fieldbus, MQTT) or via SCADA/edge gateways. MES associates this data with specific operations and units for later analysis and audits.
- In-process quality control
Enforcing inspection points, sampling plans, reaction plans, and holds. MES can initiate nonconformance records, route items to MRB, and prevent further processing until required review or disposition actions are taken, often integrating with a separate QMS or CAPA system.
- Resource and equipment management (to a point)
Managing basic status of machines, tools, and fixtures (available, down, in setup, calibration due, etc.) and applying rules that block production if prerequisites like calibration, preventive maintenance, or operator qualifications are not met. Deeper maintenance usually lives in CMMS/EAM.
- Performance monitoring and OEE inputs
Providing near real-time views of throughput, cycle time, scrap, rework, and equipment state that feed OEE, NPT, and other operational metrics. Often, MES does not own the final KPI dashboard but serves as a key data source.
How MES fits with existing systems
In most regulated environments, MES is not a greenfield replacement. It coexists with ERP, PLM, QMS, SCADA, LIMS, CMMS, and custom applications:
- ERP/MRP typically remains the source for demand, customer orders, and financial posting. MES consumes work orders and routings, executes them, and sends completions, scrap, and confirmations back.
- PLM/Document control remains the master for product definitions, BOMs, routings, and controlled documents. MES pulls or is fed released data and enforces correct versions at execution time.
- QMS usually owns CAPA, audits, and master quality procedures. MES enforces checks on the floor, initiates nonconformances, and links to QMS records.
- SCADA / control systems continue to manage real-time control and safety. MES uses them as data sources and, in some cases, as actuators for recipe selection or interlocks, subject to validation and change control.
Because of existing integrations, validation scope, and downtime constraints, trying to make MES replace all of these systems outright typically fails in aerospace-grade and similar contexts. The qualification burden, migration of history, and operational risk become too high. More realistic strategies incrementally extend MES into well-defined gaps while leaving proven systems in place.
What an MES typically does not do by itself
Despite vendor claims, most MES deployments in regulated, long-lifecycle plants do not successfully own all of these areas end-to-end:
- Enterprise planning, S&OP, or advanced APS for complex networks
- Full product lifecycle management or engineering change control
- Comprehensive QMS (CAPA, audit management, complaints, risk files)
- Plant-wide process control, safety systems, or detailed equipment maintenance
- Guaranteed regulatory compliance or audit outcomes
Elements of these may sit in MES, but in highly regulated environments they are usually shared responsibilities across multiple validated systems.
Key tradeoffs when defining what your MES should do
The exact role of MES varies by plant. When deciding what it should do in your environment, typical tradeoffs include:
- Coverage vs. validation burden: Adding more workflows and integrations to MES increases potential value but also increases validation and change control overhead.
- Centralization vs. resilience: A single MES as the execution hub simplifies traceability but makes production more dependent on one system and one vendor.
- Standardization vs. local flexibility: A tightly defined global MES model improves comparability and auditability, but may make it harder to support edge cases and legacy equipment at specific plants.
- Integration depth vs. rollout speed: Deep integration with ERP, PLM, QMS, and equipment reduces manual work and data discrepancies but lengthens implementation time and raises brownfield integration risk.
In most regulated and high-mix environments, the most durable MES implementations focus on a clear, bounded role: orchestrating and recording shop-floor execution, maintaining robust traceability and genealogy, and integrating cleanly with existing systems instead of trying to replace them all.
