Pfmea

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

Occurrence (O) - Likelihood of Cause

Detection (D) - Ability to Detect Before Customer

Action Priority (AIAG-VDA Approach)

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

RPN Thresholds (MNMUK Standard)

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