PHA Team Requirements

Design Hazard Review for New Processing Facility

PHA Team Requirements are often discussed in boardrooms and control rooms alike because the effectiveness of a Process Hazard Analysis depends as much on people as it does on methodology. In complex facilities — refineries, gas processing plants, offshore platforms, petrochemical units, bulk terminals, power and water utilities, and major construction projects — a well-constituted PHA team can be the difference between identifying a latent major accident hazard and overlooking it until it becomes an incident. This article unpacks what “good” looks like for team composition, competence, independence, and governance, with a focus on the UAE’s regulatory and operating context.

Before diving into the technical specifics, it helps to frame why team design matters. A PHA, whether conducted as HAZID, HAZOP, What-If/Checklist, Bowtie analysis, or supported by LOPA and SIL verification under IEC 61511, is fundamentally a structured conversation. The quality of that conversation is determined by who is in the room, what they know, how comfortable they are challenging assumptions, and how decisions are recorded and followed through. PHA Team Requirements, therefore, are not a paperwork issue but an operational risk control.

Across the UAE, PHA teams operate within a mosaic of expectations: ADNOC HSE requirements for operating companies and contractors, OSHAD SF in Abu Dhabi, Dubai Municipality and Civil Defence approvals, and international frameworks like OSHA PSM, CCPS concepts, ISO 45001, and ISO 14001. A robust approach reconciles these expectations with the realities of production schedules, shutdown windows, EPC deliverables, and brownfield constraints.

In what follows, we move from who should be involved, through why it matters, into practical setup and execution. Each section builds on the last, because clarity on accountability is a prerequisite for good facilitation, and facilitation is in turn the gateway to useful outcomes and credible records.

Who Does This Affect?

PHA Team Requirements

Defining who is affected clarifies who must be present and accountable. The topic touches a wide cross-section of stakeholders in high-risk industries:

  • HSE, Process Safety, and Risk Management leaders who sponsor and govern the PHA program.
  • Process engineers and discipline leads (mechanical, electrical, instrumentation and control, rotating equipment, civil/structural) who bring design intent and technical constraints.
  • Operations representatives — console operators, shift supervisors, area authorities — who understand how the plant is actually run, including start-up, shutdown, and abnormal situations.
  • Maintenance, asset integrity, and reliability engineers who contribute insight on inspection regimes, impairment management, and proof testing.
  • SIS/automation specialists who align LOPA outcomes and safety instrumented functions with IEC 61511 and alarm management practices.
  • Project management, construction, and commissioning personnel, especially during FEED, detailed design, and pre-startup safety reviews.
  • Contractor and vendor package engineers (compressors, fired heaters, relief devices, analyzers) who elucidate skid-specific hazards and safeguards.
  • Logistics and terminal operations teams for tank farms, jetties, truck loading, and marine interfaces, including control of simultaneous operations (SIMOPS).
  • Facilities management and power/water utilities staff for combined-cycle power plants, desalination units, and district cooling operations where process risks intersect with electrical safety and water chemistry.
  • Compliance officers and document controllers who ensure auditable traceability of the PHA lifecycle — planning, execution, actions, and revalidation.

Because decision-making in PHAs must reflect both design intent and operational reality, the affected parties are not just “invitees”; they are the core of a credible team. If they are not present, the analysis becomes theoretical, and assumptions proliferate.

Why This Matters

PHA Team Requirements

Having established who is involved, the question is why the composition, independence, and competence of the team are so critical. The stakes are high and multifaceted:

  • Major accident hazard prevention: Correctly identifying initiating events, escalation pathways, and barrier degradation factors reduces the likelihood of fires, explosions, toxic releases, and environmental harm.
  • Regulatory compliance: ADNOC operating companies, OSHAD SF requirements in Abu Dhabi, and Civil Defence approvals often expect documented, periodic PHAs and revalidations, with demonstrable competence for participants. While frameworks differ, the commonality is clear: competent, cross-functional teams and auditable decisions.
  • Alignment with international standards: IEC 61511 ties the quality of LOPA/SIL decisions to the quality of the hazard analysis that precedes them. API RP 14C/14J (for offshore), API 750 (management of process hazards), and CCPS guidance all presuppose strong team processes.
  • Insurability and due diligence: Insurers and lenders increasingly ask for evidence that PHAs are performed by competent teams with trackable action closure, particularly for brownfield expansions, debottlenecking, and new unit tie-ins.
  • Operational performance: Good PHAs pre-empt unplanned shutdowns and reduce nuisance trips by rationalizing safeguards, clarifying operating envelopes, and highlighting alarm rationalization opportunities.
  • Organizational learning: Diverse teams capture tacit knowledge — operator workarounds, maintenance realities, package-specific quirks — and embed it into risk controls, training procedures, and MOC governance.

