Dependent-Demand Inventory and Requirements Planning

Introduction and context

Inventory control changes fundamentally when demand for an item is derived from the demand for another item. A finished bicycle may have independent demand determined by customers; its tires, chains, brake assemblies, and packaging have dependent demand determined largely by the bicycles scheduled for production. This distinction is the foundation of material requirements planning (MRP).

MRP is a time-phased planning logic that converts a master production schedule into requirements for components and purchased materials. It answers three operational questions: what is needed, how much is needed, and when must it be available? Modern MRP is usually embedded in enterprise resource planning (ERP), but its logic remains based on bills of materials, inventory status records, lead times, scheduled receipts, and lot-sizing rules.

MRP does not eliminate uncertainty or replace managerial judgment. It is a planning system whose quality depends on data accuracy, realistic schedules, disciplined execution, and appropriate integration with capacity, suppliers, distribution, and production methods.

Learning objectives

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

1. Distinguish independent from dependent demand.
2. Interpret a bill of materials and calculate gross and net requirements.
3. Explain inventory status records, time phasing, planned receipts, and planned order releases.
4. Apply common MRP lot-sizing methods and evaluate their consequences.
5. Diagnose nervousness and other MRP failure modes.
6. Relate MRP to distribution requirements planning (DRP), ERP, capacity planning, and lean or just-in-time systems.
7. Design practical governance controls for an integrated requirements-planning process.

1. Independent and dependent demand

Independent demand arises outside the immediate control of the production system. Customer orders, forecasts, service demand, and replacement demand are typical sources. It is commonly managed with reorder points, safety stock, and statistical forecasting.

Dependent demand is calculated from the planned or actual demand for a higher-level item. If each finished product requires four bolts, a production plan for 500 finished products creates a gross requirement for 2,000 bolts, before considering inventory, scheduled receipts, scrap, and policy stock. Forecasting every bolt independently would obscure the causal relationship and can create unnecessary variability.

The distinction is not absolute. A component can have dependent demand in one use and independent demand in another. A standard motor used in a product may also be sold as a spare part. The first demand stream is dependent; the second is independent. Planning policies must therefore be defined by item, location, and use rather than by broad product category alone.

MRP is most effective when:

• the end-item schedule is reasonably known;
• product structures are valid and sufficiently detailed;
• component usage is predictable from parent production;
• lead times and inventory records are credible; and
• orders can be planned in discrete time periods.

For highly repetitive environments with stable flow, kanban or other pull mechanisms may control replenishment more simply. For complex, customized, or intermittently produced products, MRP provides valuable forward visibility.

2. The bill of materials as a product model

A bill of materials (BOM) is a structured representation of the components, subassemblies, materials, and quantities required to make one unit of a parent item. A single-level BOM identifies direct components. A multilevel BOM represents the complete product structure, including components within subassemblies.

A BOM normally contains:

• item identification and description;
• parent-child relationships;
• quantity per assembly;
• unit of measure;
• engineering revision or effectivity date;
• scrap or yield information where relevant;
• phantom, co-product, or substitute designations; and
• planning and procurement attributes.

A product structure can be represented as a tree. Suppose one finished unit, A, requires two units of B and three units of C. Each B requires four units of D, while each C requires two units of D. The total quantity of D per A is:

This calculation assumes that all components are used in the stated quantities, no alternate BOM is selected, and losses are ignored. If a component has a yield of 95%, the gross planned quantity must be adjusted according to the organization’s yield convention. For a required output of 100 good units and a yield of 0.95, the planned input is approximately 105.26 units, normally rounded according to the item’s unit and lot policy.

BOM accuracy and governance

BOM errors propagate downward. An omitted component can stop production; an overstated quantity can generate excess purchasing; an obsolete revision can produce nonconforming product. Governance therefore includes engineering change control, approval of effectivity dates, audit trails, unit-of-measure discipline, and reconciliation between the engineering BOM, manufacturing BOM, and planning BOM.

