HAZOP

Hazard and Operability Study

Marvin Rausand
Department of Production and Quality Engineering
Norwegian University of Science and Technology
marvin.rausand@ntnu.no

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 1 / 44
Introduction
What is?
When to?
Background
Standards
Types of HAZOP

Team

Process HAZOP

Procedure HAZOP Introduction

Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 2 / 44
 What is HAZOP?

Introduction
What is?
A Hazard and Operability (HAZOP) study is a structured and
When to? systematic examination of a planned or existing process or
Background
Standards
operation in order to identify and evaluate problems that may
Types of HAZOP represent risks to personnel or equipment, or prevent efficient
Team operation.
Process HAZOP

Procedure HAZOP The HAZOP technique was initially developed to analyze

Reporting chemical process systems, but has later been extended to other
Conclusions types of systems and also to complex operations and to software
systems.

A HAZOP is a qualitative technique based on guide-words and is

carried out by a multi-disciplinary team (HAZOP team) during a
set of meetings.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 3 / 44
 When to perform a HAZOP?

Introduction
What is?
The HAZOP study should preferably be carried out as early in the
When to? design phase as possible - to have influence on the design. On
Background
Standards
the other hand; to carry out a HAZOP we need a rather complete
Types of HAZOP design. As a compromise, the HAZOP is usually carried out as a
Team final check when the detailed design has been completed.
Process HAZOP

Procedure HAZOP
A HAZOP study may also be conducted on an existing facility to
Reporting
identify modifications that should be implemented to reduce risk
Conclusions
and operability problems.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 4 / 44
 When to perform a HAZOP? - (2)

Introduction
What is?
HAZOP studies may also be used more extensively, including:
When to?
Background
Standards ❑ At the initial concept stage when design drawings are
Types of HAZOP
available
Team
❑ When the final piping and instrumentation diagrams (P&ID)
Process HAZOP

Procedure HAZOP
are available
Reporting
❑ During construction and installation to ensure that
Conclusions recommendations are implemented
❑ During commissioning
❑ During operation to ensure that plant emergency and
operating procedures are regularly reviewed and updated as
required
– From Kyriakdis (2003)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 5 / 44
 HAZOP background

Introduction
What is?
❑ The basis for HAZOP was laid by ICI in 1963 and was based
When to? on so-called “critical examination” techniques
Background
Standards
❑ First guide: “A Guide to Hazard and Operability Studies”, ICI
Types of HAZOP and Chemical Industries Associations Ltd. 1977.
Team ❑ First main textbook: Kletz, T. A.: “Hazop and Hazan -
Process HAZOP
Identifying and Assessing Process Industry Hazards”,
Procedure HAZOP
Institution of Chemical Engineers.
Reporting
❑ See also: Kletz, T. A.: “Hazop – past and future”. Reliability
Conclusions
Engineering and System Safety, 55:263-266, 1997.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 6 / 44
 Standards and guidelines

Introduction
What is?
❑ IEC 61882. “Hazard and operability studies (HAZOP studies)
When to? – Application guide”. International Electrotechnical
Background
Standards
Commission, Geneva.
Types of HAZOP

Team
❑ Crawley, F., M. Preston, and B. Tyler: “HAZOP: Guide to
Process HAZOP
best practice. Guidelines to best practice for the process and
Procedure HAZOP chemical industries”. European Process Safety Centre and
Reporting Institution of Chemical Engineers, 2000
Conclusions
❑ Kyriakdis, I.: “HAZOP - Comprehensive Guide to HAZOP in
CSIRO”, CSIRO Minerals, National Safety Council of
Australia, 2003

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 7 / 44
 Types of HAZOP

Introduction
What is?
❑ Process HAZOP
When to?
Background
✦ The HAZOP technique was originally developed to assess
Standards plants and process systems
Types of HAZOP

Team ❑ Human HAZOP

Process HAZOP
✦ A “family” of specialized HAZOPs. More focused on
Procedure HAZOP
human errors than technical failures
Reporting

Conclusions ❑ Procedure HAZOP

