The supply chain planning stack: what it is and why it exists

Integrated Planning – Optimisation for the entire internal supply chain. Integrated planning and optimisation for the entire internal supply chain involves using advanced analytical tools and techniques to plan and manage the flow of goods and services within a company. This can include forecasting demand, optimising production schedules, and managing inventory levels.

One key aspect of integrated planning is the use of optimisation algorithms to determine the best course of action. These algorithms take into account a wide range of factors, such as lead times, production capacities, and costs, to find the optimal solution.

By using integrated planning and optimisation, companies can improve their overall supply chain performance, increasing efficiency and reducing costs. It also helps to identify bottlenecks and inefficiencies, and to find ways to mitigate them. Additionally, having an integrated view of the entire supply chain allows companies to respond more effectively to changes in demand and identify potential issues before they occur.

In this video, below explains the logic of integrated supply chain planning—connecting demand planning, inventory policy, and cross-functional decision-making so the business optimises the whole internal supply chain rather than isolated functions. The message is that planning must create a reliable information flow from executive objectives down to operational execution, while balancing competing outcomes like availability, inventory investment (cash/liquidity), and stability.

Supply chain planning is a layered system. Each layer answers a different question, uses a different time horizon, and produces a different type of decision. The system works only when each layer hands off clear commitments to the next and when feedback from execution improves future decisions.

Core principle:

• Planning is a ladder of decisions, not a single forecast

• Planning is a progressive commitment.

  • At the top you choose direction and capability (what you will be able to do).

  • In the middle you balance demand, supply and money (what you intend to do).

  • At the bottom you commit and execute (what you will do and what you did).

  • Integration ensures there is only one reality—what is commercially intended and physically feasible.

The planning stack at a glance (what each layer decides)

1. Strategic planning (2–5+ years): design and direction—service promise, footprint, make/buy, resilience, investment. Strategic planning designs the playing field.

2. Tactical planning / S&OP (3–24 months, monthly): balance and trade-offs—one set of numbers, policies, priorities.  Tactical planning balances demand, supply, and money within that design.

3. Operational planning (0–13 weeks typical, weekly): commitment conversion—MPS, time fences, MRP, DRP.  Operational planning converts the balance into executable commitments.

4. Execution / PAC (daily): release, sequence, control—protect the constraint and deliver the plan. Execution delivers work and generates performance signals.

5. S&OE (0–13 weeks, weekly): exception control—absorb volatility without breaking monthly decisions. S&OE manages short-term volatility and protects the integrity of execution while maintaining alignment with S&OP decisions.

Handoffs: the contract between layers

1. Strategic → S&OP: strategy provides service promise, segmentation, footprint constraints and guardrails; S&OP feeds back where strategy fails in practice.

2. S&OP → MPS/MRP/DRP: S&OP provides approved volumes, priorities and rules; operational planning feeds back feasibility gaps and the cost of instability.

3. Operational planning → Execution: provides stable schedules and replenishment timing; execution returns adherence and root causes.

4. Execution → S&OE → S&OP: execution provides truth and exceptions; S&OE resolves weekly within policy; S&OP changes rules/parameters and longer-term actions.

1 - Strategic planning (direction and design)

• Strategic planning produces design and policy decisions: service promise by segment, network/footprint intent, make-buy and sourcing posture, inventory positioning, technology roadmap, risk posture, and the operating model (governance, decision rights, cadence).

• Strategic choices must translate into planning rules such as allocation priorities, lead-time policy, and inventory targets.

• Main Question: What supply chain do we need to win in our markets, with our product mix, and our risk appetite?

• Time Horizon: 2-5 years or longer, depending on asset intensity and market dynamics.

• Decision Type: Design and policy decisions that create constraints for all later planning.

• Key Outputs:

  • Service promise by segment and channel.

  • Network design intent (plants, DC footprint, flow paths, postponement points).

  • Make/buy and sourcing posture (single vs dual source, nearshore/offshore, contracting strategy).

  • Inventory positioning strategy (where buffers live and why).

  • Technology roadmap (planning systems, WMS/TMS, visibility, data governance)

  • Risk posture (critical dependencies, contingency playbooks, resilience investments).

  • Operating model (decision rights, cadence, escalation rules, KPI ownership).

• Integration to the planning stack

  • Strategic intent must become planning rules. Examples:

    • Premium service segments require ATP priorities and allocation rules

    • Low-cost strategies require longer frozen horizons and disciplined batching.

    • Agility strategies require shorter cycles, flexible capacity, smaller lots, and strong S&OE exception management.

