S&OP, Demand Planning & Forecasting worked example
Supply Demand Gap with average daily unit consumption of 3,000 units / day: a worked example
This scenario runs the supply demand gap calculation on the strong side: average daily unit consumption of 3,000 units / day, with every other input held at its documented default. Use it when supply demand gap in s and op, demand planning and forecasting is being sized for a buffer or safety stock review.
The inputs for this scenario
- Average daily unit consumption: 3,000 units / day (raised for this scenario; the documented default is 1,200)
- Replenishment lead time: 85 days (unchanged)
- Safety stock cushion: 1.1 units (unchanged)
Working through the calculation
- Applying the documented formula (Supply demand gap cycle stock = supply demand gap daily usage × supply demand gap lead time) to the inputs above produces each figure below.
- At this operating point the engine returns 32.09 days for protected days of supply, the number this scenario is built around.
- At this operating point the engine returns 35.29 days for unprotected days.
- At this operating point the engine returns 3,000 pieces for inventory.
- At this operating point the engine returns 85 pieces / day for daily usage.
How this compares with the baseline
- Against the tool's baseline example, where average daily unit consumption sits at 1,200 units / day and the headline result is 12.83 days, this scenario comes in 150% above the baseline at 32.09 days.
- Use it during weekly S&OP reviews or whenever a supplier lead time changes, to check that on-hand stock still bridges the replenishment window. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Protected days of supply: 32.09 days (headline result)
- Unprotected days: 35.29 days
- Inventory: 3,000 pieces
- Daily usage: 85 pieces / day
Run it with your numbers
- Every input above is editable in the live Supply Demand Gap calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.