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 · Reliability Block Diagram

Preparing reliability block data

The table a reliability block diagram needs: one row per connection naming the next block, the columns and what to call them, series, parallel, standby and m-out-of-n structures, and a complete worked example.

One row per connection, naming the next block

Each row names a block and, in Connected Node ID, the block it leads to. A block that leads to several blocks, such as the point where parallel paths split, has one row for each. The output's row leaves Connected Node ID blank.

Values on a row describe that row's block. When a block has several rows, give them the same values; rows that disagree are reported, and the first row's values are used. Relationship Type on a row describes the connection from that block to the next.

  1. The input

    One row leading to the first block.

  2. Each block in series

    One row leading to the next block.

  3. A parallel split

    One row for each path, leading to the first block of that path.

  4. The end of each parallel path

    Its last block leads to the block or junction where the paths merge.

  5. An m-out-of-n block

    Each of its n blocks leads to it. Its own row carries Vote Threshold (m) and Vote Input Count (n).

  6. The output

    One row with Connected Node ID left blank.

Columns

ColumnMaps toWellFill it in on
Node IDNode IDData fieldsEvery row.
Connected Node IDConnected nodeData fieldsEvery row except the output.
Node TypeNode typeData fieldsEvery row.
LabelLabelData fieldsEvery row.
Relationship TypeRelationship typeData fieldsOptional. A blank cell is a series path.
OrderOrderData fieldsBlocks that sit side by side, such as parallel paths, to set their order from the top.
ReliabilityReliabilityValuesAny block.
AvailabilityAvailabilityValuesAny block.
Failure RateFailure rateValuesAny block.
StatusStatusData fieldsAny block, for colouring and the summary strip.
Vote ThresholdVote threshold (m)ValuesThe m-out-of-n block's row.
Vote Input CountVote input count (n)ValuesThe m-out-of-n block's row.
Diagram IDDiagram IDData fieldsEvery row, when the table holds more than one diagram.
Diagram NameDiagram nameData fieldsEvery row, for a readable name in the diagram picker.

Only Node ID has to be mapped. Any other column, such as an asset ID, an MTTR or a last tested date, needs no mapping.

Other column names that bind

RoleAlso recognised
ReliabilityR
AvailabilityUptime
Failure rateLambda, Rate, Hazard Rate
Vote threshold (m)Required Count, Required Blocks, Required Channels, Threshold, Minimum Votes, M, K
Vote input count (n)Total Count, Total Blocks, Total Channels, Total Inputs, Vote Inputs, N

These bind only to number columns. A name with a unit added, such as Failure Rate per Hour, does not bind; call the column Failure Rate, or map it by hand on the Data Mapping tab. A % sign is ignored, so Availability % binds.

A complete example

A cooling water supply: a power supply, a duty pump with a standby pump in parallel, a heat exchanger train, and three temperature transmitters voting two out of three. It validates with no errors or warnings. Reliability, Vote Threshold and Vote Input Count are in Values, set to Don't summarize. Cells with no value are left blank.

Node IDConnected Node IDNode TypeLabelRelationship TypeOrderReliabilityVote ThresholdVote Input CountStatus
INPSUInputCooling demand
PSUSPLITComponentPower supply PSU-10.998Healthy
SPLITPMP-AParallel JunctionPump splitParallel
SPLITPMP-BParallel JunctionPump splitStandby
PMP-AMERGEComponentDuty pump P-101A10.95Healthy
PMP-BMERGEStandby ComponentStandby pump P-101B20.93Degraded
MERGEHXParallel JunctionPump merge
HXTT-1SubsystemHeat exchanger train0.99Healthy
HXTT-2SubsystemHeat exchanger train0.99Healthy
HXTT-3SubsystemHeat exchanger train0.99Healthy
TT-1VOTEComponentTemperature transmitter TT-110.985Healthy
TT-2VOTEComponentTemperature transmitter TT-220.985Healthy
TT-3VOTEComponentTemperature transmitter TT-330.985Failed
VOTEOUTVotingTrip logic23
OUTOutputCooling delivered
The cooling water reliability block diagram drawn by Ataytis Assurance under IEC 61078:2016, with duty and standby pumps in parallel between a split and a merge, a heat exchanger train, and three transmitters feeding a 2/3 voting block.
The example drawn under the IEC 61078:2016 profile: filled dots for the terminals and junctions, square-cornered blocks, and 2/3 written under Trip logic.

Pump split has one row per path, and its second row is a Standby path, drawn green and dashed under the Custom profile. Heat exchanger train has one row for each transmitter it leads to, with the same values on all three. Trip logic needs two of its three transmitters, and 2/3 is written under it.

Parallel paths, with or without junctions

The split and merge can be Parallel Junction rows, as in the example, drawn as small dots. They can also be left out: the block before the paths leads to the first block of each path, and the last block of each path leads to the block after. Either way the paths stay side by side, in Order from the top.

m-out-of-n blocks

  • Vote Threshold (m) is how many of the block's inputs must work. Vote Input Count (n) is how many feed it.
  • m must be a whole number of 1 or more, and no more than n.
  • n is checked against the number of blocks that actually lead to the block.
  • With both mapped, m/n is written beneath the block, unless its label or secondary label already says it, as in 2/3 compute capacity.

If your table names the previous block

Set Data Mapping → Connection column → Reads as to Connected node comes before this row. Left on the default, such a table is read backwards, and the Validation tab reports No complete path connects the input side to the output side., together with errors that the input has something leading into it and the output carries on into another block.

Without a Node Type column

Every block is read as a component. The block with nothing before it and the block with nothing after it are taken as the input and output, so the diagram still draws, but the last block is reported with Nothing leaves this block, so no path through it reaches the output. Map a Node Type column to name the input and output and to use the other block types.

Checks before binding the table

  • Trim Node ID and Connected Node ID. An identifier that differs only by a space does not join.
  • Give every row of a block the same values.
  • Store reliability and availability the same way throughout, all as fractions or all as percentages. Nothing checks the range, and conditional formatting compares the stored number.
  • Set Reliability, Availability, Failure Rate and the vote counts to Don't summarize.
  • Use one Input and one Output.
Preparing reliability block data — Ataytis Assurance | AtaytisTech