SIS Final Element Reliability: Why Valves Dominate

Share:
DCS & Automation
SIS Final Element Reliability: Why Valves Often Dominate SIF Performance

Final element reliability decides more of a SIF's PFDavg than most engineers expect, and the valve assembly is usually where that number gets spent.

This guide breaks down why the mechanical parts of a safety loop fail more than the sensors or the logic solver, and shows the actual math behind it.

Subsystem PFD Breakdown PFD Contribution Calculator Partial Stroke Testing

Final element reliability is the weakest point in most safety instrumented functions, because the valve, actuator, and solenoid that make up the final element wear, stick, and corrode in ways electronics rarely do.

Final Element Reliability: The Weak Link in Most Safety Loops

Every SIF has three subsystems working together: a sensor that detects the dangerous condition, a logic solver that decides what to do, and a final element that actually acts, usually an emergency shutdown valve.

Of the three, the final element is almost always the one dragging down the loop's overall PFDavg. It is a moving mechanical assembly sitting in a harsh process, not a sealed electronic box.

Final element reliability

This gap between subsystems is one reason SIF design spends so much attention on the final element even though it looks like the simplest part on a P&ID.

Advertisement
Advertisement

What Actually Sits Inside a Final Element

A final element is not one part. It is a chain of three components, and any one of them failing dangerous-undetected can take down the whole SIF.

Shutoff Valve

Common TypesBall, Gate
Fails FromStiction, Corrosion
Proof TestAnnual, Full Stroke

Actuator

Common TypesPneumatic, Spring-Return
Fails FromSeal Leaks, Torque Mismatch
Proof TestAnnual, Full Stroke

Solenoid Valve

Common TypesDirect-Acting, Pilot
Fails FromCoil Burnout, Plugged Orifice
Proof TestAnnual, Full Stroke

Any one of these three can hold the whole final element back, which is why solenoid valve working principle and actuator sizing both matter just as much as the shutoff valve itself.

Why the Valve Assembly Usually Fails First

Sensors are mostly solid state now, with continuous self-diagnostics running in the background. Logic solvers, being SIL-rated PLCs, run watchdog checks constantly and catch most of their own faults, the same self-checking concept covered in our guide to safe failure fraction.

A final element has none of that built in by default. It sits exposed to process fluid, temperature swings, and vibration, and nothing tells the control room a valve has started sticking until it fails to move on demand.

SubsystemTypical Dangerous Failure BehaviourUsual Proof Test Interval
SensorLow, mostly self-diagnosed1–3 years
Logic SolverVery low, continuous self-testRarely needed separately
Final ElementHighest, mechanical wear and stiction1 year, tied to turnaround

The longer proof-test interval matters just as much as the higher failure rate. A dangerous undetected fault in a valve can sit hidden for months before the next scheduled test finds it.

This gap is explained in detail in this Valve Magazine look at functional safety in final elements.

Final Element (78%)
Sensor (15%)
Logic Solver (7%)

A typical PFDavg budget split across the three SIF subsystems

Advertisement
Advertisement

See It in Numbers: PFD Contribution by Subsystem

Enter a dangerous undetected failure rate for each subsystem, in units of 10-6 per hour, along with the proof test interval, to see how much of the loop's total PFDavg each subsystem is really responsible for.

🔧
PFD Contribution Calculator
PFDavg = (λDU × TI) ÷ 2, per subsystem
PFDavg = (λDU × TI) ÷ 2
-
-

Running the Default Numbers by Hand

Take a loop with a sensor λDU of 0.3, a logic solver λDU of 0.05, and a final element λDU of 4.0, all ×10-6 per hour, tested once a year.

TI = 8760 hours (1 year)

PFD(sensor) = (0.3 × 10-6 × 8760) ÷ 2 = 0.001314
PFD(logic solver) = (0.05 × 10-6 × 8760) ÷ 2 = 0.000219
PFD(final element) = (4.0 × 10-6 × 8760) ÷ 2 = 0.017520

Total PFDavg = 0.001314 + 0.000219 + 0.017520 = 0.019053
Final element share = 0.017520 ÷ 0.019053 = 91.95%

Even with a fairly ordinary failure rate, the final element alone accounts for over 90% of this loop's total PFDavg, purely because it carries the highest λDU and the longest gap between tests.

This same PFDavg formula is the basis of the calculator in our SIL verification vs validation guide.

