DFMEA_Handout_. 01-19
DFMEA_Handout_. 01-19
KGOC
Best Practices
Course Coverage
DFMEA – Course
Contents
• FMEA - Basic Purpose & Key Benefits
• Types & Categories of FMEA
• FMEA Objectives
• D & PFMEA Flow
• Inputs required for DFMEA
• Cross Functional Team – Roles & Resp
• DFMEA – Working Model & Detailed Work shop
• System, Sub – System, Component with various
levels & defining the relationships
DFMEA – Course
Contents
• Defining Scope
• Defining the interactions with respect to the scope
• Identification of 5 Noise Factors
• Defining the Functions
• Defining the Effects of the Interactions
• Defining Essential parameters for the designing a
product
• Construction of DFMEA
• Defining Design Review Check Points
• Defining Design Verification & Validation Plan
• Group exercises, Interaction & Conclusion
DFMEA Course –
Scope Clarifications
DFMEA Course –
Scope
• Product Structure Tree Diagram
• Boundary Diagram
• Item Function Work Sheet
• Interface Matrix
• Dr. Taguchi’s P – Diagram
• DFMEA Working Model & Application
• Design Review Check List – Guidance
• Design Review Check List - Guidance
• Robustness & Reliability (R & R) Check List -
Guidance
DFMEA Course –
Not the Scope
• QFD
• New Product Development Process (APQP)
• Production Part Approval Process
• PFMEA
• Proto Program
• GD & T
• Detailed Design Review check points
• Detailed Design Verification & Validation check
points
• Detailed R & R check points
DFMEA Course –
Not the Scope
• DOE
• Simulation Techniques (Software & Real life)
• Functional Testing Methods in detail
• DFM, DFA, DFS, DFSS – details
• Regulatory Requirements
• Restricted Material & Substances
• Problem Solving Structured Approach
• 2D & 3D software methods
• Poka Yoke
FMEA –
Implementation
• Important factor for successful implementation of an
FMEA program is “TIMELINESS”
• TIMELINESS means “Before – the – event” action not an
“after – the – fact” exercise.
• To Achieve the greatest value, the FMEA must be done
before a product or Process Failure Mode has been
incorporated into product or process.
• Product & Process Changes can be most easily and
inexpensively implemented and also will minimize late
change crises.
FMEA – Purpose
• DISASTER happens if we don’t deliver what the
customer wants and the product does not reliably function
• UNRELIABLE PRODUCTS result if we deliver what the
customer wants, but the product does not reliably
function
• RELIABLE PRODUCTS / CUSTOMER DOES NOT
WANT happens when product fulfills all functions, but
is not what customer expects
• EXCELLENT PRODUCTS results when we deliver what
customer wants and product fulfills all functions
• FMEAs get the failure out of the products
FMEA – Benefits
FMEA – Benefits
What this chart indicates?
45
40
35
30
25
20
15
10
5
0
Design Supplier Mfg. process
FMEA – Benefits
• The chart in the previous slide explains the percentage of
field failures attributed to major three categories defined.
30%
25%
20%
15%
10%
5%
0%
Int Wear P - P
usage out Varn
Applications Categories
Machinery FMEA –
Key Benefits
Machinery FMEA –
Key Outputs
• Team Formation
• Establish Scope
• Inputs to DFMEA - Product Structure Tree
- Boundary Diagram
- Interaction Matrix
- Item Function Work Sheet
- P Diagram
• Identification of Potential Failure Mode
• Estimate the potential Risk / Effect of the Failure
• Ranking Severity
• Identification of Potential Critical & Significant
Characteristics
• Identification of Potential Cause of the Failure
• Ranking the Occurrence
• Identification of Current Design Controls in terms of
Prevention and Detection
• Ranking the Detection
• Estimating the overall risk by identifying the RPN for the
causes / Failure Mode
• Right skill sets are ensured among the team members and
roles are defined by Apex Management Group.
CFT – Key
Responsibilities
• As a cross functional team, to make sure the activities
performed are as per the Launch requirement including
PPAP.
• To get involved in effectively carrying out
D & PFMEAs, PFD, CP, SPC, MSA, PPAP including WI.
• To ensure the activity completion as per the check points
under “ Program Management Responsibility” for every
stage.
• In appropriate stages, to ensure the Customer and supplier
involvement in new product launch.
HOW WHO
WHEN
WHERE
WHAT
WHY
Pen System
Cap Clip Neck Body refill tube Nib Ball Refill cap Ink Spring Component
Spring
Refill
Tube
Cap Assy Neck Body
Refill
Ink Cap
Refill
(inside) Assy
PST – Automotive
Example - Car
Car System
Sub-System
Front Rear Level - 2
Refill Nib
Assy Assy Environment
C, E, W/T - Temp
- Humidity
C, E, W/T C, E, W/T - Dust, etc
Cap Refill
Ball Neck, Cap
Assy Customer
C&E Body & C&E usage
Refill Assy
Nib Ink
C & W/T Wear & Tear
Refill
Neck Tube External
System
Lower
Bump C, E, W/T Bush & Environment
Stopper Sleeve - Temp
- Humidity
Upper C, E, W/T - Dust, etc
Bush &
Axle sleeve Rear Customer
Beam
C&E Shock E & W/T
usage
Absorber Ex: Bad
Piston Outer driving
Rod Tube
Lateral Sub Sub
Assy Wear & Tear
Rod Assy
Inner
Oil Tube External System
Tyre &
Sub Assy
Wheel
Boundary Diagram
Group Activity & Presentation
Time Limit: 0.5 hrs (max)
Defining Functions
• A well defined Function / Requirement will lead to
Reliable and Robust Design
• Consider Following Inputs to capture most functions:
- Global Customer Requirements
- System & Sub-System Design Spec
- Engineering Specifications
- Design Verification plan & Sign off
- QFD
- Regulatory Requirements
- Other essential inputs
Interaction Matrix
• Quantifying the system interactions
• If interactions are not addressed, it may lead to potential
warrenty / recall issues.
• Mandatory for all new designs
• Used to check the validity of the completed causes in
DFMEA
• Every interaction both positive and negative should be
verified
• Negative interactions are analyzed further for corrective
action recommendations
Note: Refer Subsequent slide for example of Pen
(partially completed to explain the technique)
Interaction Matrix
P: Physically Touching
E: Energy Transfer
P E
I : Information exchange I M
M: Material exchange
Rear - - - - - -
Shock
Absorber
- 0 - - - -
+2 +2 +2 +2
Oil
- - - -
Outer +2 +2
Tube Sub
Assy - -
Inner
Tube Assy
Interaction Matrix
Group Activity & Presentation
Time Limit: 0.5 hrs (max)
Construction of P - Diagram
Noise Factors
Piece to Piece Variation Customer Usage Pattern Systems Interactions
Automotive P – Diagram –
Rear shock Absorber
Design Controls:
- International Standard for Material Selection
- JIS / DIN / IS for Dimensioning & Tolerancing (Spec)
- Proto Validation
- Software Simulation
- Product Endurance Testing
Mechanical Control:
- Mounting Materials
- Packaging Locations and Volume
- Cover / Housing design and material
Chemical Control:
- Coating material & thickness spec
• Responses:
• Signal Factors:
DFMEA – Example of
Construction and Application
C
D
L F Respon
O
Potential M sibility D
Potential Potential S C D Recomm
Causes/ E & target F
Item / Function Failure Effects of E A C E ended
Mechanisms A comple M
Mode Failure V T action
of failure tion S O D E
S Actions
Prevention Detection A date E C E A
taken
P V C T
S A
P
Sample Format
• Opposite of function
• Manner in which the assembly,sub-assembly,component
will fail to meet the design intent
• Should be written for all the primary functions and
secondary functions having ranking 1 & 2
• Assumption made - Failure mode could occur but may not
necessarily occur
• Use the following to aid in defining failure modes
– Warranty reports
– Customer complaints
Various types of
potential failure modes
Various types of
potential failure modes
Identifying SC and CC
• Example
– Hand Brake Failure – Why?
– Cable Loose – why?
– Crimping Variation in the process- Process cause
Extremely Low Failure eliminated through prevention control and failure cause is not 1
possible by design
Very High
First use of design with technical innovations or materials on a new
application. New application or change in duty cycle / operating conditions.
No product verification and/or validation experience. 8
Few existing standards and best practices, not directly applicable for this
design. Prevention controls not a reliable indicator of field performance.
New design based on similar technology and materials. New application or
change in duty cycle / operating conditions. No product verification and/or
validation experience.
High Standards, best practices, and design rules apply to the baseline design, but 7
not the innovations. Prevention controls provide limited indication of
performance
Ranking Occurrence
number
• Used to Prioritize the causes/mechanisms
• Likelihood that the cause/mechanism will occur and result
in the failure mode
• Occurrence is defined based on the number of failures
which have happened/anticipated to happen during the
design life of the product.
• Occurrence number should be ranked in the following steps
– Get the data for the causes from the warranty/customer complaint
analysis reports. Ask the question “How many times this cause has
happened before” (Remember: During the Design life)
– If data is not available, Ask the question “How many times this
failure mode has happened before”
Identifying Current
Design controls
Type of Detail of Risk Examples
Controls Controls Level
Identifying Current
Design controls
• List the controls only if it is being currently
followed during the design and development
phase
7 Pass-Fail
Testing
Proven test method for verification of functionality or validation of performance, quality, reliability and
durability; planned timing is later in the product development cycle such that test failures may result in
Moderate production delays for re-design and/or re-tooling 6 Test-to-Failure
5 Degradation
Testing
4 Pass-Fail
High Testing
Proven test method for verification of functionality or validation of performance, quality, reliability and 3 Test-to-Failure
durability; planned timing is sufficient to modify production tools before release for production.
High 2 Degradation
Testing
Very High Prior testing confirmed that failure mode or cause cannot occur, or detection methods proven to always 1 -----
detect the failure mode or failure cause.
Recommended Actions -
Guide line
• Action Priority Categories:
Identifying Actions
• Ask the following questions:
– Can we introduce a design control to prevent this
cause from happening during design
– Can we introduce a design control to detect this cause
if it happens to confirm the occurrence and initiate
corrective actions
Identifying Actions
• To Reduce Occurrence numbers consider the actions
– Introduction of simulation techniques during design
– Finite element analysis during design
– Solid modelling techniques
– Computer aided design to eliminate errors
Identifying Actions
Identifying Actions
• Example of Actions:
• This will make the DVP complete and will list all the
checks/tests that needs to be done for the prototype part
• Key Inputs:
- Product Structure Tree Diagram
- Boundary Diagram
- Interaction Matrix
- Regulatory requirement review
- Item Function Work Sheet
- P – Diagram
- VOC
- Earlier Experience
• Controls:
- Prevention of Cause of the Failure Mode, Detection of
Causes, Detection of Failure Mode to be addressed in
detail
• RPN:
- There is no cut off value above which the action must be
taken or below which there is no need of action
- Min RPN is 1 and Max is 1000
- Two approaches in RPN (based on Failure Mode and
based on Causes)
Retention of FMEA