How Do the Layers Connect? Data Flow in ERP-MOM-MES Integration and Local ERPs

An order arrives, a work order opens, and then what happens? In our Reverse Look at Work Orders post, we saw how work orders grow through confirmations and change on the floor. In ERP Is Not Lying, Just Speaking Late, we discussed how ERP is built for finance and purchasing, not for real-time shop floor data. What Is MES? Real-Time Shop Floor Data covered the layer that captures actual duration, downtime, and defect data from work order open to close. What Is MOM? Orchestration Layer Above MES introduced the broader umbrella that includes MES and orchestrates production, quality, maintenance, and inventory.

Today we are standing where all three layers meet: Integration architecture.

Three Layers, Three Worlds

ERP, MOM, and MES answer different questions, operate on different time horizons, and speak at different levels of detail.

• ERP (top layer): Plans. “Produce 100 parts, 3 business days, cost X.”
• MOM (orchestration layer): Coordinates. “Synchronizes production flow with quality, maintenance, and inventory.”
• MES (execution layer): Captures reality. “Operation took 15 minutes, 2 millimeters deviation, 5 parts scrapped.”

These three layers complement each other but do not speak the same language. The data flow looks like this:

ERP → MOM → MES → Floor

ERP sends plan and targets downward. MOM contextualizes that plan operationally and establishes coordination. MES tracks operations at the machine level and pushes actual data upward.

This flow is not one-directional. Real data from the floor flows from MES to MOM, then to ERP. This way, the planning team answers “where is the plan?” not with guesses, but with actual data.

Why Integration Is So Hard

ERP and MES/MOM share the same data, but they speak at different time horizons and different levels of detail. ERP tracks “what” was done and “how much” it cost. MES tracks “how” and “when” it was done, capturing the gaps and losses in between.

This distinction becomes especially critical in customer-specific production. Every order arrives with a different route, different operations, and different acceptance criteria. Standard ERP plans become obsolete before they can be used. MES keeps each work order’s actual data, revealing the gap between plan and reality in real time.

MOM takes that data and places it in a broader operational context. What should happen with the quality control result? When a machine needs maintenance, what happens to the order? When stock runs out, how is the production flow notified?

In this scenario, integration is not just data transfer — it is meaning transfer. Operational data from MES is interpreted, correlated, and transformed into a form ERP can understand.

The Extra Layer Required for Local ERP Integration

Local ERPs like Netsis, Odoo, Logo, and Parasut are not as easy to integrate as global brands’ APIs. These systems’ data structures, accounting logic, and reporting formats are shaped by local trade rules.

Embedding production data into these ERPs usually requires a dedicated integration layer:

• Schema adaptation: MES/MOM data must be mapped into fields the local ERP understands.
• Timing synchronization: Real-time production data must be aligned with the ERP’s accounting cycle (usually daily or weekly).
• Error handling: Recovery mechanisms must be in place for data loss, duplication, or conflict.
• Local rules: VAT calculation, stock accounting method, invoicing process — all are ERP-specific.

Without this dedicated layer, rich data from MES and MOM gets compressed into ERP’s coarse-grained world and gets lost.

Where infab.cloud’s ERP Integration Layer Fits

infab.cloud’s ERP integration layer targets exactly this gap. It takes data collected by MES/MOM and transfers it to local ERP in a format it understands, through a natural flow.

The positioning is as follows:

• Input: Receives operation-level actual duration, downtime, scrap, and quality data from MES/MOM.
• Transformation: Adapts this data to the local ERP’s data model. Stock movements, cost calculations, and invoice bases are mapped to the correct schemas.
• Output: Delivers to Netsis, Odoo, Logo, or Parasut in real-time or batch mode.

infab.cloud’s approach aligns directly with MOM’s orchestration needs. Production complexity is preserved while being wrapped in a manageable digital flow.

Why This Matters in Customer-Specific Production

In customer-specific production, every order means a new BOM, a new routing, and new acceptance criteria. Standard planning templates become obsolete before they can be used.

The integration layer must be designed to absorb this variability. Each order’s data must be transferred to ERP in the correct form, linked with quality and maintenance processes before accounting. An integration that forces variable data into fixed field names loses information and creates gaps between production and finance.

Conclusion

ERP knows the plan. MOM orchestrates operations. MES captures floor reality. When these three layers come together, the gap between planning and execution closes.

But closing this gap, especially with local ERPs, requires a dedicated integration layer. This layer translates MES/MOM data into ERP’s language, synchronizes timing, and complies with local business rules.

infab.cloud’s ERP integration layer takes on this task. Production data reaches local ERP through a natural flow; accounting is prepared; planning and the floor speak the same language.

When we wrap up the week, we will address the difficulties of building MES+MOM+ERP integration on your own, and how air-gap/on-prem requirements complicate this further.