A phantom assembly is a logical grouping that is not normally stocked or scheduled as a separate item. It allows planners to organize a structure without creating unnecessary inventory transactions. A modular BOM may support configuration choices, but alternatives must be controlled so that MRP does not simultaneously plan mutually exclusive components.

3. Inventory status records

For each planned item, MRP requires an inventory status record. The record is the system’s operational picture of supply and demand over time. Typical fields include:

The record should distinguish inventory that is physically present from inventory that is available for the particular requirement. Quarantined, damaged, consigned, expired, or customer-reserved stock may not be usable. Likewise, an open purchase order is not equivalent to received inventory; its quantity and expected date remain uncertain until confirmed.

Data quality is a managerial issue, not merely an information-technology issue. Cycle counting, transaction discipline, supplier confirmation, manufacturing reporting, and exception review are essential controls.

4. MRP logic: explosion, netting, and time phasing

4.1 Requirements explosion

Requirements explosion translates parent requirements into component requirements using the BOM. If the planned order release for a parent is 300 units and each parent requires five units of a component, the component’s gross requirement is 1,500 units in the period in which the parent is scheduled to be produced. For multilevel structures, the process continues downward until purchased or manufactured planning items are reached.

The timing basis is important. A component is generally required when its parent is needed, not when the finished product is shipped. If a subassembly requires two days to build, its components must be available before the subassembly’s start date.

4.2 Netting

Netting offsets gross requirements with available inventory and scheduled receipts. A simplified projected available balance is:

where PAB_t is projected available balance at the end of period t, SR_t is the scheduled receipt in period t, POR_t is the planned order receipt in period t, and GR_t is the gross requirement in period t. The equation assumes all receipts are available in the stated period and that inventory is measured in consistent units.

If a safety-stock requirement exists, the planner must prevent the projected balance from falling below that level. A common net-requirement expression is:

where NR_t is net requirement and SS is the required safety-stock level. Organizations vary in whether safety stock is included explicitly in projected balances or treated as a protected floor; the policy must be documented to avoid double counting.

Worked example: single-level netting

A component has 80 units on hand. A scheduled receipt of 40 units is due in week 2. Gross requirements are 30 units in week 1, 70 in week 2, and 50 in week 3. No safety stock is required, and a lot-for-lot rule is used.

In week 3, the available 20 units are insufficient, so the net requirement is 30 units. A planned receipt of 30 is created in week 3. If the component’s lead time is one week, the planned order release occurs in week 2. The receipt date and release date are not interchangeable.

4.3 Time phasing and offsetting

Time phasing assigns requirements and receipts to periods. Lead-time offsetting then moves a planned receipt backward to determine its release date. If a purchased item has a two-week lead time and is required in week 6, the planned order should be released in week 4, assuming a calendar in which two full planning periods separate release and receipt.

In practice, lead time may include supplier processing, transportation, receiving, inspection, queue time, setup, and internal movement. A nominal supplier lead time that excludes these elements creates systematically late plans. Calendars should also account for weekends, holidays, shutdowns, and capacity calendars.

5. Lot sizing and planning trade-offs

MRP determines when supply is required, but a lot-sizing rule determines how much to order or produce. The choice affects setup cost, purchase price, inventory, cash, obsolescence, capacity, and schedule stability.

Lot-for-lot

Lot-for-lot creates an order equal to the net requirement in each period. It minimizes planned cycle inventory and is attractive for expensive, perishable, or highly variable items. Its disadvantages are frequent orders, setups, deliveries, and possible supplier inefficiency.

Fixed order quantity

A fixed quantity, such as a container size, minimum supplier lot, or economic order quantity, is used whenever a net requirement occurs. It is operationally convenient but may create excess inventory.

The classical economic order quantity is:

where Q* is the order quantity in units per order, D is annual demand in units per year, S is ordering or setup cost per order, and H is annual holding cost per unit per year. The model assumes relatively constant demand, instantaneous replenishment, no quantity discounts, and a linear holding-cost approximation. It is a benchmark, not a universal MRP rule. In a constrained or intermittent environment, supplier minimums, capacity, transportation, and service requirements may dominate the EOQ result.

