Supply, Production, and Integrated Business Planning Systems

Introduction

Supply chain management software has evolved from tools that calculate material requirements into integrated platforms that coordinate demand, production, distribution, finance, and strategy. This evolution reflects a fundamental managerial problem: a supply chain must satisfy customer demand while operating with limited materials, labor, equipment, cash, time, and information.

Material Requirements Planning (MRP), Distribution Requirements Planning (DRP), capacity planning, finite scheduling, constraint management, and Available-to-Promise (ATP) address different parts of this problem. Advanced Planning and Scheduling (APS) systems connect these capabilities through more sophisticated models of time, capacity, constraints, and trade-offs. Integrated Business Planning (IBP) extends the planning horizon and links operational plans to financial and strategic decisions.

These systems do not eliminate managerial judgment. Their outputs depend on data quality, modeling assumptions, organizational behavior, and the governance of trade-offs. A technically sophisticated planning engine can produce poor decisions when bills of material are inaccurate, inventory records are unreliable, capacity calendars are outdated, or commercial assumptions are politically manipulated.

Learning Objectives

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

1. Explain the purpose, logic, and limitations of MRP and DRP.
2. Distinguish aggregate capacity planning from detailed finite scheduling.
3. Analyze bottlenecks and explain the role of constraint management.
4. Calculate and interpret ATP under simple planning assumptions.
5. Compare heuristic, optimization, and simulation approaches in APS.
6. Evaluate how IBP reconciles demand, supply, finance, and strategic scenarios.
7. Assess implementation, governance, ethical, and managerial issues in planning systems.

1. The Planning Hierarchy

Planning systems operate across several time horizons. Strategic planning concerns network design, product portfolios, sourcing structure, and long-term capacity. Tactical planning translates business expectations into aggregate production, inventory, procurement, and workforce plans. Operational planning converts these plans into material orders, production sequences, shipment commitments, and exception responses.

A simplified hierarchy is:

The hierarchy is not purely sequential. Strategic decisions constrain tactical choices, while operational data can reveal that a strategic assumption is unrealistic. Effective platforms therefore support both top-down planning and bottom-up feedback.

2. Material Requirements Planning

2.1 Purpose and logic

MRP determines what materials and components are needed, how many are required, and when orders should be released. It is primarily a dependent-demand planning method. Demand for a component depends on the planned production of its parent item. For example, demand for batteries depends on the planned production quantity of vehicles using those batteries.

MRP requires five central inputs:

• a master production schedule (MPS);
• bills of material (BOMs);
• inventory records;
• planned lead times;
• order policies and calendar information.

The MPS specifies when finished products should be completed. The BOM specifies the quantity and structure of components required. Inventory records identify on-hand stock, scheduled receipts, open orders, safety stock, and item status. Lead times translate required receipt dates into release dates.

2.2 MRP calculation

For a planning period t, a basic projected available balance can be expressed as:

where:

• PAB_t = projected available balance at the end of period t, in units;
• SR_t = scheduled receipts in period t, in units;
• PORc_t = planned-order receipts in period t, in units;
• GR_t = gross requirements in period t, in units.

If the projected balance would fall below the required safety stock, net requirements are generated:

where NR_t is net requirement and SS_t is safety stock. This formulation assumes that the relevant inventory and receipts are available in the stated period and that requirements and receipts are measured in the same unit.

A planned-order receipt is converted into a planned-order release by offsetting it by lead time. If the lead time is L periods:

where PORl_t−L is the planned-order release in the period that is L periods before the required receipt.

2.3 Worked MRP example

Suppose a component has 40 units on hand, no scheduled receipts, safety stock of 10 units, and gross requirements of 30, 50, and 20 units in periods 1, 2, and 3. Assume lot-for-lot ordering and a one-period lead time.

For period 2, the requirement is 50 units and the beginning balance is 10 units. To preserve the 10-unit safety stock, the system plans a receipt of 50 units. The resulting ending balance is 10 units. The receipt is released one period earlier.

MRP is powerful when demand is dependent and product structures are stable. It becomes less reliable when lead times are highly variable, BOMs are inaccurate, demand is not properly translated into the MPS, or capacity limitations prevent planned orders from being executed.

