Inventory Control & Material Requirements Planning

Chapter 13
Network, Service-Parts, and Omnichannel Inventory

Graduate Program in Operation Management (GPOM)
Inventory Control & Material Requirements Planning   •   Graduate

Network, Service-Parts, and Omnichannel Inventory

Introduction and Context

Inventory decisions become substantially more difficult when products, facilities, customers, repair centers, and sales channels form a network rather than a single stocking point. A local warehouse may appear to have adequate stock while the system as a whole experiences shortages, duplicated safety stock, obsolete items, or costly emergency shipments. These problems are especially acute for service parts, where demand is intermittent but stockouts can stop production, violate service contracts, or endanger safety.

This chapter examines inventory as a coordinated network problem. It integrates multi-echelon inventory theory, risk pooling, centralization, distribution requirements planning (DRP), lateral transshipment, repairable spares, substitution, postponement, and omnichannel allocation. The central managerial question is not simply “How much should each location stock?” but rather: “Where should inventory be positioned, in what form, and under what allocation and replenishment rules?”

Learning Objectives

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

  1. Explain multi-echelon inventory and distinguish cycle, pipeline, and safety stock.
  2. Analyze risk pooling, centralization, and the conditions under which pooling creates value.
  3. Apply DRP logic to time-phased distribution networks.
  4. Evaluate transshipment, substitution, postponement, and repairable-spares policies.
  5. Model intermittent demand and service-level trade-offs.
  6. Design principles for omnichannel allocation and inventory visibility.
  7. Critically assess technology, governance, resilience, and ethical implications of network inventory decisions.

1. The Network View of Inventory

A supply network contains nodes and links. Nodes may include suppliers, plants, regional distribution centers (RDCs), forward stocking locations, retailers, repair depots, and customers. Links represent transportation, information, returns, and financial flows. Inventory can exist as raw material, work-in-process, finished goods, service parts, returned products, or repairable units.

A multi-echelon system has at least two inventory levels that serve the same downstream demand. For example, a national distribution center supplies regional warehouses, which supply customers. Inventory at an upstream echelon is not independent of inventory downstream: it can protect several markets, but it may have a longer response time to individual customers.

Important inventory categories are:

  • Cycle stock: inventory created by ordering or producing in batches.
  • Pipeline stock: inventory in transit or otherwise committed to a location but not yet available.
  • Safety stock: inventory held to protect against demand, lead-time, supply, or process uncertainty.
  • Anticipation stock: inventory built before predictable seasonal, promotional, or capacity-related events.
  • Decoupling stock: inventory that separates stages so that one stage can continue despite disruption at another.
  • Strategic or critical stock: inventory held because shortage consequences are unusually severe.

Inventory positioning has three dimensions: location, quantity, and form. Postponement adds a fourth consideration: the degree of product completion. A generic module may serve many final products, whereas a fully configured unit may serve only one demand class.

Echelon versus local inventory

Local inventory is physically held at a specific node. Echelon inventory is the inventory at a node plus all inventory downstream of that node, depending on the chosen echelon definition. Echelon measures are useful because upstream stock often protects downstream demand. However, echelon stock should not be added mechanically across locations; double counting is a common analytical error.

A useful system-wide objective is:

Minimize C = ∑ᵢ hᵢ Iᵢ + ∑ᵢ kᵢ Oᵢ + ∑ᵢ pᵢ Bᵢ + ∑ᵢ cᵢ Tᵢ

where Ii is average inventory at node i, Oi is order frequency or number of replenishment orders, Bi is shortage exposure, and Ti is transportation or transfer activity. The parameters h, k, p, and c represent holding, ordering, shortage, and movement costs. This is a conceptual objective: practical models may include capacity, service, carbon, risk, and budget constraints.

2. Risk Pooling and Centralization

Risk pooling occurs when uncertain demands are aggregated before inventory is committed to a specific market. If demands are not perfectly positively correlated, aggregate variability grows more slowly than aggregate mean demand. This permits lower total safety stock for a specified aggregate service level.

For independent demands with standard deviations σ1, σ2, …, σn, aggregate standard deviation is:

σA = √(σ₁² + σ₂² + … + σₙ²)

For correlated demands:

σA = √(∑ᵢ σᵢ² + 2∑ᵢ<ⱼ ρᵢⱼσᵢσⱼ)

Here ρij is the correlation between demands at locations i and j. The formula assumes that the demand measures refer to the same time period and that standard deviations are compatible units. Positive correlation reduces the benefit of pooling; negative correlation increases it.

