Claude-skill-registry Pfmea

Generate AIAG-VDA compliant Process FMEAs with proper Severity/Occurrence/Detection ratings, RPN calculations, and countermeasure recommendations. Covers MNMUK departments (Machine Shop, Damper, LVA, FML). USE WHEN user says 'PFMEA', 'FMEA', 'failure mode', 'risk analysis', 'RPN', 'severity occurrence detection', or 'process risk assessment'. Integrates with AutomotiveManufacturing, ControlPlan, and A3criticalthinking skills.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/Pfmea" ~/.claude/skills/majiayu000-claude-skill-registry-pfmea && rm -rf "$T"
manifest: skills/data/Pfmea/SKILL.md
source content

Process FMEA (PFMEA)

When to Activate This Skill

  • "Create a PFMEA for [process]"
  • "What are the failure modes for [operation]?"
  • "Calculate RPN for [risk scenario]"
  • "Rate severity/occurrence/detection for [failure]"
  • "Identify process risks"
  • "FMEA analysis for [part/process]"

AIAG-VDA 7-Step Methodology

Step 1: Planning and Preparation

  • Define scope and boundaries
  • Identify team members (cross-functional)
  • Gather documentation (process flow, control plan, drawings)
  • Review lessons learned from similar processes

Step 2: Structure Analysis

  • Define process steps from process flow diagram
  • Create process tree (System > Sub-system > Process Element)
  • Identify interfaces between steps
  • Link to product characteristics

Step 3: Function Analysis

  • Define function of each process step
  • Identify product/process requirements
  • Link to customer/engineering specifications
  • Document special characteristics (CC/SC)

Step 4: Failure Analysis

  • Identify failure modes (how can step fail to perform function?)
  • Determine failure effects (consequences to customer/next operation)
  • Identify failure causes (why would failure mode occur?)
  • Chain: Cause → Failure Mode → Effect

Step 5: Risk Analysis

  • Rate Severity (S) of effects: 1-10
  • Rate Occurrence (O) of causes: 1-10
  • Rate Detection (D) of controls: 1-10
  • Calculate Action Priority (AP) or RPN

Step 6: Optimization

  • Prioritize high-risk items
  • Develop countermeasures (hierarchy: Eliminate > Substitute > Engineer > Admin > Detect)
  • Assign responsibility and target dates
  • Re-rate after countermeasures

Step 7: Results Documentation

  • Document all analysis
  • Track countermeasure completion
  • Update Control Plan linkage
  • Archive for lessons learned

Rating Scales (MNMUK Standard)

Severity (S) - Effect on Customer/Process

RatingCriteriaMNMUK Examples
10Affects safety without warningBrake component failure, no containment possible
9Affects safety with warningSafety critical dimension OOS, detectable at assembly
8Product inoperable, 100% scrapPart cannot be reworked, total loss
7Product operable but degraded, customer dissatisfiedPerformance below spec, customer complaint
6Product operable, comfort/convenience affectedCosmetic defect, minor fit issue
550% of product may need reworkSignificant rework required
4Product requires sorting/reworkSorting operation needed
3Minor rework at stationIn-station repair possible
2Slight inconvenienceMinor adjustment
1No effectNo discernible impact

Occurrence (O) - Likelihood of Cause

RatingFailure RateCpk EquivalentMNMUK Examples
10Very high: ≥100/1000<0.33New process, no controls
9High: 50/1000≥0.33Known problem process
8High: 20/1000≥0.51Similar process had failures
7Moderately high: 10/1000≥0.67Occasional failures observed
6Moderate: 2/1000≥0.83Infrequent failures
5Moderately low: 0.5/1000≥1.00Controlled process, some failures
4Low: 0.1/1000≥1.17Well-controlled process
3Very low: 0.01/1000≥1.33Capable and controlled
2Remote: 0.001/1000≥1.50Proven design and controls
1Nearly impossible: ≤0.001/1000≥1.67Failure eliminated by design

Detection (D) - Ability to Detect Before Customer

RatingDetection CapabilityMNMUK Examples
10No detection possibleNo inspection, no opportunity to detect
9Unlikely to detectRandom sampling only, infrequent
8Low: Visual inspection by operator100% visual check, variable attention
7Very low: Double visual inspectionTwo operators check
6Low: Charting/SPCControl charts, trend monitoring
5Moderate: Attribute gagingGo/No-go gaging
4Moderately high: Variable gagingMeasurement with limit checking
3High: Automated in-process testAutomatic measurement, alarm
2Very high: Error-proofingPoka-yoke prevents defect production
1Almost certain: Error-proofing prevents causeDesign makes failure impossible

