Documentation

Ataytis Assurance documentation.

Generate fault trees, bow-ties, event trees, reliability block diagrams, GSN arguments and Markov models from Power BI data with the Ataytis Assurance visual.

Ataytis Assurance · Fault Tree Analysis

Preparing fault tree data

The table a fault tree needs: one row per node, which columns to include and what to call them, which row each value belongs on, and a complete worked example.

One row per node, naming its parent

Each row describes one node and names its parent, the node directly above it. Events and gates are separate rows: a gate is a node in its own right, between the event it defines and the events that cause it.

  1. The top event

    One row with no parent.

  2. The gate beneath it

    One row whose parent is the top event.

  3. The gate's inputs

    One row for each input, each with the gate as its parent.

  4. Each intermediate event

    Has its own gate beneath it: a row whose parent is the intermediate event, and that gate's inputs name the gate as their parent.

  5. Basic, undeveloped and house events

    End a branch. No row names them as its parent.

Columns

Name the columns as shown and each binds to its role without manual mapping. Put text columns in Data fields. Put numeric columns in Values and set each to Don't summarize.

ColumnMaps toWellFill it in on
Node IDNode IDData fieldsEvery row.
Parent IDConnected nodeData fieldsEvery row except the top event.
Node TypeNode typeData fieldsEvery row. Without it the tree draws but is not checked against the notation.
LabelLabelData fieldsEvery row.
Relationship TypeRelationship typeData fieldsRows attached as a condition, trigger or transfer. Leave blank for an ordinary input.
OrderOrderData fieldsRows that share a parent, to set their left-to-right order.
Diagram IDDiagram IDData fieldsEvery row, when the table holds more than one tree.
Diagram NameDiagram nameData fieldsEvery row, for a readable name in the diagram picker.
Linked Diagram IDLinked diagram IDData fieldsTransfer In and Transfer Out rows.
ProbabilityProbabilityValuesAny event.
Failure RateFailure rate (λ)ValuesAny event.
Repair RateRepair rate (μ)ValuesAny event.
Mission TimeMission timeValuesAny event.
Vote ThresholdVoting threshold (k)ValuesThe voting gate's own row.
Vote Input CountVoting input count (n)ValuesThe voting gate's own row.
Priority SequencePriority sequenceValuesEach input row of a Priority AND, Sequential or Spare gate.
Event StateEvent stateData fieldsHouse and zero event rows.
Dormancy FactorDormancy factorValuesEach input row of a Spare gate.
Spare ModeSpare modeData fieldsThe Spare gate's own row.
Spare Required CountRequired sparesValuesThe Spare gate's own row.
StatusStatusData fieldsAny node, for conditional formatting and the summary strip.

Only Node ID and Parent ID are needed for a tree to draw. The others add checking, values and presentation. Any further column you bind, such as an asset ID or owner, is shown in the Node Inspector without being mapped, and on hover too when it is in Values or Tooltips.

Other column names that bind

RoleAlso recognised
ProbabilityProb, Failure Probability, Event Probability, Unavailability, Q
Failure rate (λ)Lambda, Rate, Hazard Rate
Repair rate (μ)Mu, Restoration Rate
Mission timeExposure Time, Exposure, Operating Time, Mission
Voting threshold (k)Threshold, K, M, VoteK, Minimum Votes, Required Count
Voting input count (n)VoteN, N, Total Inputs, Vote Inputs, Total Count
Priority sequenceSequence Order, Sequence Number, Branch Order, Input Order, Priority Order, Step, Event Order, Failure Order
Event stateHouse State, Switch State, On Off
Dormancy factorDormancy, Alpha
Spare modeSpare Type, Redundancy Type, Standby Type
Required sparesRequired Spares, Spares Required

Which row a value belongs on

Most values describe the node on their row. Priority sequence is the exception: it describes the connection from the gate to one of its inputs, so it goes on the input's row, not the gate's.

