WHAT IS HAZOP?
HAZOP is a systematic hazard identification and evaluation methodology, developed in the 1960’s by the Imperial Chemical Industries (read here). It is an effective and popular method being utilized in the process industries, and is a legal requirement in some regions. This post discusses about the pitfalls / challenges HAZOP teams face.
Pitfall 1: Time
Current project / operational requirements tend to exert time pressure on HAZOPs. Most HAZOPs are required to be finished in a fixed time duration, by the stakeholders of the project, at times without the consultation of the HAZOP facilitator.
The first day of HAZOP is normally slow paced and the momentum picks up as the discussion progresses. The HAZOP team needs time to align / tune themselves with the flow and of the HAZOP.
Determining the HAZOP duration is not exact science. It depends on:
- Scope & Size of the facility in question
- Experience level of the facilitator
- Degree of preparedness of the facilitator and members
- Level of firm engineering details (P&ID’s, PFD’s, process descriptions)
- Level of competency of participants
A HAZOP discussion can usually be delayed by:
- Deviated discussions; usually pertaining to:-
- Discussions of redesigning the facility being HAZOPped
- Disagreements on scope, methodology and execution of the HAZOP
- Unavailability of information, data and right personnel on the team
Unwanted delays in a HAZOP can be reduced by some early preparation:
- Node selection, description and markups can be prepared well in advance. The HAZOP facilitator can, up to a certain extent, estimate the duration of the HAZOP. The facilitator could also could be prepared with a plan on how to execute the HAZOP session
- A Terms of Reference Document (TOR) can be prepared in advance. This document can be submitted for formal approval to the stakeholders; stating the scopes, methodology,guidewords, documents required and required members for the HAZOP session. This avoids deviating discussions on methodologies, scopes after the HAZOP has commenced.
Pitfall 2: Level of Information Available
HAZOP Facilitators commonly face this one challenge:
- Out of date drawings and engineering details, specifications;
- Inaccurate SOP’s, safeguarding systems, alarm points etc;
- Vague reaction data; or
- Inaccurate process envelopes / limits of operations.
The effects of inaccurate information is an inaccurate HAZOP:
- Poor deviation identification;
- Poorly defined consequences;
- Poor understanding of the design and operating principles of safeguards; hence underestimating the risk; or
- Long discussions with members trying to make design decisions in the HAZOP / refining the poorly defined parameters.
The need to Re-HAZOP the facility may also arise when the design details change.
To avoid this situation, the stakeholders could ensure the following prior to the HAZOP:
- The process flows should be firmed and finalized
- Finalized P&ID’s should be submitted for the HAZOP
- A firmed basis of design should be made available prior to HAZOP
It should be noted again that the HAZOP forum is not the place to:
- Learn the process; or
- Redesign the process
Pitfall 3: Too Large a Team Size
If a HAZOP team gets too large, the facilitator may face a challenge of having all members focusing on the HAZOP discussion. A large crown tends to deviate from the focus point and have other unrelated discussions during the HAZOP. In a large HAZOP forum, non contributing members are normally observed.
If the HAZOP team is too small, there is a lack of required expertise and the HAZOP will lack substance / or insufficient input.
Generally a team of 6 to 8 core members are deemed reasonable for a HAZOP session. Specifically, the following disciplines are normally core to the HAZOP:
- Process / Production Engineer
- Instrumentations Engineer
- Maintenance Engineer
- Chemists
- Process Safety / HSE Representative
- Operations representative
The terms of reference document (TOR) is helpful for facilitators to inform the stakeholders on assigning the right personnel to the HAZOP. The TOR should specify core, full-time members and non core members.
The non-core members can be requested to be present where the respective nodes requiring their input are being discussed, if the HAZOP is prep-planned by the Facilitator.
It is also worthwhile to keep a phone number of the non-core members and ring them up whenever their input is needed.
Pitfall 4: Distractions
Distractions are common in HAZOP discussions. A HAZOP can be taxing as it requires focus and a thorough thought process of all the members. It easy to lose focus (phone calls, laptops etc) in a HAZOP.
The HAZOP facilitator has the responsibility to maintain the focus of the group and keep the HAZOP process moving and avoiding discussions going out of control.
Adequate breaks, and engagements of all members will help to retain focus and involvement. Conducting HAZOPs outside the facility workplace can help members being called out of the forum.
Should the participants are likely to be engaged in their laptops, the facilitator can engage them by sharing the nodes and drawings electronically(instead of printed copies), too keep them engaged from their devices.
Pitfall 5: Modification / Brownfield Scopes
Most sites have a good written Management of Change (MOC) procedures and require HAZOPs for significant changes (read article on MOC’s here). The common challenge in doing such modification / Brownfield HAZOPs are adequate understanding of the overall HSE impact of the modification to the facility. Most of the times, the HAZOPs tend to focus on the hardware changes, and the cascading changes to / from associated parameters (ie downstream process, control system, utilities, waste management etc) could be overlooked. It is also true that time is a limit for Brownfield HAZOPs and the Facilitator has limits on covering a broader envelope of the facility. Under such circumstances, there are possibilities of new / escalated hazards overlooked at the facilities not directly related to brownfield tie-ins, and could potentially become a threat.
The following suggestions can help the HAZOP facilitator / stakeholders on effectively HAZOPping modifications / Brownfield scopes:-
- Review the existing HAZOP records, well before the HAZOP and understand / identify the following;
- The process descriptions and basis of design of the entire facility in question. A broad understanding of the overall engineering design, process control, alarms and safety instrumented systems will be helpful in executing the HAZOP later.
- Read the consequences identified and check if the modification / tie in would change these consequences (both upstream and downstream). Pay attention to any deviations / scenarios disregarded as not probable / possible under current conditions and check if the modifications increase the probability of occurrence. Forward these points as questions for discussion during the HAZOP.
- Carefully go through the barriers taken credit for at the process systems both downstream and upstream of the modification / tie-in. Conduct a brief assessment if the barriers would still help post modification / tie-in (Instrument ranges, set points, spurious trips etc). These could be kept as notes and asked as questions to the HAZOP forum
- A brief check through the action / close outs and the drawing updates is necessary. This is to ensure the HAZOP is conducted on an updated P&ID’s and references
- Upon such preparation, a note can be prepared to the stakeholders, should it be necessary that the existing HAZOP subjected to a review and more timeframe should be allocated.
- During the HAZOP, the participants can be reminded to be mindful of the wider impacts the modifications / tie ins. If the allocated time does not permit a revisit of the existing HAZOP, notes / actions can be generated for a review later.
Pitfall 6: Vendor Scopes
Facilitators often face some challenges with vendors. Sometimes, vendors participating in HAZOPs of their respective packages are seemed to be reserved or defensive. At times it is difficult to get meaningful HAZOP outputs when Vendor Packages are subjected to HAZOP.
Vendor packages are sometimes proprietary information and subjected to non-disclosure restraints. Sometimes certain vendor package information could a
ffect them commercially end expose commercial sensitive information to potential competitors. Also when a HAZOP dwells deeply into the design level of the vendor packages, vendors do get an impression that their equipment / designs are being criticized, that too before a potential Client. This is seen as a commercial disadvantage. Therefore it is no surprise that Vendors take a defensive stance / reluctant to disclose information in HAZOPs.
The facilitator / stakeholders can try the following suggestions to have better vendor participation in HAZOPs
- Share the TOR so the Vendors are aware of the purpose and approach of the HAZOP. They would be more participative and eager to share information if they see the HAZOP as an opportunity to directly engage Clients and an opportunity to present their products to suit Client’s requirements.
- Vendors are usually cooperative and supportive if they are given an opportunity to. The HAZOP Facilitator, instead of only seeking information from the Vendors, could provide an opportunity to briefly describe their package. Most vendors see this as opportunity and would be willing to contribute. Given the flexibility, vendors could play an effective role in the HAZOPs.
- Normally two types of information are required from vendors in HAZOPs; Operating details of their package and protective functions within their package. The HAZOP facilitator at times faces challenges on getting vendor data on how certain protective functions work, set points etc. Sometimes the Facilitator tries to engage the Vendor repetitively for such information (some might be proprietary). Instead the following approaches can be taken:
- If inadequate information available from Vendor on the protective functions, avoid taking credit for its availability. This is reasonable since most vendor package protective systems are designed to protect their equipment rather than the facility. Trying to assess these elements in too much detail can be non-productive.
- Protective functions outside Vendor packages can be taken credit of, including interfacing elements. These data are normally available with the HAZOP team
- The HAZOP team has a duty to protect the vendor’s sensitive / proprietary information. Should such information are really required to be disclosed in the HAZOP, then the stakeholders can hold a discussion on non-disclosure notes, restriction on distribution etc, and get written vendor agreement before requesting disclosure of their proprietary information. The HAZOP Team should also be careful not to have competing vendors in a single HAZOP session; it is counterproductive as the Vendors could be more defensive as they have a duty to protect their company secrets from competitors. An assurance that their sensitive information will be treated appropriately helps to gain Vendor confidence and better participation.