Campaign Sequencing: Hidden Capacity in Process Plants

Introduction

Your best planners are experts at keeping the reactors running today. But can they work out how a call made this morning will starve a packaging line three days from now? In complex chemical processing, the bottleneck usually isn't equipment speed. It's the way stages interact over time, and that's where even a great planner hits a wall, because the calculation is too big to do in your head.

The result is capacity that looks like it isn't there. The plant feels full, lines stall, and nobody can quite point to why. Often it isn't a capacity problem at all. It's a sequencing problem, and the capacity was there the whole time, just locked up by the order things ran in.

The "Tank Tetris" problem

Take a common scenario. A rush order comes in for Product A. The planner checks the board: Reactor 1 is open, the raw materials are on hand, the changeover is minimal. Easy yes. It looks like a clean efficiency win, so it gets greenlit.

And on its own terms, it is a win. The rush order ships. The problem is what the yes did to the rest of the week, somewhere the planner wasn't looking, because there was no way to look there and keep the reactors running at the same time.

Every sequencing decision looks local, one order, one reactor, one open slot. Its cost usually shows up somewhere else, days later, where nobody connected it back.

The invisible domino effect

Here's what the yes actually set in motion. Product A runs and fills an intermediate tank. That tank now can't take the output of Product B's reaction, so B gets pushed. B was the feedstock for the packaging line on Thursday, so Thursday's line runs short and sits idle for a shift. The rush order didn't add throughput. It moved a bottleneck downstream and cost you a shift of packaging you'll never get back.

None of that was visible on Monday morning. The planner saw an open reactor and available material, greenlit the obvious win, and had no way to trace the chain three stages and three days out. That's not a knock on the planner. It's a chain too long and too interlinked to hold in your head, which is exactly the kind of problem a person can't solve by looking at a board and a solver can.

The rush order didn't create capacity, it relocated a bottleneck. The planner "saved" the order and quietly gave up total plant throughput, because the cost landed three stages downstream where nobody was looking.

How WonForge handles the ripple

Where a planner looks for an open slot, WonForge solves the whole plan at once, every stage, tank, and line, across the horizon. Faced with the same rush order, it doesn't just check whether Reactor 1 is free. It weighs what saying yes costs everywhere else: the tank that fills, the reaction that gets pushed, the packaging shift that goes idle, against the value of running the rush order now.

Sometimes the answer is still yes, the order's worth the downstream hit. Sometimes it's "yes, but run it Tuesday, not today," and the whole week holds together. The point isn't that the machine overrules the planner. It's that the decision gets made on the full picture, the cost three days out included, instead of on the one open slot a person can actually see.

WonForge weighs the whole ripple before it commits, so a decision that looks good locally only gets made if it holds up across the entire plan.

The bottom line

This isn't about replacing your planner's judgment. It's about giving it the reach a person can't have by hand. A planner works in specific units and days, that's the human scale of the problem. WonForge works the whole operation at once, treating reactors, tanks, and packaging lines as one connected system, so a local efficiency never quietly costs you global throughput.

The plant that feels maxed out usually isn't. The capacity is there. It's just trapped in the order things ran in, and sequencing it right is what lets it out, no capital, no new equipment, just a better plan.

A plant that feels full is often a sequencing problem, not a capacity one. The throughput is already there; the right sequence is what releases it.

Frequently Asked Questions

Isn't this just scheduling? Our scheduler already sequences the lines.

A scheduler sequences one stage against its own constraints. What it usually can't see is how today's sequence on the reactors starves a packaging line three days out, because that ripple crosses stages and time. Campaign sequencing optimization solves the whole chain at once, so the order you run in one stage accounts for what it does everywhere downstream, which is the part a single-stage scheduler misses.

Our planners are very experienced. What does optimization add?

It's not that your planners decide badly, it's that no one can see far enough. An experienced planner makes sound calls on what's in front of them, but no human can trace a single decision three stages and several days downstream while also keeping today's plant running. That chain is too long to hold in your head. The solver sees the whole chain at once, so the same good judgment is finally acting on the full picture, and the decisions genuinely come out better because of it.

How do we know hidden capacity is really there?

The practical way is to prove it on your own data. A focused model of your plant, run on your real constraints, shows what a better sequence would free up before you commit to anything bigger. If the capacity's locked in your sequencing, an optimized plan surfaces it; if it isn't, you'll know that too.

Conclusion

If your plant suffers from mystery downtime, stops that happen because a tank was full or a line was starved, you probably don't have a capacity problem. You have a sequencing problem, and the capacity you're missing is already in the building, locked up by the order things ran in. Freeing it doesn't take new equipment. It takes a plan that weighs the whole ripple before it commits, not one open slot at a time. If you want to see how much capacity your sequencing is hiding, Check Your Fit is a short, no-commitment call to find out.

Optimal Campaign Sequencing: Unlocking Hidden Capacity