What is MOM? The Manufacturing Operations Orchestration Layer

What is MOM?

Yesterday we introduced MES. MES collects real-time data at the machine: hours worked, stoppage time, scrap rate. But as we discussed yesterday, MES alone is not enough to make decisions on the shop floor. What if a work order is designed wrong? Who decides when quality fails? What if maintenance is overdue and material doesn’t arrive on time?

The answer is MOM.

MOM (Manufacturing Operations Management) is a broader coordination layer that wraps MES. It takes the data MES measures and integrates it with production planning, quality management, maintenance, and inventory decisions. In other words: MES collects data; MOM makes decisions with that data and executes them.

MES vs MOM: Execution vs Orchestration

Let’s use an example. Remember work order M-2024-001 from yesterday? MES recorded that it completed in 3.5 hours and produced 5 parts scrapped. So what happens next?

MES perspective: Data is collected. Work order is closed.

MOM perspective: Wait. Five parts scrapped. Why? Was the recipe wrong, operator error, or machine out of adjustment? MES data shows this. Who pays for these 5 parts? Do we credit the customer, or charge the scrap cost to labor? If this work order comes back again, what changes for next time? These are MOM’s questions.

MES is execution—the operational flow is recorded. MOM is orchestration—problems, quality, budget, and human decisions that meet the operational flow are coordinated.

The Four Pillars of MOM

MOM typically covers four areas:

1. Production Operations: From work order open to close, which machine will it go to, what sequence, which operator—these assignments are controlled by MOM. MES only records at the machine; MOM decides. For example, if Machine M5 breaks down, can MOM reroute this work order to Machine M6? Or put it in a waiting queue? MOM compares delay cost against alternative cost and decides.

2. Quality Management: MES measures and records quality parameters. But if a part exceeds customer tolerance, what then? Does it go back for rework, to scrap, or do we tell the customer, “Your promised tolerance has a 2% margin, do you accept it?” MOM coordinates these decisions. Also, if the quality problem should not happen again, MOM talks to design and engineering about recipe or route change.

3. Maintenance and Equipment: MES cannot predict that Machine M5 will break—but it records the downtime after it does. However, MOM can look at predictive maintenance data, machine age, and usage frequency to plan which machine needs maintenance next week. If preventive maintenance happens, breakdown risk drops. MOM coordinates production plan with maintenance plan: “After job A finishes, let’s send Machine M5 to maintenance. Risk is managed and production is not interrupted.”

4. Inventory and Supply: MES records how much material a work order consumed. MOM looks at consumption speed and determines when the next material order should arrive. If material runs out mid-work order, what happens? MOM can foresee this and speak to supply chain. The work order doesn’t stop.

ISA-95: The Industry Standard

If these layers and their decision flows are built ad-hoc, the system becomes complex and error-prone. That’s why global standards exist.

ISA-95 (International Society of Automation) is the standard for integration between industrial process control and operations and enterprise systems.

In ISA-95, production layers are defined as:

• Level 4: Enterprise system (ERP). Finance, sales, procurement, human resources all here.
• Level 3: Production management (MOM). Production plan, work order design, quality and maintenance policies.
• Level 2: Operations control (MES). Real-time data collection and operation control at the machine.
• Level 1: Automation, sensors, machines.
• Level 0: Physical processes.

For example, when ERP (Level 4) says “This month’s target is 10,000 parts,” MOM (Level 3) breaks it into weeks: “Week 1: 2,500; Week 2: 2,500” and converts these into work orders. Then MES (Level 2) executes work orders at the machine. Machine operators collect and record data. Then MES data flows back to MOM; it is checked whether the weekly target was met. If yes, progress is good. If no, the next work order is adjusted.

Implementing MOM

MOM is not just software. MOM is a discipline, a teamwork, a workflow. To start implementing MOM at a company:

1. Data standard: Every work order must be recorded in the same format and detail. Same material with same names, same machine with same number, same operator with same ID.

2. Define responsibility: Who makes MOM decisions? Shop manager? Quality chief? Production planner? If boundaries are left wide open, decision delays and conflicts happen. The ISA-95 framework helps draw these boundaries.

3. Software and data flow: Data flow from MES to MOM, from MOM to ERP should be automatic. If carried manually, errors and delays multiply.

MOM’s Criticality in Demand-Driven Manufacturing

Demand-driven manufacturing makes planning hard. If a customer orders 50 parts at noon on Monday, production may need to start Tuesday morning. Standard manufacturing (say, the same 1,000 units of product A every month) has time for this; demand-driven does not.

Without MOM:

• Shop manager receives the order email, phones an operator, “Switch the machine to this job today.”
• Operator says, “There’s another product on the machine; I need to finish that first.”
• They argue; a decision is made.
• The night shift may get wrong information.
• When morning comes to start, material is not ready.
• Start is delayed.

With MOM (backed by MES data):

• New order is entered into ERP.
• MOM can instantly see machine availability, material stock, operator shifts.
• The optimal start time is found automatically.
• Work order design (recipe, route, standard times) is suggested by the system.
• The operator sees his job on a mobile device at 06:00 morning. He arrives ready and informed.
• Flow is achieved.

Conclusion: MES Data, MOM Decision

Without MES, the shop floor is blind and ignorant.

Without MOM, MES data is collected but never used. Data is gathered but decisions are still made by guesswork.

In demand-driven manufacturing, these two layers must work together. MES captures accurate, real-time data at the machine. MOM takes that data and orchestrates shop floor, quality, maintenance, and supply decisions. This coordination answers every question: should we do this sequence or the next work order, what do we tell the customer about this scrap, why didn’t we meet target last week?

In the coming days, we’ll discuss how these three layers (ERP, MOM, MES) connect.