Bowtie for Major Accident Hazard is a practical way to see how catastrophic scenarios develop, how they can be prevented, and how their consequences can be mitigated if they occur. In complex UAE industrial operations—refineries, petrochemical plants, offshore platforms, high-rise construction sites, logistics hubs, power generation assets—clear visibility of threats and controls is vital. The bowtie method turns that visibility into a structured picture of risk, aligning technical safeguards, human actions, and management systems into one barrier-based map. This article explains how the bowtie approach works for major accident hazards (MAHs), how it connects to common risk studies like HAZID and HAZOP, how it supports compliance with local regulators and international standards, and what to watch for when building and maintaining robust bowties across an asset’s lifecycle.
Who This Concerns

Because MAHs cut across technical, operational, and organizational boundaries, the barrier-focused logic of bowties involves multiple functions. The following roles are typically central to creating, validating, and using bowties in day-to-day decision-making:
- HSE managers, process safety leads, and discipline engineers responsible for risk identification and barrier integrity.
- Plant managers, operations superintendents, and offshore installation managers who must prioritize maintenance, impairment management, and safe production.
- Maintenance, instrument, and reliability teams who implement testing, proof checks, and performance standards for safeguards under IEC 61511 and company procedures.
- Project engineering and construction managers coordinating SIMOPS, tie-ins, and brownfield modifications where temporary barriers and elevated risks may arise.
- Emergency response coordinators, security leads, and business continuity teams who must understand mitigating controls and escalation pathways.
- Contractor HSE leaders and logistics supervisors working under permit-to-work and lifting plans where contractor interfaces are critical to barrier effectiveness.
In the UAE, this audience also includes compliance officers coordinating with ADNOC requirements, OSHAD frameworks in Abu Dhabi, Dubai Municipality EHS guidelines, MOHRE obligations, and Civil Defence approvals for fire/life safety. Whether the facility is a sour gas processing plant, a storage terminal handling jet fuel, an ammonia refrigeration system in a food plant, or a high-rise construction site with tower cranes, a clear bowtie for each MAH aligns stakeholders on what must never fail—and how to ensure it does not.
Why This Matters

Major accident hazards—loss of hydrocarbon containment, toxic gas release (e.g., H2S, chlorine), explosion in enclosed modules, ammonia release in refrigeration, catastrophic crane collapse, high-energy arc flash—carry low probabilities but extremely high consequences. The bowtie approach matters because it assembles the chain from threat to top event to consequence in a way that makes critical controls explicit, auditable, and defensible. That visibility supports:
- Regulatory expectations: alignment with ADNOC HSE requirements, OSHAD (Abu Dhabi) frameworks, Dubai Municipality codes, Civil Defence fire safety mandates, and MOHRE labour protections.
- Standards integration: mapping to ISO 45001 (occupational safety), ISO 14001 (environment), IEC 61511 (SIS lifecycle), API RP 14C/750, and NFPA codes for fire and explosion protection.
- Barrier management discipline: connecting SIL-rated functions from LOPA to proof test intervals, alarms and operator responses, passive fire protection, detection and shutdown, relief and blowdown, and emergency response arrangements.
Equally important, bowties make it easier for senior leadership to see where they are carrying disproportionate risk. If a preventive barrier like gas detection is repeatedly bypassed during maintenance, or if a mitigative barrier like firewater supply has latent reliability issues, the bowtie reveals how thin the organization’s real line of defense has become. That clarity drives better decisions on spares, staffing, competency, and budgets.
Key Points to Understand

