DDMRP and TOC §

Concept: Vocabulary that names a phenomenon.

The demand-driven materials-planning method that carries TOC replenishment and Actively Synchronized Replenishment logic into MRP-dependent supply chains, with strategic decoupling points, dynamic stock buffers, and execution priority based on actual demand.

Also known as: Demand Driven Material Requirements Planning; Demand Driven MRP.

Demand Driven MRP (DDMRP) is what TOC practitioners meet when TOC replenishment vocabulary crosses into ERP and supply-chain software practice. It is not ordinary MRP with nicer screens, and it is not simply Replenishment Pull renamed for another market. It is a demand-driven planning method for complex material environments where product structures, component lead times, and open supply still have to be visible.

The comparison matters because the Supply Chain Logistics certification track asks candidates to compare the TOC distribution and Actively Synchronized Replenishment solution with DDMRP. The short answer is: DDMRP inherits much of the TOC replenishment argument, especially strategic buffer placement, actual-consumption pull, dynamic buffers, and visible priority. It departs from classic TOC by putting the decoupling-point design and net-flow equation at the center, rather than starting from the system constraint.

Context §

DDMRP belongs in environments where the simple distribution question, “what did this location consume?”, is not enough. A manufacturer may have deep bills of material, long purchased-part lead times, shared components, capacity limits, transfer orders, and customer orders that appear inside the planning horizon. The organization still needs the useful MRP functions: bill-of-material visibility, netting, open-supply visibility, and the connection between demand allocations and supply orders. But it can’t let a forecast-push system create nervousness through every level of the product structure.

That is the same conflict Smith and Ptak’s TOC Handbook chapter frames for Actively Synchronized Replenishment (ASR). MRP remains useful, but its traditional push logic creates too much of the wrong inventory, too little of the right inventory, and repeated expediting. Pull methods such as TOC and Lean reduce exposure to forecast error, but complex material networks still need planning visibility. DDMRP sits in that space.

For a TOC reader, the family resemblance is obvious. Distribute-to-Availability creates an availability promise through central buffers, consumption-driven replenishment, and buffer-status priority. Dynamic Buffer Management resizes stock-buffer targets from red and green behavior. DDMRP keeps those ideas, then adds a formal placement and planning model for raw materials, work-in-process, finished goods, and shared components.

What It Is §

DDMRP is a method for planning and executing material flow from actual demand through strategically placed stock buffers. The TOCICO Dictionary describes it through five components.

The strongest connection to TOC is the stock buffer. In classic TOC distribution, a stock buffer protects availability at a chosen stocking point. In DDMRP, stock buffers can sit at raw-material, work-in-process, intermediate, finished-goods, and distribution positions. The buffer is not placed everywhere. Strategic positioning decides where a buffer reduces cumulative lead time, absorbs variability, and simplifies planning enough to justify the inventory.

The second distinctive move is decoupled explosion. Under ordinary MRP, a change near the top of the bill of material can ripple requirements through many lower levels. In DDMRP, the explosion stops at a buffered component. That buffered part replenishes from its own buffer signal when it enters the rebuild zone. The result is a set of decoupling points that prevent every demand change from becoming a full-system nervousness event.

The third move is the net-flow or available-stock view. Smith and Ptak’s ASR language calculates available stock as on-hand inventory plus open supply minus demand allocations, including qualified spikes. DDMRP’s public vocabulary often calls the comparable signal net flow. Either way, the planning question is not merely “what is on the shelf?” It is “what protection remains after current stock, supply already coming, and qualified demand are all counted?”

How It Is Measured or Recognized §

A practitioner can recognize DDMRP by five operating signals.

Buffers are placed deliberately, not everywhere. A DDMRP design names the decoupling points. The positioning logic considers customer tolerance time, market lead-time expectations, demand and supply variability, product-structure flexibility, and the protection of operational areas. If every item simply receives a min-max level, the system has not made the DDMRP move.

Lead time is compressed by protection points. ASR’s term for the practical lead time is the longest unprotected leg in the bill of material. A buffered component can shorten the parent item’s effective lead time because the downstream order no longer waits for the full cumulative path. The visible question is which buffers actually shorten the path the market cares about.

