Академический Документы
Профессиональный Документы
Культура Документы
Overview
Review hazOP:
limitations of hazOP,
impact of IEC 61508.
Proposal for xyzOP,
new guidewords,
phasing issues.
Overview of chazOP and coOP methodology.
Case study:
outline of control system,
application of methodology,
outcomes and lessons learned.
P
Details of
xyzOP
methodology
outlined in
Chapter 54
Case study:
being put into
public domain
for first time.
hazOP Studies
What is hazOP?
It is a technique to identify potential hazards,
well established and trusted,
the method of choice and used extensively,
IEC 61882 is an application guide.
It also happens to be:
labour intensive and costly,
unbelievably tedious and boring,
the only show in town.
Limitations of hazOP
Current practice:
varies from superficial to thorough.
much variety in procedures and practices.
end users often rely upon suppliers and/or contractors
doing walkthroughs at design stage:
but critically dependant upon detail.
some form of chazOP is often carried out in-house,
but methods lack coherence and consistency in
terms of scope, methodology, etc.
There is virtually zero information in the public domain
about how to do this.
P
Risk
DR x PFD
53-23
HR x C(E)
53-24
10
11
12
hazOP
Guideword
Meaning
Comments
No or Not
More and
Less
Quantitative increase
or decrease.
As well
Qualitative increase,
something extra.
Part of
Reverse
Other than
Complete substitution.
Table 54-1
Guideword
Meaning
Comments
chazOP
Loss
Range
Mixture
Version
Incompatibility of and/or
changes to functionality
of the system software.
Table 54-3
Security
14
Guideword
Meaning
Comments
coOP
Access
Timing
Frequency of recurrent
events and/or order of
logical events.
Structure
Conflict
Table 54-5
15
Phasing
16
Phasing contd -2
Formulate URS
Develop DFS
Design hardware
Design software
Design modules
Develop software
System acceptance
Integrate system
Integrate software
Test modules
Figure 63-1
P
17
Phasing contd -3
Detailed
pre hazOP
Construction
etc
full hazOP
Conceptual
Control system design
(hardware & system s/w)
Detailed
pre chazOP
etc
Build
full chazOP
Develop
etc
full coOP
18
chaZOP Studies
19
chazOP contd -2
20
Reminder
Detailed
pre hazOP
Construction
etc
full hazOP
Conceptual
Control system design
(hardware & system s/w)
Detailed
pre chazOP
etc
Build
full chazOP
Develop
etc
full coOP
21
coOP Studies
22
coOP contd -2
23
Case Study
Control System Upgrade
24
Case Study
25
Control System
26
Design Process
27
28
Trial contd -2
29
30
Results
coOP
chazOP
Metric
hazOP
No of nodes
23
20
Total no of actions
20
43
44
Applicability
of guideword
% of actions
generated by
guideword
n/a
n/a
loss
range
mixture
version
security
96%
83%
83%
91%
13%
access
timing
structure
conflict
95%
80%
65%
30%
loss
range
mixture
version
security
30%
21%
30%
16%
3%
access
timing
structure
conflict
39%
18%
25%
18%
31
Results contd -2
coOP
chazOP
Metric
hazOP
Hazard/operability
Hazard 75%
Hazard 19%
Hazard 11%
Opery 25%
Operability 81%
Operability 89%
Actionee
n/a
Inst engr
Project engr
Supplier
39%
33%
28%
Inst engr
Project engr
Supplier
Others
40%
53%
25%
25%
0%
35%
33%
7%
7%
61%
0%
14%
P
32%
25%
39%
4%
32
Outcomes
33
Outcomes
34
Outcomes contd -2
35
Outcomes contd -3
36
Lessons Learned
37
Lessons contd -2
Methodology:
define scope clearly, esp technical boundaries,
identify all interface points (h/w & s/w):
these are highest risk areas for specification issues
and implementation errors,
identify all instances of h/w and s/w typicals.
these are the building blocks and need full analysis.
analyse suitability of all configurables (h/w & s/w).
decide on granularity of signals: rack, card, channel?
quantify no of non-typicals to be analysed & hence the
time & effort required.
P
38