Advertisement
Advertisement

Partial Stroke Testing: Catching Trouble Between Proof Tests

A full proof test moves the valve all the way and confirms it works, but that only happens once a year in most plants. A lot can go wrong with a valve in twelve months.

Partial stroke testing, or PST, moves the valve a small amount, usually 10 to 20 percent of its travel, without actually shutting the process down. It catches stiction and early wear long before the next full proof test.

Done well, PST raises the diagnostic coverage of the final element, which lowers its effective λDU and improves the overall PFDavg, a benefit covered in detail in this Emerson explanation of partial stroke test diagnostic coverage.

PST is not a replacement for the full proof test. It narrows the exposure window, but a full stroke is still the only way to confirm the valve reaches its final safety position, a distinction also relevant to SIL compliance audits.

Practical Ways to Raise Final Element Reliability

1

Match actuator torque to valve requirements

Undersized actuators are a common root cause of final elements failing to reach full closure on demand.

2

Add partial stroke testing where the process allows it

Regular partial strokes catch stiction and wear months before the annual proof test would.

3

Choose valve materials rated for the actual process fluid

Corrosion and erosion from a mismatched material are a frequent cause of stem and seat degradation.

4

Shorten the proof test interval for high-λDU elements

A tighter test interval directly lowers PFDavg, the same lever used in SIL verification calculations.

5

Track failures in a plant-specific database

Generic manufacturer data is a starting point, but real field history gives a far more accurate λDU over time, tying back into the wider SIS safety lifecycle.

Do's and Don'ts for Final Element Reliability

✓ Do

  • Size the actuator to the valve's actual required torque or thrust, with margin
  • Run partial stroke tests between full proof tests wherever feasible
  • Match valve trim and seat material to the real process fluid
  • Log every final element failure, even minor ones, for future λDU estimates

✗ Don't

  • Assume a valve that passed commissioning will behave the same after years in service
  • Treat partial stroke testing as a substitute for the full proof test
  • Use generic failure rate data when plant-specific history is available
  • Ignore solenoid valve health, since it can strand an otherwise healthy actuator

Worth Reading if You Want to Go Deeper

DOC
Accurate Failure Metrics for Mechanical Instruments in Safety Applications
exida.com
DOC
The Next Step in Functional Safety
valvemagazine.com
Advertisement
Advertisement

Common Questions on Final Element Reliability

Why is final element reliability usually the weakest part of a SIF?
Because the final element is a moving mechanical assembly exposed to process conditions, while sensors and logic solvers are largely solid-state with continuous self-diagnostics. Mechanical wear, stiction, and corrosion push its failure rate and PFD contribution higher than the other two subsystems.
What parts make up a final element?
Typically a shutoff valve, an actuator that moves it, and a solenoid valve that controls air to the actuator. Any one of the three can cause the final element to fail on demand.
What is partial stroke testing?
A test that moves a valve a small percentage of its travel, without a full process shutdown, to check for stiction or wear between full proof tests. It improves diagnostic coverage but does not replace the full proof test.
How is the PFD contribution of a final element calculated?
Using PFDavg = (λDU × TI) ÷ 2 for each subsystem, then comparing the final element's PFD against the sensor's and logic solver's to see its share of the total loop PFDavg.
Does a shorter proof test interval improve final element reliability?
Yes. Since PFDavg scales directly with the proof test interval, testing more often reduces the time a dangerous undetected fault can sit hidden, which lowers the calculated PFDavg.
Can better failure rate data change the final element's PFD contribution?
Yes. Plant-specific failure history is usually more accurate than generic manufacturer data, and using it can shift the calculated λDU, and therefore the PFD contribution, in either direction.

External References

What We Learn Today

  • Final element reliability usually dominates a SIF's PFDavg because the valve, actuator, and solenoid are mechanical and lack continuous self-diagnostics.
  • PFDavg for each subsystem is calculated as (λDU × TI) ÷ 2, and the final element's share can exceed 90% in a typical loop.
  • Partial stroke testing catches stiction and wear between full proof tests, raising diagnostic coverage without replacing the annual test.
  • Actuator sizing, valve material selection, and proof test interval are the levers engineers actually control to improve final element reliability.
"A safety system is only as reliable as the part that has to physically move when it matters most."

Leave a Reply

Your email address will not be published. Required fields are marked *