✦ Review of procedures or operational sequences
Sometimes denoted SAFOP - SAFe Operation Study
❑ Software HAZOP
✦ Identification of possible errors in the development of
software

Only Process HAZOP and Procedure

Marvin Rausand, October 7, 2005
HAZOP are covered in this
System Reliability Theory (2nd ed), Wiley, 2004 – 8 / 44

presentation.
Introduction

Team
Team members
Good participants
HAZOP meeting
HAZOP recording

Process HAZOP

Procedure HAZOP

Reporting
HAZOP team and meetings
Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 9 / 44
 Team members and responsibilities

Introduction
❑ HAZOP team leader
Team
Team members
Responsibilities:
Good participants
HAZOP meeting ✦ Define the scope for the analysis
HAZOP recording ✦ Select HAZOP team members
Process HAZOP
✦ Plan and prepare the study
Procedure HAZOP
✦ Chair the HAZOP meetings
Reporting

Conclusions → Trigger the discussion using guide-words and

parameters
→ Follow up progress according to schedule/agenda
→ Ensure completeness of the analysis

The team leader should be independent (i.e., no responsibility for

the process and/or the performance of operations)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 10 / 44
 Team members and responsibilities (2)

Introduction
❑ HAZOP secretary
Team
Team members
Responsibilities:
Good participants
HAZOP meeting ✦ Prepare HAZOP worksheets
HAZOP recording ✦ Record the discussion in the HAZOP meetings
Process HAZOP
✦ Prepare draft report(s)
Procedure HAZOP

Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 11 / 44
 Team members

Introduction
❑ HAZOP team members
Team
The basic team for a process plant will be:
Team members
Good participants
HAZOP meeting ✦ Project engineer
HAZOP recording ✦ Commissioning manager
Process HAZOP
✦ Process engineer
Procedure HAZOP
✦ Instrument/electrical engineer
Reporting
✦ Safety engineer
Conclusions

Depending on the actual process the team may be enhanced

by:

✦ Operating team leader

✦ Maintenance engineer
✦ Suppliers representative
✦ Other specialists as appropriate

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 12 / 44
 How to be a good HAZOP participant

Introduction
❑ Be active! Everybody’s contribution is important
Team
Team members
❑ Be to the point. Avoid endless discussion of details
Good participants ❑ Be critical in a positive way - not negative, but constructive
HAZOP meeting
HAZOP recording ❑ Be responsible. He who knows should let the others know
Process HAZOP

Procedure HAZOP

Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 13 / 44
 HAZOP meeting

Introduction
Proposed agenda:
Team
Team members
Good participants
1. Introduction and presentation of participants
HAZOP meeting 2. Overall presentation of the system/operation to be analyzed
HAZOP recording
3. Description of the HAZOP approach
Process HAZOP

Procedure HAZOP
4. Presentation of the first node or logical part of the operation
Reporting
5. Analyze the first node/part using the guide-words and
Conclusions parameters
6. Continue presentation and analysis (steps 4 and 5)
7. Coarse summary of findings

Focus should be on potential hazards as well as potential

operational problems
Each session of the HAZOP meeting should not exceed two hours.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 14 / 44
 HAZOP recording

Introduction
The findings are recorded during the meeting(s) using a HAZOP
Team
work-sheet, either by filling in paper copies, or by using a
Team members computer connected to a projector (recommended).
Good participants
HAZOP meeting
HAZOP recording The HAZOP work-sheets may be different depending on the
Process HAZOP scope of the study - generally the following entries (columns) are
Procedure HAZOP included:
Reporting

Conclusions
1. Ref. no.
2. Guide-word
3. Deviation
4. Possible causes
5. Consequences
6. Safeguards
7. Actions required (or, recommendations)
8. Actions allocated to (follow-up responsibility)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 15 / 44
Introduction

Team

Process HAZOP
Prerequisites
HAZOP procedure
Modes of
operation
Process HAZOP
worksheet
Worksheet entries Process HAZOP
Process
parameters
Guidewords

Procedure HAZOP

Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 16 / 44
 Prerequisites

