Defining Consequences (HAZOP)

For each Deviation, the HAZOP team should identify feasible Causes and likely Consequences.

Defining Consequences

For each Cause, define its Consequence(s):

• Click on the Consequence card next to the Cause.

• Enter a description for the Consequence. Take note that this is a required field.

• You can use “Intelligent Text Recognition” to add Equipment to the card. Just start typing the Equipment name in the description field and click <Ctrl> + <Space>. The selected Equipment will be added to the card, but it will also be added as a link in the description field. 

• Click the fold-out bar.

• Select the Top event.

  • For some Top events a Hazard is required. If you select one of these, you will also need to select one or more Hazards. Note: The Hazards are defined on the Hazard and effect register Tab . In this case the Hazard’s Risk (Severity) has already been defined in the register and will be copied to the Consequence; else

• If you selected another Top event, do a Risk Assessment:

  • Click somewhere on the “PACE” matrix to open the HAZOP Risk Matrix.

    

  • Select the desired Tolerability option from the dropdown. This will determine which Severities are used.

  • Select P (People) / A (Asset) / C (Community) / E (Environment) and then select the associated Consequence and Likelihood for each where applicable. Note: It is possible that a different RAM matrix has been defined for your site. To learn more about flexible RAM see Flexible Risk Assessment Matrix (RAM).

    

  • When done, click X to close the pop-up.

• If a LOPA is required:

  • Check the box.

    

  • Enter LOPA description.

  • When convenient, you can click Create LOPA, to directly create your LOPA. This can also be done at a later stage. If a LOPA has already been created, it will show here. You can use the LOPA name hyperlink to navigate there.

  • Note 1: When you create a LOPA from a Consequence, the Consequence and its Severity will be copied to the LOPA. Also, the Cause (and its Frequency) will be copied as an Initiating Event, the Exiting safeguards will be copied as Barriers to the LOPA, and the ALARP note are copied. These objects will all be synced with each other.

  • Note 2: A Top event cannot be changed after a LOPA has been connected to it.

• Select all Associated Equipment.

• Close the details window.

• Note: The Severity card is populated automatically with the Worst-case scenario of the Consequence. If a LOPA is required, the Create LOPA button will also show in the Severity card.

Adding / Copying / Pasting / Deleting Consequences

You can add an additional Consequence for the Cause, but only when the first Consequence has been defined.

Use the buttons in the Toolbar or the keyboard shortcuts to Add / Copy / Paste / Delete Consequences.

Linking Consequences

It is possible that different Causes can have the same Consequence. In this case you can create a copy of the first Consequence and then link the Consequences (manually). All the Consequence child objects (Existing safeguards and Recommendations) will then automatically be replicated and linked as well (even when you create a new child object, it will also be replicated and linked).

When objects are linked, they will always be synced, with one exception: On the Existing safeguard the Validation section remains unlinked. This way it is possible to indicate an Existing safeguard as Not Valid for a specific Cause-Consequence combination.

When a LOPA is connected to a Consequence, it will thus also automatically be connected to all linked Consequences and their associated Causes. All the associated Causes will be copied to the LOPA as Initiating Events.

To link two Consequences:

• Copy the desired Consequence, select that card where you want to paste and click the paste & link button   (or use <Ctrl> + <Alt> + <L>); or

• Create a new Consequence and click on the fold-out. Then enter the Consequence number to which you want to Link this Consequence in the Copy from field and check the Keep Linked box.

When objects are linked, a link icon will show on the cards.

Preventing duplicate Cause/Consequence scenario's being sent to LOPAs

To prevent duplicate Cause/Consequence scenario's to be sent to the LOPA when a LOPA is linked to a Cause/Consequence, the following should be kept in mind:

If you are (re)using a certain Cause/Consequence combination used before on a different Deviation in the same HAZOP, this Cause/Consequence combination should not be copy/paste linked to the already existing Cause/Consequence combination. Instead, a textual reference should be made to the previously created cause/consequence combination in the HAZOP (e.g. refer to consequence of Node 1.4.1.2).