3. Distribution Requirements Planning

DRP applies MRP-like logic to replenishment across a distribution network. Instead of exploding a finished product into components, DRP uses the distribution structure: central warehouse, regional distribution centers, local depots, and sometimes customer-facing locations.

DRP plans time-phased replenishment by considering forecast demand, customer orders, inventory, safety stock, transportation lead times, lot sizes, and scheduled receipts. Demand at a regional warehouse becomes a requirement for the supplying central warehouse. In turn, the central warehouse may generate a requirement for a plant or supplier.

The key distinction is that MRP addresses dependent demand in a product structure, whereas DRP addresses replenishment demand in a geographic or distribution structure. Modern systems often integrate both. A finished product may be planned through DRP to a regional warehouse and then through MRP into its component requirements.

DRP must account for transportation calendars and shipment constraints. A replenishment recommendation that is feasible at the plant may be infeasible if a carrier does not operate on the relevant day, if a truck has insufficient capacity, or if receiving hours restrict delivery.

4. Capacity Planning

Material feasibility does not guarantee production feasibility. Capacity planning tests whether labor, machines, tools, warehouse space, suppliers, or transportation resources can support the plan.

4.1 Rough-cut and detailed capacity planning

Rough-cut capacity planning evaluates major resource groups at an aggregate level. It may use product-family rates, standard hours, or resource percentages. Its purpose is to identify strategic or tactical overloads before detailed schedules are produced.

Detailed capacity planning evaluates individual work centers, operations, shifts, calendars, setup times, and alternative resources. It is closer to execution and requires more detailed data.

A basic load calculation is:

where:

• Load_r,t = required hours on resource r in period t;
• Q_i,t = quantity of item i planned in period t;
• a_i,r = standard resource hours per unit of item i on resource r;
• the summation includes all items using resource r.

Available capacity may be estimated as:

where N is the number of equivalent resources, H is scheduled hours per resource, A is the availability factor, and E is the efficiency factor. All time terms must use the same unit, such as hours. The capacity utilization ratio is:

A ratio above 1 indicates overload under the stated assumptions; it does not prove that no schedule is possible, because overtime, subcontracting, alternate resources, or reduced processing times may be available.

4.2 Capacity example

A work center has two machines. Each is scheduled for 8 hours per day over five days, with availability of 90% and efficiency of 95%.

If the planned load is 72 hours, utilization is:

Thus the planned load is approximately 105.3% of modeled capacity. Management must decide whether to change the mix, authorize overtime, use another resource, subcontract, or revise customer commitments.

5. Finite Scheduling

Infinite-capacity planning places work according to dates without fully preventing resource overload. Finite scheduling explicitly recognizes that a resource cannot process more work than its available time. It sequences operations subject to calendars, material availability, setup times, precedence relationships, labor skills, tooling, and due dates.

A schedule can be represented by start and completion times. For an operation with processing time p and setup time s:

This relationship assumes that setup and processing are performed sequentially and that no interruption occurs. If operations overlap, batch, or are subject to transfer lots, a different representation is required.

Common dispatching rules include:

• earliest due date (EDD), which prioritizes the smallest due date;
• shortest processing time (SPT), which prioritizes short jobs;
• first-come, first-served (FCFS);
• critical-ratio sequencing, which compares remaining time to required processing time.

No rule is universally optimal. EDD may reduce lateness, SPT may reduce average flow time, and a critical-ratio rule may respond better to changing urgency. Real systems often use a priority score combining due date, customer importance, setup family, material status, and constraint criticality.

Finite scheduling is computationally difficult for many real-world environments. Consequently, APS platforms combine exact optimization for selected subproblems with heuristics, constraint propagation, local search, and user-defined priorities. A mathematically optimal schedule under an incomplete model may be inferior to a practical schedule incorporating labor relations, maintenance realities, or customer service commitments.

6. Constraint Management and the Theory of Constraints

A constraint is a factor that limits the performance of a system. It may be an internal bottleneck, such as a heat-treatment furnace, or an external constraint, such as a regulated supplier or market demand.

