Free Tool — SafeGuard Projects
SIL Verification Tool
Verify PFDavg against IEC 61511 SIL requirements for any SIS architecture. Enter your details to unlock — no spam, ever.
1oo1, 1oo2, 2oo2, 2oo3 architectures
PFDavg per IEC 61511
Common cause factor (β)
Diagnostic coverage (DC)
SIL achieved vs. required
Architecture comparison table
Please enter a valid email address.
Skip for now
🔒 No spam. No sales calls unless you ask. Your email is used only to send occasional process safety resources from SafeGuard Projects.
SafeGuard PSM
SafeGuard PSMPSM Consulting
OSHA 1910.119
OSHA 1910.119Free PSM Resource
Free Tool — Email Required

SIL
Verification Tool

Calculate PFDavg for your Safety Instrumented System and verify whether it meets the required Safety Integrity Level per IEC 61511. Supports 1oo1, 1oo2, 2oo2 and 2oo3 architectures with common cause and diagnostic coverage.

IEC 61511 / ISA-84 1oo1 / 1oo2 / 2oo2 / 2oo3 Common Cause (β) Diagnostic Coverage (DC) Architecture Comparison Print Report
IEC 61511 SIL PFDavg Ranges
SIL 10.01 – 0.1
SIL 20.001 – 0.01
SIL 30.0001 – 0.001
SIL 4< 0.0001
PFDavg = λDU × TI/2 (1oo1)simplified
📋
Safety Instrumented Function
Describe the SIF being verified
SIF Description
Required SIL
🏗️
SIS Architecture
Voting configuration for sensors, logic solver, and final elements
Voting Architecture (applies to each subsystem independently)
📉
Failure Rate Parameters
Per IEC 61508 / SIL Tier 2 assessment data
Total Dangerous Failure Rate (λD) /hr
Illustrative values: transmitter 1×10⁻⁶/hr, valve 2×10⁻⁶/hr, logic solver 1×10⁻⁷/hr. Source from SIL Tier 2 assessment or EXIDA/SIS-TECH data.
Diagnostic Coverage (DC) 0–1
DC = fraction of dangerous failures detected by online diagnostics. Drives the split between λDD (detected) and λDU (undetected).
Proof Test Interval (TI) years
Common Cause Factor (β) for redundant architectures
β is the fraction of failures that affect all redundant channels simultaneously. Ignored for 1oo1 — only applies to 1oo2, 2oo2, 2oo3.
Mission Time (TM) years — typically 20 years per IEC 61511
⚖️
Architecture Comparison
PFDavg for all architectures with current failure rate parameters
ArchitecturePFDavgSIL AchievedStatus vs. SIL 2
SIL Verification Result
New SIF
Calculated PFDavg
—
Enter parameters above
⏳
AWAITING INPUT
Enter λD and proof test interval to verify
Required SIL
SIL 2
PFDavg 0.001–0.01
SIL Achieved
—
—
Calculation Breakdown
Enter parameters to see calculation—

Architecture 1oo1
λDU (undetected dangerous) —
Proof Test Interval —
📚 IEC 61511 Reference — Failure Rate Data & PFD Formulas
Illustrative Dangerous Failure Rates (λD)

Order-of-magnitude placeholders for early screening only. Use the manufacturer FMEDA/SIL certificate or a documented database (exida, OREDA, SINTEF PDS) for the specific device.

ComponentλD (/hr)
Pressure transmitter1×10⁻⁶
Temperature transmitter5×10⁻⁷
Level transmitter2×10⁻⁶
Flow transmitter1×10⁻⁶
Pressure switch3×10⁻⁶
Solenoid valve5×10⁻⁷
Control valve (SIL-rated)2×10⁻⁶
Logic solver / PLC (SIL-rated)1×10⁻⁷
Relay (safety rated)1×10⁻⁷
PFDavg Formulas Used (IEC 61508-6)
ArchitectureSimplified PFDavg Formula
1oo1λDU × TI/2
1oo2[(1−β)·λDU·TI]²/3 + β·λDU·TI/2
2oo2λDU × TI
2oo3[(1−β)·λDU·TI]² + β·λDU·TI/2
Where λDU = λD × (1 − DC). TI = proof test interval in years. β = common cause factor. Formulas are simplified per IEC 61508-6 Annex B — for full SIL Tier 3 verification use Markov or fault tree analysis.
The Engineer's Guide

