ServicesHow We WorkSectorsAcademyLibraryAboutContactOpen the Toolbox →
Static & Safety Equipment

Process safety: HAZOP, LOPA & SIL

A relief valve is one barrier; process safety is the discipline of working out which barriers a hazard needs, and how good each must be. It runs from finding the hazards systematically (HAZOP), through crediting the protection layers already present and counting the shortfall (LOPA), to specifying how reliable the engineered safety function must be (SIL). This guide walks that chain β€” and an interactive turns a hazard scenario into a required SIL.

HAZOPLOPASIL Β· IEC 61511RRF / PFD
⚡ TL;DR

HAZOP finds hazards systematically β€” a team applies guidewords (No, More, Less, Reverse…) to each part of the process to surface credible deviations and their causes and consequences.

LOPA (layers of protection analysis) is the order-of-magnitude maths: take the initiating-event frequency, divide by the risk reduction of each independent protection layer, and compare to the tolerable frequency. The shortfall is the risk reduction the safety function must provide.

SIL (safety integrity level, IEC 61511) grades that function by its risk reduction factor RRF = 1/PFD: SIL 1 = 10–100Γ—, SIL 2 = 100–1000Γ—, SIL 3 = 1000–10,000Γ—, SIL 4 = 10,000–100,000Γ—. The model turns a scenario into the required SIL.

1 · Risk in layers

Process safety rests on one idea: a major accident almost never has a single cause, so it should never have a single barrier. Between a normal upset and a catastrophe sits a series of independent layers of protection β€” the “Swiss cheese” or onion model. Each layer reduces the risk by some factor; the accident only happens if an initiating event occurs and every layer fails. The layers split into two kinds:

Process safety is the work of choosing those layers and proving they add up to tolerable risk. Three linked methods do it, in order.

2 · HAZOP — finding the hazards

A HAZOP (hazard and operability study) is a structured, team-based review of a design. The plant is split into nodes (e.g. a line or vessel), and for each one the team applies guidewords to process parameters to provoke every credible deviation:

GuidewordExample deviation
No / NoneNo flow (pump stopped, line blocked)
MoreMore pressure, more temperature, more level
LessLess flow, less cooling
ReverseReverse / backflow
As well as / Part ofContamination; wrong composition

For each deviation the team records the causes, the consequences, the existing safeguards, and any recommendations. HAZOP is deliberately exhaustive and qualitative β€” its job is to make sure nothing credible is missed. The serious scenarios it surfaces are then passed to LOPA to be quantified.

3 · LOPA — counting the layers

LOPA is a simplified, semi-quantitative risk calculation that sits between qualitative HAZOP and full quantitative risk analysis. It works in orders of magnitude, which is enough to make the decision and keeps it auditable. For a chosen scenario:

fmitigated = finitiating Γ— PFD₁ Γ— PFDβ‚‚ Γ— …   (each IPL β‰ˆ Γ·10 or Γ·100) Multiply the initiating-event frequency by the probability-of-failure-on-demand of each independent protection layer. Compare the result to the tolerable target frequency for that consequence.

The discipline is in what counts as an independent protection layer (IPL). To be credited, a layer must be independent of the initiating cause and the other layers, effective at preventing the consequence, and auditable. A typical IPL buys one order of magnitude (PFD β‰ˆ 0.1); a well-engineered relief valve or a SIL-rated function can buy more. The BPCS loop that caused the upset can’t also be credited as a layer against it β€” a common and dangerous double-count.

If the existing layers don’t get the frequency down to tolerable, the gap is the job of a new safety instrumented function β€” and its size sets the SIL.

4 · SIL — sizing the safety function

A safety instrumented function (SIF) is a specific protection loop β€” sensor → logic solver → final element (e.g. high-pressure transmitter → trip logic → shutdown valve). Its required performance is its safety integrity level (SIL), graded by the risk reduction factor it must deliver:

RRF = 1 / PFDavg    required RRF = f(after other IPLs) / ftolerable PFDavg = average probability of failure on demand. SIL 1: RRF 10–100 (PFD 0.1–0.01). SIL 2: 100–1000. SIL 3: 1000–10,000. SIL 4: 10,000–100,000 (rare; usually redesign instead). Higher SIL means more redundancy, better diagnostics and more proof-testing.

The interactive runs the whole LOPA-to-SIL chain: set how often the scenario initiates, how much the existing layers already reduce it, and how rare the consequence must be β€” and it returns the SIL the safety function has to achieve.

Interactive — LOPA to SIL

Live model
How often the upset starts (events/year)
Combined risk reduction of credited layers
How rare the consequence must be
After existing layers
β€”
events / yr
Required RRF
β€”
from the new SIF
Required SIL
β€”
IEC 61511
SIF PFDavg
β€”
≀ this
The risk-reduction ladder
From initiating frequency down to the tolerable target (log scale)
initiatingafter existing IPLsSIF reductiontolerable target
Model: LOPA arithmetic β€” fafter = finitiating / IPL-RRF; required SIF RRF = fafter / ftolerable (floored at 1); SIL band per IEC 61511 (SIL 1 = 10–100, SIL 2 = 100–1000, SIL 3 = 1000–10,000, SIL 4 = 10,000–100,000), PFD = 1/RRF. Order-of-magnitude by design β€” a real LOPA uses a documented IPL register, conditional modifiers and a rulebook.

Two truths fall out of playing with it. You rarely need SIL 3+: if a scenario demands it, the right answer is usually to reduce the initiating frequency or add an independent non-instrumented layer, because very high SIL is expensive and hard to sustain. And the SIL is only as real as the proof testing: a SIL-2 function only delivers SIL-2 if it’s tested at the interval the calculation assumed β€” which makes functional safety a maintenance commitment, not just a design one.

The safety lifecycle is a maintenance lifecycle too. Every credited layer β€” the relief valve, the trip transmitter, the shutdown valve β€” carries a proof-test task at a defined interval, prioritised by criticality and tracked in the CMMS like any other preventive task. A missed SIS proof test silently erodes the SIL the whole risk case depends on. Functional safety and reliability engineering are the same data, viewed for safety instead of cost.

Key takeaways

Related guides