Period-order quantity

Period-order quantity groups requirements over a specified number of periods. For example, a two-period rule may combine current and next-period net requirements. It reduces order frequency but increases average inventory and can cause over-supply when demand changes.

Least total cost and least unit cost

Dynamic lot-sizing methods evaluate alternative groupings of future requirements. Least total cost seeks a grouping in which incremental holding cost is close to setup or ordering cost. Least unit cost evaluates cost per unit across candidate groupings. These methods can be useful for uneven demand, but they depend on reliable future requirements and may not reflect capacity or supplier realities.

Lot-sizing decision criteria

A professional decision should consider more than nominal cost:

• demand variability and forecast confidence;
• setup or ordering cost;
• supplier minimums and transport economics;
• shelf life, obsolescence, and quality risk;
• storage and working-capital constraints;
• production and warehouse capacity;
• service-level consequences of shortage; and
• the stability required by suppliers and employees.

6. MRP nervousness

MRP nervousness is excessive change in planned orders caused by small changes in demand, inventory, receipts, lead times, or BOM data. A modest change in an end-item schedule can cascade through several BOM levels and alter dates, quantities, and releases for many components.

Nervousness has several costs: expedited freight, supplier disruption, overtime, canceled orders, excess materials, schedule mistrust, and administrative workload. It can also create a self-reinforcing cycle. Suppliers react to unstable releases with protective lead times, which makes the plan less responsive and encourages further expediting.

Common causes include:

• frequent changes to the master production schedule;
• inaccurate inventory balances;
• unrealistic or variable lead times;
• short planning horizons;
• inappropriate lot sizes;
• lack of time fences;
• unrecorded scrap, rework, or substitutions; and
• poor coordination between sales, operations, engineering, and procurement.

Control mechanisms include:

1. Planning time fences: Freeze near-term orders while allowing changes farther out.
2. Firm and planned zones: Define which periods require approval before alteration.
3. Order-change tolerances: Avoid rescheduling small quantities or dates unless an economic threshold is exceeded.
4. Safety time or safety stock: Protect critical operations, but do not use buffers to conceal poor data.
5. Stable master scheduling: Review demand changes through a cross-functional process.
6. Exception messages: Focus planners on shortages, late receipts, invalid dates, and unusual changes.
7. Supplier collaboration: Share horizons, consume forecasts consistently, and agree on flexibility rules.

Nervousness must not be confused with responsiveness. A system that never changes may be stable but wrong. The objective is controlled responsiveness: changes should occur when their operational and economic benefits exceed the disruption they cause.

7. MRP, DRP, ERP, and capacity planning

MRP and DRP

Distribution requirements planning (DRP) applies analogous logic to replenishing warehouses, regional distribution centers, and field locations. DRP begins with customer or downstream demand, nets location inventory and scheduled receipts, and creates time-phased replenishment recommendations. Those recommendations may become shipment requirements for a supplying plant, which then become end-item requirements in MRP.

The relationship is therefore complementary. DRP plans where and when inventory should be positioned; MRP plans the materials and production needed to supply it. A distribution plan that ignores plant capacity can generate infeasible production requirements, while an MRP plan that ignores distribution priorities can manufacture the wrong mix.

MRP and ERP

ERP integrates MRP with finance, purchasing, sales, order management, warehouse operations, quality, maintenance, human resources, and sometimes customer and supplier portals. ERP can provide a shared transaction database and common master data, but integration does not guarantee good decisions. A technically integrated system can still produce poor plans if the BOM, inventory, calendar, or demand assumptions are wrong.

Important ERP governance practices include role-based authorization, master-data ownership, traceable changes, separation of duties, cybersecurity, backup and recovery, and controlled interfaces. Artificial intelligence may assist with anomaly detection, lead-time estimation, exception prioritization, or supplier-risk analysis, but it should not silently alter approved product structures or release orders without appropriate human accountability.

MRP and capacity requirements planning