Under a normal-demand approximation, safety stock for a cycle-service target is:

SS = zσL

where σL is the standard deviation of demand during replenishment lead time and z is the standard-normal quantile associated with the desired probability of no stockout during the cycle. This formula is appropriate when demand during lead time is approximately normal, the target is a cycle-service level, and replenishment lead time and demand variability are appropriately represented.

Worked example: pooling two markets

Two markets each have weekly demand standard deviation of 20 units. Weekly demands are independent. If each market is stocked separately at a 95% cycle service level, use z ≈ 1.645:

Separate safety stock:

SStotal = 1.645(20) + 1.645(20) = 65.8 units.

If stock is pooled at one warehouse:

σA = √(20² + 20²) = 28.28 units,

so pooled safety stock is:

SSpooled = 1.645(28.28) ≈ 46.5 units.

The theoretical reduction is approximately 19.3 units, or 29.3%. This result does not prove that centralization is optimal. Transportation, response-time requirements, facility risk, capacity, customs, and customer-specific service commitments may outweigh the inventory saving.

Limits of pooling

Pooling is most valuable when demand is relatively independent, products are standardized, information is timely, and customers tolerate a common replenishment point. It is less valuable when demands are strongly correlated, lead times from the pool are long, products are highly customized, or local service requirements are strict. Centralization also concentrates operational risk: a fire, cyberattack, labor disruption, or transportation failure can affect many markets simultaneously.

A sound design therefore compares at least three alternatives: decentralized stocking, fully centralized stocking, and a hybrid network with regional or forward stock for critical items.

3. Multi-Echelon Inventory Control

In a multi-echelon system, local reorder points can produce excessive stock because each node independently protects itself from the same uncertainty. Multi-echelon inventory optimization coordinates these buffers and assigns protection to the echelon that can serve the widest demand set at acceptable response time.

A reorder point in a single-stage continuous-review model is commonly written as:

ROP = μL + zσL

where μL is expected demand during lead time and σL is its standard deviation. With constant demand rate d and deterministic lead time L, μL = dL. If demand and lead time are independent, demand variance during random lead time can be approximated by:

σL² = Lσd² + d²σLtime²

where σd is the standard deviation of demand per unit time and σLtime is the standard deviation of lead time. The expression assumes a stationary demand rate, independence between demand and lead time, and a suitable approximation for the demand process.

Multi-echelon policies often use installation-stock or echelon-stock targets. An upstream facility may hold less local safety stock if downstream facilities can reorder quickly, while a critical downstream location may receive a higher service priority. Exact optimization may require stochastic programming, simulation, or specialized multi-echelon methods because replenishment times, order priorities, batch sizes, and capacity constraints interact.

Service measures

Managers must distinguish:

  • Cycle service level: probability of no stockout during a replenishment cycle.
  • Fill rate: proportion of demand units supplied immediately from stock.
  • Ready rate: proportion of time an item is available when requested.
  • Order-line fill rate: proportion of order lines fulfilled completely.

These measures are not interchangeable. A 95% cycle service level does not necessarily mean that 95% of annual demand units are filled, particularly when demand size varies.

4. Distribution Requirements Planning

Distribution Requirements Planning translates a master schedule or demand forecast into time-phased replenishment plans for distribution facilities. DRP is the distribution counterpart of material requirements planning (MRP). It uses gross requirements, scheduled receipts, projected available balance, safety stock, planned receipts, and planned order releases.

For period t, a basic projected balance is:

PABt = PABt−1 + SRt + PORt − GRt

where PABt is projected available balance, SRt is scheduled receipt, PORt is planned order receipt, and GRt is gross requirement. A planned receipt is triggered when projected stock would fall below the target or safety stock. The planned release is offset backward by the replenishment lead time.

Illustrative DRP schedule

Assume a regional warehouse begins with 80 units, maintains safety stock of 20 units, receives a scheduled shipment of 40 units in week 2, and faces gross requirements of 30, 50, 40, and 60 units in weeks 1–4. Lot-for-lot replenishment is used, and the source lead time is one week.

WeekGross requirementScheduled receiptPlanned receiptProjected balance
0———80
1300050
250403070
3400030
46005020

The week-2 planned receipt of 30 maintains the target after demand, while the week-4 receipt of 50 prevents the balance from falling below 20. With a one-week lead time, the associated releases occur in weeks 1 and 3. In practice, DRP must also consider transportation calendars, minimum shipment quantities, truck capacity, order multiples, substitutions, and inventory already in transit.

