Article
Almost every mid-size manufacturer we talk to already has an ERP, and almost none of them would say the floor is a mystery to them. But "we have data" and "we have visibility" are different claims, and the gap between them is usually invisible until someone asks a question the ERP was never built to answer. Here are five signs that gap exists in your plant.
1. Nobody can answer "where's my order right now?" without a phone call
The ERP can tell you a work order was released and when it's due. It can't tell you which station it's sitting at this minute, or why it hasn't moved since the morning shift change. If answering that question means calling a supervisor and waiting for them to walk the floor, the ERP is planning the work — it isn't tracking it.
2. Your "real-time" dashboard is actually yesterday's data
Plenty of ERP add-on dashboards are built on nightly batch jobs or end-of-shift uploads. They look live because they're on a screen, but the numbers are hours old by the time anyone sees them. If a bottleneck that started at 9am doesn't show up until the next morning's report, that's not visibility — it's a history book with a good UI.
3. Quality holds get discovered after the batch ships, not before
Tolerance checks and inspection results that live in a spreadsheet, a paper log, or a QA tool that doesn't talk to production are checks that happen in parallel with the work, not as part of it. That's how a batch with a known measurement issue ends up shipped — nobody in the loop that could stop it actually saw the number in time.
4. Two people give you two different WIP counts for the same line
When "how many units are at Assembly right now" depends on who you ask and which spreadsheet they last updated, it means work-in-progress isn't tracked at the unit level anywhere central — it's being reconstructed, informally, by whoever you happen to catch. Different people reconstruct it differently.
5. Traceability means opening a folder, not running a query
This is the one that shows up hardest during a customer audit or a warranty claim. If "trace this unit" means physically pulling a paper traveler or searching through scanned PDFs by date range, the ERP's batch and work-order records aren't a substitute for a real per-unit history — they were never meant to be.
What actually closes the gap
None of this means the ERP is wrong or should be replaced. It means the floor needs its own system of record — one that captures what actually happens, station by station, unit by unit, as it happens, and feeds that back rather than trying to infer it after the fact from planning data. That's the specific gap a manufacturing execution system is built to close.