ERP, MOM, and MES Integration: Data Flow and Layer Connection

In Order Arrived, Work Order Opened, Then What? we saw how information spreads across paper, Excel, operator memory, and WhatsApp. In ERP Is a Record System, Not a Monitoring System we learned that ERP is built for accounting, purchasing, and stock records — not real-time shop floor tracking. In What is MES? we met the layer that captures actual operation data from start to finish.

Today’s question: how do these layers connect in practice?

The Problem: Disconnected Software Worlds

Manufacturing plants in Turkey typically run an ERP system — Netsis, Odoo, Logo, or Paraşüt. This system handles finance, accounting, sales, and purchasing. But it does not tell you what is actually happening on the shop floor in real time.

Meanwhile, the shop floor manager tracks work orders in Excel, on paper, or via WhatsApp and operator memory. None of this data flows back into the ERP system.

Result: the ERP shows stock as available when the floor says “we cannot find the material.” A work order’s finish time? ERP has no prediction. Quality problem? News arrives late.

Data Flow: Bridging ERP with Shop Reality

Integration means tying ERP to shop floor truth. We’ll break this into three steps.

Step 1: Work Order Flows to the Shop

Production planning creates a work order (WO) in the ERP. The WO carries bill of materials (BOM), operation sequence (routing), planned time, and quantity. This data must flow to the MES layer and appear on a screen, paper, label, or mobile app. The operator or machine follows the WO and records actual start time, end time, quantity completed, and scrap count.

Step 2: Real Data Is Captured and Held in MES

The MES holds shop truth: operation start-stop time, pauses, scrap, interventions. This data comes from manual entry (paper → computer), QR code scan, RFID, PLC, or machine API. MES stores this in a central database.

Step 3: Production Data Flows Back into ERP

MES data passes through the MOM layer — quality, maintenance, inventory are checked — then flows back into ERP. Work order close time, actual cost, stock deduction, and real productivity feed into ERP automatically. Finance can now trust this data for reporting.

Common Integration Architectures in Turkey

Architecture 1: Partial Data Flow (Most Common)

Work order is created in Netsis, Odoo, or Logo. The shop floor knows about it but returns data only weekly via manual report. No real-time sync.

Architecture 2: Custom Bridge (Mid-Level)

A data bridge connects ERP and MES. Netsis API or Logo database is read directly; work orders flow to MES automatically. But the reverse — MES actual cost and stock deduction back to ERP — is still in development.

Architecture 3: Integrated Platform (Rare)

SAP and similar big platforms have ERP, MOM, and MES in one system. Data sync is built in. Few Turkish manufacturers use this (large OEMs, automotive suppliers mainly).

infab.cloud: The Natural Integration Layer

Why is infab.cloud a natural integration layer for this problem?

infab.cloud sits in the middle:

  1. ERP Connections: Plugs into Netsis, Odoo, Logo, Paraşüt, ERPNext via API, database read, or SDK.

  2. Shop Floor Data Points: Machines (APIs, sensors, PLCs, QR scanners) send data directly to infab.cloud.

  3. Data Translation: ERP’s “Work Order” structure is different from MES’s “Operation” structure. infab.cloud translates between the two.

  4. Real-Time Sync: When an operation finishes, MES data triggers ERP stock deduction, cost calculation, and quality report — all at once.

  5. Business Rules: Every plant has different recipes, routings, quality rules. infab.cloud stores these as configuration, not hardcoded.

Real-World Example: Make-to-Order Injection Molding

A plastic injection plant. Customer orders: 500 units, custom color caps, delivery Sept 15.

  1. Sales enters order in Netsis: “Custom Cap, 500 units, by Sept 15.”

  2. Production planning creates WO in Netsis: 2 presses, 3 paint, 2 pack, each operation on a 5-hour route.

  3. infab.cloud reads this WO from Netsis API, translates to MES format.

  4. Shop screen shows the WO. Operator starts the operation; PLC automatically sends cycle count to infab.cloud. If a different color is needed, operator pauses and infab.cloud logs the hold.

  5. When done, infab.cloud records actual time and part count; quality scan via QR is logged.

  6. MOM layer runs: quality and inventory rules are checked: “OK, 498 good, 2 scrap, 1 rework.”

  7. infab.cloud writes back to Netsis: WO closed, 498 delivered, 2 scrap, actual labor 14.5 hours, material cost from actual consumption.

  8. Accountant opens Netsis report: “500 ordered, 498 delivered, cost 2,450 TL” — perfectly accurate.

The Hidden Tension: Speed vs. Data Integrity

Automating data flow speeds operations but raises data quality risk. A sensor misreads? An operator skips a scan? Post-integration auditing becomes even more critical. We’ll explore this in the next post.

Summary

ERP, MOM, and MES cannot work disconnected. While your local ERP (Netsis, Logo, Odoo) handles finance and stock, shop floor tracking in a separate system breaks information into pieces. Integration is the data bridge that ties ERP to shop floor reality and brings data back.

infab.cloud is designed to build this bridge. Compatible with local ERPs, aligned with MES/MOM data standards, and offering real-time sync, it treats your entire production operation as one system.

Most Turkish manufacturers still track work orders in Excel or on paper. The right integration architecture changes that — and makes data useful for real decisions.