Thank You. Thank you for using exida’s premiere safety lifecycle tool, exSILentia®. What is exSILentia? exSILentia® is a completely integrated suite of engineering software tools designed to support the Process Safety Management (PSM) work process and the Safety Instrumented System (SIS) Functional Safety Lifecycle. exSILentia v4 enables data to be seamlessly shared between different lifecycle steps. We hope this Quick Start Guide helps you get familiar with this very powerful tool designed to save you time and money. Sincerely,
The exSILentia Team
1
For exSILentia online open my.exSILentia.com to launch exSILentia. Click on the exSILentia 4 icon.
2
Create a New Project by clicking on the Default project button. The default project has a default Risk Configuration and default Project Configuration elements which can be used or changed.
3
Enter the Project ID, Project Name, Revision and then press the Create
4 Click on PHA
5 Click on the ‘+’ button (New Unit)
Click on the Edit Unit button and change the “New Unit” text to “Steam Turbine”. Change the Plant Type to Power and change the
6 Click on the ‘+’ button (New
Click on the Edit Node button and change the “New Node” text to “Steam Turbine”. Change Intention to “Generate Electricity”. Change the Type to Turbine. When you change Type to Turbine it automatically creates a set of Deviations.
7
Change the name of the Cause to “PIC-002 Pressure Control Fails Open”. Change the Category to “FREQ” and change the Likelihood
Click on the Add Cause button to add a new Cause to the selected Deviation “High Pressure”
Expand the Navigation Tree and select the Deviation “High Pressure”.
8 Click on the Add Consequence button to add a new Consequence
Click on the Consequence name field and change the text to “T-100 overspeeds with potential for significant internal turbine damage”. Change the Severity Category to “B” for business assets. And change the Severity Level to 3, which represents a loss of business assets of up to $5 million if the Cause occurs.
9 Click on the Add Safeguard button to add a new Safeguard to the selected Consequence.
Change the name of the new Safeguard to “Overspeed Protection SIF”. Change the Category to “SIF” and the Tag to SIF-002.
Now that you understand a Safeguard is in place to mitigate the Likelihood of the Consequence happening, change the Likelihood W/ SG (Likelihood with Safeguards) to 2, which represents the frequency of 0.001 in a year. You can now see that the Risk w/ Safeguard is 6 compared to 12 without the
10 Click on the Add Recommendation button to add a new Recommendation to the selected Consequence.
Change the name of the new Recommendation to “Review SIL requirements for SIF-002 by completing LOPA to determine required Risk reduction factor”. Change the Category to “CALC”, the Due Date to 10/16/2015 and the Status to ASN (assigned). At this point you would decide who to assign this to but we have not added any team members.
11 Open View > Members from the menu bar to add a new member
Assign the newly added member to the Recommendation
Add a new member by pressing the ‘+’ button.
Change the newly added Member’s fields to identify the team member and close the Members window.
12 Change LOPA to Yes, which will allow this Consequence to be automatically imported to LOPA
Click on the new Hazard Scenario button ‘+’ and change the name from “New Hazard Scenario” to “Turbine Overspeed”. This Hazard Scenario will be imported automatically into LOPA since the LOPA field is set to Yes.
Click on the Hazard Scenario button. This will open the Assign Hazard Scenario window shown to the left where you will create and assign a new Hazard Scenario.
13
Add a new Consequence to the displayed Cause and change it’s Name to “T-100 overspeeds with potential for loss of containment leading to severe injuries and fatalities”. Change its Category to S (Safety) and its Severity Level to 4 (Effects national communities).
14 Link existing Safeguard and Recommendation to the new Consequence
Click on the Link button. This will open the list of available Safeguards to select. Select the Safegaurd “Overspeed Protection SIF” and press the Add button.
Click on the Link button. This will open the list of available Recommendations to select. Select the Recommendation and press the Add button.
15
Set LOPA to Yes Set the Likelihood with Safeguard to 2, which means that the event is likely to happen 0.001 or less per year. Assign the Hazard Scenario “Turbine Overspeed” to the 2nd Consequence by clicking on the Hazard Scenario button and then selecting the Available Hazard Scenario and pressing the ‘+’ button to assign it.
16 Add the following Cause/Consequence/Safeguards to the Low Temperature Deviation
Create and assign a new Hazard Scenario to the selected Consequence. Change its Name to “Serious internal damage to steam turbine”.
Also, set LOPA = Yes for the Consequence
17 Add the following Cause/Consequence/Safeguardsto the High Vibration Deviation Also, set LOPA = Yes for the Consequence
Assign the Hazard Scenario “Serious internal damage to steam turbine” to this consequence by clicking on the Hazard Scenario icon and selecting the hazard and pressing the left arrow button.
18 Switch to the LOPA Worksheet view Import Hazard Scenarios from PHA by pressing the Import from PHA button
Since this is a new project and LOPA is being used for the first time, choose Yes. You will be asked the 2nd question, which you may also choose Yes because these values were not specified in PHA.
19 Set the desired target frequencies for Business (Assets) and Safety, B=1E-3, S=1E-4.
Double click on the intersections between the IPL “Overspeed Protection SIF” and Business and Safety.
Hover the cursor over the SIF Name to display the properties editor. Then click on the Calculation icon.
Observe that the SIF’s PFD value is back calculated to meet the lowest target frequency, which is 1.00E-4.
20 Set the Target Frequency for Business to 1.00E-3.
Enable the intersections as shown here
Select the 2nd Hazard Scenario
Set the Mechanical Wear’s Frequency to 0.01.
21 Hover cursor over first IPL and click on Edit IPL Properties
Change its PFD to 0.1. Repeat for the remaining IPLs to match the snippet below. Observe that the Actual Frequency is less than the Target Frequency; therefore, RRF is N/A.
