Skip to content
Risk Based Process Safety (RBPS)Manage Risk

Conduct of Operations

Day to day operating discipline across shift handover, alarm response, and abnormal situation management

Strategic context

What this element is and why it matters

Conduct of Operations is the daily operating discipline that converts the formal PSM system into genuinely safe operation, covering how shift teams hand over, how operators respond to alarms, how abnormal situations are managed, how unit walks are conducted, and how communication discipline is sustained between the control room and the field. The Naval Reactors model, with its formal communication, repeat back protocol, and integrity in reporting, is the canonical reference. Texas City and Buncefield both included Conduct of Operations findings, and our team helps your facility build the discipline that prevents them.

Conduct of Operations

Individual significance for organisations

Conduct of Operations is where management system intention becomes operating floor reality. Sites with strong discipline here catch precursor events before they escalate, while sites without it experience the same precursors and simply miss them. The element is also the most operator engaged of all, because investing in it sends a clear signal that the organisation respects operating discipline.

Contribution to Risk Based Process Safety (RBPS)

Conduct of Operations is the operational embodiment of every pillar three element. It activates Operating Procedures (Element 8), enforces Safe Work Practices (Element 9), integrates with Asset Integrity (Element 10) through integrity operating window response, and channels Workforce Involvement (Element 4) through shift discipline. Element 15 is also a strong leading indicator of culture maturity under Element 1.

Key requirements

What compliant execution looks like

A formal shift handover with a documented checklist
Operator response to alarms per EEMUA 191 and ISA 18.2 priority
An abnormal situation management programme drawn from the ASM Consortium
Disciplined field operator walk downs
Three way communication discipline based on the Naval Reactors model
Adherence to the operating envelope with integrity operating window response
Implementation methodology

How we implement this element

A focused six step methodology calibrated to deliver conduct of operations as a working capability rather than a documented compliance artefact.

Operating Discipline Audit

We observe current shift practice across handover, alarm response, walk downs, and communication, and benchmark it against the CCPS, ASM Consortium, and Naval Reactors models.

Shift Handover Standardisation

We build a formal handover checklist covering process status, ongoing permits to work, alarm patterns, MOC in progress, and abnormal situation history, with signoff required.

Alarm Response Discipline

We align the response with EEMUA 191 and ISA 18.2 priority response times, specify the operator action per priority, and integrate it with the HMI per ISA 101.01.

Abnormal Situation Management Programme Adoption

We adopt the Abnormal Situation Management framework covering situation awareness, decision support, and escalation paths, and align it with an operator workload analysis.

Communication Discipline

We establish a three way communication protocol of instruction, repeat back, and confirmation, with the phonetic alphabet for critical readings, and integrate it into the shift culture.

Operating Envelope Discipline

We set integrity operating window response per API RP 584, give the operator clear authority to act within the envelope, and route any excursion to engineering escalation.

Implementation flow

Element implementation flow chart

A decision gated workflow that shows the actual sequence of activities from initiation through steady state operation, with key decision points highlighted.

Start
A shift change or unit walk down is initiated
Formal Handover Checklist
Process status, permits to work, alarm patterns, MOC, and abnormal situation history
Handover Signoff
Outgoing and incoming operator countersign
Alarm Received
The DCS HMI alerts the operator per EEMUA and ISA priority
Priority Recognition
The operator identifies the priority level and required response time
Response per Procedure
Three way communication and action per the abnormal situation management framework
Decision
Operating window excursion?
Decision gate
Operator Authority Action
Corrective action within the envelope
Engineering Escalation
Out of envelope, so an engineering review is triggered
Abnormal Situation Library Updated
The lesson is captured for future shift training
Walk Down Discipline
An operator field walk per the shift schedule
Deliverables

What we produce

  • An operating discipline audit and gap report
  • A standardised shift handover checklist
  • An alarm response procedure per priority
  • An abnormal situation management programme charter
  • Three way communication training and protocol
  • An integrity operating window response procedure and operator authority matrix
Common pitfalls

Where execution fails

  • A shift handover done verbally with no documented signoff
  • Operator alarm response that is not aligned to priority
  • Walk downs skipped during high workload periods
  • Informal communication with no repeat back discipline
Standards & references

Codes this element is built on

CCPS Guidelines for the Management of Conduct of Operations and Operational DisciplineASM Consortium Effective Operations PracticesEEMUA 191 and ISA 18.2 (Alarm Response)ISA 101.01 (HMI Design)API RP 584 (Integrity Operating Windows)Naval Reactors Communication Discipline Reference
Implement this element

Talk to us about implementing Conduct of Operations

We can scope this element implementation against your facility, regulatory context, and existing management system maturity, then integrate it with the other Risk Based Process Safety (RBPS) elements you already operate.