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 · Markov State Diagram

Preparing Markov data

The table a Markov diagram needs: one row per transition from the state it leaves to the state it reaches, which row each value goes on, the columns and what to call them, and a complete worked example.

One row per transition

Each row is a transition: the state it leaves in State ID, the state it reaches in Connected State ID, and its rate. A state with three transitions leaving it has three rows.

Every state needs a row of its own. A state nothing leaves, such as an absorbing state, has one row with Connected State ID left blank. Without that row, the state is not drawn, the transition into it is dropped, and the Validation tab reports A relationship references a node that is not present.

Transition Type, Transition Rate, Transition Label and Relationship ID on a row describe that row's transition. Everything else on the row describes the state it leaves, so give every row of a state the same state values: label, identifier, probability, status and flags.

Columns

ColumnMaps toWellFill it in on
State IDNode IDData fieldsEvery row: the state the transition leaves.
Connected State IDConnected nodeData fieldsEvery row except a state nothing leaves: the state the transition reaches.
Node TypeNode typeData fieldsEvery row. Optional; without it every state is a plain state.
State LabelLabelData fieldsEvery row: what the state means.
State IdentifierState identifierData fieldsOptional. The short name drawn in the symbol, such as 0 or 1A. Falls back to the State ID.
Transition TypeRelationship typeData fieldsTransition rows: Failure, Repair or Transition.
Transition LabelRelationship labelData fieldsOptional. Words for the arrow, such as Pump fails.
Transition RateTransition rateValuesTransition rows.
State ProbabilityState probabilityValuesEvery row of a state, when you have it.
StatusStatusData fieldsEvery row of a state, for colouring and the summary strip.
Relationship IDTransition IDData fieldsOptional. An identifier for each transition.
Diagram IDDiagram IDData fieldsEvery row, when the table holds more than one model.
Diagram NameDiagram nameData fieldsEvery row, for a readable name in the diagram picker.

Only Node ID has to be mapped. The flag columns a register often keeps beside its states, for absorbing and initial states, a state class and a count of failed elements, are covered on States and transitions.

Other column names that bind

RoleAlso recognised
Node IDState ID, State Code, From State, From State ID, and the names every diagram type uses
Connected nodeConnected State ID, Connected State, To State, To State ID, Next State, Next State ID, Successor State
LabelState Label, Label, Description
State identifierState Identifier, Identifier, Display ID, Tag
Relationship typeTransition Type, Relationship Type
Relationship labelTransition Label, Relationship Label
Transition rateTransition Rate, Rate, Transition Intensity, Intensity, Rate per Hour, Rate per Year, Rate per Unit Time, Transition Rate per Hour, Transition Rate per Year, Transition Rate per Million Hours
State probabilityState Probability, Probability, Steady State Probability, State Prob, Occupancy, Occupancy Probability, Current State Probability, Current Probability
Transition IDRelationship ID, Edge ID, Link ID, Connection ID, Relation ID, Rel ID

If the diagram shows states and no arrows, the connection column has not bound. Name it Connected State ID, To State or Next State, or map it to Connected node by hand.

A complete example

Two duty pumps: both available, one failed, both failed, and a casing rupture the system cannot recover from. Each failure has a repair back, apart from the rupture. It validates with no errors, warnings or notes. Transition Rate and State Probability are in Values, set to Don't summarize. Cells with no value are left blank.

State IDConnected State IDNode TypeState LabelState IdentifierTransition TypeTransition RateState ProbabilityStatus
S0S1Initial StateBoth pumps available0Failure0.00020.9978Healthy
S1S0Degraded StateOne pump failed1Repair0.1250.0016Degraded
S1S2Degraded StateOne pump failed1Failure0.00010.0016Degraded
S2S1Failed StateBoth pumps failed2Repair0.06250.0005Failed
S2S3Failed StateBoth pumps failed2Failure0.000010.0005Failed
S3Absorbing StatePump casing ruptured30.0001Failed
The two-pump Markov diagram drawn by Ataytis Assurance under the Custom profile, with four states from both pumps available to pump casing ruptured, red failure and green dashed repair transitions labelled with their rates, and a probability in each state.
The example drawn under the Custom profile: states coloured by type, failures in red, repairs green and dashed, and a heavier border on the absorbing state.

The states run from S0 on the left to S3 on the right. Each arrow carries its rate, because the table has no transition label, and each state has its probability beneath it. S1 and S2 each have two rows, one per transition leaving them, with the same state values on both.

If your table names the state a transition comes from

Some tables give each row the state reached and name the state it came from. For those, set Data Mapping → Connection column → Reads as to Connected node comes before this row.

Left on the default, every arrow points the wrong way, and because loops are allowed the diagram says little about it. The clearest signs are an absorbing state reported with An absorbing state is one the system cannot leave, but a transition leaves this one., and a state reported as unreachable.

Checks before binding the table

  • Trim State ID and Connected State ID. An identifier that differs only by a space does not join.
  • Give every state a row, including an absorbing state nothing leaves.
  • Give every row of a state the same label, identifier, probability, status and flags.
  • Type the transitions Failure or Repair, or the states with Node Type. Without either, the layout has to guess which way the model runs.
  • List each transition once. Two rows for the same two states in the same direction with the same type are drawn as one arrow.
  • Give every transition a rate, or none of them.
  • Set Transition Rate and State Probability to Don't summarize, and give them a Power BI format if you want percentages or fixed decimals on the diagram.
Preparing Markov data — Ataytis Assurance | AtaytisTech