In short, the team is the engine room of the PHA. Without the right people (and enough psychological safety to challenge assumptions), even the best methodology cannot deliver dependable outcomes.

Key Points to Understand

PHA Team Requirements

With the “who” and “why” in hand, we can define the essentials of a capable PHA team and how they fit together in practice.

1) Core roles and responsibilities

PHA Team Requirements

A PHA team generally includes a facilitator, scribe, discipline experts, and operational voices. The table below summarizes typical roles, responsibilities, and indicators of competence in a UAE context:

Role Primary Responsibility Competence Indicators
Facilitator Guide methodology (HAZID/HAZOP/What-If), maintain pace, manage bias, ensure coverage. 5+ years PHA leadership; familiarity with IEC 61511, CCPS; experience in sector (e.g., gas plants, power).
Scribe Capture node deviations, causes, consequences, safeguards, LOPA claims, and actions with traceability. Technical writing; plant nomenclature literacy; tool proficiency (PHA software or structured templates).
Process Engineer Explain design intent, PFD/P&ID basis, process control narrative, operating windows. Relevant degree; unit experience (e.g., distillation, cracking, dehydration, amine treating).
Operations Representative Describe real operating modes, start-up/shutdown, impairment management, and abnormal situations. Shift/console experience; authority to speak for operations; knowledge of SOPs and alarm response.
Maintenance/Integrity Provide inspection regimes, proof test intervals, bypass/override procedures, CMMS data. API/ASME familiarity; RCM knowledge; awareness of common-mode failures.
I&C/SIS Engineer Link safeguards to SIL targets, proof test coverage, and failure modes; ensure LOPA compatibility. IEC 61511 competence; alarm management; SIS lifecycle experience.
HSE/Process Safety Assure hazard coverage, barrier thinking, and alignment to corporate standards. Process safety background; bowtie/QRA literacy; familiarity with local regulatory expectations.
Electrical Address power distribution, UPS impacts, ESD interfaces, and ignition source controls. Arc-flash and hazardous area classification knowledge.
Vendor/Package Rep Clarify package-specific risks (compressors, heaters, relief systems) and safeguards. Detailed package design knowledge; evidence of configuration control.
Management Sponsor Resolve resource conflicts; sign-off risk acceptance; ensure action closure support. Decision authority; accountability for risk tolerability decisions.

2) Independence and authority

PHA Team Requirements

The facilitator must be independent enough to challenge assumptions, yet integrated enough to understand the facility’s context. Independence does not mean unfamiliar; rather, it means unconflicted. Similarly, the operations representative must have the authority to validate or reject assumptions about actual practices — particularly around overrides, isolation, permit-to-work, and impairment management.

3) Competence is demonstrable, not assumed

PHA Team Requirements

Competence should be evidenced by qualifications, plant or package experience, and prior PHA participation. In the UAE, this often means aligning team member CVs or competence matrices with internal policy and demonstrating to regulators or third-party reviewers that the team meets defined criteria. Typical elements include:

  1. Documented PHA methodology training (HAZOP/LOPA) for relevant members.
  2. Unit-specific experience (e.g., sour gas handling, LNG loading, naphtha hydrotreating, CCGT operations).
  3. Knowledge of company standards, ADNOC or OSHAD SF expectations, and applicable NFPA/API/IEC guidance.
  4. Evidence of independence for facilitators and absence of conflict for vendor representatives.
  5. Language proficiency to support clear bilingual discussions where needed (Arabic/English).

4) Information quality and document control

PHA Team Requirements

PHA teams are only as effective as the information they review. Up-to-date P&IDs, cause-and-effect diagrams, safeguarding narratives, safe operating limits, and shutdown keys are essential. Equally important is controlled distribution and versioning so that what is discussed corresponds to the latest approved design. Governance platforms and curated repositories (for example, CABINET NPM) illustrate how controlled access and change histories help preserve data integrity for safety-critical reviews.

5) Method selection and interface with LOPA/SIL

PHA Team Requirements

