Your ERP Is Not Lying, It Just Speaks Late and in Coarse Grains

In Order Arrived, Work Order Opened, Then What? we saw how information scatters across paper, Excel, the foreman’s head, and WhatsApp groups. Today we look at where that scattering has its biggest impact: ERP.

What ERP Is

ERP — Enterprise Resource Planning — is a structure built to unite all of an organization’s resources in a single system. Finance, sales, purchasing, stock accounting, human resources… All rely on the same data pool.

It is excellent at this job. When an order is entered, stock decreases, it is posted to the ledger, collections are scheduled. A purchase proposal is created, a supplier is selected, a payment calendar is drawn. A journal entry is recorded in finance.

ERP exists to do this, and it does. For large enterprises, accounting standards, supply chain management, and financial reporting needs make ERP indispensable. Keeping stock accurate, issuing invoices without errors, collecting payments correctly — these are all fundamental ERP functions. A factory without ERP is almost unthinkable in modern business.

What ERP Is Not

ERP is not a tool for real-time data collection on the shop floor.

Saying this is easy, but for anyone working in a factory, this distinction is vital. ERP does not know — in seconds — how a work order is progressing on the floor, how long an operator has been idle, how many defects are in a part, or which machine went down and when.

Why? Because ERP was not designed for that. For ERP, data is a documented transaction. When a work order closes, all its costs are gathered, inventories are updated, and invoices are issued. This process happens after the work is done.

What happens on the floor has not yet reached ERP.

“Your ERP Is Not Lying, It Just Speaks Late and in Coarse Grains”

This frame sits right in the middle of the problem. ERP does not give false information. The information it gives is not a current photograph of reality.

An example: An order for 100 parts. In ERP, this order appears as “completed.” Meanwhile, on the floor there are 10 defective parts and 5 second-quality pieces. ERP does not know this. Because the work order has not yet been posted, defect records have not been entered, and the quality control form has not been entered into the system.

ERP is not lying. It is simply telling you what happened yesterday evening.

Also, we say “coarse grains.” ERP generally presents daily or weekly totals. What happened in which shift, how much time was lost in which operation — these are not in ERP’s language.

What Is Needed for Real-Time Data on the Floor?

This is where MES — Manufacturing Execution System — comes in. MES captures operation-based actual duration, downtime, and defect data from the shop floor in real time, from work order opening to closing.

We will discuss this in detail in What Is MES?. For now, it is enough to know that ERP and MES share the same data but speak in different timeframes and at different levels of detail.

MES collects data from machine sensors, operator inputs, and automatic counters at the shop floor. A record is created when each operation starts, finishes, or stops. This data drops into the MES in real time. When the work order closes, MES summarizes all these detailed records and validates cost calculations by passing them to ERP.

This distinction is vital in customer-specific production. Every order is a different route, a different sequence of operations. While ERP works with fixed templates, MES tracks each work order’s unique journey.

The Extra Layer Required for Local ERP Integration

Integration with local ERPs like Netsis, Odoo, Logo, and Parasut is not as easy as global brands’ APIs. These systems’ data structures, posting logics, and reporting formats are shaped by local trade rules.

To embed production data into these ERPs, a special integration layer is usually required. The data schema must be adapted, timing must be synchronized, and error management must be established. infab.cloud’s ERP integration layer targets exactly this gap: it transfers data collected by MES/MOM to local ERPs in a format they understand, through a natural flow.

The challenge with local ERPs is that they are primarily focused on accounting and commerce. Manufacturing terms — machine codes, operation sequences, scrap types — simply do not exist in the accounting world. An integration layer bridges this gap. It translates a “15-minute downtime at Machine 5” record from MES into an “idle time record” that ERP can understand.

Conclusion

Saying ERP is wrong or insufficient is not the point. It is the heart of the company’s accounting and management world. But it is insufficient to understand the production floor.

Accepting this insufficiency is the first step. Knowing what ERP can and cannot do is what is needed to place the right systems in the right places in the factory.

Real-time data on the floor, operational decisions, and actual costs — these are not in ERP’s language. So do not misunderstand the interface. It is simply speaking late.

In How Layers Connect, we will discuss how we build the data flow between ERP, MOM, and MES.