Skip to main content

Overview

The PFMEA Detection scale measures how well manufacturing controls can identify when a process failure has occurred. Unlike DFMEA Detection, which focuses on design-level detection methods, PFMEA Detection specifically addresses production process controls such as automated gauging, Statistical Process Control (SPC), and visual inspection at manufacturing stations.
Detection ratings use an inverted scale: lower values (1-3) represent high detection capability through error-proofing and automation, while higher values (8-10) represent poor or absent detection capabilities relying on manual inspection or random sampling.

Detection Rating Scale

RatingNameDetection MethodDetection CapabilityTypical Escape Risk
0UnanalyzedNot yet assignedUnknown
1Error-Proofing (Poka-Yoke)Product/process design prevents defect creationAlmost Certain (99%+)<0.1%
2Automatic Gauging + Auto-StopAutomated measurement system halts production on defectVery High (95-99%)0.1-1%
3Multi-Layer In-Process DetectionMultiple verification points (in-station + subsequent ops)High (85-95%)1-5%
4Subsequent Operation DetectionSetup inspection or first-piece detection in downstream operationModerately High (70-85%)5-10%
5Variable/Go-No-Go GaugingMeasurement or attribute inspection after station, sampling-basedModerate (50-70%)10-20%
6SPC Charting ControlStatistical Process Control with trend monitoringLow (30-50%)20-40%
7Double Visual InspectionTwo independent visual inspections without measurementVery Low (10-30%)40-70%
8Single Visual InspectionOne visual inspection per piece, no measurementRemote (5-10%)70-80%
9Indirect or Random ChecksSampling-based or indirect indicator monitoringVery Remote (1-5%)80-99%
10No DetectionNo inspection or control existsAlmost Impossible (<1%)>99%

Detection Method Categories

Prevention-Based Controls (Ratings 1-2)

Error-Proofing (Rating 1) — The highest detection capability where process or product design makes it physically impossible to create a defective part:
  • Poka-yoke principle: design eliminates the failure mode at the source
  • Examples: keyed connectors, fixture nesting, part geometry constraints
  • RPN impact: Dramatically reduces escape risk; often combined with low severity ratings
Automatic Gauging with Auto-Stop (Rating 2) — Automated measurement systems that halt production immediately when specifications are violated:
  • In-process automated inspection: laser gauging, pneumatic comparators, vision systems
  • Prevents any out-of-spec parts from advancing downstream
  • High cost/complexity but near-perfect detection capability
  • Requires calibration and maintenance planning

In-Process Detection (Ratings 3-5)

Multi-Layer In-Process Detection (Rating 3) — Multiple verification checkpoints create redundant detection:
  • Examples: 100% in-station measurement + second-operation verification
  • Catches errors at first opportunity, with backup detection
  • Typical in safety-critical or high-complexity processes
Subsequent Operation Detection (Rating 4) — Errors detected in downstream operations:
  • Setup approval / first-piece inspection
  • Functional test in next operation
  • Trade-off: defects caught before customer, but downstream rework costs
Variable/Go-No-Go Gauging (Rating 5) — Measurement or attribute inspection with sampling:
  • Go/No-Go gauging (binary attribute checks) at the station
  • Variable measurement (continuous, e.g., 0-10 mm)
  • Sampling plans reduce detection in proportion to sample size
  • Cpk relationship: high-Cpk processes reduce occurrence rating, justifying moderate detection

Statistical & Visual Controls (Ratings 6-9)

RatingMethodAdvantagesLimitations
6SPC ChartingPredictive trend detection, process capability insightReactive (detects drift after samples plotted)
7Double VisualLow cost, no equipment neededError-prone; depends on training/attention
8Single VisualSimple implementationHigh escape risk; inconsistent standards
9Random SamplingLow labor costVery limited detection; only acceptable for stable, high-Cpk processes
Rating 6 (SPC) and Ratings 7-9 (visual inspection) are not recommended for new PFMEA analyses. Modern manufacturing standards (IATF 16949, AIAG-VDA) favor error-proofing and automated detection. Use only when justifiable by:
  • Process stability data (demonstrated Cpk ≥ 1.67)
  • Historical defect rates <10 ppm
  • Risk assessment showing acceptable residual risk

Detection and RPN Calculation

PFMEA Detection combines with Severity and Occurrence to calculate Risk Priority Number (RPN):
RPN = Severity × Occurrence × Detection