DRP is not merely a spreadsheet calculation. Its quality depends on forecast governance, accurate inventory records, realistic lead times, and disciplined exception management. A system that produces precise plans from inaccurate data produces precisely wrong decisions.

5. Transshipment and Lateral Rebalancing

A lateral transshipment moves inventory between locations at the same echelon, such as one regional warehouse supplying another. It differs from vertical replenishment, which moves inventory from a supplier or central warehouse to a downstream node.

Transshipment is attractive when one location has excess stock and another faces a shortage, especially when replenishment lead time is long and the item is expensive or critical. A decision should compare:

  1. the cost and time of transshipment;
  2. the probability and consequence of shortage at the receiving location;
  3. the opportunity cost of removing stock from the supplying location;
  4. the possibility of future demand at both locations; and
  5. transportation, handling, quality, and traceability requirements.

A simple priority rule is to transship when the avoided shortage cost exceeds incremental transfer cost plus the expected shortage cost created at the supplying location. Because the opportunity cost is uncertain, organizations commonly use thresholds: transfer only when the donor’s projected service level remains above a minimum and the recipient’s shortage risk is high.

Transshipment can be proactive, based on forecasts, or reactive, based on actual shortages. It is most effective when inventory visibility is near real time, item identification is reliable, and ownership and financial settlement rules are clear.

6. Service-Parts and Intermittent Demand

Service parts differ from ordinary finished goods in several ways: demand may be rare, failure timing is uncertain, customers may require rapid response, and the consequence of nonavailability may be far larger than the part’s purchase price. A low-volume part is not necessarily unimportant.

Intermittent demand

Intermittent demand contains many zero-demand periods and occasional nonzero demands. Standard moving averages and normal safety-stock formulas can be misleading because the distribution is often skewed and lumpy. Forecasting should separate:

  • occurrence: whether demand occurs in a period; and
  • size: how many units are demanded when it occurs.

Croston-type methods estimate these components separately. More advanced approaches include the Syntetos–Boylan adjustment, bootstrapping, Bayesian models, and intermittent-demand models based on failure processes. No method is universally superior; evaluation should reflect the decision objective, lead time, service metric, and cost of overage versus shortage.

For repairable parts, demand is linked to failures and the repair loop. A simplified stock-flow relationship is:

N = O + R + T

where N is the total population required in the support system, O is operational stock available for use, R is units in repair, and T is units in transit or otherwise unavailable. The identity is a stock-flow accounting relationship, not a complete optimization formula. Repair yield, turnaround time, cannibalization, condemnations, and fleet growth must be modeled separately.

If a fleet contains F assets, each experiences an average failure rate λ failures per unit time, and the average repair turnaround is τ, expected units in repair under stable conditions are approximately:

E[R] = Fλτ

This is a Little’s Law relationship, L = λW, and requires a reasonably stable system. For example, 1,000 assets with failure rate 0.02 per month and repair turnaround of 1.5 months generate approximately 30 units in repair. This does not mean 30 additional serviceable spares are sufficient: demand variability and required service level still require protection stock.

Criticality and segmentation

Service parts should be segmented by failure consequence, demand pattern, repairability, value, and lead time. A useful policy matrix distinguishes:

SegmentTypical policy
High criticality, intermittent demandForward stock, high service target, pooling where possible
Low criticality, predictable demandStandard reorder or periodic review
Repairable, high valueClosed-loop tracking, repair capacity, priority returns
Obsolete or very slow movingCannibalization, approved substitution, controlled disposal
Safety- or regulatory-criticalTraceability, approved sources, conservative buffers

7. Substitution, Commonality, and Postponement

Substitution allows one item to satisfy demand for another. It may be exact, functional, temporary, or hierarchical. Substitution can reduce stock variety and improve availability, but it may create compatibility, warranty, safety, configuration, or customer-acceptance risks.

A substitution policy should specify:

  • which item can replace which item;
  • whether substitution is one-way or reciprocal;
  • technical and regulatory approval requirements;
  • price and cost allocation;
  • inventory ownership; and
  • how demand and forecast history are recorded.

Commonality creates risk-pooling benefits by allowing a component to serve multiple end products. However, common components may become single points of failure. Design-for-commonality should therefore be balanced against supply risk, qualification costs, and the operational impact of a component shortage.

