Advanced Operations Management

Chapter 4
Forecasting and Demand Management

Advance Diploma in Operations management
Advanced Operations Management   •   Advance Diploma

Forecasting and Demand Management

Introduction

Forecasting is the systematic estimation of future demand, workload, resource requirements, or business conditions using historical evidence, current information, expert judgment, and explicit assumptions. In operations management, forecasting does not mean predicting the future with certainty. It means producing a disciplined estimate that supports decisions about capacity, inventory, procurement, staffing, scheduling, distribution, and customer service.

Demand management is broader than forecasting. It includes the processes used to understand, influence, prioritize, communicate, and fulfil demand. A forecast may estimate what customers are likely to request, while demand management determines how the organization responds when demand is uncertain, constrained, seasonal, promotional, or strategically undesirable.

For example, a manufacturer may forecast monthly demand for a product, sense a sudden increase in customer orders, collaborate with distributors to obtain better market information, and then adjust production and inventory policies. Effective operations therefore connect forecasting with execution rather than treating the forecast as an isolated statistical exercise.

Learning Objectives

By the end of this chapter, the reader should be able to:

  1. Explain the role, scope, and limitations of forecasting in operations.
  2. Distinguish qualitative and quantitative forecasting methods.
  3. Calculate and interpret moving-average and exponential-smoothing forecasts.
  4. Use trend, regression, and seasonal analysis appropriately.
  5. Calculate forecast-error measures and evaluate model performance.
  6. Explain demand sensing, collaborative planning, and the bullwhip effect.
  7. Select forecasting methods using data, cost, risk, and operational context.
  8. Identify governance, ethical, and technological issues in demand planning.

1. The Role of Forecasting in Operations

Forecasts support decisions at several planning horizons:

HorizonTypical decisionsCommon forecasting emphasis
Strategic: several yearsFacilities, technology, market entry, workforce capabilityScenarios, market research, macroeconomic and causal models
Tactical: months to two yearsAggregate production, budgets, supplier contracts, inventory targetsTime-series models, regression, collaborative forecasts
Operational: days to weeksScheduling, replenishment, labour allocation, transportShort-term demand sensing, recent sales, order data

Forecasts may concern independent demand, such as customer purchases, or dependent demand, such as components required to produce a finished product. Dependent demand is often calculated from a production plan and bill of materials rather than forecast independently.

A useful forecast should be:

  • sufficiently accurate for the decision being made;
  • timely and available at the required level of aggregation;
  • understandable to decision-makers;
  • consistent across products, locations, and time horizons;
  • economically justified; and
  • accompanied by uncertainty information, not just a single number.

Forecast accuracy is not the only performance criterion. A slightly less accurate model may be preferable if it is more stable, transparent, easier to maintain, or better aligned with the planning process.

2. Demand Patterns and Forecastability

Before selecting a method, the analyst should inspect the demand pattern. Four components are especially important:

  • Level: the underlying average demand around which observations fluctuate.
  • Trend: a persistent upward or downward movement.
  • Seasonality: a systematic pattern that repeats at a known frequency, such as weekly, monthly, or annual cycles.
  • Random variation: irregular movement that cannot be explained reliably by the model.

Demand can also contain cycles, promotions, price effects, stockouts, product substitutions, and structural breaks. A structural break occurs when the data-generating process changes, for example after a competitor enters the market or a product is redesigned.

The observed demand at time t may be represented conceptually as an additive model:

Yt = Lt + Tt + St + εt

where Yₜ is observed demand, Lₜ is level, Tₜ is trend, Sₜ is the seasonal component, and εₜ is random error. This representation is appropriate when seasonal variation is approximately constant in absolute units. A multiplicative representation is more suitable when seasonal variation increases with the level of demand:

Yt = Lt × Tt × St × εt

The additive and multiplicative forms are conceptual models; actual forecasting procedures require estimation of their components.

