Define
Record the risk basis, required SIL and SIF function.
Product scope · IEC 61508 · IEC 61511
Use FSMS resources across the lifecycle while required SIL, SIF definition, SRS, verification and reports stay connected.
Connected workflow
Record the risk basis, required SIL and SIF function.
Build the Safety Requirements Specification for one SIF.
Check PFDavg or PFH, architecture and systematic capability.
Issue a traceable record of inputs, assumptions and results.
Shared responsibility
SILProof structures the design record. Your organisation remains responsible for engineering decisions and lifecycle execution.
Clause numbers follow IEC 61511-1:2016. Architectural and probability calculations follow IEC 61508-2:2010 and IEC 61508-6:2010.
| Clause | Lifecycle activity | SILProof role | Platform contribution |
|---|---|---|---|
| 5 | Management of functional safety | Supported | FSMS implementation resources provide a lifecycle document map, management manual, procedures, workbooks and audit programme for adoption within your controlled management system. |
| 5.2.6.1 | Functional safety assessment | Connected | SRS and verification records provide structured evidence for assessment. Independence, planning and conclusions remain with the appointed assessor. |
| 6 | Safety lifecycle requirements | Supported | FSMS resources structure lifecycle activities, roles, deliverables and review points around the connected SIF workflow. |
| 7 | SIF design verification | Core | Verifies the quantitative, architectural and systematic gates and records the methods, inputs, assumptions and result. |
| 8 | Hazard and risk assessment inputs | Connected | Risk Analysis records the hazardous event, consequence, initiating frequency and credited protection layers used to establish the required SIL. |
| 9 | Required SIL and allocation | Core | Determines and records required SIL and risk reduction using Risk Graph, LOPA or a company matrix. |
| 10 | SIS safety requirements specification | Core | SRS Builder captures the safe state, trip points, response time, proof testing, reset, bypass and interfaces for each SIF. |
| 11.4 | Hardware fault tolerance | Core | Checks IEC 61511 Table 6 or IEC 61508-2 Route 1H / Route 2H for each subsystem. |
| 11.5 | Selection of devices | Supported | Records systematic capability, certificate or prior-use basis and the source of device failure data alongside the design. |
| 11.9 | SIF probability of failure | Core | Calculates PFDavg or PFH using the selected model, including common cause, proof testing, repair and partial stroke testing. See engine validation. |
| 12 | SIS application programming | Not supported | Application-program design, implementation and software verification remain within the organisation’s controlled engineering process. |
| 13–15 | FAT, installation, commissioning and validation | Not supported | Execution, acceptance and site records remain within the project’s approved procedures and validation plan. |
| 16 | Operation and maintenance | Connected | The SRS and verification report carry proof-test, repair and bypass requirements into operations; scheduling and execution remain in the operating system. |
| 17 | Modification and change control | Connected | SIF revisions and engine versions preserve the engineering trail; formal management of change remains within the organisation’s FSMS. |
| 18 | Decommissioning | Not supported | Planning, authorization and evidence remain within the organisation’s lifecycle and asset-management procedures. |
| 19 | Information and documentation | Supported | SRS and verification reports include document identity, revision, preparer, checker and approver fields for controlled document systems. |
Worked record
Explore a completed SIF from its risk basis through SRS and verification.