Postponement delays final differentiation until demand information is clearer. Examples include generic packaging, late-stage configuration, regional labeling, and modular assembly. Postponement reduces finished-goods variety and obsolescence, but may increase lead time, processing cost, or requirements for flexible capacity.

The postponement decision is fundamentally a location-of-decoupling decision: inventory is held in a generic form upstream and customized closer to demand. It works best when product variety is high, demand is uncertain, customization can be performed quickly, and modules are genuinely reusable.

8. Omnichannel Inventory Allocation

Omnichannel operations integrate stores, e-commerce, marketplaces, mobile applications, and fulfillment centers. Customers expect consistent availability and may choose delivery, pickup, ship-from-store, or return-to-store options. Inventory is therefore both a physical resource and a promise communicated through digital channels.

The central allocation problem is to decide whether inventory should be:

  • reserved for store demand;
  • available for online orders;
  • used for click-and-collect;
  • allocated to high-priority customers or contracts;
  • held as safety stock; or
  • transferred to another node.

A simple allocation model maximizes expected contribution subject to inventory and capacity constraints:

Maximize ∑ⱼ (pⱼ − cⱼ)xⱼ − ∑ⱼ sⱼuⱼ

subject to:

∑ⱼ aⱼxⱼ ≤ I

Here xj is quantity allocated to channel or customer class j, pj is revenue, cj is variable fulfillment cost, uj is unmet demand, sj is its penalty or lost-contribution cost, aj is inventory usage per unit, and I is available inventory. This simplified model must be extended for promised delivery times, cancellations, substitution, labor capacity, store presentation requirements, and fairness constraints.

A common operational practice is available-to-promise (ATP) inventory. ATP should deduct allocated, reserved, damaged, quarantined, and safety-protected stock. If systems show inventory that is physically present but not actually sellable, customers receive false promises. Omnichannel success therefore depends on a single, continuously reconciled inventory ledger and robust order orchestration.

Store fulfillment trade-offs

Ship-from-store may reduce delivery distance and use store inventory, but it can increase picking labor, store congestion, split shipments, and cancellation risk. A store should not automatically fulfill every online order. Allocation rules should consider distance, labor capacity, local demand, markdown risk, inventory accuracy, and customer promise time.

Returns add another complexity. Returned items may be immediately resalable, require inspection, need refurbishment, or be unsellable. Reverse logistics decisions affect both inventory availability and financial reporting.

9. Integrated Applied Case: Orion Medical Equipment

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

Background

Orion supports 8,000 medical imaging systems across three countries. Its service network contains one central parts depot, four regional depots, and 35 field technicians. Some electronic modules are repairable; others are disposable. Hospitals require a four-hour response for critical failures. Demand for many parts is intermittent, while several common modules can be configured for multiple equipment models.

Problem

Orion’s regional depots independently set reorder points. Total inventory value increased by 24% over two years, yet emergency shipments and service failures also increased. The central depot had excess stock of common modules, while one region repeatedly lacked specialized boards. Inventory records were not synchronized with repair status, and the e-commerce portal promised parts that were physically present but already allocated.

Analysis

A network study first segmented parts by criticality, repairability, demand intermittence, and substitution options. It then estimated demand correlation among regions and measured repair turnaround. The study found that common modules had relatively low cross-region correlation and could be pooled centrally, but highly critical boards required regional forward stock because transportation lead time exceeded the hospital response promise.

The team also discovered that “on-hand” inventory included quarantined returns and units waiting for repair. A revised inventory ledger separated serviceable, allocated, defective, in-repair, and in-transit states. For repairables, the team used the relationship N = O + R + T to size the total support population and identify repair-loop bottlenecks.

Approach and solution

Orion implemented a hybrid policy:

  1. Common, interchangeable modules were pooled at the central depot with regional emergency allocations.
  2. Critical, non-substitutable boards remained in forward stocking locations.
  3. Approved substitution rules were embedded in the service system.
  4. Repair turnaround targets and priority queues were established.
  5. Lateral transshipment was permitted when donor service risk stayed below a defined threshold.
  6. DRP converted the field-service forecast into time-phased regional replenishment.
  7. The customer portal used ATP based on serviceable, unallocated inventory only.
  8. A monthly governance meeting reviewed fill rate, response time, obsolete inventory, repair yield, and emergency freight.

Outcome

After the pilot period, total inventory value fell while critical-part availability improved. Emergency freight declined because common modules were pooled and repair turnaround became more predictable. The improvement did not come from one formula; it resulted from segmentation, accurate state visibility, coordinated buffers, and explicit service priorities.

