Skip to content

charlieviettq/awesome-agent-skill / .claude/skills/algo-mfg-fmea

"algo-mfg-fmea"

Verified

"Conduct FMEA to systematically identify, prioritize, and mitigate potential failure modes. Use this skill when the user needs to assess product or process risks, prioritize corrective actions, or build a risk register — even if they say 'failure mode analysis', 'risk assessment', 'what could go wrong', or 'RPN calculation'.".

FileKindSize
SKILL.mdskill md4.7 KB
examples/sample_scenario.mdmarkdown7.3 KB
references/aiag-vda-ap.mdmarkdown8.8 KB
references/scoring-rubrics.mdmarkdown11.1 KB

examples/sample_scenario.md

View on GitHub
直接撰寫檔案內容:

```markdown
# Example: EV 充電槍防水組件 PFMEA

## Scenario

**公司:** 台達電子 EV 充電部門  
**產品:** Level 2 AC 充電槍(7.4 kW 家用型)  
**背景:** 品保工程師 Emily Chen 負責充電槍組裝線(Line 4)的品質提升。近兩季田間回報(Field Return)中,有 14% 的案例與防水密封失效有關,客訴涉及充電插頭進水導致充電中斷。品保主管要求在下一版製程改善前,先完成 PFMEA,找出高優先風險並定義驗證動作。

**Emily 的問題:**
> 「我有組裝 Line 4 的流程圖,共 7 個工站。我想先聚焦在防水相關的工站做 FMEA,找出 RPN 最高的幾個點,並決定要補什麼管制。」

---

## Analysis

### Phase 1:範圍定義與輸入確認

- **類型:** PFMEA(製程 FMEA,非設計 FMEA)
- **範圍:** Line 4 防水相關工站:O-Ring 組裝(WS-3)、超音波熔接(WS-5)、氣密測試(WS-6)
- **跨職能團隊:** 製程工程師、品保、產線主管、供應商品質
- **參考文件:** 組裝作業標準(SOP-L4-003)、田間回報統計(Q3–Q4 2025)

**Gate 確認:** 範圍、團隊、SOP 與田間數據均就位。

---

### Phase 2:失效模式分析

以下針對三個工站列出主要失效模式,採用 **Classic RPN** 並附 **AIAG-VDA AP** 判定。

#### WS-3:O-Ring 組裝

| 失效模式 | 效應(客戶) | 根本原因 | 現行預防管制 | 現行偵測管制 | S | O | D | RPN | AP |
|---------|------------|---------|------------|------------|---|---|---|-----|----|
| O-Ring 漏裝 | 充電槍進水、充電中斷 | 人工組裝無防呆 | 目視 SOP | 操作員目視確認 | 9 | 4 | 7 | **252** | **High** |
| O-Ring 扭轉(Twist) | 密封不完整,低速進水 | 置入角度未管制 | 無 | 氣密測試(WS-6) | 8 | 5 | 5 | **200** | **High** |
| O-Ring 尺寸錯誤(混料) | 密封失效 | 料號相近,人工取料易混 | 料架標籤 | 無(尺寸差異不易目視) | 8 | 2 | 8 | 128 | Medium |

#### WS-5:超音波熔接

| 失效模式 | 效應(客戶) | 根本原因 | 現行預防管制 | 現行偵測管制 | S | O | D | RPN | AP |
|---------|------------|---------|------------|------------|---|---|---|-----|----|
| 熔接強度不足(Weld Weak) | 殼體分離,防水破壞 | 振幅/加壓時間漂移 | 每班參數確認 | 破壞性抽驗(每 200 pcs 1 件) | 9 | 3 | 6 | **162** | **High** |
| 熔接過強(Over-weld) | 殼體裂紋,應力進水 | 參數上限無自動斷點 | 無 | 外觀目視 | 7 | 2 | 5 | 70 | Low |
| 定位偏移(Misalign) | 接合面不均,局部滲漏 | 治具磨損 | 治具定期保養(月保) | 外觀目視 | 8 | 3 | 6 | 144 | Medium |

#### WS-6:氣密測試(現行偵測管制)

| 失效模式 | 效應(客戶) | 根本原因 | 現行預防管制 | 現行偵測管制 | S | O | D | RPN | AP |
|---------|------------|---------|------------|------------|---|---|---|-----|----|
| 測試誤判(False Pass) | 不良品流出 | 洩漏閾值設定過鬆(>5 cc/min) | 無 | 測試機自動判定 | 9 | 3 | 5 | **135** | **High** |
| 夾具洩漏(Fixture Leak) | 偵測率下降,遮蔽真實漏氣 | 夾具 O-Ring 老化 | 無定期更換頻率 | 無 | 8 | 4 | 8 | **256** | **High** |

---

### Phase 3:評分合理性複查

**Severity 審查:**
- O-Ring 漏裝 S=9 → 直接進水,可能造成充電中斷甚至短路,確認 S=9 合理(不因氣密測試的存在而降低)
- Severity 不因下游偵測管制的存在而降低 —— Iron Law 確認

**Detection 審查:**
- WS-6 夾具洩漏的偵測管制:「無」→ D=8,符合無偵測 = 高 D 值原則
- 操作員目視確認 O-Ring 漏裝:D=7(人工目視可靠性低)

**優先序確認(High AP):**
1. 夾具洩漏(RPN=256,AP=High)—— 遮蔽所有後續偵測,影響最廣
2. O-Ring 漏裝(RPN=252,AP=High)
3. O-Ring 扭轉(RPN=200,AP=High)
4. 熔接強度不足(RPN=162,AP=High)
5. 氣密測試誤判(RPN=135,AP=High)

---

### Phase 4:建議改善行動

| # | 失效模式 | 改善行動 | 預期效果 | 負責人 | 目標日期 |
|---|---------|---------|---------|-------|---------|
| A1 | 夾具洩漏 | 建立夾具 O-Ring 更換週期(每 500 件更換),加入 PM 清單 | D: 8→4 | ME 林工程師 | 2026-04-30 |
| A2 | O-Ring 漏裝 | 導入感測器防呆(組裝工站加裝壓力感知確認 O-Ring 到位) | O: 4→1, D: 7→2 | 製程工程師王組長 | 2026-05-15 |
| A3 | O-Ring 扭轉 | 設計導正槽(Groove)治具,限制置入方向 | O: 5→2 | 設計工程師 | 2026-05-31 |
| A4 | 熔接強度不足 | 導入即時監控(每件記錄振幅+能量),設定 SPC 管制界限 | O: 3→1, D: 6→2 | 品保 Emily Chen | 2026-04-25 |
| A5 | 氣密測試誤判 | 將洩漏閾值收緊至 ≤2 cc/min,重新驗證 Gauge R&R | D: 5→2 | 品保 Emily Chen | 2026-04-20 |

---

## Result

```json
{
  "fmea_items": [
    {
      "ws": "WS-6",
      "failure_mode": "夾具洩漏(Fixture Leak)",
      "effect": "偵測率下降,不良品流出",
      "cause": "夾具 O-Ring 老化,無更換週期",
      "severity": 8,
      "occurrence": 4,
      "detection": 8,
      "rpn": 256,
      "ap": "high",
      "action": "建立夾具 O-Ring 更換週期(每 500 件),納入 PM 清單"
    },
    {
      "ws": "WS-3",
      "failure_mode": "O-Ring 漏裝",
      "effect": "充電槍進水、充電中斷",
      "cause": "人工組裝無防呆",
      "severity": 9,
      "occurrence": 4,
      "detection": 7,
      "rpn": 252,
      "ap": "high",
      "action": "加裝壓力感知防呆,確認 O-Ring 到位"
    },
    {
      "ws": "WS-3",
      "failure_mode": "O-Ring 扭轉(Twist)",
      "effect": "密封不完整,低速進水",
      "cause": "置入角度未管制",
      "severity": 8,
      "occurrence": 5,
      "detection": 5,
      "rpn": 200,
      "ap": "high",
      "action": "設計導正槽治具,限制置入方向"
    },
    {
      "ws": "WS-5",
      "failure_mode": "熔接強度不足",
      "effect": "殼體分離,防水破壞",
      "cause": "振幅/加壓時間漂移",
      "severity": 9,
      "occurrence": 3,
      "detection": 6,
      "rpn": 162,
      "ap": "high",
      "action": "導入即時 SPC 監控振幅與能量"
    },
    {
      "ws": "WS-6",
      "failure_mode": "氣密測試誤判(False Pass)",
      "effect": "不良品流出",
      "cause": "洩漏閾值設定過鬆",
      "severity": 9,
      "occurrence": 3,
      "detection": 5,
      "rpn": 135,
      "ap": "high",
      "action": "閾值收緊至 ≤2 cc/min,重新執行 Gauge R&R"
    }
  ],
  "summary": {
    "total_modes": 8,
    "high_priority": 5,
    "medium": 2,
    "low": 1
  },
  "metadata": {
    "type": "PFMEA",
    "scope": "Line 4 防水工站 WS-3, WS-5, WS-6",
    "product": "Level 2 AC 充電槍 7.4 kW",
    "revision": "Rev A — 2026-04-10"
  }
}
```

**關鍵結論:**
- 最高優先項目(A1)是**夾具洩漏**,因為它讓現行偵測管制失效,導致所有後續失效模式的 Detection 分數虛高——必須最先修正,否則 WS-6 的數據完全不可信。
- 田間回報的 14% 防水失效,主要由 O-Ring 漏裝與扭轉貢獻,改善後預估 RPN 可降至 18(S=9, O=1, D=2),Field Return 率應顯著下降。
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall