Search results
Results from the WOW.Com Content Network
A fault tree diagram. Fault tree analysis (FTA) is a type of failure analysis in which an undesired state of a system is examined. This analysis method is mainly used in safety engineering and reliability engineering to understand how systems can fail, to identify the best ways to reduce risk and to determine (or get a feeling for) event rates of a safety accident or a particular system level ...
NASA Fault Tree Assessment handbook MIL-HDBK-2155, Failure Reporting, Analysis and Corrective Action Taken , U.S. Department of Defense MIL-HDBK-502A, Product Support Analysis, U.S. Department of Defense Archived 2013-12-24 at the Wayback Machine
[2] [3] In 1966 NASA released its FMECA procedure for use on the Apollo program. [4] FMECA was subsequently used on other NASA programs including Viking, Voyager, Magellan, and Galileo. [5] Possibly because MIL–P–1629 was replaced by MIL–STD–1629 (SHIPS) in 1974, development of FMECA is sometimes incorrectly attributed to NASA. [6]
graph with an example of steps in a failure mode and effects analysis. Failure mode and effects analysis (FMEA; often written with "failure modes" in plural) is the process of reviewing as many components, assemblies, and subsystems as possible to identify potential failure modes in a system and their causes and effects.
The PSSA may contain qualitative FTA, which can be used to identify systems requiring redundancy so that catastrophic events do not result from a single failure (or dual failure where one is latent). A fault tree is prepared for each SFHA hazard rated hazardous or catastrophic. Fault trees may be performed for major hazards if warranted.
In addition to these objects, SAPHIRE has a unique feature known as “table events” that allows the user to group up to eight basic events together on the fault tree graphic, thereby compacting the size of the fault tree on the printed page or computer screen. All of these objects though represent traditional static-type Boolean logic models.
[17]: 209–210 NASA conducted a fault tree analysis to determine the probable causes of the accident, and focused its investigations on the parts of the orbiter most likely to have been responsible for the in-flight breakup. [17]: 215 Engineers in the hangar analyzed the debris to determine how the orbiter came apart. Even though the crew ...
[5] [8] The more complex risk analysis tools of fault tree analysis, event tree analysis use the same principle: Things go wrong, there is a reason for that and a result too, with the result generating the adverse consequences. The bow-tie diagram introduces the concept of a central energy-based event (the "bow tie knot") in which the damaging ...