MADE Workflows > Generate Hardware FTA

WF17: Generate Hardware Fault Tree Analysis

Pre-requisites

SRA Module: access to the Safety and Risk Assessment (SRA) module enables a Hardware Fault Tree Analysis (FTA) to be generated.
FBD Model: defined with functions and functional flows required to map out Fault Tree paths. Inclusion of failure diagrams would improve detail of Fault Trees (see WF06).
Reliability Data: consists of RBD groupings, reliability values based on a distribution type (Exponential, Weibull, Markov) and duration of operation (inherent from Mission Profile).

Select 'Hardware - RBD' in 'Fault Tree' under 'Analyses' on the main menu bar or via the right-click context menu opened in the Project Explorer / System Model viewer.
Define name (mandatory) and description (optional) of the functional Fault Tree Analysis (FTA).
Select a model item/RBD grouping, from the list, to be the top event of the fault tree.
Select the source for P(f) values that will be used for each event in the FTA.
Click 'OK' to generate a hardware FTA with the details as defined and options as selected. A screen capture may be exported as a .png file.
Select 'Event List' in 'Event Table Controls' to review the events of the hardware FTA. It may be exported as a .csv file.

FTA Screen Capture: hardware FTA fault tree exported as a .png file.
Event List Raw Data: events of the hardware FTA listed in a table that could be exported as a .csv file.
FTA Report: Event list & image of the fault tree can be generated from Report Wizard.

Note: To generate reports, refer to the Fault Tree Reports and Fields guide.

Step 1: Create Hardware FTA

'Analyses' menu: Fault Tree (submenu) > Fault Tree Builder, Functional, Hardware - RBD (highlighted); Response Paths, Connection Matrix, Common Mode Analysis, Critical Item Analysis, Criticality & Reliability Editor, Diagnostic Analyses, Failure Rate Prediction, Markov Analysis, RBD Analysis, Reliability Allocation Editor, Back-Fit RCM, Classic RCM, Maintenance Cost Estimates.
Project Explorer right-click context menu on System item: New (System Model, Failure Diagram, Bond Graph, Functions, Functional Diagram), Maintenance Actions, Mission Profiles, Cut/Copy/Paste, Delete, End Effect Item, Fault Tree (submenu) > Fault Tree Builder, Functional, Hardware - RBD (highlighted), Response Paths, Save to Library, Advanced Properties.

Step 2: Define Analysis Details

"Fault Tree Analysis" — "Select Top Event": "Analysis Details": Name "New Fault Tree Analysis", Description "Description for demonstration purpose". "Fault Tree Type": radio User-defined (checkbox "Show only connected Failure Conditions", disabled) / Model-based Analysis (disabled options: Propagation Type FCM/Bond, Depth of Analysis Fault/Mechanism/Cause, Level of Analysis "System", Preferred Gate Type "OR") / Hardware Fault Tree (selected). "Reliability Metrics": Baseline / Revised (selected) with same descriptions as WF16. Note about adjusting default Depth of Analysis at Preferences → Project Preferences → Modeling → Fault Tree Analysis. Right panel "Top Event" (Model-based tab): tree showing Vehicle System > Series Group. Buttons OK, Cancel.

Step 3: Select Top Event

Same dialog with tree expanded: Vehicle System > Series Group > Updated Coupling, Power Generation (selected, highlighted) > Fuel Tank, Control Unit, Diesel Engine > Series Group > Lift Pump, Injector Pump, Engine, Coupling 1, K/N Redundancy Group; Vehicle, Driveline.

Step 4: Generate Hardware FTA

"Fault Tree Builder" view: Top-level nodes "A component failed" (Driveline, P(f)=4.03E-06, gate E3) and "Component failure" (Vehicle, gate B4) side by side. Below Driveline node: "A component failed" (Series Group, P(f)=4.03E-06, gate E7) branching via AND/OR gate into four leaves: "Component failure" (Differential, gate B8), "Component failure" (Driveshaft, gate B9), "Component failure" (Transmission, gate B10), and "All components failed" (Wheel configuration, P(f)=1.33E-07, gate E11). Header: "Fault Tree - Top Event P(f) = 5.98E-04". Event Table Controls: Event List (selected)/MCSQ/RI% Ranking; RI Type "Birnbaum". Table columns ID/Logic/Event Type/Item/Event Name/RI(F)/P(f): B29 (Basic Event, Coupling 1, "Component failure", 1.00E-04), B31 (Basic Event, Air Filter, "Component failure", 5.62E-03), B32 (Basic Event, Primary Fuel Filter, "Component failure", 5.62E-03), B33 (Basic Event, Secondary Fuel Filter, "Component failure", 5.62E-03), B34 (Basic Event, Inlet, "Component failure", 1.30E-06), B35 (Basic Event, Lining, "Component failure", 1.30E-06), B36 (Basic Event, Outlet, "Component failure", 1.30E-06), B37/B38/B39 (Basic Event, Inlet 1/Lining 1/Outlet 1, "Component failure", 1.30E-06 each), E1 (Top Event, Vehicle System, "Component failure", 5.98E-04), E2 (OR(B4+B5+E3+E6), Intermediate Event, Series Group, "A component failed", 5.98E-04), E3 (E7, Intermediate Event, Driveline, "A component failed", 4.03E-06).

Step 5: Review Event List

"Fault Tree - Top Event P(f) = 7.19E-04" table: Event Table Controls Event List selected, RI Type "Birnbaum", P(f) State "Current". Rows (ID/Logic/Event Type/Item/Event Name/RI(F)/P(f)): B3 (Basic Event, Control Unit, "Component failure", N/A, 4.44E-07); B5 (Basic Event, Inlet, N/A, 2.13E-04); B6 (Basic Event, Outlet, N/A, 2.13E-04); B7 (Basic Event, Lining, N/A, 2.13E-04); B9 (Basic Event, Lift Pump, N/A, 1.11E-09); B10 (Basic Event, Injector Pump, N/A, 7.98E-05); B11 (Basic Event, Engine, N/A, 3.06E-09); B12 (Basic Event, Coupling 1, N/A, 2.28E-10); B14 (Basic Event, Air Filter, N/A, 3.56E-10); B15 (Basic Event, Primary Fuel Filter, N/A, 5.61E-04); B16 (Basic Event, Secondary Fuel Filter, N/A, 3.13E-10); E1 (OR(E2+B3+E4), Top Event, Power Generation, "Component failure", N/A, 7.19E-04); E2 (OR(B5+B6+B7), Intermediate Event, Fuel Tank, "A component failed", N/A, 6.38E-04); E4 (Intermediate Event, Diesel Engine, "A component failed", N/A, 7.98E-05); E8 (OR(B9+B10+B11+B12+E13), Intermediate Event, Diesel Engine, "A component failed", N/A, 7.98E-05); E13 (K/N(B14,B15,B16), Intermediate Event, K/N Redundancy Group, "All components failed", N/A, 3.75E-13).