Bitruncated cubic honeycomb: Difference between revisions

From formulasearchengine
Jump to navigation Jump to search
en>Tomruen
No edit summary
en>Tomruen
5-polytope
 
Line 1: Line 1:
'''Failure mode, effects and criticality analysis (FMECA)''' is an extension of [[failure mode and effects analysis]] (FMEA).
Alyson Meagher is the title her parents   [http://koreanyelp.com/index.php?document_srl=1798&mid=SchoolNews love psychic readings] clairvoyance ([http://myfusionprofits.com/groups/find-out-about-self-improvement-tips-here/ from this source]) gave her but she doesn't like when people use her full name. She is truly fond of caving but she doesn't have the time recently. I am an invoicing officer and I'll be promoted soon. My spouse and I reside in Mississippi but now I'm considering other options.<br><br>Feel free to surf to my page: accurate psychic predictions ([http://gcjcteam.org/index.php?mid=etc_video&document_srl=696611&sort_index=regdate&order_type=desc http://gcjcteam.org/index.php?mid=etc_video&document_srl=696611&sort_index=regdate&order_type=desc])
 
FMEA is a bottom-up, [[inductive reasoning|inductive]] analytical method which may be performed at either the functional or piece-part level. FMECA extends FMEA by including a ''criticality analysis'', which is used to chart the [[probability]] of failure modes against the severity of their consequences. The result highlights failure modes with relatively high probability and severity of consequences, allowing remedial effort to be directed where it will produce the greatest value. FMECA tends to be preferred over FMEA in [[Outer space|space]] and [[NATO|North Atlantic Treaty Organization]] (NATO) [[military]] applications, while various forms of FMEA predominate in other industries.
 
==History==
FMECA was originally developed in the 1940s by the [[United States armed forces|U.S military]], which published MIL&ndash;P&ndash;1629 in 1949.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Procedures for Performing a Failure Mode, Effects and Criticality Analysis
|    section =
|  sectionurl =
|    version =
|   publisher = [[United States Department of military|U.S. Department of Defense]]
|        year = 1949
|        url =
|      format =
|          id = MIL&ndash;P&ndash;1629
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> By the early 1960s, contractors for the [[National Aeronautics and Space Administration|U.S. National Aeronautics and Space Administration]] (NASA) were using variations of FMECA under a variety of names.<ref>{{cite manual
|        last = Neal
|      first = R.A.
| author-link = R.A. Neal
|  coauthors =
|      title = Modes of Failure Analysis Summary for the Nerva B-2 Reactor
|    section =
|  sectionurl =
|    version =
|  publisher = Westinghouse Electric Corporation Astronuclear Laboratory
|        year = 1962
|        url = http://hdl.handle.net/2060/19760069385
|      format = pdf
|          id = WANL&ndash;TNR&ndash;042
|  accessdate = 2010-03-13
|      quote =
|        page =
|      pages =
|        ref =
}}</ref><ref>{{cite manual
|        last = Dill
|      first = Robert
| author-link = Robert P. Dill
|  coauthors = et al.
|      title = State of the Art Reliability Estimate of Saturn V Propulsion Systems
|    section =
|  sectionurl =
|    version =
|  publisher = General Electric Company
|        year = 1963
|        url = http://hdl.handle.net/2060/19930075105
|      format = pdf
|          id = RM&nbsp;63TMP&ndash;22
|  accessdate = 2010-03-13
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> In 1966 NASA released its FMECA procedure for use on the [[Apollo program]].<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Procedure for Failure Mode, Effects and Criticality Analysis (FMECA)
|    section =
|  sectionurl =
|    version =
|  publisher = National Aeronautics and Space Administration
|        year = 1966
|        url = http://hdl.handle.net/2060/19700076494
|      format = pdf
|          id = RA&ndash;006&ndash;013&ndash;1A
|  accessdate = 2010-03-13
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> FMECA was subsequently used on other NASA programs including [[Viking program|Viking]], [[Voyager program|Voyager]], [[Magellan probe|Magellan]], and [[Galileo (spacecraft)|Galileo]].<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Failure Modes, Effects, and Criticality Analysis (FMECA)
|    section =
|  sectionurl =
|    version =
|  publisher = National Aeronautics and Space Administration JPL
|        year =
|        url =
http://www.klabs.org/DEI/References/design_guidelines/analysis_series/1307.pdf
|      format = pdf
|          id = PD&ndash;AD&ndash;1307
|  accessdate = 2010-03-13
|      quote =
|        page =
|      pages =
|        ref =
}}</ref>
Possibly because MIL&ndash;P&ndash;1629 was replaced by MIL&ndash;STD&ndash;1629&nbsp;(SHIPS) in 1974, development of FMECA is sometimes incorrectly attributed to NASA.<ref>{{cite manual
|        last = Borgovini
|      first = Robert
| author-link = Robert Borgovini
|  coauthors = Pemberton, S., Rossi, M.
|      title = Failure Mode, Effects and Criticality Analysis (FMECA)
|    section =
|  sectionurl =
|    version = B
|  publisher = Reliability Analysis Center
|        year = 1993
|        url = http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA278508
|      format = pdf
|          id = CRTA&ndash;FMECA
|  accessdate = 2010-03-03
|      quote =
|        page = 5
|      pages =
|        ref =
}}</ref>
At the same time as the space program developments, use of FMEA and FMECA was already
spreading to civil aviation. In 1967 the [[SAE International|Society for Automotive
Engineers]] released the first civil publication to address FMECA.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Design Analysis Procedure For Failure Modes, Effects and Criticality Analysis (FMECA)  
|    section =
|  sectionurl =
|    version =
|  publisher = Society for Automotive Engineers
|        year = 1967
|        url =
|      format =
|          id = ARP926
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> The civil aviation industry now tends to use a combination of FMEA and [[Fault Tree Analysis]] in accordance with SAE [[ARP4761]] instead of FMECA, though some helicopter manufacturers continue to use FMECA for civil [[rotorcraft]].
 
Ford Motor Company began using FMEA in the 1970s after problems experienced with its [[Ford Pinto|Pinto]]
model, and by the 1980s FMEA was gaining broad use in the automotive industry. In Europe,
the International Electrotechnical Commission published IEC&nbsp;812 (now IEC&nbsp;60812) in 1985, addressing both FMEA and FMECA for general use.<ref>{{cite manual
|        last = 56
|      first =
| author-link =
|  coauthors =
|      title = Analysis techniques for system reliability – Procedure for failure mode and effects analysis (FMEA)
|    section =
|  sectionurl =
|    version =
|  publisher = International Electrotechnical Commission
|        year = 1985
|        url = http://webstore.iec.ch/p-preview/info_iec60812%7Bed1.0%7Den_d.img.pdf
|      format = pdf
|          id = IEC&nbsp;812
|  accessdate = 2013-08-08
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> The British Standards Institute published BS&nbsp;5760&ndash;5 in 1991 for the same purpose.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Reliability of Systems, Equipment and Components Part 5: Guide to Failure Modes, Effects and Criticality Analysis (FMEA and FMECA)
|    section =
|  sectionurl =
|    version =
|  publisher = British Standards Institute
|        year = 1991
|        url =
|      format =
|          id = BS&nbsp;5760&ndash;5
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref>
 
In 1980, MIL&ndash;STD&ndash;1629A replaced both MIL&ndash;STD&ndash;1629 and the 1977 aeronautical FMECA standard MIL&ndash;STD&ndash;2070.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Procedures for Performing a Failure Mode, Effects and Criticaility Analysis
|    section =
|  sectionurl =
|    version = A
|  publisher = [[United States Department of Defense|U.S. Department of Defense]]
|        year = 1980
|        url = https://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=37027
|      format = pdf
|          id = MIL&ndash;HDBK&ndash;1629A
|  accessdate = 2010-03-14
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> MIL&ndash;STD&ndash;1629A was canceled without replacement in 1998, but nonetheless remains in wide use for military and space applications today.<ref>{{cite manual
|        last =
|      first =
| author-link = Air Force Research Laboratory
|  coauthors =
|      title = Electronic Reliability Design Handbook
|    section = 7.8 Failure Mode and Effects Analysis (FMEA)
|  sectionurl =
|    version = B
|  publisher = [[United States Department of Defense|U.S. Department of Defense]]
|        year = 1998
|        url = https://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=54022
|      format = pdf
|          id = MIL&ndash;HDBK&ndash;338B
|  accessdate = 2010-03-13
|      quote =
|        page =
|      pages =
|        ref =
}}</ref>
 
==Methodology==
Slight differences are found between the various FMECA standards. By RAC CRTA&ndash;FMECA, the FMECA analysis procedure typically consists of the following logical steps:
* Define the system
* Define ground rules and assumptions in order to help drive the design
* Construct system block diagrams
* Identify failure modes (piece part level or functional)
* Analyze failure effects/causes
* Feed results back into design process
* Classify the failure effects by severity
* Perform criticality calculations
* Rank failure mode criticality
* Determine critical items
* Feed results back into design process
* Identify the means of failure detection, isolation and compensation
* Perform maintainability analysis
* Document the analysis, summarize uncorrectable design areas, identify special controls necessary to reduce failure risk
* Make recommendations
* Follow up on corrective action implementation/effectiveness
 
FMECA may be performed at the functional or piece part level. Functional FMECA considers the effects of failure at the functional block level, such as a power supply or an amplifier.
Piece part FMECA considers the effects of individual component failures, such as resistors,
transistors, microcircuits, or valves. A piece part FMECA requires far more effort, but provides the benefit of better estimates of probabilities of occurrence. However, Functional FMEAs can be performed much earlier, may help to better structure the complete risk assessment and provide other type of insight in mitigation options. The analyses are complementary.
 
The criticality analysis may be quantitative or qualitative, depending on the availability of supporting part failure data.
 
===System definition===
In this step, the major system to be analyzed is defined and partitioned into an indentured
hierarchy such as systems, subsystems or equipment, units or subassemblies, and piece parts. Functional descriptions are created for the systems and allocated to the subsystems,
covering all operational modes and mission phases.
 
===Ground rules and assumptions===
Before detailed analysis takes place, ground rules and assumptions are usually defined and
agreed to. This might include, for example:
* Standardized mission profile with specific fixed duration mission phases
* Sources for failure rate and failure mode data
* Fault detection coverage that system built-in test will realize
* Whether the analysis will be functional or piece part
* Criteria to be considered (mission abort, safety, maintenance, etc.)
* System for uniquely identifying parts or functions
* Severity category definitions
 
===Block diagrams===
Next, the systems and subsystems are depicted in functional block diagrams. Reliability
block diagrams or fault trees are usually constructed at the same time. These diagrams are
used to trace information flow at different levels of system hierarchy, identify critical
paths and interfaces, and identify the higher level effects of lower level failures.
 
===Failure mode identification===
For each piece part or each function covered by the analysis, a complete list of failure
modes is developed. For functional FMECA, typical failure modes include:
* Untimely operation
* Failure to operate when required
* Loss of output
* Intermittent output
* Erroneous output (given the current condition)
* Invalid output (for any condition)
 
For piece part FMECA, failure mode data may be obtained from databases such as RAC
FMD&ndash;91<ref>{{cite manual
|        last = Chandler
|      first = Gregory
| author-link = Gregory Chandler
|  coauthors = Denson, W., Rossi, M., Wanner, R.
|      title = Failure Mode/Mechanism Distributions
|    section =
|  sectionurl =
|    version =
|  publisher = Reliability Analysis Center
|        year = 1991
|        url = http://handle.dtic.mil/100.2/ADA259655
|      format = pdf
|          id = FMD&ndash;91
|  accessdate = 2010-03-14
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> or RAC FMD&ndash;97.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Failure Mode/Mechanism Distributions
|    section =
|  sectionurl =
|    version =
|  publisher = Reliability Analysis Center
|        year = 1997
|        url = http://infostore.saiglobal.com/store/Details.aspx?ProductID=554377
|      format =
|          id = FMD&ndash;97
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref> These databases provide not only the failure modes, but also the failure mode
ratios. For example:  
{| class="wikitable" style="margin: 1em auto 1em auto"
|+ '''Device Failure Modes and Failure Mode Ratios (FMD&ndash;91) '''
! Device Type || Failure Mode || Ratio (α)
|-
| Relay  || Fails to trip || .55
|-
|        || Spurious trip || .26
|-
|        || Short        || .19
|-
| Resistor, Composition || Parameter change || .66
|-
|                        || Open            || .31
|-
|                        || Short            || .03
|}
Each function or piece part is then listed in matrix form with one row for each failure
mode. Because FMECA usually involves very large data sets, a unique identifier must be assigned to each item (function or piece part), and to each failure mode of each item.
 
===Failure effects analysis===
Failure effects are determined and entered for each row of the FMECA matrix, considering the
criteria identified in the ground rules. Effects are separately described for the local, next higher, and end (system) levels. System level effects may include:
* System failure
* Degraded operation
* System status failure
* No immediate effect
The failure effect categories used at various hierarchical levels are tailored by the
analyst using engineering judgment.
 
===Severity classification===
Severity classification is assigned for each failure mode of each unique item and entered on the FMECA matrix, based upon system level consequences. A small set of classifications,
usually having 3 to 10 severity levels, is used. For example, When prepared using MIL&ndash;STD&ndash;1629A, failure or mishap severity classification normally follows MIL&ndash;STD&ndash;882.<ref>{{cite manual
|        last =
|      first =
| author-link = Air Force Materiel Command Safety Office
|  coauthors =
|      title = Standard Practice for System Safety
|    section =
|  sectionurl =
|    version = D
|  publisher = [[United States Department of Defense|U.S. Department of Defense]]
|        year = 1998
|        url =
https://assist.daps.dla.mil/quicksearch/basic_profile.cfm?ident_number=36027
|      format = pdf
|          id = MIL&ndash;HDBK&ndash;882D
|  accessdate = 2010-03-14
|      quote =
|        page =
|      pages =
|        ref =
}}</ref>
{| class="wikitable" style="margin: 1em auto 1em auto"
|+ '''Mishap Severity Categories (MIL&ndash;STD&ndash;882)'''
! Category || Description || Criteria
|-
| I  || Catastrophic || Could result in death, permanent total disability, loss exceeding $1M, or irreversible severe environmental damage that violates law or regulation.
|-
| II  || Critical || Could result in permanent partial disability, injuries or occupational illness that may result in hospitalization of at least three personnel, loss exceeding $200K but less than $1M, or reversible environmental damage causing a violation of law or regulation.
|-
| III || Marginal || Could result in injury or occupational illness resulting in one or more
lost work days(s), lossexceeding $10K but less than $200K, or mitigatible environmental damage without violation of law or regulation where restoration activities can be accomplished.
|-
| IV  || Negligible || Could result in injury or illness not resulting in a lost work day, loss exceeding $2K but less than $10K, or minimal environmental damage not violating law or regulation.
|}
Current FMECA severity categories for [[Federal Aviation Administration|U.S. Federal Aviation Administration]] (FAA), NASA and [[European Space Agency]] space applications are derived from MIL&ndash;STD&ndash;882.<ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = NASA Systems Engineering Handbook
|    section =
|  sectionurl =
|    version =
|  publisher = National Aeronautics and Space Administration
|        year =
|        url = http://snebulos.mit.edu/projects/reference/NASA-Generic/NASA-SP-610S
|      format =  
|          id = SP&ndash;610S
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref><ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Failure Modes, Effects and Criticality Analysis (FMECA)
|    section =
|  sectionurl =
|    version = D
|  publisher = European Space Agency
|        year = 1991
|        url =
|      format =
|          id = ECSS&ndash;Q&ndash;30&ndash;02A
|  accessdate =
|      quote =
|        page =
|      pages =
|        ref =
}}</ref><ref>{{cite manual
|        last =
|      first =
| author-link =
|  coauthors =
|      title = Reusable Launch and Reentry Vehicle System Safety Processes
|    section =
|  sectionurl =
|    version =
|  publisher = Federal Aviation Administration
|        year = 2005
|        url = http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryCircular.nsf/0/e62865e0d3765a1986257052006fc948/$FILE/AC%20431.35-2A.pdf
|      format = pdf
|          id = AC&nbsp;431.35&ndash;2A
|  accessdate = 2010-03-14
|      quote =  
|        page =
|      pages =
|        ref =
}}</ref>
 
===Failure detection methods===
For each component and failure mode, the ability of the system to detect and report the
failure in question is analyzed. One of the following will be entered on each row of the FMECA matrix:
* ''Normal'': the system correctly indicates a safe condition to the crew
* ''Abnormal'': the system correctly indicates a malfunction requiring crew action
* ''Incorrect'': the system erroneously indicates a safe condition in the event of malfunction, or alerts the crew to a malfunction that does not exist (false alarm)
 
===Criticality ranking===
Failure mode criticality assessment may be qualitative or quantitative. For qualitative
assessment, a mishap probability code or number is assigned and entered on the matrix. For
example, MIL&ndash;STD&ndash;882 uses five probability levels:
{| class="wikitable" style="margin: 1em auto 1em auto"
|+ '''Failure Probability Levels (MIL&ndash;STD&ndash;882)'''
! Description || Level || Individual Item || Fleet
|-
| Frequent  || A || Likely to occur in the life of the item || Continuously experienced
|-
| Probable  || B || Will occur several times in the life of an item || Will occur frequently
|-
| Occasional || C || Likely to occur some time in the life of an item || Will occur several times
|-
| Remote    || D || Unlikely but possible to occur in the life of an item || Unlikely, but can reasonably be expected to occur
|-
| Improbable || E || So unlikely, it can be assumed occurrence may not be experienced || Unlikely to occur, but possible
|}
The failure mode may then be charted on a criticality matrix using severity code as one axis
and probability level code as the other.
For quantitative assessment, ''modal criticality number'' <math>C_m</math> is calculated for each failure mode of each item, and ''item criticality number'' <math>C_r</math> is
calculated for each item. The criticality numbers are computed using the following values:
* Basic failure rate <math>\lambda_p</math>
* Failure mode ratio <math>\alpha</math>
* Conditional probability <math>\beta</math>
* Mission phase duration <math>t</math>
The criticality numbers are computed as <math>C_m = \lambda_p \alpha \beta t</math> and <math>C_r = \sum_{n=1}^N (C_m)_n</math>.
The basic failure rate <math>\lambda_p</math> is usually fed into the FMECA from a failure rate prediction based on MIL&ndash;HDBK&ndash;217, PRISM, RIAC&nbsp;217Plus, or a similar
model.
The failure mode ratio may be taken from a database source such as RAC FMD&ndash;97. For functional level FMECA, engineering judgment may be required to assign failure mode ratio.
The conditional probability number <math>\beta</math> represents the conditional
probability that the failure effect will result in the identified severity classification,
given that the failure mode occurs. It represents the analyst's best judgment as to the
likelihood that the loss will occur.
For graphical analysis, a criticality matrix may be charted using either <math>C_m</math> or <math>C_r</math> on one axis and severity code on the other.
 
===Critical item/failure mode list===
Once the criticality assessment is completed for each failure mode of each item, the FMECA matrix may be sorted by severity and qualitative probability level or quantitative
criticality number. This enables the analysis to identify critical items and critical
failure modes for which design mitigation is desired.
 
===Recommendations===
After performing FMECA, recommendations are made to design to reduce the consequences of critical failures. This may include selecting components with higher reliability, reducing
the stress level at which a critical item operates, or adding redundancy or monitoring to the system.
 
===Maintainability analysis===
FMECA usually feeds into both Maintainability Analysis and [[Logistics Support Analysis]], which both require data from the FMECA.
 
===FMECA report===
A FMECA report consists of system description, ground rules and assumptions, conclusions and
recommendations, corrective actions to be tracked, and the attached FMECA matrix which may
be in spreadsheet, worksheet, or database form.
 
==Risk priority calculation==
RAC CRTA&ndash;FMECA and MIL&ndash;HDBK&ndash;338 both identify Risk Priority Number (RPN)
calculation as an alternate method to criticality analysis. The RPN is a result
of a multiplication of detectability (D) x severity (S) x
occurrence (O). With each on a scale from 1 to 10, the highest RPN is
10x10x10 = 1000. This means that this
failure is not detectable by inspection, very severe and the occurrence is almost sure. If
the occurrence is very sparse, this would be 1 and the RPN would
decrease to 100. So, criticality analysis enables to focus on the highest risks.
 
==Advantages and disadvantages==
Strengths of FMECA include its comprehensiveness, the systematic establishment of relationships between failure causes and effects, and its ability to point out individual failure modes for corrective action in design. Weaknesses include the extensive labor required, the large number of trivial cases considered, and inability to deal with multiple-failure scenarios or unplanned cross-system effects such as sneak circuits.
 
According to an FAA research report for commercial space transportation,
:''Failure Modes, effects, and Criticality Analysis is an excellent hazard analysis and risk assessment tool, but it suffers from other limitations. This alternative does not consider combined failures or typically include software and human interaction considerations. It also usually provides an optimistic estimate of reliability. Therefore, FMECA should be used in conjunction with other analytical tools when developing reliability estimates.''<ref>{{cite manual
|        last =
|      first =
| author-link = Associate Administrator for Commercial Space Transportation
|  coauthors =
|      title = Research and Development Accomplishments FY&nbsp;2004
|    section =
|  sectionurl =
|    version =
|  publisher = Federal Aviation Administration
|        year = 2004
|        url =
http://www.faa.gov/about/office_org/headquarters_offices/ast/about/media/032504.pdf
|      format = pdf
 
|  accessdate = 2010-03-14
|      quote =
|        page =
|      pages =
|        ref =
}}</ref>
 
== See also ==
* [[Integrated Logistics Support]]
* [[Risk assessment]]
* [[Reliability Engineering]]
* [[Safety Engineering]]
* [[System Safety]]
* [[Failure mode and effects analysis|FMEA]]
* [[RAMS]]
 
==Further reading==
*[http://www.fmea-fmeca.com "FMEA and FMECA Examples"]
*[http://www.weibull.com/basics/fmea.htm "FMEA and FMECA: An Overview of Basic Concepts"]
*[http://www.fmeainfocentre.com "FMEA Info Centre"]
*[http://www.rcmo.com "FMEA and FMECA / RCM : Integration to SAP EAM"]
 
==References==
{{reflist}}
 
{{DEFAULTSORT:Failure Mode, Effects, And Criticality Analysis}}
[[Category:Impact assessment]]
[[Category:Maintenance]]
[[Category:Reliability engineering]]
[[Category:Safety engineering]]
[[Category:Systems engineering]]

Latest revision as of 17:11, 27 December 2014

Alyson Meagher is the title her parents love psychic readings clairvoyance (from this source) gave her but she doesn't like when people use her full name. She is truly fond of caving but she doesn't have the time recently. I am an invoicing officer and I'll be promoted soon. My spouse and I reside in Mississippi but now I'm considering other options.

Feel free to surf to my page: accurate psychic predictions (http://gcjcteam.org/index.php?mid=etc_video&document_srl=696611&sort_index=regdate&order_type=desc)