Material feasibility does not imply capacity feasibility. MRP may schedule components in time while work centers lack labor hours, machine time, tooling, dock capacity, or supplier capability. Capacity requirements planning (CRP) translates planned and released orders into work-center loads and compares them with available capacity.

A simple load calculation is:

where Load_w,t is the load on work center w in period t, Q_i,t is the quantity of item i processed in that period, r_i,w is processing time per unit at work center w, and s_i,w is applicable setup time. Units must be consistent, such as labor-hours or machine-hours. The equation is a load estimate; actual feasibility also depends on sequence, finite capacity, labor skills, downtime, and calendars.

When capacity is insufficient, managers may change lot sizes, shift production, subcontract, add overtime, alter the master schedule, revise priorities, or invest in capacity. Infinite-capacity MRP is useful for material planning but should not be mistaken for a detailed finite scheduling solution.

8. MRP and lean or just-in-time systems

MRP and lean production are often presented as opposing philosophies, but they address different planning problems. MRP is primarily a planning and coordination logic based on forecasts, schedules, and product structures. Lean and just-in-time (JIT) emphasize flow, waste reduction, short lead times, small lots, quality at the source, and pull-based replenishment.

MRP is particularly useful for:

• complex, multilevel products;
• long-lead-time materials;
• low-volume or intermittent production;
• engineering changes and project environments; and
• coordinating suppliers and distributed facilities.

Kanban and other pull controls are particularly useful for:

• repetitive production;
• stable consumption between linked processes;
• short replenishment lead times; and
• disciplined, physically visible flows.

Many organizations use a hybrid approach. MRP plans long-lead and purchased items, capacity, and aggregate schedules, while kanban controls replenishment within stable production cells. Lean does not mean eliminating all records or planning; it means reducing the causes of inventory and variability. JIT also does not justify careless removal of safety stock where supply risk, quality risk, or emergency response times are substantial.

9. Applied case: Northstar Medical Devices (illustrative)

Background

Northstar Medical Devices produces a configurable infusion pump. The product has a multilevel BOM containing a control module, display assembly, battery pack, molded housing, fasteners, and purchased electronic components. Demand has increased, but production frequently expedites displays and circuit boards while excess fasteners and plastic housings accumulate.

Problem

A diagnostic review identifies three issues. First, engineering revisions are not consistently linked to BOM effectivity dates. Second, inventory records do not distinguish quality-hold material from usable stock. Third, the master schedule is changed daily in response to sales requests, causing component releases to move repeatedly.

Analysis

The planning team maps the product structure and verifies quantities at each level. It discovers that a display assembly revision uses a different connector, but the planning BOM continues to explode the old connector for some orders. Cycle counts show that recorded on-hand inventory overstates usable circuit boards because rejected boards remain in the system. A capacity review also shows that the connector supplier has a fixed weekly shipment schedule, so daily rescheduling cannot produce daily supply.

The team establishes an inventory-status policy, quarantines rejected stock in the ERP, and assigns engineering ownership for revision effectivity. It introduces a six-week master-schedule horizon: the first two weeks are frozen except for safety or regulatory issues, the next two require cross-functional approval, and the final two remain planning periods. It also replaces frequent small releases for connectors with a supplier-compatible weekly lot, while retaining lot-for-lot planning for expensive display assemblies.

Outcome

After implementation, planned-order changes fall substantially, emergency freight declines, and shortages become visible earlier. Average connector inventory increases modestly because of the weekly lot, but total relevant cost decreases because expediting and production interruptions fall. The organization does not claim that MRP solved every problem: supplier capacity and product design remain constraints. However, the revised process aligns data governance, scheduling policy, lot sizing, and supplier capability.

Learning points

1. MRP output is only as reliable as product, inventory, and calendar data.
2. Time fences convert uncontrolled schedule changes into governed decisions.
3. Lot sizing must reflect supplier and operational realities, not only theoretical holding cost.
4. Capacity and quality status must be integrated with material planning.
5. Stability and responsiveness are complementary when supported by explicit rules.

