What is Fault Tree Analysis?

fault tree example

Before you can prevent future failures, you must first determine the root cause of the problem[cite: 5]. Otherwise, it is not a matter of if the failure will happen again, but simply a matter of time[cite: 5]. Fault Tree Analysis is a method utilized to discover the root cause of an issue, enabling the identification and analysis of the fundamental reasons before an equipment failure occurs[cite: 5].

The Development of Fault Tree Analysis

The Fault Tree Analysis method was first proposed in 1961 by Watson and Mearns of Bell Telephone Laboratories in the United States, where it was applied to analyze the Minuteman missile launch control system[cite: 5]. Subsequently, engineers at Boeing developed computational programs for the FTA method, marking its entry into the aerospace sector centered around Boeing[cite: 5].

In 1974, the United States Atomic Energy Commission published a 3,000-page report titled the "Reactor Safety Study"[cite: 5]. This report was compiled after two years of research by a safety group comprising 60 experts, led by Professor Norman Rasmussen of the Massachusetts Institute of Technology (MIT)[cite: 5]. The report evaluated the risks of nuclear power plants using Event Tree (ET) and Fault Tree Analysis methods targeting 100 commercial light-water reactor nuclear power plants in the US[cite: 5]. This significantly advanced the application of FTA[cite: 5]. The publication of this report elicited a massive response from various sectors and is regarded as a major milestone in the developmental history of FTA[cite: 5].

What is a Fault Tree?

A fault tree, also known as an error tree, is a specialized inverted tree-like logical causal relationship diagram[cite: 5]. It primarily employs event symbols, logic gate symbols, and transfer symbols to represent the causes of an accident or fault event and their logical relationships in a logic tree diagram[cite: 5].

fault tree example

IEC 61025:2006 delineates the methodology of fault tree analysis and provides guidelines for its application[cite: 5]. It simultaneously establishes suitable assumptions, events, and failure modes, and provides an explanation of identification rules and symbols[cite: 5].

Events and Their Symbols in Fault Trees

The occurrence of a condition or action is termed an event[cite: 5].

Event Type Event Symbol Description
Basic Event basic event Circle: Represents a basic event, which is the originating root fault that requires no further, or cannot be further, investigated[cite: 5].
Resultant Event resultant event Rectangle: Represents a top event or an intermediate event, which is a fault or consequence requiring further analysis[cite: 5].
Undeveloped Event undeveloped event Diamond: Represents an omitted event, indicating an event not further investigated due to a lack of information or lack of significance[cite: 5].
Switch Event switch event House: Represents a normal event or conditional switch event, which inevitably occurs or exists in a specific state under normal circumstances[cite: 5].
Conditioning Event conditioning event Ellipse: A conditional restriction that limits a logic gate or influences the occurrence of a specific event[cite: 5]. Usually paired with an inhibit gate[cite: 5].

Logic Gates and Their Symbols in Fault Trees

In fault tree analysis, logic gates strictly describe the logical causal relationships between events[cite: 5].

Logic Gate Logic Symbol Description
AND Gate and gate Indicates that the output event occurs only if all input events occur[cite: 5].
OR Gate or gate Indicates that the output event occurs if at least one input event occurs[cite: 5].
NOT Gate not gate Indicates that the output event is the mutually exclusive opposite of the input event[cite: 5].
Priority AND Gate priority and gate Indicates that the output event occurs only if the input events occur in a specified sequence[cite: 5].
Voting Gate voting gate Indicates that the output event occurs only if *k* or more out of *n* input events occur[cite: 5].
Exclusive OR Gate exclusive or gate Indicates that the output event occurs only if exactly one single input event occurs[cite: 5].
Inhibit Gate inhibit gate Indicates that the occurrence of the input event leads to the output event only when the conditioning event occurs[cite: 5].

Transfer Symbols in Fault Trees

Transfer symbols are established to avoid repetition during drafting and to keep the diagram concise[cite: 5].

Transfer Type Transfer Symbol Description
Identical Transfer Symbol identical transfer symbol 1 identical transfer symbol 2 Identical transfer symbols are used to indicate the location of a subtree[cite: 5].
Similar Transfer Symbol similar transfer symbol 1 similar transfer symbol 2 Similar transfer symbols are used to indicate the location of a similar subtree[cite: 5].

It becomes apparent that various gates inherently involve Boolean algebra, meaning fault trees can be simplified through Boolean operations[cite: 5]. A fault tree utilizes the previously described event symbols, logic gate symbols, and transfer symbols to depict the causal relationships among various events within a system[cite: 5]. The input events of a logic gate are the "causes" of the output event, and the output event of a logic gate is the "effect" of the input events[cite: 5].

What Can Fault Tree Analysis Accomplish?

  • Understand the relationship between the top-level event and the underlying undesired states[cite: 5].
  • Demonstrate the degree to which a system complies with system safety/reliability specifications[cite: 5].
  • Prioritize the various causes resulting in the top-level event: establish a list of critical equipment/components/events based on different weighted measurement methods[cite: 5].
  • Monitor and control the safety performance of complex systems (e.g., Can a specific aircraft fly safely when fuel valve x malfunctions? How long can the aircraft fly under these conditions?)[cite: 5].
  • Minimize and optimize resource requirements[cite: 5].
  • Assist in system design[cite: 5]. Fault tree analysis can serve as a design tool to create requirements for outputs or lower-level modules[cite: 5].
  • Act as a diagnostic tool to identify and correct causes leading to the top-level event, aiding in the creation of diagnostic manuals or procedures[cite: 5].

Ready to build your Fault Tree?

No software download required. Build, render, and export engineering-grade topology diagrams directly in your browser.

Try it Now Send Feedback