Computer-aided Hazard Identification Paul Chung Department of Computer Science.

Slides:



Advertisements
Similar presentations
Configuration management
Advertisements

Configuration management
GUI Testing By Norbert Haché. Contents b What is GUI testing b Elements of GUI testing b Old Approach (TRUMP Project) b Scripting b Capture / Replay b.
Lecture 8: Testing, Verification and Validation
Verification and Validation
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
HAZOP Hazard & Operability studies What is HAZOP? (Hazard & Operability) A systematic review of the design & operation of a system to identify the potential.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
S88 structure used in system configuration
Computer-aided Hazard Identification Paul Chung Steve McCoy and Dingfeng Zhou Department of Computer Science.
Fundamentals of Information Systems, Second Edition
Chapter 2: Developing a Program Extended and Concise Prelude to Programming Concepts and Design Copyright © 2003 Scott/Jones, Inc.. All rights reserved.
Programming Fundamentals (750113) Ch1. Problem Solving
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO RISK IDENTIFICATION 2.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Using Use Case Scenarios and Operational Variables for Generating Test Objectives Javier J. Gutiérrez María José Escalona Manuel Mejías Arturo H. Torres.
XP New Perspectives on Microsoft Access 2002 Tutorial 71 Microsoft Access 2002 Tutorial 7 – Integrating Access With the Web and With Other Programs.
Testing Processes of Web Applications Susan Cohen.
TEST CASE DESIGN Prepared by: Fatih Kızkun. OUTLINE Introduction –Importance of Test –Essential Test Case Development A Variety of Test Methods –Risk.
TIBCO Designer TIBCO BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop, deploy, and run integration.
SISIFO-GAS A COMPUTERIZED SYSTEM TO SUPPORT SEVERE ACCIDENTS TRAINING AND MANAGEMENT WGRisk Workshop March 29-31, 2004 Köln, Germany César Serrano.
SCADA and Telemetry Presented By:.
ERT 312 SAFETY & LOSS PREVENTION IN BIOPROCESS HAZARDS IDENTIFICATION Prepared by: Miss Hairul Nazirah Abdul Halim.
Verification and Validation Yonsei University 2 nd Semester, 2014 Sanghyun Park.
4-1 Coding Complete COBOL Programs: The PROCEDURE DIVISION Chapter 4.
VisiMix Data Base Management VisiMix Ltd, PO Box 45170, Jerusalem, 91450, Israel Tel: Fax:
ISO OPERATIONAL CONTROL
GDT V5 Web Services. GDT V5 Web Services Doug Evans and Detlef Lexut GDT 2008 International User Conference August 10 – 13  Lake Las Vegas, Nevada GDT.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Configuration Management (CM)
Requirements Engineering Requirements Elicitation Process Lecture-8.
Process, Power and Marine Division Design Safety into Your Plant Mary Kay O’Conner Process Safety Symposium Frank Joop Global Business Development Intergraph.
WXGE6103 Software Engineering Process and Practice Formal Specification.
Hazard Analysis. 2 Lecture Topics Hazards and Accidents Hazard Analysis.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Nordic Process Control Workshop, Porsgrunn, Norway Application of the Enhanced Dynamic Causal Digraph Method on a Three-layer Board Machine Cheng.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
INFORMATION MANAGEMENT Module INFORMATION MANAGEMENT Module
Submitted To: Rutvi sarang Submitted By: Kushal Bhagat.
ERT 213 PROCESS INSTRUMENTATION BY: ZULKARNAIN MOHAMED IDRIS
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
SAFEWARE System Safety and Computers Chap18:Verification of Safety Author : Nancy G. Leveson University of Washington 1995 by Addison-Wesley Publishing.
Requirements Engineering Requirements Validation and Management Lecture-24.
CISSP Common Body of Knowledge Review by Alfred Ouyang is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
A Portrait of the Semantic Web in Action Jeff Heflin and James Hendler IEEE Intelligent Systems December 6, 2010 Hyewon Lim.
ERT 312 SAFETY & LOSS PREVENTION IN BIOPROCESS HAZARDS IDENTIFICATION
Fault Tree Analysis for Fatality Prevention Dr. Steven A. Lapp President - Design Sciences, Inc.
HAZARD AND OPERABILITY STUDY Brainstorming, Multidisciplinary Team Approach Structured Using Guide Words Problem Identifying Cost Effective.
The BioTector B7000i TOC analyzer with integrated oxygen concentrator
Software Testing.
Chemstations Dynamic Seminar
Presentation CHEMCAD Simulation Software Training Simulator
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
3. HAZards and OPerability Studies (HAZOP)
HAZOP Study for Kiln Start-up Process of a Cement Production Plant
Chapter 10: Process Implementation with Executable Models
Automation Topics: Elements of an Automated System
The BioTector B3500ul TOC analyzer Process Tests
Hazard identification
Modern Systems Analysis and Design Third Edition
Model Based Testing Venkata Ramana Bandari, Expert Software Engineer
Frank Joop Global Business Development
Programming Fundamentals (750113) Ch1. Problem Solving
An Introduction to Structured Program Design in COBOL
Modern Systems Analysis and Design Third Edition
HAZOP Guidewords Base Set
Tutorial 7 – Integrating Access With the Web and With Other Programs
Modern Systems Analysis and Design Third Edition
Lecture 23 CS 507.
Presentation transcript:

Computer-aided Hazard Identification Paul Chung Department of Computer Science

Hazards and Operability (HAZOP) Studies Established and widely used technique in the process industry for hazard identification Time consuming, labour intensive process: –Tedious –Expensive

Computer-aided HAZOP Different levels of support: –Electronic report form –Electronic data (on plant, on fluids, etc.) –Automated Hazard Identification Continuous operation Batch operation

Automated Hazard Identification Continuous operation –From basic research to commercial product – HAZID –Basic technology Signed directed graph (SDG) representation Fault propagation –Go through a list of deviations systematically and identify the faults that cause the deviations and the consequences that result from the faults and deviations

HAZID Overview Automated extraction of plant design from a CAD system, e.g. Intergraph SmartPlant P&ID Convenient forms for adding any missing process specific information Tick boxes for selecting analysis options: –Deviations, e.g. more flow, less flow, etc. –Items to HAZOP, etc.

HAZID Overview HAZOP style output in different output formats –XML, with HTML web page view. –Excel spreadsheet. Query facility for viewing analysis results –e.g. viewing faults and consequences relating to a particular plant item –e.g. viewing the propagation path between a particular fault and consequence Compare facility for viewing the difference between two HAZID runs –Useful for after making a change to the design

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

Mapping SmartPlant to Hazid models SmartPlant Database References Hazid Model Types Mapping created by user for all company, then mapping is >95% automatic Automatic mapping by Hazid: = = Centrifugal Pump Valve = ????? Mixer Stripper Absorber Reactor User makes choice 8 **This User mapping is required only once for the whole Project**

Checking Automatic Nozzle Mapping Hazid model is process function: But P+ID is piping: User confirms nozzle functions: N1 is vapour/liquid in port, N2 and N3 are liquid out ports, N4 is a vapour out port N5 is Cleanout liquid in port. Liquid Vapour Vapour/Liquid In Port Liquid Out Port Vapour Out Port 9 N1 N2 N3 N4 N5

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

Interaction between Faults, Deviations and Consequences Consequence Deviation Fault Fault - can cause Consequence Fault - can cause Deviation to process variable Deviation – can cause another Deviation Deviation – can cause Consequence Equipment Knowledge Base Knowledge about behaviour of equipment These links are called “arcs” in Hazid

Equipment Knowledge Base Knowledge about Faults and Consequences This is mainly engineering knowledge and experience In Out Fault – Bearing failureConsequences Casing damage Seal damage and leakage Loss of discharge pressure Flow disturbance Pump stops

