---
slug: s-dbr
type: pattern
summary: "TOC's production method for make-to-order operations constrained by market demand: quote a reliable due date, protect it with one production buffer, release one buffer ahead."
created: 2026-05-21
updated: 2026-07-14
related:
  drum-buffer-rope:
    relation: specializes
    note: "S-DBR is the variant of DBR appropriate when market demand, not an internal resource, is the binding system constraint; it drops the constraint buffer, retains only the shipping buffer (renamed the production buffer), and replaces detailed CCR scheduling with planned-load monitoring."
  five-focusing-steps:
    relation: specializes
    note: "S-DBR is the production specialization of the Five Focusing Steps for the market-constrained case: identify the market as the constraint, exploit it by quoting reliable due dates and protecting them, subordinate by monitoring planned load on the CCR rather than scheduling it in detail."
  constraint-type-identification:
    relation: depends-on
    note: "Choosing S-DBR over DBR rests on identifying the constraint as the market and the CCR as a secondary interactive constraint rather than the primary one; an S-DBR implementation on a system whose constraint is internal mis-protects the flow."
  constraint:
    relation: depends-on
    note: "S-DBR is built on the position that the market is the strategic constraint in the vast majority of make-to-order operations; an internal CCR is treated as an interactive secondary constraint that the load-monitor watches but the planner does not schedule."
  ccr:
    relation: depends-on
    note: "S-DBR monitors planned load on the CCR rather than building a detailed drum schedule against it; the CCR concept is what distinguishes the resource the load-monitor watches from any other busy machine."
  shipping-buffer:
    relation: contains
    note: "In S-DBR the shipping buffer (renamed the production buffer in Schragenheim's later work) is the single time reserve covering the whole production interval from material release to order completion."
  buffer-management:
    relation: complements
    note: "S-DBR's planning side is paired with Buffer Management as its execution side: the production buffer's green / yellow / red zones drive priority decisions at every resource, including the CCR, which sequences against shipping-buffer status rather than against a drum schedule."
  mts-mta:
    relation: contrasts-with
    note: "S-DBR is the make-to-order variant; the make-to-availability (MTA) variant in Schragenheim's TOC Handbook Ch. 10 covers stock environments. The two are sibling solutions to different production-mode questions, not alternative answers to the same question."
  vati-plant-analysis:
    relation: depends-on
    note: "The plant topology shapes the planned-load placement and the production-buffer sizing; V-, A-, T-, and I-plants each carry S-DBR with their own emphases."
  subordination:
    relation: produces
    note: "The rope in S-DBR ties release to the production-buffer offset against the due date rather than to a CCR drum schedule; non-constraint resources subordinate to the customer commitment via material release, not to an interior schedule."
  throughput:
    relation: produces
    note: "S-DBR is calibrated against system throughput in the form of reliable on-time delivery against quoted dates; the planning logic refuses commitments that the planned load on the CCR cannot safely support."
  efficiency-trap:
    relation: corrupted-by
    note: "S-DBR is undone when the CCR's measurement frame reasserts utilization as the local goal: a CCR driven to 100 percent on local-efficiency grounds depletes the planned-load slack the planner relies on to quote safe dates."
  exploitation-without-elevation:
    relation: implements
    note: "S-DBR's load control on the CCR is the exploit-before-elevate move at the secondary constraint: the existing CCR is fully used at its current capacity, and elevation is considered only when the load reading repeatedly forecasts unsafe quotes."
---

# Simplified Drum-Buffer-Rope (S-DBR)

