A pharma plant reached a trusted plan without ripping out its ERP
Starting from a CSV, with batch and shelf-life rules and quality holds reflected directly in feasibility, the team went live on its existing stack.
The challenge
The plant had tried a large suite before and stalled in a long, costly rollout. Batch sizes, shelf life and quality holds all shaped what could actually ship, but none of that was reflected in the planning tool. When a batch went on hold, the plan did not know, and promises were made that quality could not keep.
What we did
We bootstrapped from CSV exports of the existing ERP, so nothing had to be ripped out. A company configuration captured batch and shelf-life rules. Statistical process control fed quality status straight into the Feasibility Kernel, so a hold instantly changed what the plan considered buildable. Planners saw the effect the same day, not at month end.
A quality hold used to be a surprise at dispatch. Now it shows up in the plan the moment it happens.
The outcome
The team reached a plan it trusted in a few months, kept its ERP, and cut expedites sharply as promises started matching reality. Because quality and feasibility now share one model, the plan and the floor finally agreed on what could ship and when.
CSV bootstrap removed the rollout risk, and quality holds lived inside feasibility rather than beside it.
Illustrative engagement based on typical outcomes.