The Theory of Constraints (TOC) commonly describes a five-step focusing process:

1. Identify the system’s constraint.
2. Exploit it by using its scarce time effectively.
3. Subordinate other activities to the constraint’s requirements.
4. Elevate the constraint by adding or expanding capacity.
5. Repeat the process when the constraint moves.

The distinction between local efficiency and system performance is crucial. Maximizing utilization at every work center can increase work-in-process inventory and delay orders if upstream operations produce material faster than the bottleneck can consume it.

A useful bottleneck measure is throughput per constrained hour. If product j yields contribution margin C_j and consumes h_j hours of bottleneck time, then:

This ratio supports short-term product-mix decisions when demand is sufficient, variable costs are correctly defined, and the constraint is genuinely binding. It should not be treated as a complete long-term profitability measure because it omits strategic effects, fixed-cost changes, quality risks, and future capacity.

Constraint management in software includes bottleneck identification, finite-capacity checks, buffer monitoring, exception alerts, and what-if analysis. The system should distinguish a true constraint from a temporary data anomaly or an artificially restrictive calendar.

7. Available-to-Promise and Capable-to-Promise

ATP represents the quantity of uncommitted product that can be promised to customers for specified dates. A simple discrete-period formulation is:

For the first period, existing commitments may include orders due before the next replenishment. In later periods, ATP is commonly calculated against scheduled receipts and the next replenishment event rather than independently subtracting every demand in the planning horizon. Exact definitions vary across ERP and APS products, so organizations must document their convention.

Consider 100 units on hand, a scheduled receipt of 60 units in period 2, and existing commitments of 70 units in period 1 and 40 units in period 2. Under a simple period-by-period convention:

• Period 1 ATP = 100 − 70 = 30 units.
• Period 2 ATP associated with the receipt = 60 − 40 = 20 units.

The firm can promise 30 units for period 1 or, subject to policy, 20 units against the period-2 receipt. It cannot promise 50 units for period 1 merely because 60 units arrive in period 2.

Capable-to-Promise (CTP) goes further. If finished goods are unavailable, CTP checks whether materials, capacity, and operations can produce the requested quantity by the requested date. ATP is therefore inventory-and-receipt based, while CTP is feasibility based.

ATP accuracy depends on inventory integrity, order status, allocation rules, safety-stock policy, production reliability, and synchronization between sales and operations. A promise is a commercial commitment, not merely a calculated number.

8. Optimization in APS

APS platforms seek feasible and desirable plans across multiple resources and time periods. They may use:

• heuristics for rapid, transparent rules;
• mathematical programming for explicitly modeled trade-offs;
• constraint programming for complex logical and sequencing relationships;
• simulation for uncertainty and policy testing;
• metaheuristics for large combinatorial problems.

A simplified linear planning model might minimize total cost:

subject to inventory balance:

where:

• P_t = production quantity;
• I_t = ending inventory;
• R_t = receipts from external supply;
• D_t = demand;
• B_t = backorders or unmet demand;
• O_t = overtime or another modeled decision;
• c^p, cⁱ, c^b, c^o = corresponding unit costs.

This model assumes additive costs, known demand, and linear relationships. Real systems add capacity constraints, minimum lots, changeovers, alternative resources, shelf life, transport lanes, and service-level requirements. Binary variables may be needed for setup decisions or facility activation, making the model a mixed-integer program.

Optimization does not determine the “best” plan in an absolute sense. It determines the best plan under the objective function, constraints, data, and time horizon supplied. If stockout cost is understated, the system may favor low inventory. If revenue is prioritized without service constraints, it may allocate scarce supply to high-margin customers while damaging strategic relationships.

9. Integrated Business Planning

IBP is a cross-functional management process and, increasingly, a software-supported planning architecture. It integrates:

1. demand review;
2. supply review;
3. inventory and financial review;
4. reconciliation of gaps and opportunities;
5. executive decision-making.

