_later_ analysis asp.net bibliothèque biztalk cmmi college crash decision_making design discover failure fmea gst-vpc ideas info it itek lcpo_course_idea lookup08 management method mode projectmanagement qa quality sixsigma thinking work

My tags:

From Wikipedia, the free encyclopedia

This article needs additional citations for verification. Please help improve this article by adding reliable references (ideally, using inline citations). Unsourced material may be challenged and removed. (September 2008)

A failure modes and effects analysis (FMEA) is a procedure for analysis of potential failure modes within a system for classification by severity or determination of the effect of failures on the system. It is widely used in manufacturing industries in various phases of the product life cycle and is now increasingly finding use in the service industry. Failure modes are any errors or defects in a process, design, or item, especially those that affect the customer, and can be potential or actual. Effects analysis refers to studying the consequences of those failures.

Contents 1 Basic terms 2 History 3 Implementation 4 Using FMEA when designing 4.1 The pre-work 4.2 Step 1: Severity 4.3 Step 2: Occurrence 4.4 Step 3: Detection 4.5 Risk Priority Numbers 5 Timing of FMEA 6 Uses of FMEA 7 Advantages 8 Limitations 9 Software 10 Types of FMEA 11 See also 12 Notes 13 External links

[edit] Basic terms

Failure mode: "The manner by which a failure is observed; it generally describes the way the failure occurs."
Failure effect: Immediate consequences of a failure on operation, function or functionality, or status of some item
Indenture levels: An identifier for item complexity. Complexity increases as levels are closer to one.
Local effect: The Failure effect as it applies to the item under analysis.
Next higher level effect: The Failure effect as it applies at the next higher indenture level.
End effect: The failure effect at the highest indenture level or total system.
Failure cause: Defects in design, process, quality, or part application, which are the underlying cause of the failure or which initiate a process which leads to failure.
Severity: "The consequences of a failure mode. Severity considers the worst potential consequence of a failure, determined by the degree of injury, property damage, or system damage that could ultimately occur."
^[1]

[edit] History

Learning from each failure is both costly and time consuming, and FMEA is a more systematic method of studying failure. As such, it is considered better to first conduct some thought experiments.

FMEA was formally introduced in the late 1940s for military usage by the US Armed Forces.^[2] Later it was used for aerospace/rocket development to avoid errors in small sample sizes of costly rocket technology. An example of this is the Apollo Space program. The primary push came during the 1960s, while developing the means to put a man on the moon and return him safely to earth. In the late 1970s the Ford Motor Company introduced FMEA to the automotive industry for safety and regulatory consideration after the Pinto affair. They also used it to improve production and design.

Although initially developed by the military, FMEA methodology is now extensively used in a variety of industries including semiconductor processing, food service, plastics, software, and healthcare.^[3][4] It is integrated into Advanced Product Quality Planning (APQP) to provide primary risk mitigation tools and timing in the prevention strategy, in both design and process formats. The Automotive Industry Action Group (AIAG) requires the use of FMEA in the automotive APQP process and publishes a detailed manual on how to apply the method.^[5] Each potential cause must be considered for its effect on the product or process and, based on the risk, actions are determined and risks revisited after actions are complete. Toyota has taken this one step further with its Design Review Based on Failure Mode (DRBFM) approach. The method is now supported by the American Society for Quality which provides detailed guides on applying the method.^[6]

[edit] Implementation

In FMEA, failures are prioritized according to how serious their consequences are, how frequently they occur and how easily they can be detected. An FMEA also documents current knowledge and actions about the risks of failures for use in continuous improvement. FMEA is used during the design stage with an aim to avoid future failures. Later it is used for process control, before and during ongoing operation of the process. Ideally, FMEA begins during the earliest conceptual stages of design and continues throughout the life of the product or service.

The purpose of the FMEA is to take actions to eliminate or reduce failures, starting with the highest-priority ones. It may be used to evaluate risk management priorities for mitigating known threat vulnerabilities. FMEA helps select remedial actions that reduce cumulative impacts of life-cycle consequences (risks) from a systems failure (fault).

It is used in many formal quality systems such as QS-9000 or ISO/TS 16949.

[edit] Using FMEA when designing

FMEA can provide an analytical approach, when dealing with potential failure modes and their associated causes. When considering possible failures in a design – like safety, cost, performance, quality and reliability – an engineer can get a lot of information about how to alter the development/manufacturing process, in order to avoid these failures. FMEA provides an easy tool to determine which risk has the greatest concern, and therefore an action is needed to prevent a problem before it arises. The development of these specifications will ensure the product will meet the defined requirements.

