An FTA (similar to a logic diagram) is a “deductive” analytical tool used to study a specific undesired event. The deductive analysis begins with a defined undesired event, then attempts to determine the specific causes of the event by constructing a logic diagram called a fault tree.
Fault Tree Analysis was introduced in 1962 by Bell Laboratories and is one of the most widely used to solve a wide variety of problems ranging from safety to management issues.
What is Fault Tree Analysis?
The main purpose of the Fault Tree Analysis is to help identify potential causes of system failures before the failures actually occur. It can also be used to evaluate the probability of the top event using analytical or statistical methods. These calculations involve system quantitative reliability and maintainability information, such as failure probability, failure rate and repair rate. After completing an FTA, you can focus your efforts on improving system safety and reliability.
A typical Fault Tree Analysis starts with a potential fault, and works backward to identify possible contributing factors, using a visual presentation called a fault tree diagram. The fault tree follows a top-down approach, starting with the final outcome (a potential fault condition), and evaluating the factors that could contribute to that fault.
A Fault Tree Analysis uses a few basic symbols to outline various points, causes, and effects in a process. There are many symbols, but here are some of the basics to help you get started designing a fault tree diagram.
Symbols are used to represent various events and describe relationships:
|And gate – represents a condition in which all the events shown below the gate (input gate) must be present for the event shown above the gate (output event) to occur. This means the output event will occur only if all of the input events exist simultaneously.|
|Or gate – represents a situation in which any of the events shown below the gate (input gate) will lead to the event shown above the gate (output event). The event will occur if only one or any combination of the input events exists.|
There are five types of event symbols:
|Rectangle – The rectangle is the main building block for the analytical tree. It represents the negative event and is located at the top of the tree and can be located throughout the tree to indicate other events capable of being broken down further. This is the only symbol that will have a logic gate and input events below it.|
|Circle – A circle represents a base event in the tree. These are found on the bottom tiers of the tree and require no further development or breakdown. There are no gates or events below the base event.|
|Diamond – The diamond identifies an undeveloped terminal event. Such an event is one not fully developed because of a lack of information or significance. A fault tree branch can end with a diamond. For example, most projects require personnel, procedures, and hardware. The tree developer may decide to concentrate on the personnel aspect of the procedure and not the hardware or procedural aspects. In this case the developer would use diamonds to show “procedures” and “hardware” as undeveloped terminal events.|
|Oval – An oval symbol represents a special situation that can only happen if certain circumstances occur. This is spelled out in the oval symbol. An example of this might be if switches must be thrown in a specific sequence before an action takes place.|
|Triangle – The triangle signifies a transfer of a fault tree branch to another location within the tree. Where a triangle connects to the tree with an arrow, everything shown below the connection point transfers to another area of the tree. This area is identified by a corresponding triangle that is connected to the tree with a vertical line. Letters, numbers or figures identify one set of transfer symbols from another. To maintain the simplicity of the analytical tree, the transfer symbol should be used sparingly.|
Generic Fault Tree Diagram Illustration
Fault tree development steps
To do a comprehensive FTA, follow these steps:
- Define the system. This includes the scope of the analysis including defining what is considered a failure. This becomes important when a system may have an element fail or a single function fails and the remainder of the system still operates.
- Define top-level faults. Define the fault condition, and write down the top level failure.
- Identify causes for top-level fault. Using technical information and professional judgments, determine the possible reasons for the failure to occur. Remember, these are level two elements because they fall just below the top level failure in the tree.
- Identify next level of events. Continue to break down each element with additional gates to lower levels. Consider the relationships between the elements to help you decide whether to use an “and” or an “or” logic gate.
- Add probabilities to events. If possible, evaluate the probability of occurrence for each of the lowest level elements and calculate the statistical probabilities from the bottom up.
- Finalize and review the complete diagram. The chain can only be terminated in a basic fault: human, hardware or software.
Fault Tree Diagram Example – Light cannot turn on
Let’s look at an example of a basic fault tree analysis: You flip a switch to turn on a light, but the light does not turn on. The fault condition is “No light in the room,” so that’s the beginning of the diagram
Next, what are the potential reasons the light didn’t turn on?
Fault Tree Example – System no Warning Template