Different lifecycle stages and risk profiles warrant different methods. Early-stage projects may begin with HAZID to shape design, while detailed design and operations stages often use HAZOP. Where risk tolerability decisions depend on instrumented protection layers, LOPA is used, and SIL targets are set in line with IEC 61511. The team must include or have access to members who can bridge these methods and defend assumptions (β factors, proof test coverage, common-cause failures).

6) Realistic operating modes and human factors

Start-up, shutdown, and abnormal operations deserve special focus, as many incidents occur there. Teams should include members conversant with human-machine interfaces, alarm rationalization, and fatigue risk. Human factors specialists, when available, elevate discussions about cognitive load, ergonomics, and procedural use at the point of work.

7) Psychological safety and challenge culture

Even with the right badges in the room, a PHA stalls if people feel unable to challenge. Ground rules must promote constructive challenge, “what would make this fail?” questioning, and transparent action ownership. Facilitators should actively counter groupthink and ensure quieter voices (often the ones with deep tacit knowledge) are heard.

8) Action management and traceability

Actions must be clear, time-bound, and owned. The scribe’s discipline in recording unambiguous actions — with references to the node/deviation and evidence of closure — is vital for regulatory confidence. Integration with CMMS or project action trackers ensures actions survive the meeting.

How This Works in Practice

Translating principles into practice depends on lifecycle stage and facility type. Building on the fundamentals above, a practical setup may consider the following scenarios:

During FEED for a sour gas facility, HAZID workshops establish the high-level hazard register and inform plot plan decisions (e.g., separation distances, flare systems, emergency power). The team skews toward process, layout, and safety specialists, with early operations input. As the design matures to detailed design, HAZOP node selection aligns with P&IDs and control narratives; valve line-ups, setpoints, permissives, and trip logics are interrogated with operations and control room representation. Where HAZOP outcomes hinge on instrumented layers, LOPA sessions quantify risk and link directly to SIL verification and cause-and-effect matrices.

For brownfield debottlenecking in a refinery, the team must account for tie-ins, SIMOPS, and temporary conditions. Operations voices become central, because the realities of bypassing, temporary supports, and scaffolding change risk profiles. Maintenance and integrity experts provide insights into aging equipment, corrosion under insulation, and relief device adequacy. Vendor reps brief the team on package limits and startup constraints for retrofitted compressors or heaters.

In power and water utilities, system-level interactions matter. Electrical representatives weigh in on load shedding impacts on process safety functions. Instrumentation specialists link alarm flood scenarios to human factors risk, particularly during grid disturbances. The team composition reflects this interdependence, ensuring that ESD logic, UPS configuration, and process safeguarding narratives align.

Logistics and terminals bring different patterns: truck loading interfaces, marine operations, and tank management. Here, the team expands to include marine or transport specialists and terminal operators intimately familiar with jetty operations, nitrogen purging, and overfill prevention per API 2350. The PHA must realistically reflect ship-shore interfaces and contractor roles.

Across all scenarios, the administrative foundations are the same: confirm that the P&IDs/C&E drawings are current; distribute a pre-read pack; clarify ground rules; define action coding and risk ranking scales; and maintain a clean audit trail. The outcome is a defensible record that can be presented to internal assurance, third-party reviewers, or authorities as required.

Benefits and Practical Use Cases

When PHA teams meet the requirements outlined earlier, organizations realize benefits that are immediate and measurable, as well as strategic:

  • Better hazard coverage: Cross-functional participation surfaces credible initiating events and realistic consequence paths that single-discipline reviews miss.
  • Stronger safeguards: Interfaces between process control, mechanical protection, and instrumented layers are clarified, reducing the chance of “ghost” safeguards that exist only on paper.
  • Higher-quality LOPA and SIL decisions: With the right instrumentation expertise and operational insight in the room, assumptions about proof test coverage, response times, and independence stand up to scrutiny.
  • Fewer surprises at start-up: Pre-commissioning insights from operations and vendors reduce punch-list items and late changes that drive cost and risk.
  • Credible regulatory engagement: Documented competence and action traceability build confidence with authorities, insurers, and corporate auditors.
  • Organizational learning: Actioned findings feed MOC procedures, alarm rationalization, and competency programs, improving resilience over time.

Consider practical use cases that illustrate the difference team composition makes:

  • Refinery heater upgrade: With a vendor combustion specialist present, the team clarifies flame scanner failure modes and validates permissive logic, avoiding an under-protected light-off scenario.
  • Sour gas compression retrofit: An experienced operator flags a start-up sequencing nuance that exposes a potential overpressure case, prompting relief system verification and procedural updates.
  • Terminal truck loading expansion: A logistics lead explains contractor-involved operations and highlights a spill response gap during night shifts, leading to a revised staffing and alarm strategy.
  • CCGT plant grid disturbance: Electrical and I&C engineers jointly test the hypothesis that a UPS transient can disable an instrumented protection layer, prompting a design tweak and test interval change.

