What is MOM? The Layer That Orchestrates Production

What is MOM?

For three weeks you have been facing the same problem: the shop floor manager does not know which job to start every morning. One customer says urgent, another says urgent. Both want the same machine. Which one goes first? Who decides?

The answer lies in MOM.

MOM (Manufacturing Operations Management) is the layer that takes the data recorded by MES and orchestrates production, quality, maintenance, and inventory decisions together. MES answers “what happened?” at the machine. MOM asks “what do we do next?”

Let’s walk through a scenario.

Scenario: Two Urgent Orders, One Machine

Wednesday morning, two customers call at the same time. The first needs 50 pieces of Product B by Thursday evening. The second needs 30 pieces of Product C by Friday morning. Both products run on Machine M7. Machine M7 is currently running Product D, finishing tomorrow at noon.

What does shop floor manager Mehmet do?

With MES, without MOM:

Mehmet sees in MES that Machine M7 will finish Product D tomorrow at noon. But which goes first, B or C? B is 50 pieces, 4 hours. C is 30 pieces, 3 hours. B is more urgent (Thursday evening) but takes longer. C is less urgent (Friday morning) but shorter.

Mehmet decides: let us do B first, it is more urgent. But then Customer C cannot take delivery Friday morning, it slips to Friday evening. The customer gets angry. Or if he had decided the other way, Customer B would have been late.

Mehmet makes this call based on experience and gut feel. But what if Mehmet gets sick? Takes a vacation? Leaves the company? That knowledge and experience leave with him.

With MOM:

The MOM system sees:

MOM’s recommendation: “Start Product B tomorrow at 12:00. It finishes in 4 hours, ready for delivery Thursday at 16:00. Start Product C at 16:00 Thursday. It finishes in 3 hours, ready for delivery Friday at 09:00. Both customers get firm delivery dates.”

Mehmet approves. The system automatically:

The difference: the decision is no longer in Mehmet’s head, it is in the system. Even if Mehmet is out, someone else with system access can make the same call.

MOM’s Four Coordination Arms

MOM orchestrates decisions across four domains:

1. Production Operations: Which machine, which sequence?

MES records how long a work order takes at the machine. But MOM decides which machine it runs on. If two machines are suitable, which one? MOM looks at cost, time, and capacity. Machine M3 produces 40 pieces per hour, Machine M5 produces 30. But M3 is currently loaded, M5 is relatively free. MOM assigns less critical jobs to M5, urgent and large jobs to M3.

2. Quality Management: What happens when a part is out of tolerance?

MES records the measurement. 10.2 mm came out, tolerance is 10.0 ± 0.1 mm. Out of tolerance. Now what?

MOM makes these decisions. And if the same quality issue occurs a third time, MOM automatically escalates to engineering: “Product A’s 3rd operation has produced out-of-tolerance parts in the last 5 work orders. Check recipe or machine settings.”

3. Maintenance Management: When do we schedule maintenance?

MES recorded that Machine M3 has run 480 hours. Manufacturer’s instruction: maintenance every 500 hours. MOM sends a warning at 20 hours to go: “Machine M3 needs a maintenance window next week. Which day is free?”

But MOM does not just look at the calendar. It also looks at the production plan. “Three large jobs are scheduled for Machine M3 next week. If we do maintenance Monday, these jobs slip. If we do Wednesday, there is a small job that day, we can move it to M5 and do maintenance Wednesday.”

A human would struggle to coordinate this. MOM does it.

4. Inventory and Supply: Will material arrive in time?

MES recorded that the work order consumed 110 kg of material. MOM sees this and updates inventory. “Material A1 stock is at 40 kg. Consumption rate is 20 kg per day. It runs out in 2 days. But the C order needs 60 kg in 2 days.”

MOM automatically generates a purchase request: “Material A1, 200 kg, deliver by Monday at latest.” The supplier delivers Monday. The C order starts Wednesday. Everything on schedule.

ISA-95: The Standard Framework

If you do all this coordination separately, ad hoc, you get system chaos. Who decides? The shop floor manager? The quality manager? The maintenance chief?

ISA-95 draws these boundaries:

This hierarchy shows data flowing upward, decisions flowing downward. ERP sets the monthly target. MOM breaks it into work orders. MES executes at the machine. MES data goes to MOM, MOM sends consolidated data to ERP.

MOM’s Place in Make-to-Order Manufacturing

In make-to-order manufacturing, every job is different. Recipe changes, operation sequence changes, material combination changes. This variability makes MOM critical.

In repetitive production (same product, same quantity, same route), you can get by without MOM. But in make-to-order:

Without MOM, all these decisions stay in people’s heads. People get tired, make mistakes, leave. MOM makes these decisions systematic.

Conclusion: MES Executes, MOM Orchestrates

MES records every second a work order spends at the machine. You cannot make decisions without this data. But data alone is not enough. You need to turn data into decisions.

MOM steps in right here. It takes MES data and orchestrates production, quality, maintenance, and inventory decisions. It ensures decisions are consistent, repeatable, and traceable.


Previously: What is ERP? What It Is Not and What is MES?