起源故事 · 为什么是"时间"不是"库存"
Origin Story · Why "Time" Not "Stock"
传统工厂的本能是"多备点料更保险",结果车间堆满在制品、占满资金、藏满缺陷。Goldratt 把这个观念彻底改写:
缓冲不该用件数衡量,而该用时间 —— "约束提前多久就该收到料"。
于是诞生了缓冲管理(Buffer Management):把这段提前时间分成绿、黄、红三段,
料按计划到、停在绿区就不用管;落到黄区开始关注;掉进红区立刻催料。
它只盯约束这一个点,既保证瓶颈不饿,又不让库存失控 —— 这是 TOC 对"多即是好"最漂亮的一记反击。
The reflex in a traditional plant is "stock more, sleep better" — and the result is shop floors drowning in WIP, cash trapped, defects hidden.
Goldratt rewrote the rule: a buffer should not be measured in pieces, but in time — "how far ahead the constraint should receive its material."
From that idea grew buffer management: split that lead time into green, yellow, red bands. If material arrives on plan and sits in green, leave it alone.
Once it slips into yellow, pay attention. The moment it falls into red, expedite immediately.
It watches only the constraint — the bottleneck never starves, and inventory never explodes. It is TOC's cleanest counterpunch to the "more is better" instinct.
1 约束前的缓冲池 · 上游一抖,它来吸收 The buffer pool in front of the constraint · it absorbs every upstream wobble
绿区·安全左边上游忽快忽慢地往缓冲池注水,右边约束匀速从池里取料。只要水位别见底,约束就一直有活干 —— 缓冲就是把上游的抖动"吃掉",让约束感觉不到。 Upstream feeds the pool in bursts on the left; the constraint draws material at a steady rate on the right. As long as the level stays above zero, the constraint keeps working — the buffer swallows the upstream jitter so the drum never feels it.
2 缓冲水位 · 绿/黄/红三色区监控 Buffer penetration · green / yellow / red monitoring
这就是缓冲管理的仪表盘。水位停在绿区=供料充足别动它;滑到黄区=开始留意;掉进红区=立刻催料补货,否则约束马上挨饿。 This is the buffer-management dashboard. Stay in green — supply is healthy, leave it alone. Drop into yellow — start watching. Fall into red — expedite right now, or the constraint will starve.
3 现实里的缓冲 The buffer in the real world
时间缓冲护约束:缓冲存在的唯一目的是"约束永不挨饿"——它的成本,远低于约束停机的损失。
Time buffer protects the constraint: the buffer exists for one purpose — keep the constraint from starving. Its cost is far smaller than the cost of constraint downtime.
三色区管理:绿别动、黄关注、红催料。这套信号让现场不用盯报表,看颜色就知道该不该行动。
Three-zone management: leave green alone, watch yellow, expedite red. The floor doesn't need to read reports — the color tells them when to act.
动态调缓冲:长期总在绿区→缓冲太厚可削薄;老往红区跑→上游不稳,得加厚或治本。
Dynamic buffer sizing: if you live in green, the buffer is too thick — shave it. If you keep hitting red, upstream is unstable — thicken the buffer or fix the root cause.
约束利用率 100%:缓冲调对了,约束几乎不停机,系统产出锁定在它的满产能上。
100% constraint utilization: with the buffer tuned right, the constraint barely stops — and system throughput locks onto its full capacity.
一句话In One Line
缓冲是 DBR 里最容易被误解的一环:人们一听"缓冲"就想到"多备库存",方向恰恰反了。
它是时间盾,不是库存山 —— 目标是用最薄的盾,换约束不挨饿。
太薄,上游一抖约束就停,产出立刻掉;太厚,资金和交期全被拖垮。三色区就是那把尺:
长期在绿就削、频繁进红就加(或治理上游波动)。
调到甜区,约束利用率守在 100%,整个系统的产出也就被锁定在它的极限上。
The buffer is the most misread piece of DBR. People hear "buffer" and reach for "stock more" — exactly the wrong direction.
It is a time shield, not a stock mountain — the goal is the thinnest shield that still keeps the constraint fed.
Too thin and any upstream wobble starves the drum and throughput drops; too thick and cash and lead times get crushed. The three zones are the ruler:
if you live in green, shave it; if you keep hitting red, thicken it (or fix upstream variability).
Land in the sweet spot and constraint utilization holds at 100% — the system's throughput is locked at its true ceiling.
常见误用Common Mistakes
把缓冲理解成"多备库存"。它是时间缓冲,目标是约束不饿,不是越多越好。
Reading "buffer" as "more inventory". It's a time buffer. The goal is "constraint never starves" — not "as much stock as possible".
缓冲一刀切、从不调整。看三色区动态增减:常绿削薄、常红加厚或治本。
Setting buffer size once and never touching it. Resize dynamically using the zones — shave it when green dominates, thicken it (or fix upstream) when red keeps appearing.
到处都设缓冲。只在约束前设缓冲,非约束设缓冲只会增加 WIP。
Putting buffers everywhere. Buffer only in front of the constraint. Buffers at non-constraints simply add WIP.