โ† Polyodos ยท Methods wiki ยท Industrial and technical risks
Method

๐ŸŽ€ Bow-Tie

The clearest representation of a risk scenario: causes and preventive barriers on the left, consequences and protective barriers on the right, on either side of the top event.

1What is a Bow-Tie?

The Bow-Tie (Bow-Tie) place l'top event at the centre of a bow-tie-shaped diagram: on the left, the causes that may lead to it, each intercepted by preventive barriers ; on the right, the consequences that may result, each mitigated by protective barriers. It is essentially a visual combination of a fault tree on the cause side and an event tree on the consequence side, focused on barriers rather than calculation.

Its strength is communication : a Bow-Tie diagram is much easier to read and present in a meeting than a HAZOP table or raw fault tree, while retaining equivalent analytical rigour.

Two detail levels are available: a basic mode with cause and consequence barriers but no calculation, for quick communication, and an advanced mode with logic gates, probabilistic quantification, and minimal cut sets, for a full fault-tree-equivalent analysis on both sides.

2Method steps

  1. Define the top event โ€” the scenario's tipping point (e.g. loss of containment).
  2. List the causes on the left, often taken from an existing PHA, HAZOP, or safety report.
  3. Position preventive barriers between each cause and the top event.
  4. List the consequences that may occur on the right.
  5. Position protective barriers between the top event and each consequence.
  6. (advanced mode) Quantify โ€” cause probabilities, barrier PFDs, resulting probabilities, and minimal cut sets.
A barrier counts only when it is truly independent and effective for that specific scenario. Copying the same generic barrier list to every top event indicates that the analysis lacks depth.

3Example completed in Polyodos

Section to be completed โ€” step-by-step import of a PHA safety-report scenario and positioning of barriers, with Polyodos screenshots in basic and advanced modes.

4Common mistakes

MistakeWhy it is a problem
Counting the same barrier twiceA barrier shared by several cause or consequence paths must not be counted as if every path had its own independent protection. Double counting overstates actual risk control.
Mixing preventive and protective barriersA preventive barrier acts before the top event, preventing escalation from the cause; a protective barrier acts after it, limiting the consequences. Placing barriers on the wrong side of the diagram distorts its meaning.
Confusing basic and advanced modesBasic mode contains neither probabilities nor logic gates. Expecting a quantified risk calculation from it is a misunderstanding, not a limitation of the tool.

5Further reading

FR