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.