Learning points

The case illustrates four principles. First, centralization is selective rather than universal. Second, repair-loop inventory must be counted by status, not treated as a single available quantity. Third, substitution and commonality create value only when technical governance is strong. Fourth, omnichannel availability is a promise-management problem as much as a physical inventory problem.

10. Technology, Governance, and Contemporary Developments

Modern network inventory uses enterprise resource planning, warehouse-management systems, transport-management systems, RFID, IoT condition monitoring, digital twins, optimization engines, and machine-learning forecasts. AI can improve demand classification, failure prediction, anomaly detection, and allocation recommendations. Nevertheless, AI does not remove the need for causal reasoning. A model trained on historical stockouts may learn that low observed demand means low true demand, when in fact sales were censored by unavailability.

Good governance requires:

  • clear ownership of item, location, and status data;
  • audit trails for substitutions and overrides;
  • explainable allocation priorities;
  • controls against systematic discrimination among customer groups;
  • cybersecurity for connected inventory systems;
  • human approval for safety-critical decisions; and
  • model monitoring for drift and forecast bias.

Environmental considerations include carbon from emergency air freight, energy use in facilities, packaging, obsolescence, repair versus replacement, and reverse logistics. A policy that minimizes financial holding cost may increase emissions or create unsafe disposal. Multi-objective network design should make these trade-offs explicit.

11. Limitations and Best Practices

Network models are sensitive to data quality and assumptions. Demand distributions may change, correlations may rise during disruptions, lead times may be capacity-dependent, and service consequences may be nonlinear. Normal approximations are often unsuitable for rare-event or highly lumpy demand. Optimization models can also give false confidence if constraints omit labor, customs, qualification, or customer behavior.

Best practices include:

  1. Define service measures before setting inventory targets.
  2. Segment items and customers rather than applying one policy universally.
  3. Separate physical location from inventory status and ownership.
  4. Measure demand correlation and lead-time variability empirically.
  5. Use hybrid centralization for common items and forward stock for critical items.
  6. Treat repair, returns, and substitutions as designed processes.
  7. Reconcile ATP continuously with real operational states.
  8. Use transshipment thresholds that include donor opportunity cost.
  9. Stress-test networks against correlated disruption.
  10. Validate AI and optimization recommendations through simulation, pilots, and managerial review.

Chapter Summary

Network inventory management coordinates stock across multiple echelons, channels, and product states. Risk pooling can reduce safety stock when demands are not perfectly correlated, but centralization may increase response time and concentrate disruption risk. Multi-echelon policies allocate protection where it serves the greatest demand while respecting service promises. DRP converts time-phased downstream requirements into planned receipts and releases, whereas transshipment rebalances stock laterally between locations.

Service-parts management requires attention to criticality, intermittent demand, repair loops, substitution, and failure consequences. Repairable inventory must distinguish operational, in-repair, and in-transit units. Substitution, commonality, and postponement reduce variety and improve flexibility when technical and governance conditions are satisfied. Omnichannel systems require accurate ATP, coordinated channel allocation, and explicit consideration of store capacity, delivery promises, and returns. Technology and AI can strengthen visibility and prediction, but they must be governed through data quality, explainability, cybersecurity, and human accountability.

Key Terms

Multi-echelon inventory: Inventory positioned at two or more connected supply-chain levels.

Risk pooling: Aggregating uncertain demand before inventory is committed to individual markets.

Echelon stock: Inventory viewed from an upstream level together with downstream inventory it supports.

Cycle stock: Inventory resulting from replenishment or production lot sizes.

Pipeline stock: Inventory currently in transit or otherwise committed but unavailable.

Safety stock: Inventory held to protect against uncertainty.

Cycle service level: Probability of no stockout during a replenishment cycle.

Fill rate: Proportion of demand supplied immediately from available stock.

Distribution Requirements Planning: Time-phased planning of replenishment for distribution facilities.

Lateral transshipment: Movement of inventory between locations at the same echelon.

Service part: A component held to support maintenance or repair of an operating asset.

Intermittent demand: Demand containing frequent zero periods and occasional nonzero events.

Repairable spare: A part that can be restored to service after failure.

Substitution: Use of an approved alternative item to satisfy demand.

Commonality: Design or inventory sharing in which one component serves multiple products.

Postponement: Delaying final product differentiation until demand information is clearer.

Available-to-promise: Inventory legitimately available for a new customer commitment.

