One dosing error takes three days to trace—R&D changed the formula, warehouse prepared by old BOM, the shop ran an even older process card. All three files say "latest" and the line collapses under three "latest" versions. Formula and BOM are not document-management problems—they are batch problems: which pot, which work order, which effective version.
Chaos costs more than extra phone calls—it is full-shift scrap, customer complaints, and no change trail at audit.
Versions Must Travel with Batches
Effective dates on calendars are not enough. They must be on work orders: this order locks formula version, BOM version, process card version—no verbal changes after line start. Verbal change is the accident incubator. R&D may continue the next version, but the running batch only moves through deviation documents—no silent overwrite.
- Each version has unique number, effective date, obsolete date, approver.
- At release, freeze all three; changes need new orders or deviation—no hot edits.
- Warehouse prepares by work-order version—not "everyone's assumed latest formula."
- Retain samples, QA reports, batch numbers with version numbers for audit alignment.
Changes Need Effective Points and Rollback Points
New formula trial production must pass before main plan switches. Before switch, old version must still be callable for designated orders—not overwritten into disappearance. Rollback is not failure—it protects in-process batches. The XYN digital intelligence system binds formula, BOM, and work-order batch on one record—shop sees locked version, R&D edits next version, both stop fighting one sheet of paper.
Once version management is clear, line speed returns. When unclear, more overtime means more errors.
