Functional safety
IEC 61511
The process-sector standard for safety instrumented systems — from hazard and risk assessment to proof testing and modification.
Functional safety — Safety instrumented systems for the process industry sector
- Category
- Functional safety
- Scope
- International
- Edition / refs
- IEC 61511-1:2016 + AMD1:2017, Parts 1–3
MSA output
- HAZOP worksheets & LOPA calculations
- SIF register & SIL verification
- Cause & effect matrix
- Proof test records & IEC 61511 lifecycle
What is IEC 61511?
IEC 61511 is the process-sector implementation of IEC 61508. It sets requirements for the specification, design, installation, operation and maintenance of safety instrumented systems (SIS), so that each safety instrumented function (SIF) achieves and maintains its required SIL.
Part 1 contains the requirements, Part 2 gives guidance on applying Part 1, and Part 3 gives guidance on determining the required SIL using methods such as risk graphs and layer of protection analysis (LOPA). In the United States, ANSI/ISA-61511 adopts the same requirements.
Who it applies to
- Operators of chemical, oil and gas, pharmaceutical and energy process plants
- COMAH and other major-hazard sites
- SIS integrators and engineering contractors
- Instrument and control engineers responsible for SIS design and proof testing
Key requirements
- 01
Hazard and risk assessment
Identify hazards and determine the risk reduction needed — typically HAZOP followed by LOPA or another SIL determination method.
- 02
Allocation to protection layers
Allocate safety functions to protection layers and set the SIL target for each SIF.
- 03
Safety requirements specification
Specify each SIF: safe state, trip points, response time, proof test interval, bypass and reset requirements.
- 04
Design and SIL verification
Verify PFDavg or PFH, hardware fault tolerance and systematic capability, accounting for proof test interval and coverage.
- 05
FAT, commissioning and validation
Confirm that the SIS as installed meets the safety requirements specification before hazards are introduced.
- 06
Operation, maintenance and change
Proof testing, bypass management, records, management of change and functional safety assessments at defined stages.
Summary for orientation only. Always refer to the current official text of IEC 61511 and any applicable legislation.
MSA for IEC 61511
What MSA generates
Evidence produced from your engineering inputs, traceable end to end and exported to Word, PDF or Excel.
HAZOP worksheets & LOPA calculations
Hazard scenarios carried from HAZOP into LOPA to derive the required risk reduction.
SIF register & SIL verification
Every SIF with its SIL target, verification and supporting assumptions in one register.
Cause & effect matrix
Causes, trips and final element actions documented and linked to the SIF register.
Proof test records & IEC 61511 lifecycle
Proof test procedures and records, organised by life-cycle phase.
Frequently asked questions
Is IEC 61511 a legal requirement?
Not by name. But regulators — for example HSE in Great Britain — regard IEC 61511 as relevant good practice for safety instrumented systems, and operators of major-hazard sites are expected to demonstrate an equivalent standard of risk control.
What is the difference between a SIS, a SIF and a SIL?
The SIS is the system of sensors, logic solvers and final elements. A SIF is one specific function performed by the SIS to reach a defined safe state. The SIL is the integrity target set for that SIF.
How often must SIFs be proof tested?
At the interval specified in the safety requirements specification and assumed in the SIL verification. If the actual interval or coverage differs, the verification must be revisited.
How does MSA connect HAZOP to SIL?
HAZOP scenarios are carried into LOPA. Where a gap remains, a SIF is created in the register with its SIL target, and its verification and proof test records stay attached to that same SIF.
Generate IEC 61511 evidence from your own data
See how MSA turns your requirements, drawings and process data into certification-ready documents — fully offline.