Introduction
As a basis for the HAZOP study the following information should
Team
be available:
Process HAZOP
Prerequisites
HAZOP procedure
Modes of ❑ Process flow diagrams
operation
Process HAZOP ❑ Piping and instrumentation diagrams (P&IDs)
worksheet
Worksheet entries
❑ Layout diagrams
Process
parameters
❑ Material safety data sheets
Guidewords ❑ Provisional operating instructions
Procedure HAZOP ❑ Heat and material balances
Reporting
❑ Equipment data sheets Start-up and emergency shut-down
Conclusions
procedures

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 17 / 44
 HAZOP procedure

Introduction
1. Divide the system into sections (i.e., reactor, storage)
Team
2. Choose a study node (i.e., line, vessel, pump, operating
Process HAZOP
Prerequisites instruction)
HAZOP procedure
Modes of
3. Describe the design intent
operation 4. Select a process parameter
Process HAZOP
worksheet 5. Apply a guide-word
Worksheet entries
Process 6. Determine cause(s)
parameters
Guidewords
7. Evaluate consequences/problems
Procedure HAZOP 8. Recommend action: What? When? Who?
Reporting 9. Record information
Conclusions 10. Repeat procedure (from step 2)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 18 / 44
 HAZOP procedure

Introduction
The HAZOP procedure may be illustrated as follows:
Team

Process HAZOP Divide section

Prerequisites into study nodes
HAZOP procedure
Modes of
operation
Process HAZOP Select a study node
worksheet
Worksheet entries
Process
Apply all relevant
parameters
Guidewords
Record consequences combinations of guide-
and causes and words and parameters.
Procedure HAZOP suggest remedies YES Any hazards or NO
Reporting operating problems?
Conclusions NOT SURE

Need more
information

HAZOP report

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 19 / 44
 Modes of operation

Introduction
The following modes of plant operation should be considered for
Team
each node:
Process HAZOP
Prerequisites
HAZOP procedure
Modes of ❑ Normal operation
operation
Process HAZOP ❑ Reduced throughput operation
worksheet
Worksheet entries
❑ Routine start-up
Process
parameters
❑ Routine shutdown
Guidewords ❑ Emergency shutdown
Procedure HAZOP ❑ Commissioning
Reporting
❑ Special operating modes
Conclusions

– Based on Kyriakdis (2003)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 20 / 44
 Process HAZOP worksheet

Introduction
Study title: Page: of
Team
Drawing no.: Rev no.: Date:
Process HAZOP HAZOP team: Meeting date:
Prerequisites
Part considered:
HAZOP procedure
Modes of Design intent: Material: Activity:
operation Source: Destination:
Process HAZOP Guide- Possible Conse- Actions Action
No. Element Deviation Safeguards Comments
worksheet word causes quences required allocated to
Worksheet entries
Process
parameters
Guidewords

Procedure HAZOP

Reporting

Conclusions
– Source: IEC 61882

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 21 / 44
 Worksheet entries

Introduction
❑ Node
Team
A node is a specific location in the process in which (the
Process HAZOP
Prerequisites deviations of) the design/process intent are evaluated.
HAZOP procedure Examples might be: separators, heat exchangers, scrubbers,
Modes of
operation pumps, compressors, and interconnecting pipes with
Process HAZOP
worksheet equipment.
Worksheet entries
Process
parameters
❑ Design Intent
Guidewords The design intent is a description of how the process is
Procedure HAZOP expected to behave at the node; this is qualitatively described
Reporting
as an activity (e.g., feed, reaction, sedimentation) and/or
Conclusions
quantitatively in the process parameters, like temperature,
flow rate, pressure, composition, etc.
❑ Deviation
A deviation is a way in which the process conditions may
depart from their design/process intent.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 22 / 44
 Worksheet entries - (2)