• Typical strategic failure modes

  • Strategy is not translated into policies and parameters, so the planning layers guess.

  • Strategy is not linked to constraints, so capacity investments lag reality.

  • Service promises are made without cost-to-serve funding, creating chronic execution stress.

    
    

2 - Tactical planning: S&OP (balancing and decision-making)

• Why S&OP is the centrepiece: S&OP is the cross-functional decision forum for trade-offs:

  • Demand shaping vs supply response.

  • Inventory investment vs capacity investment.

  • Allocation priorities during constraints.

  • Lead time and service trade-offs.

  • Financial reconciliation (revenue, margin, working capital, cash).

• S&OP integrates demand, supply, inventory, and finance and produces one agreed aggregate plan plus explicit trade-off decisions (capacity actions, inventory build/reduction, allocation priorities, and escalations that require leadership choices).

• Main Question: Over the next 3–24 months, can we meet demand profitably with available capacity and inventory, and if not, what explicit trade-offs will we decide?

• Time Horizon: Usually monthly, rolling forward continuously.

• Decision Type: Design and policy decisions that create constraints for all later planning.

• Inputs required for a good S&OP

  • Demand plan by family/segment with assumptions and bias visible.

  • Supply capabilities and constraints (capacity limits, supplier constraints, lead time variability).Inventory position and targets with ageing and slow movers visible.

  • Financial implications of options.

  • Events (promotions, launches, shutdowns, supplier changes).

• Outputs required from S&OP

  • One agreed aggregate plan.

  • Capacity actions (overtime, subcontract, shifts, maintenance timing).Inventory actions (build-ahead, reduction, end-of-life controls).Allocation and promise rules during constraint.

  • Escalations requiring executive decisions.

• Quality test

  • If S&OP ends without decisions, execution will make the decisions anyway, at higher cost and lower service.

  
  

3 - Operational planning: converting decisions into commitments

• Operational planning converts tactical intent into executable commitments.

• Master scheduling and the MPS translate the aggregate plan into item-date commitments and protect promise reliability using ATP discipline.

• Time fences define what may change and when to prevent churn. MRP translates the MPS into time-phased material and work orders and depends on stable schedules and accurate master data.

• DRP positions inventory across locations and feeds upstream planning so production supports demand where it occurs.

• Operational planning is where plans become executable commitments. It converts the S&OP aggregate plan into item-level schedules, material plans, and network replenishment plans.

• It includes:

  • Master Scheduling and the MPS plus order promising discipline (ATP).

  • MRP for dependent demand materials and work orders.

  • DRP for time-phased network replenishment.

  • Short-interval readiness for what can truly be executed this week.

    
    

  3.1 Master Scheduling and MPS (commitment layer)

  

  • Main question: Exactly which items will we produce, in what quantities, and on what dates, so that customer commitments can be met?

  • Why is MPS a commitment, not a suggestion? Instability in the MPS causes nervousness everywhere: MRP churn, supplier disruptions, lost productivity, warehouse and transport rework, and unreliable customer promises.

  • ATP discipline

    • ATP protects order promising.

    • Without ATP, sales commitments are not constrained by reality, and operations compensate with expediting and hidden buffers.

  • Time fences and frozen-zone rules

    • Time fences define how close to execution you are allowed to change the plan.

      • Frozen zone: changes are rare; exceptions only; approval required.

      • Slushy zone: controlled changes within rules.

      • Liquid zone: changes allowed to improve the future plan.

      • Time fences protect service and cost by preserving execution stability.

        
        

3.2 MRP (materials and dependent demand planning)

• Main question: What components and materials are required, when are they required, and what orders must be released?

• What MRP needs to work: Accurate BOMs, lead times, inventory records, realistic policies, and stable MPS.

• Why MRP fails in practice: Poor master data, unrealistic lead times, constant MPS changes, and weak release discipline.

3.3 DRP (network replenishment and positioning)

• Main question: How much inventory does each location need, when, and how should it be replenished?

• Why DRP matters: Service is delivered at customer-facing nodes. Factory plans can look perfect while customers experience stockouts if distribution replenishment is not planned and aligned.

• Common DRP traps:

  • Using shipments instead of consumption as the demand signal.

  • Disconnecting DRP from upstream planning.

  • Treating DRP as logistics rather than a planning driver.

    
    

3.4 Feasibility gates (capacity checks across the ladder)

• Feasibility must be checked where commitments are made:

  • Strategy: long-range capacity and footprint feasibility.

  • S&OP: high-level resource feasibility.

  • MPS: rough-cut feasibility at constraints.

  • MRP: detailed feasibility at suppliers and components.Execution: daily and weekly capacity control.