These examples underscore a recurring theme: the “right people, right data, right method” triad. It’s not that teams solve everything during the meeting; rather, they generate targeted, actionable work that closes real risk gaps.

Best Practices and Points of Caution

To turn principles into repeatable success, organizations can adopt several practical habits while watching for common pitfalls.

Best practices

  • Define a competency matrix: Specify facilitator credentials, minimum operations experience for representatives, and required discipline coverage per unit type (e.g., cryogenics, high-pressure hydrogen, chlorine handling).
  • Establish independence rules: Clarify when facilitators must be independent of the design contractor and how vendor participation is managed to avoid conflicts of interest.
  • Prepare a consistent pre-read pack: Current P&IDs, control narratives, alarm rationalization status, ESD/PSD logic, relief scenarios, and relevant incident learnings.
  • Adopt clear ground rules: One conversation at a time; challenge assumptions; ask for evidence; capture dissent and actions; articulate operating modes (normal, start-up, shutdown, maintenance, emergency).
  • Use structured recording: Scribes should map each cause-consequence-safeguard-action chain to node, deviation, and drawing references, avoiding vague phrasing.
  • Link to LOPA/SIL cleanly: When a safeguard is claimed, immediately note proof test intervals, diagnostic coverage, and independence for later verification.
  • Build bilingual clarity: Where teams are mixed Arabic/English, agree on terminology, abbreviations, and translation points up front to prevent misunderstandings.
  • Time-box and rotate voices: Keep momentum without rushing; draw out quieter participants; rotate who speaks first to minimize anchoring bias.
  • Protect psychological safety: Normalize “I might be wrong, but…” statements. Some of the most valuable insights start that way.
  • Close the loop: Track action owners, due dates, and completion evidence; integrate with project or CMMS systems to sustain momentum after the workshop.

Points of caution

  • Too many people: Oversized teams dilute accountability and slow progress. Include the essential contributors and provide a channel for targeted offline input.
  • Missing operations representation: No matter how strong the design team is, a PHA without real operational insight invites blind spots.
  • Legacy drawings and data: If P&IDs or safeguarding narratives are stale, the PHA will misfire. Invest time up front to validate sources.
  • Unquestioned vendor claims: Vendors are valuable, but their protective claims must be consistent with proof testing realities and independence needs.
  • Groupthink: Senior voices can dominate. Facilitators must actively rebalance to surface minority viewpoints.
  • Underplaying human factors: Many incidents hinge on alarms, interfaces, and procedures; treat human performance variability as a core analysis dimension.
  • Neglecting cyber-physical interfaces: Instrumentation and control safeguards can be affected by network and security architectures; bring the right expertise where relevant.

Frequently Asked Questions About PHA Team Requirements

How many people should be on a PHA team?

Enough to cover all relevant disciplines and operations without overwhelming the discussion. For a typical unit-level HAZOP, 6–10 core members is common: facilitator, scribe, process engineer, operations representative(s), maintenance/integrity, I&C/SIS, and HSE/process safety. Additional specialists (electrical, vendor reps) can join for targeted nodes. The governing principle is complete coverage with manageable dynamics.

Who can facilitate the PHA?

The facilitator should be experienced, independent of conflicts, and trained in the chosen method. They must be adept at managing pace, drawing out contributions, and challenging assumptions. In complex analyses involving LOPA/SIL, the facilitator should be familiar with IEC 61511 and able to anticipate where deeper SIL verification will be needed. Independence from the design package or project incentives is often beneficial to preserve objectivity.

Does the UAE regulator require specific certifications for PHA team members?

Requirements vary by authority and sector. While many frameworks (ADNOC HSE, OSHAD SF, Civil Defence approvals) do not mandate a single external certification, they expect demonstrable competence: training records, relevant experience, and alignment to recognized standards (e.g., CCPS guidance, IEC 61511 for SIS-related analyses). Your internal policy should define competence criteria, and you should be prepared to show evidence.

How often should the PHA be revalidated, and must the same team return?

