Professional Documents
Culture Documents
FMEA
• 1990’s:
Large corporations are, in turn, pressing suppliers to adopt
the method.
• Failure Mode
- Ways in which the component/system/process could fail
- Team poses the question: “How could this part, system or process fail?”
• Failure Effect
- the effect a particular defect will have on the customer
- Team poses the question: “What does the customer experience as a results
of this failure mode?”
• Severity
- an assessment of the seriousness of the failure on the customer (may be
internal or external customers)
- 1 indicates minor nuisance; 10 indicates severe consequence
FMEA Terminology
• Failure Cause
- something that can be controlled (X) that describes how the failure mode
could have occurred
- important because it points the way to preventive/ corrective action
• Occurrence
- An assessment of the frequency with which the failure occurs
- 1 indicates low probability, 10 indicates near certainty of occurrence
• Detection
- An assessment of the likelihood (or probability) that your current controls will
detect when the “X” fails or when the failure mode occurs
- 1 indicates very high probability of detection; 10 indicates low probability of
detection
FMEA Terminology
Customer:
persons and organizations that are affected by the process.
• Failure:
any malfunction, defect or error that causes the process to not perform
its
intended function(s) or meet requirements satisfactorily.
FMEA Terminology
• Failure Mode:
the appearance, manner or form in which the process failure
FMEA Terminology
manifests itself. (Short circuit or handling damage)
- potential causes
+ Customer Requirements
FMEA - Origin and Emerging of Failures
13
FMEA - Why FMEA ?
FMEA helps
to solve the
Failures With
low Cost!
14
FMEA - Types of FMEA
The following documents should be available for discussion and use in the FMEA :
• Specifications - Target and Product • Process Layout, Product Quality Plan - PQP
The depth of detail for the FMEA and selection of the objects to be
analyzed must be done by the Core Team during the preparatory
phase and will be reviewed and ratified by the FMEA team.
FMEA - System Structuring - Col. 2
2. Component or process
Examples
Comments :
- The System FMEA covers all important functions, operating condition and
conditions of system components on the basis of the system design specification,
starting from a black-box point of view.
- The Design FMEA covers all important end functions and operating conditions
of components, on the basis of the component design specification, starting
from the initial prototypes.
3. Functions Examples
System FMEA Design FMEA Process FMEA
Moronic Starter Grinding armature shaft
Object: Starter Object: Armature Shaft Object: Grinding Process step
Functions Component Functions Characteristics
- Enable cold start - Receive lateral force - Maintain dim. Tolerances
- Supply torque - Position stator core - Maintain tolerance for
cylindricity
Operating States
- Starting
- Driving
- Parked
FMEA - Failure Analysis - Mode - Col. 4
Definition : Failure mode is the improper function or the type and way
required function or a characteristic could not be fulfilled.
Comments:
- The System FMEA examines all potential malfunctions and functional limitations that
result from the function of the system components and are functionally described.
- The Design FMEA examines all potential malfunctions and failure modes that result
from component functions and are described as a physical quantity. Design for
manufacturing must also be considered.
- The Process FMEA examines all potential process failures that result from the
required process functions and part characteristics and are described as a deviation.
FMEA - Failure Analysis - Mode - Col. 4
4. Failure mode Examples
- Do not lower the ranking unless there are reasons for this.
Note : These Rules are applicable to ranking of S, O, & D (Col. 10,11 & 12)
FMEA - Failure Assessment - Severity - Col. 10
Definition : The ranking for ‚S‘ - Severity, reflects the significance of the
effects of the failure mode on the end customer.
Extremely serious failure, which affects safety and/or violates legal requirements, 10
without warning.
Extremely serious failure, which probably affects safety and/or violates legal 9
requirements, with warning, or leads to a conked-out vehicle.
Serious failure, loss of primary functions, e.g. vehicle is conked-out. 8
The failure is insignificant. The customer is only slightly bothered, and will probably 3
only notice slight interference, can be noticed by the average
driver.
It is unlikely, that the failure could have a noticeable effect on the behavior of the 2
vehicle or system. Only noticeable by experts/ experienced drivers.
No Effect 1
31
FMEA - Failure Assessment - Col. 6
Definition : Failure causes = causes and conditions that can lead to the failure
mode being considered.
Comments : • The System FMEA (Field and layout) considers implemented actions
that minimize the risk of system layout mistakes or avoid or limit the
effects of these mistakes.
Definition : The O ranking reflects the probability that the failure mode, as a
result of the failure cause being considered, will occur at the
customer/user, without being discovered beforehand.
Comments : - To avoid double ranking, it is assumed that the failure mode and
cause have not been detected before the customer accepts the
product.
- Implemented actions that prevent the failure cause are assumed
effective and are considered when O is ranked.
- The failure rates (e.g. - rates, ppm) are based on the number of
failures that are expected within the required lifetime of the
product.
- Dependence on operating time (h), driving distance (km), number
of cycles, process capability (cpk), etc. must be considered.
FMEA - Risk Assessment - Occurrence - Col. 11
Process FMEA
General assessment criteria Possible ppm Cpk Ranking Application-
failure Points specific -
rate assessment
criteria
Definition : Failure detection = Test activities or symptoms that are suitable for
timely detection of a failure mode or cause.
Comments : - In the System FMEA (Layout), these are test activities and validation
done until the system release.
- In the System FMEA (Field), these are signs and symptoms that are
suitable for timely detection of the failure mode or cause.
- In the Design FMEA, these are tests and validation, as well as other
methods of detecting failures, until the product release.
- In the Process FMEA, these are all tests and possibilities of detecting
failures, until delivery to the customer.
Signs
- Warning lamp display - Endurance testing - Measurement and
- Acoustic signal - Climatic testing tests at the work
- Fault memory readout - Initial sample testing station
during service (customer) - Process & visual tests
- Vibration testing - In- process and final
Symptoms - Testing of individual testing
- Loud noises characteristics - Quality/ reliability
- Unsteady engine running testing
- Increased fuel consumption - Technology analysis
- 100 % testing
Layout - Random sample
- Vehicle testing testing
- Simulation - Product audit
- Summer & winter testing - System audit
FMEA - Risk Assessment - Detection - Col. 12
Definition :The ‚D‘ ranking reflects the probability that the failure mode or cause is
detected before the product arrives at the customer or that the failure is
detected in the field by an implemented detection action and displayed
to the operator (e.g. driver).
Design FMEA
General assessment criteria Ranking Application –
Points Specific
assessment
area
Unlikely. It is impossible or improbable that the failure mode/cause will be 10
discovered during the development phase by testing or analysis activity
Very low. The probability is very low that the failure mode/cause will be 9
discovered during the development phase by testing or analysis 8
activities.
Low. The probability is low that the failure mode/cause will be discovered 7
during the development phase by testing or analysis activities. 6
Medium. The probability is moderate that the failure mode/cause will be 5
discovered during the development phase by testing or analysis activities. 4
High. The probability is high that the failure mode/cause will be discovered 3
during the development phase by testing or analysis activities. 2
Very high. It is certain that the failure mode/cause will be discovered during 1
the development phase by testing or analysis activities.
43
FMEA - Risk Assessment - Detection - Col. 12
Process FMEA
Improbable. 10
The failure will not or cannot be detected.
Very low. 90% 9
The probability of detecting failure is very low.
Low. 98% 8
The probability of detecting failure is low. 7
Medium. 99,70% 6
The probability of detecting failure is moderate. 5
4
High. 99,90% 3
The probability of detecting failure is high. 2
Very High. 99,99% 1
The probability of detecting failure is very high.
FMEA - Risk Assessment - RPN - Col. 13
Definition :The Risk Priority Number - RPN - is the product of the individual rankings
RPN = S x O x D
-O>3
-S>8
FMEA - Quality Improvement Actions - Col. 14
General Guidelines :
System FMEA
Design FMEA
• For high O-rankings, actions have to be implemented to ensure achievement
of the defined quality target for the product at SOP. This means that
generally O = 2 to 3 should be achieved. The target in future is O = 1 !
• Means of detection have to be performed to ensure achieving quality targets.
Process FMEA
• For safety parts, the target is O = 1. If this cannot be achieved, then suitable
means of detection must be installed to ensure that no defective parts are
delivered to the customer.
• If the probability of failure occurrence is high, then actions have to be
implemented to achieve the quality target. Generally, this requires controlled
processes, i.e. Cpk > 1,33 - 1,67 or O = 1 or 2
FMEA - Quality Improvement Actions - Col. 14
Comments : - During this phase, the team should look for any imaginable improvement
ideas.
- FMEA is a creative technique and a helpful tool for this .
- Failure prevention actions always have priority.
- Failure detection is usually expensive and does not improve quality.
FMEA - Quality Improvement Actions - Col. 14
Comments : - Actions to prevent the failure mode or cause have to be checked for
effectiveness.
- Actions to reduce S, O and D have to be assessed according to the FMEA
ranking tables.
- Actions to reduce S, O and D might be possible to be combined.
- Costs and deadlines have to be determined for the lowest risk numbers.
- Select the best-suited actions and, after agreeing to implement them, enter
the expected ranking in column 14 (in parenthesis).
- Responsibility (R:) and implementation date (I:) must be entered.
FMEA - Quality Improvement Actions - Col. 14
Definition : Actions that have been selected and agreed upon must be implemented
according to schedule.
Comments :- After implementation of the action, the new rating for ‚O‘ and ‚D‘ is
compared with the old estimated rating and the accepted ratings
and RPN are entered in the respective columns (Col. 11,12,13).
- The current, applicable rating is always written without parenthesis.
- The original rating remains for comparison and is written in
rectangular brackets [ ].
FMEA - Management Reporting
50
FMEA - Efficiency of FMEA
Efficiency of FMEA
Mistakes of FMEA
Incomplete and/or Pseudo FMEA,
Inadequate FMEA - not all Failure modes considered & too few Failure
causes listed,
Actions for Failure prevention not considered,
Description of Failure Modes, effects, causes, prevention & detection
actions are inadequate and/or ambiguous,
Failure mode, effect, cause mixed-up,
Product function (Target requirements) and Process function
(Drawing requirements) mixed-up,
Too long time taken for brain-storming for Causes and actions,
Casual involvement of Team members in discussions.
FMEA - Additional Information
FMEA is
- A systematic method for early, analysis of functional failure,
- Applicable to SYSTEMS, PRODUCTS and PROCESSES,
- A structured method for farsighted, all-embracing investigation of all
potential failure modes, failure causes and their effects,
- A method of qualitative failure evaluation and revealing risks of failure,
- A method for avoiding or reducing risks of failure by introducing suitable
improvement measures.
Conclusion :
- FMEA is an up-to-date & effective technique for failure prevention and
reducing development cost and time, which leads to customer satisfaction.
Thank You
55