Functional Safety Roles And Responsibilities are the backbone of how high-hazard industries in the UAE translate standards like IEC 61511 and IEC 61508 into real-world control over major accident hazards. When roles are clearly defined, accountable, and competent, safety instrumented systems (SIS), fire and gas systems (F&G), and interlocks do what they should: prevent loss of containment, escalation, and harm. When roles are blurred or undocumented, gaps appear—in hazard analysis, in design verification, in proof testing, in override control—and risks can slip through despite good intentions. This article maps the people dimension of functional safety so that HSE and operations leaders can align their organizations to the safety lifecycle and keep critical risk controls reliable over time.
Although the standards provide the “what” and “why,” it is the practical assignment of accountabilities—the “who” and “how”—that determines whether safeguards perform when they are needed. Across upstream and downstream oil and gas, petrochemicals, power generation, logistics terminals, and complex construction projects involving machinery safety, the discipline is the same: establish unambiguous ownership, ensure competence and independence, and connect day-to-day work to lifecycle requirements.
Who Does This Affect?

Clear ownership for functional safety touches nearly every function involved in designing, operating, and changing hazardous processes. The following roles are typically involved in UAE facilities such as refineries, gas processing plants, offshore platforms, pipelines and terminals, combined-cycle power stations, and large manufacturing operations:
- Accountable executive or duty holder who owns process safety risk on behalf of the company and sets the governance framework.
- Functional Safety Manager (FSM) or equivalent role responsible for the safety lifecycle framework, competency program, and coordination of assessments.
- Process engineering and risk teams who lead HAZID/HAZOP, LOPA, SIL determination, and define risk acceptance criteria aligned with corporate and ADNOC HSE expectations.
- Control, instrumentation, and electrical (C&I/E&I) engineers, SIS specialists, and F&G engineers who specify, design, and validate SIFs, trips, and alarms.
- Operations supervisors and control room teams who manage overrides, impairment, and day-to-day use of interlocks and alarm systems (ISA 18.2).
- Maintenance and turnaround planners, technicians, and reliability engineers who manage proof testing, bypasses during work, and repair strategies.
- Project managers and EPC/Integrator teams on capital projects who implement lifecycle requirements from concept to commissioning.
- Independent functional safety assessors (FSA) who provide lifecycle-stage assurance with appropriate independence per IEC 61511.
- Cybersecurity leads and OT network engineers ensuring SIS and BPCS segregation and resilience aligned to IEC 62443.
- HSE managers and quality/compliance officers aligning with OSHAD-SF, Dubai Municipality approvals, Civil Defence for F&G, and MOHRE worker safety requirements.
Because functional safety responsibilities cut across disciplines and organizations (owner-operator, EPC, integrators, OEMs), the RACI often spans contractual boundaries. That reality makes traceable role definition and interface agreements essential—especially where third parties commission or maintain safety-related control systems.
Why Clear Accountability for Functional Safety Matters

After identifying major accident hazards via HAZID, HAZOP, QRA, and Bowtie analysis, the facility depends on engineered barriers—SIFs, ESD systems, relief and vent systems, and F&G detection—to keep risk as low as reasonably practicable. However, barriers only work as designed when people make the right technical and operational decisions along the safety lifecycle. The consequences of unclear responsibilities show up in familiar ways: overdue proof tests, undocumented bypasses, late action on impairment, undocumented logic changes, misaligned MOC, or inadequate competency for SIL verification. These issues directly erode risk reduction (PFDavg increases), increase spurious trip exposure, and jeopardize regulatory compliance.
In the UAE, regulators and authorities having jurisdiction expect robust governance: OSHAD requires systematic risk management; Dubai Municipality and Civil Defence scrutinize F&G performance for buildings and industrial occupancies; ADNOC has stringent HSE rules for operating companies and contractors; and MOHRE emphasizes safe systems of work. Audit readiness under IEC 61511 and alignment to corporate standards are not just paperwork—they are leading indicators of whether process risk is being managed.
Ultimately, clarity around roles addresses three objectives: prevent major incidents, maintain demonstrable compliance and assurance, and optimize lifecycle cost and reliability of safety systems. When accountability is visible and supported by competence and independence, the organization can show—with evidence—that SIFs are correctly specified, verified, validated, and maintained throughout change.
Key Points to Understand