Forecastability depends on the signal-to-noise ratio, the forecast horizon, product life-cycle stage, data quality, and the stability of causal relationships. Intermittent demand, in which many periods have zero demand and occasional periods have large demand, requires special methods and should not automatically be modelled with ordinary averages.

3. Qualitative Forecasting

Qualitative methods are appropriate when historical data are limited, unreliable, or no longer representative. They are also valuable when experts possess information that has not yet appeared in sales data, such as a forthcoming regulation, competitor action, customer contract, or technology change.

Important methods include:

Jury of executive opinion

Senior managers independently or collectively estimate future demand. This method is quick but may be affected by hierarchy, anchoring, optimism, and political interests.

Sales-force composite

Sales representatives estimate demand in their territories. The method uses local customer knowledge but may produce biased estimates if sales staff protect targets, inflate opportunities, or lack statistical training.

Customer surveys and market research

Potential or existing customers are asked about intentions, preferences, or likely purchases. Stated intentions do not always become actual purchases, so survey design and sampling are critical.

Delphi method

A panel of experts provides estimates through several anonymous rounds. A coordinator summarizes the responses, allowing participants to revise their views without direct group pressure. Delphi is useful for long-range or novel situations, but it can be slow and depends on expert selection.

Scenario analysis

Managers develop internally consistent descriptions of alternative futures, such as high-growth, constrained-supply, and recession scenarios. Scenarios do not produce a single statistically optimal forecast; they improve preparedness for uncertainty.

Qualitative judgments should be documented. The organization should record the assumptions, evidence, confidence level, and responsibility associated with an adjustment. This improves accountability and enables later review.

4. Quantitative Time-Series Methods

Quantitative time-series methods use historical observations to infer a pattern that is expected to continue. Their central assumption is that relevant features of the past remain sufficiently stable during the forecast period. This assumption must be challenged when the market, product, price, or supply conditions have changed.

4.1 Naïve forecast

For a stable series, the simplest forecast for the next period is the most recent observation:

Ft+1 = Yt

Here Fₜ₊₁ is the forecast for period t + 1, and Yₜ is actual demand in period t. A seasonal naïve forecast uses demand from the corresponding previous season:

Ft+h = Yt+h-m

where h is the forecast horizon and m is the seasonal period. For monthly data with annual seasonality, m = 12. Naïve models are important benchmarks; a complex model should outperform them after considering cost and stability.

4.2 Moving averages

A simple moving average of order k uses the arithmetic mean of the most recent k observations:

Ft+1 = (Yt + Yt-1 + … + Yt-k+1) ÷ k

The method smooths random variation. A larger k produces a smoother forecast but responds more slowly to changes. A smaller k responds faster but is more sensitive to noise.

Worked example. Demand for the last three weeks was 120, 135, and 150 units. A three-week moving-average forecast for week 4 is:

F4 = (120 + 135 + 150) ÷ 3 = 405 ÷ 3 = 135 units

If week-4 demand is 165 units, the forecast for week 5, using the latest three observations, is:

F5 = (135 + 150 + 165) ÷ 3 = 150 units

A moving average treats all included observations equally. A weighted moving average assigns greater weights to observations considered more relevant:

Ft+1 = w1Yt + w2Yt-1 + … + wkYt-k+1

where each weight is non-negative and the weights sum to 1. If the weights do not sum to 1, the result is not a conventional weighted average unless a deliberate normalization is applied.

4.3 Exponential smoothing

Simple exponential smoothing updates the forecast using the previous forecast and the most recent actual demand:

Ft+1 = αYt + (1 − α)Ft

where α is the smoothing constant, 0 < α < 1. A high α reacts strongly to recent demand; a low α produces greater smoothing. The method is most appropriate for data with no strong trend or seasonality. The initial forecast F₁ must be specified, often as the first observation, an initial average, or an informed estimate.

Worked example. Let α = 0.30, actual demand in period 1 be 100 units, and the forecast for period 1 be 100 units. If actual demand in period 2 is 120 units:

