SIL Calculation Reports
SIL Calculation Reports provide the documented evidence produced after Safety Integrity Level (SIL) calculations have been completed for a Safety Instrumented Function (SIF). These reports allow engineers to review Probability of Failure on Demand (PFD), Risk Reduction Factor (RRF), proof test assumptions, architectural constraints and verification results, ensuring the design satisfies functional safety requirements and supporting compliance with IEC 61511.
Within the Instrumented Systems module of SLM, SIL Calculation Reports bring together the results of complex calculations into clear, easy-to-review reports that can be analysed, shared and printed. Whether reviewing a single Safety Instrumented Function or documenting an entire project, these reports provide the traceability needed throughout the functional safety lifecycle.
This guide explains the different report types available within SLM, how they should be interpreted, and how they support engineering decisions during design, verification and ongoing operation of Safety Instrumented Systems.
What Are SIL Calculation Reports?
SIL Calculation Reports summarise the results generated after completing SIL calculations for a Safety Instrumented Function (SIF). Rather than reviewing numerous individual calculation parameters, engineers can analyse consolidated reports showing whether a SIF satisfies its required Safety Integrity Level and achieves the required level of risk reduction.
These reports are particularly valuable during design reviews, functional safety assessments, management of change activities and project documentation because they provide a consistent record of how each Safety Instrumented Function has been evaluated.
Within SLM, SIL Calculation Reports automatically present the results generated by the calculation engine, allowing engineers to:
- Review achieved Probability of Failure on Demand (PFD).
- Compare achieved Risk Reduction Factor (RRF) against the target.
- Evaluate failure contributions.
- Analyse proof test assumptions.
- Review verification information.
- Create printable engineering documentation.
These reports become part of the documented evidence supporting the safety lifecycle described in IEC 61511 and should be retained alongside other functional safety records.
For an overview of how SIL calculations are performed before reports are generated, see our Instrumented Systems Overview.
Understanding RRF and PFD Reports
Two of the most important outputs generated by SIL calculations are the Risk Reduction Factor (RRF) report and the Probability of Failure on Demand (PFD) report. Together they demonstrate whether the Safety Instrumented Function provides the level of protection required by the process hazard analysis.
The RRF report compares the achieved risk reduction against the target risk reduction defined during hazard analysis or Layer of Protection Analysis (LOPA). If the achieved value exceeds the target, the design satisfies the required level of protection. If not, engineers may need to modify the architecture, proof test intervals or component selection.
The PFD report focuses on the calculated probability that the Safety Instrumented Function will fail to perform when demanded. Lower PFD values indicate a more reliable safety function.
SLM presents these results for multiple failure-rate sources, allowing engineers to compare:
- Prior Use failure data.
- Design Basis failure data.
- Custom failure-rate datasets where applicable.
The reports also display how failures are distributed across:
- Input devices.
- Logic solvers.
- Output elements.
- UPS equipment where energised-to-trip architectures are used.
Understanding these contributions helps engineers identify where improvements will have the greatest impact on overall Safety Instrumented Function performance.
For more information about the calculations behind these reports, see Instrumented Systems – SIL Calculations.
Using IO Sensitivity Reports to Optimise Proof Testing
IO Sensitivity Reports help engineers understand how changing proof test intervals affects the achieved Risk Reduction Factor of a Safety Instrumented Function.
Rather than evaluating a single proof test interval, SLM allows users to generate multiple scenarios by varying both input and output proof test frequencies. The resulting report can be viewed as either a colour-coded matrix or an engineering graph.
This allows engineers to answer practical questions such as:
- How much can proof testing be delayed before the target RRF is no longer achieved?
- Which proof test interval provides the greatest improvement?
- Are current maintenance schedules sufficient to satisfy SIL requirements?
- Can proof test intervals be safely optimised without compromising risk reduction?
The colour-coded matrix provides an immediate visual indication of acceptable operating ranges:
- Green cells indicate combinations that achieve or exceed the target Risk Reduction Factor.
- Red cells indicate combinations that fall below the required safety target.
The accompanying graph presents the same information as performance curves, allowing engineers to compare different proof test strategies while understanding how maintenance intervals influence long-term Safety Instrumented Function performance.
These reports are especially valuable during maintenance planning, proof test optimisation and Management of Change activities.
Interpreting the SIL Verification Report
The SIL Verification Report consolidates the information required to demonstrate whether a Safety Instrumented Function achieves its specified safety performance. Instead of reviewing calculation inputs and results across several separate views, engineers can use this report to examine the complete verification basis in one place.
Within SLM, the report is accessed from the relevant SIF through the SIL Verification tab. The information displayed can include:
- The functional requirements and target SIL for the SIF.
- The governing calculation result and selected failure-rate source.
- The total calculated PFD and achieved RRF.
- Architectural constraint results.
- Mean Time to Fail Spurious calculations.
- The SIF architecture and component arrangement.
- Failure contributions from inputs, logic solvers and outputs.
- Proof test intervals and diagnostic assumptions.
- Voting arrangements and common-cause failure parameters.
- Component failure-rate data and repair assumptions.
The governing result source is particularly important. SLM may calculate results using several available failure-rate datasets, but the governing source identifies the result formally used to assess the SIF against its target. Reviewers should confirm that the selected source is appropriate, approved and consistent with the project’s verification methodology.
The report should also be checked against the documented requirements for the function. The target SIL, required response, operating mode, proof test interval and other design assumptions should align with the approved Safety Requirements Specification (SRS).
A successful calculation does not by itself confirm that every lifecycle requirement has been met. Engineers should also verify that the architecture, equipment selection, testing assumptions and operating constraints accurately represent the installed or proposed design.
For additional context on how a SIF performs within a Safety Instrumented System, see the Safety Instrumented Function guide.
Printing and Exporting SIL Calculation Reports
SIL Calculation Reports often need to be circulated beyond the engineer performing the calculation. They may be reviewed by project teams, independent functional safety assessors, operations personnel, maintenance teams, clients or regulatory stakeholders.
SLM provides two principal ways to produce a printable SIL Verification Report.
Printing an individual SIF report
When reviewing a specific Safety Instrumented Function, the user can open its SIL Verification view and select the print option. The report can then be printed directly or saved as a PDF for controlled distribution and retention.
This method is useful when:
- One SIF is being reviewed during a design meeting.
- A calculation has recently been revised.
- Evidence is required for a specific action or approval.
- A report must be attached to an individual engineering record.
Generating reports for multiple SIFs
For broader reporting requirements, users can navigate to the reporting area and select the SIL Verification Report. The report can then be filtered by site and unit before selecting one or more Safety Instrumented Functions.
After the report is generated, each selected SIF is presented as a separate report section. This allows teams to produce a coordinated verification package covering an entire unit, project or review scope.
Before issuing a report, confirm that:
- The correct site, unit and SIFs have been selected.
- The latest approved calculation results are displayed.
- The governing failure-rate source is correct.
- The report includes the required architecture and test information.
- Any assumptions or outstanding actions are clearly documented.
- The file is stored using the organisation’s document-control process.
Generated reports should be assigned a revision, review status and approval record where required by the project’s functional safety management procedures. This prevents superseded results from being mistaken for the current verification basis.
The SLM Instrumented Systems module provides a central environment for maintaining SIF data, calculation results and verification documentation throughout the safety lifecycle.
Best Practices for Reviewing SIL Calculation Results
A SIL calculation report should be treated as an engineering verification record, not simply as confirmation that the software has produced a passing result. Effective review requires engineers to examine the calculation basis, assumptions and design representation alongside the final PFD and RRF values.
Confirm the target and operating mode
Verify that the report uses the correct target SIL or target RRF and that the calculation mode reflects how the function operates. Low-demand and continuous or high-demand functions require different performance measures and should not be evaluated using an inappropriate calculation basis.
Review the governing result source
Check which failure-rate dataset governs the reported result. Prior Use, Design Basis and approved custom data may produce different outcomes. The selected source should be justified, traceable and consistent with the organisation’s approved engineering practices.
Check the complete SIF architecture
Confirm that every relevant input, logic solver, output element, voting arrangement and supporting component is represented. Missing or incorrectly configured equipment can produce a result that does not accurately describe the real design.
Examine failure contributions
A SIF may technically achieve its target while remaining heavily dependent on one part of the architecture. Reviewing failure contributions helps identify whether inputs, the logic solver or final elements dominate the overall PFD.
This information can guide improvements such as:
- Using more reliable equipment.
- Adding redundancy where justified.
- Improving diagnostics.
- Changing proof test intervals.
- Reviewing common-cause assumptions.
- Improving final-element testing.
Validate proof test assumptions
Proof test intervals and proof test coverage can significantly affect calculated performance. Confirm that the values used in the report are achievable through the planned maintenance programme and supported by appropriate test procedures.
IO Sensitivity Reports can help determine whether a proposed test interval remains within the acceptable RRF range. However, any extension to a proof test interval should be assessed through the organisation’s engineering and Management of Change processes.
Review margins rather than relying on a narrow pass
A result that only narrowly exceeds the target may be vulnerable to future changes in equipment data, test intervals or operating assumptions. Where practical, designs should provide a reasonable engineering margin instead of relying on an exact threshold.
Document the review and approval
The final report should identify who performed the calculation, who independently reviewed it and which revision was approved. Outstanding assumptions, recommendations and actions should be recorded before the verification is accepted.
These review practices help support the verification and documentation expectations associated with IEC 61511 compliance while creating a clear audit trail for future modifications, assessments and operational reviews.
Common Challenges When Using SIL Calculation Reports
SIL Calculation Reports provide valuable engineering evidence, but they should always be interpreted within the wider context of the Safety Instrumented System. A report can only be as accurate as the data, assumptions and configuration used to generate it.
One of the most common mistakes is focusing solely on whether the achieved Risk Reduction Factor (RRF) or Probability of Failure on Demand (PFD) satisfies the target. While meeting the target is important, engineers should also review the assumptions behind the calculation to ensure they accurately represent the installed system.
Areas that should always be checked include:
- Failure-rate data is current and from an approved source.
- Proof test intervals reflect the actual maintenance strategy.
- Diagnostic coverage values are realistic.
- Repair times represent achievable maintenance performance.
- Voting architectures have been configured correctly.
- All field devices, logic solvers and final elements have been included.
- Common cause failures have been appropriately considered.
Reports should also be reviewed whenever changes are made to the Safety Instrumented Function. Modifying an instrument, adjusting proof test intervals or replacing equipment may alter the calculated SIL performance and require the report to be regenerated.
Using the latest approved report throughout design reviews, maintenance planning and Management of Change activities helps maintain confidence that the Safety Instrumented Function continues to satisfy its intended performance throughout its operational life.
Using SIL Calculation Reports Throughout the Safety Lifecycle
SIL Calculation Reports are not simply design documents. They provide evidence that supports multiple stages of the functional safety lifecycle, from initial design through to long-term operation and maintenance.
During the design phase, reports demonstrate that the proposed Safety Instrumented Function has sufficient risk reduction capability to meet the required target. During project execution they support design reviews, hazard studies and verification activities.
Once the system has been commissioned, the same reports continue to provide value by helping engineers evaluate modifications, assess proof test strategies and confirm that operational changes have not adversely affected SIL performance.
Typical lifecycle activities supported by SIL Calculation Reports include:
- Safety Instrumented System design verification.
- Functional Safety Assessments (FSAs).
- Project approval and design reviews.
- Management of Change (MoC).
- Proof test optimisation.
- Periodic engineering reviews.
- Regulatory and client audits.
- Lifecycle documentation and record retention.
Because SLM stores both calculation inputs and generated reports together, organisations benefit from improved traceability throughout the life of the asset. Engineers can quickly regenerate reports after design changes, compare revisions and maintain a complete history of how each Safety Instrumented Function has evolved.
Combining SIL calculations, verification reporting and lifecycle documentation within a single engineering platform reduces manual effort while helping organisations demonstrate compliance with recognised functional safety standards. The IEC 61511-1 functional safety standard defines requirements for the specification, design, installation, operation and maintenance of Safety Instrumented Systems used in the process industry.
Learn More About SIL Calculation Reports
SIL Calculation Reports provide the documented evidence needed to verify that Safety Instrumented Functions achieve their required level of risk reduction. By presenting PFD, RRF, architectural constraints, proof test assumptions and verification results in a structured format, they enable engineers to make informed decisions throughout the safety lifecycle.
Within SLM, these reports support engineering reviews, functional safety assessments, project approvals and ongoing operational management by ensuring that calculation results remain traceable, repeatable and easy to communicate across multidisciplinary teams.
Whether reviewing a single Safety Instrumented Function or generating reports for an entire facility, maintaining accurate SIL Calculation Reports helps organisations improve documentation quality, simplify compliance activities and build confidence in the integrity of their Safety Instrumented Systems.
To learn more about the Instrumented Systems capabilities available within SLM, explore the related guides throughout the Safety Systems documentation or contact Mangan Software Solutions for a demonstration.
Instrumented Systems – SIL Calculation Reports
0:06
Welcome to this Application Explainer video, part of our Instrumented Systems topic range.
0:11
In this video, we’ll cover the subject of seal calculation reports within SLM.
0:17
Seal calculation reports are the reports that are populated and can be viewed for further analysis on the Sith or HIPS once its seal calculations are completed.
0:28
In this video, we will discuss what is required for the setup of these reports, where they can be found, and what information is displayed.
0:36
The following information will be covered in this training.
0:39
Chapter one will be RRF and PFD by type, Chapter 2 will be IO sensitivity graphs and charts, and Chapter 3 will be Seal Verification Report.
0:55
In Charter One, we will be covering requirements for the RRF and FD by Type report, viewing the RRF by Type report, and viewing the FD by Type report.
1:07
For the RRF by Type tab to be effective, there are two values needed, the target RRF which can be entered manually or pulled in from the Loper module, and the achieved RRF for the desired failure rate sources.
1:21
As a result of the sill calculations for the PFD by Type report, all that is needed is the achieved PFD for the desired failure rate sources.
1:31
To find the RRF by Type report in the Instrumented Systems module, click on the SIF and then click on the RRF by Type tab.
1:40
The RRF by Type report displays the achieved risk reduction factor for each failure rate source that has been achieved through seal calculations and compares that with the target risk reduction factor for the SIF or HIPS.
1:55
Each horizontal bar shows the risk reduction factor for the different failure rate sources and whether it has met the target RF requirements, shown here as the blue bold vertical line.
2:08
In this example, only the design basis failure rate source has exceeded the target risk reduction factor.
2:15
Define the PFD by Type report, click on the SIF and click on the PFD by Type tab.
2:23
The PFD by Type report displays the seal calculation results for the SIF for each of the failure rate sources.
2:32
The next table shows the failure contributions for each of the failure rate sources by input, logic solver, and outputs.
2:40
Failure contributions are the percentage of the total failures that are attributed to inputs, logic solvers, and outputs.
2:49
UPS’s can also be included for any energized to trip scenarios.
2:55
Below that are paragraphs that show the failure contributions of the SIF components.
3:02
Each PIE graph is associated with a different failure rate source.
3:14
In Chapter 2, we’ll be covering the purpose of the IO sensitivity report, requirements for the IO sensitivity results, setting up the IO sensitivity graph and chart, interpreting the IO sensitivity chart, and interpreting the IO sensitivity graph.
3:32
The IO Sensitivity report allows you to compare and achieve risk reduction factors with the target risk reduction factor with a range of input and output test intervals.
3:43
This report has 2 main uses, 1 ensuring the design for the SIF based on test intervals meets the seal criteria specified from Loper and two, determine how long a test can be deferred before falling short of the target risk reduction factor.
4:00
For the IO sensitivity results to be effective, the same 2 requirements as the RRF by type reports are needed, the target RRF and the achieved RRF.
4:11
However, in this report, the achieved RRF must be the result of one of the three failure rate sources displayed as a result of the SEAL calculations performed in SLM prior use custom failure rate and design basis failure rate.
4:26
To begin using the IO Sensitivity report, click on the IO Sensitivity tab for the SIF.
4:33
Scroll down and click on the blue bar at the bottom of the view.
4:37
Expanding this will reveal a section of fields in which you may designate parameters.
4:42
These include the input and output test interval, the step for each, and the failure rate source used for the inputs, outputs, and logic solvers.
4:52
The drop down does not show the external result as there are no test interval values in SLM associated with this result.
5:07
The step for each test interval is the time between test intervals as shown on the chart and graph.
5:14
The unit of measure for the step always follows those of the corresponding test intervals.
5:20
Click and generate will show the results of the report in both a chart and graphical format.
5:28
The chart view and the graph view show the same information displayed in different ways.
5:33
Starting with the chart, the horizontal axis shows the input test interval as well as any changes in test intervals defined by the input step specified in the initial parameters, while the vertical axis shows the output test intervals in the same way.
5:51
Inside the chart, the coloured cells show the RRF for the intersecting input and output test intervals.
5:58
If the cell is red, the RRF falls short of the target.
6:02
If the cell is green, the RRF meets or exceeds the target RRF.
6:10
The graph view shows the same information in a different way.
6:13
The vertical axis is the achieved risk reduction factor for the SIF.
6:17
The horizontal axis is the output test interval.
6:22
Each curve on the graph is a different input test interval as denoted by the legend.
6:27
Each point on the line show the achieved risk reduction factor for that input or output combination.
6:35
Hovering the cursor over the point displays a tooltip specifying the risk reduction factor.
6:41
The horizontal dotted line is the target RRF.
6:45
Any points on or above the dotted line meet or exceed the target RRF requirements, while those points below it fall short of the target.
6:57
In Chapter 3, we will be covering viewing the Seal Verification Report and printing the Seal Verification Report.
7:06
The Seal Verification Report found by navigating to the SIF and clicking on the Seal Verification tab, is the view that places all seal verification information in one place.
7:18
It displays key information like the SIF functional requirements, which include the target information.
7:24
The sill verification results, which include the governing result source specifying which result among the failure rate sources is the official result for the sill calculations.
7:35
The SIF architectural limits calculated mean time to fail spurious.
7:40
The diagram for the SIF.
7:42
The seal calculation results, which include the total PFD and the total RRF for all of the failure rate sources.
7:52
The failure contributions of the failure rate source designated as the governing result source.
7:59
Test intervals for each of the components, then voting layer information like the voting group, PFD and voting for the beta, as well as information for each of the components like your dangerous, detected, dangerous, undetected, safe detected safe, undetected failure rates and a proof test interval.
8:22
Proof test coverage, diagnostic coverage, and mean times repair for each of the components.
8:27
That includes the inputs, the logic solver, and the outputs.
8:33
This view or report could be printed in two ways.
8:35
First, by navigating to the top of the screen and clicking the print button and printing to PDF.
8:41
Second, clicking on the report section and selecting the sealed verification report.
8:47
Here you can filter down by selecting the site and unit and then select one or multiple Sifs.
8:57
Click Generate to preview this report.
9:01
In this view it will show all Sifs that have been selected.
9:05
This is the first SIF.
9:09
As we Scroll down, we come to the next SIF or by pressing Print the PDF which allows you to print all reports in one view.