What Is ERP, and What Is It Not? (The Gap Between Office and Shop Floor)
In the previous post, we discussed how order arrival, work order creation, and information scattered across paper, Excel, the master technician’s memory, and WhatsApp create problems. Today let’s look at the root cause: what does an ERP system cover, and what does it leave out?
The ERP DNA
Netsis, Odoo, Logo, Paraşút, SAP — all of them share the same backbone:
- Finance: Revenue, expense, receivable, payable, tax, period close
- Sales: Customer, order, invoice, delivery note
- Procurement: Vendor, quotation, purchase order, goods receipt
- Stock: Inbound, outbound, inventory, warehouse location
- Accounting: Chart of accounts, journal, ledger, balance sheet
- Reports: Profitability, cash flow, budget comparison
In these domains, ERP rules are clear, calculations are correct, and integration patterns are mature. It reliably manages the money side of a factory.
But what happens on the shop floor?
In a make-to-order operation, the day starts like this:
Morning 08:00. The production planner opens the ERP. Three work orders are scheduled for today. The ERP shows:
| Work Order | Product | Qty | Deadline |
|---|---|---|---|
| WO-2847 | Custom gasket | 200 pcs | Today 17:00 |
| WO-2848 | Flange | 50 pcs | Tomorrow 12:00 |
| WO-2849 | Sleeve | 150 pcs | Today 16:00 |
This data is correct. But it does not answer the planner’s real questions:
- Which machine for WO-2847? (CNC-3 is free, CNC-7 is down, CNC-2 is running WO-2849)
- Which recipe for the gasket? (Customer wants NBR instead of FKM this time)
- What is the operation sequence? (This customer wants milling first, drilling second — the standard routing is the opposite)
- Which operator will run it? (Mehmet is on leave, AyĹźe is waiting for another job to finish)
These answers are not in the ERP. They are on paper, on the phone, or in the operator’s head.
Scenario: Work Order Opened, But…
Work order WO-2847 is marked “In Production” in the ERP. At 14:00 the planner returns and checks: still “In Production”. How much progress? Has material been issued? How many operations are done? Any scrap?
The ERP answer: nothing. Just one status: “In Production”. Deadline is 17:00, but at 14:00 the job might be halfway through, or it might not have started yet.
17:30. Work order still shows “In Production”. Why?
What happened on the floor:
- 09:00-10:30: Material waiting (warehouse couldn’t move it to CNC-3)
- 10:30-12:00: First operation complete
- 12:00-13:00: Lunch break
- 13:00-13:30: Second operation started, tool broke
- 13:30-14:30: Tool replaced (no spare on shelf, called procurement)
- 14:30-17:00: Second operation still running
The ERP only shows “Complete” at 17:30. The content of the intervening 9.5 hours is lost.
The Standard Cost vs. Actual Cost Illusion
The work order has a standard cost calculated in ERP:
- Material: 8,000 TL (200 pcs Ă— 40 TL)
- Labor: 4,000 TL (8 hours Ă— 500 TL/hour)
- Overhead: 2,000 TL
- Total: 14,000 TL
But the actual journey:
- Material scrap: 8% (NBR is more expensive, and miscuts happened) → +640 TL
- Broken tool: 1,200 TL
- Extra labor: 2 hours (tool change + milling setup) → +1,000 TL
- Actual cost: 16,840 TL
Difference: 2,840 TL. The ERP cannot see this. Accounting sees the total margin erosion at month-end, but which work order caused it, why, and when cannot be determined.
The World ERP Prefers
ERP is comfortable when:
- Recipes are fixed
- Operation sequences are standard
- Times and scrap rates are known
- Batch production (same product, same steps)
- Few and predictable variables
The Make-to-Order World
- Every order has a different recipe
- Operation sequence changes per customer
- Times and scrap are estimates, not reality
- Every work order is a small project
In this environment, ERP is no more than a piece of paper. Real instructions, real times, real costs stay outside the system.
Conclusion
ERP is necessary for finance, accounting, order, and stock management. But it cannot answer “how do we make this, how long will it takes, what will it actually cost”.
Filling this gap requires real-time data capture on the shop floor, dynamic recipe management, and operation orchestration. We call this MES and MOM.
Tomorrow, in Day 3, we will see what MES is and how it illuminates the dark side of the work order.