What is Fault Tree Analysis?

Slides:



Advertisements
Similar presentations
99/11/12. When to use it Fig. 1. Fault Tree Analysis in problem solving.
Advertisements

Software Testing Technique. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves.
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
Design Concepts and Principles
Reliability Block Diagrams A reliability block diagram is a success-oriented network describing the function of the system. If the system has more than.
Modern Techniques of Accident Investigation C.Jayasuriya, S.V.Karthikeyan and S.E.Kannan IGCARKalpakkam.
Slide 1 May 8th, 2007Compliance EngineeringUltratech Internal Use Only Introduction to FBD and FTA Functional Block Diagrams Fault Tree Analysis.
1 Software Testing and Quality Assurance Lecture 39 – Software Quality Assurance.
Testing an individual module
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
Systems Analysis and Design in a Changing World, 6th Edition
C++ for Engineers and Scientists Third Edition
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO RISK IDENTIFICATION 2.
Lucas Phillips Anurag Nanajipuram FAILURE MODE AND EFFECT ANALYSIS.
Design, Implementation and Maintenance
1 Software Testing Techniques CIS 375 Bruce R. Maxim UM-Dearborn.
Basics of Fault Tree and Event Tree Analysis Supplement to Fire Hazard Assessment for Nuclear Engineering Professionals Icove and Ruggles (2011) Funded.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Risk Assessment and Probabilistic Risk Assessment (PRA) Mario. H. Fontana PhD.,PE Research Professor Arthur E. Ruggles PhD Professor The University of.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Combinational Logic Design CS341 Digital Logic and Computer Organization F2003.
Digital Logic Chapter 4 Presented by Prof Tim Johnson
Truth Table-Based Testing Generating test cases when the test model is a truth table Reading: Binder Chapter 6.
ERT 312 SAFETY & LOSS PREVENTION IN BIOPROCESS RISK ASSESSMENT Prepared by: Miss Hairul Nazirah Abdul Halim.
ERT 322 SAFETY AND LOSS PREVENTION RISK ASSESSMENT
Combinational Logic Design BIL- 223 Logic Circuit Design Ege University Department of Computer Engineering.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
6 Systems Analysis and Design in a Changing World, Fifth Edition.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
TUGAS K3 DALAM INDUSTRI KIMIA
SOFTWARE TESTING. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves any activity.
WHAT IF ANALYSIS USED TO IDENTIFY HAZARDS HAZARDOUS EVENTS
SAFEWARE System Safety and Computers Chap18:Verification of Safety Author : Nancy G. Leveson University of Washington 1995 by Addison-Wesley Publishing.
IAEA Training Course on Safety Assessment of NPPs to Assist Decision Making System Analysis Workshop Information IAEA Workshop City, Country XX - XX Month,
Condition Testing. Condition testing is a test case design method that exercises the logical conditions contained in a program module. A simple condition.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
1 CS 352 Introduction to Logic Design Lecture 4 Ahmed Ezzat Multi-level Gate Circuits and Combinational Circuit Design Ch-7 + Ch-8.
Prof. Enrico Zio Fault tree analysis Prof. Enrico Zio Politecnico di Milano Dipartimento di Energia.
Fault Tree Analysis for the BLEDP Student meeting Vegard Joa Moseng.
Fault Tree Analysis Why do we need fault tree analysis? What is it? Why do we use it? Why this matters to you How it works Bridgestone/Firestone Brief.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
Software Testing. SE, Testing, Hans van Vliet, © Nasty question  Suppose you are being asked to lead the team to test the software that controls.
LOGO Combining Fault Trees and Event Trees Seung Ki, Shin.
Fault Tree Analysis Using Binary Decision Diagrams
Tools Of Structured Analysis
Design and Documentation
PRA: Validation versus Participation in Risk Analysis PRA as a Risk Informed Decision Making Tool Richard T. Banke– SAIC
Combinational Logic Design&Analysis.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
Software Testing.
Logic Gates.
CS 352 Introduction to Logic Design
Safety and Risk.
UNIT-4 BLACKBOX AND WHITEBOX TESTING
Logic Gates.
Root Cause Analysis: Why? Why? Why?
CUT SET TRANSFORMATION
Fault Tree Analysis Why do we need fault tree analysis? What is it?
Review and comparison of the modeling approaches and risk analysis methods for complex ship system. Author: Sunil Basnet.
UNIT-4 BLACKBOX AND WHITEBOX TESTING
Presentation transcript:

What is Fault Tree Analysis? Fault Tree Analysis(FTA) is one of the several deductive logic model techniques, and one of the most common hazard identification tool. The deduction begins with a stated top level hazardous/undesired event. It uses logic diagrams and Boolean Algebra to identify single events and combinations of events that could cause the top event. Probability of occurrence values are assigned to the lowest events in the tree in order to obtain the probability of occurrence of the top event. Palaniappan Kannan CFSE 1

Fault tree main symbols. Commonly Used Symbols Occasionally Used Symbols OR gate Incomplete event AND gate An External Event An Event / Fault Inhibit gate Basic Event Palaniappan Kannan CFSE 2

FTA Symbols Explained Basic Event: A lower most event that can not be further developed. E.g. Relay failure, Switch failure etc., An Event / Fault: This can be a intermediate event (or) a top event. They are a result logical combination of lower level events. E.g. Both transmitters fail, Run away reaction OR Gate: Either one of the bottom event results in occurrence of the top event. E.g. Either one of the root valve is closed, process signal to transmitter fails. AND Gate: For the top event to occur all the bottom events should occur. E.g. Fuel, Oxygen and Ignition source has to be present for fire. Palaniappan Kannan CFSE 3