ValueBelongs onExample
Probability, failure rate, repair rate, mission timeThe event it describes.Relief valve fails to lift: Probability 0.018
Voting threshold (k), voting input count (n)The voting gate.Two of three protections lost: Vote Threshold 2, Vote Input Count 3
Priority sequenceEach input of the ordered gate.Duty pump seal fails: 1. Standby pump seal fails dormant: 2
Spare mode, required sparesThe Spare gate.Duty pump with standby: Cold, 1
Dormancy factorEach input of the Spare gate.Standby pump seal fails dormant: 0
Event stateThe house or zero event.Turnaround in progress: FALSE

A complete example

A loss-of-containment tree using an OR gate, an AND gate, a voting gate, a cold Spare gate, an undeveloped event and a house event. It validates with no errors under IEC 61025:2006. Cells with no value are left blank. Relationship Type is left out because every connection is an ordinary input, which is what a blank cell means.

Node IDParent IDNode TypeLabelOrderProbabilityVote ThresholdVote Input CountPriority SequenceSpare ModeSpare Required CountDormancy FactorEvent State
TETop EventLoss of containment from transfer line
G-TOPTEOR GateAny release path
IE-CORG-TOPIntermediate EventCorrosion breach1
G-CORIE-CORAND GateCoating and inspection both fail
BE-COATG-CORBasic EventInternal coating degraded0.012
BE-INSPG-CORBasic EventInspection misses wall loss0.04
IE-OPG-TOPIntermediate EventOverpressure rupture2
G-OPIE-OPVoting GateTwo of three protections lost23
BE-PSVG-OPBasic EventRelief valve fails to lift0.018
BE-ALMG-OPBasic EventHigh-pressure alarm fails0.011
BE-TRIPG-OPBasic EventPump trip fails0.022
IE-SEALG-TOPIntermediate EventPump seal release3
G-SEALIE-SEALSpare GateDuty pump with standbyCold1
BE-P1G-SEALBasic EventDuty pump seal fails0.0061
DE-P2G-SEALDormant EventStandby pump seal fails dormant0.00420
UE-THIRDG-TOPUndeveloped EventThird-party damage (not developed)40.002
HE-TURNG-TOPHouse EventTurnaround in progress50FALSE
The loss-of-containment fault tree drawn by Ataytis Assurance: an OR gate under the top event, AND, voting and spare gates beneath three intermediate events, and an undeveloped event and a house event beside them.
The example drawn under IEC 61025:2006. The voting gate carries 2/3, and the Spare gate's inputs are numbered [1] and [2] from their Priority Sequence.

An event under more than one gate

Give the event one row for each gate it feeds, with the same Node ID and a different Parent ID. It remains one event: selecting it selects all of its rows.

An event with nothing beneath it is drawn separately under each gate that uses it. An event with its own branch beneath it is drawn once, connected to each gate. Advisory diagnostics note repeated events, because they matter to any probability calculated outside the visual.

More than one tree in a table

Add a Diagram ID column and give every row of a tree the same value. Add Diagram Name for a readable name. A Diagram Type column holding Fault Tree Analysis, Fault Tree, FTA or FT helps the visual open a fault tree when the table also holds other diagram types.

When a table restates each tree once per snapshot or period, filter or slice it to a single snapshot, so each node carries one set of values.

Checks before binding the table

  • Trim the Node ID and Parent ID columns. An identifier that differs only by a space does not join.
  • Type probability, rate, time, threshold, count and sequence columns as numbers. A text column is not bound to a numeric role automatically.
  • Give every row a Node ID. Completely empty rows are skipped; a row with content and no Node ID is reported.
  • Leave Parent ID blank on the top event. A blank cell, or one holding only spaces, means no parent.
  • Keep node type wording as your source writes it. Case, spaces, underscores, hyphens and full stops are ignored, and unrecognised wording can be mapped under Node type values on the Data Mapping tab.
Preparing fault tree data — Ataytis Assurance | AtaytisTech