Adding Failure Effects To Hazop: Colin Feltoe B.SC), MIPENZ, C.Eng P.Eng (UK) (Can) (NZ)
Adding Failure Effects To Hazop: Colin Feltoe B.SC), MIPENZ, C.Eng P.Eng (UK) (Can) (NZ)
Starting each line with a failure analysis has several benefits. Most causes generated by the
traditional guidewords are captured at this stage, and the team must do some solid analysis
from the start improving their understanding of the line dynamics before the classical
guidewords are applied. The quality of the finished product, namely the HAZOP report, in
the author’s opinion, is greatly improved. One disadvantage is that lateral thinking can be
inhibited. It is suggested however, that not much lateral thinking goes on in practice, after a
few days HAZOP’ing.
The addition of failure effects to the HAZOP process will be demonstrated by example.
This will include deviations to be addressed in typical control systems (switches,
transmitters, protection devices) and process equipment items. For example, how can a
measurement offset (high or low) affect a control system or protection device? Can this
lead to a failure on demand and what will be the consequence? The thought process can be
interesting, particularly with complex control loops. Those familiar with instrumented
protection (IPF) reviews will recognise these questions and the relationship to safety
integrity level (SIL) determination which can be incorporated into the review if required.
Introduction:
It is proposed that a list of failures be generated (as causes) and analysed for each line
before the application of traditional HAZOP guidewords. This technique has been applied
by the author for several years with positive feedback from clients who have suggested the
method be shared. There are several benefits including:
i. An initial list of pertinent causes is immediately and easily generated for the
HAZOP team to tackle. This reduces the mental effort required for a long study.
ii. An improved understanding by the team of the line dynamics.
iii. Most of the issues raised by the traditional guidewords will have already been
raised so only additional issues need addressing and documenting.
iv. The likelihood of an omission is reduced, providing confidence that the
HAZOP has been rigorously carried out. This is a subjective view supported by
client feedback and the author’s experience.
v. The overall time required is not increased but may be reduced.
The views presented are those of the author having applied this method to approximately
100 HAZOP studies of varying size and are offered in the hope they will make HAZOPs
more effective.
Background:
HAZOP emerged as a diagnostic tool in the late 60’s and has remained the preferred
method for systematically identifying process plants hazards. It was initially used in the
petrochemical/oil and gas industries but now can be found in many others including dairy,
pulp and paper, power generation, mineral processing and mining. Some changes to the
method have emerged over the years. One example is to batch (or sequential) processes.
Traditionally HAZOP involves the selection of a line on a P&ID. This line is interrogated
by the application of guidewords such as more or less flow, pressure, temperature, level etc
to generate causes of deviations from the design intent. The consequence associated with
each cause is defined assuming any safeguards have failed. These (safeguards) are then
identified to determine if the design is sufficiently robust. If not, an action results. Where a
large number of action items are expected, a qualitative judgement of risk (assuming
existing controls are in place) can be made, possibly using a matrix or even the gut
judgement of the team. This enables the actions to be prioritised. Fig 1 shows a typical
HAZOP worksheet.
Fig 1 HAZOP WORKSHEET
Diagram: Line No:1 Design Intent:
Study Process Cause Consequence Safeguards Risk Actn Action By
No. Devn #
Line Comments:
2
C. Feltoe
3
C. Feltoe
4
C. Feltoe
HAZOP Worksheet
Diagram: DB 723-P- 11 rev D Line No:23 (red) Design Intent: Debutaniser feed to column bottoms, re-boil and
product to storage.
Study Process Cause Consequence Safeguards Risk Actn Action By
No. Deviation #
Line Comments:
1. TC 1 to control RVP below 69 kPa
2. Zero water assumed in feed other than under process upset.
23.1 Control/Eq FC-1 Fails Hi Reduced throughput Operator L
Failure – not significant observation of
(Lo Flow)* low tops temp
23.2 " FC-1 Fails Lo Hi feed to tower, Product lab H 1 Configure TAH on TI and AB
(Hi Flow) potential flooding, analysis (too late) TAL on TC1.
Off spec products. Operator
Significant observation of
reprocessing cost. temperatures.
23.3 " LC-1 Fails Lo Hi level, in tower, LSH L
(Hi Level) tray damage.
23.4 " LC-1 Fails Hi Lo Level , re-boiler LSL. H 2 Confirm if tubes CD
(Lo Level) tubes exposed, tube Vent sized for designed to run dry, if not
failure, C4 in hot oil. LCV fail open. revisit metallurgy
Vapour by pass to
storage, storage 3 Consider relocation of BC
overpressure. FCV-3 downstream of re-
boiler.
23.5 " LSH Fails on As Study23. 3 NA 4 Feed into IPF** review BC
(Hi level) demand
23.6 " LSL Fails on As study 23.4 NA 5 Feed into IPF* review BC
(Lo Level) demand
23.7 " RV-1 Spring Rapid tower Low likelihood L
(Hii Flow) Failure depressuring. CCTV on flare
Significant process with operator
upset. Equipment observation.
damage unlikely. Numerous alarms
23.8 " RV-1 Passes Loss of product to CCTV on flare L
(Hi Flow) flare
23.9 " TC-1 Fails Hi Lo bottoms Product lab M 6 Provide independent TI on BC
(Lo Temp) temperature, analysis. tray 3
condensate RVP high Operator
Loss of C4 product. observation of
C4 venting from storage vent
storage. (unlikely).
23.10 " TC-1 Fails Lo
(Hi Temp)
23.11 " FC-3 Fails Hi
(Lo Flow)
23.12 " FC-3 Fails Lo
(Hi Flow)
23.13 " HX-1 Leaks
(Impuities)
23.14 " HX-2 Leaks
(Impurities)
Once all the above causes have been addressed then the traditional guidewords can be
applied.
23.15 Hi Flow Operator set
point error
23.16 Misdirected Drain open or
Flow passing
23.17 Lo Flow Loss of Feed
5
C. Feltoe
Cause 1 Level Transmitter Fails High: This means there is an offset such that the
instrument is reading higher than the actual level. The controller will still be
controlling to the set point so the operator will be unaware of the fault.
Consequence Low level in the vessel, pump cavitation, possible seal failure and fire.
Eventual backflow if pump trips.
Safeguards Low level switch alarms and trips pump, operator observation of cavitation
(not considered likely).
Risk Medium
Action Quantify risk and consider backflow protection.
6
C. Feltoe
Cause 2 Level Transmitter Fails Low: The offset is now lower than the actual level
Consequence High Level with liquid carryover. Compressor damage – significant cost.
Safeguards High level switch alarms and trips compressor.
Risk High (Considered likely within life of plant)
Action Feed into IPF (Instrument Protection) review and provide protection with
appropriate SIL (Safety Integrity Level).
The next “cause” to be considered is the “failure on demand” of each level switch. The
consequence will be the same as for the transmitter failures. The required SIL level can
now be determined (or tabled for a separate meeting) and the system designed to provide
the required probability of failure on demand (fractional dead time/unavailability,
whichever terminology you care to use).
It is now common to have two level transmitters (one for control and the other for
independent safeguarding actions) rather than a level transmitter and two switches. The
total cost is similar once cabling etc has been included and a comparison between
transmitters is provided reducing the need for periodic calibration. Full function testing is
still required to verify the status of other elements in the system. While the use of a second
transmitter is an improvement, additional failures are introduced as follows.
“Fail Low” of the trip transmitter could result in a failure to trip on demand for a high level
or a spurious low level trip.
“Fail High” will be the reverse. Failure to trip on a low level or a spurious high level trip.
Fig 2b is an atmospheric feed vessel with a constant flow out and on/off make up based
upon the level switches. (A silly arrangement, but one which can be found. This guarantees
an incident every time a switch fails in service).
Cause 1 Level Switch Low (LSL) fails on demand: A demand is placed upon it
every time it is asked to operate.
Consequence The pump will cavitate eventually running dry. Worst case - pump
replacement. (Quick evaluation by leader: Cost ~ $3000 for each switch
failure. Failure rate ~ every 4 years for payback time of two years worth
spending ~$1500 to eliminate)
Safeguards None
Risk Low
Action Assess test frequency for switch and monitor performance.
7
C. Feltoe
8
C. Feltoe
Benefits:
The suggestion, to commence the study of each line by addressing the failure effects as
individual causes, does not change the principles upon which HAZOP is based. The
classical HAZOP guidewords are still applied after the failures have been analysed but only
additional issues are considered. It should be noted that a conscientious application of the
traditional guidewords alone should bring out all of the issues raised by the failure effects
application. But why wait? The HAZOP worksheet completed for fig 3 identifies all the
failure effect process deviations as “equipment or control system failure”. Study item
“23.1” could just as easily have been labelled “Low Flow”.
The quality of the review is of paramount importance and many factors can compromise
this. A large study can involve many P&ID’s and requires stamina from both the leader and
the team. After a few sessions, the sight of “High Flow” for the 57th time can induce an
attention deficit known as “analysis paralysis”. The number of visits to this guideword do
not change, but the mental burden is reduced. In addition, some team members find the
classical guidewords abstract, making the generation of “causes” hard work. It is easier to
generate a list of equipment and control system failures at the outset. By progressing along
a line, identifying all the failures associated with equipment and control systems, a list of
“causes” is immediately generated for the team to get stuck into. Having worked through
these, they will have a very good understanding of the line and it’s dynamics. The classical
guidewords are then applied. Only issues not already raised in the study of failure effects
are addressed and documented. It could be argued that time is saved in the generation of
“causes” but time saving is not the objective. HAZOP quality is the main issue.
9
C. Feltoe
The benefit of working in this way did not come as a blinding flash of inspiration for the
author. It resulted from undertaking many batch/sequential process HAZOPs where one
method of generating deviations is to assume each item is not in it’s desired state at each
stage in the process. The power of this simple approach slowly became apparent. Applying
the same principle to continuous processes was a logical step.
Why only failure effects and not failure modes?
So long as a failure is credible, it can be considered. Any failure having serious
consequences and thought to be sufficiently likely can then have its failure modes analysed
as a HAZOP action item. Note: Low likelihood is not the same as not credible. It may,
however, be a reason to accept risk.
An Additional Burden?
The author does not see the application of failure effects as an additional burden but rather
an enhancement to the existing methodology. If it is accepted that all the issues raised by a
review of the failure effects are necessary then there is no additional burden in review time
or documentation.
Conclusion:
Starting each line with a failure analysis has several benefits. Most causes that would be
generated by the traditional guidewords are captured at this stage, and the team must do
some solid analysis from the start improving their understanding of the line dynamics
before the classical guidewords are applied. The quality and completeness of the finished
product, namely the HAZOP report, in the author’s opinion, is greatly improved as is the
efficiency of the review.
Biography:
Colin has more than 35 years industrial experience including the oil& gas, petrochemical,
dairy and other associated industries. He established Safety Solutions Ltd in 1993 and now,
together with his son Paul, offers Process Safety, Training and Advanced Process Control
consultancy services. He has extensive experience in HAZOP and other process hazard
review techniques and has trained over 1000 HAZOP leaders and participants over the last
15 years. A qualified chemical engineer, Colin has professional registration in the UK,
Canada and New Zealand, where he is now based. In his spare time he moonlights as a Test
Certifier under New Zealand’s Hazardous Substances and New Organisms legislation and
as a New Zealand Qualifications Authority assessor.
10