The planning signal counts open supply and qualified demand. A buffer may look low on hand but safe because supply is already committed. Another may look acceptable on hand but be at risk because a qualified order spike is inside the relevant horizon. DDMRP asks for that full picture before creating or expediting supply.

Execution priority is visible. Purchase orders, manufacturing orders, transfer orders, and supplier follow-up are not ranked only by due date. Buffer color, percent penetration, stockout risk, projected stockout alerts, synchronization alerts, and lead-time alerts tell planners which order protects flow now. If planners still work every MRP message as if it has equal weight, the method hasn’t changed execution.

Buffers change from behavior. A DDMRP implementation expects buffer levels to move as demand and supply behavior change. Planned adjustments handle known events such as seasonality, ramp-up, or ramp-down. Dynamic adjustment handles the steady evidence of too much or too little protection. A frozen buffer target is a sign that the system has kept the vocabulary but lost the control loop.

Why It Matters §

DDMRP matters to TOC readers because it is the commercial descendant many supply-chain practitioners will encounter before they meet the TOC source vocabulary. A candidate may know DDMRP’s five components from software or APICS-style material, while a TOC practitioner knows replenishment pull, stock buffers, buffer penetration, dynamic buffer management, and ASR. The two vocabularies overlap enough to confuse the reader and differ enough that the distinctions matter.

The convergence is real. Both DDMRP and TOC replenishment reject forecast push as the daily execution signal. Both place protection strategically instead of everywhere. Both use buffer status to create priority. Both treat visible execution as a condition of flow, not an afterthought. Both aim to dampen the bullwhip effect and the nervousness created when every small demand change is exploded through the whole network.

The divergence is also real. TOC starts from the system constraint and asks how the whole system protects throughput. Classic Distribute-to-Availability starts with the central warehouse and downstream consumption, then uses Buffer Aggregation in Distribution and frequent replenishment to raise availability with less total inventory. DDMRP starts with decoupling points across the bill of material and supply network, then uses the net-flow position to plan and execute around those buffers. That makes it especially useful in complex material environments, but it can also shift attention away from the one constraint that limits the system’s goal.

The clean comparison is therefore not “TOC versus DDMRP.” It is closer to “which TOC-derived supply-chain problem is being solved?” If the problem is a distribution chain that needs an availability offer, DTA and replenishment pull are the simpler frame. If the problem is a complex manufacturer whose MRP system creates nervousness through shared components, long lead-time purchased parts, and deep product structures, DDMRP’s decoupling-point model may be the better operational language. If the organization has both problems, the practitioner has to connect the two without pretending they are identical.

For certification-track readers, the practical payoff is exam fluency. DDMRP is not outside TOC’s body of knowledge. The Dictionary includes it and points to ASR. But the comparison should preserve the terms: stock buffer is not generic inventory cushion; buffer status is not a due-date list; decoupling is not ordinary safety stock; and demand-driven planning is not the same thing as a better forecast.

Common Misunderstanding §

“DDMRP is just TOC replenishment with a new brand.” It isn’t. DDMRP uses much of the same logic, but it formalizes decoupling-point placement, buffer profiles, net-flow planning, and MRP-compatible execution in a way that classic distribution replenishment does not need.

“DDMRP replaces the constraint.” It doesn’t. A DDMRP buffer protects material flow; it does not by itself identify the system’s current constraint or decide where improvement work belongs. A TOC practitioner still has to ask which resource, market, supplier, policy, or cash condition limits the goal.

“If a part is important, buffer it.” That is not the positioning rule. Strategic buffers earn their place when they compress effective lead time, absorb meaningful variation, protect a critical operating area, or simplify a shared-component path. Buffering every part recreates excess inventory under demand-driven language.

“Net flow is the same as on-hand stock.” It isn’t. The useful planning signal counts on-hand inventory, open supply, and qualified demand allocations. That is why a part can be low on hand but not require a new order, or appear acceptable on hand while a known spike makes it urgent.

“Demand-driven means forecast-free.” It doesn’t. Forecasts and sales plans still matter for capacity, seasonality, product introductions, and planned adjustments. The change is that the daily supply signal is governed by actual demand and buffer status, not by forecast push alone.

“Software compliance is the implementation.” It isn’t. DDMRP software can calculate zones and signals, but the method still depends on correct positioning, credible data, disciplined execution, and measurements that don’t drag the organization back into local optimization.

Related Articles §

Sources §