Skip to main content

Safety Instrumented Systems (SIS) for Oilfields

By NFM Consulting 5 min read

Key Takeaway

Safety Instrumented Systems (SIS) for oilfield applications protect personnel and equipment by automatically executing emergency shutdown functions when hazardous conditions are detected. Designed to IEC 61511 standards, oilfield SIS systems provide independent safety protection separate from the basic process control system (BPCS), achieving Safety Integrity Levels (SIL) 1 through 3 for functions ranging from wellsite ESD to H2S emergency response.

What Is a Safety Instrumented System?

A Safety Instrumented System (SIS) is an independent, dedicated control system designed to bring a process to a safe state when hazardous conditions are detected. Unlike the Basic Process Control System (BPCS), which manages normal operations, the SIS only activates when the BPCS fails to control a dangerous situation or when conditions exceed safe operating limits. The SIS is the last automated line of defense before physical consequences (explosion, toxic release, equipment destruction) occur.

In oilfield applications, SIS functions include high-pressure shutdown of wells and flowlines, emergency shutdown (ESD) of facilities, fire and gas detection with automatic suppression activation, and H2S release detection with automated isolation. The design, implementation, and maintenance of these systems must follow IEC 61511, the international standard for safety instrumented systems in the process industries.

IEC 61511 and the Safety Lifecycle

Safety Integrity Levels (SIL)

IEC 61511 defines four Safety Integrity Levels (SIL 1 through SIL 4) that specify the required risk reduction factor for each safety function. In upstream oil and gas, SIL 1 and SIL 2 are most common:

  • SIL 1: Risk reduction factor of 10-100x. Probability of Failure on Demand (PFDavg) between 0.1 and 0.01. Typical for basic wellsite high-pressure shutdowns, tank high-level shutdowns, and single-well ESD functions.
  • SIL 2: Risk reduction factor of 100-1,000x. PFDavg between 0.01 and 0.001. Required for facility-wide ESD systems, H2S detection and shutdown in sour gas areas, and fire and gas systems protecting occupied buildings.
  • SIL 3: Risk reduction factor of 1,000-10,000x. PFDavg between 0.001 and 0.0001. Required for high-consequence scenarios like HIPPS (High Integrity Pressure Protection Systems) on high-pressure pipelines and offshore platform ESD systems.

Safety Lifecycle Phases

The IEC 61511 safety lifecycle defines the systematic process for implementing SIS:

  • Hazard and risk assessment: HAZOP (Hazard and Operability Study) or similar method identifies process hazards and determines which require SIS protection.
  • SIL determination: LOPA (Layer of Protection Analysis) or risk graph methods determine the required SIL for each safety function based on consequence severity, exposure frequency, and existing protection layers.
  • SIS design: Selection of sensors, logic solver, and final elements that collectively achieve the required SIL. Includes voting architecture (1oo1, 1oo2, 2oo3), diagnostic coverage, common cause failure analysis, and proof test interval determination.
  • Implementation and commissioning: Programming, factory acceptance testing (FAT), installation, and site acceptance testing (SAT).
  • Operation and maintenance: Periodic proof testing, demand rate tracking, bypass management, and management of change (MOC) procedures.

Common Oilfield SIS Applications

Wellsite Emergency Shutdown (ESD)

Wellsite ESD is the most prevalent SIS application in upstream oil and gas. A typical wellsite ESD system includes:

  • Initiating events: High wellhead pressure, high flowline pressure, fire detection, H2S detection, manual ESD pushbutton
  • Logic solver: A dedicated safety PLC or a safety relay system. For simple wellsite ESD, hardwired safety relay systems (Hima, Pepperl+Fuchs) provide SIL 2 capability at lower cost than a full safety PLC.
  • Final elements: Surface safety valve (SSV) on the wellhead, wing valve, and flowline block valve. Fail-safe (spring-close, pneumatic-open) actuated valves with SIL-rated solenoids.
  • Action: On any initiating event, all ESD valves close simultaneously, isolating the well from downstream facilities. Manual reset required to reopen.

Fire and Gas Detection Systems

Fire and gas (F&G) systems protect personnel and facilities from fire and toxic gas hazards:

  • Fire detection: UV/IR flame detectors for rapid open fire detection. Heat detectors (rate-of-rise and fixed temperature) for enclosed spaces. Linear heat detection cable for cable trays and pipe racks.
  • Gas detection: Catalytic bead sensors for combustible gas (LEL monitoring). Electrochemical sensors for H2S. Point and open-path detectors provide different coverage patterns for facility layouts.
  • Cause and effect matrix: Defines the mapping between detector inputs and output actions. Example: fire detector Zone 1 activates deluge system Zone 1, sounds alarm, and initiates facility ESD.
  • Voting logic: To prevent spurious trips, critical actions may require 2-out-of-3 (2oo3) detector voting. This reduces false alarm rates while maintaining detection reliability.

High Integrity Pressure Protection Systems (HIPPS)

HIPPS protect downstream piping and equipment from overpressure when the upstream source can exceed the downstream design pressure. In oilfield applications, HIPPS are used on high-pressure well flowlines connecting to lower-rated gathering systems. A HIPPS system replaces or supplements pressure relief valves and typically consists of redundant pressure transmitters (2oo3 voting), a certified safety logic solver, and redundant block valves (1oo2 configuration). HIPPS must achieve SIL 3 and require rigorous proof testing schedules.

SIS vs BPCS Separation

A fundamental requirement of IEC 61511 is separation between the SIS and the BPCS. The safety system must operate independently so that a BPCS failure (software bug, communication loss, power failure) does not compromise safety functions. This separation applies to:

  • Sensors: SIS sensors must be independent from BPCS sensors. Sharing sensor signals between systems is allowed only with proper analysis and diagnostic coverage.
  • Logic solver: The safety PLC/relay must be physically separate from the process control PLC. Combined controllers (like Allen-Bradley GuardLogix) are acceptable when the safety and standard programs are logically separated with certified partitioning.
  • Final elements: SIS valves should have independent actuation from BPCS control valves. Sharing final elements requires careful analysis of common cause failures.
  • Power supply: Independent or redundant power supplies for the SIS prevent BPCS power issues from affecting safety functions.

Proof Testing and Maintenance

SIS components must be periodically proof-tested to verify they will function correctly on demand. The proof test interval (PTI) is a critical parameter in the SIL calculation. Longer intervals between tests increase the probability of undetected dangerous failures. Typical proof test intervals for oilfield SIS are:

  • ESD valves: Partial stroke testing quarterly, full stroke testing annually. Partial stroke testing (moving the valve 10-20% of travel) verifies the valve is not stuck without interrupting production.
  • Pressure transmitters: Calibration verification annually. Smart transmitters with HART diagnostics can extend intervals based on diagnostic coverage.
  • Fire and gas detectors: Functional testing semi-annually with calibration gas or test lamps. Sensitivity verification annually.
  • Logic solver: Self-diagnostic PLCs with high diagnostic coverage (greater than 90%) may have proof test intervals of 5-10 years for the logic solver hardware.

Compliance Documentation

Maintaining SIS compliance requires comprehensive documentation including the safety requirements specification (SRS), cause and effect matrices, SIL verification calculations, proof test procedures and records, bypass and override logs, and management of change (MOC) records. Automated SIS management systems track proof test schedules, record test results, and alert maintenance teams when tests are overdue. This documentation is essential for regulatory audits and insurance underwriting.

Frequently Asked Questions

Ready to Get Started?

Our engineers are ready to help with your automation project.