10. Implementation and managerial best practices

A robust requirements-planning process should include the following practices:

• Assign accountable owners for BOMs, item masters, lead times, calendars, and inventory accuracy.
• Measure inventory-record accuracy by financially and operationally important item classes.
• Separate gross requirements, scheduled receipts, planned receipts, and firm orders in reports.
• Use exception-based planning rather than asking planners to inspect every item equally.
• Review lead times using actual performance and distinguish quoted, planned, and observed lead times.
• Establish frozen, slushy, and liquid planning zones.
• Segment items by value, criticality, uncertainty, shelf life, and replenishment method.
• Link MRP, DRP, CRP, supplier collaboration, and financial planning through a common operating rhythm.
• Monitor shortage, schedule adherence, expedite frequency, inventory turns, obsolete inventory, supplier confirmation, and plan-change measures.
• Validate automated recommendations before release, especially where regulated products, safety-critical components, or contractual commitments are involved.

Ethically and legally, organizations must preserve traceability for regulated materials, prevent unauthorized changes, protect supplier and customer data, and avoid using algorithmic recommendations as a substitute for accountable decisions. In medical, aerospace, food, and other controlled industries, lot traceability, revision control, shelf-life management, and documented approvals are not optional planning conveniences.

Chapter Summary

Dependent demand is derived from the planned or actual requirements of a parent item, making it appropriate for calculation rather than independent forecasting. MRP converts a master production schedule into time-phased component and material plans through BOM explosion, inventory netting, lead-time offsetting, and lot sizing. Inventory status records provide the data foundation, while scheduled receipts and planned receipts distinguish existing commitments from system-generated recommendations.

Lot-for-lot, fixed order quantity, period-order quantity, EOQ-based policies, and dynamic lot-sizing methods balance ordering, setup, holding, capacity, and service considerations differently. MRP nervousness results when small changes produce disproportionate schedule disruption; time fences, stable master schedules, accurate data, and controlled exception management reduce it.

DRP extends similar logic to distribution networks, ERP integrates planning with enterprise transactions, and capacity requirements planning tests whether material plans are operationally feasible. MRP and lean or JIT systems can coexist in a hybrid design: MRP coordinates complex and long-lead requirements, while pull systems control stable repetitive flows. Effective implementation depends less on software alone than on data governance, cross-functional discipline, realistic lead times, and clear managerial accountability.

Key Terms

Dependent demand: Demand calculated from the requirements of a higher-level item.

Independent demand: Demand originating from customers, forecasts, or other external sources.

Material requirements planning (MRP): Time-phased logic for planning materials and component orders.

Bill of materials (BOM): Structured list of components and quantities required to make a parent item.

Multilevel BOM: Product structure showing several levels of parent-child relationships.

BOM explosion: Translation of parent requirements into component requirements.

Inventory status record: Item-level record of inventory, requirements, receipts, lead times, and planning parameters.

Gross requirement: Total demand before available supply is deducted.

Net requirement: Demand remaining after applicable inventory and receipts are considered.

Scheduled receipt: Supply from an existing open order expected at a specified time.

Planned receipt: Supply recommendation generated by MRP.

Planned order release: Date on which a planned order should be placed or production launched.

Time phasing: Assignment of requirements and supply to specific planning periods.

Lead-time offsetting: Moving a required receipt backward by the applicable lead time.

Lot sizing: Rule used to determine the quantity of an order or production batch.

MRP nervousness: Excessive changes to planned orders caused by small planning-data changes.

Distribution requirements planning (DRP): Time-phased planning of replenishment across distribution locations.

Enterprise resource planning (ERP): Integrated system linking planning and transactions across business functions.

Capacity requirements planning (CRP): Analysis of work-center loads created by planned orders.

Kanban: Pull-based replenishment signal used to regulate flow between processes.

Review Questions

Short Answer Questions

1. What distinguishes dependent demand from independent demand?
2. What information is normally contained in an inventory status record?
3. Why is a planned order release earlier than its planned receipt?
4. What is MRP nervousness, and why is it costly?
5. How does DRP complement MRP?

