Does ISO 22400 define manufacturing operations management (MOM) differently from MES?

ISO 22400 does not create a new, conflicting definition of Manufacturing Operations Management (MOM) compared with MES. Instead, it largely follows the IEC 62264 / ISA‑95 view: MOM is a functional scope, and MES is one of the main categories of systems used to implement that scope.

How ISO 22400 treats MOM vs MES

ISO 22400 is a standards family focused on manufacturing KPIs (for example OEE and related metrics) and how to structure them. When it refers to MOM and related layers, it aligns with the ISA‑95 / IEC 62264 concept of a MOM level that sits between enterprise planning (ERP) and shop-floor control (SCADA, DCS, equipment controllers).

Within that structure:

• MOM is the collection of business and technical functions that manage production, quality, logistics, and maintenance execution at the plant level.
• MES is typically the primary software category that implements many MOM functions, but not the only one. LIMS, APS, maintenance systems, and custom applications can all be part of the MOM layer.

ISO 22400 does not redefine MES itself; it assumes the widely used industry notion of MES as an execution system that carries out a subset of the broader MOM responsibilities.

The practical difference in real plants

In a regulated, brownfield environment, the gap between MOM scope and what your MES actually does can be significant:

• One MES may handle electronic travelers, work-in-process tracking, and basic quality, but leave maintenance, detailed scheduling, or laboratory workflows to other systems.
• Some sites run multiple MES-like systems by line, plant, or product family, which together fulfill MOM functions.
• Legacy or homegrown tools (Access databases, spreadsheets, custom web apps) may carry key MOM functions that are not reflected in the vendor MES brochure.

Seen through the ISO 22400 / ISA‑95 lens, all of these systems, integrations, and procedures form your actual MOM environment. MES is one important implementation component, not the full definition of MOM.

Why this matters for KPIs and ISO 22400

Because ISO 22400 is about KPIs and their relationships, its use of MOM is primarily to:

• Clarify where KPI data should originate in the architecture (for example, MOM vs ERP vs control systems).
• Distinguish between KPIs describing execution (MOM/MES layer) and those about higher-level planning or business performance.

For an aerospace or other regulated operation, that means:

• You should not assume that adopting an MES product automatically gives you a complete MOM layer as envisioned in ISO 22400.
• KPI design and data lineage need to reflect the actual mix of MES, QMS, LIMS, PLM, maintenance, and custom tools in use.
• Traceability, validation, and change control have to be applied across the full MOM scope, not just the MES application.

Coexistence with existing MES and other systems

In long-lifecycle, highly regulated plants, fully replacing MES or rebuilding the MOM layer around a single new platform is rarely straightforward. Qualification burden, integration complexity, downtime risk, and the need to maintain historical traceability often make incremental change the only viable path.

In that context:

• Use ISO 22400 and the MOM concept to map functions and data ownership across your existing MES, ERP, PLM, QMS, and maintenance tools.
• Identify which MOM functions are not covered by your current MES and where KPI data is fragmented or unreliable.
• Plan integrations and changes under formal change control and validation, focusing first on the MOM areas that most affect safety, quality, and regulatory exposure.

This approach treats MOM as the functional blueprint and your MES as one (important) building block, consistent with how ISO 22400 and ISA‑95 use the terms.