Fault Tree Analysis (FTA)

OPI OEA L1A

© 2012 PETROLIAM NASIONAL BERHAD (PETRONAS)

All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording or otherwise) without the permission of the copyright owner. This document has been produced by PETRONAS whether by itself or through third
party consultants and the manner in which this document is used is strictly controlled by PETRONAS.
 When to use
When you need to understand the root causes, or potential causes of a problem, on hazard.

 What you get

A systematic graphical breakdown of the causes of a problem or hazard into a clear tree
structure.
 Time
Dependent upon the complexity of the system and depth of analysis required, nominally a few
hours.
 Number of people
For best results at least two people with relevant understanding of all facets of the system,
process, product or service.
 Equipment
A pen and paper for a basic FTA. Specific computer software is available for producing risk
assessments based on the probability of each root cause.

© 2014 Petroliam Nasional Berhad (PETRONAS)

 Method
1. Clearly state the problem or hazard and place this at the top of a diagram.
2. Break the problem down into generic components or potential causes and place these in boxes
below the problem in a tree structure (see example diagram).
3. For each connecting node in the tree, consider If the two linking components would cause the
effect one level up the tree, if they occurred independently (an OR gate).
4. OR and AND gates are Boolean expressions, and are placed in the three diagram at each node,
denoted by the sysbols:

5. Repeat steps 2 to 4 for each new block added until either no further cause can be established,
or a consensus of agreement is reached that a sufficient depth of analysis has been undertaken.
6. Other symbols used in the tree are:
Cause event not fully traced back
Fault resulting from other events
to its source

Basic cause or event, taken as an

input

© 2014 Petroliam Nasional Berhad (PETRONAS)

 Example
The example is for a car radiator. The FTA can be seen opposite.
The analysis shows that if the system is low in antifreeze AND the outside temperature is low,
then the radiator fault. The radiator water being too hot also leads to a fault, but the manner in which
the water gets too hot is not investigated.
 Exercise
Consider the problem of a headache and try to break it down using a fault tree.
 Additional comments
This analysis enables you to understand and map the connectedness of issues that normal, or more
linear fault identification techniques would miss.
you can use other symbols for AND and OR if you prefer, e.g.

AND OR

This tool is often used with Tool 28: FMECA.

 Other information
For further detail see Neil Storey, Safety Critical Computer System, Addison-Wesley, 1996

© 2014 Petroliam Nasional Berhad (PETRONAS)

 Radiator fault

Water freezes Surface

Water too hot
puncture

Low
Low anti-
outside
freeze
temp Impact Build
damage Vibration
fault

© 2014 Petroliam Nasional Berhad (PETRONAS)