The demand plan should include statistical forecasts, customer intelligence, promotions, market assumptions, and commercial judgment. The supply review tests capacity, materials, suppliers, logistics, and inventory implications. Finance translates volume and operational assumptions into revenue, cost, working capital, cash flow, and profitability. Executive review selects actions and assigns accountability.

IBP differs from a simple planning dashboard because it requires a common set of assumptions, explicit scenario comparison, decision rights, and integration with financial planning. A plan is not integrated merely because several departments can view the same screen.

9.1 Scenario planning

A scenario is a coherent set of assumptions, such as a demand surge, supplier disruption, product launch, capacity expansion, or currency change. Scenario analysis should identify:

• assumptions changed;
• operational consequences;
• financial consequences;
• service and risk consequences;
• decisions required;
• indicators that would trigger a change in plan.

For example, a 15% demand increase may require overtime, premium freight, additional inventory, or customer allocation. The scenario should show not only additional sales but also contribution margin, cash requirements, capacity utilization, supplier exposure, and the probability of service failure.

9.2 Reconciliation of demand, supply, and finance

Reconciliation involves translating between different units and perspectives. Sales may propose revenue and units by market; supply planners need item, location, and time buckets; finance needs revenue, cost, margin, inventory value, and cash timing. Master data and planning hierarchies must support aggregation and disaggregation without creating contradictory numbers.

A useful governance practice is to maintain one approved baseline and separate approved scenarios. Unapproved changes should not silently overwrite the baseline. Version control, assumption ownership, and audit trails are essential.

10. Applied Case: Northstar Home Appliances

The following is an illustrative case, not a report of an actual company.

Background

Northstar produces three models of energy-efficient refrigerators. It sells through national retailers and regional distributors. The company uses an ERP system for transactions but has historically planned production through spreadsheets. Forecasts are frequently changed by sales representatives, and production planners often create excess inventory of popular components while finished products remain unavailable.

Problem

Demand for the premium model is rising. Its compressor is supplied by one vendor, and final assembly shares a testing cell with the standard model. The sales team has promised delivery dates without checking capacity. Management wants to increase service without doubling inventory.

Analysis

An MRP review reveals that the premium model’s BOM requires one compressor per unit, but the supplier’s lead time is eight weeks rather than the six weeks recorded in the system. DRP analysis shows that two regional warehouses are carrying excess standard-model inventory while a third location is experiencing stockouts. Capacity analysis shows that the testing cell will operate at 118% of available weekly capacity under the unconstrained demand plan.

Finite scheduling demonstrates that producing more refrigerators cannot solve the problem unless the testing cell is addressed. A CTP check also shows that several retailer orders promised for week 6 require components that cannot arrive before week 7.

Approach and solution

Northstar establishes a cross-functional IBP baseline. Demand management separates statistical demand from promotional uplift. Supply planning corrects the compressor lead time, introduces supplier capacity visibility, and models a second source. APS is configured to treat the testing cell as finite capacity and to prioritize orders using contractual due dates and strategic customer rules.

The company chooses four actions:

1. subcontract selected testing operations for six weeks;
2. rebalance inventory among regional warehouses;
3. revise customer promises using CTP rather than sales judgment alone;
4. evaluate a permanent testing-cell expansion through financial scenarios.

The executive team compares the scenarios using service level, margin, inventory, cash, supplier risk, and capital expenditure. The short-term subcontracting option costs more per unit but protects key retailer launches. The permanent expansion has a favorable long-term financial result only if the premium-model demand scenario persists.

Outcome

After implementation, Northstar reduces false promises, improves visibility of bottleneck utilization, and lowers regional stock imbalance. It does not achieve perfect forecast accuracy; instead, it improves decision quality by making uncertainty and trade-offs explicit. The company postpones permanent expansion until demand indicators confirm the higher-volume scenario.

Learning points

The case illustrates five principles. First, MRP cannot compensate for inaccurate lead times. Second, distribution planning must consider location-specific inventory. Third, finite capacity can invalidate an otherwise attractive demand plan. Fourth, CTP is essential when customer commitments depend on production feasibility. Fifth, IBP creates value by linking operational choices to financial and strategic consequences rather than by producing a single supposedly objective forecast.