Before looking at how bowties are built and used in practice, it helps to ground the core anatomy and terminology. A standard bowtie has a clearly defined hazard (e.g., pressurized hydrocarbon), a “top event” (e.g., loss of containment), threats that may lead to the top event (e.g., corrosion under insulation, vibration fatigue, human error in isolation), and consequences on the right side (e.g., jet fire, pool fire, toxic exposure, environmental release). Between the threats and the top event sit preventive barriers; between the top event and the consequences sit mitigative barriers. Two other elements matter greatly: escalation factors that can degrade the performance of a barrier, and escalation controls designed to counter those factors.
The effectiveness of a bowtie depends on how precisely these pieces are defined and evidenced. Barriers should be “critical controls” with clear performance standards: what function they must perform, under what conditions, and how performance will be assured and verified over time. Performance standards are not just technical parameters; they include people, process, and governance factors. For example, a high-integrity pressure protection system (HIPPS) may be technically sound under IEC 61511, but it is only effective if the proof test coverage is adequate, bypass rules are enforced, and impairment is escalated for risk-based decision-making during maintenance.
Below is a compact view of typical bowtie elements and what “good” looks like in the UAE industrial context:
| Bowtie Element | Typical Examples in UAE Facilities | What “Good” Looks Like (Assurance) |
|---|---|---|
| Hazard & Top Event | High-pressure sour gas; Top event: Loss of containment | Scope and boundaries defined; alignment with HAZOP nodes and process safety information |
| Threats | Internal corrosion, overpressure, valve misalignment, SIMOPS interference | Evidence-based from incident data, integrity reports, and operations narratives |
| Preventive Controls | SIL-rated SIS, PSV, operator monitoring, isolation and lockout | Performance standards specifying functionality, availability, proof test intervals, and bypass rules |
| Mitigative Controls | Fire detection and suppression, blowdown systems, gas dispersion modeling-informed ER plans | Demonstrated reliability via impairment tracking, drills, and maintenance KPIs |
| Escalation Factors | High ambient temperature, temporary equipment during shutdown, simultaneous maintenance tasks | Specific escalation controls (e.g., temporary firewatch, additional gas detectors) with clear ownership |
| Critical Control Verification | Barrier health dashboard, shift handover checks, independent assurance | Defined verification tasks, frequencies, and triggers for management review |
Bowties are not developed in isolation. They typically sit on top of hazard identification (HAZID), HAZOP studies, consequence modeling (QRA, dispersion, fire/explosion analysis), and layers of protection analysis (LOPA). HAZOP and LOPA provide the technical rigor (failure modes, SIL) that helps quantify or qualify the risk reduction credited to a barrier; the bowtie, in turn, organizes this information into a communication and assurance tool managers can act on. In ADNOC-governed assets, for example, the bowtie often becomes part of the formal process safety management system, providing a graphical spine for barrier assurance programs and management of change (MoC) controls.
As bowties mature, organizations often move from “cataloguing controls” to “critical control management” (CCM). The shift is marked by tighter definitions of critical controls, clear verification tasks, and live monitoring of impairments. Governance also broadens: frontline operations verify barriers daily or weekly; technical authorities provide independent oversight; senior leaders periodically review barrier health in leadership safety visits or structured process safety reviews. For additional perspectives on governance and risk leadership culture that often sit alongside CCM approaches, see CABINET NPM.
Finally, good bowties acknowledge human and organizational performance. Alarm response depends on workload and competence; permit-to-work effectiveness relies on supervision; emergency response hinges on familiarity with layouts and drills. Embedding these realities in performance standards makes barriers auditable without pretending they are infallible.
How This Works in Practice

Translating the framework into day-to-day practice begins with data. Teams compile process safety information, P&IDs, HAZOP deviations, integrity assessments, incident and near-miss histories, and operations narratives (e.g., where the system is fragile during startups). That evidence anchors selection of MAHs at the right level of granularity: not too generic (e.g., “fire”) and not too narrow (e.g., one valve’s failure mode). Defining the top event precisely—“loss of primary containment from the amine regenerator overhead”—helps keep threats and mitigations focused.
Workshops then structure knowledge from SMEs across operations, process engineering, instrumentation, maintenance, inspection (RBI), and emergency response. The group maps threats to preventive barriers and consequences to mitigations. SIL-rated functions and LOPA credits are integrated to avoid double-counting risk reduction and to ensure controls are independent where required. Interface hazards—e.g., gases from adjacent units during turnarounds, hot work near live lines, or marine and aviation operations on offshore platforms—are documented as threats or escalation factors, tying back to SIMOPS plans and bridging documents with contractors.
Once drafted, bowties are validated by walkthroughs in the field: verifying detector locations against obstruction, checking if bypasses are controlled, confirming relief paths and blowdown capacity, and assessing signage, muster routes, and communications for emergency response. These checks often reveal “failure-to-activate” risks that are otherwise invisible in diagrams—e.g., blocked deluge nozzles, degraded passive fire protection, or alarm flooding that obscures critical alerts during upsets.
The final bowtie is then embedded in management processes:
- Assign barrier owners and define verification tasks (frequency, method, evidence required).
- Connect barrier health to existing systems—CMMS for proof tests, impairment logs for firefighting systems, control room checklists for alarm management.
- Link bowties to MoC so modifications automatically prompt a refresh of threats and controls.
- Integrate with training and competence so that frontline teams can read bowties and perform critical verifications.
- Use periodic leadership reviews to examine trends, exceptions, and systemic issues revealed by barrier health data.
Regulatory interfaces fit naturally: documentation supports Civil Defence approvals for fire protection, ADNOC safety cases or equivalents, and OSHAD requirements where applicable. In many facilities, bowties are displayed in control rooms and used in pre-job briefings, so contractors understand both the threats they can trigger and the controls they must not compromise.
Benefits and Practical Use Cases

