Consider a mid-size automotive parts manufacturer in the Marmara region: the sales team submits an ambitious demand forecast for the second half of the year, while the production manager flags serious uncertainty in raw material supply. The planning meeting ends with a compromise — a single plan that is neither as optimistic as sales expects nor as cautious as production recommends. When actual demand comes in well above or below that figure mid-season, the plan gets rewritten from scratch. The scenario management function within MRP II is designed precisely to break this cycle.
MRP II — Manufacturing Resource Planning — is an integrated planning layer that connects production orders, material requirements, and capacity needs into a single coherent model. The core MRP calculation, determining which materials are needed in what quantities and when, is available in most production software packages. Scenario management extends this by running the calculation across multiple possible futures simultaneously rather than committing to one. In practice, this means maintaining three distinct plan sets in the system at the same time: an optimistic scenario, a base scenario, and a pessimistic scenario.
The optimistic scenario is built on the highest demand expectations the sales team can justify; capacity utilization is pushed high and material purchase orders are sized generously. The base scenario draws on historical performance data and the current order book, representing the middle-ground forecast most companies use as their working plan. The pessimistic scenario models adverse conditions — a demand slowdown, a supplier disruption, or a production line outage — with capacity utilization trimmed and inventory targets pulled back. These three scenarios do not cancel each other out; all three remain live in the system and management decides which one is the active plan at any given time.
The real value of scenario management lies in defining trigger conditions in advance. Working on a project with a textile manufacturer, the most expensive pattern I observed was the delay between recognizing that conditions had shifted and actually revising the plan — a process that took weeks because new calculations had to be done manually and suppliers had to be notified by fax or phone. MRP II scenario infrastructure eliminates that lag: management defines upfront that ‘if monthly order intake falls more than fifteen percent below the base scenario, we switch to the pessimistic plan.’ When that threshold is crossed, the system is already prepared; material requirements, production orders, and capacity allocations are ready to be recalculated at the push of a button.
Capacity scenarios work the same way. Every machine park has a gap between theoretical capacity and realistic capacity — planned maintenance, shift changes, and scrap rates all contribute to that gap. An optimistic capacity scenario accounts for overtime and additional shifts; a pessimistic scenario models the possibility of one production line going offline. When a manager has prepared and saved these scenarios in the system, they can see the full material and capacity load of each option in minutes — before entering a price negotiation with a supplier or committing to a delivery date with a customer.
The practical difficulty with this approach is keeping the scenarios current. As the number of scenarios grows, so does the maintenance burden; when the sales forecast changes, raw material prices shift, or a supplier signals a capacity constraint, all three scenarios need to be updated. In smaller manufacturing companies this work typically falls to a single planning coordinator, and when that person is overloaded the scenarios go stale. A second common problem is the absence of a clear decision-making structure around scenario switching; when the trigger condition is met and the sales manager and production manager are each advocating for a different scenario, the resulting delay erases much of the benefit the system was meant to provide.
For a SME manager evaluating MRP II scenario management, two questions are decisive. First, how often does the current planning cycle break down — if the plan is being rewritten from scratch two or three times a year, a scenario infrastructure pays for itself quickly in reduced rework and faster response. Second, can the organization build a clear ownership structure for scenario transition decisions and trigger monitoring — regardless of how capable the software is, if the answer to that question is no, the scenario module will not deliver the results it promises. When properly configured, scenario management frees production planning from dependence on a single forecast and turns uncertainty into a variable that can actually be managed.
This article was originally written in Turkish by Gökhan MERCANOĞLU on May 30, 2005 and has been automatically translated into English and other languages using machine translation.