Select SP P+ID From SmartPlant Run Hazid data wizard, Extract plant data from SP database: *Plant Items *Piping, valves, fittings *Controls *Fluids information: Temperature Pressure Fluid name Hazid maps SP icons to Hazop “Process” models Converts P+I diagram to Analysis model Hazid analyses plant and generates Hazop Report Hazid Operation 7

HAZOP Style Output from HAZID

HAZID Viewer Queries Standard format questions: –What causes could there be for a selected hazard? –What consequences are there for a given failure mode? –How is a given hazard realised? Show a path of deviations for propagation –Display all hazards with a given severity rank or higher

Filtered Output showing Fault Paths for a given Hazard

Automated Batch Plant Hazard Identification Batch operation –Early research prototype (CHECKOP) –Basic technology Action representation State-based simulation –Go through a set of operation instructions systematically and identify potential ambiguities, operating problems and hazards –Applying guidewords such as before, after, no action, etc.

CHECKOP System Overview

Simple Batch Reactor Example

CHECKOP Plant Description instance(tank101 isa tank, [content info [reactantA], outports info [out is [pump101,in]]]). instance(pump101 isa pump, [status is offline, outports info [out is [valve101,in]]]). instance(valve101 isa valve, [status is closed, outports info [out is [reactor101, in2]]]). instance(reactor101 isa stirred_tank_reactor, [ outports info [out1 is [valve103,in], out2 is [valve106,in]], heatSink info [hout is [jacket101,hin]], reaction info [reaction_ab_p] ]).

Operating instruction format Natural language –Easy for user –Requires natural language processing –Could be ambiguous Structured template –Easy for computer to process –Limited expressive power

Operating instruction format Object Action –valve101 open Object Action until Condition –mixer on until elapsed-time 20 minute Object1 Action Object2 Filler-word Fluid until Condition –reactor101 fill-from tank101 with reactantA until volume 30 percent

CHECKOP Operating Procedure Input charge reactor101 with reactantA: { (1) valve101 open (2) pump101 start (3) reactor101 fill_from tank101 with reactantA until volume 30 percent (4) pump101 stop (5) valve101 close } etc…

Deviation Generation Combine each single action in the procedure with guide words, from: –No action – Simple omission. –Early/Late action – Sequence of procedure changed (how many steps feasible?). –Early/Late action termination – “until” condition of action varied. Then, simulate the effect of executing the new procedure on the plant, detect hazards.

Batch HAZOP Output OperationKeywordConsequences (3) reactor101 fill from tank101 with reactantA until volume 30 percent No action(6) agitator running while vessel empty (17) cannot empty [reactantA, productP] from reactor101 to tank103 because content of reactor is [reactantB]. Early action (-2) reactor101 cannot be filled from tank101 because there is no flow path. Late action (+3) reactor101 cannot be filled from tank101 because there is no flow path.

Batch HAZOP Output OperationKeywordConsequences (3) reactor101 fill from tank101 with reactantA until volume 30 percent Early termination (to only 10 percent) no consequence. Late termination (to 50 percent) (17) cannot empty [reactantA, productP] from reactor101 to tank103 because content of reactor is [reactantA, productP]. (17) contamination in tank103.

Future Work on CHECKOP A formal structured language for operating instructions More guide words –“Other” Action – change other variables of the Action model Rules for reasonable deviations –What are the most likely mistakes in operation? Integrate with HAZID –HAZID is strong on process hazards, CHECKOP better for operating errors, etc. –HAZOP of start-up, shutdown, maintenance, etc.

Conclusions Automated hazard identification –continuous operation commercial tool that can reduce the time of HAZOP –batch operation promising area of research and development for identifying problems associated with human errors and operating procedures Benefits: –Doing HAZOP earlier, and on modifications. –Consistent, repeatable, complete hazard identification method.

Acknowledgements The work described in this presentation is being funded by –HAZID Technologies Ltd –Engineering and Physical Sciences Research Council, UK Thanks are also due to my colleagues –Dr Steve McCoy –Mr Dingfeng Zhou