Drum-Buffer-Rope
Synchronize the entire production system to the constraint's pace using a drum to set the beat, a buffer to protect it, and a rope to control material release
Drum-Buffer-Rope is the scheduling and production control mechanism that operationalizes the subordination step of the Five Focusing Steps. The metaphor originates from Alex's boy scout hike, where his children propose two solutions to the problem of the troop spreading out: Sharon suggests a drummer to set the pace (like in a parade), and Dave suggests tying everyone together with a rope (like mountain climbers). The combined insight becomes the DBR method. The Drum is the constraint resource, which sets the pace for the entire system -- just as Herbie set the pace for the entire troop. The Buffer is a time buffer placed before the constraint to ensure it is never starved by upstream disruptions -- analogous to ensuring Herbie always has someone ready to walk behind him. The Rope is the mechanism that ties material release at the beginning of the process to the constraint's consumption rate -- analogous to tying a rope from the front of the line to Herbie so the front cannot walk faster than the constraint allows. Together, these three elements ensure the system produces at the maximum rate the constraint allows, with minimum work-in-process inventory and predictable lead times.
- The constraint sets the pace for the entire system -- it is the drum that everyone marches to
- Material should be released into the system only at the rate the constraint can process it -- the rope
- Time buffers before the constraint protect it from upstream variability -- the buffer
- Total work-in-process inventory is controlled by the rope length, not by individual resource speeds
- Non-constraint resources must have excess capacity to recover from disruptions and maintain the buffer
- Activating a resource is not the same as utilizing it -- activation without constraint synchronization just builds inventory
- Establish the Drum -- identify and schedule the constraintThe constraint resource becomes the master schedule for the entire system. Schedule the constraint based on market demand and its own capacity, ensuring it works on the highest-priority items first. The constraint's schedule determines when every other resource should work and on what.Pro tipIn Alex's plant, the drum was the processing schedule of the heat-treat oven and the NCX10 machine. Every other resource's schedule was derived from these two bottlenecks' schedules.WarningIf you schedule non-constraint resources independently of the drum, you will build inventory at the constraint and create confusion about priorities.
- Establish the Buffer -- protect the constraint with timePlace a time buffer before the constraint to absorb upstream variability. The buffer is not inventory for its own sake -- it is insurance that the constraint will always have work waiting when it finishes a batch. The buffer size should be based on the typical variability in upstream processing, not on a fixed inventory level.Pro tipThe buffer should be measured in time, not units. A two-day time buffer means that work scheduled for the constraint should arrive two days before the constraint needs it. This accounts for varying processing times across different parts.WarningToo large a buffer increases work-in-process and lead times. Too small a buffer risks starving the constraint. Monitor buffer consumption to calibrate: if the buffer is rarely touched, it is too large; if the constraint frequently waits for work, it is too small.
- Establish the Rope -- tie material release to constraint consumptionRelease raw materials into the system only at the rate the constraint consumes them, offset by the time buffer. If the constraint processes a batch every four hours and the time buffer is two days, material should be released roughly two days and four hours before the constraint needs it. This prevents the buildup of excess work-in-process inventory.Pro tipThe rope replaces the common practice of releasing materials based on forecasts or based on keeping upstream resources busy. By tying release to actual constraint consumption, you automatically control total work-in-process.WarningThe rope will cause non-constraint resources to have idle time. This is correct and expected. Resist pressure to release more material just to keep upstream resources busy -- that is the exact behavior that creates the inventory chaos the rope is designed to prevent.
- Monitor buffer status and adjustContinuously monitor the time buffer. If work arrives at the constraint well ahead of schedule, the buffer may be oversized. If work arrives just in time or late, the buffer is too small or upstream performance has problems that need attention. Use buffer penetration as an early warning system for production issues.Pro tipDivide the buffer into three zones (green, yellow, red). Green means work arrived early -- no action needed. Yellow means work is arriving on time -- monitor closely. Red means work is late or missing -- expedite immediately. This replaces the chaos of managing by hot lists with a structured early-warning system.WarningDo not use buffer management as an excuse to reintroduce universal expediting. The purpose is targeted intervention on specific orders that penetrate the red zone, not a return to the fire-fighting culture the rope was designed to eliminate.
After Herbie -- the slowest boy -- determined the entire troop's pace, Alex's children independently proposed the two key elements. Sharon suggested Herbie beat the drum to set the pace. Dave suggested tying everyone together with a rope to prevent gaps. Alex synthesized these ideas: only the front of the line needed to be connected to Herbie. If the front boy could not walk faster than Herbie, the line would stay together and the gaps (excess inventory) would disappear.
Before implementing DBR, the plant released materials based on forecasts and upstream resource availability. Work-in-process inventory was enormous, lead times were unpredictable, and everything was constantly expedited. After identifying the bottlenecks, the team began releasing materials only at the rate the bottlenecks could process them, with time buffers to protect against upstream disruptions.
After the boy scout hike where Alex discovered the impact of dependent events and statistical fluctuations, he discusses the problem with his children at the kitchen table. He asks them how they would prevent the hike line from spreading out. Sharon proposes a drummer to keep everyone marching in step, and specifically suggests that Herbie -- the slowest boy -- should beat the drum. Dave proposes tying everyone together with a rope so nobody can fall behind or surge ahead. Alex realizes the rope would control total inventory (the length of the line) with precision. He then synthesizes both ideas: you do not need everyone marching in exact step or tied together at every point. You just need to prevent the front of the line from walking faster than Herbie. The rope from Herbie to the front of the line -- combined with Herbie's drum setting the pace -- becomes the production control system for his plant.