ERP Is a System of Record, Not a Monitoring System

In Order Arrived, Work Order Opened, Then What? we saw how information fragments across paper, spreadsheets, the foreman’s memory and WhatsApp groups. At the center of that fragmentation sits one place where everyone asks the same question: the ERP.

Planners look at the ERP, find no answer, and pick up the phone. A manager opens an ERP report and cannot find out which operation a work order is currently at. Everyone expects the ERP to answer this question. But the ERP was never designed for it.

Two Different Jobs

A system can do two fundamental jobs, and people constantly confuse them.

Recording: something happened, write down the official entry. An order was entered, stock decreased, an invoice was issued, payment was scheduled. The record system’s question is: what happened, how much, on which account?

Monitoring: where is this job right now, on which machine, in whose hands, how long has it been stopped? The monitoring system’s question is: what is the current state, when did it change, why did it change?

The ERP is built for the first job, and it does that job well. Accounting entries post, stock movements process, ledgers reconcile. When the books close, no number is missing. No other system does this with the same maturity.

But the second job is not in the ERP’s vocabulary. Monitoring demands continuously flowing data. Recording demands a completed transaction. The ERP speaks per transaction: order entered, goods receipt posted, work order closed. What happens on the shop floor in the hours between those events is unknown to the ERP, and nobody expects it to know.

What Forcing the Shop Floor into the ERP Costs

Many factories refuse to accept this distinction. “We already have an ERP, let’s do production tracking there too.” The outcome usually shows up in three forms.

First: delayed, manually entered data. Days after operations actually finish, a shift supervisor batches the entries. The system is technically up to date, but the information inside it has gone stale. Nobody trusts that data when a decision has to be made.

Second: resistance from the floor. Asking a machine operator to enter every stoppage and every scrap into the ERP is not a discipline that survives real production. The operator’s actual job was making parts, not typing data. Entries are skipped, half-done, or jotted on paper with a promise to “enter it tonight.”

Third: shadow systems multiply. When the ERP falls short, everyone builds their own workaround. Planning keeps its own spreadsheet, foremen keep notebooks, customer service tracks orders in a WhatsApp group. The distance between the official system and the real operation grows. This is exactly where the fragmentation from Order Arrived, Work Order Opened begins.

All three share one property: none of them is the ERP’s fault. The mistake is asking the wrong system the wrong question.

Which Questions Does the ERP Actually Answer?

Let us make this concrete for a customer-specific order:

Questions the ERP can answer: How much will we collect on this order? Which material did we buy from which supplier at what price? What is the accounted cost of this work order? What is in stock?

Questions the ERP cannot answer: Which operation is this work order at right now? Why did the machine stop during last night’s third shift, and for how long? At which operation did scrap occur, and why? How complete is this order as of today?

The second group shares a common trait: every question asks about “right now, per operation.” The ERP’s time resolution is the transaction, not the operation.

I previously wrote that your ERP is not lying, it just speaks late and coarse-grained. This piece looks at the same truth from another side: the ERP speaks late because it is a recording system, not because it fails at being a monitoring one.

The Right Placement

The solution is not to fake a monitor out of the ERP. It is to give each system its own job.

On the shop floor you need a layer that collects continuously flowing data: actual durations, stoppages and scrap per operation, from work order opening to closure. I covered that layer in detail in What Is MES?

The ERP’s role stays clear: orders, purchasing, stock, invoicing and accounting. The MES turns the actual shop floor data into transactions and feeds them to the ERP. As a result, ERP records are both accurate and close to real time. Nobody is forced to type shop floor data into the ERP, and nobody has to make decisions off a stale report.

In short: the ERP is the factory’s memory, not its eyes. Let it do the job it was built for, and stop forcing it to watch.