MES (Manufacturing Execution System)

A Manufacturing Execution System (MES) is a software application or suite that manages, monitors, and records production activities on the shop floor in near real time. It typically sits between enterprise-level planning systems, such as ERP, and plant-level control or automation systems, such as PLCs, SCADA, and DCS.

Scope and core functions

MES commonly refers to the operational IT/OT layer that:

• Translates production plans and work orders into executable shop floor operations
• Guides and records execution of manufacturing steps, often via electronic work instructions and operator terminals
• Captures production data, including material usage, process parameters, equipment status, and operator actions
• Tracks work-in-process (WIP), material flow, and product genealogy across batches, lots, or serial numbers
• Supports quality control activities, including in-process checks, holds, deviations, and nonconformance recording
• Coordinates resource usage, such as machines, tools, and personnel, according to defined routing and rules
• Provides visibility into production performance, including metrics like cycle time, downtime, yield, and OEE

In regulated manufacturing environments, MES often plays a central role in enforcing defined process sequences, recording execution evidence, and supporting electronic records and audit trails.

Position in the systems landscape

Within common reference models, such as ISA-95, MES is usually associated with manufacturing operations management at the level between business planning and scheduling (ERP) and direct process control (PLC/SCADA/DCS). In practice, an MES may:

• Receive production orders and master data (materials, BOMs, routings) from ERP or planning systems
• Exchange status and parameter data with equipment, historians, or other OT systems
• Provide execution data back to ERP, quality systems, data lakes, and reporting tools

MES is not the same as ERP, which focuses on planning, finance, and high-level logistics, and it is not the same as control systems that execute low-level machine control logic.

Operational use in industrial environments

On the shop floor, MES typically appears as operator terminals or integrated interfaces that:

• Display the correct job, recipe, or batch record to each work center
• Prompt operators for data entry, checks, sign-offs, or electronic signatures where required
• Trigger equipment setpoints or recipe downloads when integrated with automation
• Enforce sequencing and interlocks, for example preventing a step from proceeding until required inspections are complete
• Generate a detailed execution history, often used for traceability, investigations, and continuous improvement analysis

In many regulated industries, MES capabilities may overlap or integrate with systems used for electronic batch records, deviation logging, and certain aspects of quality management.

Common confusion

• MES vs ERP: ERP focuses on planning, inventory, and commercial transactions. MES focuses on executing and recording detailed production activities. They are often integrated but serve different purposes.
• MES vs SCADA/PLC: SCADA and PLCs directly control and monitor equipment signals and automation logic. MES uses data from these systems but focuses on workflows, materials, and records at the operations level.
• MES vs MOM: Manufacturing Operations Management (MOM) is sometimes used as a broader term that can include MES plus related functions such as maintenance, quality operations, and inventory operations. In many organizations the terms are used interchangeably, but MES often refers more specifically to execution-centric capabilities.

Relation to integration and standards

MES is frequently designed or configured with reference to standards and models for manufacturing integration and operations, such as ISA-95 and related guidance. These models are commonly used to structure system boundaries, data flows, and responsibilities between ERP, MES, automation, and quality systems. Implementations vary by industry and vendor, and the specific division of functions between MES and other systems is highly context-dependent.