[TOC Fundamentals (TOCFC)](learning-tracks.md#toc-fundamentals): [prev: Shipping Buffer](shipping-buffer.md) -> Simplified Drum-Buffer-Rope (S-DBR) -> [next: Buffer Management](buffer-management.md)
[Supply Chain & Operations (SCL Practitioner)](learning-tracks.md#scl-pom): [prev: Shipping Buffer](shipping-buffer.md) -> Simplified Drum-Buffer-Rope (S-DBR) -> [next: Buffer Management](buffer-management.md)

> **Pattern:** A named solution to a recurring problem.

*TOC's production-planning method for make-to-order operations whose system constraint is market demand rather than an internal resource: quote a reliable due date based on the planned load on the capacity-constrained resource, protect that date with a single production buffer covering the whole shop interval, and release materials one production buffer ahead of the date.*

*Also known as: simplified DBR. The shipping buffer is renamed the production buffer in S-DBR's later formulation.*

Simplified Drum-Buffer-Rope (S-DBR) adapts [Drum-Buffer-Rope (DBR)](drum-buffer-rope.md) to make-to-order operations where the market, not an internal resource, is the strategic constraint. Schragenheim and Dettmer proposed it in *Manufacturing at Warp Speed* (2000) to avoid the upkeep of detailed schedules in common MRP/ERP environments. Schragenheim's *TOC Handbook* Ch. 9 (2010) is the field's main treatment of the transition, whose basic principles Goldratt later adopted. S-DBR is now the preferred make-to-order method except where sequence-dependent setups require a detailed drum.

## Context

S-DBR fits a make-to-order operation that could sell more with reliable delivery. An internal resource may still become capacity-constrained under heavy load, but market demand remains the binding strategic constraint. Flow must also be stable enough for one buffer to protect the whole production interval. Many job shops, build-to-order assembly plants, and contract manufacturers meet these conditions.

The choice between S-DBR and DBR follows the [Constraint Type Identification](constraint-type-identification.md) performed at Step 1 of the [Five Focusing Steps](five-focusing-steps.md). When a furnace, heat-treat oven, or single-source assembly cell is the binding constraint, traditional DBR protects its scheduled drum with a constraint buffer. When the market is the constraint and the internal capacity-constrained resource (CCR) is secondary, S-DBR omits that buffer and the detailed drum schedule.

Customer due dates replace the internal drum and set the pace. The [Capacity-Constrained Resource](ccr.md) is monitored rather than scheduled. The sole [Shipping Buffer](shipping-buffer.md), renamed the *production buffer*, covers the interval from material release to order completion. The rope ties release to the due date minus that buffer, enforcing [Subordination](subordination.md) through gating. [Buffer Management](buffer-management.md) reads buffer penetration and sets priority at every resource, including the CCR. [Exploitation Without Elevation](exploitation-without-elevation.md) still applies: planned-load monitoring uses the CCR's existing capacity before elevation is considered.

The *TOCICO Dictionary* defines S-DBR as managing operations against a market drum and a production buffer while monitoring planned load on the CCR. It identifies the production buffer as S-DBR's only buffer and planned load as its capacity-control measure. Schragenheim's chapter supplies the operational detail.

## Problem

A make-to-order plant may quote lead times that operations can't meet while maintaining detailed schedules that disruption invalidates within hours. Traditional DBR can deepen the problem when the busiest machine isn't the system constraint. A drum built around that machine misreads a market-constrained system, and its constraint buffer adds planned waiting without protecting the actual constraint. Product-mix changes then force the planner to maintain a CCR schedule the operation doesn't need.

S-DBR asks how to quote a safe due date, protect it with one time buffer, and keep the CCR from becoming the constraint without scheduling it in detail. A detailed drum changes too slowly when the product mix shifts. Unrestricted release is no better: uneven CCR load floods the shop on peak days and starves it on slack ones.

## Forces

- **The strategic constraint is the market.** Customers can switch suppliers when internal delays weaken commitments. The operation loses orders rather than settling into a stable internal-constraint equilibrium.
- **An interactive secondary constraint still has to be watched.** Most plants have a CCR such as heat-treat, paint, calibration, or certified assembly. Ignoring its load eventually produces unsafe due-date quotes. Monitoring that load is not the same as scheduling the resource.
- **A single production buffer covering the whole interval is simpler and safer than three buffers covering pieces of it.** A red shipping buffer competes with a red CCR buffer for the same resource's attention; one buffer per order produces one set of priorities. Operators don't have to choose between competing red signals.
- **Local efficiency at the CCR damages flow.** If the CCR is driven to full utilization on local-efficiency measures, the planned-load slack the planner uses to quote safe dates evaporates. The pattern works only if the CCR sequences against shipping-buffer status, not against its own throughput target.
- **Sequence-dependent setups are the named exception.** The *TOCICO Dictionary* and Schragenheim both direct operations with long color changeovers, hardware-tool changes, or regulated batch campaigns back to traditional DBR. Without these dependencies, the CCR can re-sequence orders by buffer priority. With them, forced re-sequencing loses more capacity than simplification saves.
- **The production buffer is iterative, not calculated.** The field practice is to start at roughly half of current production lead time, then resize against Buffer Management's color readings over weeks. Implementations that demand a calculated production buffer before going live stall; the ones that go live with a ballpark figure converge.

## Solution

S-DBR coordinates four decisions: the market drum, production buffer, planned load, and rope.

**The market drum** is the production-completion date promised to the customer. The planner doesn't build a detailed CCR sequence. Instead, the planner quotes a date protected by the production buffer. The product's standard market lead time is the floor because faster quotes seldom help sales and may signal that the plant lacks work. The market drum is therefore a quoting discipline, not a scheduling table. Every accepted order carries a date supported by the planned load and production buffer.

**The production buffer** is the single time reserve from material release to order completion. At start-up, practitioners size it at roughly half the current production lead time. Removing large batches and queue buildup is expected to cut waiting by about half. Buffer Management's color readings then guide resizing over several weeks. A job shop may settle between one and two weeks, a high-velocity assembly operation at several days, and a complex multi-component product at longer. The buffer is *not* the lead time shown to the customer. The customer sees the quoted date, which includes the planned-load horizon and transportation. Buffer Management reads only the production buffer's state.

**Planned-load monitoring** replaces the detailed CCR drum. The planner totals accepted orders' CCR work in hours and compares it with available capacity over the production-buffer horizon. If a new order fits, the planner quotes the standard lead time. If it doesn't, the quote moves out by the extra time forced by the planned load. The CCR sequences work by shipping-buffer status, with red-zone orders first, rather than following a published drum schedule. The same daily color reading governs every other resource.

**The rope** ties material release to the customer due date minus the production buffer. Material enters the plant exactly one production buffer before the quoted date. Spare capacity at the gate doesn't justify early release, and an idle gate doesn't justify delay. The rope follows the buffer offset, not a detailed CCR schedule. Downstream non-constraints use simple FIFO unless Buffer Management promotes a red order to the head of each queue.

S-DBR refuses three familiar moves. It doesn't schedule the CCR in detail because planned load supports safe quotes and buffer status supports sequencing. It doesn't calculate the starting buffer from disruption distributions; practitioners start at half the current lead time and adjust. It also rejects local-efficiency measures at the CCR. Any reading that favors CCR utilization over buffer-priority sequencing is [Cost-World Thinking](cost-world-thinking.md).

## How It Plays Out

**A make-to-order job shop after a failed DBR implementation.** A specialty fabricator ran traditional DBR for nine months around a robotic welding cell. Weekly product-mix shifts between automotive subassemblies and one-off prototypes kept breaking the drum schedule. Operators saw the constraint buffer as inventory, while on-time delivery stayed near 70 percent. The team switched to S-DBR with a nine-working-day production buffer, roughly half the old lead time, and planned-load monitoring on the welder. The rope released work nine days before the quoted date, and the welder sequenced by shipping-buffer color. On-time delivery reached the low 90s within eight weeks. After four months, color readings supported trimming the buffer to seven working days. The planned-load reading remained the operation's single capacity gauge.

**A contract electronics manufacturer with no clear internal constraint.** An electronics manufacturing services shop ran pick-and-place, reflow, hand assembly, and test. Hand assembly was busiest, but staffing and product-mix changes kept it from becoming a stable drum. The team treated the customer commitment as the constraint and monitored planned load on the less-flexible placement machines. One production buffer covered the whole shop interval. Quotes against the standard market lead time became reliable, and customers accepted more of the firmer commitments. The case follows the *TOC Handbook* Ch. 9 example of S-DBR in a system with an unstable internal constraint.

**A regulated-batch operation that S-DBR does not fit.** A pharmaceutical contract manufacturer tried S-DBR despite sequence-dependent cleaning between product campaigns. Within four months, it returned to traditional DBR. Reordering the formulation suite by shipping-buffer status cost more setup time than the resulting flow benefit. The team restored a sequence-aware CCR schedule and placed a constraint buffer ahead of the suite. This is the *TOCICO Dictionary*'s named exception: strong sequence dependencies require a detailed drum.

## Consequences

**Benefits:**

- **The planning surface is minimal.** One buffer per order, one running load total, and one rope offset can absorb product-mix shifts that would break a detailed CCR drum within hours.
- **Quoted lead times are reliable.** Planned load and the production buffer support each customer commitment, letting the operation quote and meet the standard market lead time.
- **Throughput can rise without capital expenditure.** Removing the detailed CCR schedule, constraint buffer, and assembly buffer typically cuts production lead time roughly in half at start-up. Buffer Management then improves priority decisions over the following months.
- **Work-in-process drops sharply.** The rope holds material outside the plant, and the time-based production buffer replaces inventory released for a forecast CCR schedule.
- **Buffer Management becomes the control discipline.** Every resource reads the same order-level color signal. Priority disputes become readings of buffer state rather than negotiations between supervisors.

**Liabilities:**

- **Sequence-dependent setups break the pattern.** When CCR setup depends on sequence, order-by-order buffer priority can cost more setup time than it saves in flow. Regulated campaigns, long color or chemistry changeovers, and large hardware-tool changes need traditional DBR's detailed drum.
- **Cost-world reporting argues against the pattern.** CCR utilization and finished-goods inventory may fall, while non-constraints sometimes sit idle by design. Local reports read these outcomes as efficiency losses. Without [Throughput Accounting](throughput-accounting.md), the measurement system drives the CCR toward 100 percent utilization and restores the [Efficiency Trap](efficiency-trap.md).
- **Planned-load drift is the hidden failure mode.** If the planner doesn't remove closed orders or treats the total as an estimate, quoted dates become unsafe. Durable implementations give planned load the same operational priority as buffer state.
- **The production buffer is iterative, not calculated.** Starting at half of current lead time is the field rule of thumb; the right size emerges from Buffer Management's color readings over weeks. Implementations that demand a calculated buffer stall before going live.
- **S-DBR is not DBR; the choice is structural.** Using S-DBR where a furnace, unique tool, or regulated certification step is the true constraint leaves that resource unprotected. The production buffer covers the wrong interval, and planned load watches the wrong resource. After six to twelve months of unstable performance, the operation will likely rebuild traditional DBR. The S-DBR choice must be revisited when evidence no longer supports the market-constraint assumption.
- **Practitioners disagree on the boundary.** Schragenheim's *TOC Handbook* Ch. 9 prefers S-DBR except where sequence-dependent setups demand DBR. Pirasteh and other practitioners set a wider boundary, favoring traditional DBR for moderate sequence dependencies or seasonally moving constraints. The choice turns on volatility, CCR setup structure, and evidence about the binding constraint.

The named successful cases maintain planned-load discipline. The cautionary cases ignore sequence-dependent setups or quietly rebuild detailed CCR schedules outside the planner's view.

## Sources

- Cox, *TOCICO Dictionary* (2nd ed., 2012), entries "simplified drum-buffer-rope (S-DBR)," "production buffer," "planned load," and "capacity-constrained resource", the certification-grade definitions this entry cross-checks against. The Dictionary names S-DBR's exception case (sequence-dependent setups) and the planned-load mechanism explicitly.
- Schragenheim and Dettmer, [*Manufacturing at Warp Speed*](https://openlibrary.org/works/OL1967829W) (2000), the volume in which S-DBR was first proposed as a simplification of DBR appropriate to common MRP/ERP environments. The book gives the original derivation of the single-shipping-buffer approach and the planned-load mechanism.
- Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 9 (Schragenheim, "From DBR to Simplified-DBR for Make-to-Order"), the chapter-length operational specification this entry's solution and worked examples cross-check against. The chapter develops the three viewpoints (Five Focusing Steps, minimum planning, flow) that motivate the transition from DBR to S-DBR and names the sequence-dependent-setup exception.
- Schragenheim, Dettmer, and Patterson, [*Supply Chain Management at Warp Speed*](https://openlibrary.org/works/OL25181754W) (2009), Chs. 1–4 on the production-supply-chain interface; the volume that situates S-DBR within the supply-chain solution and names the planned-load mechanism as the bridge to make-to-availability.
- Goldratt and Cox, [*The Goal*](https://openlibrary.org/works/OL2463051W) (1984; revised 1986, 1992), the originating treatment of DBR. The S-DBR chapter in the *TOC Handbook* explicitly traces its own derivation from *The Goal*'s NCX-10 and boy-scouts arguments, then names the points at which the field's later understanding diverged from the original formulation.
- Goldratt, [*What Is This Thing Called Theory of Constraints and How Should It Be Implemented?*](https://openlibrary.org/works/OL4186015W) (1990), formalizes the Five Focusing Steps that S-DBR's "the market is the constraint" position depends on.

---

- [Next: Buffer Management](buffer-management.md)
- [Previous: Drum-Buffer-Rope (DBR)](drum-buffer-rope.md)