Manufacturing Execution and the Plant Floor Stack
The acronyms describe layers, not competitors. A control system runs the equipment, an execution system runs the order through the plant, and an enterprise system runs the business. ISA-95 exists to define where each stops.
These are layers, not alternatives. SCADA does not compete with an MES any more than a steering rack competes with a route planner. Each works on a different time horizon.
MOM is broader than MES. Execution is one activity within operations management, which also covers scheduling, maintenance, quality, and inventory.
ISA-95 settles the boundary question. Its value in a project is less the object models than the shared vocabulary for deciding which system owns which responsibility.
OEE is three numbers, not one. The headline hides the factor that moved, and the denominators are chosen locally, which is why cross-plant comparison misleads.
Build versus buy is a real question here. Many plants run homegrown systems successfully, because a package that forces process change can cost more than it saves.
Market overview
The short answer
A manufacturing execution system runs the production order through the plant: it dispatches work, presents instructions, collects data from equipment and operators, records genealogy and traceability, manages quality events, tracks downtime and equipment effectiveness, and in regulated industries produces the electronic batch record. Manufacturing operations management is the broader term, encompassing execution alongside detailed scheduling, maintenance, quality, and inventory operations. Below both sit the control systems that physically run the equipment, and above them sits the enterprise system that plans the business. ISA-95, published internationally as IEC 62264, exists to define where each of those responsibilities stops, and most integration disputes on a plant floor turn out to be arguments about a boundary that standard already draws.
What does an MES do, and how is MOM broader?
The functional core of an MES is the production order and what happens to it. The system receives orders from the planning layer, dispatches them to work centers, and sequences the work at a level of detail the enterprise system does not attempt. It presents work instructions to operators, including revision-controlled documents where that matters. It collects data, both automatically from equipment and manually from operators, which is what allows everything downstream to exist.
From that collected data come the capabilities buyers usually name first. Genealogy and traceability link finished output back to the specific inputs, equipment, and personnel involved, which is what makes a targeted recall possible instead of a broad one. Quality management captures inspections and non-conformances against the order rather than in a separate silo. Downtime tracking and equipment effectiveness reporting quantify where capacity is going. Labor and machine tracking supports both costing and scheduling. In regulated industries the electronic batch record assembles all of this into the reviewable document the process requires.
Manufacturing operations management is the wider frame. In the ISA-95 formulation, operations management spans production, quality, maintenance, and inventory as four parallel activity areas, each with its own definition, scheduling, dispatching, execution, tracking, and analysis. Execution of production is therefore one activity inside one of four areas. In commercial terms, a vendor describing a MOM platform is usually describing an MES plus some combination of detailed scheduling, maintenance management, and quality management on a shared data model.
The distinction matters commercially rather than academically. A plant with an execution problem and a maintenance problem can buy two products or one, and the integration burden differs sharply between those choices. Naming which of the four operations areas are actually in scope prevents the common outcome where an execution deployment is judged against expectations it was never scoped to meet.
Where do SCADA, the historian, ERP, and WMS stop and start?
Four neighbors, four boundaries. Below the execution layer sit the control systems: programmable logic controllers and distributed control systems that directly sense and actuate, and supervisory control and data acquisition systems with their operator interfaces sitting above them. These work in seconds and minutes, they are concerned with the state of the process right now, and they have no concept of a production order or a customer. An MES asking a control system what it is doing is asking a question the control system can answer; an MES asking why is not.
Figure 1. The level model. The right-hand column gives the planning horizon each layer works on, which is the underlying reason they are separate systems rather than a design preference. The dashed line is the enterprise to operations boundary ISA-95 exists to define.
The process historian sits alongside the execution layer rather than beneath it. It is a time-series store optimized for high-frequency process data, and it answers questions about what a measurement did over time. It is frequently confused with an MES because both consume plant data, but a historian has no notion of an order, a specification, or a disposition. Plants commonly run both, and the useful division is that the historian holds the signal and the execution system holds the context.
Above sits the enterprise system, planning in weeks and months, holding the order, the bill of material, the cost, and the financial record. The boundary here is the one ISA-95 was principally written to define, and it is where most integration effort is spent. Finally, the warehouse system meets the execution system at the material handoff: the warehouse is responsible for material until it is issued to production and again once finished goods are received. Disputes about who owns work-in-process staging areas are the practical form this boundary takes, and they are worth settling in design rather than in commissioning.
Table 1. The stack by level. The historian sits alongside Level 3 rather than within the hierarchy, and the warehouse system meets it at the material handoff rather than at a level boundary.
What is ISA-95, and why does it matter for integration?
ISA-95 is the standard for integrating enterprise and control systems, published internationally as IEC 62264. Its first part, covering models and terminology, was revised recently, and further parts cover the object model attributes, the activity models of manufacturing operations management, and related material. A buyer does not need to read the standard to benefit from it, and should know three things it provides.
The first is the level hierarchy described in the previous section, which draws on the Purdue reference model. Its practical use is as a decision aid: when two vendors both claim a capability, asking which level it belongs at usually resolves the argument faster than comparing feature lists. SCR's guide to operational technology security uses the same model for a different purpose, and readers concerned with segmentation and network boundaries should read that page rather than this one.
The second is the object models: standardized ways of describing personnel, equipment, material, and process segments. Their value is that they give two systems a shared idea of what a piece of equipment or a material lot is, which is precisely what integrations usually lack. The third is B2MML, an XML implementation of the standard's models, which provides a concrete message format rather than only a conceptual one.
What ISA-95 does not do is tell you which product to buy or how to configure it. Its contribution to a project is vocabulary and boundary, and that contribution is larger than it sounds: a substantial share of integration cost on plant projects comes from two teams discovering late that they held different assumptions about which system owns a responsibility. Establishing that in the design phase against a common reference is inexpensive; discovering it during commissioning is not.
How should I measure OEE, and why can't I compare plants?
Overall equipment effectiveness is the product of three factors: availability, performance, and quality. Availability is the share of scheduled time the equipment was actually running. Performance is the share of theoretical output achieved while running, measured against an ideal cycle time. Quality is the share of output that was good first time. The measure originates with Seiichi Nakajima's work on total productive maintenance, and his widely quoted world-class benchmark of eighty-five percent is built from roughly ninety percent availability, ninety-five percent performance, and effectively perfect quality.
The first discipline is to report the three factors rather than the product. An OEE of sixty percent says nothing about what to do; the same sixty percent produced by poor availability and by slow running call for entirely different responses. Organizations that report only the composite deprive themselves of the diagnostic the measure exists to provide.
The second discipline is to recognize how easily each factor moves without anything improving. Availability depends on the definition of scheduled or planned time, and narrowing that denominator by excluding categories of stoppage raises the number without changing the plant. Performance depends on the ideal cycle time, and setting that target conservatively makes ordinary running look excellent. Quality depends on what counts as a defect and when rework is netted. None of this requires bad faith; local definitions are set by local teams for local reasons, and they diverge.
Table 2. The three factors. The manipulation column describes ordinary definitional variation as much as deliberate distortion, which is exactly why the numbers are not portable between sites.
The conclusion follows directly: cross-plant OEE comparison is usually invalid, and league tables of site OEE tend to reward definitional creativity rather than operational improvement. What OEE supports well is comparison of one asset against itself over time, on a fixed definition, with the three factors visible. Where a corporate function needs comparability across sites, the definitions themselves have to be standardized and audited first, and that is a substantial governance exercise rather than a reporting configuration.
What do regulated industries require, and what is validation?
In life sciences and other regulated manufacturing, the execution system becomes a regulated record system, which changes the project fundamentally. In the United States, the relevant rule is the Food and Drug Administration regulation on electronic records and electronic signatures, which sets the criteria under which electronic records and signatures are considered trustworthy, reliable, and equivalent to paper. It does not create new record-keeping obligations; it governs how records required by other regulations may be kept electronically. Practically it drives requirements for audit trails, access control, record integrity, and signature manifestation.
The agency finalized guidance on electronic systems, electronic records, and electronic signatures in clinical investigations in late 2024, taking a risk-based approach. In the European Union, the corresponding expectations for computerized systems in good manufacturing practice sit in Annex 11 of the GMP guidelines, whose current published revision dates from 2011, with draft revisions and a proposed new annex addressing artificial intelligence issued subsequently and expected to be finalized. Anyone building a compliance case should confirm the current status of both before relying on them.
Validation is the activity that demonstrates the system does what it is specified to do and will continue to. In practice it follows a qualification sequence covering installation, operation, and performance, supported by documented specifications and traceability between requirement and test. The widely used industry framework is GAMP 5, published by ISPE and now in a second edition, which categorizes software by type and directs effort according to risk rather than applying uniform rigor to everything. The regulatory direction of travel, expressed through computer software assurance thinking, points the same way: concentrate testing where patient or product risk is highest.
For a buyer the consequence is a cost and schedule reality that unregulated plants do not face. Validation effort is substantial, it recurs on change, and it constrains how freely the system can be modified after go-live. A vendor's claim that a product is compliant should be examined carefully, because compliance is a property of a validated implementation in a specific process rather than of software in the abstract. What a vendor can legitimately offer is a product built to support validation and a documentation package that reduces the effort.
The fair case against a large execution deployment deserves stating. A modern enterprise system with shop-floor modules, a historian, and targeted effectiveness tooling covers many plants adequately at lower cost and risk, and a homegrown system built around how a plant actually works can outperform a rigid package that forces process change to fit it. Execution projects have a long history of over-scoping and disappointing returns. The defensible position is that the buy case strengthens with regulatory burden, traceability depth, and plant complexity, and weakens without them.
Frequently asked questions
What is the difference between MES and MOM?
Manufacturing operations management is the broader frame, spanning production, quality, maintenance, and inventory operations. A manufacturing execution system is principally concerned with executing the production order. In commercial terms a MOM platform is usually an execution system plus some combination of scheduling, maintenance, and quality on a shared model.
Is SCADA the same as an MES?
No. SCADA is supervisory control, working in minutes and concerned with the state of the process now. An execution system works in shifts and days and is concerned with the production order, its genealogy, and its quality. They are adjacent layers with different time horizons, not competing products.
Do I need a historian if I have an MES?
Frequently yes. A historian is optimized for high-frequency time-series process data and answers questions about what a measurement did over time. An execution system holds order context. Many plants run both, with the historian holding the signal and the execution system holding the meaning.
What is ISA-95 and do I have to follow it?
It is the standard for integrating enterprise and control systems, published internationally as IEC 62264. Nothing compels compliance, and its value in a project is the shared vocabulary and boundary definitions that prevent two teams from holding different assumptions about which system owns what.
What is B2MML?
An XML implementation of the ISA-95 models, providing a concrete message format for exchanging the standard's object definitions between systems. It is useful when integrating products from different vendors that both claim ISA-95 alignment.
What is a good OEE score?
Nakajima's world-class benchmark of about eighty-five percent is widely quoted and is a target from total productive maintenance rather than a universal standard. What matters more is the trend of the three factors on a fixed definition, since the composite alone does not say what to fix.
Why can't I compare OEE across plants?
Because each site chooses what counts as scheduled time, what the ideal cycle time is, and how rework is treated. Those choices move the number substantially without anything changing on the floor. Comparability requires standardizing and auditing the definitions first, which is a governance exercise.
Does the electronic records regulation apply to me?
It applies where you keep records electronically that are required by other regulations, principally in life sciences and regulated manufacturing. It does not create new records; it sets criteria for audit trails, access control, integrity, and signatures so that electronic records are treated as equivalent to paper.
What does validation involve?
Demonstrating that the system does what it is specified to do and continues to, through a qualification sequence covering installation, operation, and performance, with traceability from requirement to test. The GAMP framework directs effort by software category and risk rather than applying uniform rigor.
Should I build or buy?
Both are defensible. Homegrown systems built around actual plant workflows can outperform rigid packages, and many plants run them successfully. The buy case strengthens with regulatory burden, traceability depth, and complexity, and weakens where the package would force process change to fit it.
Method, sources, and where to go deeper
Method
The reference architecture in sections 03 and 04 follows the ISA and IEC standards directly rather than vendor interpretations of them, and notes where part editions differ.
Regulatory material follows the Food and Drug Administration and European Commission sources, with the current status of pending revisions flagged rather than assumed.
The OEE treatment follows the originating total productive maintenance literature and peer-reviewed reviews of the measure, rather than vendor explainers, which were used only to confirm current market usage.
Supply Chain Research is independent and vendor-neutral. We accept no payment from the vendors or categories covered, and this page names no products.
Caveats
SCR publishes no benchmark for equipment effectiveness improvement, downtime reduction, or scrap reduction from an execution system. The percentages circulating in this market originate with vendors and carry no disclosed baseline or method.
The eighty-five percent world-class benchmark is attributable to Nakajima's total productive maintenance work and should be cited as a target from that tradition rather than as an industry standard.
Standard editions differ by part. The first part of ISA-95 was revised recently while other parts carry earlier dates, so confirm the applicable edition before writing it into a specification.
Regulatory status is as of August 2026. Revisions to the European computerized systems annex and to guidance on software assurance were in progress and should be reverified.
Figure 1, Table 1, and Table 2 are structural summaries rather than measured research findings. Nothing on this page is regulatory or validation advice.
Where to go deeper
Readers concerned with securing these systems rather than integrating them should read the SCR guide to supply chain cybersecurity and operational technology security, which uses the same layered model for segmentation and should not be duplicated here. The digital twin guide covers simulation built on plant data. The guide to MRP versus ERP versus APS covers the planning logic that generates the orders an execution system receives, and the WMS, WES, and WCS guide covers the warehouse systems that meet it at the material handoff. Readers scoping across categories should start with the SCR supply chain software category map.
Sources
Sources
- International Society of Automation. ANSI/ISA-95. 00.01, enterprise control system integration, models and terminology. Primary standards body. The current edition of the first part.
- International Society of Automation. The ISA-95 standard overview. Primary standards body. Structure of the parts and their scope.
- International Society of Automation. Announcement of the updated ISA-95 standard. Primary; establishes the revision date of the first part.
- US Food and Drug Administration. Electronic systems, electronic records, and electronic signatures in clinical investigations, final guidance. Primary regulator source.
- Federal Register. Notice of the final guidance on electronic systems, records, and signatures. Primary.
- Electronic Code of Federal Regulations. Title 21, Part 11, electronic records and electronic signatures. Primary regulatory text.
- MESA International. Manufacturing execution and operations management definitions. Professional association, member funded. Authoritative on category definitions, with a membership interest.
- Peer-reviewed review of overall equipment effectiveness. Review article covering the measure and its critiques, citing Nakajima and later literature. Academic; used for the definition and the documented weaknesses of the measure.
- Kneat. Explanation of the GAMP framework and its software categories. Interested source: a validation software vendor. Cited only for an explanation of the framework's structure.
