Functional Safety · worked example, computed with First Out AI

Fired heater fuel trip: choosing scanner voting for safety and uptime

One flame scanner is cheap but not enough. Two scanners voted one out of two are safe but trip the heater on either scanner's fault. The calculation shows which voting meets the required risk reduction and keeps the heater running.

Target
SIL 2, low demand
Method
LOPA, verification of four votings
Final element
Double block valves, 1oo2
Chosen
2oo3 scanners, PFDavg 2.3 × 10⁻³

Scenario

If the flame in a fired heater goes out while fuel gas keeps flowing, gas accumulates in the hot firebox and can ignite explosively. Flame scanners detect loss of flame and the safety function closes two fuel gas block valves in series.

Scanners are a frequent source of spurious trips on fired heaters. Each unnecessary trip costs a restart, thermal cycling of the tubes and lost production.

SIL determination by LOPA

StepItemValueNote
Initiating eventFlame-out with fuel gas still flowing into a hot firebox0.5 /yrgeneric value for flame instability events; confirm with heater history
Conditional modifierProbability a person is near the heater0.05
Mitigated event frequencywithout the SIF0.025 /yr
Tolerable frequencycompany criterion (illustrative)1.0 × 10⁻⁴ /yr
Required risk reductionPFDavg ≤ 4.0 × 10⁻³RRF 250SIL 2

Required risk reduction 250: SIL 2, PFDavg ≤ 4.0 × 10⁻³.

Architecture and input data

Scanner safe failure rate set high on purpose: it drives the spurious trip comparison.

Flame scannersScanner 1Scanner 2Scanner 32oo3, HFT 1Logic solverLogic 1oo1, HFT 1Fuel gas block valvesValve 1Valve 21oo2, HFT 1
Two block valves in series act as 1oo2: either valve closing stops the fuel.
SubsystemVotingλDU /hλDD /hλS /hβProof testCoverageRenewal / overhaulPartial strokeTypeSCSFF
Flame scanners2oo34.0 × 10⁻⁷1.5 × 10⁻⁶3.0 × 10⁻⁶5%1 yr90%20 yr–BSC 391.8%
Logic solver1oo1, internal HFT 11.0 × 10⁻⁹5.0 × 10⁻⁷2.0 × 10⁻⁷–10 yr100%20 yr–BSC 399.9%
Fuel gas block valves1oo21.4 × 10⁻⁶05.0 × 10⁻⁷10%1 yr85%15 yr–ASC 326.3%

Function mission time (averaging horizon): 20 yr. Renewal / overhaul is when failures that no test reveals are cleared for each subsystem.

Four votings compared

Same valves and logic solver in every case; only the scanner voting changes.

Scanner votingFunction PFDavgScanner HFTBandScanner spurious trips /hScanner MTTFSAgainst required PFD
Scanners 1oo17.1 × 10⁻³0SIL 24.5 × 10⁻⁶25.4 yrShort
Scanners 1oo22.3 × 10⁻³1SIL 28.8 × 10⁻⁶13.0 yrMeets
Scanners 2oo32.3 × 10⁻³1SIL 22.3 × 10⁻⁷505.4 yrMeets
Scanners 2oo20.0120SIL 12.3 × 10⁻⁷506.7 yrShort
SubsystemPFDavgSharePFDavg, perfect test (IEC 61508-6)HFT achieved / requiredRoute 1H limitSpurious trips /h
Flame scanners3.4 × 10⁻⁴14%1.0 × 10⁻⁴1 / 0SIL 32.3 × 10⁻⁷
Logic solver4.8 × 10⁻⁵2%4.8 × 10⁻⁵1 / 0SIL 47.0 × 10⁻⁷
Fuel gas block valves2.0 × 10⁻³84%6.6 × 10⁻⁴1 / 0SIL 29.5 × 10⁻⁷
RequirementResultSupportsVerdict
Probability of failure on demandPFDavg 2.3 × 10⁻³SIL 2Pass
Hardware fault tolerance (IEC 61511)minimum HFT per subsystemSIL 3Pass
Systematic capabilitylowest element SC 3SIL 3Pass
Required PFDavg (from LOPA)≤ 4.0 × 10⁻³PFDavg 2.3 × 10⁻³Met
Functiontarget SIL 2SIL 2Meets target
Spurious trip rate1.9 × 10⁻⁶ /hMTTFS 60.9 yrReported
PFD over the mission time, 2oo3 scanners
  • PFD(t) of the function
SIL 2SIL 3SIL 41 × 10⁻⁶1 × 10⁻⁵1 × 10⁻⁴1 × 10⁻³0.0105101520Years in servicePFD (log scale)PFDavg 2.3 × 10⁻³Required 4.0 × 10⁻³

Hover or tap the chart, or focus it and use the arrow keys, to read the value at any time.

Chart data
Years in servicePFD(t) of the function
07.35 × 10⁻⁶
12.32 × 10⁻⁴
24.63 × 10⁻⁴
32.07 × 10⁻³
42.35 × 10⁻³
51.14 × 10⁻³
61.40 × 10⁻³
73.17 × 10⁻³
83.47 × 10⁻³
92.15 × 10⁻³
102.34 × 10⁻³
114.27 × 10⁻³
124.59 × 10⁻³
133.16 × 10⁻³
143.46 × 10⁻³
155.54 × 10⁻³
162.03 × 10⁻³
172.31 × 10⁻³
181.08 × 10⁻³
191.34 × 10⁻³

Findings

A single scanner (7.1 × 10⁻³) and 2oo2 (0.012) fall short of the required 4.0 × 10⁻³: their scanner failures add directly to the valves' share. 1oo2 and 2oo3 both meet it, because the fuel valves then dominate the PFDavg.

Between those two, the difference is uptime. 1oo2 trips the heater on any one scanner's safe failure, about every 13 years from the scanners alone; on a heater with several burners and scanners, that becomes a trip every year or two. 2oo3 keeps a fault tolerance of one and pushes the scanners' spurious trip interval to about 505 years.

Recommendation

Use three scanners voted 2oo3. With one scanner forced to the tripped state for maintenance, the voting becomes 1oo2 and stays safe; bypassed as healthy, it becomes 2oo2 with no fault tolerance. The procedure should require the tripped state, or limit the bypass time.

Worked example with an illustrative design and data, chosen to show the method; it is not a client project. Failure rates are typical of published device certificates and are not taken from any reliability database. Computed with the First Out AI engine v0.3.0 on 28.10.2026. First Out AI supports engineering judgement and does not replace it: results must be checked by a competent functional safety engineer, and First Out AI is not certified software. This is not engineering advice for a specific plant.