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

Transfers and large trees

Continuing a fault tree in another diagram with Transfer In and Transfer Out, how readers follow a transfer, and keeping a large tree readable.

Continuing a tree in another diagram

A branch can be developed in its own diagram in the same table. On the main tree the branch is replaced by a Transfer In. On its own diagram the branch starts from a Transfer Out.

  1. Give each part its own Diagram ID

    Every row of the main tree carries one Diagram ID, and every row of the continued branch carries another.

  2. Add a Transfer In to the main tree

    A row with Node Type Transfer In whose Parent ID is the gate the branch belongs under. Set its Linked Diagram ID to the continued branch's Diagram ID.

  3. Start the branch with a Transfer Out

    On the continued diagram, a row with Node Type Transfer Out and no Parent ID. Set its Linked Diagram ID to the main tree's Diagram ID.

  4. Develop the branch beneath it

    The Transfer Out needs exactly one gate beneath it, as an intermediate event does.

  5. Give both halves the same label

    When a diagram holds several transfers, the matching label is how a reader following a transfer lands on the right one.

Diagram IDNode IDParent IDNode TypeLabelLinked Diagram ID
FTA_MFG_01_MAINMFG-G-TOPMFG-TOPOR GatePackaging cell outage causes
FTA_MFG_01_MAINMFG-TR-CTRL-INMFG-G-TOPTransfer InControl and safety platform unavailableFTA_MFG_02_CONTROL
FTA_MFG_02_CONTROLMFG-TR-CTRL-OUTTransfer OutControl and safety platform unavailableFTA_MFG_01_MAIN
FTA_MFG_02_CONTROLMFG-G-CTRL-TOPMFG-TR-CTRL-OUTOR GateControl and safety failure causes

A diagram that starts from a Transfer Out and has no top event is treated as a continued branch, so it is not reported for having no top event.

Every transfer needs exactly one reference: a Linked Diagram ID, or a Transfer relationship to its partner in the same diagram. A Linked Diagram ID that names a diagram not in the table is an error. Several Transfer Ins may link to the same diagram.

Following a transfer

Select a transfer on the report. The Node Inspector shows the diagram it links to, under Developed in for a Transfer In or Referenced from for a Transfer Out, with Open linked diagram. Opening it draws that diagram and selects the matching transfer there, with the Inspector open on it.

Following a transfer is not saved. The report opens on its starting diagram for the next reader.

Transfers within one diagram

To pair a Transfer In and a Transfer Out in the same diagram, give the Transfer Out a row whose Parent ID is the Transfer In and whose Relationship Type is Transfer, and leave Linked Diagram ID blank on both.

Keeping a large tree readable

  • Collapse a branch with the collapse button on its node. Readers can expand it again.
  • Select a node and use Focus branch in the Node Inspector to keep the node, the branch that develops it and its path to the top event prominent while the rest fades.
  • Use Search diagram to find a node by its text.
  • Set Density to Compact on the Diagram tab, or apply the Compact style preset.
  • Split the tree with transfers, so each diagram shows one branch in full.
Multiple diagrams in one tableDiagram ID, the diagram picker and the reader's diagram selector.Selecting a nodeFocus branch and the Node Inspector.Navigating a diagramCollapse and search.
Transfers and large trees — Ataytis Assurance | AtaytisTech