Module Connections
Instrumented Systems Module Connections allow engineering data to flow between different stages of the functional safety lifecycle. Within SLM, information entered during Process Hazard Analysis (PHA) and Layer of Protection Analysis (LOPA) can be shared directly with the Instrumented Systems module, reducing duplicate data entry and improving consistency.
By synchronising information between modules, engineers can maintain a single source of truth for Safety Instrumented Functions (SIFs), Safety Requirement Specifications (SRS), SIL targets and lifecycle documentation. This helps ensure engineering decisions remain traceable from hazard identification through design, verification and ongoing maintenance.
This guide explains how module connections work, what information is shared between LOPA and Instrumented Systems, and how synchronisation supports efficient lifecycle management.
What Are Instrumented Systems Module Connections?
Instrumented Systems Module Connections are the links that allow engineering information to be exchanged between SLM modules. Instead of manually recreating data in multiple locations, connected modules automatically share key functional safety information where it is needed.
These connections improve collaboration between hazard analysis, risk assessment and engineering design by ensuring important information remains consistent throughout the project lifecycle.
Examples of information shared between connected modules include:
- Target Risk Reduction Factor (RRF).
- Target Probability of Failure on Demand (PFD).
- Target Safety Integrity Level (SIL).
- Calculated demand rates.
- PHA scenario information.
- Barrier and IPL associations.
- Safety Instrumented Function references.
Because this information is synchronised automatically, engineering teams spend less time maintaining duplicate records while improving traceability between hazard studies and Safety Instrumented System design.
For an overview of how the Instrumented Systems module fits into the wider engineering workflow, see the Instrumented Systems Overview.
How Instrumented Systems Module Connections Share Data
One of the primary module connections within SLM is between the LOPA module and the Instrumented Systems module. This connection allows information generated during risk assessment to be reused during engineering design without manual re-entry.
Rather than creating separate records, SLM links the associated Independent Protection Layer (IPL) with the relevant Safety Instrumented Function. Once synchronised, engineering information can be viewed from either module while remaining connected to the same underlying data.
The shared information includes three main categories:
- Target Risk Reduction Factor (RRF), Target PFD and Target SIL.
- PHA scenario information including causes and consequences.
- Calculated demand rate for the Safety Instrumented Function.
Maintaining these links improves consistency throughout the engineering process and ensures changes made during risk assessment can be reflected within the design documentation.
For more information about determining risk reduction requirements, see the LOPA Calculations guide.
Synchronising Instrumented Systems Module Connections
Module synchronisation is achieved by associating a barrier or Independent Protection Layer within LOPA with a corresponding engineering function in the Instrumented Systems module. Once linked, both modules reference the same engineering relationship, allowing important lifecycle information to remain synchronised.
Users can associate existing Safety Instrumented Functions or automatically create new engineering objects where required, reducing manual configuration effort.
Synchronisation provides several advantages:
- Eliminates duplicate engineering records.
- Maintains consistent SIL targets.
- Synchronises calculated demand rates.
- Improves traceability between hazard studies and design.
- Supports lifecycle documentation.
- Simplifies future engineering modifications.
Using connected engineering data helps ensure that hazard analysis and detailed design remain aligned throughout the functional safety lifecycle.
To understand how these engineering objects are configured, see the Configuring a Safety Instrumented Function guide.
Performing a LOPA Function Sync
A LOPA Function Sync creates the relationship between an Independent Protection Layer (IPL) in the LOPA module and its corresponding engineering object within the Instrumented Systems module. Once synchronised, both modules reference the same function, allowing engineering information to be shared automatically throughout the safety lifecycle.
Users can perform a function sync from either the Instrumented Systems module or directly from the associated barrier within the LOPA module. Existing Safety Instrumented Functions can be linked, or new functions can be created during the synchronisation process.
Synchronising functions provides several benefits:
- Maintains a single source of engineering data.
- Reduces duplicate data entry.
- Keeps LOPA and engineering records aligned.
- Improves lifecycle traceability.
- Simplifies future engineering updates.
For more information on configuring engineering objects after synchronisation, see the Configuring a Safety Instrumented Function guide.
Shared Risk Reduction and SIL Data
Once a function has been synchronised, key risk assessment information becomes available within the Instrumented Systems module. This eliminates the need to manually transfer important engineering values between modules.
Shared information includes the calculated Target Risk Reduction Factor (RRF), Target Probability of Failure on Demand (PFD) and Target Safety Integrity Level (SIL). These values originate from the LOPA study and remain linked to the associated Safety Instrumented Function.
Maintaining these shared values helps engineers verify that system designs continue to satisfy the risk reduction requirements established during hazard analysis.
To learn more about these calculations, see the LOPA Calculations guide.
Viewing Connected Scenario Information
Module connections also synchronise the scenario information associated with each Safety Instrumented Function. Engineers can view linked causes, consequences, calculated risk reduction factors and associated barrier information without switching between disconnected engineering records.
By maintaining these relationships throughout the safety lifecycle, teams can quickly understand why a Safety Instrumented Function exists and the hazards it is designed to protect against. This improves engineering reviews, management of change activities and future Functional Safety Assessments.
Connected scenario information provides complete traceability from hazard identification through detailed engineering design, helping organisations maintain accurate lifecycle documentation while reducing administrative effort.
For an overview of how connected engineering information supports the wider lifecycle, see the Instrumented Systems Overview.
Benefits of Connected Engineering Data
Connecting the LOPA and Instrumented Systems modules provides far more than a convenient data transfer mechanism. By maintaining relationships between hazard studies, Safety Instrumented Functions (SIFs) and engineering documentation, organisations can build a complete digital record of the functional safety lifecycle.
Instead of manually updating multiple records, engineers can work from a shared dataset that improves consistency across projects and reduces the risk of conflicting information.
- Reduces duplicate engineering effort.
- Improves consistency between LOPA and design activities.
- Maintains traceability throughout the safety lifecycle.
- Supports more accurate engineering reviews.
- Simplifies management of change activities.
- Provides greater confidence in lifecycle documentation.
Using connected engineering data allows project teams to spend less time maintaining information and more time delivering safe, compliant systems.
Common Module Synchronisation Mistakes
Module synchronisation is most effective when engineering objects are linked correctly and maintained throughout the project lifecycle. Inconsistent object selection or manual duplication can reduce the benefits of connected data.
Common mistakes include:
- Creating duplicate Safety Instrumented Functions instead of linking existing ones.
- Synchronising the wrong barrier or IPL with a function.
- Failing to review shared data after engineering changes.
- Maintaining separate records outside the connected workflow.
- Ignoring updated risk assessment information after LOPA revisions.
Following a consistent synchronisation process helps ensure engineering data remains accurate, traceable and aligned across every phase of the functional safety lifecycle.
Learn More About Instrumented Systems
Module connections are only one part of the Instrumented Systems workflow within SLM. Additional guides explain how Safety Instrumented Functions are configured, how Safety Requirement Specifications are managed and how engineering calculations support IEC 61511 compliance.
- Instrumented Systems Overview
- Safety Requirement Specification (SRS)
- Configuring a Safety Instrumented Function
- SIL Calculation Reports
- LOPA Calculations
For additional guidance on functional safety lifecycle requirements, refer to the International Electrotechnical Commission (IEC), which publishes the IEC 61511 standard for Safety Instrumented Systems.
Instrumented Systems – Module Connections
0:07
Welcome to this Application Explainer video, part of our Instrumented Systems topic range.
0:12
In this video, we’ll cover the subjects of module connections within SLM.
0:18
One of the main benefits of SLM is the way it connects data across phases of the life cycle.
0:24
There are many connections made between the modules that permit data to flow more efficiently.
0:29
In this video, we will cover what data is shared between the PHA and design portions of the life cycle and how that sharing is initiated by the user.
0:39
The following information will be covered in this training.
0:42
Chapter one will be LOPA associations and Chapter 2 will be LOPA function sync.
0:52
In Chapter 1, we’ll be covering a data shared between LOPA and Instrumented Systems modules and the location of data in each module.
1:01
There are three main grouping categories of data shared between the LOPA and the instrumented systems module.
1:08
First is the target risk reduction factor, which also is associated with the target probability of failure on demand and the safety integrity level for those Ipls.
1:19
Second is the PHA scenario information, and 3rd is the calculated demand rate.
1:26
The first of the three groups of data that we will look at is the target risk reduction factor, target probability of failure on demand, and target safety integrity level.
1:35
In the local module, navigate to the IPO object.
1:39
The Calculated Fields table displays the calculated target risk reduction factor and calculated target safety integrity level values.
1:50
The target RRF and PFD for a SIF is calculated in the LOPA module based on the scenarios it’s applied to and the remaining gap for each of these scenarios.
2:01
For more information on this calculation, see the video on LOPA calculations in instrumented systems.
2:08
The same information can be seen by clicking on the SIF object and viewed in the first section for the performance, target sill RRF, and PFD.
2:18
The target PFD is calculated as the inverse of the target RRF.
2:23
The second group amongst the information shared between LOPA and instrumented systems is the PHA scenario information.
2:30
We can see this information on the Barrier or IPL tab by scrolling down to the risk reduction factor for the SIF.
2:39
This table displays the scenario information, including initiating calls for the short description, the risk reduction factor for each of the scenarios, and the hazard or consequence.
2:51
This information can also be seen in instrumented systems on the SIF SIF Overview tab.
2:57
Scroll down to the Local reference table here.
3:01
It shows the local barrier or IPL ID, the local worksheet scenario information including your cause and consequence, and risk reduction factor.
3:10
The first set of data that is shared between the local module and instrumented systems is the calculated demand rate for the SIF in the local module.
3:20
This information can be found once again on the IPL or Barrier object in the Calculated Fields table.
3:27
For more information on how this demand rate is calculated, see the video on Local calculations.
3:32
To view the same information in the Instrumented Systems module, navigate once again to the SIF and click on the General tab.
3:40
In this first section, you can see the calculated SIF demand rate.
3:45
For more information on how this demand rate is calculated, see the LOPA Calculations video.
3:54
In Chapter 2, we will cover what is a LOPA function sync, performing a LOPA function sync from the Instrumented Systems module, and performing a LOPA function sync from the LOPA module.
4:05
A LOPA function sync is when the IPL from LOPA is associated with a function in Instrumented systems, relief systems, or non instrumented systems.
4:15
It’s this association of objects that allows for the data from the LOPER module to be shared with the design modules, although the process is the same with any of the design modules.
4:26
This video will be specifically looking at an instrumented systems example.
4:30
There are two main locations that you can perform this LOPER function sync.
4:34
1 is in the Features menu, Instrumented Systems.
4:37
The second is the IPL or Barrier object in LOPA.
4:41
To start the process of performing a LOPA function sync in the Instrumented Systems module, navigate to the Features menu, click on LOPA Function Sync.
4:50
Here you’ll go for a series of filters to navigate to the desired barrier by selecting the unit, the LOPA Study Barrier category, and Barrier Type, which are all the instrumented functions in Instrumented Systems.
5:06
In this example, we will link together a barrier to a SIF, select Get Barriers and now you see 2 tables.
5:12
One is the barrier list or IPL, where you can search for the barrier that you wish to link to your function.
5:21
Select that barrier.
5:22
On the right hand side you can see the function list where you can select the function that exists currently in Instrumented Systems to associate it with.
5:31
To sync these two functions, the barrier and the functions gather.
5:34
Click on Sync to selected function.
5:36
If the function does not exist in the function list in Instrumented Systems and you wish to have it created, you click Create New function and it would automatically create a new function of the filtered type now that the function has been synced.
5:57
The scenario information is shown.
6:00
The second way to sync a function is in the local module on the barrier or IPO object.
6:08
Navigate to the IPO object and in the function link click on No Data and then search for the function that you would like to find.
6:22
Click save and now the barrier and the functions are linked.
6:29
The difference between using the lope method and the instrumented systems method is that with the lope method there is no restriction on barrier type linked to a specific function type of object.
6:41
You can select as seen here alarms, BPCSS and so on, whereas in the instrumented systems method you must select the function or object type that matches with the barrier category.