Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
    • Asset Reliability @ Work
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • Quality Engineering Statistics
    • An Introduction to Reliability Engineering
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Fred Schenkelberg Leave a Comment

Basic Description of a Fault Tree Analysis

Basic Description of a Fault Tree Analysis

A fault tree analysis (FTA) is a logical, graphical diagram that starts with an unwanted, undesirable, or anomalous state of a system.

The diagram then lays out the many possible faults and combination of faults within the subsystems, components, assemblies, software, and parts comprising the system which may lead to the top level unwanted fault condition.

An FTA shows the many possible cause and effect paths to a specific fault condition.

For example, a laptop computer may have a top-level fault of not turning on. A few possible causes are a dead battery, faulty power distribution circuitry, or a broken power switch.

By graphically portraying the various paths to the top level fault you may be able to:

  1. Identify ways to improve the system reliability by improving critical elements of the system
  2. Quickly identify the root cause of an actual fault by using the FTA to evaluate each potential cause
  3. Using boolean algebra calculate the probability of the fault occurring overall and via each potential path
  4. Provide an alternative view of system performance with a focus on one particular fault at a time
  5. Uncover potential unwanted interactions, adverse secondary faults, and impact of human interaction of system behavior

A team activity

The development of an FTA should be accomplished by a team.

While an individual could construct a fault tree, bringing a group of individual with deep knowledge of the various elements of a system will result in a comprehensive fault tree.

Furthermore, the team gains the insights through discussion of system response to potential faults. This may result in the identification of additional experimentation or modeling to fully characterize system behavior. Or, it may reveal potential improvements to the design or improved mitigation to potential faults.

The initial construction of the fault tree should take place early in the system development process. Ideally, the initial work begins just as the basic system architecture and essential functions are defined.

As the system development defines subsystems and specific components, the team should refine the FTA and use the tool as a guide to avoid increasing the probability of the top level fault occurring.

If the FTA occurs too late in the development process it will have little impact on the development and improvement of the system reliability.

Elements of a Fault Tree

A fault tree is a top-down, graphical, logical model depicting the various ways a specific fault may occur and is made up of specific logic symbols.

The logic gates provide a means to relate the various lower level faults as they progress to the occurrence of the top level fault.

There are three groups of symbols useful when constructing a fault tree.

  • Event symbols: Events are conditions or faults and the symbols indicate if they are normal, independent, conditional, or contributing. Generally the lowest level faults in the analysis.
  • Gate symbols: Gates depict the basic functional relationship in logic form and used to connect lower level events which contribute to the upper-level events or faults.
  • Transfer symbols: Transfer symbols provide a convenient means to connect related fault trees, including fault trees of a subsystem to its system.

Common event symbols

FTA-and-gateBasic Event —circle: a basic initiating fault requiring no further development

FTA-ovalConditioning Event —oval: specific conditions or restrictions that apply to any logic gate (used primarily with Priority AND and Inhibit gates)

FTA-diamondUndeveloped Event —diamond: an event which is not further developed either because it is of insufficient consequence or because information is unavailable

FTA-houseHouse Event —house: an event which is normally expected to occur

Common gate symbols

FTA-and-gateAND — output fault occurs if all the input faults occur

FTA-or-gateOR — output fault occurs if at least on of the input faults occur

FTA-combinationCombination — output fault occurs if n of the input faults occur

FTA-XOR-2Exclusive OR —Output fault occurs if exactly one of the input faults occurs

FTA-priority-andPriority AND — output fault occurs if all the input faults occur in a specific sequence (use conditioning event to detail specific order)

FTA-inhibitInhibit — output fault occurs if the (single) input fault occurs in the presence of an enabling condition (use condition event to detail enabling condition(s))

Common transfer symbols

FTA-transfer-inTransfer in — indicates that the tree is developed further at the occurrence of the corresponding transfer out (e.g. On another page)

FTA-transfer-outTransfer out — indicates that this portion of the tree must be attached to the corresponding transfer in

 

Symbols and descriptions from:

Fault tree handbook with aerospace applications. Office of safety and mission assurance NASA Headquarters, 2002.


Related:

Basic Approaches to Life Testing (article)

Reliability Testing (article)

The Next Step in Your Data Analysis (article)

 

Filed Under: Articles, CRE Preparation Notes, Reliability in Design and Development Tagged With: Fault Tree Analysis and Success Tree Analysis, FTA

« In a World of “Black Swans”, How Do You Know Which One to Worry About
Software Reuse Considerations »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Article by Fred Schenkelberg
in the Musings series

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Articles

  • Risk Prioritization in FMEA – a Summary
  • What Are Best Practices for Facilitating Qualitative Assessments?
  • So, What’s Still Wrong with Maintenance
  • Foundation of Great Project Outcomes – Structures
  • What is the Difference Between Quality Assurance and Quality Control?

© 2023 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy

This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.