F3 = 0.30(120) + 0.70(100) = 36 + 70 = 106 units

If actual demand in period 3 is 110 units, the period-4 forecast is:

F4 = 0.30(110) + 0.70(106) = 33 + 74.2 = 107.2 units

Forecast values may be fractional even when units are indivisible; operational systems can round the result at the execution stage.

Simple exponential smoothing can be expressed through forecast error eₜ = Yₜ − Fₜ:

Ft+1 = Ft + αet

This form shows that the forecast is adjusted in proportion to the latest error.

4.4 Trend-adjusted and seasonal smoothing

When trend is present, methods such as Holt’s linear method estimate both level and trend. One common formulation is:

Lt = αYt + (1 − α)(Lt−1 + Tt−1)
Tt = β(Lt − Lt−1) + (1 − β)Tt−1
Ft+h = Lt + hTt

Here Lₜ is the estimated level, Tₜ is the estimated trend, h is the number of periods ahead, and α and β are smoothing constants between 0 and 1. The initialization of level and trend must be specified. Holt’s method should not be used blindly when the trend is temporary or when long-range extrapolation is implausible.

Seasonal exponential-smoothing models add a seasonal component. Additive seasonality is appropriate when seasonal effects are roughly constant in units; multiplicative seasonality is appropriate when effects are proportional to the level. Model selection should be tested empirically and reviewed operationally.

5. Regression and Causal Forecasting

Time-series methods use the internal history of demand. Regression models explain demand using one or more explanatory variables, such as price, advertising, temperature, income, number of active customers, or construction activity.

A simple linear regression is:

y = a + bx + ε

where y is demand, x is an explanatory variable, a is the intercept, b is the estimated change in demand for a one-unit change in x, and ε is the unexplained error. The fitted forecast is:

ŷ = a + bx

The ordinary least-squares estimates are:

b = ∑(xi − x̄)(yi − ȳ) ÷ ∑(xi − x̄)2
a = ȳ − bx̄

where x̄ and ȳ are sample means. These formulas assume a linear conditional relationship and are sensitive to outliers. For reliable interpretation, analysts should examine residuals, omitted variables, multicollinearity in multiple regression, and whether the explanatory variable will be known or forecast at the time the demand forecast is produced.

Regression association does not automatically establish causation. A strong relationship may reflect a third variable or common trend. For example, both sales and online advertising may rise over time without advertising being the sole cause of sales growth.

For multiple drivers:

y = a + b1x1 + b2x2 + … + bpxp + ε

Each coefficient represents the estimated effect of its variable while holding the other included variables constant, subject to model assumptions. Categorical effects, interventions, promotions, and seasonal indicators can be represented using appropriately coded variables.

6. Seasonality and Calendar Effects

Seasonality must be distinguished from trend. Trend changes the underlying level over time; seasonality repeats at a known frequency. Retail demand may peak before holidays, electricity demand may vary by hour and day, and agricultural demand may follow climatic cycles.

A practical seasonal procedure is:

  1. Define the seasonal period, such as 7 days, 12 months, or 4 quarters.
  2. Inspect a time plot and compare corresponding seasons.
  3. Estimate and remove trend when necessary.
  4. Estimate seasonal indices.
  5. Forecast the underlying level or trend.
  6. Reapply the seasonal factors.
  7. Validate the resulting forecasts on holdout data.

For multiplicative seasonality, a seasonal index can be interpreted as:

Sj = average demand in season j ÷ average demand across seasons

Indices are commonly normalized so that their average over a complete seasonal cycle equals 1. For additive seasonality, seasonal effects are measured in demand units and typically sum to zero over a full cycle.

Calendar effects such as the number of working days, moving holidays, payday timing, and leap years may be mistaken for ordinary seasonality. These effects should be represented explicitly where they materially affect demand.

7. Forecast-Error Measurement

Let the error in period t be:

et = Yt − Ft

A positive error means actual demand exceeded the forecast; a negative error means the forecast exceeded actual demand.

