MOMManufacturing Operations Management

Manufacturing Operations Management — MOM — is the name ISA-95 Part 3 (ANSI/ISA-95.00.03-2013, internationally IEC 62264-3) gives to the totality of work that happens at Level 3 of the enterprise hierarchy. Where Part 1 of the standard draws the five-level pyramid and names Level 3 "manufacturing operations management", Part 3 opens the box and decomposes Level 3 into four operational domains and eight activity groups that every credible operations platform performs in some form.

The acronym MOM was coined in part to escape the historical narrowness of "MES". For most of the 2000s, an "MES" was understood as a production-execution system: it dispatched work orders, captured operator data and produced a batch record. Quality lived in a separate QMS. Maintenance lived in a separate CMMS. Inventory and warehouse movement lived in a separate WMS. The ERP did costing on top of the four. ISA-95 Part 3 made it explicit that Level 3 is one thing — operations — and that splitting it across four products is a deployment choice, not a fact of nature.

Practically, "MES" and "MOM" are now used interchangeably by most vendors and most regulators. The substantive question is no longer the label — it is whether the platform actually covers the four Part-3 domains, or whether the customer is being sold a production-only system dressed in MOM language. The activity-model section below is the test.

Part 3 splits Level 3 into four operational domains. Each domain has the same internal structure (the eight activities below) — what differs is the subject matter.

The standard's insight is that these four are not independent. A maintenance event on a tablet press affects production scheduling; an OOS in the lab puts a material lot into quarantine and may withdraw downstream finished-goods lots; a dispense weight from the warehouse is an in-process record that the eBMR has to reference. If each domain lives in a separate system, the regulated manufacturer is doing data integration as an audit-time forensic exercise — instead of having it as a first-class property of the operations record.

Inside each domain, Part 3 names eight activity groups that together describe what a MOM system does. They are not steps in a workflow — they are categories of work that run in parallel, all the time, with information flowing between them.

1. Definition management — keep the masters: products, recipes, routings, methods, asset classes, sampling plans, calibration procedures, training matrices. "What it is supposed to look like".
2. Resource management — keep the runtime state of resources: which line, which operator, which balance, which lot, available / quarantined / under maintenance. "What is available right now".
3. Detailed scheduling — turn the Operations Schedule from Level 4 into a finite, executable plan against real resources. Sequence-aware, equipment-aware, qualification-aware.
4. Dispatching — push the next task to the right operator at the right station at the right time. The kiosk queue, the LIMS sample list, the maintenance work-order list.
5. Execution management — own the running task: enforce sequence, capture readings, prompt for in-process checks, escalate deviations, manage holds.
6. Data collection — capture everything contemporaneously: weights, signatures, photos, instrument readings, comments. The ALCOA+ surface area.
7. Tracking — maintain genealogy: which raw lot fed which intermediate fed which finished lot, on which equipment, by which operator, using which method, at what time.
8. Performance analysis — compute the KPIs (OEE, FPY, RFT, MTBF, MTTR, throughput) per ISO 22400 and surface them on the management dashboard.

The relationship between MES and MOM is one of the most-asked questions on industry forums. The short answer: MOM is the superset. MES is the production-domain slice.

Vendor positioning has caught up: most credible "MES" platforms in 2026 cover at least two of the four MOM domains, and the leaders cover all four. The label "MES" persists because customers recognise it; the substance is MOM.

ISA-95 Part 4 (Objects and Attributes for MOM Integration, 2018) extends the Part-2 object model — which standardises the L3↔L4 exchange — to standardise the intra-Level-3 exchange between the four MOM domains. The same four object categories (personnel, equipment, material, process segments) re-appear, with additional MOM-specific objects: operations definition, operations schedule, operations performance, capability, response, plus quality-specific (test, sample, specification), maintenance-specific (work request, maintenance plan) and inventory-specific (lot, location, movement) extensions.

The point of Part 4 is portability: a quality result captured against a sample in the LIMS domain can be referenced by a production-domain batch record without each side reinventing the schema. A maintenance event on a piece of equipment can suspend that equipment in resource management without a custom integration. An inventory move can be triggered by a production segment without an export / re-import cycle.

Part 3 names performance analysis as the eighth activity group of every MOM domain, but it deliberately stops short of standardising the KPIs themselves. That work is done by ISO 22400 (Automation systems and integration — Key performance indicators for manufacturing operations management), published in two parts.