What “functional safety” means in industrial operations

Functional safety is the part of overall safety that depends on a system operating correctly in response to inputs. In practice, this includes SIS, BPCS interlocks, F&G detection and shutdowns, burner management (NFPA 85/86), emergency shutdown (ESD), and machinery safety (ISO 13849/IEC 62061) for rotating equipment, conveyors, and cranes. The objective is to design, verify, install, validate, operate, and maintain these functions so they achieve a target risk reduction (SIL or performance level) with tolerable spurious trip frequency.
Standards establish lifecycle discipline: IEC 61511 for process industry SIS, supported by IEC 61508 for devices and systematic capability, ISA 18.2 for alarm management, and IEC 62443 for cybersecurity of industrial automation and control systems. API RP 14C and API RP 750 inform offshore and process safety management approaches, respectively, often referenced by operators in the region. Your facility type and hazard profile determine which standards are explicitly in scope, but the role clarity principles apply across the board.
The safety lifecycle and RACI alignment

IEC 61511 organizes work into lifecycle stages: hazard and risk assessment, allocation of safety functions (with SIL targets), SRS development, design and engineering, installation and commissioning, validation, operation and maintenance, modification (MOC), and decommissioning. Independent functional safety assessment (FSA) checkpoints sit across these stages. A practical way to make the lifecycle actionable is to align roles to each activity using a RACI (Responsible–Accountable–Consulted–Informed). The table below summarizes typical role-to-accountability mapping; adapt it to your organization and contractor interfaces.
| Role | Primary Accountability | Key Lifecycle Focus | Required Independence (IEC 61511) |
|---|---|---|---|
| Accountable Executive/Duty Holder | Owns process safety risk and governance | Approves lifecycle policy, tolerability criteria, and resource commitment | Independent from day-to-day SIS design decisions |
| Functional Safety Manager (FSM) | Implements lifecycle processes and competence program | Coordinates HAZOP/LOPA, SRS quality, verification plan, FSA readiness | Organizational independence from design teams for assurance |
| Process Engineer/Risk Analyst | Leads hazard/risk studies and SIL determination | HAZID/HAZOP, LOPA, target SILs, proof test interval rationale | May be same org as design; independent verification required |
| SIS/Control Systems Engineer | Specifies and designs SIFs and logic | SRS realization, device selection per IEC 61508/61511, CCF mitigation | Design verified by independent competent person |
| Operations Supervisor | Controls overrides and impairment; ensures operator response | Override permits, alarm response procedures, shift handover | Independent from maintenance scheduling decisions |
| Maintenance/Reliability Lead | Proof testing, repair, and SIF availability tracking | Proof test plans/coverage, spares, bad actor resolution | Independent from operations approval of extended bypass |
| Independent Assessor (FSA) | Lifecycle stage assurance (FSA 1–5) | Confirms compliance, competence, and evidence integrity | Independent from those responsible for the work being assessed |
| Cybersecurity Lead (IACS) | Protects SIS integrity against cyber threats | Segregation, patching policies, access control, incident response | Independent review of security risk assessments |
| EPC/Integrator | Executes design/implementation under owner governance | Implements SRS, manages suppliers, factory/site acceptance tests | Subject to owner/operator independent verification and FSA |
Core responsibilities you should expect to see

