What Is Sales and Operations Planning? EDGEBIC Definition

Sales and operations planning, usually shortened to S&OP, is the recurring cross-functional process that reconciles what a company intends to sell with what it is able to make and afford. Sales brings the demand plan. Operations brings the supply plan. Finance brings the money view. The output is one agreed production plan for the months ahead that all three sides own.

The everyday version: the Monday meeting where sales, production, and finance sit down and agree on what to build next month, rather than each department planning against its own private forecast and discovering the mismatch on the shop floor.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary.

How Sales and Operations Planning Works

The problem S&OP exists to solve is that different parts of a company plan on different numbers.

Sales plans on what it expects to sell. Operations plans on what it can build. Finance plans on what the cash will support. Left alone, all three are internally consistent and mutually incompatible. Sales promises volume nobody resourced. Operations holds capacity for demand that never comes. Finance is surprised by both.

S&OP is the discipline of forcing those views into one plan on a regular cadence, typically monthly, over a horizon of several months rather than days.

It runs in a recognizable shape. Demand is consolidated first: orders on the books plus forecast for what has not been ordered yet. Supply is assessed against it: can the plant, the material, and the people deliver that volume. Gaps are surfaced honestly and resolved by decision rather than by drift, whether that means adding a shift, moving a customer, subcontracting, or accepting a shortfall. What comes out is a single agreed plan.

It belongs to a family of planning layers, and it helps to see where it sits. S&OP is above the master production schedule, which is the committed build plan for finished goods by product and time bucket. Below that sits material planning, which explodes the build plan into component requirements. Below that sits finite-capacity scheduling, which places individual operations on real machines with real hours. Each layer is shorter in horizon and finer in detail than the one above.

The reason this hierarchy matters is that a decision made at the wrong layer is expensive. Deciding in a monthly meeting which machine runs which job is pointless. Discovering on the shop floor that the year's volume was never resourced is worse.

A Concrete Example

A pump manufacturer holds its monthly planning meeting in early September to set the plan for the fourth quarter.

Sales brings the demand view: firm orders on the books for October, plus a forecast for November and December driven by a customer expected to place a large order that has not landed yet. Total demand is roughly a thirty percent lift on the current run rate.

Operations brings the supply view. The question is not whether the plant would like the work; it is whether the plant can resource it. Thirty percent more volume through the same machining and assembly centers is a claim that has to be checked, not assumed.

That check is where a build plan becomes useful. The proposed volume is written down as committed quantities by product and week, and the finite-capacity engine schedules against it using real work center hours, real shift calendars, and real routings. The answer comes back specific: the machining centers absorb the lift, the heat treatment station does not, and it becomes the constraint from the middle of November.

Now the meeting has a decision to make rather than a disagreement to have. Add a shift on heat treatment, subcontract the overflow, or move a customer's dates. Any of those is a legitimate answer. What matters is that it is decided in September with the numbers in front of everyone, rather than discovered in November by a foreman with an overloaded oven.

How EDGEBIC Fits Into It

S&OP is a company process rather than a software module, and running the meeting stays with the people in it. The product covers the supply side of the answer:

• The master production schedule holds the planner-committed build quantities by product and time bucket, which is the artifact an S&OP decision produces.
• Finite-capacity scheduling tests whether a proposed build plan can physically be executed on the machines and shifts that exist, so the supply side arrives with a checked answer rather than an opinion.
• Demand inputs come from confirmed customer order lines and planner-entered forecasts, which is the same pair of sources the demand side of an S&OP conversation is built on.

For the artifact that carries the committed plan, see what is a master production schedule. For the process of consolidating demand, see what is demand management. To work the build plan itself, follow how to work the MPS grid.