In most factories, work orders are released to the shop floor as fast as machines can accept them. The result is predictable: mountains of work-in-progress inventory, chaotic prioritisation, and chronic late deliveries — despite everyone working at full capacity.
Drum-Buffer-Rope (DBR), the TOC production scheduling methodology, turns this logic on its head. It coordinates the entire production system around a single governing resource — the constraint — and produces dramatically better flow without adding capacity.
The Three Elements
The Drum is the constraint — the resource that sets the pace of the entire system. In TOC, only the constraint's schedule matters. Everything else must synchronise with it. The drum beats; everything else follows.
The Buffer is time-based protection placed in front of the constraint. Its purpose is simple: ensure the constraint is never idle. Because variability exists everywhere in production, the buffer absorbs disruptions upstream so the constraint always has work to process.
The Rope is the work release mechanism. Raw material enters the production system only when the constraint is ready for it — not when upstream resources are available. This is the most counterintuitive element for managers trained on efficiency metrics: non-constraint resources will appear idle. They should be idle when the constraint cannot absorb more work.
The Results DBR Produces — and Why
Implementing DBR typically produces immediate WIP reduction — often 40-60% — which is experienced as a dramatic reduction in lead times. Customers get faster delivery. The constraint, no longer buried under excessive WIP, becomes visible and manageable.
On-time delivery improves sharply because the system is now scheduled to protect commitments, not to maximise utilisation. The buffer management system (green/yellow/red zones) provides early warning when something upstream is threatening a delivery — allowing corrective action before the constraint is starved.
The Step Most Organisations Skip
Subordination — Step 3 of the Five Focusing Steps — is the one that kills most DBR implementations before they start. It requires non-constraints to serve the constraint's needs, even when this means they run at less than full utilisation. This looks like inefficiency on local metrics. Supervisors are evaluated on machine utilisation. So they keep their machines busy. WIP builds. Lead times creep back. The constraint is buried again.
This is why measurement systems must change before or simultaneously with DBR implementation. If you measure and reward local efficiency, you will not sustain flow improvement regardless of what scheduling system you install.
S-DBR: The Most Common Real-World Version
In the majority of real production environments, the market is the actual constraint — there is more capacity than orders. In these cases, full constraint scheduling (DBR) is replaced by Simplified DBR (S-DBR), which uses a shipping buffer and tracks planned load rather than managing a constraint buffer. S-DBR is simpler to implement and appropriate for market-constrained environments, which covers 80-90% of manufacturing businesses.