• If infeasibility is only discovered at execution, planning is reactive.

4 - Execution (PAC and daily operations control)

• Execution releases and sequences work, manages constraints, and measures adherence. Premium freight and expediting are not just cost problems; they are signals of planning, data, or governance failure upstream.

• Main question: What work do we execute today and this week, in what sequence, using what resources, to deliver the plan?

• Execution includes: Release and dispatch, sequencing, bottleneck management, labour deployment, quality control, picking and loading, transport execution, and delivery performance.

• Execution signals that planning must respond to:

  • Schedule adherence at constraints.

  • Backlog and recovery patterns.

  • Premium freight and expediting triggers.

  • Quality holds and rework patterns.

    
    

5 - S&OE (weekly short-term exception engine)

• S&OE connects daily operations to S&OP by managing near-term exceptions within agreed rules and escalating true cross-functional trade-offs. It protects execution stability while absorbing real volatility.

• Main question: Over the next 0–12 weeks, what changed, what actions are required, and what must be escalated?

• Purpose: S&OE translates the mid-term plan into short-term actions and manages exceptions within agreed rules. It is not a mini-S&OP, nor daily firefighting.

• Typical S&OE scope:

  • Demand exceptions, supply exceptions, inventory imbalances, execution disruptions.

  • Decisions: reallocation, substitution, rescheduling within fences, controlled expedites.

  • Escalations: policy overrides and major trade-offs.

• Success test: After S&OE, teams know the next 1–4 week plan, what is frozen, who owns each exception, and what is escalated.

6 - Integration to execution: operating model essentials

• A planning stack only works with governance, discipline, and data ownership.

• Core governance components:

  • clear decision rights (who can change what and when),

  • disciplined cadence (monthly S&OP, weekly S&OE, daily control),

  • escalation rules for overrides,

  • policy management (time fences, allocation rules, inventory policy),

  • data ownership (BOM, lead times, routings, locations), and

  • closed-loop performance review to improve the system over time.

• Minimum viable one set of numbers: Demand view, supply view, inventory view, financial view, all aligned and consistent.

Why it matters (service, cost, cash, risk)

• Service: Stable commitments improve promise reliability and reduce last-minute surprises for customers.

• Cost: Less expediting, fewer changeovers, fewer firefighting, and fewer avoidable premium moves.

• Cash: Better inventory positioning and fewer “buffer stacks” built by fear reduce working capital.

• Risk: Clear time-horizon rules + exception routines expose risks early and force decisions at the right level.

How it shows up when the stack is broken (symptoms)

• S&OP becomes a forecast meeting with no decisions (“review without resolve”).

• Operational plans change daily; MRP churn becomes normal.

• Execution runs on expedites, not priorities; the constraint is not protected.

• Excess and stockouts coexist because inventory is in the wrong place/time.

• Sales commits beyond what is feasible because ATP/commitment rules are weak.

• Root causes/drivers (what usually breaks the stack)

• No decision rights by horizon (everyone can change everything, anytime).

• “One set of numbers” doesn’t exist (demand, supply, and finance run different plans).

• Master data/parameters are unstable (lead times, BOMs, routings) so MRP outputs noise.

• Time fences are defined but not respected (frozen zone violated constantly).

• No weekly exception governance (S&OE missing or treated as another meeting, not a control loop).

  
  

How to measure (simple diagnostic + what “good” looks like)

Simple diagnostic (4-week sprint):

• Track these weekly for one product family and one constrained resource:

• Plan stability: number of MPS changes inside the planning time fence

• Schedule adherence at the constraint

• Service: OTIF / fill rate (family + critical SKUs)

• Inventory: DOS trend + imbalance (where stock sits vs where demand is)

• Expedite signals: premium freight, hot lists, late supplier recoveries

Good looks like:

• Changes inside the planning time fence are rare and escalated

• S&OE produces a short list of actions, owners, and dates each week

• Execution adherence improves; expedites decline; service improves without inventory spikes

How to improve (End2End playbook)

• Define decision rights by horizon

  • Strategic decisions belong to strategy governance; monthly trade-offs belong to S&OP; near-term exceptions belong to S&OE; daily sequencing belongs to execution.

• Build time-fence discipline (stability rules)

  • A time fence is a policy boundary where restrictions on change apply; changes get harder and more expensive closer to execution.

• Use the planning time fence to control changes that would disrupt component schedules, capacity, deliveries, and cost.

  • Use slushy-zone rules to negotiate trade-offs (not to permit chaos).

• Make S&OP decision-led

  • S&OP must produce decisions and a production plan (not just updated spreadsheets).