How SIL Verification Actually Works

SIL verification answers one question: will this safety instrumented function (SIF), as designed, actually deliver the risk reduction it was assigned? It comes after SIL determination. A LOPA or risk graph says a function needs SIL 2. Verification proves the hardware, architecture, and test plan get you there.

Under IEC 61511 (ISA 84 in the U.S.), a SIF must pass three separate checks. Passing the math alone is not enough.

  1. Random hardware failures (PFDavg). The calculated average probability of failure on demand must fall inside the target SIL band. This is what the calculator above does.
  2. Architectural constraints (hardware fault tolerance). The function needs enough redundancy for its SIL, regardless of what the math says.
  3. Systematic capability. Every device must be certified (IEC 61508 SC rating) or justified by documented prior use for the target SIL.

SIL bands (low-demand mode)

SILPFDavg rangeRisk reduction factor (RRF)
SIL 1≥ 10⁻² to < 10⁻¹> 10 to ≤ 100
SIL 2≥ 10⁻³ to < 10⁻²> 100 to ≤ 1,000
SIL 3≥ 10⁻⁴ to < 10⁻³> 1,000 to ≤ 10,000
SIL 4≥ 10⁻⁵ to < 10⁻⁴> 10,000 to ≤ 100,000

RRF is simply 1 ÷ PFDavg. Most process-industry SIFs are SIL 1 or SIL 2. SIL 3 is uncommon and expensive, and SIL 4 is essentially never used in process plants. If your LOPA lands on SIL 3 or higher, it's usually worth revisiting the scenario or adding independent protection layers first.

The PFDavg Formulas, Explained

A SIF is a chain of three subsystems: sensors, a logic solver, and final elements (valve, actuator, solenoid). The PFDavg of the function is the sum of the three subsystems, because any one failing defeats the function.

PFDavg(SIF) = PFD(sensors) + PFD(logic solver) + PFD(final elements)

For each subsystem, the simplified formulas from IEC 61508-6 Annex B are:

ArchitectureMeaningSimplified PFDavg
1oo1Single device, no redundancyλDU × TI / 2
1oo2Two devices, either can trip[(1−β) × λDU × TI]² / 3 + β × λDU × TI / 2
2oo2Two devices, both must tripλDU × TI
2oo3Three devices, any two trip[(1−β) × λDU × TI]² + β × λDU × TI / 2
Watch the β term. In redundant architectures, the common cause term (β × λDU × TI / 2) usually dominates the result. Two identical valves from the same batch, on the same air supply, tested by the same technician, do not fail independently. Diversity (different makes or technologies) is often worth more than adding a third device.

Worked Example: High-Pressure Trip on a Reactor Feed

LOPA assigns SIL 2 (RRF > 100) to a high-pressure trip that closes the reactor feed valve. The first design is one pressure transmitter, a SIL 3-certified safety PLC, and one shutdown valve assembly. Everything is proof tested annually (TI = 1 year).

SubsystemDataCalculationPFD
Sensor (1oo1 transmitter)λDU = 3.0×10⁻⁷/hr = 2.63×10⁻³/yr2.63×10⁻³ × 1 / 21.31×10⁻³
Logic solver (SIL 3 PLC)From manufacturer certificate—1.0×10⁻⁴
Final element (1oo1 valve + actuator + solenoid)λDU = 2.0×10⁻⁶/hr = 1.75×10⁻²/yr1.75×10⁻² × 1 / 28.76×10⁻³
SIF total1.02×10⁻² → RRF ≈ 98

Result: SIL 1. Fails the SIL 2 target. Notice where the risk sits: the final element is 86% of the total PFD. That's typical. Valves are almost always the weak link, which is why redundancy or testing on the valve side gives the biggest return.

Fix option A: Redundant valves (1oo2, β = 10%)

(0.9 × 1.75×10⁻²)² / 3 + 0.1 × 1.75×10⁻² / 2 = 8.3×10⁻⁵ + 8.76×10⁻⁴ = 9.59×10⁻⁴

New SIF total: 2.37×10⁻³ → RRF ≈ 420. Passes SIL 2 with margin. Note that 90% of the redundant valve's PFD comes from the common cause term.

Fix option B: Keep one valve, test every 6 months

