Order Arrived, Work Order Opened, Then What?
An order arrived. A work order opened. Then what?
In customer-specific production, every order is unique. BOMs change, routes change, control points change. These changes happen fast and are often communicated verbally. Written record systems, fixed forms, and approval mechanisms are not built for this pace of change.
To understand what happens next, follow Order #247 through the shop floor.
Intro: Everything Looks Clear in the System
Order #247 was a custom industrial control panel. The BOM was approved, operations were listed, machines were assigned, and the schedule was finalized. The work order was entered into the system. Everyone had the same information — for that moment.
1. Revision Arrived by Email Only
Two hours after the order opened, the customer requested an additional contactor group. The sales rep mentioned it in a reply email to the customer. It never entered the work order system or the BOM. The production plan stayed the same.
The information lived in the email thread. The work order never saw it.
When production started, the missing part caused a shortage. Extra assembly was needed. Delivery slipped by two days.
2. Routing Changed on a Phone Call
Production began. When the first part was mounted, the operator noticed the primary machine was down. He called planning. Planning approved switching to the secondary machine. But the change was discussed on a phone call. The work order and production screen still showed the original routing.
Three operators worked two different sequences. The work order did not reflect the conflict.
3. Drawing File, Two Versions Apart
The technical drawing was updated to Order_247_v2.pdf. But the production screen still displayed Order_247_v1. The assembly station downloaded the old file. The first two parts came out with incorrectly sized holes.
Scrap increased. Rework started. The system’s drawing was updated, but the production screen was not.
4. Quality Added an Unwritten Test
The customer required a 100% amperage test for this batch. Quality heard about it, but nobody updated the work order. Production moved forward, and when the test station was reached, the special equipment was not there.
The batch was rejected. When rework began, the system still showed the original requirements.
5. Packaging Chose the Old Label
The final part was completed. Packaging used the old label template from the system. The barcode carried the old part number. Logistics shipped to the wrong address.
The customer refused delivery. Return and re-shipment took several days.
Why Does This Chaos Persist?
Customer-specific production is inherently variable. BOMs change, routes change, control points change. These changes happen fast and are often communicated verbally. Written systems, fixed forms, and approval workflows were not designed for this tempo.
The result: everyone works from a different reality. The work order tries to become the single truth — an aggregation of all these fragments — but it usually fails.
What Changes When Information Reunites?
Every scattered piece eventually becomes a cost: defects, rework, scrap, late delivery. But the cost is not only financial. Trust erodes — the operator’s trust in planning, the customer’s trust in delivery, and the team’s trust in each other.
What ERP Is and What It Is Not looked at what ERP actually covers and why it speaks late. What Is MES? showed how real-time shop floor data gets captured from work order open to close. How Do the Layers Connect? will examine how ERP, MOM, and MES fit together — and why an integration layer is the natural home for solving exactly this information-scattering problem.