Insights & Use Cases
Explore our use cases and insights to learn how optimization can transform your business
The plant hit its tonnage for the month. Board was green, target met. Then margin came in soft, and nobody could name the day it went wrong, because it didn't go wrong on any single day. It leaked an hour at a time.
Here is the root of it, and it is the one thing a discrete factory never deals with. A discrete plant counts: one input becomes one output, quantity conserved. A process plant splits. A ton of feed becomes some product, some saleable co-product, some off-spec, and some loss, and that split is different from one grade, line, and season to the next. Standard ERPs assume a ton in equals a ton out at a fixed yield. Your plant runs a different split for every product, line, and period, and the margin hides in which split you planned for.
In a discrete plant, yield is a scrap rate, a small loss off a known count. In a process plant, yield is what share of the split comes out as sellable product instead of co-product, off-spec, or loss, and that share is not one number. It differs by product, by line, by season. Same ton of feed, different mix. An ERP carries yield as one fixed coefficient and uses it only to net requirements. It cannot represent a split that differs across products and periods, and it cannot weigh the co-product, which is revenue, against the product when deciding what to run.
Discrete yield is a loss off a count. Process yield is a split across several real outputs, and only one of them is the thing you meant to make.
The split has an input side. When feedstock varies, hitting spec is a decision, not a lookup: which inputs, in what proportion, to land on spec at the lowest cost. A discrete plant never faces this. You do not blend bolts. A process plant faces it every lot, because ore grade wanders and recovered streams come back dirty, and the cheapest on-spec blend is different today than yesterday. A fixed recipe can't follow a moving feed, so it leans on premium input to stay safe, which means it runs richer than it had to, every time.
Every time the feed moves, the cheapest on-spec blend moves with it. A static recipe can't follow, so the plant pays for the safety margin.
On a line that can't stop, an hour below the rate you planned for is capacity gone for good, not deferred to next week. That much a discrete line shares. What a process plant has on top of it: each grade and product runs at its own rate and its own yield, so the rate you plan for a given mix is tied to the split you expect from it. Plan the line as one flat rate and one flat yield, and the plan is wrong for every product that isn't average. So a process manufacturer can make its monthly tonnage and still lose, because the plan chased a single volume number instead of the product-by-product split and rate behind it.
Deferred production you can make up. Lost capacity on a continuous line you can't. And a flat rate assumption hides which products were actually worth running.
Yield, blend, and rate aren't three separate plans. They are three sets of constraints on the same plan. The blend you choose, the yield each line and grade will run, and the rate limits you have to respect all bound the same set of decisions, and the best plan is the one that satisfies them together at the lowest cost. A spreadsheet can't find that plan. It works one tab at a time, settling the blend, then the volumes, then the schedule, each step blind to the constraints the others just set. So even your best planner, working flat out, lands on a plan that is feasible but not best, because solving the pieces in sequence can't land where solving them together would. That is not a skill gap. It is what happens when a problem with thousands of interacting constraints is worked by hand, one piece at a time, and the distance between feasible and best is margin, sitting there every month. It also lives in one fragile spreadsheet in one person's head, so when they leave, even the feasible plan gets worse.
The limit is the method, not the planner. Settling the pieces one tab at a time can't reach the plan that satisfies every constraint at once.
WonForge solves it as one optimization, and not just for production. The yield, blend, and rate decisions are planned at the same time as the constraints around them: material availability, tank and storage limits, and shipment restrictions across the network. That is the difference. The split you choose on the line is only right if the raw material is there to feed it, the tank can hold what comes off it, and the shipment can move it on time. Plan production by itself and you get a number that falls apart the moment it meets the rest of the supply chain. Plan it inside the whole chain and every limit holds at once, and the judgment that used to live in one person's spreadsheet becomes a model the business owns.
A production plan is only as good as the chain around it. WonForge plans the split together with material, tank, and shipment limits, so the number you commit to is one the whole supply chain can execute.
In discrete manufacturing, yield is a scrap rate—a small loss off a known unit count. In process manufacturing, yield is the sellable share of a split across product, co-product, off-spec, and loss, and that share differs by product, line, and season—not one fixed coefficient. ERPs model yield as a single number for netting requirements; the plant runs a different split for every product, line, and period.
Blend-to-spec is the decision of which inputs, in what proportion, will land a batch on specification at the lowest cost. When feedstock grade or recovered-stream quality varies, the cheapest on-spec blend changes daily. A fixed recipe cannot follow a moving feed, so plants over-spec with premium inputs to stay safe—and pay for that safety margin on every lot.
Because they are constraints on the same plan, not three separate worksheets. The blend you choose, the yield each line and grade will run, and the rate limits you must respect all bound the same decisions. A spreadsheet settles them one tab at a time, each step blind to the constraints the others just set. The gap between that sequential feasible plan and the plan that satisfies every constraint at once is where margin leaks every month.
A discrete plant counts its output. A process plant splits its feed, and the split differs across every product, line, and period. That is why a process manufacturer can hit every number on the board and still lose margin: the numbers are volumes, but the margin lives in the split that made them. A spreadsheet can describe the split. It can't solve it. Closing the gap between feasible and optimal is the whole opportunity. Want to see whether your plan is chasing tonnage or optimizing the split behind it? Click Check Your Fit and we will take it from there.
We'll tell you in 20 minutes whether we can solve it.
Email: contact@wonforge.com
Based in Wilmington, DE, serving businesses across the U.S.