{"id":73874,"date":"2026-09-01T15:00:26","date_gmt":"2026-09-01T18:00:26","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=73874"},"modified":"2026-09-01T15:00:26","modified_gmt":"2026-09-01T18:00:26","slug":"hazop-engineering-methodology-guide-words-process-deviations","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/hazop-engineering-methodology-guide-words-process-deviations\/","title":{"rendered":"HAZOP in Engineering: Methodology, Guide Words, and Process Deviation Analysis"},"content":{"rendered":"\n

HAZOP, short for Hazard and Operability Study<\/strong>, is a structured technique for analyzing risks and operability problems based on the systematic examination of deviations from design intent. The team divides the system into manageable parts, defines relevant parameters, and uses guide words to trigger questions such as \u201cwhat happens if there is more pressure?\u201d, \u201cno flow?\u201d, \u201creverse flow?\u201d, \u201clower temperature?\u201d or \u201coperation different from intended?\u201d. For each plausible deviation, causes, consequences, safeguards, and recommendations are analyzed.<\/p>\n\n\n\n

IEC 61882:2016 is the specific international reference for HAZOP studies. It provides guidance on definition, preparation, examination sessions, documentation, and follow-up. In Engineering, HAZOP should not be treated as a generic brainstorming meeting or as simply filling out a spreadsheet. The value of the technique depends on clear design intent, a competent multidisciplinary team, well-defined study nodes, appropriate guide words, consistent records, and subsequent treatment of recommendations<\/strong>.<\/p>\n\n\n\n

What Is HAZOP and What Problem Does It Solve?<\/h2>\n\n\n\n

HAZOP was developed to systematically investigate how a system may deviate from its intended behavior and what risks or operability problems may result from those deviations. Its starting point is not a prior list of failures, but the design intent<\/strong>: what each part of the system is expected to do under defined conditions.<\/p>\n\n\n\n

The technique is particularly powerful when system behavior depends on variables, sequences, flows, states, interlocks, or interfaces. Instead of asking only \u201cwhat can go wrong?\u201d, the facilitator leads the team through structured combinations of guide word + parameter<\/strong>, turning the analysis into a repeatable process.<\/p>\n\n\n\n

Examples of parameters include flow, pressure, temperature, level, voltage, current, flow rate, concentration, speed, sequence, time, composition, availability, communication, or signal. Guide words introduce deviations such as none, more, less, part of, as well as, reverse, before, after, or other than \u2014 always adapted to the technical context.<\/p>\n\n\n\n\n

\n

When design intent, interfaces, and operating criteria are not yet sufficiently defined, HAZOP exposes a gap that precedes the risk analysis itself: the project needs to consolidate requirements and decisions before deviations can be assessed consistently.<\/p>\n\n\n\n

Structure requirements, evidence, and acceptance criteria \u2192<\/a><\/p>\n<\/div>\n\n\n\n\n

Design Intent: The Reference for Recognizing a Deviation<\/h2>\n\n\n\n

Without clear design intent, there is no high-quality HAZOP. The team needs to know the expected function of the node, normal operating conditions, acceptable limits, existing interfaces, and which operating states need to be considered.<\/p>\n\n\n\n

Intent is not limited to a nominal value. In a pumping circuit, for example, it may involve delivering a specified flow rate between two points, maintaining pressure within a range, preventing backflow, operating in normal and standby modes, and preserving safe conditions during startup, shutdown, and maintenance.<\/p>\n\n\n\n

In electrical systems, the intent may involve feeding a bus from a specified source, transferring load under specific conditions, maintaining protection selectivity, preventing unintended paralleling, and preserving continuity for critical loads. In automation, it may involve receiving a valid signal, executing logic, issuing a command, and positioning an actuator within a defined time.<\/p>\n\n\n\n

When requirements, diagrams, cause-and-effect lists, operating philosophy, or protection criteria are incomplete, HAZOP tends to expose the documentation deficiency even before the risk analysis is concluded. This is useful: gaps in design intent are, in themselves, engineering and integration risks.<\/p>\n\n\n\n

Study Nodes: How to Divide the System<\/h2>\n\n\n\n

A complete HAZOP needs to break the system down into units of analysis known in many contexts as study nodes<\/strong>. The goal is to select sections homogeneous enough for design intent and parameters to be discussed coherently.<\/p>\n\n\n\n

A node that is too large produces vague discussions and mixes different functions. A node that is too small increases the number of combinations without proportional benefit, making the study slow and repetitive.<\/p>\n\n\n\n

Boundaries may follow equipment, process sections, functions, subsystems, operating modes, sequence steps, or interfaces. The criterion should consider how the system actually works and where changes in intent or conditions alter risk.<\/p>\n\n\n\n

Before the sessions, the study leader should prepare the node list, applicable documents, intent for each node, and relevant parameters. This preparation reduces unproductive time and improves consistency between sessions.<\/p>\n\n\n\n

Guide Words: How HAZOP Triggers Deviations<\/h2>\n\n\n\n

Guide words are systematic prompts used to explore variations from design intent. They should not be applied mechanically to every parameter. The facilitator selects combinations that make sense for the system being analyzed.<\/p>\n\n\n\n

Some typical combinations are:<\/p>\n\n\n\n

Guide word<\/td>Possible interpretation<\/td>Example<\/td><\/tr>
None<\/td>absence of the function or parameter<\/td>no flow, no signal<\/td><\/tr>
More<\/td>value above intended<\/td>more pressure, more voltage<\/td><\/tr>
Less<\/td>value below intended<\/td>less flow rate, lower level<\/td><\/tr>
Reverse<\/td>opposite direction or logic<\/td>reverse flow, reverse sequence<\/td><\/tr>
Part of<\/td>incomplete composition<\/td>part of the supply available<\/td><\/tr>
As well as<\/td>additional undesired condition<\/td>contaminant present, additional signal<\/td><\/tr>
Before<\/td>premature occurrence<\/td>command before permissive<\/td><\/tr>
After<\/td>late occurrence<\/td>transfer after allowable limit<\/td><\/tr>
Other than<\/td>state different from intended<\/td>wrong equipment in operation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The objective is not to fill every possible cell, but to use guide words to avoid relying exclusively on the memory or individual experience of the team.<\/p>\n\n\n\n

Structure of a HAZOP Record Row<\/h2>\n\n\n\n

A record row needs to preserve the team’s reasoning. A robust structure normally contains:<\/p>\n\n\n\n

  • node or item analyzed;<\/li>
  • design intent;<\/li>
  • parameter;<\/li>
  • guide word;<\/li>
  • deviation;<\/li>
  • plausible causes;<\/li>
  • consequences;<\/li>
  • existing safeguards;<\/li>
  • risk assessment, when adopted;<\/li>
  • recommendation or action;<\/li>
  • owner and due date;<\/li>
  • status and closure evidence.<\/li><\/ul>\n\n\n\n

    The spreadsheet is not the HAZOP; it is the memory of the study. If the record does not allow someone to reconstruct why a recommendation was made, traceability is insufficient.<\/p>\n\n\n\n

    HAZOP study sequence<\/title>