Across the lifecycle, several responsibilities are non-negotiable, even though the role that holds them may vary by organization:
- Setting and maintaining corporate functional safety policy, tolerability criteria, and competence requirements.
- Conducting HAZOP/LOPA with competent, independent facilitation and documentation control.
- Translating risk reduction targets into a high-quality Safety Requirements Specification (SRS) with clear SIF boundaries and proof test strategies.
- Independent design verification and SIL verification (including PFDavg and spurious trip rate checks) with documented assumptions.
- Validation planning and execution: FAT, SAT, cause-and-effect testing, loop checks, and proof test procedure validation.
- Operational control: managing overrides, impairment, alarm response, and permit-to-work interfaces (especially with hot work and confined space).
- Maintenance and reliability: proof test planning, coverage and intervals, bad actor analysis, and spares strategy.
- Management of change (MOC): controlling logic changes, setpoint edits, and device substitutions, with updated SRS and drawings.
- Assurance: FSA at appropriate lifecycle stages, KPI tracking (e.g., overdue proof tests, SIF bypass hours), and leadership review.
- Cybersecurity for SIS and F&G: segregation from BPCS, access control, and backup/restore integrity aligned to IEC 62443.
Competence, independence, and documentation

Three cross-cutting principles keep the lifecycle credible. First, competence: each responsibility must be assigned to a role that can demonstrate knowledge, skill, and experience for the task. Second, independence: the person verifying or assessing must be sufficiently independent from those who performed the work, as specified by IEC 61511 (especially for FSA and SIL verification). Third, documentation: decisions and evidence must be complete, controlled, and retrievable—from HAZOP minutes and LOPA worksheets to SRS revisions, calculation files, validation results, and proof test records.
Many organizations rely on structured document and knowledge management to keep this evidence available across years of operation and workforce turnover. For teams seeking a centralized, auditable repository approach that complements technical lifecycle artifacts, it can help to review examples of organized knowledge frameworks such as CABINET NPM, which illustrates a way to bring governance and accessibility to critical records without diluting technical rigor.
How This Works in Practice

