how to draw event tree analysis

Event tree analysis (ETA) is a forward, top-down, logical modeling technique for both success and failure that explores responses through a single initiating event and lays a path for assessing probabilities of the outcomes and overall system analysis.^[1] This analysis technique is used to analyze the effects of functioning or failed systems given that an event has occurred.^[2]

ETA is a powerful tool that will identify all consequences of a system that have a probability of occurring after an initiating event that can be applied to a wide range of systems including: nuclear power plants, spacecraft, and chemical plants. This technique may be applied to a system early in the design process to identify potential issues that may arise, rather than correcting the issues after they occur.^[3] With this forward logic process, use of ETA as a tool in risk assessment can help to prevent negative outcomes from occurring, by providing a risk assessor with the probability of occurrence. ETA uses a type of modeling technique called "event tree", which branches events from one single event using Boolean logic.

History [edit]

The name "Event Tree" was first introduced during the WASH-1400 nuclear power plant safety study (circa 1974), where the WASH-1400 team needed an alternate method to fault tree analysis due to the fault trees being too large. Though not using the name event tree, the UKAEA first introduced ETA in its design offices in 1968, initially to try to use whole plant risk assessment to optimize the design of a 500MW Steam-Generating Heavy Water Reactor. This study showed ETA condensed the analysis into a manageable form.^[1] ETA was not initially developed during WASH-1400, this was one of the first cases in which it was thoroughly used. The UKAEA study used the assumption that protective systems either worked or failed, with the probability of failure per demand being calculated using fault trees or similar analysis methods. ETA identifies all sequences which follow an initiating event. Many of these sequences can be eliminated from the analysis because their frequency or effect are too small to affect the overall result. A paper presented at a CREST symposium in Munich, Germany, in 1971^[2] shows how this was done. The conclusions of the US EPA study of the Draft WASH-1400^[3] acknowledges the role of Ref 1 and its criticism of the Maximum Credible Accident approach used by AEC. MCA sets the reliability target for the containment but those for all other safety systems are set by smaller but more frequent accidents and would be missed by MCA.

In 2009 a risk analysis was conducted on underwater tunnel excavation under the Han River in Korea using an earth pressure balance type tunnel boring machine. ETA was used to quantify risk, by providing the probability of occurrence of an event, in the preliminary design stages of the tunnel construction to prevent any injuries or fatalities because tunnel construction in Korea has the highest injury and fatality rates within the construction category.^[4]

Theory [edit]

Performing a probabilistic risk assessment starts with a set of initiating events that change the state or configuration of the system.^[3] An initiating event is an event that starts a reaction, such as the way a spark (initiating event) can start a fire that could lead to other events (intermediate events) such as a tree burning down, and then finally an outcome, for example, the burnt tree no longer provides apples for food. Each initiating event leads to another event and continuing through this path, where each intermediate event's probability of occurrence may be calculated by using fault tree analysis, until an end state is reached (the outcome of a tree no longer providing apples for food).^[3] Intermediate events are commonly split into a binary (success/failure or yes/no) but may be split into more than two as long as the events are mutually exclusive, meaning that they can not occur at the same time. If a spark is the initiating event there is a probability that the spark will start a fire or will not start a fire (binary yes or no) as well as the probability that the fire spreads to a tree or does not spread to a tree. End states are classified into groups that can be successes or severity of consequences. An example of a success would be that no fire started and the tree still provided apples for food while the severity of consequence would be that a fire did start and we lose apples as a source of food. Loss end states can be any state at the end of the pathway that is a negative outcome of the initiating event. The loss end state is highly dependent upon the system, for example if you were measuring a quality process in a factory a loss or end state would be that the product has to be reworked or thrown in the trash. Some common loss end states:^[3]

• Loss of Life or Injury/ Illness to personnel^[3]
• Damage to or loss of equipment or property (including software)^[3]
• Unexpected or collateral damage as a result of tests
• Failure of mission^[3]
• Loss of system availability^[3]
• Damage to the environment^[3]

Event tree diagram example

Methodology [edit]

The overall goal of event tree analysis is to determine the probability of possible negative outcomes that can cause harm and result from the chosen initiating event. It is necessary to use detailed information about a system to understand intermediate events, accident scenarios, and initiating events to construct the event tree diagram. The event tree begins with the initiating event where consequences of this event follow in a binary (success/failure) manner. Each event creates a path in which a series of successes or failures will occur where the overall probability of occurrence for that path can be calculated. The probabilities of failures for intermediate events can be calculated using fault tree analysis and the probability of success can be calculated from 1 = probability of success (ps) + probability of failure (pf).^[3] For example, in the equation 1 = (ps) + (pf) if we know that pf=.1 from fault tree analysis then through simple algebra we can solve for ps where ps = (1) - (pf) then we would have ps = (1) - (.1) and ps=.9.

