Why Process Plants Sign Off an S&OP Plan the Floor Can't Run

Introduction

Every month the S&OP plan gets built, reviewed, signed off. Demand balanced against capacity, numbers reconciled, leadership on board. A good plan. Then the month starts, and within two weeks the floor is running something else.

Nobody decided to abandon it. It just couldn't be run as written, so the schedulers rebuilt it day by day, the way they always do. The plant hit most of the volume, so the plan looked like it worked. It didn't. The schedulers' improvising worked, and the plan everyone signed was a forecast of a plant that doesn't exist.

Two plans that were never going to match

The monthly plan and the daily schedule aren't one plan at two zoom levels. They're two different plans, and almost everything about how they're made pushes them apart. The S&OP plan says "make 4,000 tons of product B in March." It doesn't say in what order, on which line, after which product, across which changeover. Those decisions, the ones that decide whether 4,000 tons is even possible, get made later, somewhere else, by someone else, usually in a spreadsheet. And they get made against the real physics the monthly plan averaged away: the grade that fouls the line if it runs in the wrong order, the tank still draining, the rate that product actually holds. So the monthly plan is feasible in the aggregate, where the hard parts disappear into averages. The moment it has to become a sequence of real runs, it stops being executable, and someone fixes it by hand.

Why a better S&OP process won't fix it

The usual response is procedural: tighter cadence, better demand inputs, a consensus forecast everyone commits to. All of that sharpens the number. None of it touches the gap, because the gap isn't a communication problem, it's a handoff. You can run a flawless S&OP process and still hand the floor an aggregate number that nobody has checked against the actual sequence. The plan breaks at the handoff, and no amount of process discipline removes the handoff. Meanwhile the cost leaks quietly, never as one line item. Capacity, because the aggregate plan promised volume the sequenced floor can't deliver. Shared-asset limits, because the S&OP plan treats a month of capacity as one big number and never sees that two products need the same asset in the same week, so the volume it promised was never physically runnable. Trust, because every month the commitment misses in the details and finance, sales, and operations slowly stop believing the plan they all approved.

The fix is one plan, not two

The gap closes only when the long-range plan and the floor schedule stop being two documents and become one model at different resolutions. The monthly volumes and the actual run sequence are solved together, so the aggregate plan is built already knowing the changeovers, yields, shared-asset and tank limits, and rates that decide whether it can be executed. Zoom out and it's an S&OP plan. Zoom in and it's a schedule. Same plan, same math, no handoff between them. That's what WonForge does. One optimization carries the plan from the long-range horizon down to the near-term sequence, with production, material, tank, and shipment limits all inside it. There's no second system that has to discover the plan is impossible, because the physics was in the plan from the start. The number leadership signs is the number the plant runs.

Frequently Asked Questions