S&OP response-time simulator v1.2
Revenue is recognized when the customer takes delivery. So the days a changed material date sits un-updated in your ERP don't just dent a KPI — they push promises past their dates, break OTIF, and slide proof-of-delivery into next quarter. Move the sliders to your reality and watch it flow through.
Sliders are a guide — type any value in the number fields, even beyond the slider range.
The prize
All the impact below is attributable to the days a changed date sits un-updated. Take the lag to same-day and it goes to zero — revenue lands in-quarter and the cost disappears.
Output A · Revenue timing
Output B · Service & cost
slip = volatility × lead time — week-long lead times breed week-long slips.f_bad = gated% × slip-rate × min(1, d / window)P(miss) = e^(−(buffer + safety stock) / slip) → for week-scale slips this approaches 1.at-risk = f_bad × P(miss), on top of your baseline.effectiveness = 0.55…0.95 from resequencing-led to substitution-led. net miss = at-risk × (1 − rate × effectiveness). You pay for every attempt; only the ones that land avoid the miss, slip, and penalty.cross ≈ (slip / 90) × 1.5 (end-of-quarter loading).The curve is the revenue you'd recover per year at each update-lag value; the dot is where you sit today, and the green drop to zero is what you'd gain by getting to same-day updates. Every other lever reshapes the curve.