MeasureFormulaInterpretation
Mean error (ME)∑eₜ ÷ nBias; positive values indicate under-forecasting on average
Mean absolute error (MAE)∑\eₜ\
Mean squared error (MSE)∑eₜ² ÷ nPenalizes large errors more heavily
Root mean squared error (RMSE)√MSEError in the original demand units
Mean absolute percentage error (MAPE)100 × ∑(\eₜ ÷ Yₜ\
Weighted absolute percentage error (WAPE)100 × ∑\eₜ\

The symbol n is the number of evaluated periods. MAE, MSE, and RMSE require consistent units. MAPE is undefined when actual demand is zero and can become disproportionately large when actual demand is close to zero. WAPE can be more interpretable for portfolios but may hide poor performance on low-volume items.

Worked example. Actual demand over three periods is 100, 120, and 80 units; forecasts are 90, 130, and 100 units. Errors are 10, −10, and −20 units. Therefore:

ME = (10 − 10 − 20) ÷ 3 = −6.67 units
MAE = (10 + 10 + 20) ÷ 3 = 13.33 units
MSE = (100 + 100 + 400) ÷ 3 = 200 units²
RMSE = √200 ≈ 14.14 units

For non-zero actual values:

MAPE = 100 × [(10÷100) + (10÷120) + (20÷80)] ÷ 3 ≈ 13.89%

Accuracy should be evaluated on data not used to fit or select the model. Rolling-origin validation is often useful: the model is repeatedly trained on an earlier period and tested on the next period. Errors should be segmented by product, location, customer, horizon, and demand regime rather than summarized only by one overall number.

Bias monitoring is especially important. A model with acceptable MAE but persistent negative errors may cause chronic stockouts. Tracking the cumulative forecast error helps identify systematic bias:

CFEt = ∑i=1t ei

A large sustained cumulative error suggests that the model or the process requires investigation. It does not by itself prove that the model is statistically unacceptable; control limits and business consequences should be defined appropriately.

8. Demand Sensing and Collaborative Planning

Demand sensing uses high-frequency and near-real-time signals to update a baseline forecast. Signals may include point-of-sale data, customer orders, inventory positions, web traffic, search activity, weather, mobility, promotions, cancellations, and distributor inventory. Its value is greatest when demand changes faster than the normal planning cycle.

Demand sensing should not be confused with replacing the forecast with raw daily fluctuations. Short-term signals may contain noise, duplication, order batching, or channel distortions. A robust process distinguishes genuine demand from inventory transfers, emergency orders, returns, and orders created by promotions.

Collaborative planning aligns organizations that possess different information. Common approaches include:

  • CPFR: collaborative planning, forecasting, and replenishment between trading partners;
  • S&OP: sales and operations planning, which reconciles market demand with supply, capacity, and financial objectives;
  • IBP: integrated business planning, extending this reconciliation to strategic and financial planning;
  • shared sales forecasts and promotion calendars;
  • joint review of exceptions, constraints, and assumptions.

Collaboration can reduce information distortion, but it requires common definitions, data standards, agreed ownership, and incentives that do not encourage demand inflation. A supplier and retailer should clarify whether a forecast represents consumer demand, retailer orders, shipments, or expected inventory movement.

The bullwhip effect describes the amplification of demand variability as information moves upstream in a supply chain. Causes include forecast updating, order batching, price promotions, rationing, long lead times, and poor visibility. Mitigation includes sharing point-of-sale data, reducing lead times, stabilizing prices, coordinating replenishment, and using inventory and capacity information in joint decisions.

9. Selecting and Implementing a Forecasting Process

A professional forecasting process normally includes the following sequence:

  1. Define the decision, horizon, unit of analysis, and required frequency.
  2. Establish the demand measure and clean the historical data.
  3. Identify stockouts, promotions, price changes, returns, and exceptional events.
  4. Segment items by volume, variability, lifecycle, and strategic importance.
  5. Establish a naïve benchmark.
  6. Test suitable qualitative and quantitative methods.
  7. Validate using time-ordered holdout or rolling-origin procedures.
  8. Combine statistical output with documented expert knowledge.
  9. Translate the forecast into capacity, inventory, procurement, and staffing decisions.
  10. Monitor error, bias, assumptions, and changing conditions.

Forecasting should be integrated with inventory policy. If demand during lead time is uncertain, safety stock may be required. Under a simplified independent-demand assumption, safety stock can be represented as:

SS = zσLT

where SS is safety stock, z is the service-factor corresponding to the desired cycle-service probability, and σ_LT is the standard deviation of demand during lead time. This formula is valid only when the uncertainty estimate and service interpretation are appropriate; lead-time variability, forecast error, correlation, non-normal demand, and review policies may require more advanced calculations.

The forecast should be expressed with uncertainty where possible. Prediction intervals, scenario ranges, or demand quantiles are often more useful for decisions than a point forecast alone. A capacity decision based on the expected value may be inappropriate when the cost of shortage is much higher than the cost of excess capacity.

10. Technology, AI, and Governance

Enterprise resource-planning systems, advanced planning systems, cloud data platforms, and machine-learning tools can automate data preparation, model comparison, anomaly detection, and forecast updating. Machine-learning models may capture nonlinear relationships and interactions, but they require sufficient representative data and careful validation.

Technology does not remove the need for operational judgment. Common risks include data leakage, where future information enters model training; concept drift, where relationships change; overfitting; unexplained model outputs; and automation bias, where planners accept system recommendations without challenge.

Good governance includes:

  • a clear owner for each forecast;
  • documented data definitions and data lineage;
  • version control for models and assumptions;
  • independent validation of important models;
  • monitoring for bias across customers, regions, or product groups;
  • controlled overrides with reasons and expiry dates;
  • access controls for commercially sensitive information; and
  • review of privacy, competition, and contractual obligations.

Forecasting customer demand can involve personal or commercially sensitive data. Organizations should collect only necessary data, protect it, comply with applicable privacy law, and avoid discriminatory or exploitative uses. Collaborative forecasts must respect confidentiality and competition law; sharing information should not become an agreement to manipulate prices or restrict supply.

11. Illustrative Case: FreshBite Distribution

Background

FreshBite is a fictional regional distributor of chilled prepared meals. It supplies supermarkets and workplace catering customers. Demand is weekly, expires quickly, and rises during colder months. The company historically used the previous week’s orders as its forecast.

Problem

FreshBite experienced frequent stockouts for popular vegetarian meals and excessive waste for two slower products. Retailer promotions were communicated late, and the distributor received only shipment data rather than point-of-sale data. Managers believed the forecasting problem was purely statistical, but investigation showed that data definitions and collaboration were also inadequate.

Analysis

The planning team separated retailer shipments from estimated consumer sales, identified periods affected by stockouts, and created a product-location-week data set. It compared a naïve model, a four-week moving average, and exponential smoothing. The team also examined weekday composition, promotional events, temperature, and remaining shelf life.

For the high-volume vegetarian product, a four-week moving average was too slow after a successful promotion. Exponential smoothing with a higher α responded more quickly, but it also reacted excessively to one unusual order. The team therefore used a baseline statistical forecast, a promotion adjustment based on historical uplift, and a short-term demand-sensing adjustment using daily point-of-sale data from two major retailers.

Approach and solution

FreshBite introduced a weekly collaborative planning meeting. Retailers shared promotion calendars, point-of-sale information, and inventory levels. FreshBite reported capacity constraints and shelf-life limits. Forecast overrides required a recorded reason and were reviewed after the event.

The company used different policies by segment: stable high-volume items used exponential smoothing; items with clear annual seasonality used seasonal models; new products used market research and analogues; and intermittent items were managed through service-level and replenishment rules rather than an ordinary average alone.

Outcome

In this illustrative case, forecast bias declined, stockouts on promoted items were reduced, and waste fell for slow-moving products. The improvement came not from selecting one universally superior algorithm, but from combining clean data, segmentation, collaboration, event information, and disciplined review.

Learning points

  1. A shipment forecast is not necessarily a consumer-demand forecast.
  2. Forecast accuracy depends on data quality and process design as well as model choice.
  3. Promotional and shelf-life information must be integrated with statistical forecasts.
  4. Different demand patterns require different methods.
  5. Forecast governance makes overrides reviewable and prevents unstructured optimism.

12. Challenges and Limitations

No forecasting method eliminates uncertainty. Historical data may be incomplete, censored by stockouts, distorted by promotions, or inconsistent across systems. Forecasts may fail after structural breaks, especially when models extrapolate past relationships into a changed environment.

Long-horizon forecasts are usually more uncertain than short-horizon forecasts, although a long horizon may be easier to forecast in aggregate than at individual-item level. Aggregation can reduce random variation, but it may conceal local shortages and substitution effects. Disaggregation of an aggregate forecast is therefore not automatically accurate.

Expert judgment can add valuable information but can also introduce bias. Statistical models can provide apparent objectivity while embedding biased data or inappropriate assumptions. Performance measures can create dysfunctional behaviour if employees are rewarded for low forecast error by deliberately producing conservative forecasts or manipulating inputs.

Managers should therefore evaluate the total decision system: forecast, inventory policy, capacity flexibility, lead time, service objectives, and the cost of error. The best forecast is not necessarily the one with the lowest historical error; it is the one that improves decisions under current conditions.

Chapter Summary

Forecasting provides structured estimates of future demand, while demand management coordinates the interpretation and response to that demand. Forecasts may be qualitative or quantitative. Qualitative methods are valuable when data are scarce or structural change is expected; quantitative methods include naïve forecasts, moving averages, exponential smoothing, regression, and seasonal models.

Moving averages smooth observations by averaging recent demand, whereas exponential smoothing weights recent information through a smoothing constant. Trend and seasonality require enhanced methods rather than simple level models. Regression introduces causal or explanatory variables but requires careful attention to assumptions, data availability, residuals, and the distinction between association and causation.

Forecast errors should be measured using appropriate indicators such as ME, MAE, MSE, RMSE, MAPE, and WAPE. No single measure is sufficient in all contexts, especially when demand is zero or intermittent. Bias, validation design, forecast horizon, and business consequences must also be considered.

Demand sensing uses timely operational signals, and collaborative planning aligns the information and decisions of supply-chain partners. These practices can reduce the bullwhip effect when supported by reliable data, shared definitions, appropriate incentives, and governance. Technology and AI can improve speed and pattern recognition, but they require validation, transparency, privacy protection, and human accountability.

Key Terms

Forecast: A systematic estimate of a future quantity or condition.

Demand management: The process of understanding, influencing, prioritizing, and fulfilling demand.

Time series: Observations recorded sequentially over time.

Level: The underlying average magnitude of a demand series.

Trend: A persistent long-term upward or downward movement.

Seasonality: A recurring pattern at a known frequency.

Naïve forecast: A forecast based on the latest observation or corresponding prior season.

Moving average: The mean of a specified number of recent observations.

Exponential smoothing: A method that updates a forecast using a weighted combination of recent demand and the previous forecast.

Regression: A statistical method relating a dependent variable to one or more explanatory variables.

Forecast error: The difference between actual demand and forecast demand.

Bias: Persistent over- or under-forecasting.

MAE: Mean absolute error, measured in demand units.

RMSE: Root mean squared error, which emphasizes large errors.

MAPE: Mean absolute percentage error, subject to problems with zero or very small actual values.

Demand sensing: Use of recent high-frequency signals to update a demand estimate.

Collaborative planning: Joint planning and information sharing between supply-chain participants.

Bullwhip effect: Amplification of demand variability upstream in a supply chain.

Structural break: A lasting change in the process generating demand.

Forecast governance: Policies for ownership, validation, overrides, monitoring, and accountability.

Review Questions

Short Answer Questions

  1. What is the difference between forecasting and demand management?
  2. State two situations in which qualitative forecasting is appropriate.
  3. How does increasing the window size of a moving average affect responsiveness?
  4. Why can MAPE be problematic when actual demand is zero?
  5. What is the bullwhip effect?

Long Answer Questions

  1. Compare moving averages and exponential smoothing, including their assumptions, advantages, and limitations.
  2. Explain how trend and seasonality should be diagnosed and incorporated into a forecasting process.
  3. Discuss the role of regression in demand forecasting and explain why correlation does not prove causation.
  4. Develop a forecasting governance process for a multi-site manufacturing organization.
  5. Explain how demand sensing and collaborative planning can improve supply-chain performance.

Analytical / Application Questions

  1. Demand in the last four periods was 80, 100, 120, and 140 units. Calculate the four-period moving-average forecast for the next period. Explain one limitation of this forecast if demand is continuing to trend upward.
  2. Using α = 0.25, a previous forecast of 200 units, and actual demand of 240 units, calculate the next exponential-smoothing forecast. Interpret the result.
  3. A retailer has frequent stockouts during promotions and excess inventory after promotions. Design an integrated forecasting and demand-management response, specifying data, methods, collaboration, and performance measures.

Multiple Choice Questions with Answers

Question 1

Which forecasting method gives equal weight to each of the most recent k observations?

A. Simple moving average

B. Simple exponential smoothing

C. Linear regression

D. Delphi method

Correct Answer: A. Simple moving average

Question 2

Actual demand is 120 units and the forecast is 100 units. What is the forecast error using eₜ = Yₜ − Fₜ?

A. −20 units

B. 20 units

C. 120 units

D. 220 units

Correct Answer: B. 20 units

Question 3

A three-period moving average uses demands of 90, 120, and 150 units. What is the next forecast?

A. 110 units

B. 120 units

C. 130 units

D. 150 units

Correct Answer: B. 120 units

Question 4

In simple exponential smoothing, a larger α generally makes the forecast:

A. Less responsive to recent demand

B. More responsive to recent demand

C. Independent of the previous forecast

D. Automatically seasonal

Correct Answer: B. More responsive to recent demand

Question 5

Which measure is expressed in the original demand units and penalizes large errors more strongly than MAE?

A. MAPE

B. ME

C. RMSE

D. Seasonal index

Correct Answer: C. RMSE

Question 6

Which situation is most appropriate for a qualitative forecasting method?

A. A stable product with ten years of clean weekly data

B. A new product with no historical sales

C. A product with a reliable seasonal database

D. A repetitive process with no market changes

Correct Answer: B. A new product with no historical sales

Question 7

For a multiplicative seasonal model, a seasonal index of 1.20 indicates that the season is typically:

A. 20% below the underlying level

B. 20 demand units above the underlying level

C. 20% above the underlying level

D. Unrelated to the underlying level

Correct Answer: C. 20% above the underlying level

Question 8

What is a principal purpose of demand sensing?

A. To eliminate all forecast uncertainty

B. To use recent operational signals to update short-term demand estimates

C. To replace inventory records with expert opinion

D. To guarantee that demand is independent of supply

Correct Answer: B. To use recent operational signals to update short-term demand estimates

Question 9

Which practice can help reduce the bullwhip effect?

A. Hiding point-of-sale data from suppliers

B. Increasing order batching

C. Sharing timely demand and inventory information

D. Changing prices unpredictably

Correct Answer: C. Sharing timely demand and inventory information

Question 10

Using α = 0.25, a previous forecast of 200 units, and actual demand of 240 units, what is the next exponential-smoothing forecast?

A. 205 units

B. 210 units

C. 220 units

D. 240 units

Correct Answer: B. 210 units

Advanced Operations Management
Chapter 4 of 15