--- slug: drum-buffer-rope type: pattern summary: "TOC's production method for make-to-order operations with an internal capacity constraint: schedule the constraint, protect it with a time buffer, release work only at its pace." created: 2026-05-21 updated: 2026-07-01 related: five-focusing-steps: relation: specializes note: "DBR is the production specialization of the Five Focusing Steps: the drum exploits the constraint, the rope subordinates release, the constraint buffer protects exploitation against upstream variability." constraint: relation: depends-on note: "DBR operates on a named internal capacity constraint; without one, the system is market-constrained and S-DBR applies instead." ccr: relation: depends-on note: "The drum schedules the constraint or, when the constraint is interior to a chain of nearly-balanced resources, the capacity-constrained resource that protects it; the CCR concept is what distinguishes the resource the drum addresses from any other busy machine." constraint-buffer: relation: contains note: "The constraint buffer is one of the three buffers DBR positions; it absorbs upstream variability so the constraint is not starved when Murphy strikes." shipping-buffer: relation: contains note: "The shipping buffer protects the customer-due-date commitment after the constraint has done its work; both DBR and S-DBR retain it." buffer-management: relation: complements note: "DBR is the planning side; Buffer Management is the execution-control side that reads buffer penetration to expedite at-risk work and resize buffers over time." s-dbr: relation: precedes note: "S-DBR is the simplification appropriate when market demand, not an internal resource, is the system constraint; the standalone entry names the boundary and the trade-offs of dropping the constraint buffer." vati-plant-analysis: relation: depends-on note: "The VATI classification of plant types determines how DBR is applied: V-plants exploit at divergence points, A-plants at convergence points, T-plants at both, I-plants at the single bottleneck." subordination: relation: produces note: "The rope is the mechanism through which subordination is enforced: non-constraint release is held to the constraint's pace rather than to each non-constraint's local capacity." exploitation-without-elevation: relation: implements note: "DBR is the production-floor implementation of the exploit-before-elevate rule: the drum, the buffers, and the rope are the operational moves that have to be in place before any elevation against the constraint is reasonable." throughput: relation: produces note: "DBR is calibrated against system throughput, not against each resource's local utilization; the planning logic refuses moves that would raise utilization at the cost of throughput." efficiency-trap: relation: corrupted-by note: "DBR is most often eroded by the surrounding measurement system reasserting itself: non-constraints driven toward 100 percent local utilization rebuild inventory queues that the rope was designed to prevent." improving-non-constraints: relation: prevents note: "The rope's release discipline and the constraint-output measurement frame together refuse the temptation to invest in non-constraint capacity that DBR's logic identifies as harmful." cost-world-thinking: relation: corrupted-by note: "Cost-world reporting reads non-constraint idle time as waste and the constraint's buffer as inventory excess; both readings argue against DBR as it is meant to operate." throughput-accounting: relation: complements note: "Throughput Accounting supplies the measurement frame DBR runs against: the planning logic moves T up while holding I and OE flat, and the accounting reading surfaces the move as preferable to capacity additions that would raise OE without raising T." --- # Drum-Buffer-Rope (DBR) [TOC Fundamentals (TOCFC)](learning-tracks.md#toc-fundamentals): [prev: Capacity-Constrained Resource (CCR)](ccr.md) -> Drum-Buffer-Rope (DBR) -> [next: Constraint Buffer](constraint-buffer.md) [Supply Chain & Operations (SCL Practitioner)](learning-tracks.md#scl-pom): [prev: Capacity-Constrained Resource (CCR)](ccr.md) -> Drum-Buffer-Rope (DBR) -> [next: Constraint Buffer](constraint-buffer.md) > **Pattern:** A named solution to a recurring problem. *TOC's production-planning and execution-control method for make-to-order operations whose system constraint is an internal capacity-limited resource: schedule the constraint (the drum), insulate it with time-based protection (the buffer), and release work upstream only at the rate the constraint can consume it (the rope).* *Also known as: synchronized production.* Drum-Buffer-Rope is the production-floor form of the [Five Focusing Steps](five-focusing-steps.md) when the system constraint is inside the plant. The drum is the constraint's schedule. The buffer is time protection before the constraint and before shipment. The rope is the release rule that prevents upstream work from entering faster than the constraint can use it. Goldratt and Cox made the mechanism memorable through Alex Rogo's NCX-10 and Herbie's boy-scout hike in *The Goal*; Srikanth's *TOC Handbook* Ch. 8 gives the implementation-grade specification. DBR answers one practical question: how can a plant protect throughput without flooding itself with work-in-process? ## Context DBR fits production environments with three properties: an internal resource is the binding [Constraint](constraint.md), variability can starve that resource, and dependency between resources lets upstream disruption reach downstream commitments. Make-to-order job shops, build-to-order assembly plants, and capital-intensive process operations often fit this case. In [VATI Plant-Type Analysis](vati-plant-analysis.md), V-plants, A-plants, T-plants, and I-plants carry DBR differently, but all need the same constraint-protection logic. The simpler [Simplified Drum-Buffer-Rope (S-DBR)](s-dbr.md) variant applies when the market, not an internal resource, is binding. The choice turns on [Constraint Type Identification](constraint-type-identification.md) at Step 1. Full DBR needs a named internal constraint or [Capacity-Constrained Resource](ccr.md), a [Constraint Buffer](constraint-buffer.md) ahead of it, a [Shipping Buffer](shipping-buffer.md) at the customer commitment, and sometimes an assembly buffer at convergence. The rope enforces [Subordination](subordination.md). [Buffer Management](buffer-management.md) reads the buffers during execution. [Exploitation Without Elevation](exploitation-without-elevation.md) supplies the rule: exploit and subordinate before adding capacity. The *TOCICO Dictionary* defines DBR as the TOC method for scheduling and managing operations when there is an internal resource constraint, with the drum as the constraint or CCR, the buffer as time protection, and the rope as the release-control mechanism. *TOC Handbook* Ch. 8 (Srikanth, "DBR, Buffer Management, and VATI Flow Classification") is the chapter-length operational specification; Schragenheim, Dettmer, and Patterson's *Supply Chain Management at Warp Speed* extends the treatment into the supply-chain interface. Srikanth and Umble's *Synchronous Manufacturing* is the predecessor textbook in which the V-A-T-I classification and the first detailed DBR worked examples appeared. ## Problem A plant has identified the constraint and made the obvious exploitation moves. The resource is staffed through breaks, quality inspection has moved upstream, and the queue has been re-sequenced against system output rather than batch convenience. Throughput rises, then two failures remain. On bad days, the constraint runs out of work because an upstream disruption blocked material from reaching it. On ordinary days, work-in-process keeps climbing because every non-constraint, measured on local efficiency, produces faster than the constraint can consume. The plant has found the constraint, but the rest of the plant keeps undoing the exploitation. DBR turns constraint exploitation into a plant-wide planning system. It schedules the constraint, protects it with time, and stops upstream release from exceeding the constraint's pace. It does not try to maintain an MRP-style detailed schedule at every resource; Srikanth's chapter is explicit that a nervous per-resource schedule usually costs more than its precision is worth. It also does not copy a kanban-style release-on-demand rule, because DBR starts from the fact that the plant is not balanced. It plans in detail at the drum, the gating operation, and the convergence points that need it. Everywhere else, the shop floor follows a simple priority rule. ## Forces - **The plant is unbalanced and will stay that way.** Capacity comes in finite increments, and protective capacity at non-constraints is necessary. Srikanth is explicit that the perfectly balanced plant is neither achievable nor desirable. - **Variability is unavoidable and will not average out.** Dependent operations propagate the bad half of the variability distribution and absorb the good half; the constraint cannot make up time it has lost. Without explicit time protection ahead of the drum, every upstream disruption costs system throughput one for one. - **Local efficiency at non-constraints damages flow.** A non-constraint driven to 100 percent utilization rebuilds inventory or finishes work the system does not yet need. The shop floor fills with material the rope was designed to keep out. - **The priority rule must survive a shift change.** Operators cannot maintain a constantly updated real-time schedule under disruption. The non-constraint rule has to be readable without a computer. - **Buffer size is a judgment call.** Srikanth's field rule is ballpark sizing, typically half of current production lead time, then adjustment through Buffer Management. Exact buffer sizing from disruption distributions stalls before go-live. - **The cost-world measurement frame argues against the pattern.** Idle non-constraints read as waste, time buffers read as excess inventory, and the rope reads as deliberate under-utilization. ## Solution DBR places three coordinated decisions in the plant. **The drum** is the detailed schedule at the constraint. It states what the constrained resource will produce, in what sequence, and in what batch sizes, against firm customer commitments and current load. It accounts for setup dependencies, such as a color-changeover line that runs light-to-dark before dark-to-light. The drum is the only detailed schedule in the plant. In a make-to-order operation, it covers the immediate horizon of firm orders; in a make-to-availability operation, it is set against finished-stock buffer levels. **The buffers** are time reserves where missing protection would cost throughput. The constraint buffer sits immediately ahead of the drum so the constraint does not starve. The shipping buffer sits at the customer-commitment point and protects the due date after the constraint has done its work. At convergence points, an assembly buffer may protect the join between non-constraint feed paths and the constraint's output. These buffers are not calculated to an optimum. Field practice starts around half of current production lead time and then resizes against Buffer Management's color readings over weeks. **The rope** ties material release to the drum. Material enters the plant exactly one time buffer before the constraint is scheduled to consume it: not earlier, even when release capacity is available; not later, even when the gating operation is busy. Non-constraints work FIFO unless Buffer Management promotes a red order, which moves to the head of every queue it encounters. Divergence and convergence points get additional priority lists from the drum; everywhere else, material availability is the instruction. The discipline is mostly refusal. Do not schedule non-constraints in detail. Do not size buffers from distributions the plant does not understand. Do not measure non-constraints on local efficiency. If the rope is holding release down, utilization at those resources will look bad in a cost-world report and correct in a throughput report. ## How It Plays Out **Goldratt and Cox's NCX-10, plus the boy-scouts hike.** *The Goal* teaches DBR through two stories. In the plant, Alex Rogo's team identifies the NCX-10 as the constraint and the heat-treat oven as a downstream constraint at certain product mixes. The team exploits each, sets a drum schedule against firm orders, places time buffers before the constraints and before shipping, and rope-controls release at the gate. Throughput rises, lead times shrink, and on-time delivery stabilizes. In the hike, Herbie is the slowest scout. Herbie's pace is the drum, spacing among the scouts is the buffer, and the rope prevents the column from stretching. The plant case makes the mechanism operational; the hike makes it visible. **A make-to-order job shop running V-plant flow.** A specialty-steel rolling mill identifies a heat-treat furnace as its CCR. The furnace has already been exploited: loads are sequenced to reduce setups, staffing covers shift changes, and quality inspection has moved upstream. DBR adds a drum schedule for the immediate two-week customer-load horizon, a 24-hour constraint buffer before the furnace, a 24-hour shipping buffer at dispatch, and a rope that releases raw material exactly 24 hours before the furnace's scheduled need. Output-to-plan had been below 60 percent before DBR. It rises into the high 80s within two months and the high 90s within a year, with no added capacity and less work-in-process. **An A-plant with feeder paths converging at assembly.** An aerospace-component assembly plant identifies its assembly cell as the constraint. The feeder paths vary widely in cycle time and reliability. DBR places the drum at the assembly cell, a constraint buffer before it, and an assembly buffer where the feeders meet. The rope ties release at each feeder gate to the drum schedule, offset by that feeder's expected lead time plus buffer. On-time delivery, measured against customer due dates, rises from below 70 percent to above 95 percent within four months. The case fits the *TOC Handbook* Ch. 8 family of A-plant examples. ## Consequences **Benefits:** - **Throughput rises without capital expenditure.** The gain comes from recovering constraint hours, not from adding capacity. Field-cited implementations recover 30 to 50 percent of pre-DBR throughput within months. - **Work-in-process drops.** The rope holds material out of the plant. The buffers are time, not inventory, and only the constraint runs to its full capacity. - **Lead times become shorter and more predictable.** Production lead time becomes process time plus planned buffers; the rope keeps actual lead time close to the planned figure. - **The planning surface is small.** The drum and gating operation carry the detailed schedule. FIFO with red-order promotion is enough elsewhere. - **The next constraint becomes visible.** Once the drum is exploited, Buffer Management's penetration pattern shows where the elevation question belongs. **Liabilities:** - **Subordination is hard to hold.** Non-constraints idled by the rope look bad against cost-world measures. Operators and supervisors often lobby for more material in the first six months, before Buffer Management has validated the design. - **Buffer sizing is iterative.** A reasonable starting buffer and weekly adjustment converge; a demand for a calculated buffer before go-live stalls. - **The drum needs a stable constraint.** If the constraint moves frequently, the drum and rope offsets must be rebuilt each time. The planning system loses the small surface that made it robust. - **The cost-world system keeps arguing against DBR.** Resource utilization at non-constraints falls, and [Cost-World Thinking](cost-world-thinking.md) reads the fall as inefficiency. [Throughput Accounting](throughput-accounting.md) supplies the corrective frame; without it, the [Efficiency Trap](efficiency-trap.md) returns. - **DBR is not S-DBR.** Full DBR on a market-constrained system is a category error. The constraint buffer protects nothing, the drum schedules a non-binding resource, and the rope is calibrated against the wrong point. The *TOCICO Dictionary* makes the distinction explicit; a misread constraint type often forces a rebuild six to twelve months later. - **V-plants are the hardest case.** Divergence points multiply control responsibilities. Operators at those points need priority lists the FIFO rule cannot supply alone; teams that skip the V-plant discipline find work piling up at the wrong outputs. DBR is most valuable where it is hardest to hold: a high-variability, high-dependency plant whose measurement system rewards the behaviors the rope prevents. The canonical cases, including the NCX-10 sequence in *The Goal*, the V-plant rolling-mill cases in Srikanth and Umble, and the A-plant aerospace-assembly cases in the *TOC Handbook*, held the discipline. The cautionary cases gave way to local efficiency when the cost-world reports arrived. ## Sources - Cox, *TOCICO Dictionary* (2nd ed., 2012), entries "drum-buffer-rope (DBR)," "drum," "rope," "constraint buffer," "shipping buffer," "buffer management," and "capacity-constrained resource", the certification-grade definitions this entry cross-checks against. The Dictionary is distributed through TOCICO membership rather than the trade book channel and doesn't carry an Open Library record. - Goldratt and Cox, [*The Goal*](https://openlibrary.org/works/OL2463051W) (1984; revised 1986, 1992), the originating treatment. The NCX-10 sequence and the boy-scouts hike together name the drum, the buffer, and the rope as a single coordinated mechanism; the field's anchoring worked example for DBR. - 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 and gives the first operational specification of DBR as a Step 2 / Step 3 mechanism rather than a stand-alone scheduling method. - Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 8 (Srikanth, "DBR, Buffer Management, and VATI Flow Classification"), the chapter-length operational specification this entry's solution and worked examples cross-check against. The chapter pairs DBR with Buffer Management and connects both to the V-A-T-I plant-type classification. - Schragenheim and Dettmer, [*Manufacturing at Warp Speed*](https://openlibrary.org/works/OL1967829W) (2000), the implementation-grade treatment of DBR with worked examples across plant types; the volume the chapter-level references in Srikanth's *TOC Handbook* chapter direct readers to for the operational detail. - Schragenheim, Dettmer, and Patterson, [*Supply Chain Management at Warp Speed*](https://openlibrary.org/works/OL25181754W) (2009), Chs. 1-4 on DBR in the supply-chain interface; the volume that articulates when full DBR's constraint buffer is necessary and when S-DBR's omission of it is appropriate. - Umble and Srikanth, [*Synchronous Manufacturing*](https://openlibrary.org/works/OL2934171W) (1989), the predecessor textbook in which the V-A-T-I plant classification was first published and the detailed DBR worked examples first developed; the volume from which the *TOC Handbook* chapter draws its plant-type cases. --- - [Next: Simplified Drum-Buffer-Rope (S-DBR)](s-dbr.md) - [Previous: The Four Concepts of Flow](four-concepts-flow.md)