When used consistently, bowties become a common language for risk—a bridge between engineers, supervisors, and executives. Clear benefits emerge in daily operations and during abnormal situations:
- Operational discipline: Operators use bowties to prioritize response when alarms cascade, focusing on critical controls that prevent escalation to the top event.
- Maintenance planning: Barrier impairments guide work scheduling; if a key mitigative control (e.g., foam system) is down, work that elevates ignition risk is deferred or additional controls are applied.
- Turnarounds and SIMOPS: Temporary barriers—additional gas detection, firewatch, isolations—are integrated with the bowtie, clarifying what changes when systems are partially decommissioned.
- Evidence for regulators and insurers: Bowties showcase a structured approach to controlling MAHs in line with ISO 45001/14001 and ADNOC expectations, helping demonstrate ALARP decision-making.
- Learning from events: After an incident, teams use the bowtie to ask where the pathway breached—was it a missing threat control, a degraded escalation control, or an unrecognized escalation factor?
- Change management: MoC reviews incorporate bowtie updates, ensuring new threats introduced by design changes are addressed before commissioning.
Concrete use cases span the UAE industrial landscape:
- Refineries and petrochemicals: Loss of containment in a crude unit or cracker; bowtie aligns SIS trips, relief systems, detection/suppression, and emergency blowdown strategy informed by QRA.
- Gas processing and LNG: H2S release potential; critical controls include H2S detection, breathing apparatus readiness, muster and shelter-in-place procedures, and HVAC shutdowns.
- Offshore platforms: Ignition management and escalation; bowtie clarifies segregation, deluge reliability, ESD hierarchy, and evacuation/escape routes.
- Construction of high-rises: Crane collapse as an MAH; preventive measures include ground bearing checks, wind cut-offs, exclusion zones, and lifting plans; mitigations cover emergency access and rescue.
- Manufacturing with ammonia refrigeration: Ammonia release; preventive controls include integrity inspection and valve management; mitigations cover gas dispersion-informed ER and neutralization resources.
- Power generation: Steam line rupture/boiler overpressure; bowtie covers protection systems, inspection regimes, and hot zone evacuation planning.
The unifying benefit is tangible: decisions are faster and better when everyone can see which controls keep a low-frequency, high-consequence event at bay—and what to do if one of those controls is compromised.
Best Practices and Points of Caution

As with any risk tool, the value of bowties depends on disciplined application. The following practices help ensure the diagrams become living, decision-driving assets:
- Define the top event precisely. Avoid vague phrases like “accident happens.” Be specific about the loss of control state.
- Credit only independent, effective controls. If LOPA would not credit a safeguard as independent, the bowtie should not either.
- Write performance standards for each critical control. Include functionality, availability, response time, testing, impairment protocols, and competency requirements.
- Connect to assurance. Assign owners, define verification tasks, and track barrier health visually (e.g., dashboards) so leaders can spot trends.
- Include human and organizational factors. Consider workload, staffing, language barriers, training, and supervision in the effectiveness of controls.
- Keep the model current. Tie bowties to MoC and refresh them after incidents, audits, and major shutdowns.
Common pitfalls are also predictable, and avoiding them protects the integrity of the bowtie:
- Oversimplification: Reducing a complex MAH to a generic picture dilutes actionability. Calibrate scope to the actual process and layout.
- Barrier inflation: Listing every procedure as a barrier obscures which controls are truly critical. Distinguish between supporting activities and critical controls.
- Neglecting escalation controls: If high ambient temperatures, contractor interfaces, or temporary equipment can degrade a control, define the countermeasures explicitly.
- Forgetting assurance detail: A control without a verification task and acceptance criteria will drift toward notional status over time.
- Not integrating with existing systems: If proof tests, firefighting impairments, and alarm KPIs sit in separate silos, barrier health will be partial and late.
- Ignoring local regulatory context: Civil Defence expectations for fire protection and evacuation, or OSHAD requirements for risk management, should be reflected in the controls and verification cadence.
Finally, treat the bowtie as a shared language. Publish diagrams where operators can reference them; translate key labels for bilingual teams; and incorporate them into toolbox talks so contractors can see how their work interacts with critical controls.
Frequently Asked Questions About Bowtie for Major Accident Hazard

How is a bowtie different from HAZOP or LOPA?