Introduction
❑ Parameter
Team
The relevant parameter for the condition(s) of the process
Process HAZOP
Prerequisites (e.g. pressure, temperature, composition).
HAZOP procedure
Modes of ❑ Guideword
operation
Process HAZOP A short word to create the imagination of a deviation of the
worksheet
Worksheet entries
design/process intent. The most commonly used set of
Process
parameters
guide-words is: no, more, less, as well as, part of, other than,
Guidewords and reverse. In addition, guidewords like too early, too late,
Procedure HAZOP instead of, are used; the latter mainly for batch-like processes.
Reporting
The guidewords are applied, in turn, to all the parameters, in
Conclusions
order to identify unexpected and yet credible deviations from
the design/process intent.

Guide-word + Parameter → Deviation

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 23 / 44
 Worksheet entries - (3)

Introduction
❑ Cause
Team
The reason(s) why the deviation could occur. Several causes
Process HAZOP
Prerequisites may be identified for one deviation. It is often recommended
HAZOP procedure to start with the causes that may result in the worst possible
Modes of
operation consequence.
Process HAZOP
worksheet
Worksheet entries
❑ Consequence
Process
parameters
The results of the deviation, in case it occurs. Consequences
Guidewords may both comprise process hazards and operability problems,
Procedure HAZOP like plant shut-down or reduced quality of the product.
Reporting
Several consequences may follow from one cause and, in turn,
Conclusions
one consequence can have several causes

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 24 / 44
 Worksheet entries - (4)

Introduction
❑ Safeguard
Facilities that help to reduce the occurrence frequency of the
Team
deviation or to mitigate its consequences. There are, in
Process HAZOP
Prerequisites
principle, five types of safeguards that:
HAZOP procedure
Modes of
operation 1. Identify the deviation (e.g., detectors and alarms, and human
Process HAZOP operator detection)
worksheet
Worksheet entries 2. Compensate for the deviation (e.g., an automatic control system
Process that reduces the feed to a vessel in case of overfilling it. These are
parameters
Guidewords
usually an integrated part of the process control)
3. Prevent the deviation from occurring (e.g., an inert gas blancket in
Procedure HAZOP
storages of flammable substances)
Reporting
4. Prevent further escalation of the deviation (e.g., by (total) trip of
Conclusions
the activity. These facilities are often interlocked with several units
in the process, often controlled by computers)
5. Relieve the process from the hazardous deviation (e.g., pressure
safety valves (PSV) and vent systems)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 25 / 44
 Process parameters

Introduction
Process parameters may generally be classified into the following
Team
groups:
Process HAZOP
Prerequisites
HAZOP procedure
❑ Physical parameters related to input medium properties
Modes of
operation
❑ Physical parameters related to input medium conditions
Process HAZOP ❑ Physical parameters related to system dynamics
worksheet
Worksheet entries ❑ Non-physical tangible parameters related to batch type
Process
parameters processes
Guidewords
❑ Parameters related to system operations
Procedure HAZOP These parameters are not necessarily used in conjunction with
Reporting guide-words:
Conclusions
✦ Instrumentation
✦ Relief
✦ Start-up / shutdown
✦ Maintenance
✦ Safety / contingency
✦ Sampling

– From Statoil Guideline HMS-T/99142

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 26 / 44
 Examples of process parameters

Introduction
Flow Composition pH
Team
Pressure Addition Sequence
Process HAZOP
Prerequisites Temperature Separation Signal
HAZOP procedure
Modes of
Mixing Time Start/stop
operation
Process HAZOP
Stirring Phase Operate
worksheet Transfer Speed Maintain
Worksheet entries
Process Level Particle size Services
parameters
Guidewords Viscosity Measure Communication
Procedure HAZOP Reaction Control
Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 27 / 44
 Guidewords

Introduction
The basic HAZOP guide-words are:
Team

Process HAZOP
Guide-word Meaning Example
Prerequisites
HAZOP procedure No (not, none) None of the design intent is achieved No flow when production is expected
Modes of
operation More Quantitative increase in a parameter Higher temperature than designed
Process HAZOP (more of, higher)
worksheet
Less Quantitative decrease in a parameter None of
Lower pressure
the design
thanintent
normal
is achieved
Worksheet entries
(lessof, lower)
Process
parameters As well as An additional activity occurs Other valves closed at the same time
Guidewords (more than) (logic fault or human error)

