In many factories, MES is introduced through what users can see:
A production dashboard.
An OEE screen.
A downtime Pareto chart.
A digital work instruction.
A traceability report.
These elements are visible, demonstrable, and useful for communicating progress. They also encourage a dangerous simplification:
That MES is primarily a collection of screens positioned between the shopfloor and ERP.
It is not.
A screen is only an interface through which a user interacts with part of the system. The real value of MES/MOM lies underneath: in the production models, operational rules, master data, execution states, validations, workflows, resource constraints, decision rights, and evidence that govern how manufacturing work is performed.
This is the practical significance of Level 3 within the ISA-95 model.
Level 3 is not merely a software layer, nor is it necessarily a single application. It is the functional domain in which manufacturing operations are coordinated, controlled, and recorded.
It converts enterprise production requirements into executable work and converts shopfloor activity into reliable operational evidence.
MES is not valuable because it displays production. It is valuable because it helps govern the conditions under which production may proceed and preserves the operational truth of what actually occurred.
Between Enterprise Planning and Physical Execution
ERP generally operates at the level of enterprise planning, commercial commitments, material requirements, inventory, costing, and business transactions.
It addresses questions such as:
- What must be produced?
- In what quantity?
- By which date?
- Which materials should be available?
- What demand or customer requirement created the order?
- What cost and inventory consequences should be recorded?
PLCs, machines, robots, distributed control systems, and other automation technologies operate much closer to the physical process.
They control motors, sequences, temperatures, pressures, positions, speeds, interlocks, and equipment states. Their logic may execute in milliseconds or seconds.
Between these two domains lies a difficult operational space.
A production requirement must be translated into work that is physically executable.
The factory must determine:
- which resource can perform the work;
- which materials are valid and available;
- which recipe, specification, or parameter set applies;
- which people are qualified and authorised;
- which tools, fixtures, and gauges are required;
- which quality controls must be completed;
- how interruptions and deviations will be handled;
- and how the result will be declared and reconciled.
This is Level 3 territory.
It is where manufacturing is managed as an operation rather than merely planned as a business requirement or controlled as a machine sequence.
Why Enterprise Planning Alone Is Insufficient
ERP is essential, and modern ERP platforms may include production, quality, warehouse, or maintenance functions.
The issue is not that ERP is incapable of containing operational information. The issue is that enterprise planning structures and transaction cycles are generally insufficient to represent and govern the detailed, time-sensitive conditions of shopfloor execution.
An ERP order may request 10,000 units of a product.
The factory must still determine:
- which line, cell, or machine will execute the order;
- whether the equipment is available, capable, and released;
- which version of the recipe or specification is valid;
- which material batches may be consumed;
- whether operators possess the required qualifications;
- which sequence and changeover conditions apply;
- which in-process quality checks are mandatory;
- how stoppages, scrap, and rework will be classified;
- and how actual production evidence will be returned.
These are not peripheral technical details.
They are the mechanisms through which the organisation protects quality, traceability, productivity, cost, safety, and compliance.
When Level 3 capabilities are weak, these decisions move into spreadsheets, local databases, paper records, whiteboards, emails, and individual memory.
The factory continues operating, but operational control becomes fragmented.
ERP may show that an order remains open while the line considers it complete. Materials may have been consumed differently from the standard. Quality may have unresolved inspections. Maintenance may have imposed a restriction on the equipment. The production declaration may reflect what was entered rather than what physically occurred.
The problem is not simply a lack of visibility.
It is a lack of execution discipline and operational reconciliation.
Why the Screen Is the Wrong Design Starting Point
Many MES initiatives begin by asking users what they want to see.
That question is understandable, but it is insufficient.
Users request dashboards, reports, coloured indicators, simplified transactions, and faster data entry. The project team converts these requests into screens. The screens are reviewed, configured, demonstrated, and approved.
Then the system reaches the shopfloor, and deeper problems become visible.
The equipment hierarchy does not reflect the actual operating structure.
The production model cannot represent shared resources or alternative routes.
Downtime reason codes are too generic to support meaningful loss analysis.
Material status is inconsistent between ERP, warehouse, quality, and production.
Recipe versions are not governed.
Operator qualifications are not connected to task authorisation.
Rework has no valid digital route.
The same production interruption is classified differently across shifts.
The interface may appear modern, while the operating model beneath it remains weak.
A well-designed screen cannot compensate for poor execution logic.
MES/MOM design should therefore begin not with visualisation, but with the manufacturing operating model.
That operating model should define:
- production resources and capabilities;
- routing and dispatching logic;
- execution states and transitions;
- material status and genealogy;
- quality gates;
- equipment and personnel qualifications;
- exception paths;
- decision rights;
- system responsibilities;
- and the evidence required to prove correct execution.
Only after these foundations are clear should screens be designed around them.
What Level 3 Actually Coordinates
Level 3 MOM brings together several operational dimensions that are frequently managed in separate systems or functions.
Production operations
The operational layer must receive production requirements, convert them into executable work, dispatch activities, manage execution status, and record actual results.
This involves more than opening and closing an order. It includes sequencing, resource allocation, work-in-progress visibility, production declarations, partial completions, and deviations from the planned route.
Quality operations
Quality must be embedded within execution rather than treated exclusively as a final inspection activity.
The operational layer may:
- enforce required inspections;
- collect results;
- prevent the use of unreleased material;
- place products or batches on hold;
- trigger containment;
- manage nonconforming output;
- and preserve evidence that required controls were performed.
Maintenance operations
Equipment condition directly affects production feasibility.
MES/MOM does not replace CMMS/EAM, but it should recognise relevant asset states, restrictions, and maintenance events. Production execution should not assume that every resource appearing in an ERP routing is physically available and operationally capable.
Inventory and material operations
Material availability is not only a warehouse concern.
Level 3 must understand which material is physically present, released, allocated, staged, consumed, returned, scrapped, or associated with a specific production result.
Personnel and resource coordination
Factories do not execute through machines alone.
People, tools, fixtures, gauges, documents, recipes, and qualifications may all determine whether work can proceed.
A mature MOM capability represents these constraints rather than leaving them to informal knowledge.
This is why MES is more than a production screen.
It is a coordination mechanism that keeps operational resources, rules, evidence, and responsibilities aligned around real manufacturing work.
Visibility, Orchestration, Enforcement, and Evidence
A factory can possess excellent visualisation and still have weak operational control.
A useful way to assess Level 3 capability is to distinguish four functions.
Visibility
What is happening, what has happened, and where does attention appear to be required?
Orchestration
Which work, resources, approvals, and activities must be coordinated next?
Enforcement
Which conditions must prevent, restrict, warn, or escalate execution?
Evidence
What information must be preserved to demonstrate what occurred, under which conditions, and with whose authorisation?
A dashboard may show that a machine has stopped. That does not mean the stoppage was classified correctly, responsibility was assigned, escalation occurred, or recovery was confirmed.
A quality screen may display inspection results. That does not mean the system prevented production under an expired specification.
A traceability report may be available after production. That does not mean the system controlled which material batches could be consumed during execution.
A digital work instruction may appear on a terminal. That does not mean the correct version was enforced or that deviations were authorised.
Visibility explains what appears to be happening.
Operational control defines what is permitted to happen, what evidence must be captured, and what response is required when execution moves outside the approved standard.
Level 3 should support both.
When MES is designed primarily as a reporting layer, it often delivers visibility without sufficient orchestration, enforcement, or evidence.
Control Should Be Proportionate to Operational Risk
Operational control does not mean that every deviation must create a hard system block.
Excessive enforcement can create new risks, particularly when master data, sensors, interfaces, or system availability are unreliable.
A mature MOM design should determine whether each condition requires:
- hard prevention;
- a warning;
- authorised override;
- escalation;
- additional evidence;
- or retrospective review.
For example, the use of an unreleased material batch may require a hard block. A minor delay in a non-critical inspection may require a warning and supervisor authorisation. A production deviation may require approval and enhanced traceability rather than automatic stoppage.
The objective is not maximum digital restriction.
It is proportionate and traceable operational control.
A Practical Example: The Changeover Outside the System
Consider a packaging line producing several product variants.
ERP sends the production order. The MES terminal displays the next product. The operator starts the order.
On paper, the process appears digital.
In reality, the changeover depends on several conditions:
- the correct tooling must be installed;
- residual material from the previous product must be cleared;
- new packaging components must be verified;
- the approved recipe must be loaded;
- cleaning must be completed;
- quality must approve the first-off sample;
- and the operator must confirm the start of stable production.
When these activities are managed through memory, paper, and verbal confirmation, MES is not controlling the changeover.
It is merely displaying the order before and after the real process occurs elsewhere.
A mature Level 3 design would connect these conditions.
The system could verify the relationship between product and tooling, enforce the approved recipe version, record line clearance, confirm valid material components, request first-piece approval, and prevent normal production status until critical checks are complete.
The purpose is not to digitise every human action.
It is to make the operational conditions for safe and correct execution explicit, governed, and traceable.
MES/MOM as Industrial Process Management
Viewed from this perspective, MOM functions as an industrial process-management capability.
It connects events, rules, work, resources, data, and accountability around manufacturing execution.
A production order is not merely displayed. It moves through controlled operational states.
A material is not merely scanned. Its identity, status, and genealogy determine what actions are allowed.
A downtime event is not merely recorded. It may trigger classification, escalation, maintenance response, and follow-up.
A quality result is not merely stored. It may release, block, contain, or redirect production.
An equipment condition is not merely visualised. It may change resource availability or require authorisation to continue.
This is where MES/MOM aligns naturally with BPM thinking.
However, industrial execution operates under tighter time constraints, deeper equipment integration, and more immediate consequences for safety, quality, and output than most administrative workflows.
The process model must therefore represent the reality of the factory, including its constraints and exceptions, rather than an idealised sequence of office activities.
Exception Handling Is the Real Design Test
The normal production path is usually the easiest part of an MES design.
The real complexity appears when:
- an order is partially completed;
- material must be substituted;
- production is interrupted;
- rework is required;
- equipment becomes restricted;
- quality places material on hold;
- a batch must be split;
- a recipe must be temporarily deviated;
- or execution must resume after a system or machine failure.
These situations determine whether the system supports real operations or only an ideal process.
The quality of an MES design is revealed less by how it manages the standard route than by how it governs exceptions without losing traceability, accountability, or operational meaning.
When exception scenarios are not designed explicitly, users create external workarounds.
The result is a nominally digital process with its most critical decisions taking place outside the system.
Where Level 3 Projects Commonly Fail
One frequent failure is treating Level 3 as a thin technical interface between ERP and machines.
Orders are transmitted downward and production confirmations upward, but operational rules remain undefined. The result is technically connected but operationally shallow.
Another failure is copying ERP structures directly into MES.
ERP routings, work centres, and material definitions may be sufficient for planning and costing but inadequate for real-time execution. A production line may share machines, tooling, labour, or intermediate resources in ways that the enterprise model does not represent.
A third failure is building dashboards before designing master data, execution states, and exception logic.
The screens appear convincing during demonstrations, but users later discover that statuses, hierarchies, reasons, and transitions do not reflect how the plant operates.
A fourth failure is attempting to make MES responsible for every manufacturing function.
MOM must coordinate with ERP, SCADA, historians, CMMS/EAM, QMS, WMS, laboratory systems, and other applications. It should not duplicate all their capabilities.
A fifth failure is neglecting semantic ownership.
An integration may exchange data successfully while leaving basic questions unresolved:
- Which system owns the production order?
- Which system owns equipment state?
- Which system authorises material status?
- Which system owns maintenance execution?
- Which system governs production status?
- Which system preserves the final as-built record?
Clear architectural boundaries require more than technical interfaces. They require explicit responsibility for data meaning, transaction authority, and operational decisions.
Level 3 Must Preserve Operational Truth
One of the most important purposes of MOM is to preserve the relationship between plan and reality.
ERP may define what should occur.
Automation systems may record physical signals.
Level 3 must establish the operational meaning of what actually occurred.
It must help answer:
- Which product was produced?
- Under which order and specification?
- On which equipment?
- With which material batches?
- Using which recipe or parameter set?
- During which execution state?
- Under whose authorisation?
- Which interruptions occurred?
- What quality evidence was collected?
- How much good output, scrap, and rework resulted?
- Which deviations were approved?
- What was the final as-built record?
Without this context, plant data remains a collection of transactions, timestamps, and signals.
With it, the organisation can analyse losses, reconstruct genealogy, investigate deviations, evaluate performance, and connect operational behaviour with financial and customer outcomes.
This is the operational truth that Level 3 must preserve.
Level 3 as a Foundation for Smart Manufacturing and Industrial AI
Level 3 is foundational for Smart Manufacturing and Industrial AI because AI requires contextualised operational data, not merely large volumes of plant data.
A model may detect an unusual temperature pattern. To support a useful decision, it may also need to know:
- which product was being produced;
- which production phase was active;
- which recipe version applied;
- the equipment state;
- the material batch;
- the operator authorisation;
- the current quality disposition;
- the maintenance condition;
- and whether a deviation was active.
Without this context, the model may identify correlation without understanding operational meaning.
MOM provides much of the semantic structure required to interpret plant data correctly.
This does not mean that every AI capability must reside inside MES. It means that reliable industrial intelligence depends on the production context, state, governance, and evidence that Level 3 helps create.
Before Implementing the Capability, Check Whether…
Before implementing or expanding MES/MOM, the organisation should be able to answer the following questions clearly:
- Is the production model aligned with the actual equipment, lines, cells, and routes?
- Are ERP and shopfloor definitions compatible without being forced to be identical?
- Are execution states and transitions explicitly defined?
- Are material, equipment, personnel, recipe, and process-segment master data governed?
- Are quality controls embedded at the correct points in execution?
- Are downtime and loss classifications operationally meaningful?
- Are rework, deviations, substitutions, interruptions, and partial completions designed explicitly?
- Are system responsibilities across MES/MOM, ERP, SCADA, CMMS/EAM, QMS, WMS, and historians clear?
- Is the required level of control proportionate to operational risk?
- Does the system preserve evidence supporting decisions, not only transactions?
- Have operators, supervisors, maintenance, quality, engineering, and planners validated the model at the gemba?
When these foundations are unclear, additional screens merely create a more attractive representation of the same ambiguity.
The Real Test of MES/MOM
The maturity of a Level 3 capability should not be judged by the number of terminals, dashboards, reports, or connected machines.
A more meaningful test is whether the system helps the factory answer, consistently and in context:
What should be happening now?
What is actually happening?
Is execution within the approved standard?
Which condition prevents work from continuing?
What action is required?
Who is authorised and accountable to act?
What evidence will demonstrate that the work was completed correctly?
Can the organisation reconstruct what happened after the event?
That is the difference between a display system and an operational management capability.
MES becomes valuable when it stops being treated merely as a window into production and becomes part of the discipline through which production is executed, governed, and understood.
The screen is visible.
The real system is the operating logic, decision structure, and operational evidence beneath it.
Questions for reflection
Does your MES govern manufacturing execution, or mainly display information about it?
Which critical production decisions still occur in spreadsheets, paper forms, meetings, or individual memory outside the Level 3 environment?
When an exception occurs, does the system preserve control and traceability, or does the real process leave the digital model?
#MES #MOM #ISA95 #SmartManufacturing #OperationalExcellence #ManufacturingExcellence #IndustrialDigitalization #ShopfloorManagement #IndustrialAI #BPM #ProductionOperations