Long Answer Questions

1. Explain the complete sequence from a master production schedule to planned component-order releases.
2. Compare lot-for-lot, fixed order quantity, period-order quantity, and EOQ-based planning.
3. Discuss how BOM governance and inventory-record accuracy affect MRP performance.
4. Explain why a material-feasible MRP plan may still be capacity-infeasible.
5. Evaluate how MRP and lean/JIT systems can be combined in a hybrid operating model.

Analytical / Application Questions

1. A component has 120 units available. Requirements are 50 units in week 1, 90 in week 2, and 40 in week 3. A scheduled receipt of 30 arrives in week 2. Using lot-for-lot and no safety stock, calculate the planned receipt and, with a one-week lead time, the planned release.
2. A company’s daily schedule changes repeatedly, although suppliers ship weekly and work centers require long setups. Diagnose the sources of nervousness and recommend a governance design involving time fences, lot sizing, and supplier coordination.
3. A distribution center’s DRP plan creates a large production peak at the plant. Explain how the organization should use MRP, CRP, inventory policy, and cross-functional decision-making to evaluate and revise the plan.

Multiple Choice Questions with Answers

Question 1

Which situation best illustrates dependent demand?

A. Customer demand for replacement bicycles

B. Forecast demand for winter jackets

C. Demand for tires generated by a scheduled bicycle production plan

D. Demand for emergency medical services

Correct Answer: C. Demand for tires generated by a scheduled bicycle production plan

Question 2

A parent item requires 3 units of component X. A planned production order is for 400 parent units. Ignoring scrap and inventory, what is the gross requirement for X?

A. 133 units

B. 397 units

C. 403 units

D. 1,200 units

Correct Answer: D. 1,200 units

Question 3

Which record represents supply already associated with an open order?

A. Gross requirement

B. Scheduled receipt

C. Safety stock

D. Planned order release

Correct Answer: B. Scheduled receipt

Question 4

If a component is required in week 8 and has a two-week lead time, when should its planned order generally be released?

A. Week 6

B. Week 7

C. Week 8

D. Week 10

Correct Answer: A. Week 6

Question 5

Under a lot-for-lot policy, the planned receipt quantity is generally equal to:

A. The economic order quantity in every period

B. The fixed supplier minimum regardless of demand

C. The net requirement in the period

D. The total annual demand

Correct Answer: C. The net requirement in the period

Question 6

Using Q* = √(2DS/H), which change would increase the EOQ, all else equal?

A. A decrease in annual demand

B. A decrease in ordering cost

C. An increase in annual holding cost

D. An increase in annual demand

Correct Answer: D. An increase in annual demand

Question 7

What is the principal concern represented by MRP nervousness?

A. The system never generates any planned orders

B. Small input changes cause disruptive changes in many planned orders

C. All inventory is held as safety stock

D. Capacity is always greater than demand

Correct Answer: B. Small input changes cause disruptive changes in many planned orders

Question 8

What does capacity requirements planning add to material requirements planning?

A. A test of work-center load against available capacity

B. A replacement for the bill of materials

C. A method for forecasting customer demand independently

D. A guarantee that suppliers will deliver on time

Correct Answer: A. A test of work-center load against available capacity

Question 9

Which statement most accurately describes the relationship between DRP and MRP?

A. DRP plans distribution replenishment, while MRP plans materials and production

B. DRP replaces all BOM logic in manufacturing

C. MRP is used only for transportation routing

D. DRP and MRP are identical names for financial accounting

Correct Answer: A. DRP plans distribution replenishment, while MRP plans materials and production

Question 10

Which practice is most likely to reduce uncontrolled MRP nervousness?

A. Changing the master schedule whenever a minor forecast changes

B. Ignoring inventory accuracy until an annual audit

C. Using planning time fences and controlled change approvals

D. Increasing every lot size without regard to obsolescence

Correct Answer: C. Using planning time fences and controlled change approvals