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

Field mapping

How bound columns are matched to roles automatically, how to map them by hand, and which roles each diagram type reads.

The Data Mapping tab

Data Mapping lists every role the selected diagram type reads, required roles first. Beside each role's name, a small note says what it applies to: node, edge, diagram or value. Each role has a dropdown of the fields bound to the visual, labelled with the well each came from, for example Probability · Value. A field whose type does not suit the role is marked type mismatch.

The Data Mapping tab of the Ataytis Assurance editor with a Markov state diagram in the preview and the Field mapping list on the right, showing the column mapped to each role.
Field mapping for a Markov state diagram. Each role shows the column mapped to it and the well it came from, such as StateID · Data. Node ID is marked Required, and the note on the right says whether a role applies to a node, an edge or the diagram.
Status under a roleMeaning
Required mappingA required role has nothing mapped. The diagram will not build until it is mapped.
Mapped field is no longer availableThe mapped column was removed from the visual or is no longer in the model.
More than one field matches this saved mappingTwo bound fields match the saved mapping. Choose the right one.

Automatic binding

When a role has nothing mapped, the visual looks for a bound column whose name matches one of the names that role is known by. Matching ignores case, spaces and punctuation, so Node_ID, node id and NodeID are the same name. A column is used for one role only.

RoleExamples of column names that bind automatically
Node IDNode ID, ID, Event ID, Element ID, Code, Reference, State ID
Connected nodeParent ID, Parent, Connected node, Connected to, Output, Predecessor, Target, To state, Next state
Node typeNode type, Type, Event type, Symbol, Gate type, Category, Kind, State class
LabelLabel, Description, Title, Event name, Node name, State label
Relationship typeRelationship type, Relationship, Link type, Edge type, Transition type
OrderOrder, Sequence, Sort order, Position, Rank
Diagram IDDiagram ID, Diagram, Tree ID, Model ID, Analysis ID
Diagram nameDiagram name, Diagram title, Analysis name, Model name
StatusStatus, State, Condition, Current status
ProbabilityProbability, Unavailability, Q, Branch probability

Only the roles the selected diagram type reads are matched. Numeric roles bind only to numeric columns: a text column named Probability is left unmapped rather than mapped to a role it would fail.

Mapping by hand

Choose a field in any role's dropdown. Choosing Not mapped is kept as a decision: automatic binding does not put the column back on the next refresh.

Mappings are stored against the field itself, not its position in the well. Reordering fields does not change a mapping, and removing a mapped field produces a mapping message instead of another column being used in its place.

A saved mapping that points at a column the current table does not contain is not treated as your choice. Automatic binding runs again for that role.

Roles every diagram type reads

RoleWhat it does
Node IDIdentifies a node. Rows with the same Node ID become one node.
Connected nodeThe node this row connects to.
Node typeWhat the node is. Decides its symbol and which rules apply.
LabelText drawn on the node.
Secondary labelA second line of text on the node.
Relationship typeWhat the connection means, where the method distinguishes kinds of connection.
Relationship labelText drawn on the connection.
OrderThe order of nodes that sit side by side.
Diagram IDSeparates several diagrams held in one table.
Diagram typeHelps choose which diagram to open when the table holds several.
Diagram nameA readable name for each diagram, used in the diagram picker.
Linked diagram ID and Linked diagram typePoint a node at another diagram, such as the target of a fault tree transfer.

Roles specific to each diagram type

Diagram typeAdditional roles
Fault Tree AnalysisProbability, Failure rate (λ), Repair rate (μ), Mission time, Voting threshold (k), Voting input count (n), Priority sequence, Event state, Dormancy factor, Spare mode, Required spares, Status
Bow-Tie Risk AnalysisThreat, Barrier, Consequence, Top event, Escalation factor, Escalation control, Status, Health
Event Tree AnalysisBranch label, Probability, Frequency, Status
Reliability Block DiagramReliability, Availability, Failure rate, Status, Vote threshold (m), Vote input count (n)
Goal Structuring NotationStatus, Health, Relationship ID, Challenged relationship, Identifier, Module reference, Decorators
Markov State DiagramTransition rate, State probability, Status, Absorbing state, Initial state, State class, Failed elements, State identifier, Transition ID

Units are never converted. A failure rate, repair rate, mission time, frequency or transition rate is shown in whatever unit the report model uses.

Field mapping — Ataytis Assurance | AtaytisTech