[edit] The pre-work

The process for conducting an FMEA is straightforward. It is developed in three main phases, in which appropriate actions need to be defined. But before starting with a FMEA, it is important to complete some pre-work to confirm that robustness and past history are included in the analysis.

A robustness analysis can be obtained from Interface Matrices, Boundary Diagrams and Parameter Diagrams. A lot of failures are due to noise factors and shared interfaces with other parts and/or systems, because engineers tend to focus on what they control directly.

To start it is necessary to describe the system and its function. A good understanding simplifies the further analysis. This way an engineer can see which uses of the system are desirable and which are not. It is important to consider both intentional and unintentional uses! Unintentional uses are a form of hostile environment.

Next a block diagram of the system needs to be created. This diagram gives an overview of the major components or process steps and how they are related. These are called logical relations around which the FMEA can be developed. It is useful to create a coding system to identify the different system elements. The block diagram should always be included with the FMEA.

Before starting the actual FMEA, a worksheet needs to be created, which contains the important information about the system, such as the revision date or the names of the components. On this worksheet all the items or functions of the subject should be listed in a logical manner, based on the block diagram.

Example FMEA Worksheet

Function	Failure mode	Effects	S (severity rating)	Cause(s)	O (occurrence rating)	Current controls	D (detection rating)	CRIT (critical characteristic	RPN (risk priority number)	Recommended actions	Responsibility and target completion date	Action taken
Fill tub	High level sensor never trips	Liquid spills on customer floor	8	level sensor failed level sensor disconnected	2	Fill timeout based on time to fill to low level sensor	5	N	80	Perform cost analysis of adding additional sensor halfway between low and high level sensors	Jane Doe 10-Oct-2010

[edit] Step 1: Severity

Determine all failure modes based on the functional requirements and their effects. Examples of failure modes are: Electrical short-circuiting, corrosion or deformation. It is important to note that a failure mode in one component can lead to a failure mode in another component. Therefore each failure mode should be listed in technical terms and for function. Hereafter the ultimate effect of each failure mode needs to be considered. A failure effect is defined as the result of a failure mode on the function of the system as perceived by the user. In this way it is convenient to write these effects down in terms of what the user might see or experience. Examples of failure effects are: degraded performance, noise or even injury to a user. Each effect is given a severity number (S) from 1 (no danger) to 10 (critical). These numbers help an engineer to prioritize the failure modes and their effects. If the severity of an effect has a number 9 or 10, actions are considered to change the design by eliminating the failure mode, if possible, or protecting the user from the effect. A severity rating of 9 or 10 is generally reserved for those effects which would cause injury to a user or otherwise result in mitigation.

[edit] Step 2: Occurrence

In this step it is necessary to look at the cause of a failure and how many times it occurs. This can be done by looking at similar products or processes and the failures that have been documented for them. A failure cause is looked upon as a design weakness. All the potential causes for a failure mode should be identified and documented. Again this should be in technical terms. Examples of causes are: erroneous algorithms, excessive voltage or improper operating conditions. A failure mode is given an occurrence ranking (O), again 1–10. Actions need to be determined if the occurrence is high (meaning >4 for non safety failure modes and >1 when the severity-number from step 1 is 9 or 10). This step is called the detailed development section of the FMEA process. Occurrence also can be defined as %. If a non-safety issue happened less than 1%, we can give 1 to it. It is based on your product and customer specification.

[edit] Step 3: Detection

When appropriate actions are determined, it is necessary to test their efficiency. Also a design verification is needed. The proper inspection methods need to be chosen. First, an engineer should look at the current controls of the system, that prevent failure modes from occurring or which detect the failure before it reaches the customer. Hereafter one should identify testing, analysis, monitoring and other techniques that can be or have been used on similar systems to detect failures. From these controls an engineer can learn how likely it is for a failure to be identified or detected. Each combination from the previous 2 steps receives a detection number (D). This ranks the ability of planned tests and inspections to remove defects or detect failure modes in time. The assigned detection number measures the risk that the failure will escape detection. A high detection number indicates that the chances are high that the failure will escape detection, or in other words, that the chances of detection are low.

After these 3 basic steps, Risk Priority Numbers (RPN) are calculated.

[edit] Risk Priority Numbers

RPN do not play an important part in the choice of an action against failure modes. They are more threshold values in the evaluation of these actions.

After ranking the severity, occurrence and detectability the RPN can be easily calculated by multiplying these 3 numbers: RPN = S x O x D

This has to be done for the entire process and/or design. Once this is done it is easy to determine the areas of greatest concern. The failure modes that have the highest RPN should be given the highest priority for corrective action. This means it is not always the failure modes with the highest severity numbers that should be treated first. There could be less severe failures, but which occur more often and are less detectable.

After these values are allocated, recommended actions with targets, responsibility and dates of implementation are noted. These actions can include specific inspection, testing or quality procedures, redesign (such as selection of new components), adding more redundancy and limiting environmental stresses or operating range. Once the actions have been implemented in the design/process, the new RPN should be checked, to confirm the improvements. These tests are often put in graphs, for easy visualisation. Whenever a design or a process changes, an FMEA should be updated.

A few logical but important thoughts come in mind:

• Try to eliminate the failure mode (some failures are more preventable than others)
• Minimize the severity of the failure
• Reduce the occurrence of the failure mode
• Improve the detection

[edit] Timing of FMEA

The FMEA should be updated whenever:

• At the beginning of a cycle (new product/process)
• Changes are made to the operating conditions
• A change is made in the design
• New regulations are instituted
• Customer feedback indicates a problem

[edit] Uses of FMEA

• Development of system requirements that minimize the likelihood of failures.
• Development of methods to design and test systems to ensure that the failures have been eliminated.
• Evaluation of the requirements of the customer to ensure that those do not give rise to potential failures.
• Identification of certain design characteristics that contribute to failures, and minimize or eliminate those effects.
• Tracking and managing potential risks in the design. This helps avoid the same failures in future projects.
• Ensuring that any failure that could occur will not injure the customer or seriously impact a system.

[edit] Advantages

• Improve the quality, reliability and safety of a product/process
• Improve company image and competitiveness
• Increase user satisfaction
• Reduce system development timing and cost
• Collect information to reduce future failures, capture engineering knowledge
• Reduce the potential for warranty concerns
• Early identification and elimination of potential failure modes
• Emphasis problem prevention
• Minimize late changes and associated cost
• Catalyst for teamwork and idea exchange between functions

[edit] Limitations

Since FMEA is effectively dependent on the members of the committee which examines product failures, it is limited by their experience of previous failures. If a failure mode cannot be identified, then external help is needed from consultants who are aware of the many different types of product failure. FMEA is thus part of a larger system of quality control, where documentation is vital to implementation. General texts and detailed publications are available in forensic engineering and failure analysis. It is a general requirement of many specific national and international standards that FMEA is used in evaluating product integrity. If used as a top-down tool, FMEA may only identify major failure modes in a system. Fault tree analysis (FTA) is better suited for "top-down" analysis. When used as a "bottom-up" tool FMEA can augment or complement FTA and identify many more causes and failure modes resulting in top-level symptoms. It is not able to discover complex failure modes involving multiple failures within a subsystem, or to report expected failure intervals of particular failure modes up to the upper level subsystem or system.^{[citation needed]}

Additionally, the multiplication of the severity, occurrence and detection rankings may result in rank reversals, where a less serious failure mode receives a higher RPN than a more serious failure mode. The reason for this is that the rankings are ordinal scale numbers, and multiplication is not a valid operation on them. The ordinal rankings only say that one ranking is better or worse than another, but not by how much. For instance, a ranking of "2" may not be twice as bad as a ranking of "1," or an "8" may not be twice as bad as a "4," but multiplication treats them as though they are. See Level of measurement for further discussion.

[edit] Software

The usage of software will improve the documentation process of FMEA. A number of software packages exist. When selecting the software package, it is important to choose one that is easy to learn and promotes consistent updating of the documentation. It is not necessary to spend a lot of money to have an effective, user-friendly system. Some FMEA software companies provide free upgrades, free support, and software with unlimited licenses. This is especially helpful in ensuring the long-term acceptance, understanding, and implementation of FMEAs. FMEA is applicable to all engineering process.

[edit] Types of FMEA

• Process: analysis of manufacturing and assembly processes
• Design: analysis of products prior to production
• Concept: analysis of systems or subsystems in the early design concept stages
• Equipment: analysis of machinery and equipment design before purchase
• Service: analysis of service industry processes before they are released to impact the customer
• System: analysis of the global system functions
• Software: analysis of the software functions

[edit] See also

Failure Mode, Effects, and Criticality Analysis (FMECA) Causal layered analysis Futures techniques Failure mode Failure rate Forensic engineering High availability Process decision program chart

Hazard Analysis and Critical Control Points‎ Quality control Reliability engineering Risk assessment Safety engineering Six sigma DRBFM Fault tree analysis

[edit] Notes

[edit] External links

• FMEA and FMECA Information
• FMEA Info Centre
• Failure Aalysis of FMEA Article
• Expanded FMEA (EFMEA) Article