What is MOM? The Operations Orchestration Umbrella

What is MOM?

Yesterday, we learned about MES. MES records every minute, every scrap—from work order opening to closing. But now the question: Who makes the decision?

A work order was opened and within one hour, 5 pieces were scrapped. Why? Was the recipe wrong, the machine calibration off, operator error? MES just records that 5 pieces were lost—it cannot explain why. But what happens next? Do we write a report to the customer, modify the recipe, retrain the operator, or call the supplier?

This is where MOM enters.

MES vs MOM: Execution Recording vs Decision Orchestration

MOM (Manufacturing Operations Management) takes the data that MES collects and manages production, quality, maintenance, and inventory decisions as one coordinated system. MES executes at the machine level; MOM orchestrates the decisions behind that execution.

Let me give a concrete example. Monday morning, Customer Ahmet orders 100 pieces of Product A. Delivery required by Tuesday morning. What does the shop floor manager think?

Without MOM (traditional shop floor):

• Manager receives the email.
• Calls an operator: “I need 100 pieces of Product A by Tuesday morning.”
• Operator: “That machine is tied up with Product B until this evening.”
• Manager walks the shop floor, asking machine by machine.
• Retrieves the recipe from the filing cabinet (if it’s there).
• Gives an estimate: “Hopefully, 24 hours.”
• By Tuesday morning, it’s clear this won’t make it. Manager tells customer: “Tuesday evening or Wednesday.”
• Start is delayed because materials weren’t prepared.
• Or the machine counts 95 pieces instead of 100 and everyone pretends not to notice.

With MOM (integrated shop floor):

• Order is entered into the ERP.
• MOM (a management discipline supported by software) instantly sees:
  • Machine M3 is running Product B; it will finish at 4:00 PM.
  • Machine M5 is completely idle.
  • Product A recipe is in MES: 4 operations, total 6 hours.
  • Material store has 120 kg of raw material A1 (need 110 kg for 100 pieces).
  • Operator Cetin starts at 3:00 PM; Operator Ayse starts at 8:00 AM.
• MOM recommends: “Set up Machine M5 for Product A on Tuesday at 8:00 AM. Operator Ayse on the schedule at 8:00 AM start. Material stock is sufficient. Estimated completion: 2:00 PM. Delivery ready Tuesday 2:00 PM.”
• The decision is presented to the shop floor manager. He clicks “Approve” or rejects it. If approved:
  • Work order 100 pieces is automatically opened.
  • Material store movement is recorded (110 kg A1 reserved).
  • When Operator Ayse clocks in, her mobile device shows: “Tuesday 8:00 AM, Machine M5, Work Order XYZ-001, 100 pieces Product A, 6 hours expected.”
  • Ayse arrives prepared. Machine starts at 8:00. 100 pieces come out by 2:00 PM.
  • MES records every hour, every stoppage reason, every scrap count.
  • Tuesday 2:00 PM report: “Plan 100 pieces, output 100 pieces. Duration 6 hours. Scrap 0. Customer delivery ready.”

The difference is huge: one scenario has uncertainty and person-dependency; the other has data, preparation, and reliability.

Four Core Areas of MOM

In a make-to-order environment, MOM typically manages four areas:

1. Production Operations

A work order is open. Which machine? Which operator? When to start? MOM determines this. If Machine M3 breaks down, reassign the work order to M5. Or if reassignment is impossible, extend the queue by 4 hours but inform the customer of the delay. MOM dynamically allocates machines, operators, and operation sequences.

2. Quality Management

MES measures piece dimensions. But if it exceeds tolerance, what decision does MOM make?

• Rework: The piece immediately goes to Machine M4 for a correction pass. Time and cost are added.
• Acceptance with deviation: The piece is slightly out of tolerance (±0.1 mm), so consult the customer: “Will you accept this?”
• Scrap: The piece is completely defective. Inform the customer, review the recipe or machine setup, apply lessons to the next batch.

At the same time, if a quality issue repeats, MOM escalates it to engineering and procurement. For example, if raw material A1 from the supplier is always problematic, a supplier change may be decided.

3. Maintenance & Equipment Management

MES recorded 8 hours of Machine M3 usage. But MOM knows this machine is due for maintenance (per manufacturer spec: every 500 hours). MOM is careful about which work orders go to a machine approaching its 500-hour limit. If the work order is minor, the machine goes to maintenance immediately after. This reduces the risk of unplanned downtime.

