What Is MOM?

Back to Blog

The Four Areas of MOM

ISA-95 frames MOM around four operational activities. Production operations management covers scheduling, dispatching, and executing production. Quality operations management handles testing, inspections, and quality records. Inventory operations management tracks materials and product movement. Maintenance operations management coordinates the upkeep of equipment - work orders, preventive maintenance, and reliability data.

MOM is the wider view; MES is often the production-focused engine within it. In practice the terms overlap heavily, and vendors use them loosely. The useful distinction is scope: when someone says MOM, they usually mean the complete operations picture across production, quality, inventory, and maintenance; when they say MES, they usually mean the production-execution core. Both live at ISA-95 Level 3, drawing real-time data from control systems and exchanging plans and results with enterprise ERP.

MOM in Context

The point of MOM as a concept is integration. Rather than treating production, quality, inventory, and maintenance as disconnected systems, MOM frames them as one coordinated operations layer with a shared model of the plant. That coordination is what lets an operation see, for example, how a maintenance backlog is affecting production quality, or how inventory constraints are driving scheduling decisions.

In oil and gas, few operators run a formal MOM suite by that name, but the same activities exist: production accounting, measurement and quality, materials management, and maintenance all coordinate around the field. The real-time foundation for all of them is field data, which is where SCADA sits. A cloud SCADA platform such as Merobix supplies that live data - polled from field devices over Modbus, DNP3, OPC UA, and other protocols - to whatever Level 3 systems consume it.

The Level 2 Data MOM Runs On

Every MOM activity is downstream of field data, and the quality of that feed decides whether Level 3 is analysis or archaeology. Production operations need run status, counts or flow totals, and rates. Quality needs process measurements captured with timestamps that can be tied to what was being produced at the time. Inventory needs movements: tank levels, meter totals, transfers. Maintenance needs run hours, starts and stops, and the condition signals - vibration, temperatures, currents - that drive condition-based work. All of it originates at Level 2, the control and monitoring layer described in ISA-95 levels in practice.

The integration work is less about moving bytes than about context. A flow total is useless to production accounting until it is tied to which product, which order or well, and which time period; a downtime event is useless to maintenance until it is tied to equipment identity and a reason code. That context layer - consistent equipment naming, time discipline, agreed definitions of events - is the real interface between Level 2 and MOM, and it is where most integrations actually fail.

Anchor Everything to the Equipment Hierarchy

The four MOM areas coordinate only if they describe the plant in the same terms, and the shared vocabulary ISA-95 provides is the equipment hierarchy: enterprise, site, area, line or unit, equipment. When production counts, quality results, material movements, and work orders all reference the same hierarchy nodes, cross-area questions become queries - what did the maintenance backlog on this unit cost in output - instead of reconciliation projects.

This is the highest-leverage early decision for any operation moving toward MOM: define the hierarchy once, get the field tag database, the maintenance system, and the reporting layer to use it, and resist letting each system keep its own naming. Renaming equipment across systems later is among the most expensive kinds of cleanup in operations IT, because every historical record on the old names loses its meaning.

How MOM Footprints Actually Grow

Very few plants buy a MOM suite on day one. The realistic path starts with point systems - a maintenance package here, a quality database there, production reporting out of spreadsheets - each solving a local pain. MOM as a discipline enters when the seams start to cost money: production numbers that disagree between the control room and the business system, downtime that maintenance and operations classify differently, inventory the scheduler cannot see. Consolidation then follows the pain, area by area, rather than arriving as one big program.

MOM area	Typical point system	Core records
Production	Execution and scheduling tools (MES)	Orders, counts, downtime
Quality	Laboratory and quality systems	Samples, tests, dispositions
Inventory	Materials and warehouse systems	Movements, balances, genealogy
Maintenance	Maintenance management systems	Work orders, history, spares

The right-hand column is the tell: if two systems both claim to own the same record type - two places downtime lives, two places counts live - the integration is not done, whatever the architecture diagram says. One system of record per record type, with everything else reading from it, is the practical test of a working MOM layer.

Signs an Operation Needs MOM Discipline

The need rarely announces itself as a request for MOM. It shows up as symptoms: the daily production number takes hours of spreadsheet work to produce and still gets challenged in the morning meeting; the same downtime hour is categorized differently by operations and maintenance; quality holds are managed by email; nobody can state what a recurring equipment problem has cost. Each symptom is a coordination failure between activities that MOM exists to coordinate.

The remedy does not have to start with software selection. Agreeing on the equipment hierarchy, standardizing downtime reason codes, and putting one owner on each number - who publishes the official count, from which source - delivers a large share of the benefit and makes any later software project dramatically cheaper, because the operational model the software must implement already exists on paper.

Frequently Asked Questions