ERP-MOM-MES Integration: How Layers Connect

In the first four days, we described something simple: an order arrives, information gets scattered, the ERP opens a work order, MES collects machine data, and MOM coordinates decisions. But in the real world, these layers don’t run in the same product or solution. Most factories use a separate ERP system like Netsis, Odoo, Logo, or Paraşüt. MES runs in different software, MOM in yet another place. So how does information and decision flow between these layers? When is data synchronized? How much delay is acceptable?

Information Flow Between Layers

In ideal terms, three layers—ERP, MOM, MES—follow each other:

1. ERP prepares the order: Sales order arrives. Is material available? Is capacity suitable? Does the price fit the customer budget? All these decisions happen in ERP and a work order opens.

2. MOM receives the plan: The work order flows into the MOM layer. MOM takes it, plans it into production by considering the right machines, operators, and maintenance windows.

3. MES records execution: The plan from MOM goes into MES. MES, at the machine, the operator receives the instruction, starts, and every second records data: hours worked, quality parameters, downtime, material consumption.

4. Data returns: MES sends collected data back to MOM. MOM checks quality, updates maintenance plan, makes inventory decisions. The result reports back to ERP: work order closed, material accounted, labor hours calculated.

This flow is ideal. But in practice, when these systems run in four different places, integration becomes complex.

Real-World Integration

If you use Netsis, orders close in Netsis. The work order comes out of Netsis. But if the MES software is, say, Wonderware or Phoenix, a bridge between these two systems is necessary. Two options exist:

Option 1: Manual Bridge

You manually take the work order from Netsis and type it into Wonderware. At hour’s end, you take the report from Wonderware and paste it back into Netsis. This is the Gün 1 problem: information scattered across paper, Excel, operator memory. Slow, wrong, and error-prone.

Option 2: API and Database Synchronization

Modern software offers APIs. Netsis (or Odoo, Logo, Paraşüt—all major ERP providers now expose APIs) sends the work order to an API endpoint. The MES system listens to this API and automatically imports it into its own database. The work order runs in MES, data flows every second. When the work order closes, MES automatically sends the result back to Netsis via API. Netsis converts it to material movement, labor hours, processing cost.

This approach is much faster, correct, and traceable. But the problem is this: passing from MES to MOM, from MOM back to ERP, each step is a separate integration, another API endpoint. If MES is one software, MOM is another, and ERP is a third, you need two separate integrations.

Netsis, Odoo, Logo, Paraşüt: The ERP Choice

Commonly used ERPs in Turkey are:

• Netsis: Enterprise-grade, accounting heritage, widespread in chemicals and manufacturing. API support exists but data flow isn’t fast; batch operations are the basis.

• Odoo: Open-source, modular, very open API. Integration is easiest. But on its own it isn’t powerful enough; highly dependent on MES, MOM layers.

• Logo / SAP: For large factories. API, data flow, standardization are excellent. But cost is high and implementation is complex.

• Paraşüt: Accounting-focused, suitable for SMBs. MES, MOM integration is limited; general quality suffers.

Whichever you choose, the questions are the same:

1. Does this ERP have an API for MES, MOM integration?
2. How often is data synchronized? Real-time or batch hourly?
3. If data conflicts (e.g., labor hours differ between Netsis and MES), who decides what’s correct?

Integration Architecture: Middleware and Hub

For small factories, “direct connection” (Netsis API directly to MES API) is sufficient. But for medium and large factories, using a “middleware” or “hub” is smarter.

Middleware connects to ERP on one side and to MES, MOM, Quality, Maintenance on the other. All data flow passes through this hub. Why?

1. Synchronization: The hub ensures that all parties have consistent data. If Netsis and MES differ, which is true? The hub makes this decision centrally.

2. Flexibility: If you switch software (e.g., Netsis to Odoo), you just add another driver to the hub. No need to touch other systems.

3. Audit Trail: All data flow is recorded centrally. Auditors and quality inspectors can see exactly where data came from and when it changed.

Market software for this exists: MuleSoft, Boomi, Informatica—integration platforms. But they’re expensive. Open-source options: Node-RED, Apache NiFi. Or write your own middleware.

The Natural Position of infab.cloud

infab.cloud is designed to occupy the exact space where this integration hub should be.

As a data layer, infab.cloud:

1. Pulls data from ERP: Via Netsis, Odoo, Logo APIs, it fetches work orders, materials, planning data. It normalizes them—each ERP has a different schema—into a common model.

2. Sends data to MES: The MES system at the machine (Wonderware, MEA, Parsec, or even a simple IoT sensor system) receives the work order from infab.cloud, starts, and every second sends data back to infab.cloud.

3. Offers management interface to MOM: The infab.cloud dashboard shows production managers, quality engineers, accountants: real-time work order status, cost, quality, downtime. Decisions can be made.

4. Reports back to ERP: Work order closed, infab.cloud sends it back to ERP. Netsis, Odoo, Logo data is updated. The accountant can see labor hours.

In other words, infab.cloud connects a factory’s four different software systems (Netsis, MES, Quality, Inventory) through a single data layer, ensuring synchronization, consistency, and reliability between them.

Why Is Integration Hard?

If it’s so correct and necessary, why doesn’t every factory have it?

1. Cost: Integration platform software, licenses, development, and maintenance are expensive. SMBs and even medium-sized factories don’t have the profit margin for this.

2. Expertise: Engineers who write these integrations must know Netsis API, MES schema, data connection. In Turkey, this expertise is very limited.

3. Software Vendor Resistance: ERP vendors (Netsis, Odoo) aren’t eager to make integration easy. If the customer starts buying MES software (Wonderware), the ERP vendor’s service door narrows.

4. Data Ownership: Disputes arise over who owns the data. The factory manager wants data to belong to the company. The Netsis vendor wants data to stay in the licensed software. The MES vendor wants MES data in their system. This contention blocks integration.

5. Temporal Misalignment: Work order, data flow, synchronization isn’t “perfectly timed.” Planning in Netsis happens in an hour; execution in MES in five minutes. Managing this time gap and keeping data aligned is technically complex.

Conclusion

Today, ERP-MOM-MES integration isn’t “nice to have,” it’s “necessary.” Netsis, Odoo, Logo, Paraşüt—all major ERPs are opening APIs. But a central layer to bring these APIs together, ensure data synchronization, and manage the whole flow is still missing in most SMBs.

This is why integration layers like infab.cloud exist.

Next, on Gün 6, we’ll discuss the unique challenges of make-to-order production: variable recipes, dynamic routes, actual cost tracking—and the technology needed to solve them.