• ISO 22400-1 (2014) — Overview, concepts and terminology. Defines the KPI elements, the time model (loading time, planned production time, actual production time, downtime categories), and the aggregation rules.
• ISO 22400-2 (2014, amended 2017) — Definitions and descriptions for 34 KPIs across the four MOM domains. Includes the OEE family (Availability, Performance, Quality, OEE, NEE, TEEP), throughput, yield, FPY, RFT, scrap ratio, rework ratio, plus maintenance (MTBF, MTTR, Mean Time To Failure) and inventory (inventory turnover, fill rate) KPIs.

A MOM platform that reports OEE without citing 22400-2 definitions is computing one of three different things and not telling you which. The most common subtle error is the Performance ratio denominator: ideal cycle time, design cycle time, and nameplate speed produce three different numbers. 22400-2 forces the question and gives the answer.

MOM is not a regulation, and no health authority requires you to implement a MOM platform. It is, however, the operating model that makes the underlying regulations tractable. The four MOM domains map almost perfectly to the four regulated records most manufacturers have to produce.

The point is that the same operations record — one batch, one work order, one lot — has to support four different regulatory artefacts. A MOM platform that owns all four domains can generate all four from one source of truth. A four-system stitch-up has to reconcile them at audit time, every time.

A defensible MOM implementation does not require a big-bang four-domain go-live. It requires that the architecture support all four from day one and that the deployment sequence reflect the customer's pain order.

1. Domain order — most regulated manufacturers go production first (where the deviation pain is loudest), then quality (LIMS replacement / first-pass-yield closing), then inventory (dispense / weigh, FEFO / FIFO enforcement), then maintenance / calibration last. The order is not theology; the rule is that whichever domain you skip is the one that bites you at the next inspection.
2. Single source of truth — pick one platform that owns the four-domain schema. Do not bolt a separate LIMS to an MES and call it MOM — that is an integration project, and the integration layer is where data integrity breaks.
3. Activity coverage — for each domain, audit the eight Part-3 activities against the candidate platform. If detailed scheduling or tracking or performance analysis is missing, the platform is a system of record, not an operations platform.
4. KPIs to 22400 — define the KPI set up front and bind the definitions to 22400-2. "OEE" without a 22400 citation is a number nobody can defend.
5. ERP boundary — keep MOM at Level 3. Do not absorb purchasing, finance or demand planning — those are Level 4 and have their own systems. The interface stays the Part-2 / Part-5 transaction set.

Mistake 1 — "MOM is just a new word for MES"

If your operations platform covers production only, calling it MOM does not make it MOM. The substantive question is the four-domain coverage. Vendors that lean hard on the relabelling without expanding the scope are doing marketing, not architecture.

Mistake 2 — "We will integrate four best-of-breed systems"

This is the most expensive mistake in regulated manufacturing. Each integration is a custom interface, a custom validation, a custom upgrade path and a custom failure mode. After two years the integration layer is more expensive to maintain than the four products combined, and the regulated record is fragile in a way that is impossible to defend at an inspection.

Mistake 3 — "Performance analysis is a dashboard we will add later"

ISO 22400-defined KPIs require the underlying time model and event capture to be in place from day one. If OEE is bolted on at year two, the back-data is almost always unusable and the KPI is computed on a much narrower window than management thinks. Build the time model with the platform, not on top of it.

Mistake 4 — "Maintenance can stay in CMMS"

If the calibration register is in a separate system, the eBMR has to import it at every batch — and the moment that import lags, you have signed an eBMR against a balance whose calibration was, technically, expired. The cheap fix is to put calibration in the MOM platform and let dispense block when a balance is out of cert. The expensive fix is a 483.

V5 Ultimate is a full MOM platform built against ISA-95 Part 3 and Part 4. The four domains live in one tenant, one schema and one audit trail; the eight activities are covered for each domain; the KPIs report to ISO 22400-2.

• Production — formulas / routings / phase-level execution + electronic work instructions + in-process check + deviation + hold + MMR-snapshotted eBMR / eDHR / batch production record.
• Quality — first-class LIMS (sample login, methods, instrument data, OOS / OOT, CoA), supplier scorecard, inspection plans, two-person e-sig release.
• Maintenance — asset register, PM plans, work-order queue, calibration register with kiosk-blocking on out-of-cert equipment, MTBF / MTTR per 22400.
• Inventory — receipt, putaway, FEFO / FIFO picking, weigh / dispense, move, scrap, quarantine, release, full lot genealogy, license-plate / SSCC support.
• ERP boundary — V5's ERP bridge stays at the Level 3 ↔ Level 4 interface; the operations record is V5's, the financial record is the ERP's, the contract between them is the ISA-95 Part-2 / Part-5 transaction set.