Procedure HAZOP Part of Only some of the design intention is Only part of the system is shut down
achieved
Reporting
Reverse Logical opposite of the design intention Back-flow when the system shuts down
Conclusions occurs

Other than Complete substitution - another activity Liquids in the gas piping
(other) takes place

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 28 / 44
 Additional guidewords

Introduction
Guide-word Meaning
Team

Process HAZOP Early / late The timing is different from the intention
Prerequisites
HAZOP procedure
Modes of Before / after The step (or part of it) is effected out of sequence
operation
Process HAZOP
worksheet Faster / slower The step is done/not done with the right timing
Worksheet entries
Process
parameters Where else Applicable for flows, transfer, sources and destinations
Guidewords

Procedure HAZOP

Reporting

Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 29 / 44
 Guideword + parameter

Introduction
Some examples of combinations of guide-words and parameters:
Team

Process HAZOP
Prerequisites ❑ NO FLOW
HAZOP procedure
Modes of Wrong flow path - blockage - incorrect slip plate - incorrectly
operation
Process HAZOP
fitted return valve - burst pipe - large leak - equipment failure
worksheet - incorrect pressure differential - isolation in error
Worksheet entries
Process
parameters ❑ MORE FLOW
Guidewords
Increase pumping capacity - increased suction pressure -
Procedure HAZOP
reduced delivery head - greater fluid density - exchanger tube
Reporting

Conclusions
leaks - cross connection of systems - control faults
❑ MORE TEMPERATURE
Ambient conditions - failed exchanger tubes - fire situation -
cooling water failure - defective control - internal fires
– Many more examples in Kyriakdis (2003)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 30 / 44
Introduction

Team

Process HAZOP

Procedure HAZOP
What is a
procedure
HAZOP?
Procedure
Guidewords

Reporting
Procedure HAZOP
Conclusions

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 31 / 44
 What is a procedure HAZOP?

Introduction
A procedure HAZOP is an examination of an existing or planned
Team
operation (work) procedure to identify hazards and causes for
Process HAZOP
operational problems, quality problems, and delays.
Procedure HAZOP
What is a
procedure
HAZOP?
Procedure ❑ Can be applied to all sequences of operations
Guidewords ❑ Focus on both human errors and failures of technical systems
Reporting
❑ Best suited for detailed assessments, but can also be used for
Conclusions
coarse preliminary assessments
❑ Flexible approach with respect to use of guide-words

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 32 / 44
 Procedure

Introduction
❑ Breakdown of operation (work) procedure to suitable steps
Team
❑ Define intention of each step
Process HAZOP
❑ Establish boundary conditions
Procedure HAZOP
What is a
procedure
HAZOP?
Procedure else as
Guidewords
conventional Process HAZOP
Reporting

Conclusions
❑ Apply guide-words to intention and boundary conditions for
each step.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 33 / 44
 Guidewords

Introduction
Guide-word Meaning
Team

Process HAZOP No (not, none) None of the design intent is achieved

Procedure HAZOP
What is a More
procedure
Quantitative increase in a parameter
(more of, higher)
HAZOP?
Procedure Less
Quantitative decrease in a parameter
Guidewords (lessof, lower)
Reporting As well as
An additional activity occurs
(more than)
Conclusions
Part of Only some of the design intention is achieved

Reverse Logical opposite of the design intention occurs

Other than
Complete substitution - another activity takes place
(other)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 34 / 44
 Alternative guidewords - (1)

Introduction
Guide-word Meaning
Team

Process HAZOP Unclear Procedure written in confusing and ambiguous fashion

Procedure HAZOP
What is a Step in wrong Procedure will lead to actions out of correct sequence or
procedure place recovery failure
HAZOP?
Procedure Wrong action Procedure action specified is incorrect
Guidewords

Reporting Incorrect
Information being checked prior to action is incorrectly specified
information
Conclusions
Step omitted Missin step, or steps too large, requiring too much of the operator

Step
Step likely to be unsuccessful due to demands on operator
unsuccessful
Interference effects Procedure-following performance likely to be affected by other
from others personnel carrying out simultaneous tasks (usually when co-located)

