LOPA, SRS and SIL verification, connected in one record
Cloud-based software for safety instrumented functions and independent protection layers, whether you deliver studies for clients or own the facility: run LOPA studies, write the SRS, verify SIL with transparent calculations, and keep the records current through modifications.
Free demo workspace, set up for you
Reviewed and approved by a person, not a bot
No payment details needed
Prefer to look before you try? Ask for the SIFintegrity demo videos first. Once we’ve approved your request, we’ll email you the link.
Thank you. We’ll reply by email within 2 working days.
See it in action
From LOPA scenario to as-built SIF, in one record
Follow one SIF from the LOPA study that designates it, through the registers, SRS, verification and approval, to as-built: one connected record, with a basis behind every value.
Built for the way assessments and verifications are really done
LOPA studies
Build layer of protection analysis scenarios with initiating events, enabling conditions and IPL credits that trace back to their justification.
SIL verification
Calculate PFD or PFH, check architectural constraints and hardware fault tolerance, and see exactly how each number was reached.
Register of record
Keep SIFs and IPLs, whether derived in the tool or assessed elsewhere, in one register that stays current through modifications.
Mandatory basis for every value
Failure rates, proof-test intervals and credits cannot be entered without a stated source, so assumptions never go missing.
Your data, not ours
Reference lists of typical values and a reliability library built from your own and vendor data. No generic failure data is assumed.
Cloud-based, nothing to install
SIFintegrity runs in your web browser, hosted and maintained by us. Each facility has its own separate deployment, so client data never mixes.
The feature set
From LOPA scenario to verified SIF, in one connected record
The same record serves a consultancy delivering a study for a client and an operator keeping its protection layers current for years. Here is what each part does.
LOPA studies
Plan, record and issue layer of protection analysis studies against your own risk criteria.
Several initiating events per consequence, with mitigated event likelihood against the target
Risk criteria editor: up to four consequence categories, three to eight levels each, with criteria import
Reference lists of typical initiating event frequencies and layer values, exchanged by CSV
Each candidate SIF carries the risk reduction its scenarios need
Safety requirements specification
Define each SIF once and issue the SRS from the data, so the document never drifts from the record.
SIF structure: subsystems, voting and devices, with an as-built view
SRS definition per SIF, issued as documents and datasheets
Each SIF linked to the LOPA scenarios that set its requirement
Equipment register of the devices used across SIFs
SIL verification
Transparent calculations you can follow from input to result.
PFDavg and PFH to IEC 61508-6
Architectural constraints by Route 1H or Route 2H
Systematic capability
Maximum proof-test interval that still meets the target
Reliability library built from your own and vendor data, with a verification datasheet per SIF
Registers
Every protection layer in one place, wherever it was assessed.
SIF and integrity level register
Protection layer and consequence registers across all studies
SIFs and protection layers assessed outside the tool, recorded with their source
Verification results reported by others, recorded as reported
Register exports in CSV and Excel
Data import and projects
Bring existing records in, and keep project work separate until it is ready.
Bulk CSV import of layers, verification results, equipment, SIF structures, events and consequences, SRS data and reliability data
Import of archive files from other LOPA software
LOPA worksheet packages exported and imported between deployments
Projects for capital work and management of change, released to the live record when complete
Re-importable exports of the current record
Review, approval and integrity
Built so the record stands up to later scrutiny.
A mandatory basis for every claimed value
Consistency checks that flag; engineers conclude
Study review, approval, revisions and revalidation
Reports in PDF and Word, with issued copies fingerprinted and retained
Administrator, editor and read-only roles, with access set per person
Every action written to an audit record
Packages
Packages, from a single consultant to a whole facility
Every package runs on the same SIFintegrity, so you can start small and move up without moving your data. Prices are indicative; ask us for a quote for your team.
What each SIFintegrity package includes
Feature
Solo LOPAOne consultant running LOPA studies
Solo SRS and SIL verificationOne consultant writing SRS and verifying SIL
ProfessionalSmall and medium consultancies
ConsultancyLarger engineering consultancies
Owner-OperatorHazard owners managing their own facility
It keeps to the part of the lifecycle where a traceable record matters most, and leaves the rest to the tools and people already doing it well.
Host HAZOP or other PHA studies. SIFintegrity starts where your HAZOP hands scenarios to LOPA.
Schedule proof tests or send reminders. It records the requirement; your maintenance system plans the work.
Decide that a design is safe. It shows the calculation and the gaps; a competent engineer concludes.
Who it’s for
Made by functional safety engineers, for functional safety engineers
Functional safety consultancies delivering LOPA, SRS and SIL verification for clients
Owner-operators keeping SIF and protection layer records current through operation
Process safety and SIS engineers, and LOPA facilitators
Our design principle
SIFintegrity documents human engineering judgement and never produces it. Checks flag; engineers conclude. Every claimed value carries a mandatory basis, because the output is evidence that regulators and investigators will read.
See SIFintegrity with your own examples
Request a free demo workspace. We review every request by hand and reply by email within 2 working days.