11. Implementation, Governance, and Contemporary Issues

Data and process governance

Critical master data includes item identifiers, BOMs, routings, lead times, calendars, lot sizes, sourcing rules, inventory status, and customer priorities. Ownership must be explicit. Data-quality measures should include completeness, accuracy, timeliness, and conformance to approved structures.

Organizational adoption

Planning software changes authority. Sales may lose the ability to promise unconstrained dates; production may lose informal control over priorities; finance may gain greater visibility into operational assumptions. Implementation therefore requires process design, training, role clarity, and escalation rules, not only technical configuration.

AI and advanced analytics

Machine learning can support demand sensing, anomaly detection, lead-time prediction, and parameter recommendation. However, predictive accuracy does not guarantee decision quality. AI systems may reproduce historical allocation bias, obscure causal assumptions, or respond poorly to unprecedented disruptions. Human oversight, explainability appropriate to the decision, model monitoring, and controlled override processes are necessary.

Ethics, resilience, and sustainability

Planning decisions distribute scarce supply among customers, regions, and communities. Allocation rules should be transparent and consistent with contractual, legal, safety, and ethical obligations. Systems should also support sustainability measures such as emissions, energy use, waste, and supplier labor-risk indicators. A low-cost plan that externalizes environmental or social harm is not necessarily an integrated or responsible plan.

Best practices

Effective organizations typically:

• define a single planning calendar and hierarchy;
• distinguish forecasts, orders, and commitments;
• validate MRP and DRP master data continuously;
• model bottlenecks explicitly;
• use ATP and CTP with documented promise rules;
• separate baseline plans from scenarios;
• align operational and financial calendars;
• monitor exceptions rather than manually reviewing every item;
• audit overrides and allocation decisions;
• measure plan quality by service, cost, resilience, cash, and strategic fit.

Chapter Summary

MRP converts a master production schedule into time-phased component requirements using BOMs, inventory, lead times, and order policies. DRP performs analogous replenishment planning across distribution locations. Neither method alone guarantees feasibility; capacity planning is required to compare planned load with available labor, equipment, supplier, and logistics capacity.

Finite scheduling recognizes resource limits and sequences work using calendars, precedence, setup, material, and due-date constraints. Constraint management focuses attention on bottlenecks and prevents local efficiency from undermining system performance. ATP estimates uncommitted supply, while CTP evaluates whether production and supply resources can fulfill a requested commitment.

APS platforms combine heuristics, optimization, constraint programming, and simulation to evaluate trade-offs. Their results are conditional on objectives, constraints, data, and assumptions. IBP extends the planning process by reconciling demand, supply, finance, and strategic scenarios through cross-functional governance. The central managerial lesson is that planning software is a decision-support system, not an autonomous substitute for accountable judgment.

Key Terms

MRP: A system for planning dependent-demand materials and components.

DRP: A time-phased replenishment planning method for distribution networks.

Master Production Schedule: A time-phased plan for producing finished products.

Bill of Material: A structured record of components required for a parent item.

Projected Available Balance: Expected inventory after requirements and receipts.

Net Requirement: The quantity needed after considering available inventory and receipts.

Lead Time: Time between releasing and receiving or completing an order.

Capacity Planning: Analysis of whether resources can support a proposed plan.

Finite Scheduling: Scheduling that explicitly respects resource capacity limits.

Bottleneck: A resource or condition that constrains system throughput.

Constraint Management: Identification and management of factors limiting performance.

ATP: Available-to-Promise quantity based on uncommitted supply.

CTP: Capable-to-Promise quantity based on production and supply feasibility.

APS: Advanced Planning and Scheduling software using detailed models and analytical methods.

Heuristic: A practical decision rule that seeks a good solution efficiently.

Optimization: Selection of the best modeled solution under stated objectives and constraints.

IBP: Integrated Business Planning linking demand, supply, finance, and strategy.

Scenario: A coherent set of assumptions used to evaluate possible futures.

Master Data: Foundational records that define items, structures, resources, and rules.

Review Questions

Short Answer Questions

