顯示具有 HMS Dragon 標籤的文章。 顯示所有文章
顯示具有 HMS Dragon 標籤的文章。 顯示所有文章

2026年3月5日 星期四

瓶頸官僚主義:限制理論剖析 HMS Dragon 與倫敦水電工延遲

 瓶頸官僚主義:限制理論剖析 HMS Dragon 與倫敦水電工延遲


從限制理論(TOC,Eliyahu Goldratt 所創)觀點,HMS Dragon 部署塞浦路斯延誤,或召喚倫敦水電工,皆源於相同根源:未識別瓶頸扼殺產出。TOC 主張每個系統僅有一關鍵限制阻礙效能——提升它,否則永遠落後。對 HMS Dragon,瓶頸非船隻(Type 45 驅逐艦極具能力),而是準備碎片化:維護後重新裝填導彈、武器重置、樸茨茅斯上港焊接。這些任務形成非線性鏈,船員可用性、零件物流、系統檢查構成關鍵路徑。同樣,倫敦水電工瓶頸在排程超載——單一技工多頭燒,遠赴 Essex 取零件,無緩衝應急。兩案皆然,「工具」(船或扳手)已備;缺失在於狠抓優先、從屬一切的意願。

關鍵鏈專案管理(CCPM)即 TOC 解藥。此法將安全邊際彙整至專案末端緩衝,而非任務內填充,縮減工期 30-50%。對 HMS Dragon,繪製關鍵鏈(導彈裝填→測試→出航),斷絕多工(無雙重任務配置),以緩衝護航供應波動。水電工可借簡易 App 實踐 CCPM:依緊急批次作業,高優先維修鏈結,共享緩衝應付缺席,將等候從數週壓至數日。模擬顯示 CCPM 解決 80% 延誤,聚焦資源爭奪,而非加班英雄。

然,症結在此:這些方法在工廠、IT 屢試不爽——波音至英特爾皆然——卻在意志薄弱處失效。英國國防部陷預算緊縮、艦隊準備拖沓;水電工抗軟體,偏好現金混亂。工具比比皆是(海軍用 Primavera,技工用 Jobber);缺失非工具,乃實作、衡量、強制的意願。未採 TOC 紀律,英國將繼續漂流——Dragon 緩行,水管永滴。

Bottlenecks of Bureaucracy: Theory of Constraints on HMS Dragon and London Plumbers

 Bottlenecks of Bureaucracy: Theory of Constraints on HMS Dragon and London Plumbers


From a Theory of Constraints (TOC) perspective, delays in deploying HMS Dragon to Cyprus or summoning a London plumber stem from the same root: unidentified bottlenecks choking throughput. TOC, pioneered by Eliyahu Goldratt, posits that every system has a single constraint limiting performance—elevate it, or suffer perpetual lag. For HMS Dragon, the constraint isn't the ship itself (a capable Type 45 destroyer), but fragmented preparation: post-maintenance rearming, weapon reconfiguration, and welding at Portsmouth's upper harbor. These tasks form a non-linear chain where crew availability, parts logistics, and system checks create the critical path. Similarly, London plumbers face their bottleneck in scheduling overload— one tradie juggling multiple jobs, sourcing obscure parts from Essex, with no buffer for emergencies. In both cases, the "tool" (ship or wrench) is ready; the deficiency lies in the will to ruthlessly prioritize and subordinate everything else.

Enter Critical Chain Project Management (CCPM), TOC's antidote to such chaos. CCPM aggregates safety margins into project buffers at the end, not per-task padding, cutting lead times by 30-50%. For HMS Dragon, map the critical chain (missile loading → testing → sail), cut multitasking (no dual mission fittings), and protect it with a buffer against supply hiccups. Plumbers could adopt CCPM via simple apps: batch jobs by urgency, chain high-priority fixes with shared buffers for no-shows, slashing wait times from weeks to days. Simulations show CCPM resolves 80% of delays by focusing on resource contention, not heroic overtime.

Yet, here's the rub: these methods work wonders in factories and IT—from Boeing to Intel—but falter where will is weak. UK's MoD dilly-dallies on fleet readiness amid budget squeezes; plumbers resist software, preferring cash-in-hand chaos. Tools abound (Primavera for navies, Jobber for trades); the deficiency is not the tool, but the will to implement, measure, and enforce. Until brass and blokes embrace TOC's discipline, Britain will drift—Dragon dawdling, pipes perpetually dripping.