The event tree diagram models all possible pathways from the initiating event. The initiating event starts at the left side as a horizontal line that branches vertically. the vertical branch is representative of the success/failure of the initiating event. At the end of the vertical branch a horizontal line is drawn on each the top and the bottom representing the success or failure of the first event where a description (usually success or failure) is written with a tag that represents the path such as 1s where s is a success and 1 is the event number similarly with 1f where 1 is the event number and f denotes a failure (see attached diagram). This process continues until the end state is reached. When the event tree diagram has reached the end state for all pathways the outcome probability equation is written.^{[1] [3]}

Steps to perform an event tree analysis:^{[1] [3]}

1. Define the system: Define what needs to be involved or where to draw the boundaries.
2. Identify the accident scenarios: Perform a system assessment to find hazards or accident scenarios within the system design.
3. Identify the initiating events: Use a hazard analysis to define initiating events.
4. Identify intermediate events: Identify countermeasures associated with the specific scenario.
5. Build the event tree diagram
6. Obtain event failure probabilities: If the failure probability can not be obtained use fault tree analysis to calculate it.
7. Identify the outcome risk: Calculate the overall probability of the event paths and determine the risk.
8. Evaluate the outcome risk: Evaluate the risk of each path and determine its acceptability.
9. Recommend corrective action: If the outcome risk of a path is not acceptable develop design changes that change the risk.
10. Document the ETA: Document the entire process on the event tree diagrams and update for new information as needed.

Mathematical concepts [edit]

1 = (probability of success) + (probability of failure)

The probability of success can be derived from the probability of failure.

Overall path probability = (probability of event 1) × (probability of event 2) × ... × (probability of event n)

In risk analysis [edit]

The event tree analysis can be used in risk assessments by determining the probability that is used to determine risk when multiply by the hazard of events. Event Tree Analysis makes it easy to see what pathway creating the biggest probability of failure for a specific system. It is common to find single-point failures that do not have any intervening events between the initiating event and a failure. With Event Tree Analysis single-point failure can be targeted to include an intervening step that will reduce the overall probability of failure and thus reducing the risk of the system. The idea of adding an intervening event can happen anywhere in the system for any pathway that generates too great of a risk, the added intermediate event can reduce the probability and thus reduce the risk.

Advantages [edit]

• Enables the assessment of multiple, co-existing faults and failures^[1]
• Functions simultaneously in cases of failure and success^[1]
• No need to anticipate end events^[1]
• Areas of single point failure, system vulnerability, and low payoff countermeasures may be identified and assessed to deploy resources properly^[1]
• paths in a system that lead to a failure can be identified and traced to display ineffective countermeasures.^[1]
• Work can be computerized^[3]
• Can be performed on various levels of details^[3]
• Visual cause and effect relationship^[3]
• Relatively easy to learn and execute^[3]
• Models complex systems into an understandable manner^[3]
• Follows fault paths across system boundaries^[3]
• Combines hardware, software, environment, and human interaction^[3]
• Permits probability assessment^[3]
• Commercial software is available^[3]

Limitations [edit]

• Addresses only one initiating event at a time.^[1]
• The initiating challenge must be identified by the analyst^[1]
• Pathways must be identified by the analyst^[1]
• Level of loss for each pathway may not be distinguishable without further analysis^[1]
• Success or failure probabilities are difficult to find.^[1]
• Can overlook subtle system differences^[3]
• Partial successes/failures are not distinguishable^[3]
• Requires an analyst with practical training and experience^[3]

Software [edit]

Though ETA can be relatively simple, software can be used for more complex systems to build the diagram and perform calculations more quickly with reduction of human errors in the process. There are many types of software available to assist in conducting an ETA. In nuclear industry, RiskSpectrum PSA software is widely used which has both event tree analysis and fault tree analysis. Professional-grade free software solutions are also widely available. SCRAM is an example open-source tool that implements the Open-PSA Model Exchange Format open standard for probabilistic safety assessment applications.

See also [edit]

• Fault tree analysis
• Failure modes and effect analysis

References [edit]

1. ^ ^{a b c d e f g h i j k l m n} Clemens, P.L.; Rodney J. Simmons (March 1998). "System Safety and Risk Management". NIOSH Instructional Module, A Guide for Engineering Educators. Cincinnati,OH: National Institute for Occupational Safety and Health: IX-3–IX-7.
2. ^ ^{a b} Wang, John et al. (2000). What Every Engineer Should Know About Risk Engineering and Management, p. 69., p. 69, at Google Books
3. ^ ^{a b c d e f g h i j k l m n o p q r s t u v w x y} Ericson, Clifton A. (2005). Hazard Analysis Techniques for System Safety. John Wiley & Sons, Inc.
4. ^ Hong, Eun-Soo; In-Mo Lee; Hee-Soon Shin; Seok-Woo Nam; Jung-Sik Kong (2009). "Quantitative risk evaluation based on event tree analysis technique: Application to the design of shield TBM". Tunneling and Underground Space Technology. 24 (3): 269–277. doi:10.1016/j.tust.2008.09.004.

smithwaystand.blogspot.com

Source: https://en.wikipedia.org/wiki/Event_tree_analysis

Share this post