Five-year revalidation is a common benchmark aligned with international practice, or earlier if major changes occur under MOC. The exact interval depends on company policy and regulatory expectations. While continuity helps, revalidation benefits from fresh perspectives. Aim for a blend: some returning members for context, plus new voices to challenge drift and capture operational changes.

Can contractors and vendors participate, or does that compromise independence?

Contractors and vendors are often essential for package-specific hazards and safeguards. Their participation should be transparent and managed: declare potential conflicts, restrict discussions to relevant scope, and ensure that risk decisions remain with the operating company. Independence concerns primarily apply to facilitation and to final risk acceptance.

What documentation must the team produce for audit or authority review?

At minimum: meeting agenda and attendance, current document set used (P&IDs, narratives), node/deviation records with causes, consequences, safeguards, and actions; risk ranking criteria; LOPA worksheets where applicable; and an action register with owners and due dates. Traceability is key: an auditor should be able to follow a line of reasoning from hazard to control to closure evidence.

Do remote or hybrid PHA sessions work?

They can, with strong preparation. Stable visualization of drawings, disciplined turn-taking, and robust recording become more important. Hybrid sessions should ensure that remote participants are not marginalized. For intensive nodes or contentious issues, many teams still prefer in-person sessions to preserve engagement and nuance.

How do PHA teams integrate with QRA and Bowtie analysis?

PHA outputs (causes, consequences, safeguards, and action effectiveness) inform QRA frequency and consequence modeling, as well as Bowtie barrier diagrams. Conversely, QRA and Bowtie results can focus PHA attention on high-risk scenarios and barrier health. Cross-pollination requires consistent taxonomy and data stewardship so that terminologies align across methods.

What if the team cannot reach consensus on a risk decision?

Record the dissenting views and the basis for each position, then elevate the decision to the appropriate risk owner or management forum. The facilitator’s role is to surface the assumptions, not to force agreement. Where uncertainty is high, actions to obtain further evidence (tests, calculations, vendor clarifications) are often the best immediate outcome.

Are there minimum experience thresholds for operations representatives?

There is no universal number, but operations representatives should have sufficient time-on-plant and exposure to abnormal and transitional operations to speak credibly for the team. Shift supervisors or senior console operators are common choices. What matters most is that they are empowered to challenge design assumptions and accurately represent actual practices.

Conclusion

Bringing the discussion full circle, PHA Team Requirements are less about a checklist and more about orchestrating the right expertise, independence, and behaviors to surface and control risk. We began by identifying who is affected — from HSE leadership to operators and vendors — and why team quality matters for regulatory confidence, major hazard prevention, and operational performance. We then examined the mechanics: role clarity, competence evidence, document integrity, method selection, human factors, and action traceability. Practical examples showed how this plays out across refineries, gas plants, power and water utilities, and terminals, while best practices and cautions translated principles into everyday discipline. If there is a single takeaway, it is that the caliber of the people in the room — and the conditions under which they collaborate — will define the value of the analysis as surely as the method chosen.

To go further on this topic, NPM’s broader Process Hazard Analysis Services UAE page covers this in more depth.

Explore NPM’s References

NPM’s track record spans complex industrial contexts where the rigor of risk assessment must be matched by the pragmatism of operations. Over the years, our teams have supported operators, EPCs, and utility providers across multiple sectors — oil and gas production and processing, refining and petrochemicals, bulk storage and terminals, power generation and water desalination, and major construction programs involving SIMOPS and high-hazard interfaces. The common thread is not a single methodology, but disciplined collaboration: ensuring that facilitators, operators, discipline engineers, and vendor specialists converge around accurate data, clear ground rules, and an action-focused mindset. This approach has helped clients strengthen barrier health, align instrumented layers with IEC 61511, rationalize alarms, and construct resilient operating envelopes that stand up to both regulator and insurer scrutiny. Our references illustrate how credible PHA records integrate with MOC, pre-startup safety reviews, and broader risk studies such as QRA and Bowtie, turning workshop insights into sustained operational improvements. Whether the setting is an offshore compression upgrade, a refinery heater replacement, a terminal expansion, or a CCGT power block integration, the throughline is consistent: competence, independence, and accountability. We invite you to explore how this philosophy is reflected in our completed work and the outcomes our clients have achieved.

For more information about our references, visit Our References.

Speak with NPM

If you have questions about team composition, competence criteria, or how to structure upcoming PHAs for your facility, we’re happy to discuss practical approaches grounded in real operations. A short conversation can help you pressure-test plans and avoid common pitfalls before workshops begin.

For any further questions or to speak with our team, Contact Us.