– Adapted from B. Kirwan

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 35 / 44
 Alternative guidewords - (2)
Parameter Guide-word / deviation
Introduction

Team
Time Too early, too late

Process HAZOP
Sequence Wrong sequence, omissions, wrong action
Procedure HAZOP
What is a
procedure Procedure Not available, not applicable, not followed
HAZOP?
Procedure Measurement Instrument failure, observation error
Guidewords

Reporting Organization Unclear responsibilities, not fitted for purpose

Conclusions
Communication Failed equipment, insufficient/incorrect information

Personnel Lack of competence, too few, too many

Position Wrong position, movement exceeding tolerences

Power Complete loss, partly lost

Weather Above limitations - causing delayed operation

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 36 / 44
Introduction

Team

Process HAZOP

Procedure HAZOP

Reporting
Report contents
Review meetings

Conclusions Reporting and review

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 37 / 44
 Report contents

Introduction
Summary
Team
1. Introduction
Process HAZOP
2. System definition and delimitation
Procedure HAZOP

Reporting
3. Documents (on which the analysis is based)
Report contents 4. Methodology
Review meetings
5. Team members
Conclusions
6. HAZOP results
– Reporting principles
– Classification of recordings
– Main results

Appendix 1: HAZOP work-sheets

Appendix 2: P&IDs (marked)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 38 / 44
 Review meetings

Introduction
Review meetings should be arranged to monitor completion of
Team
agreed actions that have been recorded. The review meeting
Process HAZOP
should involve the whole HAZOP team. A summary of actions
Procedure HAZOP

Reporting
should be noted and classified as:
Report contents
Review meetings

Conclusions ❑ Action is complete

❑ Action is in progress
❑ Action is incomplete, awaiting further information

– Based on Kyriakdis (2003)

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 39 / 44
Introduction

Team

Process HAZOP

Procedure HAZOP

Reporting

Conclusions
HAZOP Results
Advantages
Success factors
Conclusions
Pitfalls

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 40 / 44
 HAZOP Results

Introduction
❑ Improvement of system or operations
Team
– Reduced risk and better contingency
Process HAZOP
– More efficient operations
Procedure HAZOP
❑ Improvement of procedures
Reporting

Conclusions
– Logical order
HAZOP Results – Completeness
Advantages
Success factors ❑ General awareness among involved parties
Pitfalls ❑ Team building

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 41 / 44
 Advantages

Introduction
❑ Systematic examination
Team
❑ Multidisciplinary study
Process HAZOP
❑ Utilizes operational experience
Procedure HAZOP

Reporting
❑ Covers safety as well as operational aspects
Conclusions
❑ Solutions to the problems identified may be indicated
HAZOP Results ❑ Considers operational procedures
Advantages
Success factors ❑ Covers human errors
Pitfalls ❑ Study led by independent person
❑ Results are recorded

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 42 / 44
 Success factors

Introduction
❑ Accuracy of drawings and data used as a basis for the study
Team
❑ Experience and skills of the HAZOP team leader
Process HAZOP
❑ Technical skills and insights of the team
Procedure HAZOP

Reporting
❑ Ability of the team to use the HAZOP approach as an aid to
Conclusions
identify deviations, causes, and consequences
HAZOP Results ❑ Ability of the team to maintain a sense of proportion,
Advantages
Success factors especially when assessing the severity of the potential
Pitfalls consequences.

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 43 / 44
 Pitfalls and objections

Introduction
❑ Time consuming
Team
❑ Focusing too much on solutions
Process HAZOP
❑ Team members allowed to divert into endless discussions of
Procedure HAZOP

Reporting
details
Conclusions
❑ A few of the team members dominate the discussion
HAZOP Results ❑ “This is my design/procedure”
Advantages
Success factors – Defending a design/procedure
Pitfalls – HAZOP is not an audit
❑ “No problem”
❑ “Wasted time”

Marvin Rausand, October 7, 2005 System Reliability Theory (2nd ed), Wiley, 2004 – 44 / 44