The BOM That Was Wrong Before The Job Started.
The client manufactured precision machined components for industrial OEMs under strict tolerance and specification requirements. Their product engineering team maintained BOMs in an internal shared drive. The purchasing team maintained a separate version with approved supplier part numbers. The production supervisor maintained a third "working" version that incorporated undocumented floor-level substitutions accumulated over years.
Nobody was wrong, exactly. Each version made sense in its context. The problem was that no single person had visibility across all three — and the moment an engineering change was released, it could take weeks to propagate through all three systems. Or never, if someone forgot a st
- Mapped all three BOM systems and conducted a line-by-line reconciliation across the 22 active BOMs — identifying every discrepancy, substitution, and version drift between engineering, purchasing, and production
- Documented 47 active discrepancies across the BOM ecosystem, 11 of which were directly causing recurring rework on current production orders
- Implemented Odoo Manufacturing with a single-source BOM architecture: engineering BOMs with approved manufacturing variants, each accessible to purchasing, production planning, and the shop floor from a common record
- Built an Engineering Change Order (ECO) workflow — changes enter staging, are reviewed and costed, and only release to production after sign-off, with automatic BOM versioning and audit trail
- Configured a component substitution framework: approved substitutes are documented in the BOM with their conditions, so the floor isn't improvising — they're selecting from a pre-approved list
- Retired all three legacy spreadsheet systems with a documented 30-day parallel-run cutover protocol
- Rework cost dropped 71% in the first 6 months post go-live — from $640K annually to under $190K, with the remaining rework attributable to machine calibration issues unrelated to BOM errors
- Emergency procurement events (rush orders to cover floor-level material substitutions) fell from an average of 14 per month to fewer than 2 — reducing premium freight spend by approximately $78K annually
- Engineering change cycle time — from ECO submission to production floor implementation — compressed from an average of 23 days to 4 days
- All 22 active BOMs now have a single verified version in the ERP, with a complete version history accessible to any user
- First-pass quality rate on production runs improved from 81% to 94% — directly attributable to correct material specs reaching the floor
- A customer audit that had previously flagged BOM traceability as a nonconformance was cleared with zero findings at next review
We had three people who each thought they had the right BOM. They were all right in their own world and all wrong on the shop floor. An ERP didn't make us smarter — it made us look at the same piece of paper for the first time in ten years.— VP of Operations · Precision Manufacturing · Great Lakes, U.S.
Why BOM Fragmentation Is a Revenue Problem, Not Just an Operations Problem
Every time the floor builds from the wrong BOM, someone pays for it. Sometimes it's scrap. Sometimes it's rework labor. Sometimes it's a rush order for the correct material at a 40% freight premium. Sometimes it's a customer nonconformance report that costs a contract. The true cost of BOM fragmentation is almost always underestimated because it hides in three or four different cost buckets — none of which ever get totaled into a single line item. When we reconcile them, the number usually surprises even the operators who knew the problem was there.