• Convert to executable commitments

  • Ensure master scheduling produces item/date commitments and protects ATP logic (promise only what’s uncommitted and feasible).

• Run S&OE as an exception engine

  • Weekly: detect exceptions, decide actions within rules, escalate true trade-offs, and protect the frozen zone.

SCOR lens (map interventions per process)

• Plan: S&OP, policy setting, time fences, scenario options

• Order: order promising/ATP rules, allocation priorities under constraint

• Source: supplier commitments, lead-time governance, exception recovery plans

• Transform: MPS/MRP, constraint protection, schedule adherence and stability

• Fulfill: inventory positioning, DRP cadence, service recovery rules

• Return: exception visibility for returns/dispositions that disrupt plans

• Orchestrate: governance, one set of numbers, KPI ownership, escalation cadence

CSCP exam cues (what gets tested)

• S&OP is the integrator (demand + supply + finance) and operates at aggregate level monthly.

• MPS is not a forecast; it is what the company plans to produce (config/qty/date) and it drives MRP.

• Time fences exist to protect stability; slushy zone is negotiated change, not free-for-all.

• S&OE is weekly, short-term, and connects S&OP to daily actions.

End2End practitioner notes

• Start with “stability rules” before you chase accuracy: planning credibility is built through fewer surprises, not prettier forecasts.

• If execution is firefighting daily, the fix is usually above execution (rights, fences, and S&OE), not “work harder.”

• Keep S&OE small and ruthless: exceptions only, decisions only, owners only.

Mini-cases by layer (practical one-paragraph examples)

• Strategic planning: An FMCG business segments service (premium for top retailers, standard for others, make-to-order for long-tail SKUs) and adjusts footprint (central DC plus regional cross-docks). This sets inventory positioning and acceptable trade-offs.

• S&OP: A medical distributor anticipates a guideline-driven uplift while one imported item is supplier-allocated. S&OP approves early builds for A-items, limits non-critical promotions, and sets allocation rules to protect hospitals.

• S&OE: A supplier confirms a two-week delay within the month. S&OE applies allocation rules, rebalances DC stock, updates promise dates for low-priority channels, and escalates only the premium freight decision due to margin impact.

• MPS: Sales requests a major change inside the frozen zone. Master scheduling shows consequences (sequence disruption, extra changeovers, other missed shipments) and forces an explicit accept/reject/escalate decision.

• MRP: Chronic expediting traces to optimistic lead times and BOM/inventory inaccuracies. Fix master data and stabilise the MPS—then shortages drop and exceptions become real.

• DRP: Coastal stores stock out while inland DCs overflow. DRP parameters are reset (frequency, safety stock by variability/lead time, rebalancing rules), improving availability without raising total stock.

• Execution/PAC: A packaging bottleneck causes erratic output. PAC implements a stable product wheel, protects the constraint, and tracks adherence daily—reducing overtime and improving promise reliability.

Exam-style scenarios (10) with answers and rationale

1. Footprint decision (add regional DC vs central DC vs cross-dock).

   Answer: Strategic planning.

   Rationale: long-term network design/capability.

2. Next-quarter promo uplift with constrained capacity; decide overtime vs shift promo vs prioritise.

   Answer: S&OP.

   Rationale: cross-functional mid-term trade-off.

3. Supplier delay causing stockout risk within a month; rebalance DCs and prioritise customers within policy.

   Answer: S&OE.

   Rationale: short-term exception control.

4. Sales requests next-week schedule change inside frozen zone; disrupts components and other deliveries.

   Answer: MPS/time fence governance.

   Rationale: item-date commitment stability.

5. MRP planned orders exist but shortages persist due to wrong lead times/inventory accuracy.

   Answer: MRP discipline (master data integrity).

   Rationale: data/parameter governance.

6. Total stock sufficient but one region stocks out while another is excess; set time-phased replenishment.

   Answer: DRP.

   Rationale: network positioning/replenishment.

7. Monthly plan met but daily output erratic due to dispatching/bottleneck starvation; control sequencing and protect constraint.

   Answer: Execution/PAC.

   Rationale: daily control.

8. NPI introductions and variant discontinuations over next year; consider service promise, complexity, capacity.

   Answer: S&OP (with strategic alignment).

   Rationale: tactical portfolio decisions.

9. Leadership wants frozen/slushy/liquid zones and who can approve changes.

   Answer: Time fences (master scheduling governance).

   Rationale: stability mechanism.

10. Service targets unclear; teams treat all SKUs as urgent; need segment-based promise and lead-time policy.

    Answer: Strategic planning.

    Rationale: service policy/segmentation guardrail.