MES System: Functions and Differences From ERP and EBR

The IEC 62264 series describes Manufacturing Operations Management as Level 3, between enterprise planning and process control functions. ^[1]

What matters is less the software label than the functions performed during ongoing production.

An MES Connects Planning and Manufacturing Execution

A production order specifies what needs to be manufactured. It does not yet establish which materials are available at a workstation, whether a required inspection has been completed, or which task comes next.

An MES translates this plan into a guided workflow. It provides tasks, assigns resources, records results, and tracks progress.

Consider a fictional example.

Batch CH-836 is scheduled for filling on equipment AF-12. The production order is available, but the required inspection of an input material is still pending.

The production order remains valid at the planning level. For execution, however, the important question is whether the material may be used.

An appropriately configured MES displays the pending inspection status in the order context and guides responsible personnel through the required steps. Work proceeds according to the configured prerequisites.

A planned order thus becomes a sequence of specific tasks, recorded results, and decisions.

MES Functions Range From Resources to Quality

An MES supports different areas of operational manufacturing management. IEC 62264-3 addresses activity models for Manufacturing Operations Management. ^[2]

Guide production tasks. Production orders are translated into actionable steps and responsibilities. A workflow engine coordinates tasks, results, and the transitions defined between them.

Assign resources. Materials, personnel, equipment, and other resources are associated with the production order. Availability and suitability are assessed against the specified requirements.

Capture execution data. Quantities, times, measurements, and results are assigned to the relevant operation during manufacturing. This preserves the relationship between recorded information and the work performed.

Integrate quality checks. Required inspections are connected to execution. An unresolved finding becomes the subject of a specific review or decision task.

Analyze production paths. Recorded events provide a basis for examining processing times, waiting periods, and different execution paths. The analysis of process variants reveals differences between documented runs.

For CH-836, these functions are connected: the material inspection affects the subsequent filling operation, its result belongs to the batch, and the following assessment requires the associated records.

ERP and MES Address Different Operational Levels

An ERP system (Enterprise Resource Planning) supports the planning and management of business resources. It connects functions such as procurement, inventory management, stock levels, production orders, and business transactions.

An MES, by contrast, focuses on operational manufacturing execution.

The simplified formula is: ERP plans; MES supports manufacturing execution. It describes two areas of emphasis, not a rigid technical boundary.

ERP systems sometimes include manufacturing functions of their own. MES applications may also handle detailed scheduling, resource coordination, and reporting.

For CH-836, the ERP system manages the production order and planned material requirements. The MES coordinates execution on AF-12, takes the material inspection into account, and records completed work steps.

Once processing is complete, consumed quantities and order status information return to enterprise planning.

Both levels therefore need shared identifiers for orders, materials, and batches. It must also be clear which system is authoritative for each type of information.

The distinction between ERP and MES thus depends on their respective responsibilities for functions and data, rather than on the user interface alone.

MES and Electronic Batch Records Serve Different Purposes

In regulated batch processes, operational production management is accompanied by controlled records of batch execution.

An Electronic Batch Record documents the execution of a batch electronically. It includes the applicable instructions, completed steps, results, and associated reviews and decisions.

An MES may include the record functions described in the article on Electronic Batch Records. Conversely, an EBR system may also support execution through tasks and inspections.

Operational manufacturing guidance and batch-specific recordkeeping are different functions that can be combined in one application.

For CH-836, both aspects matter: How is the filling operation performed, and what controlled record results from it?

IEC 61512-1:2026 addresses models and terminology for batch control in the process industries. It provides a framework for describing batch-oriented and procedural control models, but does not establish that a particular software application is suitable as an EBR system. ^[3]

The Benefits of an MES Emerge During Execution

The main benefit of an MES is that information is available where it is needed during work, rather than having to be assembled only after production is complete.

Fewer transfers between paper and systems. When material, order, and instruction data are already associated with the relevant work step, separate transfers of the same information are eliminated. Work proceeds within a shared order context.

Earlier identification of errors and unresolved prerequisites. Missing material inspections, incorrect assignments, and outstanding results become visible at the point where they affect the continuation of work. A later document review is no longer the first opportunity to identify the issue.

More focused preparation for batch review. Completed tasks, results, timestamps, and associated decisions remain connected to the operation. The reviewer receives a coherent execution history with outstanding items clearly identified.

For CH-836, the missing material inspection appears before filling begins. The responsible person addresses the open inspection task and documents the decision. The planned process then continues.

The documented filling operation and its prerequisites therefore remain part of the same operational context. The subsequent batch review begins with this history instead of assembling information from separate records.

MES Costs Depend on Integration and Implementation

MES costs consist of the required functional scope, technical integration, and ongoing support.

The main cost drivers include:

• Process scope: The number and variety of production processes, workstations, products, and exceptions.
• Interfaces: Connections to ERP, equipment, measuring devices, and laboratory and quality systems.
• Master data: Consistent identification of orders, materials, batches, and resources.
• Tasks and rules: Configuration of work instructions, roles, inspection conditions, and approval paths.
• Implementation: Testing workflows, training personnel, and migrating existing data where required.
• Operations: Maintaining interfaces, permissions, instructions, and process models.

In regulated environments, additional requirements may apply to the qualification and validation of computerized systems and to documented changes. EU GMP Annex 11 addresses corresponding requirements. ^[4]

For CH-836, the implementation effort differs depending on whether the system guides only filling tasks or also integrates material inspection, equipment connectivity, batch records, and approval into a shared workflow.

A meaningful cost comparison therefore begins with the required functions and their integration into existing operations.

MES Selection Begins With Required Operational Functions

MES selection should begin with the specific tasks the system needs to perform during manufacturing.

How such requirements can be assessed against demonstrated functionality is explained in the guide to selecting compliance software.

For an MES, these requirements include order execution, material assignment, equipment connectivity, inspection tasks, reporting, and batch documentation.

For CH-836, a useful demonstration would therefore not consist of a general overview of software modules, but of a connected operational sequence:

The order is scheduled, the pending material inspection appears in the workflow, the responsible person makes a decision, the filling operation is performed, and its result is made available for subsequent review.

This sequence shows which functions are available, what information they require, and where organizational or technical handoffs occur.

An MES Does Not Replace Professional Judgment

An MES guides tasks, records results, and takes defined prerequisites for process transitions into account. Its records must nevertheless be assessed against the operational requirements of the particular organization.

Reporting a produced quantity to the ERP system provides an example.

If CH-836 is reported as complete and a quantity is transferred into inventory, successful processing of that message initially establishes only that the transaction was accepted. It does not establish that the reported quantity underwent a complete plausibility check or that all required quality decisions have been made.

A technically completed task is not necessarily a batch that has been released.

Data review, deviation handling, and responsible approval must therefore remain distinct activities. An MES supports their execution and documentation but does not replace the substantive decision.

Likewise, the MES label does not establish regulatory compliance. What matters is the available functionality, its specific configuration, the data used, and the system's suitability for its intended use.