HAZOP is a systematic hazard identification and deviation study at the node level; LOPA quantifies risk reduction and assigns SILs to instrumented functions. A bowtie synthesizes the scenario view: hazard → threats → top event → consequences, with preventive and mitigative barriers in between. It does not replace HAZOP/LOPA but communicates their outcomes in an operationally readable map and adds assurance detail (owners, verification tasks) to sustain control effectiveness.
How do we define a “top event” for a major accident hazard?
The top event is the point at which control is lost but before consequences unfold—such as “loss of primary containment from the propane depropanizer overhead.” It should be specific, aligned with P&IDs and HAZOP nodes, and scoped so that threats and mitigations are relevant and non-generic. If the top event is too broad (“fire”), controls become vague; too narrow, and the bowtie becomes unmanageable and misses systemic threats.
How many barriers should a strong bowtie show?
Quality matters more than quantity. Each credited barrier should be independent, effective, and verifiable. Having three robust, well-assured preventive controls may be stronger than listing ten nominal ones. Where LOPA assigns SIL credit, ensure the bowtie reflects the same independence and avoids double-counting. The right number is the set that demonstrably keeps risk tolerable (e.g., ALARP) and can be reliably maintained.
How often should bowties be reviewed?
There is no universal frequency; reviews should be risk-based and event-driven. Typical triggers include incidents/near misses, significant MoC, major shutdowns/turnarounds, or new regulatory requirements. Periodic reviews (e.g., annual) can catch drift in performance standards, ownership, and assurance tasks. Day-to-day, barrier verification tasks ensure that control health is visible and current between formal reviews.
What sources of evidence support barrier performance standards?
Evidence includes SIS proof test results (IEC 61511), relief system inspection and service records, impairment logs for firewater and foam systems, alarm rationalization outputs, operator competency matrices, emergency drill findings, and inspection data (e.g., RBI). Incident investigations and near-miss reports are equally valuable—they often reveal latent conditions and escalation factors that degrade performance.
Can software replace face-to-face workshops for bowtie development?
Software helps with version control, visualization, and linking to KPIs, but it does not substitute for structured, cross-functional dialogue. Many critical insights emerge from operators’ and maintainers’ experiences in the field. A good approach is hybrid: use software to maintain a single source of truth and assurance workflows, while building the content collaboratively with SMEs and validating it on site.
How do UAE regulatory frameworks intersect with bowties?
Bowties help demonstrate a systematic approach to risk consistent with ADNOC HSE expectations, OSHAD risk management elements, Dubai Municipality EHS frameworks, and Civil Defence fire/life safety approvals. They provide an auditable line of sight from hazards to controls to assurance tasks—useful in safety cases, audits, and incident inquiries. They also support ISO 45001 and ISO 14001 management system requirements for risk control and continual improvement.
How should we connect bowties to KPIs and leadership oversight?
Define a small set of leading indicators tied to barrier verification (e.g., on-time proof tests, alarm response drills, impairment closure times) and lagging indicators from incidents. Summarize barrier health in routine leadership meetings, highlighting red/amber controls, systemic issues, and required decisions. The purpose is to enable timely action, not to create a reporting burden—so keep metrics meaningful and few.
Conclusion
Major accident hazards demand clarity, discipline, and sustained assurance. A bowtie translates technical depth from HAZOP, LOPA, and QRA into an operational picture that everyone can use: executives who set priorities, engineers who define performance standards, operators who verify critical controls, and responders who plan for worst-case scenarios. By defining the top event precisely, crediting only effective and independent barriers, and embedding verification into daily work, organizations strengthen their defenses across both prevention and mitigation. In UAE facilities, the method aligns naturally with ADNOC HSE expectations, OSHAD frameworks, Civil Defence requirements, and international standards like IEC 61511 and ISO 45001. Done well, Bowtie for Major Accident Hazard becomes not just a diagram but a living management practice.
To go further on this topic, NPM’s broader Bowtie Analysis Services UAE page covers this in more depth.
Explore NPM’s References
NPM’s references demonstrate how a barrier-based approach to process safety, integrity management, and emergency preparedness performs under real-world constraints—brownfield modifications, SIMOPS, harsh environments, and complex contractor interfaces. Across oil and gas production, refining, petrochemicals, power generation, manufacturing, and large-scale construction, our teams have supported clients by integrating bowties with HAZID, HAZOP, LOPA, and QRA; aligning critical controls with IEC 61511 lifecycle requirements; and building assurance programs that make barrier health visible to frontline teams and leadership alike. These references highlight practical outcomes: more focused maintenance backlogs, clearer impairment protocols for firefighting systems, crisper alarm response expectations, and better-prepared emergency teams. They also show how bowties help organizations meet the expectations of regulators and stakeholders—articulating what must never fail, what to do when a control is impaired, and how to justify ALARP decisions transparently. Beyond individual projects, the portfolio illustrates NPM’s ability to embed bowties within management systems (ISO 45001/14001) and leadership routines so that risk visibility is durable, not episodic. Whether the need is to strengthen a safety case, improve turnaround risk controls, or standardize critical control management across multiple assets, our references offer concrete examples and lessons learned that readers can adapt to their own context with confidence.
For more information about our references, visit Our References.
Speak With NPM
If you would like to discuss how a barrier-based approach could clarify risks at your facility, we are happy to share perspectives and practical considerations. Whether you are refining existing bowties or building a program from the ground up, a short conversation can help you frame the next steps. For any further questions or to speak with our team, Contact Us.