Omnichannel fulfillment: Coordinated fulfillment across integrated sales and service channels.

Echelon optimization: Coordinated inventory decisions across connected supply-chain levels.

Inventory status: Operational condition of stock, such as serviceable, allocated, defective, or in repair.

Review Questions

Short Answer Questions

  1. What is the difference between local inventory and echelon inventory?
  2. Why does demand correlation affect the value of risk pooling?
  3. What information does a DRP record contain?
  4. Define lateral transshipment and give one reason to use it.
  5. Why is intermittent demand difficult to forecast with ordinary averages?

Long Answer Questions

  1. Explain the benefits and limitations of centralizing inventory in a multi-echelon network.
  2. Compare cycle service level, fill rate, and ready rate, and explain why confusing them can lead to poor decisions.
  3. Discuss how repairability changes service-parts inventory policy.
  4. Explain how substitution, commonality, and postponement influence inventory variety and risk.
  5. Analyze the organizational and data requirements for successful omnichannel inventory management.

Analytical / Application Questions

  1. Two independent markets each have demand standard deviation of 15 units per week. Using z = 1.645, calculate separate and pooled safety stock for a 95% cycle service target. State the assumptions behind your calculation.
  2. A regional warehouse has 100 units available, but 20 are allocated, 15 are quarantined, and 10 are in repair. What quantity should be considered physically present but unavailable for a normal ATP promise? Explain the distinction between on-hand and promiseable inventory.
  3. Design a hybrid inventory policy for a service-parts network containing high-criticality intermittent parts, low-criticality predictable parts, repairable modules, and approved substitutes. Justify the location, service target, and replenishment approach for each category.

Multiple Choice Questions with Answers

Question 1

Which condition generally increases the benefit of risk pooling?

A. Perfectly positively correlated regional demand

B. Independent or weakly correlated regional demand

C. Longer transportation lead time to the pool

D. Highly customized products with no substitution

Correct Answer: B. Independent or weakly correlated regional demand

Question 2

In the basic DRP balance equation, what does POR_t represent?

A. Projected order requirement

B. Planned order receipt

C. Physical operating reserve

D. Prior-period order release

Correct Answer: B. Planned order receipt

Question 3

A lateral transshipment is a movement of inventory:

A. From a supplier to a plant

B. From a plant to a central warehouse

C. Between locations at the same echelon

D. From a customer to a repair supplier

Correct Answer: C. Between locations at the same echelon

Question 4

Which measure is the proportion of demand units supplied immediately from stock?

A. Fill rate

B. Cycle service level

C. Lead-time variance

D. Inventory turnover

Correct Answer: A. Fill rate

Question 5

Why can ordinary normal-demand safety-stock methods be misleading for intermittent demand?

A. Intermittent demand has no lead time

B. It contains frequent zero periods and lumpy nonzero events

C. It is always perfectly predictable

D. It cannot be measured in units

Correct Answer: B. It contains frequent zero periods and lumpy nonzero events

Question 6

A fleet has 1,000 assets, a failure rate of 0.02 per month, and a repair turnaround of 1.5 months. Using E[R] = Fλτ, expected units in repair are:

A. 13.3 units

B. 20 units

C. 30 units

D. 750 units

Correct Answer: C. 30 units

Question 7

Which statement best describes postponement?

A. Completing all customization before demand is known

B. Delaying final differentiation until demand information improves

C. Eliminating all finished-goods inventory

D. Moving inventory only between regional warehouses

Correct Answer: B. Delaying final differentiation until demand information improves

Question 8

In omnichannel operations, ATP should generally exclude:

A. Serviceable and unallocated inventory

B. Inventory already allocated to another order

C. Inventory that has passed inspection

D. Inventory physically available and correctly recorded

Correct Answer: B. Inventory already allocated to another order

Question 9

For repairable parts, the relationship N = O + R + T includes which categories?

A. Orders, revenue, and taxes

B. Operational stock, repair stock, and transit stock

C. Obsolete stock, returns, and transfers only

D. Demand, forecast, and transportation cost

Correct Answer: B. Operational stock, repair stock, and transit stock

Question 10

Which is a major limitation of full inventory centralization?

A. It always eliminates transportation cost

B. It can increase response time and concentrate disruption risk

C. It prevents all risk pooling

D. It makes inventory visibility unnecessary

Correct Answer: B. It can increase response time and concentrate disruption risk

Inventory Control & Material Requirements Planning
Chapter 13 of 15