Turning principles into daily practice means making sure the right people have the right authority at the right time. Consider a brownfield refinery revamp that introduces new fired heaters and modifies an existing SIS. The process team refreshes the HAZOP for new operating envelopes, then runs LOPA to confirm whether existing trips still achieve target SIL. The SIS engineer revises the SRS to separate burner management from process trips and addresses common cause failure by diversifying transmitters. Independent SIL verification recalculates PFDavg based on updated proof test coverage. Meanwhile, operations and maintenance agree a revised override policy for startup heater light-off, with explicit authorization levels and time limits. Before start-up, validation testing spans cause-and-effect matrices and field proof tests, and the independent assessor completes FSA-3 to confirm readiness for operation.
In a gas compression facility onshore, the picture looks different but the logic is the same. A spate of spurious trips linked to suction pressure transmitters triggers a focused review. Maintenance discovers partial proof tests missed a failure mode; reliability proposes an interval change and device upgrade; the SIS engineer assesses the impact on PFDavg and spurious trip rate; and the FSM updates the proof test procedures, making sure the change goes through MOC. Operations receives refresher training on bypass control and shift handover to prevent silent impairments. The roles are distinct, but coordinated—each doing its part to restore performance and availability while maintaining risk reduction.
On an offshore platform, overrides are common during well workovers. The operations supervisor issues an override permit aligned with the impairment standard, the control room logs the duration, and the FSM’s dashboard aggregates total SIF impairment hours. If a bypass exceeds the threshold, the accountable executive must confirm continued operation is justified or order a controlled shutdown. Civil Defence requirements may add additional constraints for F&G availability in occupied modules; ensuring these authorities’ expectations are reflected in local procedures is part of the HSE manager’s remit.
For power generation (CCGT), boiler and turbine protection functions sit alongside process trips. NFPA 85 burner management rules and OEM trip logic bring additional stakeholders—the OEM and turbine protection engineers. The EPC delivers the integrated control and safety system (ICSS), but the owner must still assign internal roles for SRS ownership, acceptance of device selections, and long-term proof testing. Clarifying who within the owner organization signs off on deviations during commissioning prevents last-minute decisions that could undermine independence or lifecycle documentation.
Benefits and Practical Use Cases
When Functional Safety Roles And Responsibilities are explicit, practiced, and audited, the organization sees tangible results that go beyond compliance checklists. Among the most relevant benefits for UAE industrial operators are:
- Improved risk control: SIFs deliver designed risk reduction because assumptions from HAZOP/LOPA flow through design, validation, and proof testing without dilution.
- Fewer spurious trips and associated production losses: spurious trip analysis is owned, test coverage is optimized, and device selection reflects true service conditions.
- Regulatory confidence and audit readiness: OSHAD, Dubai Municipality, Civil Defence, and ADNOC requirements map to clean evidence trails; findings become opportunities, not crises.
- Faster, safer modifications: MOC interfaces with SRS ownership and independent verification, preventing logic edits from bypassing lifecycle controls.
- Higher SIS availability: impairment is tracked, overrides are time-limited, and repair priority reflects risk criticality.
- Resilient operations: cybersecurity, alarm management, and mechanical integrity align with functional safety so that interdependencies don’t create blind spots.
Concrete use cases include establishing an enterprise-wide competence matrix for functional safety roles; implementing an override permit system with automated notifications for time-at-risk; integrating proof test planning with CMMS to manage intervals and coverage; and setting up a cross-functional “SIS review board” chaired by the FSM to resolve design and operational trade-offs with documented, independent verification.
Best Practices and Points of Caution
Building a durable model for role clarity requires attention to both governance and frontline realities. The following practices help organizations sustain performance over years of operation and organizational change:
- Write down your RACI and keep it alive: Align every lifecycle activity to a named role, not just a department. Include contractors and system integrators where they act on your behalf.
- Separate authority for overrides from those requesting them: Require at least one level of independent approval for extended or safety-critical bypasses.
- Define competence for each responsibility: Use a matrix that maps tasks to training, experience, and periodic reassessment. Competence is evidence-backed, not self-declared.
- Treat the SRS as a living baseline: All MOC affecting functions, setpoints, or devices must update the SRS, calculations, and drawings. No “shadow logic.”
- Verify with independence: Ensure design verification and SIL verification are performed by individuals or teams independent from the original design.
- Focus on proof test coverage: Specify what each test detects and what it cannot, then address uncovered failure modes through design or interval changes.
- Track KPIs that matter: Overdue proof tests, SIF impairment hours, nuisance trip rate, and MOC backlogs are leading indicators for leadership review.
- Harden SIS against cyber risk: Enforce network segregation from BPCS, restrict access, and maintain validated backups and restore drills.
- Integrate alarm management: Align ISA 18.2 practices so alarms support, not compete with, safety functions—especially during abnormal operation or startup.
- Engage authorities early: Where Civil Defence approvals or ADNOC standards drive F&G or ESD performance, reflect their expectations in your lifecycle documents and validations.
Common pitfalls include allowing EPC or vendor schedules to dictate the independence of verification, treating FSA as an after-the-fact audit rather than a planned assurance step, underestimating the resource load of proof testing during turnarounds, and failing to close the loop between bad actor analysis and SRS updates. By anchoring decision rights and competence to each of these areas, organizations avoid the drift that can otherwise accumulate between design intent and operational reality.
Frequently Asked Questions About Functional Safety Roles and Responsibilities
Who should be the “Accountable Executive” for functional safety?
This is typically a senior leader (e.g., plant manager, asset director, or operations VP) who owns process safety risk and approves the functional safety policy, resources, and tolerability criteria. The role is not about doing the technical work; it is about ensuring the organization has competent people, clear processes, and adequate assurance.
Can the same engineer design and verify a Safety Instrumented Function?
IEC 61511 requires that verification be performed by a competent person independent from those responsible for the work being verified. In smaller organizations, this can be achieved by organizational separation or by an independent competent person not involved in the original design.
What is the difference between validation and proof testing?
Validation confirms the installed safety functions meet the SRS prior to operation (e.g., FAT, SAT, cause-and-effect checks). Proof testing is a periodic activity during operation to reveal hidden failures and maintain the claimed risk reduction. Validation is lifecycle entry control; proof testing sustains performance over time.
How do operations and maintenance share responsibility for overrides?
Operations typically owns the authorization and control of overrides and impairment, while maintenance coordinates proof tests and repairs that may require bypasses. A defined permit process sets time limits, authority levels, and handover requirements, ensuring the risk is understood and managed by both parties.
Who leads a LOPA, and how does that connect to SIL verification?
A competent process risk engineer usually facilitates LOPA, with participation from operations, maintenance, and C&I. The LOPA output (target SIL and assumptions) feeds the SRS and SIL verification calculations performed by an independent competent engineer, ensuring the design achieves the claimed risk reduction.
When is an Independent Functional Safety Assessment (FSA) required?
IEC 61511 defines FSA at multiple stages: concept (FSA-1), design (FSA-2), pre-startup/commissioning (FSA-3), operation/maintenance (FSA-4), and modification/decommissioning (FSA-5). The assessor must be independent of those responsible for the lifecycle activities being assessed.
How should we treat OEM trip logic and packaged units in functional safety governance?
Packaged equipment skids (e.g., compressors, furnaces) often arrive with OEM protection logic. The owner remains responsible for integrating these functions into the overall SRS, verifying interfaces, and ensuring proof test regimes and MOC controls apply to the package as well.
What KPIs help leaders know if roles and responsibilities are working?
Useful KPIs include overdue proof tests, total SIF impairment hours, top nuisance trip causes and rates, proportion of MOC affecting SRS, closure of FSA findings, and competence reassessment completion. These indicators connect day-to-day work to risk reduction performance.
Bringing It Together
Functional safety only delivers its promise when people, processes, and technology align through the lifecycle. By defining the accountable executive’s ownership, appointing a Functional Safety Manager to orchestrate the framework, and assigning competent, independent roles for analysis, design, verification, validation, operation, maintenance, and assurance, organizations keep safety functions effective and evidence-based. The UAE’s regulatory environment and the demands of complex assets—refineries, gas plants, offshore platforms, power stations, and storage terminals—make this clarity non-negotiable. The practical steps discussed above—RACI alignment to lifecycle stages, living SRS discipline, independent verification and FSA, controlled overrides, and targeted KPIs—turn standards into reliable barriers.
To go further on this topic, NPM’s broader Functional Safety Management Services UAE page covers this in more depth.
Our References
NPM’s references demonstrate how role clarity and lifecycle discipline translate into safer, more reliable operations across a wide range of industries and facility types worldwide. Our work has spanned greenfield and brownfield contexts: integrating functional safety governance into major refinery upgrades; aligning SIS responsibilities during complex offshore platform modifications; harmonizing SRS ownership and MOC across multi-plant petrochemical networks; and bringing proof test coverage and KPI tracking into routine management reviews at gas processing facilities and CCGT power stations. In each case, the emphasis has been on establishing clear, auditable accountability for hazard analysis, SIL determination, design verification, validation, operations control, maintenance execution, and independent assessment in line with IEC 61511.
Beyond the process industries, NPM’s teams have supported machinery safety programs in advanced manufacturing, ensuring that performance levels and interlock responsibilities are well-defined and competent. We have helped clients connect alarm management (ISA 18.2) and industrial cybersecurity (IEC 62443) to their functional safety models, eliminating organizational blind spots where responsibilities overlap. Whether coordinating owner-operator, EPC, integrator, or OEM roles, our track record shows that clarity of responsibility, backed by competence and independence, is the single strongest predictor of sustained functional safety performance. Stakeholders—from accountable executives and Functional Safety Managers to technicians and independent assessors—can see their part in the lifecycle and how their decisions affect risk reduction and availability. This transparency builds confidence with regulators and insurers while improving operational stability and cost control.
For more information about our references, visit Our References.
Have Questions? Speak with NPM
If you would like to discuss how these role definitions map to your organization or a specific asset, our team is happy to share perspective. We welcome technical questions on lifecycle responsibilities, competence models, or assurance planning. For any further questions or to speak with our team, Contact Us.