1. What are the principal inputs required by an MRP system?
2. How does DRP differ from MRP?
3. Why can a material plan be feasible in MRP but infeasible in production?
4. Distinguish ATP from CTP.
5. What is the purpose of the IBP executive review?

Long Answer Questions

1. Explain the logic of MRP, including projected available balance, net requirements, and lead-time offsetting.
2. Compare rough-cut capacity planning, detailed capacity planning, and finite scheduling.
3. Explain the five-step focusing process associated with constraint management and discuss its managerial implications.
4. Evaluate the strengths and limitations of optimization in APS platforms.
5. Discuss how IBP reconciles operational plans with financial and strategic decisions.

Analytical / Application Questions

1. A plant has 3 machines, each scheduled for 36 hours per week. Availability is 92% and efficiency is 90%. A proposed plan requires 92 hours. Calculate available capacity and utilization, then recommend two possible responses.
2. A warehouse has 240 units on hand, 80 units already committed in the current period, and a scheduled receipt of 150 units in the next period. Explain the maximum current-period promise under a simple ATP convention and identify information needed before promising additional units.
3. A company’s demand plan is profitable but overloads a single finishing resource by 20%. Design an IBP scenario comparison including at least four operational or financial measures and recommend what information executives should require before approving the plan.

Multiple Choice Questions with Answers

Question 1

Which input is most directly required to explode a finished-product requirement into component requirements in MRP?

A. Bill of material

B. Customer satisfaction survey

C. Carrier fuel index

D. Annual financial statement

Correct Answer: A. Bill of material

Question 2

A work center has 80 hours of available capacity and a planned load of 72 hours. What is its utilization?

A. 8%

B. 72%

C. 90%

D. 152%

Correct Answer: C. 90%

Question 3

What is the defining feature of finite scheduling?

A. It ignores resource calendars

B. It explicitly respects resource capacity limits

C. It plans only purchased materials

D. It eliminates the need for due dates

Correct Answer: B. It explicitly respects resource capacity limits

Question 4

Which statement best distinguishes CTP from ATP?

A. CTP evaluates production feasibility, whereas ATP evaluates uncommitted supply

B. CTP applies only to warehouses, whereas ATP applies only to factories

C. CTP ignores capacity, whereas ATP models every constraint

D. CTP is a financial forecast, whereas ATP is a sales forecast

Correct Answer: A. CTP evaluates production feasibility, whereas ATP evaluates uncommitted supply

Question 5

Under a simple ATP convention, inventory is 100 units and existing commitments are 70 units. What quantity is available to promise in the current period?

A. 30 units

B. 70 units

C. 100 units

D. 170 units

Correct Answer: A. 30 units

Question 6

In the Theory of Constraints, what should normally occur after identifying a system constraint?

A. Maximize inventory at every work center

B. Exploit the constraint’s scarce capacity

C. Remove all customer priorities

D. Stop measuring throughput

Correct Answer: B. Exploit the constraint’s scarce capacity

Question 7

What is a principal purpose of DRP?

A. Exploding a BOM into raw materials

B. Planning replenishment across distribution locations

C. Calculating employee compensation

D. Designing product packaging

Correct Answer: B. Planning replenishment across distribution locations

Question 8

Why can an optimization model produce an undesirable managerial recommendation?

A. Optimization never uses constraints

B. The result depends on the objective, constraints, data, and assumptions modeled

C. Optimization always maximizes inventory

D. Optimization cannot compare alternatives

Correct Answer: B. The result depends on the objective, constraints, data, and assumptions modeled

Question 9

Which activity is most characteristic of IBP?

A. Reconciling demand, supply, financial, and strategic scenarios

B. Recording only warehouse receipts

C. Replacing all executive decisions with an algorithm

D. Calculating only machine setup times

Correct Answer: A. Reconciling demand, supply, financial, and strategic scenarios

Question 10

A resource has 2 machines, 40 scheduled hours per machine, 90% availability, and 95% efficiency. What is modeled available capacity?

A. 36.0 hours

B. 40.0 hours

C. 68.4 hours

D. 76.0 hours

Correct Answer: C. 68.4 hours