FTA Symbols Explained Incomplete Event: An event which has scope for further development but not done usually because of insufficient data. E.g. Software malfunction, Human Error etc., External Event: An event external to the system which can cause failure. E.g. Fire. Inhibit Gate: The top event occurs only if the bottom event occurs and the inhibit condition is true. E.g. False trip of unit on “maintenance override” not ON. Palaniappan Kannan CFSE 4

Simple Examples OR AND Example 1: Example 2: 0.28 Transmitter Failed 0.1 0.2 0.000002(2E-06) Valve Failed AND Valve 1 Failed Valve 2 Failed 0.001 0.002 Palaniappan Kannan CFSE 5

Procedure Procedure for Fault Tree Analysis Define TOP event Define overall structure. Explore each branch in successive level of detail. Solve the fault tree Perform corrections if required and make decisions Palaniappan Kannan CFSE 6

Procedure Define Top Event: Use PHA, P&ID, Process description etc., to define the top event. If its too broad, overly large FTA will result. E.g. Fire in process. If its too narrow, the exercise will be costly. E.g. Leak in the valve. The boundaries for top event definition can be a System, Sub-system, Unit, Equipment (or) a Function. Some good examples are: Overpressure in vessel V1, Motor fails to start, Reactor high temperature safety function fails etc., Palaniappan Kannan CFSE 7

Procedure Procedure for Fault Tree Analysis Define TOP event Define overall structure. Explore each branch in successive level of detail. Perform corrections if required and make decisions Solve the fault tree Palaniappan Kannan CFSE 8

Procedure Define overall structure: Determine the intermediate events & combination of failure that will lead to the top event. Arrange them accordingly using logical relationship. Palaniappan Kannan CFSE 9

Procedure Procedure for Fault Tree Analysis: Define TOP event Define overall structure. Explore each branch in successive level of detail. Perform corrections if required and make decisions Solve the fault tree Palaniappan Kannan CFSE 10

Procedure Explore each branch in successive level of detail: Continue the top down process until the root cause for each branch is identified and/or until further decomposition is considered unnecessary. So each branch will end with a basic event or an undeveloped event. Consider Common cause failure & Systematic failures in the process of decomposition. A good guide to stop decomposing is to go no further than physical (or) functional bounds set by the top event. Palaniappan Kannan CFSE 11

Procedure Procedure for Fault Tree Analysis: Define TOP event Define overall structure. Explore each branch in successive level of detail. Perform corrections if required and make decisions Solve the fault tree Palaniappan Kannan CFSE 12

Procedure Solve the Fault Tree: Assign probabilities of failure to the lowest level event in each branch of the tree. From this data the intermediate event frequency and the top level event frequency can be determined using Boolean Algebra and Minimal Cut Set methods. Palaniappan Kannan CFSE 13

Procedure Steps to get the final Boolean equation: 1. Replace AND gates with the product of their inputs. IE1 = A.B IE2 = C.D 2. Replace OR gates with the sum of their inputs. TOP = IE1+IE2 = A.B+C.D 3. Continue this replacement until all intermediate event gates have been replaced and only the basic events remain in the equation. TOP = A.B+C.D TOP IE1 IE2 A B C D Palaniappan Kannan CFSE 14

Procedure Minimal Cut Set theory: The fault tree consists of many levels of basic and intermediate events linked together by AND and OR gates. Some basic events may appear in different places of the fault tree. The minimal cut set analysis provides a new fault tree, logically equivalent to the original, with an OR gate beneath the top event, whose inputs (bottom)are minimal cut sets. Each minimal cut set is an AND gate with a set of basic event inputs necessary and sufficient to cause the top event. Palaniappan Kannan CFSE 15

Procedure Boolean Algebra Reduction Example: TOP = IE1 + IE2 = (A.B) + (A + IE3) = A.B + A + (C.D.IE4) = A.B + A + (C.D.D.B) = A + A.B + B.C.D.D (D.D = D) = A + A.B + B.C.D (A + A.B = A) = A + B.C.D So the minimal cut sets are: CS1 = A CS2 = B.C.D meaning TOP event occurs if either A occurs OR (B.C.D) occurs. A B IE3 C D IE4 TOP IE1 IE2 Palaniappan Kannan CFSE 16

Procedure Procedure for fault tree analysis: Define TOP event Define overall structure. Explore each branch in successive level of detail. Perform corrections if required and make decisions Solve the fault tree Palaniappan Kannan CFSE 17

Procedure Perform corrections and make decisions: Application of Boolean Algebra and Minimal Cut Set theory will result in identifying the basic events(A) and combination of basic events(B.C.D) that have major influence on the TOP event. This will give clear insight on what needs to be attended and where resources has to be put for problem solving. Palaniappan Kannan CFSE 18

Advantages of FTA Plus points of FTA: Deals well with parallel, redundant or alternative fault paths. Searches for possible causes of an end effect which may not have been foreseen. The cut sets derived in FTA can give enormous insight into various ways top event occurs. Very useful tool for focused analysis where analysis is required for one or two major outcomes. Palaniappan Kannan CFSE 19

Disadvantages of FTA Minus points of FTA: Requires a separate fault tree for each top event and makes it difficult to analyze complex systems. Fault trees developed by different individuals are usually different in structure, producing different cut set elements and results. The same event may appear in different parts of the tree, leading to some initial confusion. Palaniappan Kannan CFSE 20

END Palaniappan Kannan CFSE 21