Actively Synchronized Replenishment §

Pattern: A named solution to a recurring problem.

Place stock buffers at selected material and distribution points, replenish from actual demand, and use visible buffer priority so complex MRP-dependent supply chains protect flow without returning to forecast-push.

Also known as: ASR; Beyond MRP; demand-driven materials and replenishment.

Actively Synchronized Replenishment (ASR) is the TOC supply-chain method for environments where simple distribution pull is not enough. A retailer or finished-goods distributor can often ask, “what did this location consume?” and replenish from that signal. A complex manufacturer has a harder problem: deep bills of material, long purchased-part lead times, shared components, open supply, and customer orders inside the planning horizon all still matter.

ASR keeps the useful parts of MRP, especially bill-of-material visibility, netting, and the link between demand allocations and open supply. It changes the operating logic around them. Instead of letting a forecast-push system treat every MRP message as equally urgent, ASR places stock buffers where they compress lead time and protect flow, then makes replenishment and expediting priorities visible through buffer status.

Context §

ASR belongs between Replenishment Pull and DDMRP and TOC. Replenishment Pull explains the core TOC supply-chain rule: replace what was consumed and manage by buffer status. DDMRP is the later demand-driven planning vocabulary that many supply-chain practitioners now meet through software, APICS-adjacent training, and the Demand Driven Institute. ASR is the TOC-derived bridge that Smith and Ptak described in the Theory of Constraints Handbook: a way to make complex MRP-dependent material flow act like a pull system without discarding the planning visibility MRP still supplies.

The TOCICO Dictionary defines ASR as demand-driven planning and execution techniques for inventory positioning in material and distribution replenishment systems. Its short perspective is load-bearing: ASR integrates pull distribution with demand-driven material requirements planning. That makes it broader than finished-goods replenishment and narrower than a generic “supply-chain improvement” program.

The method fits plants and supply chains where long-lead purchased parts, shared components, subassemblies, and finished goods all have to be synchronized. If the product structure is shallow and replenishment is simple, classic TOC distribution may be enough. If the bill of material is deep and the organization still needs MRP’s visibility, ASR names the compromise that keeps the visibility and changes the priority system.

Problem §

Traditional MRP is useful and dangerous at the same time. It sees product structures, open supply, demand allocations, and the dates attached to each. That visibility is why complex manufacturers keep it. But the ordinary MRP operating logic is forecast-push: explode the plan through every level, issue messages, reschedule when the plan changes, and ask planners to work through the resulting noise.

The result is familiar to materials managers. Too much of the wrong material sits in the system, too little of the right material is available when needed, and expediting becomes the daily operating mode. A small demand change can ripple through the bill of material, creating nervousness in parts that were never the real risk. Planners spend attention on messages that don’t protect throughput while missing the few orders that do.

The harder problem is not whether MRP should exist. It is what governs action once MRP has exposed the data. If due date alone ranks the queue, a purchase order due tomorrow can outrank a later order that protects a red customer-facing buffer. If every forecast variation creates a full-system explosion, the chain rebuilds the push behavior TOC was meant to escape.

Forces §

Solution §

Use MRP for visibility, not for priority. Build the material system around strategically placed stock buffers, actual-demand replenishment, realistic ASR lead times, and visible execution alerts.

The Handbook gives ASR five operating components.

Choose strategic inventory positions. The first question is not how much inventory to hold. It is where inventory protects the system. ASR places stock buffers at selected purchased parts, subassemblies, finished goods, and distribution points when those positions shorten effective lead time, absorb meaningful supply or demand variation, protect a critical operating area, or simplify a shared-component path. Buffering every part recreates excess inventory under demand-driven language. Buffering none leaves the plant exposed to the same material shortages that made MRP feel necessary.

Group and size buffers through profiles. Parts with similar behavior are grouped into buffer profiles. Lead time, make-or-buy status, demand variability, supply variability, order multiples, minimum quantities, seasonality, and other traits shape the initial zone levels. The target is not a one-time min-max number. It is a starting protection level that can be read by color and refined from behavior.

Let buffers move. ASR buffers are dynamic. Planned adjustments handle known events such as seasonality, ramp-up, ramp-down, or capacity changes. Behavior-based changes handle the evidence that the buffer is too large, too small, or placed under new conditions. A frozen buffer target is a sign that the organization has kept the terminology but lost the control loop.

Generate supply from actual demand and available stock. ASR’s planning signal is available stock: on-hand inventory plus open supply minus demand allocations, including qualified spikes. That differs from on-hand stock alone. A part may look low on hand but be safe because supply is already committed; another may look acceptable on hand but be at risk because a qualified order spike is inside the ASR lead-time horizon. ASR also decouples the bill-of-material explosion at buffered components, so a parent change doesn’t automatically send nervousness through every lower level.

Make execution priority visible. Purchase orders, transfer orders, manufacturing orders, and supplier follow-up get ranked by buffer status and alerts, not merely by due date. Current inventory alerts show stocked-out or threatened parts. Projected stockout alerts show where expected consumption will outrun incoming supply. Material synchronization alerts show where demand and supply dates no longer line up. Lead-time alerts prompt follow-up on critical non-stocked components before they become shortages.

Do not turn ASR into colored MRP: ASR fails when a team adds buffer colors to an unchanged push system. The colors matter only if they govern replenishment, expediting, and supplier follow-up. If planners still work every MRP message in due-date order, the method hasn’t changed execution.

How It Plays Out §

A complex manufacturer with shared purchased parts. A plant builds several parent products from overlapping purchased components. Under ordinary MRP, a change in one parent order ripples through the shared lower levels and generates reschedule messages across the chain. ASR buffers the few components that compress the most cumulative lead time, stops the explosion at those buffers, and lets each buffered part replenish from its own available-stock signal. The planner stops chasing every message and works the parts whose buffer readings show real risk.

A DBR plant whose constraint waits on materials. A company schedules capacity through Drum-Buffer-Rope but still releases or delays work because purchased parts are late. The DBR implementation looks weak even though the capacity logic is sound, because material availability is governed by the old push system. ASR protects the selected material positions and gives purchasing, production control, and the constraint resource the same priority signal. The constraint doesn’t wait because a non-constraint part was invisible until release.

A supplier with several open purchase orders. A buyer has multiple POs at one supplier. One is due tomorrow but protects a green buffer. Another is due next week but protects a red buffer with demand allocated against it. Due-date priority tells the supplier to work the first order. ASR priority tells the supplier which order protects flow now and which one can wait.

Consequences §

Benefits.

Liabilities.

ASR’s test is practical. When demand shifts, a supplier slips, or a parent order changes, can the chain tell which buffered part is at risk, which open order protects it, and who must act first? If it can’t, the organization still has MRP data. It doesn’t yet have actively synchronized replenishment.

Related Articles §

Sources §