biz-toc
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTheory of Constraints (TOC)
约束理论(TOC)
Overview
概述
TOC asserts that every system has at least one constraint (bottleneck) that limits total throughput. Improving non-bottleneck processes does NOT improve system output �� only improving the bottleneck does. The Five Focusing Steps provide a systematic method to find and manage constraints.
TOC认为,每个系统至少存在一个限制整体吞吐量的约束(瓶颈)。优化非瓶颈流程无法提升系统产出——只有优化瓶颈才能实现。五大聚焦步骤提供了一套系统化的方法来寻找并管理约束。
Framework
核心框架
IRON LAW: The System Is Only as Strong as Its Weakest Link
Improving a non-bottleneck process is a WASTE of resources — it produces
more work-in-progress that piles up at the bottleneck. Before optimizing
any process, verify it IS the bottleneck. If it's not, stop.铁律:系统的强度取决于其最薄弱的环节
优化非瓶颈流程是对资源的浪费——这会产生更多在制品,堆积在瓶颈环节。在优化任何流程之前,请先确认它确实是瓶颈。如果不是,请停止优化。The Five Focusing Steps
五大聚焦步骤
- IDENTIFY the constraint — Find the bottleneck (highest utilization, longest queue, most WIP accumulation)
- EXPLOIT the constraint — Maximize throughput at the bottleneck without adding resources (reduce downtime, eliminate waste at this step, ensure it never starves for input)
- SUBORDINATE everything else — Pace all other processes to the bottleneck's rhythm. Non-bottlenecks should NOT run at full capacity.
- ELEVATE the constraint — If exploitation isn't enough, invest to increase bottleneck capacity (add equipment, hire, outsource)
- REPEAT — After elevating, the constraint may shift to another process. Go back to Step 1.
- 识别约束——找出瓶颈(利用率最高、队列最长、在制品(WIP)堆积最多的环节)
- 挖尽约束——在不增加资源的前提下最大化瓶颈的吞吐量(减少停机时间、消除该环节的浪费、确保瓶颈不会因待处理任务不足而闲置)
- 迁就其他环节——让所有其他流程的节奏匹配瓶颈的节奏。非瓶颈环节不应满负荷运行。
- 提升约束——如果挖尽瓶颈仍不足以提升产出,则通过投资增加瓶颈的产能(添加设备、招聘人员、外包)
- 重复——提升瓶颈后,约束可能会转移到其他流程。回到步骤1重新开始。
Drum-Buffer-Rope (DBR) Scheduling
Drum-Buffer-Rope(DBR)调度
| Element | What It Is | Purpose |
|---|---|---|
| Drum | The bottleneck's pace | Sets the rhythm for the entire system |
| Buffer | Time buffer before the bottleneck | Ensures the bottleneck never starves for work |
| Rope | Signal to release work at the start | Controls WIP by tying input rate to bottleneck pace |
| 元素 | 定义 | 目的 |
|---|---|---|
| Drum | 瓶颈的生产节奏 | 设定整个系统的运转节奏 |
| Buffer | 瓶颈前的时间缓冲 | 确保瓶颈不会因待处理任务不足而闲置 |
| Rope | 启动环节的任务释放信号 | 通过将输入速率与瓶颈节奏绑定来控制在制品(WIP)数量 |
Throughput Accounting (TOC Financial Metrics)
吞吐量会计(TOC财务指标)
| Metric | Definition |
|---|---|
| Throughput (T) | Revenue - Truly Variable Costs (materials only) |
| Investment (I) | Money tied up in the system (inventory, equipment) |
| Operating Expense (OE) | All other costs to run the system |
| Net Profit | T - OE |
| ROI | (T - OE) / I |
| 指标 | 定义 |
|---|---|
| Throughput (T) 吞吐量 | 收入 - 真正可变成本(仅包含原材料成本) |
| Investment (I) 投资 | 系统中占用的资金(库存、设备等) |
| Operating Expense (OE) 运营费用 | 维持系统运行的所有其他成本 |
| 净利润 | T - OE |
| 投资回报率(ROI) | (T - OE) / I |
Output Format
输出格式
markdown
undefinedmarkdown
undefinedTOC Analysis: {System/Process}
TOC分析:{系统/流程}
System Map
系统流程图
{Process A} → {Process B} → {Process C (bottleneck)} → {Process D} → Output
{流程A} → {流程B} → {流程C(瓶颈)} → {流程D} → 产出
Constraint Identification
约束识别
- Bottleneck: {process step}
- Evidence: {utilization %, queue length, WIP accumulation}
- Current throughput: {units/period}
- 瓶颈:{流程环节}
- 依据:{利用率百分比, 队列长度, 在制品堆积情况}
- 当前吞吐量:{单位/周期}
Five Focusing Steps
五大聚焦步骤实施计划
| Step | Action | Expected Impact |
|---|---|---|
| 1. Identify | {bottleneck location} | — |
| 2. Exploit | {optimize without investment} | +X% throughput |
| 3. Subordinate | {pace other processes} | Reduce WIP by X% |
| 4. Elevate | {investment if needed} | +X% throughput |
| 5. Repeat | {new constraint location} | — |
| 步骤 | 行动 | 预期影响 |
|---|---|---|
| 1. 识别 | {瓶颈位置} | — |
| 2. 挖尽 | 无投资优化措施 | 吞吐量提升X% |
| 3. 迁就 | 其他流程节奏调整 | 在制品减少X% |
| 4. 提升 | (如需)投资措施 | 吞吐量提升X% |
| 5. 重复 | 新约束位置 | — |
DBR Implementation
DBR实施方案
- Drum: {bottleneck pace = X units/hour}
- Buffer: {X hours of WIP before bottleneck}
- Rope: {release new work every X minutes}
undefined- Drum:{瓶颈节奏 = X单位/小时}
- Buffer:{瓶颈前X小时的在制品量}
- Rope:{每X分钟释放一次新任务}
undefinedExamples
应用示例
Correct Application
正确应用
Scenario: TOC for a PCB assembly line (5 stations)
- Station throughput: Solder Paste (100/hr) → Pick & Place (80/hr) → Reflow Oven (50/hr) → Inspection (90/hr) → Packaging (120/hr)
- Bottleneck: Reflow Oven (50/hr) — lowest throughput, highest utilization
- Exploit: Reduce oven changeover time from 30 min to 10 min → effective capacity +15%
- Subordinate: Slow Pick & Place to 55/hr (don't overproduce WIP before oven)
- Elevate: If needed, add second reflow oven → double capacity
场景:PCB组装线的TOC应用(5个工位)
- 工位吞吐量:焊膏印刷(100块/小时)→ 贴装(80块/小时)→ 回流焊炉(50块/小时) → 检测(90块/小时)→ 包装(120块/小时)
- 瓶颈:回流焊炉(50块/小时)——吞吐量最低,利用率最高
- 挖尽优化:将炉体切换时间从30分钟缩短至10分钟 → 有效产能提升15%
- 迁就调整:将贴装工位的速度降至55块/小时(避免在回流焊炉前堆积过多在制品)
- 提升措施:如有需要,添加第二台回流焊炉 → 产能翻倍
Incorrect Application
错误应用
- Bought a faster Pick & Place machine (80→120/hr) → System throughput unchanged because Reflow Oven (50/hr) is still the bottleneck. Wasted investment. Violates Iron Law.
- 采购了更快的贴装设备(80→120块/小时)→ 系统吞吐量未发生变化,因为回流焊炉(50块/小时)仍是瓶颈。投资被浪费,违反了铁律。
Gotchas
注意事项
- Constraints can be non-physical: Market demand, policy, or management attention can be the real constraint. If the factory can produce 1000 but only sells 500, the market is the constraint.
- Moving bottleneck: After elevating one constraint, the bottleneck shifts. Teams often celebrate and forget Step 5 (Repeat).
- Subordination is counterintuitive: Running non-bottleneck machines at less than full capacity feels wasteful. It's not — overproduction at non-bottlenecks creates WIP that clogs the system.
- TOC vs Lean: Lean eliminates waste everywhere. TOC focuses only on the constraint. They complement each other: use TOC to find WHERE to focus, Lean to optimize HOW.
- 约束可能是非物理性的:市场需求、政策或管理层关注度都可能成为真正的约束。如果工厂产能可达1000件,但仅能售出500件,那么市场就是约束。
- 瓶颈会转移:提升一个瓶颈后,约束可能会转移到其他环节。团队常常在庆祝后忘记步骤5(重复)。
- 迁就反直觉:让非瓶颈设备不满负荷运行看起来像是浪费,但实际上并非如此——非瓶颈环节的过度生产会产生在制品,导致系统拥堵。
- TOC vs 精益生产:精益生产致力于消除所有环节的浪费。TOC仅聚焦于约束环节。二者可以互补:用TOC确定聚焦的位置,用精益生产优化具体的方法。
References
参考资料
- For Drum-Buffer-Rope implementation details, see
references/dbr-scheduling.md
- 如需了解Drum-Buffer-Rope调度的实施细节,请参阅
references/dbr-scheduling.md