DI-SESS-82511
Process Failure Mode and Effects Analysis (PFMEA)
Describes the Process Failure Mode and Effects Analysis (PFMEA) report used as a proactive risk management tool to identify failure modes, rank their risk, and develop mitigation actions for manufacturing and assembly processes.
Approval DateJanuary 8, 2026
AMSC NumberN10613
Preparing ActivityAS
Project NumberSESS-2026-004
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Supersedes
—Related
—Description & Purpose
—
Application & Interrelationship
—
Use & Relationship
This report leverages Process Failure Mode and Effects Analysis (PFMEA) as a structured, proactive risk management tool used continuously from conceptual design onward to document, monitor, and approve manufacturing and assembly processes by identifying potential failure modes, ranking their risk based on probability and consequence, and developing mitigation actions, ultimately aiming to prevent failures, reduce costs, enhance quality, improve customer satisfaction, and optimize production performance, particularly in critical processes where safety and mission performance are paramount.
This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract SOW.
Preparation Instructions
1Reference documentsN/A
2FormatThe report shall be in contractor's format.
3ContentThe report shall systematically address the following components:
3.1Process Function
3.1.1DescriptionInclude a clear and concise statement of what the manufacturing process does (e.g., "Drilling holes for fastener insertion," "Applying protective coating," "Assembling two components").
3.1.2ContextProvide supporting details to understand the process's role within the overall manufacturing flow. Explain its purpose and how it contributes to the final product.
3.1.3Performance MetricsInclude relevant metrics to measure the process's effectiveness and efficiency. This could be cycle time, defect rate, throughput, etc.
3.2Potential Failure Mode
3.2.1DescriptionDefine how the process or part can fail to meet requirements or cause customer dissatisfaction. Focus on the physical manifestation of the failure (e.g., "Hole drilled off-center," "Surface coating uneven," "Component not properly seated," "Part bent during handling").
3.2.2CompletenessIdentify and describe all predictable failure modes for each component, subsystem, and process characteristic.
3.3Failure Effects
3.3.1DescriptionDetail the consequences of each failure mode on different levels:
3.3.1.1Local EffectInclude the immediate impact of the failure on the process itself (e.g., "Cannot assemble next component," "Damages drill bit," "Causes excessive vibration").
3.3.1.2Next Higher-Level EffectDescribe the impact on the subsequent manufacturing steps or systems (e.g., "Downstream process delayed," "Part doesn't fit in next assembly"). For downstream manufacturing, this is stated in terms of process performance.
3.3.1.3End EffectAddress the ultimate impact on the end user or the overall manufacturing process (e.g., "Product fails to function correctly," "Premature wear," "Rework required," "Increased scrap rate," "Intermittent operation," "Unacceptable noise"). These effects should be stated in terms of product or system performance.
3.4Severity
3.4.1DescriptionInclude a numerical ranking assigned to each failure effect, reflecting the worst potential consequence of the failure.
3.4.2Ranking CriteriaEstablish clear, objective criteria for severity levels (e.g., Minor, Marginal, Critical, Catastrophic) and assign numerical values to each. The PFMEA team must agree on these criteria.
3.4.3ConsiderationsFactors to consider include potential for injury, disruption to the manufacturing process, and damage to equipment or the final product.
3.5Causes
3.5.1DescriptionIdentify the potential root causes of each failure mode. These should be stated in terms that are controllable or preventable.
3.5.2Examples"Inaccurate tooling calibration," "Worn guide rails," "Improper material composition," "Insufficient lubrication," "Incorrect process parameters."
3.5.3Avoid AmbiguityDo not use vague causes like "Operator error" or "Machine malfunction." These need to be broken down into specific, actionable items.
3.5.4InvestigationRecognize that causes can be complex and interrelated. Design of experiments or other methods may be necessary to identify the most significant controllable factors.
3.6Occurrence
3.6.1DescriptionThe probability that a specific failure mode will occur.
3.6.2Numerical RankingAssigned a numerical rank based on established criteria.
3.6.3Data Sources
3.6.3.1Historical DataUse historical failure rate data whenever available.
3.6.3.2Similar ProcessesIf historical data is lacking, use statistical data from similar processes as a benchmark.
3.6.3.3Subjective AssessmentIf data is unavailable, the team may need to make a subjective assessment based on experience and knowledge.
3.7Current Process Controls
3.7.1DescriptionIdentify existing controls that are in place to either prevent or detect potential failure modes.
3.7.2Prevention Controls (Preferred)Controls that aim to stop the failure from happening in the first place (e.g., Statistical Process Control (SPC), error-proofing, robust design).
3.7.3Detection ControlsControls that are used to identify the failure after it has occurred (e.g., Gauging, manual inspection, automated testing, inability to pass a bad part to the next stage).
3.8Detection
3.8.1DescriptionThe probability that a failure will not be detected by the existing controls.
3.8.2Numerical RankingAssigned a numerical rank based on established criteria.
3.8.3AssessmentEvaluate the effectiveness of the detection controls. Consider factors like the reliability of the inspection process, the sensitivity of the measuring equipment, and the frequency of inspections.
3.9Risk Priority Number (RPN)
3.9.1CalculationRPN = Severity (S) x Occurrence (O) x Detection (D)
3.9.2InterpretationThe RPN provides a relative measure of criticality for each failure mode. Higher RPNs indicate more critical failures that require immediate attention.
3.9.3PrioritizationFocus efforts on addressing failure modes with the highest RPNs. Items with very low RPNs may not warrant action.
3.10Recommended Actions
3.10.1PurposeDevelop actions to reduce the RPNs by addressing the underlying causes of the failure modes.
3.10.2PrioritizationStart with the failure modes with the highest RPNs and work down the list.
3.10.3Reduction HierarchyPrioritize actions that reduce:
3.10.3.1SeverityEliminate or minimize the potential consequences of the failure. This is often the most difficult to change.
3.10.3.2OccurrenceReduce the probability of the failure occurring.
3.10.3.3DetectionImprove the ability to detect the failure before it reaches the customer.
3.10.4Emphasis on PreventionFocus on preventing failures rather than simply detecting them.
References
—
Schema v3.0Community-maintained · Verify against ASSIST
Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer
Verify against ASSIST·GitHub·About·Disclaimer