RPN Decision Matrix

This matrix shows how detection rating affects risk classification for a sample process failure:
SeverityOccurrenceDetection RatingRPNRisk LevelRecommendation
861 (Error-proof)48LowAcceptable; routine monitoring
863 (Multi-layer)144MediumMonitor; consider controls if Occ high
866 (SPC)288HighUnacceptable; require auto-gauging
869 (Random)432CriticalUnacceptable; implement error-proofing
Example: A process failure with Severity 8, Occurrence 6 becomes acceptable (RPN 48) only with error-proofing (Rating 1). Relying on visual inspection (Rating 8) yields RPN 384 — unacceptable.

RPN Thresholds

TestAuto2 — Automotive Safety Solution follows AIAG-VDA FMEA thresholds:
RPN RangeClassificationAction Required
1–40LowRoutine process control; document in control plan
41–100MediumEvaluate control improvements; may require risk control
101–200HighImplement additional controls; risk control mandatory
>200CriticalUnacceptable; implement immediate mitigation

Detection Improvement Workflow

Detection ratings evolve during PFMEA lifecycle:
Pre-Mitigation Analysis          Control Plan Implementation
─────────────────────────        ────────────────────────────
Initial Detection Rating         Updated Detection Rating
   (Current Controls)               (Proposed Controls)
        ↓                               ↓
   RPN Calculated              New RPN Shows Risk Reduction
   (Often High)                (RPN should drop 50-80%)
        ↓                               ↓
   High-Risk Items             Post-Mitigation Tracking
   Identified                  in pfmRPNPost field
Progressive Workflow: In Risksheet PFMEA documents, users can:
  1. Initial PFMEA Phase: Assess detection using current manufacturing controls
  2. Risk Assessment Phase: Calculate pre-mitigation RPN
  3. Control Plan Phase: Define improved detection methods (e.g., upgrade from Rating 6 to Rating 2)
  4. Post-Mitigation Phase: Update detection rating, recalculate RPN to verify acceptability

Configuration in TestAuto2

Risksheet Integration

PFMEA Detection appears in Risksheet PFMEA documents as the pfmDetection field:
# Column name in PFMEA Risksheet
- fieldName: pfmDetection
  type: enum
  label: "Detection (Pre)"
  enumRef: processFailureMode-detection-enum
  required: true
  description: "Current manufacturing control detection effectiveness"
Related fields:
  • pfmDetectionPost — Post-mitigation detection rating (after controls implemented)
  • pfmSeverity + pfmOccurrence — Combined with detection to calculate pfmRPN

Configuration Properties

PropertyValueNote
EnumerationprocessFailureMode-detection-enum11 values (0-10)
Work Item TypeprocessFailureModePFMEA failure mode records
Field NamepfmDetectionPre-mitigation detection rating
Post-Field NamepfmDetectionPostPost-mitigation rating tracking
RPN FormulapfmSeverity × pfmOccurrence × pfmDetectionCalculated field
Default Value0 (Unanalyzed)Must be set before RPN calculation

Best Practices

  1. Start with current-state detection: Assess what controls actually exist today, not what you wish existed
  2. Document the control method: In control plan module, describe the gauge/process used (e.g., “100% laser gauging at Station 3B”)
  3. Upgrade detection before occurrence: It’s typically easier to improve detection (add gauging) than reduce occurrence (process redesign)
  4. Error-proofing first: If RPN is unacceptable, prioritize moving from Rating 6-9 → Rating 1-2 rather than accepting high escape risk
  5. Post-mitigation tracking: Always update pfmDetectionPost and pfmRPNPost when implementing controls to show risk reduction effectiveness
  6. SPC as complement, not primary: Use Rating 6 (SPC) only in combination with sampling inspection, never as sole detection method for new design

Enumeration Values Reference

<!-- .polarion/tracker/fields/processFailureMode-detection-enum.xml -->
<option id="pfmDetection-0">
  <name>0 - Unanalyzed</name>
  <description>Detection method not yet assigned</description>
</option>
<option id="pfmDetection-1">
  <name>1 - Error-Proofing (Poka-Yoke)</name>
  <description>Design prevents defect creation; almost certain detection</description>
</option>
<option id="pfmDetection-2">
  <name>2 - Automatic Gauging + Auto-Stop</name>
  <description>Automated measurement halts production on defect</description>
</option>
<!-- ... Ratings 3-10 follow similar pattern ... -->

See Also