Forecast object
Event outcome: timing known, outcome uncertain.
Event timing: outcome known, timing uncertain.
Time series: historical observations projected into future periods.
Level, trend, and seasonality are different demand structures. This guide keeps them separate, compares them only when useful, and follows the complete workflow from forecast definition and holdout evaluation to Excel, SAS, and cross-functional S&OP decisions.
Keyboard: Space play/pause, → step, R reset. The shortcuts are ignored while typing in a field.
Variation around a roughly constant mean.
A persistent direction of change over time.
A recurring pattern tied to the calendar interval.
A method cannot be judged until the forecast object, users, horizon, aggregation level, data availability, and decision context are explicit.
Event outcome: timing known, outcome uncertain.
Event timing: outcome known, timing uncertain.
Time series: historical observations projected into future periods.
Univariate: only the series’ own history.
Multivariate: adds predictors such as price, promotion, weather, or economic variables.
Point: one number.
Range: an interval.
Density: a probability distribution. More information can support richer decisions, but is harder to communicate.
Moving averages and simple exponential smoothing are level methods. A trend requires an explicit trend component. Recurring calendar behavior requires a seasonal component. Treating all three as interchangeable creates systematic lag or repeated seasonal error.
A naïve forecast is the minimum benchmark: next period equals the latest observed demand. A more complex process must beat a reasonable baseline to demonstrate value.
A short moving average reacts quickly but remains noisy. A longer window is smoother but slower. Neither is designed to extrapolate a persistent trend.
Simple exponential smoothing can respond to change, especially with high alpha, but its multi-step forecast remains flat. A rising series therefore exposes the method’s structural mismatch.
Time-series regression models demand as an intercept plus change per period. The slope extends the direction into the holdout horizon.
Multiplicative seasonal indices measure demand relative to an estimated trend. Each month receives a factor above or below 1.0.
Holt-Winters updates level, trend, and seasonal factors each period. It is not “better” by definition; it is appropriate only when those components are present and stable enough to extrapolate.
The included workbook has 60 monthly observations per series: 48 training periods and a 12-period holdout. Edit any observation or upload a CSV; all methods, metrics, charts, and exercises recalculate immediately.
Select a method, adjust its parameters, move the forecast origin, and reveal calculations period by period. The holdout evaluation always fits only the training data.
Residual = actual − one-step forecast. Persistent same-sign errors indicate bias; patterns indicate structure the model has not captured.
Cells reveal in sequence as the origin moves. Excel formulas use the visible worksheet convention: column A = period, B = actual, C = forecast.
The laboratory uses the multiplicative seasonal form. The additive specification is included for comparison. Each equation also shows its equivalent error-correction form.
Symbols. dt is actual demand; Lt is level; Tt is trend; St is the seasonal component; s is the number of periods in a season; α, β, and γ are smoothing constants between 0 and 1; Ft+1 is the one-period-ahead forecast.
Excel makes every forecasting step visible: generate a time series, build one-step forecasts, calculate errors, compare parameters, and preserve the logic in copy-down formulas.
The compact equation shows the selected forecast operation. The worksheet expression updates with the method controls in the laboratory.
Follow the sequence when learning the methods, or open one step as a focused implementation reference.
SAS separates data preparation from statistical procedures. A reliable workflow defines the time interval, fits competing models, creates a genuine forecast region, and compares every method on the same holdout observations.
Instructional example only. The browser does not execute SAS. The performance summary below is calculated from the included or edited data.
A low fitted error is not proof of future accuracy. All model rankings below use a fixed-origin forecast created from training observations only and compared with the separated holdout.
MFE, MAD, MSE, and MAPE are the core forecast-quality measures. CFE, RMSE, tracking signal, and FVA extend the diagnosis. Here, n is the number of evaluated periods; error is actual minus forecast. MAPE is calculated as a ratio and displayed as a percentage.
Positive: underforecast. Negative: overforecast.
Running signed error; persistent drift signals bias.
Average signed error; a bias measure, not an accuracy measure.
Average error magnitude in the original demand units.
Squares errors, so large misses receive more weight.
Returns squared-error performance to the original demand units.
Undefined at zero actual demand and unstable when actual demand is near zero.
Monitors cumulative signed error relative to typical absolute error.
Positive: the new process step reduced error. Negative: it made the forecast worse.
The workflow is: fit on training data → freeze the model → forecast the holdout → compare forecast with actual → select the method → refit the selected method on all known data for a future forecast.
No universal winner is declared. Each column ranks a different objective. Rank 1 is best within that criterion and current dataset. Accuracy uses holdout RMSE; bias uses absolute holdout MFE; responsiveness compares forecast changes with actual holdout changes; stability uses the standard deviation of forecast changes; interpretability is an explicit teaching rubric rather than a statistical estimate.
A high alpha puts more weight on the newest observation. A longer moving-average window spreads weight over more periods. Both choices alter how quickly forecasts move and how much noise they transmit.
Forecast Value Added asks whether a step improves performance relative to a prior baseline. Here, positive FVA means a reduction in holdout MAD relative to the previous step.
A judgmental override is not automatically value-adding. It must be evaluated against the unadjusted statistical forecast and the naïve baseline.
S&OP version rule: preserve the statistical forecast, commercial adjustment, constrained supply plan, approved consensus plan, and actual result as separate records. Use FVA for forecast changes; use service, cost, inventory, and financial measures for planning decisions.
This is a teaching guide, not an automated guarantee. Data quality, structural breaks, intermittent demand, causal information, and business loss still require judgment.
Sales and Operations Planning integrates demand, supply, and financial perspectives at an aggregate level. The forecast remains an evidence-based estimate; S&OP converts that evidence into an authorized plan without erasing the original baseline.
Core distinction: an approved consensus plan may include capacity limits, targets, risk choices, and executive judgment. It should not be relabeled as an unbiased statistical forecast.
The most likely outcome under a stated information set and assumptions.
The result management wants to achieve. A gap to forecast requires actions, not silent forecast inflation.
The actions, resources, timing, and ownership selected to respond to the forecast and pursue the target.
The feasible commitment after capacity, supply, labor, inventory, capital, and logistics limits are applied.
Planning level: S&OP typically works by product family, month, and aggregate resource category. MPS and MRP translate that decision into operating detail.
Each error can invalidate a technically correct formula or turn a useful forecast into a poor operating decision.
Using holdout values, future promotions, or future seasonal ratios while fitting the model.
Sorting by demand instead of date, or reversing the series before applying lags.
Mixing daily, weekly, and monthly observations without aggregation rules.
Silently compressing the calendar so a two-month gap appears to be one period.
Using season length 12 because the data are monthly without confirming a repeated annual pattern.
Selecting parameters on the same observations used to report performance.
Reporting MAD or RMSE while ignoring persistent underforecasting or overforecasting.
Choosing a model by the smallest error without considering loss, horizon, responsiveness, stability, and operating consequences.
Raising the forecast to match an aspiration instead of preserving the baseline and specifying demand-shaping actions.
Overwriting the baseline with an override or constrained plan, making bias, accountability, and Forecast Value Added impossible to evaluate.
Use the hints only after attempting the question. Worked solutions are concise and tied to the forecasting and planning conventions used throughout this guide.