Additionally, MOM may see predictive maintenance data: vibration sensor signals are increasing, acoustic patterns changing. There is a 60% chance this machine will fail within 72 hours. MOM avoids giving this machine critical work orders in the near future; it assigns smaller, safer jobs instead.

4. Inventory & Supply

MES recorded how much material a work order consumed. MOM saw this and informed the inventory system. Now the system knows: consumption of material A1 is accelerating. 30 kg remains in stock; consumption is 20 kg per day. Stock will run out soon. MOM automatically alerts the procurement department: “Order 200 kg of A1; delivery needed within 3 days, otherwise Friday work orders will be halted.”

If the supplier delivers in 2 days, the plan stays on track. If not, MOM considers sourcing from an alternative supplier or reducing that day’s work orders.

ISA-95: The Industry Standard

If this coordination is done haphazardly, the system becomes chaotic. Who makes the decision? The shop floor manager, the quality lead, or the procurement officer? If they act without knowing each other’s decisions, conflict and delay multiply.

ISA-95 (International Society of Automation) is the standard for industrial automation. It defines data flow and responsibility distribution among production layers:

• Level 4 (Enterprise): ERP. Finance, sales, HR, general accounting. Company-wide decisions.
• Level 3 (Operations Management): MOM. Production planning, work order design, decision coordination.
• Level 2 (Operations Control): MES. Machine-level execution and data collection.
• Level 1 (Device Control): Machine controllers, sensors.
• Level 0 (Physical Processes): Machine, die, workpiece.

Example flow: ERP states, “This month’s target is 50,000 pieces of Product X.” MOM sees this and divides it by week: Week 1: 12,000; Week 2: 12,500; Week 3: 13,500; Week 4: 12,000. Then it converts these targets into work orders. MES executes these work orders at the machine level. Everything is recorded. At week’s end, if the MES report says “Week 2: 11,900 pieces made, target was 12,500,” MOM sees this and may increase Week 3’s target to 13,600 or shift some to Week 4. This way, the monthly target is preserved.

What Does MOM Mean in Practice?

MOM is not software—MOM is the name of a discipline, a workflow, and team coordination. Software helps implement this discipline.

If a factory wants to adopt MOM:

1. Establish data standards: Every work order is entered into the same template. The same material has the same code. Machines are numbered consistently. Operator identities are registered.

2. Define responsibility: Who makes the MOM decision? Does the shop floor manager manually assign machines to work orders, or does the system recommendation apply automatically? Who escalates a quality issue? Who approves a maintenance request? The ISA-95 framework helps draw these boundaries.

3. Automate data flow: If data is manually passed from MES to MOM to ERP, the system breaks. Errors and delays multiply without automation.

Why Make-to-Order Matters

Make-to-order production is very different from planned production. In planned manufacturing (e.g., 5,000 pieces of Product A every month), work is prepared in advance, routes are fixed, recipes are fixed, material orders are predictable. But in make-to-order, every day brings a new order, a new recipe variation, a new urgency.

Without MOM in such an environment:

• Customers always complain: “Why was this 2 days late?”
• The shop floor is never calm: “Three customers want their orders started simultaneously today.”
• Cost control disappears: “This piece cost 45 lira but actually came out to 52 lira.”
• Scrap and defect data are not tracked: “Quality issues keep recurring, but I don’t know why.”

MOM does not solve all these problems; but by providing information and coordination, it allows decisions to be made faster and more soundly.

Conclusion: MES at the Machine, MOM on the Shop Floor

In make-to-order production, this operational sequence works well:

1. MES: At the machine, records the actual time, stops, and quality of each work order. Data must be accurate.
2. MOM: Takes MES data and orchestrates decisions by the shop floor manager, quality lead, maintenance, and procurement. Alerts on variances from plan. If a customer is delayed, MOM finds the root cause.
3. ERP: Takes consolidated results from MOM and posts them to financial accounting. Invoices the customer.

In the next article, we’ll discuss how these three layers exchange data and integrate: How do Netsis, Odoo, Logo, Paraşüt ERPs, and the infab.cloud platform connect?

See also: What is MES? /en/blog/writer-daily-post-gun3-mes-nedir-dongu2-en What is ERP? /en/blog/writer-daily-post-gun2-erp-nedir-ne-degildir-en