Halving TI halves every 1oo1 term. The sensor drops to 6.57×10⁻⁴ and the valve to 4.38×10⁻³, for a total of 5.14×10⁻³ → RRF ≈ 195. Passes SIL 2, but you've signed up for twice the testing and twice the bypass time, and the plant has to be able to test the valve online. On paper it's cheaper. In operation it often isn't.

The trap: imperfect proof testing

The formulas above assume each proof test finds 100% of dangerous failures. Real tests don't. A valve stroke test may not catch seat leakage, for example. With proof test coverage (PTC) below 100%, the untested failures accumulate over the whole mission time (MT) of the device:

PFDavg ≈ PTC × λDU × TI / 2 + (1 − PTC) × λDU × MT / 2

Take the original single valve with an 80% effective proof test and a 10-year mission time: valve PFD becomes 2.45×10⁻², nearly three times worse, and the whole SIF is no longer SIL 2-capable even with annual testing. This is the most common reason "verified" SIFs fail an audit. Write proof test procedures that are designed to find each failure mode, and use their realistic coverage in the calculation.

Architectural Constraints (Hardware Fault Tolerance)

Even if the math passes, IEC 61511-1 (2016 edition, clause 11.4) sets a minimum hardware fault tolerance (HFT), the number of device failures the subsystem can tolerate and still perform its function:

SILMinimum HFTPractical meaning
SIL 101oo1 acceptable
SIL 2 (low demand)01oo1 acceptable
SIL 2 (high/continuous demand)1Redundancy required
SIL 31Redundancy required (1oo2, 2oo3)
SIL 42Triple redundancy

The standard allows some adjustments, for example based on prior use evidence or safe failure fraction for devices assessed to IEC 61508. Treat this table as the starting point and confirm against the edition of the standard your project is contracted to.

Where to Get Failure Rate Data

Whatever you use, document the source for every number. An auditor's first question is "where did this λDU come from?"

Common SIL Verification Mistakes

  1. Using λD instead of λDU. This overstates PFD, or, if diagnostics are double-counted, understates it.
  2. Forgetting the solenoid. The final element is valve + actuator + solenoid, and the solenoid is often the worst performer.
  3. Assuming 100% proof test coverage. See the example above.
  4. Ignoring common cause in redundant designs. Leaving β out makes 1oo2 look an order of magnitude better than it is.
  5. Calculating once and never again. When test intervals slip, devices are swapped, or bypasses become routine, the SIL you verified is no longer the SIL you have. Verification belongs in your MOC process.
  6. Skipping the HFT and systematic capability checks. A SIF can pass the PFD math and still not be compliant.

SIL Calculation FAQ

What is the formula for PFDavg?

For a single device (1oo1), PFDavg ≈ λDU × TI / 2, where λDU is the dangerous undetected failure rate per year and TI is the proof test interval in years. For the complete SIF, add the PFDavg of the sensor, logic solver, and final element subsystems.

How do I convert a failure rate per hour to per year?

Multiply by 8,760 (hours in a year). For example, 2.0×10⁻⁶/hr × 8,760 = 1.75×10⁻²/yr.

What's the difference between PFD, PFDavg, and RRF?

PFD is the probability the function fails on demand at a given moment. It rises between proof tests and resets after each one. PFDavg is its average over the test interval, which is the number compared against SIL bands. RRF (risk reduction factor) = 1 / PFDavg.

What's the difference between SIL determination and SIL verification?

SIL determination (or assignment) decides how much risk reduction a function needs, usually through LOPA or a risk graph. SIL verification proves the designed function achieves it. Try our free LOPA calculator for the determination step.

Are simplified formulas acceptable for compliance?

For straightforward 1oo1 and 1oo2 designs with realistic data, simplified IEC 61508-6 equations are widely used. Complex architectures, partial stroke testing credit, staggered testing, or high-demand functions generally need Markov models or fault tree analysis.

This guide is a technical overview for engineers and project teams. It is not a substitute for a SIL verification performed by a qualified functional safety engineer against the edition of IEC 61511 / ISA 84 applicable to your project.

Need a Full SIL Tier 3 Verification?

This tool provides a Tier 1/2 PFDavg estimate. Formal SIL verification for IEC 61511 compliance requires a Tier 3 assessment — Markov analysis, fault tree, or FMEDA — performed by a qualified functional safety engineer. Our team brings decades of hands-on SIS experience on chemical, refinery, and gas-to-liquids projects, from FEED through commissioning and startup.

Talk to Our SIL Team →