Action Priority (AIAG-VDA Approach)

Instead of or in addition to RPN, use Action Priority:

PriorityCriteriaAction Required
HIGHS=9-10 (any O, D) OR S=7-8 with O≥4 AND D≥4Immediate action required
MEDIUMS=5-8 with O≥4 OR D≥4Action recommended
LOWAll othersMonitor and document

RPN Thresholds (MNMUK Standard)

RPN RangePriorityRequired Action
≥120CriticalImmediate countermeasure, cannot ship without action
80-119HighCountermeasure required before PPAP
40-79MediumCountermeasure recommended
<40LowMonitor, no immediate action

Note: Any Severity ≥8 requires action regardless of RPN.

Countermeasure Hierarchy

When addressing failure modes, apply controls in this priority order:

  1. Eliminate - Design out the failure mode entirely
  2. Substitute - Replace with less hazardous process/material
  3. Engineer - Install physical safeguards, poka-yoke
  4. Admin - Procedures, training, work instructions
  5. Detect - Inspection, testing, monitoring

Special Characteristics

Critical Characteristics (CC)

  • Safety or regulatory impact
  • Marked with shield symbol or (CC)
  • Requires enhanced controls
  • Mandatory documentation

Significant Characteristics (SC)

  • Fit, function, or durability impact
  • Marked with diamond or (SC)
  • Requires appropriate controls
  • SPC typically required

Output Format

When generating PFMEA content:

# PFMEA: [Part/Process Name]
**Part Number**: [P/N]
**Process**: [Description]
**FMEA Number**: PFMEA-[DEPT]-[SEQ]
**Revision**: [Rev] | **Date**: [YYYY-MM-DD]
**Team**: [Names/Roles]

## Process Step: [Step Name]

### Failure Mode 1: [Description]
**Function**: [What the step should do]
**Effect**: [What happens if it fails]
**Cause**: [Why it would fail]

| S | O | D | RPN | AP |
|---|---|---|-----|-----|
| X | X | X | XXX | H/M/L |

**Current Controls**:
- Prevention: [Current prevention measures]
- Detection: [Current detection measures]

**Recommended Actions**:
- [ ] [Action description] - Owner: [Name] - Due: [Date]

**After Action**:
| S | O | D | RPN | AP |
|---|---|---|-----|-----|
| X | X | X | XXX | H/M/L |

Department-Specific Guidance

Machine Shop

  • Common failure modes: Dimensional OOS, surface finish, tool wear
  • Focus on: Fixturing, program parameters, tool life management
  • Key controls: First piece inspection, SPC, gage R&R

Damper Assembly

  • Common failure modes: Leak, incorrect torque, missing component
  • Focus on: Seal integrity, fastener torque, component presence
  • Key controls: Leak test, torque verification, poka-yoke

LVA (Low Volume Assembly)

  • Common failure modes: Wrong component, incorrect orientation, damage
  • Focus on: Part identification, assembly sequence, handling
  • Key controls: Visual verification, traveler documentation

FML (Final Manufacturing Line)

  • Common failure modes: Test failure, labeling error, packaging damage
  • Focus on: Final test parameters, traceability, packaging
  • Key controls: Automated test, barcode verification, packaging audit

Integration with Related Skills

ControlPlan

PFMEA feeds directly into Control Plan:

  • High S/O items require enhanced inspection
  • Detection controls become Control Plan methods
  • Special characteristics flow to Control Plan

Load:

read ~/.claude/skills/Controlplan/SKILL.md

AutomotiveManufacturing

Work instructions should reflect PFMEA findings:

  • High-risk steps highlighted
  • Operator controls documented
  • Quality checkpoints specified

Load:

read ~/.claude/skills/Automotivemanufacturing/SKILL.md

A3criticalthinking

When PFMEA reveals issues:

  • Use 5 Whys for root cause analysis
  • Fishbone diagram for cause identification
  • A3 format for countermeasure planning

Load:

read ~/.claude/skills/A3criticalthinking/SKILL.md

Supplementary Resources

For detailed guidance:

read ~/.claude/skills/Pfmea/CLAUDE.md

For templates:

ls ~/.claude/skills/Pfmea/templates/

For rating scales:

read ~/.claude/skills/Pfmea/reference/rating-scales.md

For common failure modes:

read ~/.claude/skills/Pfmea/reference/common-failure-modes.md