general electric€¦ · tableofcontents...

Meridium APM SIS Management

Confidential and Proprietary Information of Meridium, Inc. • of 547


3.6.1.0.0

Copyright and Legal



3.6.1.0.0

Copyright © Meridium, Inc. 2016

All rights reserved. Printed in the U.S.A.

This software/documentation contains proprietary information of Meridium, Inc.; it isprovided under a license agreement containing restrictions on use and disclosure. All rightsincluding reproduction by photographic or electronic process and translation into other lan-guages of this material are fully reserved under copyright laws. Reproduction or use of thismaterial in whole or in part in any manner without written permission from Meridium, Inc. isstrictly prohibited.

Meridium is a registered trademark of Meridium, Inc.

All trade names referenced are the service mark, trademark or registered trademark of therespective manufacturer.

About This Document


About This DocumentThis file is provided so that you can easily print this section of theMeridiumAPMHelp system.

You should, however, use the Help system instead of a printed document. This is becausethe Help system provides hyperlinks that will assist you in easily locating the related instructionsthat you need. Such links are not available in a print document format.

TheMeridiumAPMHelp system can be accessed within MeridiumAPM itself or via theMeridiumAPMDocumentationWebsite (https://www.me-ridium.com/documentation/WebHelp/WebHelpMaster.htm).

Note: If you do not have access to theMeridiumAPMDocumentationWebsite, contactMeridiumGlobal Support Services.

https://www.meridium.com/documentation/WebHelp/WebHelpMaster.htm

https://www.meridium.com/documentation/WebHelp/WebHelpMaster.htm

https://www.meridium.com/support

Table of Contents


Table of ContentsMeridium APM SIS Management 1

Copyright and Legal 2

About This Document 3

Table of Contents 4

Overview of Safety Instrumented System (SIS) Management 15

What is a Safety Instrumented System? 17

SIS Management System Requirements 19

Overview of the SIS Management Data Model 20

Illustration of the SIS Management Data Model 21

Safety Instrumented System Family Is the Predecessor Family 23

Instrumented Function Family Is the Predecessor Family 25

Protective Instrument Loop Family Is the Predecessor 27

Components of an SIL Analysis 28

The SIS Management Workflow 30

SIL Analysis State Configuration 31

Protective Instrument Loop State Configuration 34

SIS Trip Report State Configuration 38

Integration with Hazards Analysis 41

Accessing the SIS Management Start Page 42

Aspects of the SIS Management Start Page 43

First-Time Deployment Workflow 44

Upgrade or Update SIS Management to 3.6.1.0.0 46

SIS Management Security Groups 54

Accessing the SIS Management Administration Page 60

Aspects of the SIS Management Administration Page 61

Common Tasks Menu 62

Specifying a Different Query on SIS Management Administration Page 63

Specifying the Asset Source for ASM Integration 64

Table of Contents


About Importing Data from an Exida Project File 65

Accessing the Options Screen 66

Creating a New Analysis for the Imported Data 69

Appending the Imported Data to an Existing Analysis 71

About Exporting Data to an Exida Project File 73

Exporting Data to an Exida Project File 74

About Managing the Types of Independent Layers of Protection 78

About Independent Layer of Protection Types 79

Modifying the Default Values in the Baseline IPL Type Records 81

Defining Additional IPL Types 82

An Example: Defining Additional IPL Types 85

About Navigating SIS Management 87

The Navigation Menu in SIS Management 88

About SIL Analysis Records 89

Accessing the SIL Analysis Search Page 90

Aspects of the SIL Analysis Search Page 91


Searching for SIL Analysis Records 93

Accessing the SIL Analysis Definition Page 94

Aspects of the SIL Analysis Definition Page 95


About Defining SIL Analysis Records 97

Creating SIL Analysis Records 98

Copying SIL Analysis Records 99

Modifying SIL Analysis Records 101

Opening Existing SIL Analysis Records 102

Removing SIL Analysis Records from the SIL Analysis Search Page 103

About Associating SIL Analyses with a Specific Site 104

About the SIL Analysis Team 105

Accessing the SIL Analysis Team Members Page 106

Table of Contents


Aspects of the SIL Analysis Team Members Page 107

Common Tasks 108

Creating New Users and Adding Them to the SIL Analysis Team 109

Adding New Team Members Who Already Have A Human Resource Record 111

About SIL Analysis Team Member Roles 113

Assigning Roles to SIL Analysis Team Members 114

Viewing Human Resource Records for Existing Team Members 115

Removing Team Members from the SIL Analysis Team 116

Accessing the Reference Documents Page 117

Aspects of the Reference Documents Page 118

Common Tasks 119

Creating New Reference Document Records and Adding Them to the SIL Analysis 120

Adding Existing Reference Document Records to the SIL Analysis 121

Viewing Reference Documents 122

Opening Reference Document Records 123

Removing Reference Documents from the SIL Analysis 124

About Safety Instrumented System Records 125

Accessing the Safety Instrumented Systems Page 126

Aspects of the Safety Instrumented Systems Page 127

Assessment Tasks 128

Common Tasks 129

Creating New Safety Instrumented System Records 130

Adding Existing Safety Instrumented System Records to the SIL Analysis 132

Copying Existing Safety Instrumented System Records 134

Modifying Safety Instrumented System Records 135

Removing Safety Instrumented System Records from the SIL Analysis 136

About Instrumented Function Records 137

Accessing the Instrumented Functions (IFs) Page 138

Aspects of the Instrumented Functions (IFs) Page 139

Assessment Tasks 141

Table of Contents


Common Tasks 143

About Defining Instrumented Function Records 144

Creating New Instrumented Function Records 146

About the Instrumented Function Tab 148

About The Safety Requirement Specification Tab 149

About SIF Common Cause Failure Records 150

Aspects of the Common Cause Failures Tab 152

Creating New Common Cause Failure Records 154

Linking Existing SIF Common Cause Failure Records to Instrumented FunctionRecords 157

Linking Additional Instrumented Function Records to an SIF Common Cause FailureRecord 159

Removing SIF Common Cause Failure Records from an Instrumented FunctionRecord 161

About Concurrent Safe State Hazards and Instrumented Function Records 162

Aspects of the Concurrent Safe States Tab in Instrumented Function Records 165

Defining Concurrent Safe State Hazards for Instrumented Functions 167

Removing Instrumented Functions From the Concurrent Safe States Tab 174

Adding Existing Instrumented Function Records to the SIL Analysis 176

Copying Existing Instrumented Function Records 178

Modifying Existing Instrumented Function Records 179

About Assessing the SIL Level for Instrumented Functions 180

SIL Level and Required Probability of Failure 181

About Assessing SIL Values Via the Risk Matrix 186

Accessing the Risk Assessment Interface 187

About Assessing SIL Values via a Hazards Analysis Risk Assessment 188

About Mapping Values from a Hazards Analysis 189

Selecting a Risk Assessment Record from a Hazards Analysis 190

Aspects of the PHA Risk Assessment Window 193

What is a Layer of Protection Analysis (LOPA)? 195

Navigation Menu 196

Table of Contents


Common Tasks 197

About LOPA Records 198

Accessing the LOPA Definition Page 199

Aspects of the LOPA Definition Page 200

Creating LOPA Records 201

Opening Existing LOPA Records 202

Adding Existing LOPA Records to the Associated Risk Assessments Grid 203

Copying LOPA Records to Create New Ones 205

Removing LOPA Records from the Associated Risk Assessments Grid 206

About Independent Layer of Protection Records 207

Creating Independent Layer of Protection Records 208

Deleting Independent Layer of Protection Records 210

About Consequence Modifier Records 211

Accessing the Consequence Modifiers Page 212

Aspects of the Consequence Modifiers Page 213

Creating New Consequence Modifier Records 214

Removing Consequence Modifier Records from the Consequence Modifiers Grid 215

About Promoting Instrumented Functions to ASM 216

Promoting Instrumented Functions to ASM 218

Viewing Asset Strategies Created from Instrumented Functions 219

About Proof Testing 220


Accessing the Proof Test Template Definition Page 223

Aspects of the Proof Test Template Definition Page 224

Creating SIS Proof Test Template Records 225

Accessing a List of Existing SIS Proof Test Template Records 227

Aspects of the Proof Test Templates Page 229

Viewing an Existing SIS Proof Test Template Record 230

Adding Existing SIS Proof Test Template Detail Records to the SIS Proof Test Tem-plate Record 231

Table of Contents


Viewing Existing SIS Proof Test Template Detail Records 233

Removing SIS Proof Test Template Detail Records from the SIS Proof Test Tem-plate Record 234

Copying SIS Proof Test Template Records to Create New Ones 235

Removing SIS Proof Test Template Records 236

About SIS Proof Test Records 237


Accessing the Proof Test Definition Page 239

Aspects of the Proof Test Definition Page 240

Creating New SIS Proof Test Records 241

Accessing the List of Existing SIS Proof Test Records 242

Aspects of the Proof Tests Page 243

Opening SIS Proof Test Records 244

Recording Proof Test Results in SIS Proof Test Records 245

About Protective Instrument Loops 247

About the SIL Validation Feature 248

The SIL Validation Workflow 250

The Navigation Menu 251

The SIL Validation Menu 252

The Common Tasks Menu 253

About Creating Protective Instrument Loops 254

Creating New Protective Instrument Loops Manually 255

Creating New Protective Instrument Loops Based on a Template 256

About Opening Existing Protective Instrument Loops 258

Accessing a List of Existing Protective Instrument Loops 259

Aspects of the Protective Loop Search Page 260

Common Tasks 261

Opening an Existing Protective Instrument Loop 262

Opening Protective Instrument Loops Associated with an Instrumented Function inan SIL Analysis 263

Table of Contents


Aspects of the Protective Instrument Loop Diagram View Page 264

Adding Elements to the Protective Instrument Loop Diagram 266

Defining Element Properties in the Diagram View 267

Removing Elements from the Protective Instrument Loop Diagram 269

Linking Existing Records to Elements in the Protective Instrument Loop 270

Unlinking Elements from a Protective Instrument Loop 274

Accessing the Protective Instrument Loop Grid View Page 277

Aspects of the Protective Instrument Loop Grid View Page 278

Accessing the Protective Instrument Loop Summary Page 279

Aspects of the Protective Instrument Loop Summary Page 280

Deleting Protective Instrument Loops 281

About Protective Instrument Loop Templates 282

About Creating Protective Instrument Loop Templates 284

Creating Protective Instrument Loop Templates from Scratch 285

Creating Protective Instrument Loop Templates Based on Existing Protective Instru-ment Loops 286

Copying Protective Instrument Loop Templates to Create New Ones 287

Accessing the Protective Loop Template Search Page 288

Aspects of the Protective Loop Template Search Page 289

The Common Tasks Menu 290

Opening Existing Protective Instrument Loop Templates 291

About Calculating SIL Validation Results 292

Calculating SIL Validation Results for a Protective Instrument Loop 293

Calculating SIL Validation Results for Multiple Protective Instrument Loops 294

About Calculation Details 295

About the Missing Required Values Dialog Box 296

About Protective Instrument Loop Final Element Records 298

About Defining Hazards Associated With Combined Output States 299

Aspects of the Dangerous Combination of Output States Tab in Protective InstrumentLoop Final Element Records 302

Table of Contents


Defining Combined Output State Hazards for Final Elements 304

Removing Final Elements From the Dangerous Combination of Outputs Tab 312

About the Protective Instrument Loop Report 314

Viewing the Protective Instrument Loop Report 316

Viewing SIL Analysis Graphs 317

Viewing SIL Analysis Reports 319

About the Safety Requirement Specifications Report 320

Accessing the Safety Requirement Specifications Report 321

About Managing Validation Failure Rate Reference Data 323

Navigation 324

Common Tasks 325

Accessing the Sensor Reference Data Search Page 326

Aspects of the Sensor Reference Data Search Page 327

Opening Existing Protective Instrument Loop Sensor Records 328

Aspects of the Sensor Reference Data Page 329

Creating New Protective Instrument Loop Sensor Records from Scratch 330

Creating Protective Instrument Loop Sensor Records as Copies of an Existing One 331

Approving and Revoking Approval for Protective Instrument Loop Sensor Records 334

Accessing the Logic Solver Reference Data Search Page 335

Aspects of the Logic Solver Reference Data Search Page 336

Opening Existing Protective Instrument Loop Logic Solver Records 337

Aspects of the Logic Solver Reference Data Page 338

Creating Protective Instrument Loop Logic Solver Records from Scratch 339

Creating Protective Instrument Loop Logic Solver Records Based on Existing Ones 340

Creating Protective Instrument Loop Logic Solver Records as Copies of an ExistingOne 342

Linking Protective Instrument Loop Logic Solver Channel Records to ProtectiveInstrument Loop Logic Solver Records 345

Removing Protective Instrument Loop Logic Solver Channel Records from ProtectiveInstrument Loop Logic Solver Records 347

Table of Contents


Approving and Revoking Approval for Protective Instrument Loop Logic SolverRecords 348

Accessing the Final Element Reference Data Search Page 349

Aspects of the Final Element Reference Data Search Page 350

Opening Existing Protective Instrument Loop Final Element Records 351

Aspects of the Final Element Reference Data Page 352

Creating New Protective Instrument Loop Final Element Records from Scratch 353

Creating Protective Instrument Loop Final Element Records as Copies of an ExistingOne 354

Approving and Revoking Approval for Protective Instrument Loop Final ElementRecords 356

About SIS Trip Reports 357

Accessing the SIS Trip Report Search Page 358

Aspects of the SIS Trip Report Search Page 359

Opening Existing SIS Trip Report Records 360

Navigation 361

Common Tasks 362

Aspects of the SIS Trip Report Page 363

Creating New SIS Trip Report Records 364

Accessing the SIS Trip Report Details Page 367

Aspects of the SIS Trip Report Details Page 368

Creating New SIS Trip Report Details Records 369

Viewing SIS Trip Report Detail Records 370

Deleting SIS Trip Report Detail Records 371

About Revision History in SIS Management 372

Accessing SIL Analysis Revisions 373

Aspects of the Analysis Revision History Page 374


Viewing the Datasheet for a Revision Record 377

Viewing Changes That Were Made Between Revisions 378

About Risk Assessment Recommendation Records and the SIL Analysis 379

Table of Contents


Accessing the Recommendations Dialog Box 380

Aspects of the Recommendations Dialog Box 382

Creating New Risk Assessment Recommendation Records 383

Adding Existing Risk Assessment Recommendation Records to the SIL Analysis 385

Removing Risk Assessment Recommendation Records from the SIL Analysis 387

Using the Status Field in Recommendations 388

About Scheduling Risk Assessment Recommendation Alerts 390

Scheduling Alert to Notify an Assignee When a Recommendation is Due 391

Scheduling an Alert to Notify Assignees When a Recommendation is Due for Ree-valuation 392

Viewing the List of Risk Assessment Recommendation Records for the Current SILAnalysis 393

Viewing the List of Risk Assessment Recommendation Records for All SIL Analyses394

About Inspection Tasks Records 395

Creating Inspection Task Records 396

Viewing the List of Inspection Task Records that are Linked to an Individual Record 398

Viewing the List of Inspection Task Records for All SIL Analyses 399

Associated Pages 400

About the SIS Management Catalog Folder Structure 401

Dashboards Folder 403

LOPA Folder 404

PIF Folder 405

Proof Test Template Folder 406

Proof Tests Folder 407

Protective Instrument Loop Folder 408

About The Queries Folder 409

Queries That Support Module-Specific Pages 410

Queries That Support The SRS Report 415

Dashboard Queries Folder 417

SIL Folder 420

Table of Contents


SIS Trip Report Folder 422

Consequence Modifier 423

Independent Layer of Protection 424

Instrumented Function 427

Functional Test Detail 453

LOPA 458

Protective Instrument Loop 464

Protective Instrument Loop Final Element 481

Protective Instrument Loop Logic Solver 484

Safety Instrumented System 493

SIF Common Cause Failure 498

SIL Analysis 499

SIS Proof Test 517

SIS Proof Test Template 522

SIS Proof Test Template Detail 524

System Code Tables Used by SIS Management 526

Parameters for the SIS Management URL 527

Examples of SIS Management URLs 542

Instrumented Function 543

Maintenance Capability Index (MCI) 544

Proof Test 545

Protective Instrument Loop 546

SIL Value 547

Overview of Safety Instrumented System (SIS) Management


Overview of Safety Instrumented System (SIS) Man-agementThe Safety Instrumented System (SIS) Management module lets youmanage the safety instru-mented systems that are in place in a facility to monitor andmaintain controlled processes andensure efficiency and safety during those processes.

For example, heating the temperature of a room is a process that has a specific, desired outcometo reach andmaintain the desired temperature (e.g., 20 degreesCelsius). If the temperatureincreases too rapidly, the temperature change could lead to a chain of events that may result inequipment failure or a catastrophic event. To prevent a rapid temperature increase during theheating process, a sensor within the thermometer continuallymeasures the temperature andrelays that information to a computer. The computer decideswhether the temperature is increas-ing at intervals that are in line with the specified safe limits for this process. If the data transmittedto the computer indicates that the temperature is increasing too rapidly, it will send a command tothe heating element to decrease the temperature.

Together, the sensor within the thermometer, the computer, and the heating element act as asafety instrumented system that monitors the process of heating a room to ensure that it is per-formed safely and efficiently.

Using SIS Management, you can conduct a Safety Integrity Level (SIL) Analysis, which you canuse to assess the integrity of the safety instrumented systems that are already in place in yourfacility and to uncover areas that may require further safeguarding. An SIL Analysis (pronouncedS-I-L) lets you assign a numeric rating to the safety instrumented systems that you are analyzing.This numeric rating represents the level of protection that those systems currently provide, calleda safety integrity level (SIL).

For instance, consider the previous example. If the heating element safely and successfullyreduces the speed at which the temperature is increasing, this safety instrumented systemwouldbe considered to have a higher integrity level than one in which the temperature in the room con-tinues to increase despite the efforts of the system.

To conduct an SIL Analysis in SIS Management, a team of individuals will:

l Define the function of the safety instrumented systems that will be assessed.

l Identify the undesirable consequences that the safety instrumented systems are designedto prevent.

l Test the components of the safety instrumented systems to determine if its performance ismeeting the specified requirements and identify failures that may be occurring within thosesystems.

l Based on the test results, determine where further improvements are needed within thesafety instrumented systems.

In addition, the SIS Management module provides the tools necessary for compliance with thestandard IEC 61511.

Overview of Safety Instrumented System (SIS) Management


Note: TheMeridiumAPMSIS Management module and supporting documentation are ded-icated inmemory of Steve Soos IV, Product Manager, whose knowledge, dedication, and vis-ion are realized therein.

What is a Safety Instrumented System?


What is a Safety Instrumented System?A safety instrumented system (SIS) is a system comprised of instruments that are designed spe-cifically to:

l Monitor the conditions of a process. Processes can be executed by an equipment andlocations.

l Recognize conditions that are indicative of failure. Identifying the initiating events thatcould lead to a safety instrumented system failure can provide the systemwith enough timeto prevent the failure. The consequences of a safety system failure can lead to a chain ofevent that causes further equipment failure and even a catastrophic event.

l Prevent consequences by reacting to conditions that are indicative of a failure. Safetyinstrumented systemsmake adjustments to the process to bring the conditions to amit-igated state or even shut down that process to prevent failures.

A safety instrumented system consists of the following items:

l One or more protective instrument loops (PIL), which is a series of interconnected instru-ments. Each protective instrument loop (PIL) is designed tomaintain a defined conditionwithin the process, meaning that it serves a specific purpose or instrumented function(IF).In other words, for every instrumented function that exists for a safety instrumented sys-tem, there is one protective instrument loop in place to fulfill that function.

l One logic solver, which is a computer that interprets readings from the components of theprotective instrument loop (PIL) andmeasures that information against predefined criteriato determine whether that system needs tomake adjustments tomitigate the risk asso-ciated with the instrumented functions of each protective instrument loop.

For example, assume that Unit A provides steam to Unit B, and SIS-A is in place on Unit A andUnit B tomaintain the pressure levels during that process to prevent loss of pressure or excesspressure beyond the defined safe and productive levels. Maintaining safe and productive pres-sure levels are the instrumented functions of the protective instrument loopswithin SIS-A. Thelogic solver within SIS-A receives data from the components of the protective instrument loopsand decideswhether the pressure levels are normal, exceed, or are lower than the safe and pro-ductive pressure levels. If the current pressure levels indicate the possibility of a process failure,which includes scenarios like loss of productivity or explosion, the logic solver tells the com-ponents of the SIS to do something tomitigate the current condition. For example, if the currentcondition of the process indicates that the pressure is too low, the logic solver will tell an elementof the protective instrument loop to increase the pressure so the levels are within the safe and pro-ductive levels defined for that process.

The following image illustrates a safety instrumented system and the relationships describedabove.

What is a Safety Instrumented System?


In summary:

l A given process can havemore than one safety instrumented system in place tomonitorand safeguard its conditions.

l Each safety instrumented system contains one protective instrument loop per instru-mented function to fulfill that function within the safety instrumented system.

l Each safety instrumented system contains one logic solver to interpret the readings fromthe components of the protective instrument loop and instruct those elements to takeaction if necessary.

l The components of a protective instrument loop provide data in the form of readings to thelogic solver.

SIS Management System Requirements


SIS Management System RequirementsThe SIS Management license is required to take advantage of SIS Management functionality. Inaddition, your systemmust contain the basicMeridiumAPM system architecture.

In order to use the integration between SIS Management and Hazards Analysis, the HazardsAnalysis license is also required.

ŒHint: Details on the system requirements for the basicMeridiumAPM system architectureand activating licenses can be found in the Installation, Upgrade, and SystemAdministrationsection of theMeridiumAPMHelp system.

After you have installed and configured the basic system architecture, you will need to performsome configuration tasks specifically for the SIS Management feature.

Overview of the SIS Management DataModel


Overview of the SIS Management Data ModelThe SIS Management datamodel uses families to represent the various components of an SILAnalysis. MeridiumAPM leverages its fundamental entity and relationship family infrastructure tostore data related to an SIL Analysis. When attempting to understand andmake use of theMeridiumAPMSIS Management functionality, it is helpful to visualize the SIS Management datamodel.

Because you should already be familiar with the concept of records and viewing records in theMeridiumAPMRecordManager, as you attempt to get your bearings in SIS Management, it maybe useful to remember that SIS Management is simply a customized view of individual recordsthat work together to make up an SIL Analysis.

Note: While SIS Management provides a customized view of individual records that exist in theMeridiumAPMdatabase, you should not use the RecordManager tomanage records for usewith SIS Management. You should use the features provided in theMeridiumAPMSIS Man-agement module only.

All SIL Analyses begin with an SIL Analysis record. Each SIL Analysis record will be linked to:

l One Equipment or Functional Location record.

l One or more HumanResource records.

l One or more Reference Document records.

l One or more Instrumented Function records.

l One or more Safety Instrumented System records.

Each Safety Instrumented System record will be linked to:

l One or more Instrumented Function records.

l One or more SIS Proof Test records.

l One or more SIS Proof Test Template records.

Each Instrumented Function recordswill be linked to:


l One or more Protective Instrument Loop records.

l One or more Inspection Tasks records.

l OneRisk Assessment records.

l One or more LOPA records.

l One or more SIS Proof Test records.

l One or more SIS Proof Test Template records.

Illustration of the SIS Management DataModel


Illustration of the SIS Management Data ModelThe SIS Management datamodel uses families to represent various components of an SIL Ana-lysis. MeridiumAPM leverages its fundamental entity and relationship family infrastructure tostore data related to an SIL Analysis.

The following diagram illustrates the families that participate in the SIL Analysis. The shadedboxes represent entity families, and the arrows represent relationship families. You can determ-ine the direction of each relationship definition from the direction of the arrow head: the box to theleft of each arrow head is the predecessor in that relationship definition, and the box to the right ofeach arrow head is the successor in that relationship definition.

The SIS Management datamodel is best understood if you view it in portions, and to simplify thisimage, some relationship and entity families are not included.

This section of the documentation includes images of the portions of the SIS Management datamodel that are not illustrated in the preceding image. Each image illustrates the portion of the SISManagement datamodel where the following families participate as the predecessor family in therelationships illustrated in the image:

l Safety Instrumented System

l Instrumented Function

l Protective Instrument Loop

The Reference Document family is a shared family. Meaning that the Reference Document fam-ily is used bymultiple families within the SIS Management datamodel. To simplify all the datamodel images, the Reference Document family is included only in the preceding image, wherethe SIL Analysis family is the predecessor. In addition to this relationship, the Reference

Illustration of the SIS Management DataModel


Document family participates as the successor in the HasReference Documents relationshipdefinition with the following families:

l SIL Analysis

l SIS Proof Test

l SIS Proof Test Template


l Risk Assessment Recommendation

To simplify the datamodel images, the following families are not included:

l Risk Assessment Recommendation.Within the SIS Management datamodel, the RiskAssessment Recommendation family participates as the successor in the HasRecom-mendations relationship definition with the following families:

n Instrumented Function

n Protective Instrument Loop

n SIS Proof Test

n SIS Proof Test Template

l IPL Type. This family is not related to any family in the baselineMeridiumAPMdatabase.The IPL Type family is a subfamily of theMeridiumReference Tables family. IPL Typerecords store details about independent layer of protection types and are used to populateIndependent Layer of Protection records.

l Hazards Analysis. The Hazards Analysis family participates as the successor in the HasHAZOP Reference relationship definition with the SIL Analysis and Instrumented Functionfamilies.

Safety Instrumented System Family Is the Predecessor Family


Safety Instrumented System Family Is the PredecessorFamilyThe following image shows the relationshipswhere the Safety Instrumented System family par-ticipates as the predecessor.

Note: To simplify this image, the relationships between the Instrumented Function family andthe SIS Proof Test and SIS Proof Test Template families is not included. This relationship isillustrated in the image that illustrates the relationships in which the Instrumented Function fam-ily participates as the predecessor.

The Safety Instrumented System family contains records that store information about the safetyinstrumented system that you are analyzing. Safety Instrumented System records are linked toInstrumented Function records, which store information about the specific functions associatedwith the safety instrumented system. Safety Instrumented System records are also linked torecords in the following families:

l SIS Proof Test: Store details about a proof test that is performed on a safety instrumentedsystem and serves as a record of the proof test event. SIS Proof Test record can be linkedto Functional Test Detail records, which store the detailed steps that need to be performedduring the proof test.

l SIS Proof Test Template: Store details about the steps that should be taken when testinga safety instrumented system.When you create SIS Proof Test record, you can select anSIS Proof Test Template record, and the details from the SIS Proof Test Template recordwill be populated automatically in the SIS Proof Test record. SIS Proof Test Template

Safety Instrumented System Family Is the Predecessor Family


records can be linked to SIS Proof Test Template Detail records, which store details on thesteps that need to be performed during the proof test.

The SIS Proof Test, SIS Proof Test Template, and Reference Document families participate asthe successor in other relationshipswithin the SIS Management datamodel. Thismeans thatthese families appears in another portion of the datamodel.

Instrumented Function Family Is the Predecessor Family


Instrumented Function Family Is the Predecessor Fam-ilyThe following image shows the relationships in which the Instrumented Function family par-ticipates as the predecessor.

Instrumented Function records store details about a specific function of an SIS. InstrumentedFunction records are linked directly to records in the following families:

l Inspection Task: Stores details on when a task should be performed on the item rep-resented by the record to which the Inspection Task record is linked, including the due datefor the task.

l SIS Proof Test: Stores details about a test that is taken on a safety instrumented systemand serves as a record of the event.

l SIS Proof Test Template: Stores details about the steps that should be taken when test-ing a safety instrumented system.When you create an SIS Proof Test record, you canselect an SIS Proof Test Template record, and the details from the SIS Proof Test Tem-plate record will be populated automatically in the SIS Proof Test record.

l Risk Assessment: Stores the unmitigated risk associated with the item represented bythe record to which the Risk Assessment record is linked.

Instrumented Function Family Is the Predecessor Family


l Protective Instrument Loop: Stores the details of the protective instrument loop and itscomponents, including the calculated results of the proof test associated with the SafetyInstrumented System record to which the Protective Instrument Loop record is linked.

l LOPA: Stores the details of the Layer of Protection Analysis that you want to conduct,including a description of the initiating event that is indicative of a process failure. LOPArecords store details of the risk assessment that is determined after conducting the Layerof Protection Analysis.

l SIF Common Cause Failure: Stores the details of a failure that affects the operation ofmultiple instrumented functions.

l Instrumented Function: Indicates that if both the instrumented functions represented bythe two records are in theirsafe stateat the same time, a hazardous event may occur.

Note: The SIS Proof Test and SIS Proof Test Template families also appear in other portionsof the datamodel.

Protective Instrument Loop Family Is the Predecessor


Protective Instrument Loop Family Is the PredecessorThe following image shows the relationships in which the Protective Instrument Loop family par-ticipates as the predecessor.

Protective Instrument Loop records store summary information about all the records that arelinked to that record. The Protective Instrument Loop record combined with all the records thatare linked to that recordmake up the protective instrument loop.

Components of an SIL Analysis


Components of an SIL AnalysisA Safety Integrity Level (SIL) Analysis lets you assess the safety instrumented systems in yourfacility to ensure that they are adequately safeguarding your equipment, locations, and pro-cesses. An SIL Analysis consists of an SIL Analysis record and ALL the records that are linked tothat record both directly and indirectly. SIL Analysis records store overview information about theanalysis that you are conducting, including the start and end dates for the analysis. The followingimage illustrates the records that are linked directly to an SIL Analysis record.

You can see that records in the following families are linked directly to an SIL Analysis record:

l Human Resource: Stores information about the people who will participate in the analysisas SIL Analysis teammembers.

l Reference Document: Stores the URL path to a document that is external to MeridiumAPMand contains reference information related to the SIL Analysis.

l Instrumented Function: Stores information about the instrumented functions of the safetyinstrumented system that you are analyzing.

l Safety Instrumented System: Stores information about the safety instrumented systemsthat you are analyzing.

Additionally, Safety Instrumented System records and Instrumented Function records are linkedto one another through the Has IF relationship. In addition to the relationships described above,an SIL Analysis includes records in the families that are linked to Safety Instrumented Systemrecords and Instrumented Function records. For more information on these records, see the datamodel image.

When you conduct an SIL Analysis, you will:

l Assess the level of safety integrity per instrumented function, using theMeridiumAPMRiskMatrix interface or via a Layer of Protection Analysis (LOPA). The overall safety integ-rity level (SIL) for a safety instrumented systemwill be calculated automatically by theMeridiumAPM system based upon the defined risks.

l Validate the safety integrity level (SIL) of a safety instrumented system using the SIL Val-idation tool, which lets you create a diagram of the protective instrument loops (PIL) thatmake up the safety instrumented system and calculate the ability of a protective instrumentloop tomeet the required safety integrity level (SIL) for that process. TheMeridiumAPM

Components of an SIL Analysis


system uses equations defined by IEC 61508 to calculate the probability of failure onDemand average (PFD Avg) or probability of failure per hour (PFH).

l Determine whether further safeguarding is necessary, based upon the safety integrity levelmaintained by those safety instrumented systems.

The SIS Management Workflow


The SIS Management WorkflowThe first step in creating an SIL Analysis is to create an SIL Analysis record. After you have cre-ated the SIL Analysis record on the SIL Analysis Definition page, you can complete the SIL Ana-lysis by:

l Defining the SIL Analysis team.

l Managing Reference Document records.

l Defining the Safety Instrumented System records.

l Defining Instrumented Function records.

l Assess risk, which includes:n Using a RiskMatrix.

n Conducting a Layer of Protection Analysis (LOPA)

l Manage Risk Assessment Recommendation records.

l Validate the safety integrity level (SIL) of the safety instrumented systems bymanaging pro-tective instrument loops (PILs).

l Manage SIS Trip Report records.

l Manage Inspection Task records.

l Manage Validation Failure Rate Reference data.

SIL Analysis State Configuration


SIL Analysis State ConfigurationThis topic describes attributes of the State Configuration that is defined for the SIL Analysis familyin the baselineMeridiumAPMdatabase.

States and Operations

The following State Configuration is defined for the SIL Analysis family. In this image, a box rep-resents a state, and an arrow represents an operation. The state to which an arrow points rep-resents a successor state.



Initial State

The Planning state is the initial state of all new SIL Analysis records.

Datasheet Configuration



By default, states and operationswill appear on the datasheet when you are viewing an SIL Ana-lysis record in SIS Management, the RecordManager, or the Bulk Data Form.

Reserved States and Operations

The following table lists the baseline states and operations and indicateswhich of these statesand operations are reserved. You cannot remove or modify reserved states or operation. Youcan, however, add your own states and operations to the State Configuration.

States

State Is Reserved?

Planning Yes

Active Yes

Review Yes

Pending Approval Yes

Complete Yes

Operations

Operation Is Reserved?

Begin Yes

Propose Yes

Submit Yes

Accept Yes

Reject Yes

Modify/Reassess Yes

State Configuration Roles

By default, theMI SIS Administrator andMI SIS Engineer State Configuration Roles areassigned to all states in the SIL Analysis State Configuration. You can assign State ConfigurationRoles to any state. In addition, for each state, the Require a specific user to be assigned to astate check box is selected.

Protective Instrument Loop State Configuration


Protective Instrument Loop State ConfigurationThis topic describes attributes of the State Configuration that is defined for the Protective Instru-ment Loop family in the baselineMeridiumAPMdatabase.


The following State Configuration is defined for the Protective Instrument Loop family. In thisimage, a box represents a state, and an arrow represents an operation. The state to which anarrow points represents a successor state.



Initial State

TheDesign state is the initial state of all new Protective Instrument Loop records.




By default, states and operationswill appear on the datasheet when you are viewing a ProtectiveInstrument Loop record in SIS Management, the RecordManager, or the Bulk Data Form.



States

State Is Reserved?

Design Yes

Pending Approval Yes

Approval Yes

In Service Yes

Out of Service Yes

Operations


Submit Yes

Accepted Yes

Rejected Yes

Commissioned Yes

Modify Yes

Resinstate Yes


The following table lists the baseline states and indicateswhich State Configuration Roles areassigned to each state.

State Security Groups

Design MI SIS Administrator

MI SIS Engineer




Pending Approval MI SIS Administrator

MI SIS Engineer

Approval MI SIS Administrator

MI SIS Engineer

In Service MI SIS Administrator

MI SIS Engineer

Out of Service MI SIS Administrator

MI SIS Engineer

In addition, for each state, the Require a specific user to be assigned to a state check box isselected.

SIS Trip Report State Configuration


SIS Trip Report State ConfigurationThis topic describes attributes of the State Configuration that is defined for the SIS Trip Reportfamily in the baselineMeridiumAPMdatabase.


The following State Configuration is defined for the SI Trip Report family. In this image, a box rep-resents a state, and an arrow represents an operation. The state to which an arrow points rep-resents a successor state.

Initial State

The Active state is the initial state of all new SIS Trip Report records.




By default, states and operationswill appear on the datasheet when you are viewing an SIS TripReport record in SIS Management, the RecordManager, or the Bulk Data Form.



States

State Is Reserved?

Active No

Review No

Pending Approval No

Complete No

Operations


Propose No

Submit No

Accept No

Reject No

Modify/Reassess No


The following table lists the baseline states and indicateswhich State Configuration Roles areassigned to each state.


Active MI SIS Administrator

MI SIS Engineer

Review MI SIS Administrator

MI SIS Engineer




Pending Approval MI SIS Administrator

MI SIS Engineer

Complete MI SIS Administrator

MI SIS Engineer

In addition, for each state, the Require a specific user to be assigned to a state check box isselected.

Integration with Hazards Analysis


Integration with Hazards AnalysisIn the Hazards Analysismodule, you can conduct a Hazards Analysis to identify hazards asso-ciated with a process, and then assess the risks associated with those hazards. In the SIS Man-agement module, you can use a SIL Analysis to assess the risks associated with theinstrumented functions in a safety instrumented system to determine whether it requires addi-tional safeguarding.

After you assess risk in the Hazards Analysismodule, you can apply that risk assessment to anInstrumented Function record in an SIL Analysis in the SIS Management module. You can usethe Risk Assessment record that you created in a Hazards Analysis to calculate the safety integ-rity level (SIL) for your Instrumented Function record without having to recreate the assessmentin the SIS Management module.

To take advantage of this functionality:

l TheHazards Analysis licensemust be active.

l Youmust assign at least view permissions to the Hazards Analysis family to any SIS Man-agement Security Groups that should have access to integration with Hazards Analysis.

l Youmust have full permissions to the HasHAZOP Reference relationship family.

Note: All SIS Management and Hazards Analysis Security Groups have full permissionsto the HasHAZOP Reference family by default, with the exception of theMI HA MemberSecurity Group.

Accessing the SIS Management Start Page


Accessing the SIS Management Start PageTo access the SIS Management Start Page:

l On theMeridiumAPMFrameworkmainmenu, clickGo To, point to Asset Safety, andthen click SIS Management.

The SIS ManagementStart Page appears.

Aspects of the SIS Management Start Page


Aspects of the SIS Management Start PageThe SIS Management Start Page serves as a starting point for tasks that you can perform usingthe SIS Management module.

The SIS Management Start Page contains the following links:

l SIL Analysis: Displays the SIL AnalysisSearch page, where you can create andmanageSIL Analysis records.

l SIL Validation: Displays the Protective Loop Search page, where you can search for andopen existing Protective Instrument Loop records.

l SIL Validation Template: Displays the Protective Loop Template Search page, whereyou can create andmanage Protective Instrument Loop Template records.

l SIS Trip Report: Displays the SIS Trip Report Search page, where you can create andmanage SIS Trip Report records.

l Manage Tasks: Displays theTask Listpage, where you can view andmanage the Taskrecords that are associated with all SIL Analyses.

l Manage Recommendations: Displays theRecommendation Management page, whereyou can view andmanage a list of Risk Assessment Recommendation records that areassociated with all SIL Analyses.

l Manage Validation Failure Rate Reference Data: Displays the Sensor Reference DataSearch page, where you can create andmanage records in the Protective InstrumentLoop Element families.

l Perform Administrative Tasks: Displays the SIS Management Administration page,where you can perform administrative tasks for the SIS Management module. This linkappears only if you are logged in as a Super User or amember of theMI SIS AdministratorSecurity Group.

First-Time Deployment Workflow


First-Time Deployment WorkflowDeploying and configuring SIS Management for the first time includes completingmultiple steps,which are outlined in the table in this topic. The steps in this section of the documentation provideall the information that you need to deploy and configure the SIS Management module on top ofthe basicMeridiumAPM system architecture.

Whether a step is required or optional is indicated in the Required/Optional cell. Steps aremarked asRequired if youmust perform the steps to take advantage of SIS Management func-tionality.

The person responsible for completing each taskmay vary within your organization.We recom-mend, however, that the steps be performed in relatively the same order in which they are listedin the table.

Step Task Required/Optional Notes

1 Review the SIS Managementdatamodel to determine whichrelationship definitions you willneed tomodify to include yourcustom equipment or locationfamilies. Modify any rela-tionship definitions as neededvia ConfigurationManager.

Optional This task is necessary only ifyou store equipment or loc-ation information in familiesother than the baseline Equip-ment and Functional Locationfamilies.

2 Assign the desired SecurityUsers to one or more SIS Man-agement Security Groups inConfigurationManager.

Required Users will not be able toaccess SIS Managementunless they have permissionsto the SIS Management fam-ilies.

3 Manage the queries whose res-ults will appear throughout theSIS Management module.

Required None

4 Specify the whether Equipmentor Functional Location recordswill be used when integratingwith the Asset StrategyMan-agement (ASM) module.

Required None

5 Import data from an Exida pro-ject file.

Optional This is necessary only if youwant to create SIL Analysesusing an Exida project file.

6 Export data from an Exida pro-ject file.

Optional None

First-Time Deployment Workflow


Step Task Required/Optional Notes

7 Manage the types of inde-pendent layers of protectionthat will be used to populateIndependent Layer of Pro-tection records.

Required None

8 Activate the Hazards Analysislicense in ConfigurationMan-ager.

Optional This is necessary only if youwant to take advantage of theintegration between the Haz-ards Analysismodule andSIS Management.

9 Assign at least view per-missions to the Hazards Ana-lysis family to SIS ManagementSecurity Groups in Con-figurationManager.

Optional This is necessary only forSecurity Groups that will beused in the integrationbetween the Hazards Ana-lysismodule and SIS Man-agement.

Upgrade or Update SIS Management to 3.6.1.0.0


Upgrade or Update SIS Management to 3.6.1.0.0The following tables list the steps that are required to update or upgrade SIS Management to3.6.1.0.0. These steps assume that you have completed the steps for upgrading the componentsin the basicMeridiumAPM system architecture.

Upgrade from any version V3.6.0.0.0 through V3.6.0.12.3

Ste-p

TaskRequired/Op-tional

Notes

1 Activate the Hazards Analysis license via Con-figurationManager.

Optional This isnecessaryonly if youwant totake advant-age of theintegrationbetweenthe Haz-ards Ana-lysismodule andSIS Man-agement.

2 Assign at least view permissions to the Hazards Ana-lysis family to SIS Management Security Groups inConfigurationManager.

Optional This isnecessaryonly forSecurityGroups thatwill be usedin the integ-rationbetweenthe Haz-ards Ana-lysismodule andSIS Man-agement.



Ste-p


Notes

3 Verify successful completion of the Protective LoopUtility after you have completed your databaseupgrade.

A. Review the log 93_Pro-tectiveLoopUtility.cmd.log found in your<root>:\Program Files\Meridi-um\Client\100.0.0.0.0\DBUpgrade\logs dir-ectory.

B. Youmust manually click on Calculate on theCommon Tasks Menu for each existing Pro-tective Instrument Loop.

Required This step isrequired ifyou havepreviouslyimporteddata froman exida™project file.

Upgrade from any version V3.5.1.0.0 through V3.5.1.12.0

Ste-p


Notes





Ste-p


Notes







Upgrade from any version V3.5.0 SP1 LP through V3.5.0.1.9.0



Ste-p


Notes







Ste-p


Notes





Upgrade from any version V3.5.0 through V3.5.0.0.7.1

Ste-p


Notes

1 Activate the Hazards Analysis licensevia Con-figurationManager.




Ste-p


Notes







Upgrade from any version V3.4.5 through V3.4.5.0.1.4



Ste-p


Notes





SIS Management Security Groups


SIS Management Security GroupsThe following Security Groups are provided for use with SIS Management:

l MI SIS Administrator

l MI SIS Engineer

l MI SIS User

These groups are intended to support the threemain types of users who will use Hazards Ana-lysis. Each of these groups has privileges assigned to it by default. The baseline family-level priv-ileges are summarized in the following table.

Family MI SIS Admin-istrator MI SIS Engineer MI SIS User

Entity Families

Asset Criticality Analysis View None None

Asset Criticality AnalysisSystem

View None None

Consequence View, Update,Insert, Delete

View View

ConsequenceModifier View, Update,Insert, Delete

View, Update,Insert, Delete

View

Equipment View View View

Functional Location View View View

Functional Systems View, Update,Insert, Delete


View

Functional Test Detail View, Update,Insert, Delete



HumanResource View, Update,Insert, Delete


View

Independent Layer of Pro-tection



View

Instrumented Function View, Update,Insert, Delete


View

IPL Type View, Update,Insert, Delete


View




LOPA View, Update,Insert, Delete


View

Notification View, Update,Insert, Delete


None

Probability View, Update,Insert, Delete

View View

Protection Level View, Update,Insert, Delete

View, Insert View

Protective Instrument LoopElement



View

Proven In Use Justification View, Update,Insert, Delete


View

RBI Components View, Update,Insert, Delete


None

Reference Document View, Update,Insert, Delete


View

Risk View, Update,Insert, Delete


View

Risk Assessment View, Update,Insert, Delete


View

Risk Assessment Recom-mendation



View

Risk Category View, Update,Insert, Delete


View

RiskMatrix View, Update,Insert, Delete

View View

Risk Threshold View, Update,Insert, Delete

View View

Safety Instrumented Sys-tem



View

Safety Integrity Level View, Update,Insert, Delete

View View




SIF CommonCause Failure View, Update,Insert, Delete


View

SIL Analysis View, Update,Insert, Delete


View

SIL Threshold View, Update,Insert, Delete

View View

SIS Proof Test View, Update,Insert, Delete



SIS Proof Test Template View, Update,Insert, Delete


View

SIS Proof Test TemplateDetail



View

SIS Trip Report View, Update,Insert, Delete


View

SIS Trip Report Detail View, Update,Insert, Delete


View

Site Reference View View View

Task View, Update,Insert, Delete


View

Time Based Inspection Inter-val

View View View

Time Based Inspection Set-ting

View View View

Relationship Families

Analysis HasHumanResource



View

Asset Criticality AnalysisHas System

View None None

Equipment Has Equipment View View View

Functional Location HasEquipment

View View View




Functional Location HasFunctional Location

View View View

HasConsequenceModifier View, Update,Insert, Delete


View

HasEquipment View, Update,Insert, Delete


View

Has Functional Location View, Update,Insert, Delete


View

Has Functional Test View, Update,Insert, Delete



Has Functional Test Detail View, Update,Insert, Delete



HasHazard Event View, Update,Insert, Delete


View

HasHAZOP Reference View, Update,Insert, Delete



Has IF View, Update,Insert, Delete


View

Has Independent ProtectionLayer



View

Has Instrumented FunctionRevision



View

Has Instrument Loop View, Update,Insert, Delete


View

Has Instrument Loop Revi-sion



View

Has LOPA View, Update,Insert, Delete


View

Has LOPA Revision View, Update,Insert, Delete


View




Has PIL Device View, Update,Insert, Delete


View

HasPIL Device Revision View, Update,Insert, Delete


View

HasPIL Group View, Update,Insert, Delete


View

HasPIL Group Revision View, Update,Insert, Delete


View

HasPIL Subsystem View, Update,Insert, Delete


View

HasPIL SubsystemRevi-sion



View

HasPIL System View, Update,Insert, Delete


View

HasPIL SystemRevision View, Update,Insert, Delete


View

HasProven In Use Jus-tification



View

HasRBI Components View, Update,Insert, Delete


None

HasRecommendations View, Update,Insert, Delete


View

HasReference Documents View, Update,Insert, Delete


View, Insert

HasReference Values View, Update,Insert, Delete

View View

Has Risk View, Update,Insert, Delete


View




HasRisk Category View, Update,Insert, Delete


View

HasRiskMatrix View, Update,Insert, Delete


View

HasSIF CommonCauseFailures



View

HasSIS Analysis Revision View, Update,Insert, Delete


View

HasSIS Revision View, Update,Insert, Delete


View

HasSIS Trip Report Detail View, Update,Insert, Delete


View

HasSite Reference View, Update,Insert, Delete


View

Has TaskHistory View, Insert View, Insert View, Insert

Has Tasks View, Update,Insert, Delete


View

Has TaskRevision View View View

Has Template Detail View, Update,Insert, Delete


View

Has Templates View, Update,Insert, Delete


View

Has Time Based InspectionInterval

View View View

MitigatesRisk View, Update,Insert, Delete


View

WasPromoted to ASMEle-ment



View

Accessing the SIS Management Administration Page


Accessing the SIS Management Administration PageAccessing the SIS Management Administration page:

l On the SIS Management Start Page, click the Perform Administrative Tasks link.

The SIS Management Administration page appears.

Aspects of the SIS Management Administration Page


Aspects of the SIS Management Administration PageThe SIS Management Administration page contains the following sections:

l Manage Queries: Contains the following options:n SIL Analysis Search Query: Specifies the query whose results will appear on the SIL

Analysis Search page. The query \\Public\Meridium\Modules\SIS Man-agement\Queries\SIL_Analysis_Search is specified for this setting by default.

n Protective Loop Search Query: Specifies the query whose results will appear on the Pro-tective Loop Search page. The query \\Public\Meridium\Modules\SIS Man-agement\Queries\Safety_Loop_Search is specified for this setting by default.

n Protective Loop Template Search Query: Specifies the query whose results will appearon the Protective Loop Template Search page. The query \\Public\Meridi-um\Modules\SIS Management\Queries\Safety_Loop_Template_Search is specified forthis setting by default.

n Sensor Reference Data Query: Specifies the query whose results will appear on theSensor Reference Data Search page. The query \\Public\Meridium\Modules\SIS Man-agement\Queries\Sensor_Reference_Data_Search is specified for this setting by default.

n Logic Solver Reference Data Query: Specifies the query whose results will appear onthe Logic Solver Reference Data Search page. The query \\Public\Meridi-um\Modules\SIS Management\Queries\Logic_Solver_Reference_Data_Search is spe-cified for this setting by default.

n Final Element Reference Data Query: Specifies the query whose results will appear onthe Final Element Reference Data Search page. The query \\Public\Meridi-um\Modules\SIS Management\Queries\Final_Element_Reference_Data_Search is spe-cified for this setting by default.

n IF Protective Loop Search Query: Specifies the query whose results will appear on theProtective Loop Search page when you search for protective instrument loops associatedwith an instrumented function. The query \\Public\Meridium\Modules\SIS Man-agement\Queries\IF_Safety_Loop_Search is specified for this setting by default.

n SIS Trip Report Search Query: Specifies the query whose results will appear on the SISTrip Report Searchpage. The query \\Public\Meridium\Modules\SIS Man-agement\Queries\SIS_Trip_Report_Search is specified for this setting by default.

For the preceding options, you can specify a different query by clicking the button that

appears to the right of each option. This button displays the Select Query dialog box,where you can navigate to the desired query.

l Import/Export Exida Projects: Displays the textImport fromExida ProjectandExport toExida Projectwith corresponding buttons, which appear to the right of these labels:

n Import: Displays the Import Builder, which takes you step-by-step through importing datafrom an Exida project file stored on your computer. When you import data from an Exidaproject file, that data is transferred intoMeridiumAPM records and creates an SIL Analysisor updates an existing SIL Analysis.

n Export: Displays the Export Builder, takes you step-by-step through exporting SIL Ana-lysis data from theMeridiumAPMdatabase to an Exida project file stored on your com-puter.

l ASM Integration: Using SIS Management, you can promote to ASM Instrumented Func-tion records, which contain an Equipment ID and Functional Location ID field. The ASMIntegrationsection contains the text Asset Source Field and the following options that youcan use to specify which field in the Instrumented Function record that theMeridiumAPMsystemwill use to promote to ASM the corresponding record that represents the equip-ment or location:

n Equipment:Specifies that theMeridiumAPM systemwill promote to ASM the Equipmentrecord that is specified in the Equipment ID field in the Instrumented Function record. Thisis the default option.

n Functional Location: Specifies that theMeridiumAPM systemwill promote to ASM theFunctional Location record that is specified in the Functional Location ID field in the Instru-mented Function record.

At the bottom of the SIS Management Administration page, the following options appear:

l Save: Saves the current administrative settings.

l Exit: Displays the SIS Management Start Page. If you have unsaved changes on thepage, a dialog box appears first, asking if you want to save your changes.

The SIS Management Administration page contains one taskmenuCommon Tasks.

Common Tasks Menu


Common Tasks Menu

TheCommon Tasks menu on the SIS Management Administration page contains the fol-lowing options:

l Save: Saves the current administrative settings.

l Open Analysis: This link is disabled.

l Delete:This link is disabled.

l Send To: Displays a submenuwith options that let youprovide a link to the current page onyour desktop (create shortcut), in an email message, or on a HomePage.

l Help: Displays the context-sensitive help topic for theSIS Management Administrationpage.

Specifying a Different Query on SIS Management Administration Page


Specifying a Different Query on SIS ManagementAdministration PageIn theManageQueries section on the SIS Management Administration page, you can specifythe Catalog path to a query other than the one that is currently displayed.

To specify a different query on the SIS Management Administration Page:

1. Access the SIS Management Administration page.

2. To the right of the text box that corresponds to the query that you want to change, click thebutton.

The Select Query dialog box appears.

3. Navigate to the desired query.

4. Click the Open button.

The Select Query dialog box closes, and the name of the query that you selected appearsin the corresponding text box.

5. On the Common Tasks menu, click the Save link.

Your changes are saved.

Specifying the Asset Source for ASM Integration


Specifying the Asset Source for ASM IntegrationWhen you specify the Asset Source for ASM integration, you are specifying which relationshipfamily you are using to relate Instrumented Function records representing the desired equipmentor location. You will need to specify whether this relationship is Safety Analysis Has Equipment orHas Functional Location. If you are using both relationships, you will need to specify which oneyou want to use to promote an asset to ASMwhen the Instrumented Function to which it is linkedis promoted.

To specify the asset source for ASM integration:

1. Access the SIS Management Administration page.

2. In the ASM Integration section, to the right of the Asset Source field label, select the optionthat corresponds to the relationship family that you are using.

3. Click the Save button.


About Importing Data from an Exida Project File


About Importing Data from an Exida Project Fileexida™ is a software solution, where you can store information about the systems in a facility.When you import data from an exida™ project file on your computer, you are importing inform-ation to automatically create Instrumented Function records in theMeridiumAPMdatabase.Those records are also automatically linked to the SIL Analysis to which they belong. The inform-ation in this section of the documentation provides details on using the Import Builder on the SISManagement Administration page to import data from a file on your computer into theMeridiumAPMdatabase.

When you use the Import Builder to import data from an exida™ file, you will have two optionsthat you can use to do so:

l Create a new SIL Analysis for the data.

l Append the data to an existing SIL Analysis.

Depending on themethod that you select, the screens that you see in the builder will change.This section of the documentation provides instructions for using the Import Builder to:

l Accessing theOptions screen, where you can select the import method that you want touse.

l Creating a new SIL Analysis for the imported data.

l Appending the imported data to an existing SIL Analysis.

Accessing the Options Screen


Accessing the Options ScreenTo import data from an exida™ project file:

1. On the SIS Management Administration page, in the Import/Export Exida Projects sec-tion, click the Import button.

The Import Builder appears, displaying theWelcome screen.

2. Click the Next button.

The Specify exSILentia file screen appears.

3. In the Path text box, type the path to the file that you want to import.

-or-

Click the button to search for the file on your computer. These instructions assume thatyou want to search for the file.

The Import dialog box appears.

4. Navigate to the desired exSILentia file, and click the Open button.

The path to the selected file appears in the Path text box.


The Select Instrumented Functions screen appears, displaying a list of InstrumentedFunction records that exist in the specified file.



6. Select the rows containing the Instrumented Function records that you want to import.


TheOptions screen appears, displaying the options that you can use to import the Instru-mented Functions.

At this point, you can follow the procedure for importing data via the desiredmethod:

l Creating a new analysis for the imported data.



l Appending the imported data to an existing analysis.

Creating a New Analysis for the Imported Data


Creating a New Analysis for the Imported DataThe following instructions provide details on using theOptions screen and successive screens inthe Import Builder to import data from an exida™ project file and create a new analysis for thedata. For details on importing data from an exida™ project file and appending it to an existing ana-lysis, see the instructions for appending imported data to an existing SIL Analysis.

To create a new analysis for the imported data:

1. Access theOptions screen in the Import Builder.

2. Select the Create a New Analysis option.

The Next button is disabled.

3. Click the Finish button.

A new blank SIL Analysis record appears in a new window.

4. Provide values in the fields as desired. Note that the Analysis ID field is required.

5. ClickOK.

Creating a New Analysis for the Imported Data


The SIL Analysis record closes, and the Progress dialog box appears, displaying the pro-gress of the import process.

When the import is finished, the Confirmation dialog box appears, indicating that the selec-ted Instrumented Function recordswere imported successfully.

Note:If the import process is unsuccessful, a message will appear, indicating that the pro-cesswas not successful. If you see thismessage, you will need to correct any issues,and then try again.

6. On the Confirmation dialog box, clickOK.

The Import Builder closes, revealing the SIS Management Administration page. At thispoint, you can view the new SIL Analysis.

ŒHint: On the Confirmation dialog box, you can click the Detail>> button to view a listof IDs for the Instrumented Function records that were imported.

Appending the Imported Data to an Existing Analysis


Appending the Imported Data to an Existing AnalysisThe following instructions provide details on using theOptions screen and successive screens inthe Import Builder to import data from an exida™ project file and append that data to an existingSIL Analysis. For details on importing data from an exida™ project file and creating a new analysisfor that data, see the instructions for creating a new SIL Analysis for imported data.

To append the imported data to an existing analysis:

1. Access theOptions screen in the Import Builder.

2. Select the Append to Existing Analysis option.

The Finish button is disabled.


The Select an Analysis screen appears and displays a query prompt for the record stateand SIL Analysis Owner of the desired SIL Analysis record.

4. Select the desired search criteria, and then clickOK.

-or-

Accept the default All options, and click OK.

The Select an Analysis screen is revealed, and the query results are displayed in the grid.

Appending the Imported Data to an Existing Analysis


5. In the grid, select the row containing the SIL Analysis record to which you want to link theInstrumented Function records.


The Progress dialog box appears, displaying the progress of the import process.


Note: If the import process is unsuccessful, a message will appear, indicating that the pro-cesswas not successful. If you see thismessage, you will need to correct any issues,and then try again.




About Exporting Data to an Exida Project File


About Exporting Data to an Exida Project FileWhen you export data from theMeridiumAPMdatabase to a file on your computer, you areexporting information from Instrumented Function records an exida™ project file. The informationin this section of the documentation provides details on using the Export Builder on the SIS Man-agement Administration page to export data from theMeridiumAPMdatabase to an exida™ pro-ject file on your computer.

Exporting Data to an Exida Project File


Exporting Data to an Exida Project FileThe following instructions provide details on using the Export Builder to export InstrumentedFunction records and Protective Instrument Loop records to an exida™ project file on your com-puter.

To export data to an exida project file:

1. On the SIS Management Administration page, in the Import/Export Exida Projects sec-tion, click the Export button.

The Export Builder appears, displaying theWelcome screen.


The Select SIL Analysis screen appears and displays a query prompt for the record stateof the SIL Analysis whose Instrumented Function records you want to export.

3. In the State list, select the state that corresponds to the record state of the SIL Analysiswhose Instrumented Function records you want to export.

-or-

Accept the default option, All.

4. ClickOK.

The Select SIL Analysis screen appears, and the query results are displayed in the grid.



5. In the grid, select the row that contains the SIL Analysis record whose Instrumented Func-tion records you want to export.


The Select Instrumented Function screen appears, displaying a list of Instrumented Func-tion records that are linked to the SIL Analysis record that you selected on the Select SILAnalysis screen.

7. In the grid, select the rows that contains the Instrumented Function records that you wantto export.


The Select Protective Instrument Loop screen appears, displaying the list of ProtectiveInstrument Loop records that are linked to the Instrumented Function records that youselected on the Select Instrumented Function screen.



9. In the list, select the rows containing the Protective Instrument Loop records that you wantto export.


The Specify Output File screen appears.



11. In the Path text box, type the file path to the desired location.

-or-

Click the button to search for the desired file. These instructions assume that you wantto search for the file.

The Export dialog box appears, where you can navigate to the desired exSILential file.

12. Navigate to the desired file on your computer, and then click the Save button.

The specified file path appears in the Path text box.


The Progress dialog box appears, displaying the progress of the export process.

When the export is finished, the Confirmation dialog box appears, indicating that the selec-ted recordswere exported successfully.

Note: If the export process is unsuccessful, a message will appear, indicating that the pro-cesswas not successful. If you see thismessage, you will need to correct any issues,and then try again.


The Progress dialog box appears, displaying the progress of the import process.


Note: If the import process is unsuccessful, a message will appear, indicating that the pro-cesswas not successful. If you see thismessage, you will need to correct any issues,and then try again.




Export Builder closes, revealing the SIS Management Administration page.

ŒHint: On the Confirmation dialog box, you can click the Detail>> button to view a listof IDs for the Instrumented Function records that were exported.

About Managing the Types of Independent Layers of Protection


About Managing the Types of Independent Layers ofProtectionTomanage the types of independent layers of protection that will be used to populate Independ-ent Layer of Protection records, you will need to:

1. Modify the values in the Default Value fields in the baseline IPL Type records.

2. Define additional IPL types.

About Independent Layer of Protection Types


About Independent Layer of Protection TypesAn independent layer of protection is a system, action, or item that mitigates the risk associatedwith an instrumented function. In SIS Management, details on independent layers of protectionare stored in Independent Layer of Protection records.When you conduct a Layer of ProtectionAnalysis (LOPA) to assess risk for a given instrumented function, you will create one Independ-ent Layer of Protection record per independent layer of protection.When you do so, you will needto select in the Type list the type of independent layer of protection that the record represents.Throughout the documentation, we refer to the values in the Type list as IPL types.

The IPL type that you select in the Independent Layer of Protection record is used to determinethe probability of failure data (PFD) value that is associated with that type of independent layer ofprotection. The PFD value is stored in the PFD field in the Independent Layer of Protectionrecord and used to calculate the overall risk associated with a given instrumented function. Onthe Independent Layer of Protection datasheet, the Type list contains the IPL types that aredefined in theMeridiumAPMdatabase in the form of records belonging to the IPL Type family.

The IPL Type family is a subfamily of theMeridiumReference Tables family and is not related toany families in the SIS Management datamodel. You can think of IPL Type records as templatesthat you can use to define Independent Layer of Protection records. The following list containsthe Record IDs for the baseline IPL Type records that are provided in theMeridiumAPMdata-base:

l Control loop

l Human performance (trained, no stress)

l Human performance (under stress)

l Operator response to alarms

l Vessel pressure rating abovemax challenge

The baseline IPL Type records contain a value in the Default Value field. As part of the admin-istrative steps for the SIS Management module, you will need to review andmodify these defaultvalues. The value in the Default Value field is used to populate the PFD field in the IndependentLayer of Protection record.

For each baseline IPL Type record, a corresponding SystemCode is provided in the LOPA IPLTYPE (MI_IPL_TYPE) SystemCode Table. You can use these SystemCodes to translate thebaseline IPL types, if desired.

In the Type list, the following information is displayed for each IPL type:

<IPL Type ID> (<Default Value or Lower Boundary> - <Upper Boundary>)

...where:

l <IPL Type ID> is the value stored in the IPL Type ID field in the corresponding IPL Typerecord.

l <Default Value>is a numeric value that is stored in the Default Value field in the cor-responding IPL Type record.

About Independent Layer of Protection Types


l <Lower Boundary> is a numeric value that is stored in the Lower Boundary field in the cor-responding IPL Type record.

l <Upper Boundary> is a numeric value that is stored in the Upper Boundary field in the cor-responding IPL Type record.

Together, the values stored in the Lower Boundary and Upper Boundary fields define a PFDrange for that IPL type.

For example, the baseline IPL typeControl Loopis displayed in the Type list asControl Loop (.01),where.01is the value stored in the Default Value field in the corresponding IPL Type record. Like-wise, the baseline IPL typeHuman performance (trained, no stress)is displayed in the Type listasHuman performance (trained, no stress) (0.0001 - 0.01), where0.0001 - 0.01is the PFD rangedefined for that IPL type. Specifically:

l 0.0001 is the value stored in the Lower Boundary field in the corresponding IPL Typerecord.

-and-

l 0.01is the value stored in the Upper Boundary field in the corresponding IPL Type record.

In addition to the baseline IPL types, you can define additional IPL types that will appear in theType list on the Independent Layer of Protection datasheet.

Modifying the Default Values in the Baseline IPL Type Records


Modifying the Default Values in the Baseline IPL TypeRecordsThe following instructions provide details onmodifying the baseline IPL Type records to changethe values stored in the Default Value fields in these records.

To modify the value in the Default Value field in a baseline IPL Type record:

1. Open the baseline IPL Type record whose default value you want to modify.

2. In the Default Value field, modify the value as desired.

3. On the datasheet toolbar, click the Save button.

The record is saved.

Defining Additional IPL Types


Defining Additional IPL TypesIf desired, you can define additional IPL types that will appear in the Type list on the IndependentLayer of Protection datasheet. To define additional IPL types, you will need to create a newrecord in the IPL Type family, using the RecordManager. To do so, youmust be logged in as amember of theMI SIS Administrator or MI SIS Engineer Security Group. After you save therecord, the IPL type will be available in the Type list on the Independent Layer of Protection data-sheet.

Remember that the values you enter in the IPL Type record define a type of independent layer ofprotection and will be used to determine the PFD value in Independent Layer of Protectionrecords. The following table provides a description of the fields that appear on the IPL Type data-sheet and how they effect Independent Layer of Protection recordswhen you select an IPL Typerecord in the Type list. You should use this table to determine how to define additional IPL types,based upon how the valueswill be used by Independent Layer of Protection records.

IPL TypeField

IPL Type Field Descrip-tion

Effect on Independent Layer of ProtectionRecords

Default Value

A numeric value rep-resenting the PFD valuethat is associated with theIPL type.

This field is required.

The PFD field will be populated automatically withthis value.

Description A description of the IPLtype.

The Description field is populated automaticallywith this value.

IPL Type ID

An ID for the IPL type.This value is used toidentify the IPL Typerecord.

This value will be displayed in the Type list, alongwith the:

l Value in the Default Value field.

-or-

l Range defined by the values in the LowerBoundary and Upper Boundary fields.

The value that is displayed here depends uponwhether the Is Fixed Value check box is selectedin the IPL Type record.



IPL TypeField



Is FixedValue

A check box that indic-ates whether the IPL typeis associated with a fixedPFD value or a PFDrange.

l If the Is FixedValue check box isselected, theLower Boundaryand Upper Bound-ary cells are dis-abled, and theDefault Value cellis required.

l If theIs FixedValue check box isclear, the DefaultValue cell is dis-abled, and theLower Boundaryand Upper Bound-arycells arerequired.

If the Is Fixed Value check box is selected in theIPL Type record:

l The PFD field will be required, and thevalue that you enter in the PFD cell must fallwithin the PFD range defined in the IPLType record.

If the value that you enter in the PFD celldoes not fall within the PFD range, ames-sage will appear, indicating that youmustenter a value that falls within the specifiedrange.

l In the Type list, the IPL Type ID will beappended with the values stored in theLower Boundary and Upper Boundaryfields in the IPL Type record, which definethe PFD range.

If the Is Fixed Value check box is cleared in theIPL Type record:

l The PFD field will be populated auto-matically with the value stored in the DefaultValue field in the IPL Type record.

l In theType list, the IPL Type ID will beappended with the value stored in theDefault Value field in the IPL Type record.

Lower Bound-ary

A numeric value rep-resenting the lowestvalue in the PFD rangeassociated with an IPLtype.

Together, this value andthe value in the UpperBoundary field define thePFD range for the IPLtype.

If the Is Fixed Valuecheck box is selected, thisfield is disabled.

If the Is Fixed Value check box is selected in theIPL Type record, this value will be displayed in theType list, along with the following values stored inthe IPL Type record:

l IPL Type ID

l Upper Boundary

In addition, when you enter a value in the PFDcell, theMeridiumAPM systemwill use this valueto determine if the PFD value falls within thedefined PFD range. If the value does not fall withinthe PFD range, amessage will appear, indicatingthat youmust enter a value that falls within the spe-cified range.



IPL TypeField



Upper Bound-ary

A numeric value rep-resenting the highestvalue in the PFD rangeassociated with an IPLtype.

Together, this value andthe value in the LowerBoundary field define thePFD range for the IPLtype.

If the Is Fixed Valuecheck box is selected, thisfield is disabled.

If the Is Fixed Value check box is selected in theIPL Type record, this value will be displayed in theType list, along with the following values stored inthe IPL Type record:

l IPL Type ID

l Lower Boundary

In addition, when you enter a value in the PFDcell, theMeridiumAPM systemwill use this valueto determine if the PFD value falls within thedefined PFD range. If the value does not fall withinthe specified range, amessage will appear, indic-ating that youmust enter a value that falls withinthe specified range.

An Example: Defining Additional IPL Types


An Example: Defining Additional IPL TypesAssume that you want the IPL type Vessel pressure rating below minimum challenge to be avail-able for selection in an Independent Layer of Protection record. In addition, assume that a fixedPFD value of .2 is associated with this IPL type. To define this additional IPL type, you would cre-ate the following IPL Type record.

If you create a new Independent Layer of Protection record and select the Vessel pressure ratingbelow minimum challenge IPL type in the Type list, that record would look similar to the followingimage.

Alternatively, if you assume that the Vessel pressure rating below minimum challenge IPL type isassociated with a PFD range of 0.00001 -0.000001, you would create the following IPL Typerecord.

An Example: Defining Additional IPL Types


If you create a new Independent Layer of Protection record and select the Vessel pressure ratingbelow minimum challenge IPL type in the Type list, that record would look similar to the followingimage.

At this point, you couldmodify the PFD value that is populated automatically with the value in theDefault Value field in the specified IPL Type record. The PFD value that you typemust fall withinthe PFD range (shown in parenthesis in the Type list).

About Navigating SIS Management


About Navigating SIS ManagementSIS Management is context-driven. Thismeans that each page that you view within themodulewill contain data related only to the SIL Analysis with which you are currently working. After youhave opened an SIL Analysis record on the SIL Analysis Definition page, the ID of the SIL Ana-lysis will appear on the site map and the title bar on each page within themodule, indicating thatSIL Analysis with which you are currently working.

The Navigationmenu appears on almost every page in SIS Management and provides access tothe pages that contain the features that allow you to create and performSIL Analyses. After youopen an SIL Analysis record on the SIL Analysis Definition page, you can use the links on theNavigationmenu to facilitate a workflow for creating the remaining records that make up the SILAnalysis.

For example, assume that the SIL Analysis record B0007-009 SteamBoiler SIS appears on theSIL Analysis Definition page. The site map and the title bar will contain the text B0007-009SteamBoiler SIS as shown in the following image.

To define the SIL Analysis team for the SIL Analysis B0007-009 SteamBoiler SIS, you couldclick the Team Members link on the Navigationmenu and see that the site map and title bar onthe SIL Analysis Team Members page still contain the Analysis ID B0007-009 SteamBoilerSIS.

The NavigationMenu in SIS Management


The Navigation Menu in SIS Management

TheNavigationmenu appears onmost pages in SIS Management and provides access to theSIS Management features. A green arrow to the left of an option indicates the feature that youare currently viewing. The Navigationmenu contains the following links:

l Analysis Definition: Displays the SIL Analysis Definition page, where you canmodify anSIL Analysis record or create a new one.

l Team Members: Displays the SIL Analysis Team Members page.

l Documents: Displays the Reference Documents page, where you canmanage Refer-ence Document records for the current SIL Analysis.

l Systems: Displays the Safety Instrumented Systems page, where you canmange theSafety Instrumented System records for the current SIL Analysis.

l Functions: Displays the Instrumented Functions (IFs) page, where you canmanage theInstrumented Function records for the current SIL Analysis.

l All Recommendations: Displays the Recommendation Management page, where youcanmanage the list of Risk Assessment Recommendation records for the current SIL Ana-lysis.

l Revision History: Displays the Analysis Revision History page, where you canmanagethe SIL Analysis Revision records that exist for the analysis. This link is enabled only if thestate of the SIL Analysis record with which you are currently working has ever been set toComplete.

About SIL Analysis Records


About SIL Analysis RecordsSIL Analysis records store information about an SIL Analysis. Creating an SIL Analysis record isthe first step in creating an SIL Analysis. All other records that you create for the SIL Analysis willbe linked directly or indirectly to the SIL Analysis record.

SIL Analysis records are defined via a custom form datasheet that contains the following tabs:

l SIL Analysis

l Safety Requirement Specifications

l General SIS Requirements

l General SIF Requirements

After you have created the SIL Analysis record, it will appear on the SIL Analysis Definitionpage, fromwhich you can use the links on the Navigationmenu to:

l Define the SIL Analysis team.

l Define Reference Document records.

l Define the safety instrumented systems that you are analyzing.

l Define the instrumented functions that make up the safety instrumented system.

l Manage Risk Assessment Recommendation records that are linked to the SIL Analysisrecord.

Accessing the SIL Analysis Search Page


Accessing the SIL Analysis Search PageThe SIL Analysis Search page lets you search for existing SIL Analysis records or create newones. To access this page, youmust be a Super User or amember of theMI SIS Administrator,MI SIS Engineer, or MI SIS User Security Group.

To access the SIL Analysis Search page:

l On the SIS Management Start Page, click the SIL Analysis link.

The SIL Analysis Search page appears.

Aspects of the SIL Analysis Search Page


Aspects of the SIL Analysis Search PageThe SIL Analysis Search page contains the SIL Analysis Search workspace, which displaysthe results of the query specified in the SIL Analysis Search Query text box on the SIS Man-agement Administration page. This documentation assumes that you are using the baselineSIL_Analysis_Search query, which contains two prompts that appear as lists at the top of the SILAnalysis SearchWorkspace:

l State:Contains a list of record states that have been configured for the SIL Analysis family.You can choose from the following baseline states:

n Active: Displays the list of existing SIL Analysis recordswhose State field containsthe value Active.

n Complete: Displays the list of existing SIL Analysis recordswhose State field con-tains the value Complete.

n Pending Approval: Displays the list of existing SIL Analysis recordswhose Statefield contains the value Pending Approval.

n Planning: Displays the list of existing SIL Analysis recordswhose State field con-tains the value Planning.

n Review: Displays the list of existing SIL Analysis recordswhose State field containsthe value Review.

Selecting the All option will cause the query to return all SIL Analysis records in any state.

l SIL Analysis Owner: Contains a list of User IDs of the users whose name is stored in theOwner field in any SIL Analysis record.

After you select different criteria, you can click the Run Query button to run the SIL_Analysis_Search query and displays the results in the grid at the bottom of the page. The query results willinclude hyperlinked Analysis IDs, which you can use to open the SIL Analysis record on theSILAnalysis Definition - <Analysis ID>page, where<Analysis ID>is the ID of the SIL Analysiswith which you are currently working.

Below the query results, options appear that you can use to navigate the results.

The SIL Analysis Search page contains the following taskmenus:

l Common Tasks

l Associated Pages

Common Tasks Menu


Common Tasks Menu

TheCommon Tasks menu on the SIL Analysis Search page contains the following options:

l Find Analysis: Displays theSIL Analysis Search page. This link appears on other pagesin SIS Management and is disabled on theSIL Analysis Search page.

l Create Analysis: Displays a new SIL Analysis record on the SIL Analysis Definitionpage.

l Copy Analysis: Displays on the SIL Analysis Definition page a new SIL Analysis record,which is populated with information from the SIL Analysis record that is currently selected.

l Open Analysis: Displays the selected SIL Analysis record on the SIL Analysis Definitionpage.

l Delete: Displays a confirmationmessage, asking if you want to delete the selected record,and then deletes the selected SIL Analysis record.

l Send To: Displays a submenuwith options that let you provide a link to the current pageon your desktop (create shortcut), in an email message, or on a HomePage.

l Help: Displays the context-sensitive Help topic for the SIL Analysis Search page.

Searching for SIL Analysis Records


Searching for SIL Analysis RecordsTo search for an SIL Analysis record:

1. Access the SIL Analysis Search page.

2. In the SIL Analysis Search workspace, in the State list, select the record state bywhichyou want to filter the results.

3. In the SIL AnalysisOwner list, select the User ID for the name of the analysis owner bywhich you want to filter the results.

4. Click the Run Query button.

The records that meet your search criteria appear in the query results section.

Accessing the SIL Analysis Definition Page


Accessing the SIL Analysis Definition PageThe SIL Analysis Definition page displays:

l A new blank SIL Analysis datasheet, which you can use to create a new SIL Analysisrecord.

-or-

l The datasheet for the selected SIL Analysis record, which you can use tomodify the SILAnalysis record.

To access the SIL Analysis Definition page:


2. On the Common Tasks menu, click the Create Analysis link.

-or-

Click the hyperlinked Analysis ID of an existing SIL Analysis record.

The SIL Analysis Definition page appears.

Aspects of the SIL Analysis Definition Page


Aspects of the SIL Analysis Definition PageThe SIL Analysis Definition page contains the following items:

l SIL Analysis Definitionworkspace: Contains the SIL Analysis record with which you arecurrently working. Via the SIL Analysis Definition workspace, you can create a new SILAnalysis record or modify an existing SIL Analysis record.

l Task Menus: The SIL Analysis Definition page contains the following taskmenus:l Common Tasks

l Navigation

l Associated Pages

Common Tasks Menu


Common Tasks Menu

TheCommon Tasks menu on the SIL Analysis Definition page contains the following options:

l Find Analysis: Displays theSIL Analysis Search page.

l Create Analysis: Displays a new SIL Analysis record on the SIL Analysis Definitionpage.

l Copy Analysis: Displays on the SIL Analysis Definition page a new SIL Analysis record,which is populated with information from the SIL Analysis record that is currently selected.

l Save: Saves the current SIL Analysis record.

l Open Analysis: This link is disabled in the SIL Analysis Definition page.

l Delete: Displays a confirmationmessage, and then deletes the current record.


l Reports: Displays a submenuwith the captions of the reports that are stored in the Cata-log folder \\Public\Meridium\Modules\SIS Management\SIL\Reports.

l Graphs: Displays a submenuwith captions of the graphs that are stored in the Catalogfolder \\Public\Meridium\Modules\SIS Management\SIL\Graphs.

l Help: Displays the context-sensitive Help topic for theSIL Analysis Definition page.

About Defining SIL Analysis Records


About Defining SIL Analysis RecordsYou can define SIL Analysis records via the SIL Analysis datasheet on the Analysis Definitionpage. The SIL Analysis datasheet is a custom form that contains the following tabs that displaysfields that are configured for the SIL Analysis family:

l SIL Analysis

l Safety Requirement Specifications

l General SIS Requirements

l General SIF Requirements

Creating SIL Analysis Records


Creating SIL Analysis RecordsTo create an SIL Analysis record:


2. On the Common Tasks menu, click the Create Analysis link.

The SIL Analysis Definition page appears, displaying a new SIL Analysis record.

3. On the SIL Analysis tab, in the Analysis ID field, type a unique name for the SIL Analysis.

4. Provide values in the remaining fields as desired.

5. Click the Safety Requirement Specifications tab, and enter values as desired.

6. Click the General SIS Requirements tab, and enter values as desired.

7. Click the General SIF Requirements tab, and enter values as desired.

8. At the top of the datasheet, click the Save button.

The SIL Analysis record is saved.

Copying SIL Analysis Records


Copying SIL Analysis RecordsWhen you copy an existing SIL Analysis record, you are creating a new SIL Analysis record thatwill be populated with the values from the record that was copied. The values in all the fields froma source record will be copied to the new record with the exception of the following fields:

l Analysis ID

l Analysis End Date

l Analysis Start Date

l Equipment ID

l Functional Location ID

l Hazards Analysis Date

l Hazards Analysis Reference

l Hazards Analysis Reference Key

l Hazards Analysis Revision

l Last Modified By

l Last Modified Date

To copy an SIL Analysis record:

1. Access the SIL Analysis Definition page for the SIL Analysis record that you want tocopy.

2. On the Common Tasks menu, click theCopy Analysis link.

A new SIL Analysis record appears and is populated automatically with values from the cur-rently selected record.

Copying SIL Analysis Records


3. In the Analysis ID text box, type a unique name for the SIL Analysis. This field is required.

4. If needed, modify the values in the remaining fields.

5. On the Common Tasks menu, click the Save link.

The new SIL Analysis record is saved.

Modifying SIL Analysis Records


Modifying SIL Analysis RecordsTo modify an SIL Analysis record:

1. Open the desired SIL Analysis record on the SIL Analysis Definition page.

2. On the SIL Analysis datasheet, modify the fields as desired.

3. At the top of the datasheet, click the Save icon.


Opening Existing SIL Analysis Records


Opening Existing SIL Analysis RecordsTo open an existing SIL Analysis record:

1. On the SIL Analysis Search page, search for the desired record.

2. In the results, locate the row that contains the desired SIL Analysis record.

3. In the Analysis ID column, click the hyperlinked Analysis ID.

The record appears on the SIL Analysis Definition page, where you canmodify therecord and continue working with the SIL Analysis.

Removing SIL Analysis Records from the SIL Analysis Search Page


Removing SIL Analysis Records from the SIL AnalysisSearch PageIf you are finished with an SIL Analysis record and no longer want to see that record in the queryresults on the SIL Analysis Search page, you can remove the SIL Analysis record from thequery results via theDelete option on theCommon Tasks menu.

Using the Delete option does not delete the SIL Analysis record from the database. Instead,when you remove an SIL Analysis record:

l The Is Deleted check box in the record is selected, and that record will no longer appear inthe query results.

l The links between that record and other records associated with the SIL Analysis aredeleted.

You can remove an SIL Analysis record from the query results on the SIL Analysis Search pageregardless of the state of that record. After an SIL Analysis record has been removed from thequery results, you can still access the record via a search.

To remove an SIL Analysis record from the SIL Analysis Search page:

1. On the SIL Analysis Search page, select the row containing the SIL Analysis record thatyou want to delete.

2. On the Common Tasks menu, click the Delete link.

A confirmationmessage appears, asking if you really want to delete the SIL Analysisrecord and all the records linked to that record.

3. Click the Yes button.

The SIL Analysis record is removed from theSIL Analysis Search page, and the links to allthe records that are linked to that record are deleted.

About Associating SIL Analyses with a Specific Site


About Associating SIL Analyses with a Specific SiteSome companies that use theMeridiumAPM software have facilities at multiple sites, or loc-ations, around the world. Each site contains unique equipment and locations.

If desired, you can define these sites and associate equipment and locationswith the site to whichthey belong. You can also associate riskmatriceswith specific sites. If a riskmatrix is associatedwith a site, you can specify which site you want to associate with an SIL Analysis. You can asso-ciate a site with an SIL Analysis by selecting the ID of the desired Site Reference record in theSite ID field in the SIL Analysis record for that SIL Analysis.

After an SIL Analysis is associated with a site, when you create a Risk Assessment record for anInstrumented Function record associated with an SIL Analysis, rather than seeing the default riskmatrix, you will see the riskmatrix that is associated with the specified site.

About the SIL Analysis Team


About the SIL Analysis TeamThe SIL Analysis team is a group of individuals who will complete the SIL Analysis. You can addMeridiumAPMusers and non-MeridiumAPMusers to the SIL Analysis team.

l MeridiumAPMusers will have an existingMeridiumAPMSecurity User record and anassociated HumanResource record that was created automatically when the SecurityUser record was created.

l Non-MeridiumAPMusers will not have aMeridiumAPMSecurity User record or a HumanResource record. To add a non-MeridiumAPMuser to the SIL Analysis team, you willneed to create a HumanResource record for that user. You can do so via the SIL Ana-lysis Team Members page or usingMeridiumAPMFramework Tools.

Note: A MeridiumAPMSecurity User record is required for logging in to theMeridiumAPMFramework application and using SIS Management. SIL Analysis teammemberswho do nothave a Security User account may participate in and contribute to the analysis but will not beable to use the application.

Anymember of the SIL Analysis team can be assigned a role within the SIL Analysis team, whichprovides a reference of the tasks for which that teammembers is responsible.

Accessing the SIL Analysis TeamMembers Page


Accessing the SIL Analysis Team Members PageOn the SIL Analysis Team Members page, you can add teammembers to the SIL Analysis andassign teammembers the role of ProcessOwner or Facilitator.

To access the SIL Analysis Team Members page:

1. Open the SIL Analysis record for the desired SIL Analysis.

2. On the Navigationmenu, click the Team Members link.

The SIL Analysis Team Members page appears.

Aspects of the SIL Analysis TeamMembers Page


Aspects of the SIL Analysis Team Members PageThe SIL Analysis Team Members page displays the Team Members workspace, which con-sists of a grid that displays the names of the SIL Analysis teammembers. Each row in the grid rep-resents one HumanResource record. For each HumanResource record that appears in thegrid, the following information is displayed:

l User ID: The name of the teammember as it appears in the First Name and Last Namefields in the HumanResource record for that user.

l Process Owner: Indicateswhether or not the teammember has the role of ProcessOwner. This check box can be selected for only one teammember per SIL Analysis team.

l Facilitator: Indicateswhether or not the teammember has the role of Facilitator. Thischeck box can be selected for only one teammember per SIL Analysis.

Below the grid, the following buttons appear:

l Add New Member: Displays a new HumanResource record that you can define and linkto the SIL Analysis record.

l Add Existing Members: Displays the Find Items window, where you can search for anexisting HumanResource record and link it to the SIL Analysis record.

l Remove Members: After asking for confirmation, removes the selected user from theteam. This button is enabled only when records appear in the grid.

The SIL Analysis Team Members page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Common Tasks


Common Tasks

TheCommon Tasks menu on the SIL Analysis Team Members page contains the followinglinks:

l Find Analysis: Displays theSIL Analysis Searchpage, where you can search for an exist-ing SIL Analysis record.

l Create Analysis: Displays a new blank SIL Analysis record on the SIL Analysis Defin-ition page.


l Delete: This link is disabled.


l Help: Displays the context-sensitive Help topic for theSIL Analysis Team Memberspage.

Creating New Users and Adding Them to the SIL Analysis Team


Creating New Users and Adding Them to the SIL Ana-lysis TeamWhen you create new users and add them to the SIL Analysis team, you are creating newHumanResource records in theMeridiumAPMdatabase and linking them to the SIL Analysisrecord. This option should be used for teammemberswho do not have a HumanResourcerecord. If you want to add a teammember who is already has a HumanResource record, see thetopic for adding new teammemberswho already have a HumanResource record.

To create a new user and add that user to the SIL Analysis team:

1. Access the SIL Analysis Team Members page.

2. At the bottom of the Team Members workspace, click the Add New Member button.

A new HumanResource record appears.

Creating New Users and Adding Them to the SIL Analysis Team


3. Enter values in the fields on the datasheet as desired. Note that the Last Name field isrequired.

4. ClickOK.

The HumanResource record is saved, and the new SIL Analysis teammember appears intheTeam Members workspace.

Adding New TeamMembers Who Already Have A HumanResource Record


Adding New Team Members Who Already Have AHuman Resource RecordWhen you add a new SIL Analysis TeamMember who already has a HumanResource record,you are linking an existing HumanResource record to the SIL Analysis record. This option shouldbe used for teammemberswho already have a HumanResource record. If you want to add anew SIL Analysis teammember who does not already have a HumanResource record, see thetopic for creating a new user to add to the SIL Analysis team.

To add a new team member who already has a Human Resource record:


2. At the bottom of the Team Members workspace, click the Add Existing Members button.

The Find Items window appears, and the HumanResource family is selected in theSearch In list by default.

3. If desired, type your search criteria in the Look For text box., and then click the FindNow button.

The search results appear.

4. Locate the desired HumanResource record, and click the Open button.

Adding New TeamMembers Who Already Have A HumanResource Record


The new SIL Analysis teammember appears in theTeam Members workspace.

About SIL Analysis TeamMember Roles


About SIL Analysis Team Member RolesSIL Analysis teammember roles serve as a reference of which SIL Analysis teammember isresponsible for a given task related to the SIL Analysis. The following roles are available for anSIL Analysis:

l Process Owner: The teammember who is responsible for the SIL Analysis. After youassign a teammember the role of ProcessOwner, that teammember's namewill appearin the Owner field in the SIL Analysis record.

l Facilitator: The teammember who is in charge of conducting the SIL Analysis and organ-izing the SIL Analysis team.

There can be only one ProcessOwner and one Facilitator per SIL Analysis. A single teammem-ber, however, can be designated as both the ProcessOwner and Facilitator.

Assigning Roles to SIL Analysis TeamMembers


Assigning Roles to SIL Analysis Team MembersThe following instructions provide details on designating a teammember as the ProcessOwneror Facilitator. Assigning a teammember to a role serves as a reference for the team.

To assign a role to an SIL Analysis team member:


2. In the Team Members workspace, locate the row containing the teammember that youwant to assign the role of ProcessOwner or Facilitator.

3. In either the Process Owner or Facilitator column, select the check box to indicate that theteammember is assigned to the corresponding role.

The teammember is assigned the specified role, and theOwner field on the SIL Analysisdatasheet is populated with that teammember's name.

To assign a role to a different teammember, select the Process Owner or Facilitatorcheck box in the row that represents that teammember.

Viewing HumanResource Records for Existing TeamMembers


Viewing Human Resource Records for Existing TeamMembersTo view the Human Resource record for an existing SIL Analysis team member:


2. In the Team Members workspace, locate the row containing the teammember whoseHumanResource record you want to view.

3. In the User ID column, click the teammember's hyperlinked User ID.

The HumanResource record for that teammember appears. At this point you canmodifythe fields if desired.

4. ClickOK.


Removing TeamMembers from the SIL Analysis Team


Removing Team Members from the SIL Analysis TeamWhen you remove a teammember from an SIL Analysis team, you are deleting the link betweenthe HumanResource record and the SIL Analysis record.

Additionally, if you remove from the SIL Analysis team a teammember who is assigned the roleof ProcessOwner, the Owner field in the SIL Analysis record will be cleared.

To remove team members from the SIL Analysis team:


2. In the Team Members workspace, select the rows containing the teammember that youwant to remove from the SIL Analysis team.

3. At the bottom of the Team Members workspace, click the Remove Members button.

A confirmationmessage appears, asking if you really want to remove the selected teammembers.


The selected teammembers are removed from the SIL Analysis team.

Accessing the Reference Documents Page


Accessing the Reference Documents PageTheReference Documents page lets you create andmanage Reference Document records thatare linked to the SIL Analysis record for the current SIL Analysis.

To access the Reference Documents page:


2. On the Navigationmenu, click the Documents link.

The Reference Documents page appears.

Aspects of the Reference Documents Page


Aspects of the Reference Documents PageTheReference Documents page contains the Reference Documents workspace, which con-sists of a grid that displays a list of Reference Document records that are linked to the current SILAnalysis. Each row in the grid represents one Reference Document record. For each ReferenceDocument record that appears in the grid, the following information is displayed:

l ID: The value that exists in the ID field of the associated Reference Document record.

l Description:The value that exists in the Description field of the associated ReferenceDocument record.


l Add New Document: Displays a new blankReference Document record in the <empty>(new Reference Document) dialog box.

l Add Existing Documents: Displays the Find Items window, where you can search for anexisting Reference document record to link to the SIL Analysis.

l Remove Documents: Displays a confirmationmessage and then removes the ReferenceDocument record from the SIL Analysis. This button is enabled only when a row in the gridis selected.

l Open Document: Opens the file associated with the selected Reference Documentrecord. This button is enabled only when a row in the grid is selected.

The Reference Documents page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Common Tasks


Common Tasks

TheCommon Tasks menu on the Reference Documents page contains the following links:

l Find Analysis: Displays the SIL Analysis Search page, where you can search for anexisting SIL Analysis record.

l Create Analysis: Displays a new, blank SIL Analysis record on the SIL Analysis Defin-ition page.




l Help: Displays the context-sensitive Help topic for the SIL Analysis Team Memberspage.

Creating New Reference Document Records and Adding Them to the SIL Analysis


Creating New Reference Document Records andAdding Them to the SIL AnalysisWhen you create a new Reference Document record and add it to the SIL Analysis, you are link-ing the new Reference Document record to the SIL Analysis record.

To create a new Reference Document record and add it to the SIL Analysis:

1. Access the Reference Documents page.

2. Below the grid, click the Add New Document button.

A new Reference Document record appears.

3. Follow the standard procedure for creating a Reference Document record.

The new Reference Document record is saved and linked to the SIL Analysis record, andthe record appears in the Reference Documents workspace.

Adding Existing Reference Document Records to the SIL Analysis


Adding Existing Reference Document Records to theSIL AnalysisWhen you add an existing Reference Document record to the SIL Analysis, you are linking theReference Document to the SIL Analysis record.

To add existing Reference Document records to the SIL Analysis:


2. Below the grid, click the Add Existing Documents button.

The Find Items window appears, and the Reference Document family appears in theSearch In list by default.

3. Provide additional search criteria if desired, and then click the Find Now button.


4. In the search results grid, select the row containing the Reference Document record thatyou want to link to the SIL Analysis record.


The selected record appears in the Reference Documents workspace.

Viewing Reference Documents


Viewing Reference DocumentsWhen you view a reference document, you are opening the file specified in the Reference Docu-ment record. To be able to view a reference document on your computer:

l The file must be saved to a location that can be accessed from your computer.

l The application required to open that document must be installed on your computer.

To view a reference document:


2. In the Reference Documents workspace, select the row containing the reference doc-ument that you want to view.

3. At the bottom of the Reference Documents workspace, click the Open Document button.

The reference document file appears in the application required to display it. For example,if the reference document is a word document, it will appear in theMicrosoft Word applic-ation.

Opening Reference Document Records


Opening Reference Document RecordsTo open a Reference Document record:


2. In the Reference Documents workspace, locate the row containing the Reference Docu-ment record that you want to open.

3. In the ID column, click the hyperlinked Record ID of the record.

The Reference Document record appears in a new window. At this point, you canmodifythe records as desired.

To close the Reference Document record and return to the Reference Documents page,click OK (to save your changes) or Cancel.

Removing Reference Documents from the SIL Analysis


Removing Reference Documents from the SIL AnalysisWhen you remove a reference document from the SIL Analysis, you are deleting the link betweenthe Reference Document record and the SIL Analysis record. You are not deleting the ReferenceDocument record from the database.

To remove reference documents from the SIL Analysis:


2. In the Reference Documents workspace, select the row containing the reference doc-ument that you want to remove from the SIL Analysis.

3. Click the Remove Documents button.

A confirmationmessage appears, asking if you really want to remove the selected record.


The selected record is removed from the SIL Analysis and is no longer displayed in thegrid.

About Safety Instrumented System Records


About Safety Instrumented System RecordsSafety Instrumented System records store details about safety instrumented systems (SIS) forwhich you are conducting an SIL Analysis. A safety instrumented system is a system that isequipped with one or more protective instrument loops (PIL), which consist of a series of inter-connected instruments that are designed specifically to monitor the process defined by that pro-tective instrument loop's instrumented function and prevent consequenceswithin that process.You should add to the SIL Analysis one Safety Instrumented System record per safety instru-mented system that you want to asses via the analysis.

When you add a Safety Instrumented System record to an SIL Analysis, you are linking theSafety Instrumented System record directly to the SIL Analysis record. Additionally, Safety Instru-mented System records can be linked to records in the following families:

l Instrumented Function: Store details on the specific function of a given protective instru-ment loop within the safety instrumented system.

l SIS Proof Test: Store details on the steps that need to be performed to test each safetyinstrumented system and the results of that test.

l SIS Proof Test Template: Store details on the steps that need to be performed to test aninstrumented function. You can use an SIS Proof Test Template record to populate an SISProof Test record with data that is common tomore than one proof test.

You can add Safety Instrumented System records to the SIL Analysis using the followingmeth-ods:

l Create a new one.

l Add an existing one.

l Copy an existing one and automatically create a new one.

After you have added to the SIL Analysis the desired Safety Instrumented System records, youcan define the specific Instrumented Functions (IFs) of those Safety Instrumented Systems.

Accessing the Safety Instrumented Systems Page


Accessing the Safety Instrumented Systems PageOn the Safety Instrumented Systems page, you can create new Safety Instrumented Systemrecords andmodify existing ones.

To access the Safety Instrumented Systems page:


2. On the Navigationmenu, click the Systems link.

The Safety Instrumented Systems page appears.

Aspects of the Safety Instrumented Systems Page


Aspects of the Safety Instrumented Systems PageThe Safety Instrumented Systems page contains the Safety Instrumented Systems work-space, which consists of a grid that displays a list of Safety Instrumented System records that arelinked to the current SIL Analysis. Each row in the grid represents one Safety Instrumented Sys-tem record. For each Safety Instrumented System record that appears in the grid, the followinginformation is displayed:

l System ID: The value that exists in the SIS ID field in the Safety Instrumented Systemrecord.

l Description: The value that exists in the SIS Description field in the Safety InstrumentedSystem record.

l Logic Solver Type: The value that exists in the Logic Solver Type field in the Safety Instru-mented System record.

l Is Default: Specifies whether or not the Safety Instrumented System record is the default.If you havemore than one safety instrumented systems defined for an SIL Analysis, youwill need to specify one as the default.


l Create New System: Displays a new blank Safety Instrumented System record in a newwindow.

l Add Existing System: Displays the Find Items window, where you can search for anexisting Safety Instrumented System record to link to the SIL Analysis record.

l Copy System: Displays a new Safety Instrumented System record and populates it auto-matically with values from the currently selected record. This button is enabled only when arecord appears in the grid.

l Remove System: After displaying a confirmationmessage, deletes the link between theselected Safety Instrumented System record and the SIL Analysis record. This button isenabled only when a record appears in the grid.

The Safety Instrumented Systems page contains the following taskmenus:

l Navigation

l Assessment Tasks

l Common Tasks

l Associated Pages

Assessment Tasks


Assessment Tasks

The Assessment Tasks menu on the Safety Instrumented Systems page contains the fol-lowing links:

l Test Templates: Displays a submenuwith the following options:n Create: Displays theProof Test Template Definition page, where you can create a new

Proof Test Template record and link it to the selected Safety Instrumented System record.

n View: Displays theProof Test Templates page, where you can view a list of Proof TestTemplate records that are linked to the selected Safety Instrumented System record.

l Proof Tests: Displays a submenuwith the following options:n Create: Displays the Proof Test Definition page, where you can create a new Proof Test

record to link to the selected Safety Instrumented System record.

n View: Displays the Proof Tests page, where you can view a list of Proof Test records thatare linked to the selected Safety Instrumented System record.

l Tasks: Displays a submenuwith the following options:

n Create: Displays a new Inspection Task record that you can link to the selectedSafety Instrumented System record.

n View: Displays theTask List page, where you can view a list of Inspection Tasksrecords that are linked to the selected Safety Instrumented System record.

The Assessment Tasks menu appears onmultiple pages throughout SIS Management. Thelinks that are available to you will vary depending on where you are accessing themenu.

Common Tasks


Common Tasks

TheCommon Tasks menu on the Safety Instrumented Systems page contains the followinglinks:






l Help: Displays the context-sensitive help topic for theSafety Instrumented Systemspage.

Creating New Safety Instrumented System Records


Creating New Safety Instrumented System RecordsWhen you create a new Safety Instrumented System record, it will be linked automatically to theSIL Analysis record for the current SIL Analysis.

To create a new Safety Instrumented System record:

1. Access the Safety Instrumented Systems page.

2. At the bottom of the Safety Instrumented Systems workspace, click the Create New Sys-tem button.

A new blank Safety Instrumented System record appears in a new window.

3. In the SIS ID text box, type a unique name for the safety instrumented sysetm. This field isrequired.

Creating New Safety Instrumented System Records


4. Provide values for the remaining fields as desired.

5. ClickOK.

The record window closes, and the record is created and linked to the SIL Analysis recordfor the current analysis and appears in the Safety Instrumented Systems grid.

Adding Existing Safety Instrumented System Records to the SIL Analysis


Adding Existing Safety Instrumented System Recordsto the SIL AnalysisWhen you add an existing Safety Instrumented System record to an SIL Analysis, you are linkingthat record to the SIL Analysis record for the current SIL Analysis.

To add an existing Safety Instrumented System record to the SIL Analysis:


2. At the bottom of the Safety Instrumented Systems workspace, click the Add ExistingSystems button.

The Find Items window appears, where you can search for an existing Safety Instru-mented System record.

3. If desired, in the Look For text box, type the desired search criteria, and click the Find Nowbutton.

The search results appear and contain only the Safety Instrumented System records thatare not currently linked to an SIL Analysis.

Adding Existing Safety Instrumented System Records to the SIL Analysis


4. In the search results, select the row containing the record that you want to add to the ana-lysis.


The Find Items window closes, and the selected record is linked to the SIL Analysis recordfor the current SIL Analysis and appears in the Safety Instrumented Systems grid.

Copying Existing Safety Instrumented System Records


Copying Existing Safety Instrumented System RecordsWhen you copy an existing Safety Instrumented System record, you are creating a new SafetyInstrumented System record that will be populated with the values from the record that wascopied. The new record will be linked automatically to the SIL Analysis record for the current SILAnalysis. That values in all the fields from a source record will be copied to the new record withthe exception of the SIS ID field. Each Safety Instrumented System record should have a uniqueID.

To copy a Safety Instrumented System record:


2. In the Safety Instrumented Systems grid, select the row containing the Safety Instru-mented System record that you want to copy.

3. At the bottom of the Safety Instrumented Systems workspace, click the Copy Systembutton.

A new Safety Instrumented System record appears in a new window and is populatedautomatically with values from the currently selected record with the exception of the SISID field.

4. In the SIS ID field, type a unique name for the safety instrumented system.

5. Modify the values in the remaining fields as desired, and then clickOK.

The record window closes, and the new record is linked to the SIL Analysis record for thecurrent SIL Analysis and appears in the Safety Instrumented Systems grid.

Modifying Safety Instrumented System Records


Modifying Safety Instrumented System RecordsTo modify a Safety Instrumented System record:


2. In the Safety Instrumented Systems grid, locate the Safety Instrumented System recordthat you want to modify.

3. In the System ID cell, click the hyperlinked Record ID of that record.

The selected record appears in a new window.

4. Modify the values in the fields as desired, and then clickOK.


Removing Safety Instrumented System Records from the SIL Analysis


Removing Safety Instrumented System Records fromthe SIL AnalysisWhen you remove a Safety Instrumented System record from the SIL Analysis, you are deletingthe link between the Safety Instrumented System record and the SIL Analysis record for the cur-rent SIL Analysis.

To remove a Safety Instrumented System record from the SIL Analysis:


2. In the Safety Instrumented Systems grid, select the row containing the Safety Instru-mented System record that you want to remove from the analysis.

3. At the bottom of the Safety Instrumented Systems grid, click the Remove System but-ton.

A confirmationmessage appears, asking if you really want to remove the Safety Instru-mented System record form the analysis.

4. ClickOK.

The link between the selected record and the SIL Analysis record for the current analysis isdeleted, and the record is removed from the Safety Instrumented Systems grid.

About Instrumented Function Records


About Instrumented Function RecordsInstrumented Function records store details about the specific functions that exist within a safetyinstrumented system. An instrumented function is a specific need required of a safety instru-mented system tomonitor the conditions of a process. For each instrumented function defined fora safety instrumented system, one protective instrument loop (PIL) will exist to satisfy that need.A protective instrument loop consists of interconnected safety instruments that monitor aspects ofa process and take readings on its condition. You should create one Instrumented Functionrecord per instrumented function on an SIS. An instrumented functionmay be associated with aparticular equipment or location within the process that the SIS exists to safeguard.

When you create an Instrumented Function record, it will be linked automatically to the SIL Ana-lysis record for the current analysis. When you define the Instrumented Function record, in addi-tion to details about the instrumented function, you can specify the:

l Safety Instrumented System record to which the Instrumented Function record is linked.

l Equipment and Functional Location record to which the Instrumented Function record islinked.

l SIF CommonCause Failure records that are linked to the Instrumented Function record.

l Hazardous events that may occur if the safe state associated with the current instrumentedfunction occurs at the same time as the safe state associated with a different instrumentedfunction.

You can add Instrumented Function records to the SIL Analysis using the followingmethods:

l Create a new one.

l Add an existing one.

l Copy an existing one and automatically create a new one.

After you have defined the desired Instrumented Function records, you can assess the risk asso-ciated with an instrumented function and define the protective instrument loop that exists for aninstrumented function.

Accessing the Instrumented Functions (IFs) Page


Accessing the Instrumented Functions (IFs) PageThe Instrumented Functions (IFs) page lets youmange the Instrumented Function records thatare linked to the SIL Analysis record for the current SIL Analysis.

To access the Instrumented Functions (IFs) page:


2. On the Navigationmenu, click the Functions link.

The Instrumented Functions (IFs) page appears.

Aspects of the Instrumented Functions (IFs) Page


Aspects of the Instrumented Functions (IFs) PageThe Instrumented Functions (IFs) page contains the following sections:

l Instrumented Functions: Consists of a grid that contains a list of Instrumented Functionrecords that are linked to the SIL Analysis record for the current SIL Analysis and optionsthat you can use tomanage those records. Each row in the grid corresponds to one Instru-mented Function record. For each Instrumented Function record in the grid, the followinginformation appears:

n Function ID: The value that exists in the IF ID field in the Instrumented Functionrecord. This value appears as a hyperlink, which you can click to view the contents ofthe Instrumented Function record.

n Description: The value that exists in the IF Description field in the InstrumentedFunction record.

n SIL Method: The value that exists in the SIL Assessment Method field in the Instru-mented Function record.

n SIL Mode: The value that appears in the SILMode field in the Instrumented Func-tion record.

n Selected SIL Level: The value that exists in the Selected SIL Level field in the Instru-mented Function record. If the Selected SIL Level field is empty (i.e., an SIL Levelhas not been assessed), the Selected SIL Level cell will contain the value 0.

n Protective Loop ID: The ID of the Protective Instrument Loop record that is linked tothe Instrumented Function record. If more than one Protective Instrument Looprecord is linked to the Instrumented Function, this field contains the ID of the Pro-tective Instrument Loop record that is in theApproved state. If a Protective Instru-ment Loop record that is linked to the Instrumented Function record is not in anApproved state, this field contains the ID of the first Protective Instrument Looprecord that is linked to the Instrumented Function record.


n Create New Function: Displays a new blank Instrumented Function record in a new win-dow.

n Add Existing Functions: Displays the Find Items window, where you can search for anexisting Instrumented Function record to add to the SIL Analysis.

n Copy Function: Displays a new Instrumented Function record that is populated auto-matically with values from the source record. This button is enabled only when a recordappears in the grid.

n Remove Function: Displays a confirmationmessage, and then removes the selectedInstrumented Function record from the SIL Analysis. This button is enabled only when arecord appears in the grid.

l Associated Risk Assessments: Consists of a grid that contains a list of LOPA recordsthat are linked to the Instrumented Function record that is currently selected in the Instru-mented Functions grid. Each row in the grid represents one LOPA record. For eachLOPA record in the grid, the following information appears:

Aspects of the Instrumented Functions (IFs) Page


n LOPA ID: The value that exists in the LOPA ID field in the LOPA record.

n Description: The value that exists in the Description field in the LOPA record.

n Calculated SIL Level: The value in the Calculated SIL field in the LOPA record.

n RRF: The value that exists in the Required PIF Risk Reduction Factor field in theLOPA record.


n Create New LOPA: Displays the LOPA Definition page, where you can create a LOPArecord and conduct a Layer of Protection Analysis.

n Add Existing LOPA: Displays the Find Items window, where you can search for an exist-ing LOPA record to link to the SIL Analysis.

n Copy LOPA: Displays on the LOPA Definition page a new LOPA record that is auto-matically populated with values from the currently selected LOPA record.

n Remove LOPA: Displays a confirmationmessage, and then removes the LOPA recordfrom the SIL Analysis.

You can collapse and expand the Instrumented Functions and Associated Risk Assessmentssections using the following buttons, which appear in the top right corner of the sections in turn:

: Indicates that the section is expanded. You can click this button to collapse the section.

: Indicates that the section is collapsed. You can click this button to expand the section.

The Instrumented Functions (IFs) page contains the following taskmenus:

l Navigation

l Assessment Tasks

l Common Tasks

l Associated Pages

Assessment Tasks


Assessment Tasks

The Assessment Tasks menu on the Instrumented Functions (IFs) page contains the followinglinks:

l Risk Matrix: Displays the Risk Assessment interface fromwhich you can define the unmit-igated risk for the selected Instrumented Function record.

l Protective Loops: Displays the Protective Instrument Loop Diagram View page, whereyou canmange Protective Instrument Loop records.

l Recommendations: Displays the Recommendations dialog box, where you canmanageRisk Assessment Recommendations records for the selected Instrumented Functionrecord.

l Asset Health Manager: Displays the SIS - Asset Health Manager for <InstrumentedFunction Record ID> (Instrumented Function) page, where you canmanage the HealthIndicator records for the selected Instrumented Function record.

Note: The integration between SIS Management and Asset Health Manager (AHM) isnot documented.

l Test Templates: Displays a submenuwith the following options:n Create: Displays the Proof Test Template Definition page, where you can create a new

Proof Test Template record and link it to the selected Instrumented Function record.

n View: Displays the Proof Test Templates page, where you can view a list of Proof TestTemplate records that are linked to the selected Instrumented Function record.

l Proof Tests: Displays a submenuwith the following options:l Create: Displays the Proof Test Definition page, where you can create a new Proof Testrecord to link to the selected Instrumented Function record.

l View: Displays the Proof Tests page, where you can view a list of Proof Test records thatare linked to the selected Instrumented Function record.

l Tasks: Displays a submenuwith the following options:n Create: Displays a new Inspection Task record that you can link to the selected Instru-

mented Function record.

n View: Displays the Task List page, where you can view a list of Inspection Tasks recordsthat are linked to the selected Instrumented Function record.

Assessment Tasks


l ASM: Displays a submenuwith the following options:n Promote: Promotes the Equipment or Functional Location record that is linked to the selec-

ted Instrumented Function record to an ASMand displays on the ASM - Asset StrategyOverview page the Asset Strategy for that record.

n View: Displays the Asset Strategy for the Equipment or Functional Location record that islinked to the selected Instrumented Function record. This link is enabled only if that Equip-ment or Functional Location record has been promoted to ASMand has an existing AssetStrategy.

The ASM link is enabled only if the selected Instrumented Function record is linked to anEquipment or Functional Location record and a Risk Assessment record.

The Assessment Tasks menu appears onmultiple pages throughout SIS Management. Thelinks that are available to you will vary depending on where you are accessing themenu.

Common Tasks


Common Tasks

TheCommon Tasks menu on the Instrumented Functions (IFs)page contains the followinglinks:






l Reports: Displays a submenu that contains the captions of the following Catalog items aslinks:

n IF Report: Displays in the Report Viewer the IF Report for the selected Instrumented Func-tion record.

n IF Risk Matrix Result Report:Displays in the Report Viewer the IF RiskMatrix ResultReport for the selected Instrumented Function record.

l Help:Displays the context-sensitive help topic for theInstrumented Functions (IFs)page.

About Defining Instrumented Function Records


About Defining Instrumented Function RecordsInstrumented Function records are defined via the <Record ID> (Instrumented Function) win-dow, where <Record ID>is the value stored in the IF ID field in that record. The<Record ID>(Instrumented Function)window contains the following tabs:

l Instrumented Function: Displays the Instrumented Function datasheet, which is a customform and contains fields that store information about the instrumented function that recordrepresents.

l Safety Requirement Specification: Displays the Safety Requirement Specification data-sheet, which is a custom form and contains fields that are used by the Safety RequirementSpecifications report.

l Common Cause Failures: Contains options you can use tomanage the SIF CommonCause Failure records that are linked to Instrumented Function records.

l Concurrent Safe States: Contains options you can use tomanage the other InstrumentedFunction records that are linked to the current Instrumented Function record and specifythe hazardous event that can occur when the instrumented functions represented by thoserecords are in safe states at the same time.

The following image showswhat an Instrumented Function record looks like in the <Record ID>(Instrumented Function) window, where the Instrumented Function tab is selected by default.

About Defining Instrumented Function Records


Creating New Instrumented Function Records


Creating New Instrumented Function RecordsWhen you create a new Instrumented Function record, it will be linked automatically to the SILAnalysis record for the current SIL Analysis.

To create a new Instrumented Function record:

1. Access the Instrumented Functions (IFs) page.

2. In the Instrumented Functions section, below the grid, click the Create New Function but-ton.

A new blank Instrumented Function record appears in the <Record ID> (InstrumentedFunction) window, and the Instrumented Function tab is selected by default.

Creating New Instrumented Function Records


3. In the IF ID text box, type a unique name for the instrumented function. This field isrequired.

4. Provide values in the remaining fields as desired.

5. Click the Safety Requirement Specification tab, and then provide values in the fields asdesired.

6. Click the Common Cause Failures tab, and define the common cause failures associatedwith the instrumented function.

7. Click the Concurrent Safe States tab, and define the concurrent safe state hazards asso-ciated with the instrumented function.

8. ClickOK.

The window closes, and the record is linked to the SIL Analysis record for the current ana-lysis and appears in the Instrumented Functions grid.

About the Instrumented Function Tab


About the Instrumented Function TabThe Instrumented Function tab on the <Record ID> (Instrumented Function) window displaysthe Instrumented Function datasheet, which is the default datasheet for the Instrumented Func-tion family. This datasheet is a custom form and contains fields that are used to define the instru-mented function that the record represents.

The following image showswhat the Instrumented Function tab looks like in the<Record ID>(Instrumented Function) window.

About The Safety Requirement Specification Tab


About The Safety Requirement Specification TabThe Safety Requirement Specification tab on the <Record ID> (Instrumented Function) win-dow displays the Safety Requirement Specification datasheet, which is a custom form that con-tains fields that store information that is used by the Safety Requirement Specification report.

The following image showswhat the Safety Requirement Specification tab looks like on the<Record ID> (Instrumented Function) window.

About SIF CommonCause Failure Records


About SIF Common Cause Failure RecordsSIF CommonCause Failure records store details about a failure or a condition within a plant thatcan affect the operation of multiple instrumented functions. Throughout this documentation, werefer to these items as common cause failures. SIF CommonCause Failure recordsmust belinked to at least two Instrumented Function records. In other words, for every SIF CommonCause Failure record, there will be at least two Instrumented Function records that represent theinstrumented functions that are affected by the common cause failure defined in the SIF Com-monCause Failure record.

For example, incorrect maintenance of sensors can affect multiple instrumented functions. In thiscase, you would first create an SIF CommonCause Failure record to document incorrect main-tenance of sensors as a common cause failure and then link that SIF CommonCause Failurerecord to the Instrumented Function records representing the instrumented functions that wouldbe affected by the incorrect sensor maintenance.

You canmanage SIF CommonCause Failure records via the Common Cause Failures tab onthe <Record ID> (Instrumented Function) window for an Instrumented Function record. Usingthe Common Cause Failures tab, you can specify the common cause failures that exist for thecurrent instrumented function and other instrumented functions that are defined in theMeridiumAPMdatabase. More specifically, to define a common cause failure, you will need to:

n Link SIF CommonCause Failure records to the current Instrumented Function record.

n Link additional Instrumented Function records to those SIF CommonCause Failurerecords.

The following illustration shows the records that will exist for a given common cause failure scen-ario.

When you are working with records in the SIF CommonCause Failure and Instrumented Func-tion families, it is helpful to refer to the SIS Management datamodel in which the InstrumentedFunction family is the predecessor family.

The following image showswhat the Common Cause Failures tab looks like on the <RecordID> (Instrument Function) window.

About SIF CommonCause Failure Records


Aspects of the CommonCause Failures Tab


Aspects of the Common Cause Failures TabTheCommon Cause Failures tab on the <Record ID> (Instrumented Function)window con-tains the following sections:

l Common Cause Failures: Contains a grid that displays the SIF CommonCause Failurerecords that are linked to the current Instrumented Function record and the additionalInstrumented Function records that appear in the Related Instrumented Function grid.Each row in the Common Cause Failures grid represents one SIF CommonCause Fail-ure record. For each SIF CommonCause Failure record, the following values that arestored in the corresponding SIF CommonCause Failure record are displayed:

n CCF ID: An ID for the common cause failure. This value appears as a hyperlink,which you can click to view the contents of the corresponding SIF CommonCauseFailure record in a new window.

n CCF Description: A description of the common cause failure.

n CCF Mitigation: A description of the way(s) in which you canmitigate the occur-rence of the effect of the common cause failure.


n Create New: Displays a new SIF CommonCause Failure record in a new window, whereyou can define a common cause failure and automatically link the SIF CommonCause Fail-ure record to the current Instrumented Function record. After you create an SIF CommonCause Failure record, a new row will appear in the Related Instrumented Functions gridto represent the current Instrumented Function, and amessage will appear in that section,indicating that youmust link at least onemore Instrumented Function record to the SIFCommonCause Failure record.

n Add Existing: Displays the Find Items window, where you can search for an existing SIFCommonCause Failure record and link it to the current Instrumented Function record.After you link an existing SIF CommonCause Failure record to the Instrumented Functionrecord, a new row will appear in the Related Instrumented Functions grid to representthe current Instrumented Function record, and amessage will appear in that section, indic-ating that youmust link at least onemore Instrumented Function record to the SIF Com-monCause Failure record.

n Remove: After displaying a confirmationmessage, deletes the link between the SIF Com-monCause Failure record and the current Instrumented Function record. If the SIF Com-monCause Failure record is linked to an Instrumented Function record other than thecurrent one, that link will not be removed. This button is disabled until at least one SIF Com-monCause Failure record appears in the grid.

l Related Instrumented Functions: Contains a grid that displays Instrumented Functionrecords, if at least one SIF CommonCause Failure record appears in the Common CauseFailures grid. Specifically, the rows in the Related Instrumented Functions grid containthe:

n Current Instrumented Function record. This record always appears in the first row.

n Additional Instrumented Function records that are linked to the SIF CommonCauseFailure record that is selected in the Common Cause Failures grid.

Aspects of the CommonCause Failures Tab


Below the grid, the Add Existing button appears, which displays the Find Items window,where you can search for an existing Instrumented Function record that you want to link tothe selected SIF CommonCause Failure record.

The following image showswhat the Common Cause Failures tab looks like whenONE SIFCommonCause Failure record is linked to the current Instrumented Function record and twoadditional Instrumented Function records.

Creating New CommonCause Failure Records


Creating New Common Cause Failure RecordsWhen you create a new SIF CommonCause Failure record, it will be linked automatically to theInstrumented Function record with which you are currently working.

To create a new SIF Common Cause Failure record:

1. Open the Instrumented Function record to which you want to link a new SIF CommonCause Failure record.

2. Click the Common Cause Failures tab.

The Common Cause Failures tab appears.

3. In the Common Cause Failures section, click the Create New button.

A new SIF CommonCause Failures record appears in a new window.



4. Provide values in the fields as desired. All the fields are required.

5. ClickOK.

The SIF CommonCause Failures record closes, and the following rows are added to theCommon Cause Failures tab:

l One row in the Common Cause Failures section that represents the SIF CommonCauseFailure record.

l One row in the Related Instrumented Functions section that represents the current Instru-mented Function record.

In addition, amessage appears, indicating that youmust link at least onemore Instru-mented Function record to the SIF CommonCause Failure record. The following imageshows an example of how the Common Cause Failures tab appears after you create anew SIF CommonCause Failure record.



6. Link the additional Instrumented Function record(s) to the SIF CommonCause Failurerecord.

7. ClickOK.

The Instrumented Function record closes, and your changes are saved.

Linking Existing SIF CommonCause Failure Records to Instrumented Function Records


Linking Existing SIF Common Cause Failure Recordsto Instrumented Function RecordsTo link an existing SIF Common Cause Failure record to an Instrumented Function record:

1. Open the Instrumented Function record to which you want to link an existing SIF CommonCause Failure record.

2. Click the Common Cause Failures tab.

The Common Cause Failures tab appears.

3. In the Common Cause Failures section, click the Add Existing button.

The Find Items window appears.

4. Perform a search for the desired SIF CommonCause Failure record.

5. In the search results, select the row containing the SIF CommonCause Failure record that

Linking Existing SIF CommonCause Failure Records to Instrumented Function Records


you want to link to the current Instrumented Function record, and then click the Open but-ton.

The Find Items window closes, and the following rows are added to the Common CauseFailures tab:

l One row in the Common Cause Failures section that represents the SIF CommonCauseFailure record that you selected.

l One row in the Related Instrumented Functions section that represents the current Instru-mented Function record.

In addition, amessage appears, indicating that youmust link at least onemore Instru-mented Function record to the SIF CommonCause Failure record. The following imageshows an example of how the Common Cause Failures tab appears after you link anexisting SIF CommonCause Failure record to an Instrumented Function record.

6. Link the additional Instrumented Function record(s) to the SIF CommonCause Failurerecord.

7. ClickOK.

The Instrumented Function record closes, and your changes are saved.

Linking Additional Instrumented Function Records to an SIF CommonCause Failure Record


Linking Additional Instrumented Function Records toan SIF Common Cause Failure RecordThe following instructions assume that you are viewing the Common Cause Failures tab in anInstrumented Function record that is linked to at least one SIF CommonCause Failure record.

To link an additional Instrumented Function record to an SIF Common Cause Failurerecord:

1. In the Common Cause Failures section, select the row containing the SIF CommonCause Failure record that you want to link to an additional Instrumented Function record.

2. In the Related Instrumented Functions section, click the Add Existing button.


3. Perform a search for the desired Instrumented Function record.

4. In the search results, select the row containing the Instrumented Function record that youwant to link to the SIF CommonCause Failure record, and then click the Open button.

The Find Items window closes, and the Instrumented Function record appears in a newrow in the Related Instrumented Functions grid.

Linking Additional Instrumented Function Records to an SIF CommonCause Failure Record


5. ClickOK.

The Instrumented Function record closes, and your changes are saved. Note that if youview the Common Cause Failures tab in the Instrumented Function record that you justadded, the SIF CommonCause Failure record will be displayed in the Common CauseFailures grid.

Removing SIF CommonCause Failure Records from an Instrumented Function Record


Removing SIF Common Cause Failure Records froman Instrumented Function RecordThe following instructions provide details on removing an SIF CommonCause Failure recordfrom an Instrumented Function record. When you do so, you are deleting the link between theSIF CommonCause Failure record and the Instrumented Function record.

These instructions assume that you are viewing the Common Cause Failures tab on the<Record ID> (Instrumented Function) window for an Instrumented Function record that islinked to at least one SIF CommonCause Failure record.

To remove an SIF Common Cause Failure record from an Instrumented Function record:

1. In the Common Cause Failures section, select the row containing the SIF CommonCause Failure record that you want to remove.

2. Click the Remove button.

A confirmationmessage appears, asking if you really want to remove the SIF CommonCause Failure record from the Instrumented Function record.


The link between the SIF CommonCause Failure record and the Instrumented Functionrecord is deleted, and the rows in the sections are updated in the following ways:

l The SIF CommonCause Failure record is removed from the Common Cause Failuresgrid.

l The Instrumented Function record(s) that appeared in the Related Instrumented Func-tions section are removed from the grid.

4. ClickOK.

Your changes are saved, and the Instrumented Function record closes.

About Concurrent Safe State Hazards and Instrumented Function Records


About Concurrent Safe State Hazards and Instru-mented Function RecordsWhen you define an Instrumented Function record, you will define the safe state to the instru-mented function is responsible for taking the process in the event that the process is in an unsafestate. In other words, if a given process is approaching an unsafe condition, the instrumentedfunction that monitors that processwill take the process to a condition that is specified as the safefor that process. For example, if the temperature reaches an unsafe level, the cooling systemwillbe triggered to bring down the temperature to a safe state.

In some cases, if a given process is in its associated safe state at the same time as a different pro-cess, while the individual processes are in a safe state, the combination of these conditions couldtrigger a hazardous event. For example, assume that to reach a safe state in a Flare system, thesteam valve needs to vent. Now assume that two steam valves need to vent at the same time. Inthis case, the Flare system can become overloaded due to both processes reaching their safestates concurrently.

In MeridiumAPM, the combinations of safe states that can lead to hazardous events are referredto as concurrent safe state hazards. You can document the concurrent safe state hazards thatexist for instrumented functions via the Instrumented Function record representing that instru-mented function. In other words, for each instrumented function that participates in a potentiallyhazardous relationship, you will need to define the concurrent safe state hazard(s) for that instru-mented function.

The Concurrent Safe States tab in the <Record ID> (Instrumented Function) window allowsyoumanage all the concurrent safe state hazards that exist for an instrumented function. Todefine concurrent safe state hazards for an instrumented function, you will need to:

l Link the Instrumented Function record to the other Instrumented Function record rep-resenting the instrumented function whose concurrent safe state can cause a hazard.Instrumented Function records can be linked to one or more other Instrumented Functionrecords through the HasHazardous Event relationship.

l Describe the hazardous event that can occur when the safe state conditions occur con-currently. Because some instrumented functions can participate in multiple concurrent safestate scenarios, in each Instrumented Function record, you will need to describe the haz-ardous events that are associated with that instrumented function. In other words, describ-ing the hazardous event in one Instrumented Function record will not automaticallypopulate the linked Instrumented Function record with the same description. You will needto open the linked Instrumented Function record and enter the description of the con-current safe state hazard.

The following image illustrates the records that participate in a concurrent safe state scenario inwhich the combination of three concurrent safe states can lead to a hazardous event.



Notice that the Instrumented Function record to which you link other Instrumented Functionrecords is the predecessor in the relationship. When you are working with Instrumented Functionrecords, it is helpful to refer to the SIS Management datamodel image in which the InstrumentedFunction family is the predecessor family.

The following image showswhat the Concurrent Safe States tab looks like in the <Record ID>(Instrumented Function) window.

Aspects of the Concurrent Safe States Tab in Instrumented Function Records


Aspects of the Concurrent Safe States Tab in Instru-mented Function RecordsTheConcurrent Safe States tab in the <Record ID> (Instrumented Function)window containsthe Hazard for Concurrent Safe States? check box, which indicateswhether the instrumentedfunction represented by the current Instrumented Function record is associated with any hazardsthat result from safe states that occur simultaneously. When the Hazard for Concurrent SafeStates? check box is:

l Selected, the remaining options on the Concurrent Safe States tab are enabled, and amessage appears indicating that youmust link at least one Instrumented Function recordto the current Instrumented Function record. The additional Instrumented Function recordrepresents the instrumented function whose safe state can lead to a hazardous event if itoccurs simultaneously with the safe state for the current instrumented function. After youlink at least one Instrumented Function record to the current Instrumented Function record,themessage is hidden.

l Cleared, the remaining options on the Concurrent Safe States tab are disabled. This indic-ates that the instrumented function represented by the current Instrumented Functionrecord is not associated with any concurrent safe state hazards.

After at least one Instrumented Function record is linked to the current Instrumented Functionrecord, the Hazard for Concurrent Safe States? check box is disabled.

In addition, you can clear this check box only if the Individual Safe State Detail grid is empty (i.e.,there are no concurrent safe state hazards associated with the instrumented function).

Below the Hazard for Concurrent Safe States? check box, the following sections appear:

l Individual Safe State Detail: Contains a grid that displays the list of Instrumented Func-tion records that are linked to the current Instrumented Function record. Each row in thegrid represents one instrumented function whose safe state can lead to a hazardous eventif it occurs simultaneously with the safe state of the current instrumented function. The fol-lowing information is displayed for each Instrumented Function record that appears in thegrid:

n Function ID:The ID for the instrumented function that is stored in the IF ID field inthe corresponding Instrumented Function record. This value appears as a hyperlink,which you can click to view the contents of the corresponding Instrumented Functionrecord.

n Description: The description of the instrumented function that is stored in the IFDescription field in the corresponding Instrumented Function record.

n Safe States: The description of the safe state that is associated with the instru-mented function, which is stored in the Safe State Description field in the cor-responding Instrumented Function record.


n Add Existing: Displays the Find Items window, which you can use to search for an exist-ing Instrumented Function record and link it to the current Instrumented Function record.

Aspects of the Concurrent Safe States Tab in Instrumented Function Records


After you link an Instrumented Function record to the current Instrumented Functionrecord, a new row will appear in the Individual Safe State Detail grid to represent thatinstrumented function.

n Remove:After displaying a confirmationmessage, deletes the link between the selectedInstrumented Function record and the current Instrumented Function record and removesthe instrumented function from the grid. This button is disabled until at least one Instru-mented Function record appears in the Individual Safe State Detail grid.

l Potential Concurrent Safe State Hazard: Contains a field, which stores the description forthe concurrent safe state hazards that are associated with the current instrumented func-tion. This field is required. If the current instrumented function is associated with multipleconcurrent safe state hazards, you should provide a description in this field for each ofthese hazards.

Defining Concurrent Safe State Hazards for Instrumented Functions


Defining Concurrent Safe State Hazards for Instru-mented FunctionsTo define a concurrent safe state hazard for instrumented functions, you will need to:

n Link to one another the Instrumented Function recordswhose associated safe states cancause a hazardous event when they occurs simultaneously.

n Describe in each of the Instrumented Function records the hazardous event that can occurif the safe states associated with the instrumented functions occur simultaneously.

To define a concurrent safe state hazard for an instrumented function:

1. Open the Instrumented Function record for which you want to define a concurrent safestate.

2. Click the Concurrent Safe States tab.

The Concurrent Safe States tab appears.



3. Select the Hazard for Concurrent Safe States? check box.

The remaining options are enabled, and amessage appears, indicating that youmust linkat least one Instrumented Function record to the current Instrumented Function record.



4. In the Individual Safe State Detail section, click the Add Existing button.

The Find Items window appears, and the Search In text box contains Instrumented Func-tion by default.

5. Perform a search for the desired Instrumented Function record.

6. In the search results, select the rows containing the Instrumented Function records thatyou want to link to the current Instrumented Function record, and then click the Open but-ton. Keep inmind the records you select should represent the instrumented functionswhose safe states can lead to a hazardous event if they occur concurrently with the safestate of the current instrumented function.

The Find Items window closes, and the Instrumented Function records that you selectedappears in the Individual Safe State Detail grid.



7. In the Potential Concurrent Safe State Hazard section, enter a description of the haz-ardous event that can occur if the safe states for the instrumented functions in the Indi-vidual Safe State Detail section occur simultaneously with the safe state for the currentinstrumented function.



8. In the Individual Output States section, in the first row in the grid, click the hyperlinked IDin the Function ID cell.

The corresponding Instrumented Function record appears in a new window.


The Concurrent Safe States tab appears. You can see that the Hazard for ConcurrentSafe States? check box is selected automatically and the Individual Safe State Detail gridcontains the Instrumented Function record to which the current record is linked (i.e., therecord fromwhich you accessed the current record).



10. In the Concurrent Hazardous Event section, enter a description for the hazardous eventthat can occur if the safe states associated with the instrumented occur simultaneously.This should be the same description that you entered in step 7.



11. ClickOK.

Your changes are saved, and the Instrumented Function record closes, revealing the pre-vious Instrumented Function record.

12. Repeat steps 8 through 11 for each Instrumented Function record that appears in the Indi-vidual Safe State Detail grid.

13. ClickOK.


Removing Instrumented Functions From the Concurrent Safe States Tab


Removing Instrumented Functions From the Con-current Safe States TabWhen you remove an Instrumented Function from the Concurrent Safe States tab, you are delet-ing the link between the Instrumented Function records.

To remove an instrumented function from the Concurrent Safe States tab:

1. Open the Instrumented Function record fromwhich you want to remove a linked Instru-mented Function record.


The Concurrent Safe States tab appears.

Removing Instrumented Functions From the Concurrent Safe States Tab


3. In the Individual Safe State Detail section, select the row containing the instrumentedfunction that you want to remove.

ŒHint:Youmaywant to update the text stored in theConcurrent Hazardous Eventsec-tion in the corresponding Instrumented Function record before you remove it from the cur-rent record. To do so, click the hyperlinked value in theFunction IDcell in that row.




The link between the selected Instrumented Function record and the current InstrumentedFunction record is deleted, and the instrumented function is removed from the IndividualSafe State Detail grid.

ŒHint: Youmaywant to update the text stored in the Concurrent Hazardous Event sec-tion in the current record.

6. ClickOK.


Adding Existing Instrumented Function Records to the SIL Analysis


Adding Existing Instrumented Function Records to theSIL AnalysisWhen you add an existing Instrumented Function record to an SIL Analysis, you are auto-matically linking that record to the SIL Analysis record for the current SIL Analysis.

To add an existing Instrumented Function record to the SIL Analysis:


2. In the Instrumented Functions section, below the grid, click the Add Existing Functionsbutton.

The Find Items window appears, where you can search for an existing Instrumented Func-tion record.

3. If desired, in the Look For text box, type the desired search criteria, and click the Find Nowbutton.

The search results appear and contain only the Instrumented Function records that are notcurrently linked to an SIL Analysis.

Adding Existing Instrumented Function Records to the SIL Analysis


4. In the search results, select the row containing the record that you want to add to the ana-lysis.


The Find Itemswindow closes, and the selected record is linked to the SIL Analysis recordfor the current SIL Analysis and appears in the Instrumented Functions grid.

Copying Existing Instrumented Function Records


Copying Existing Instrumented Function RecordsWhen you copy an existing Instrumented Function record, you are creating a new InstrumentedFunction record that is populated with the values from the record that was copied and auto-matically linking it to the SIL Analysis record for the current SIL Analysis. The values in all thefields from a selected record will be copied to the new recordswith the exception of the followingfields:

l IF ID

l Hazards Analysis Date

l Hazards Analysis Reference

l Hazards Analysis Reference Key

To copy an Instrumented Function record:

1. Access the Instrumented Functions page.

2. In the Instrumented Functions section, select the row containing the Instrumented Func-tion record that you want to copy.

3. Below the Instrumented Functions grid, click the Copy Function button.

A new Instrumented Function record appears that is populated with information from thesource record.

4. In the IF ID field, type the ID for the instrumented function.

5. Modify the values in the remaining fields as desired.

6. ClickOK.

The record is saved and appears in the Instrumented Functions section.

Modifying Existing Instrumented Function Records


Modifying Existing Instrumented Function RecordsTo modify an existing Instrumented Function record:


2. In the Instrumented Functions grid, locate the row containing the Instrumented Functionrecord whose contents you want to modify.

The Instrumented Function record appears in a new window.

3. Modify the record as desired.

4. ClickOK.

The record closes, and your changes are saved.

About Assessing the SIL Level for Instrumented Functions


About Assessing the SIL Level for Instrumented Func-tionsBefore the SIL Analysis team canmake recommendations for actions that should be taken tomit-igate risk for a given safety instrumented system, the teammust first assign a numeric rating toeach instrumented function within that safety instrumented system. The safety integrity level(SIL) is a numeric value that represents an overall rating for the instrumented function. This ratingtells you to what degree the instrumented function ismeeting its requirements tomitigate risk.After you have assigned an SIL value to each instrumented function within a safety instrumentedsystem, the combination of these values indicates overall safety integrity of the safety instru-mented system to which the instrumented functions belong.

You can use the followingmethods to assess the SIL value for an instrumented system:

l Risk Matrix: Lets you use the standardMeridiumAPMRisk Assessment interface toselect the risk rank values for specific categories of risk. Thehighest risk rank value that youselect in the RiskMatrix is used to determine the SIL value for that instrumented function.You can use the baseline RiskMatrix or a customRiskMatrix.

l Layer of Protection Analysis (LOPA): Lets you evaluate on a granular level the risk valueassociated with a given risk for the instrumented function to determine the SIL value that isassociated with each risk. The highest SIL value that is assigned to a given risk is used todetermine the SIL value of the instrumented function with which those risks are associated.

l Hazards Analysis Risk Assessment: Lets you select an existing Risk Assessmentrecord that is associated with a Hazards Analysis record to which the Instrumented Func-tion record is linked. The existing risk rank valueswill be used to determine the SIL valuefor that instrumented function automatically.

You can usemore than one risk assessment method to determine the SIL value for a given instru-mented function and then compare the results of the different methods. If you usemore than onerisk assessment method, however, only one of the resulting SIL values can exist in the SelectedSIL Level field in the Instrumented Function record. To indicate whether the SIL value will bedetermined by the RiskMatrix, LOPA, or Hazards Analysis Risk Assessment method, you canselect the corresponding value in the SIL Assessment Method field in the Instrumented Functionrecord. For example, if you select the value RiskMatrix - Internal in the SIL Assessment Methodfield, the SIL value determined by the RiskMatrix assessment method will appear in the SelectedSIL Level field.

In addition to the Select SIL Level field, SIL values are also displayed in the Selected SIL Levelcolumn in the Instrumented Functions section on the Instrumented Functions (IFs) page. Afteran SIL value exists for an instrumented function, the SIL Analysis team canmake recom-mendations for actions that should be taken tomitigate the risk associated with that instrumentedfunction, if necessary. They can do so using Risk Assessment Recommendation records.

For example, assume you have conducted a LOPA for the Instrumented Function record IF -1001, and the SIL value is 4. In this case, your SIL Analysis teammight want to create a RiskAssessment Recommendation record that contains a recommendation for adding an additionallayer of protection to that instrumented function.

SIL Level and Required Probability of Failure


SIL Level and Required Probability of FailureThe required probability of failure is a number representing the probability that an instrumentedfunction will fail in a dangerous scenario. This value is represented as a probability value (e.g.,.001) and is an indicator of whether the instrumented function ismeeting its requirements tomit-igate risk.

The required probability of failure is defined in the Required Probability of Failure field in theInstrumented Function record. The required probability of failure value is based upon the fol-lowing values stored in the Instrumented Function record:

l The SIL value, which is stored in the Selected SIL Level field. The higher the SIL value foran instrumented function, the lower the probability that the instrumented function will fail.

l Themethod used to determine the SIL value, which is stored in the SIL AssessmentMethod field (e.g., RiskMatrix).

l The demand rate, which is stored in the SILMode field and represents how frequently theinstrumented function will be needed to protect the safety instrumented system as a resultof a failure (i.e., Low Demand, High Demand, or Continuous).

Depending upon these values in other fields, this field is either disabled and populated auto-matically or enabled so that you can type a valuemanually. The following sections define how therequired probability of failure is calculated for each demand rate.

High Demand and Continuous

In an Instrumented Function record, when the value in the SILMode field is High Demand orContinuous demand, theMeridiumAPM system assumes that the demand rate of the instru-mented functionmore frequent than once per year. In these cases, the failure rate ismeasuredby the average probability of dangerous failures per hour (PFH). The required probability of fail-ure is defined by an industry standard that is associated with the SIL. The following table containsthe standard PFH values for each SIL.



S-a-f-e-t-y-

Integrity

L-e-v-e-l

(-S-I-L-)

Required Probability ofFailure (PFH)

4 10-9to 10-8

3 10-8to 10-7

2 10-7to 10-6

1 10-6to 10-5

If you use an internal RiskMatrix to determine the SIL value, the value in the Required Probabilityof Failure field on the Instrumented Function datasheet will be populated automatically with thelowest (i.e., themost conservative) value as the targeted probability and disabled. For example, ifthe SIL is 2, the Required Probability of Failure field will be populated automatically with 1E-07(i.e., 10-7).

If you use an internal Layer of Protection Analysis to determine the SIL value, the value in theRequired Probability of Failure field is disabled and populated automatically with the differencebetween the values in theMitigated Consequence Frequency field and the RequiredMitigatedConsequence Frequency field in the LOPA record.

If you use an SIS Assessment Method other than an internal Layer of Protection Analysis or RiskMatrix (e.g., LOPA - External), the Required Probability of Failure field will be enabled, and youcan type the probability valuemanually. In this case:



l If youmodify the value in the Selected SIL Level field, the value in the Required Probabilityof Failure field will be updated automatically to fall within the correct range of values for thatlevel.

l If you type a value that does not fall within the range defined in the table, an error messagewill appear.

l If you type a value in the Required Probability of Failure field without first typing a value inthe Selected SIL Level field, an error message will appear.

Low Demand

In an Instrumented Function record, when the value in the SILMode field is Low Demand, theMeridiumAPM system assumes that the demand rate of the instrumented function is less fre-quent than once per year. In this case, the failure rate ismeasured by the average probability offailure on demand (PFD Avg).

In these cases, a risk reduction factor can also be used to indicate the probability of failure for aninstrumented function. The risk reduction factor is the inverse of the required probability of failure,which is represented in years in cases of low demand. For example, a required probability of fail-ure value of .001 would equal a risk reduction factor of 1,000, meaning that the instrumented func-tion would fail during a dangerous scenario about every 1,000 years.

The required probability of failure is defined by the industry standard that is associated with eachSIL. The following table contains the standard PFD Avg values for each SIL.



S-a-f-e-t-y-

Integrity

L-e-v-e-l

(-S-I-L-)

RequiredProbabilityofFailure(PFDAvg) Target Risk Reduction Factor

4 10-5to 10-4 10,000 to 100,000

3 10-4to 10-3 1,000 to 10,000

2 10-3to 10-2 100 to 1,000

1 10-2to 10-1 10to 10

If you use an internal RiskMatrix to determine the SIL value, the Required Probability of Failurefield on the Instrumented Function datasheet will be disabled and populated automatically withthe lowest (i.e., themost conservative) value as the targeted probability. For example, if the SIL is3, the Required Probability of Failure field will be populated automatically with 0.001 (i.e., 10-3).The value in the Risk Reduction Factor field is the inverse of value in the Required Probability ofFailure field, so for an SIL of 3, the Risk Reduction field on the Instrumented Function datasheetwill be disabled and populated automatically with 1,000 (i.e., the inverse of 0.001). In otherwords, for an SIL value of 3, the instrumented function should not fail more than once every 1,000years.

If you use an internal Layer of Protection Analysis to determine the SIL value, the Required Prob-ability of Failure field is populated automatically in the sameway aswhen the demand rate is HighDemand or Continuous. The value in the Risk Reduction Factor field, however, is now populatedautomatically with the inverse of value in the Required Probability of Failure field.



For an SIL Assessment Method other than an internal RiskMatrix or Layer of Protection Analysis (e.g., LOPA - External), the Required Probability of Failure field and the Risk Reduction field willbe enabled, and you can type a value into those fieldsmanually. The same restrictions apply inthis case aswhen the demand rate is High Demand or Continuous but with the following addi-tional logic:

l If youmodify the value in the Required Probability of Failure field, the value in the RiskReduction Factor field will be populated automatically with the inverse of the value in theRequired Probability of Failure field.

l If youmodify the value in the Risk Reduction field, the value in the Required Probability ofFailure field will be populated automatically with the inverse of the value in the Risk Reduc-tion field.

About Assessing SIL Values Via the Risk Matrix


About Assessing SIL Values Via the Risk MatrixWhen you assess a SIL value for an instrumented function via the RiskMatrix, you will use theRisk Assessment interface to create a Risk Assessment record and link it to the InstrumentedFunction record representing that instrumented function.

Specifically, you will use the RiskMatrix on the Risk Assessment interface to select a risk rankvalue for each risk category that is defined in that RiskMatrix. After you select risk rank values inthe RiskMatrix, the sum of the unmitigated risk rank values that you selected (i.e., the overallunmitigated risk rank) is used to determine the SIL value for that instrumented function. Thisvalue is stored in the Unmitigated Risk Ranktext box above RiskMatrix on the Risk AssessmentInterface.

SIL values are stored in the SIL Level field in SIL Threshold records. SIL Threshold records alsostore numeric ranges, which correspond to risk rank values that appear in the RiskMatrix. TheMeridiumAPMbaseline database contains SIL Threshold records that you can use for this pur-pose. The overall unmitigated risk rank value will be compared to the ranges that are defined inthe SIL Threshold records. The SIL value that corresponds to the range in which the overall unmit-igated risk rank value falls is assigned to the instrumented function.

For example, assume that the following SIL Threshold record exists, where the numeric range is100 - 1000 with a corresponding SIL value of 2.

In this case, if the overall unmitigated risk rank value is 500, a SIL value of 2 would appear in theSelected SIL Level field in the Instrumented Function record.

Accessing the Risk Assessment Interface


Accessing the Risk Assessment InterfaceThe following instructions provide details on accessing the Risk Assessment interface to selectrisk rank values.When you select risk rank values via the Risk Assessment interface, you are cre-ating a Risk Assessment record and linking it to the selected Instrumented Function record.

To access the Risk Assessment interface:


2. In the Instrumented Functions section, select the row containing the instrumented func-tion whose risk rank values you want to assess.

3. On the Assessment Tasks menu, click the Risk Matrix link.

The Risk Analysis dialog box appears, displaying the Risk Assessment interface.

At this point, you can follow the standard procedure for assessing risk via the RiskMatrix,and then click the Save button.

The Risk Assessment record will be linked to the selected Instrumented Function record,and the SIL Level value will be calculated automatically and displayed in the Selected SILLevel cell in the currently selected row.

About Assessing SIL Values via a Hazards Analysis Risk Assessment


About Assessing SIL Values via a Hazards AnalysisRisk AssessmentIf you have already performed risk assessments for a Hazards Analysis via the Hazards Analysismodule, you can use one of those risk assessments to assess the SIL value for an instrumentedfunction. Before you can use a risk assessment from aHazards Analysis, youmust:

1. Link the Instrumented Function record to the Hazards Analysis record that is associatedwith the risk assessment that you want to use.

2. In the SIL Assessment Method field in the Instrumented Function record, select PHA-Internal.

After you have completed these steps, on the Assessment Tasks menu, you can click the RiskMatrix link to select which Risk Assessment record you want to use and then view its details onthe PHA Risk Assessment window.

About Mapping Values from aHazards Analysis


About Mapping Values from a Hazards AnalysisWhen you assess the SIL value for an instrumented function using a Hazards Analysis RiskAssessment, you will select a Risk Assessment record that has been previously defined for a Haz-ards Analysis and use it to assess risk for that instrumented function.

The risk rank values and RiskMatrix that have been defined for that risk assessment aremappedto corresponding fields on the PHA Risk Assessment window. The risk rank values on the PHARisk Assessment window are used to determine the SIL value in the sameway risk rank valuesfrom the standard Risk Assessment interface are used to determine the SIL value, with the fol-lowing exceptions:

l The risk rank values on the PHA Risk Assessment window are already defined and can-not bemodified.

l The overall unmitigated risk rank value is not always used to determine the SIL value. TheMeridiumAPM system determineswhich risk rank values to use based upon the followingcriteria:

n If the risk from the Hazards Analysis has not beenmitigated, the sum of the unmitigatedrisk rank values is used to calculate the SIL value in the sameway as the values are cal-culated using the standard Risk Assessment interface.

n If the risk from the Hazards Analysis has beenmitigated, then the sum of themitigated riskrank values from the risk assessment (i.e., the overall mitigated risk rank) is compared tovalues in SIL Threshold records to determine the SIL value. The overall mitigated risk rankvalue is displayed in theMitigated Risk Rank text box above the RiskMatrix on the PHARisk Assessment window.

In addition, after you select a Risk Assessment record from aHazards Analysis, certain valuesthat are stored in fields in Hazards Analysis Cause and Hazards Analysis Consequence recordsfrom that Hazard Analysis are copied to corresponding fields in the Instrumented Functionrecord. The following table lists the families and fields in the Hazards Analysismodule that storethese values and the field in the Instrumented Function record to which they aremapped.

Hazard Analysis Family Hazard Analysis Field Instrumented Function Field

Hazard Analysis Cause Cause Type Initiating Event

Hazard Analysis Cause Cause Description Initiating Event Description

Hazard Analysis Cause Cause Frequency (per year) Frequency of Initiating Event(per yr)

Hazard Analysis Con-sequence

Consequence Type Hazardous Event

Hazard Analysis Con-sequence

Consequence Description Consequence Description

Selecting a Risk Assessment Record from aHazards Analysis


Selecting a Risk Assessment Record from a HazardsAnalysisTo use risk ranks that were defined in a Risk Assessment record in a Hazards Analysis, youmustaccess the PHA Risk Assessment window instead of the standard Risk Assessmentinterface.The following instructions assume that the Instrumented Function record for which youare assessing risk is linked to a Hazards Analysis record and contains the valuePHA - Internal inits SIL Assessment Method field.

To select an existing Risk Assessment record from a Hazards Analysis:

1. On the Instrumented Functions page, select the Instrumented Function record for whichyou want to define risk ranks using an existing Risk Assessment record from aHazardsAnalysis.

2. On the Assessment Tasks menu, click the Risk Matrix link.

The Search Tool appears. The Search In list is populated automatically with the RiskAssessment family, the Linked To list is populated automatically with the Hazards Ana-lysis Consequence family, and the Through list is disabled and populated automaticallywith the HasRisk family.



3. Click the Find Now button.

The search results display all the Risk Assessment records that are linked to a HazardsAnalysis Consequence record though the HasRisk relationship family.

Note: Only Risk Assessment records that are associated with the Hazards Analysisrecord to which the selected Instrumented Function record is linked will appear in thesearch results.

4. Select the row containing the Risk Assessment record whose risk rank values you want touse, and then click theOpen button.

The PHA Risk Assessment window appears, displaying the read-only risk assessmentfrom the Hazards Analysis. In the Instrumented Function record, the values in the followingfields are calculated and populated automatically according to the risk rank values stored inthe Risk Assessment record:

l Selected SIL Level

l Required Probability of Failure

l RiskReduction Factor (RRF)



5. Click the button to close the PHA Risk Assessment window.

Aspects of the PHA Risk Assessment Window


Aspects of the PHA Risk Assessment WindowThe PHA Risk Assessment window functions the same as the standard Risk Assessment inter-face, with some exceptions:

l TheRiskMatrix and risk rank values are populated automatically with the correspondingvalues from the Risk Assessment record that is associated with the Hazards Analysis.

l TheRiskMatrix is disabled, and you cannot make changes to the risk rank values. If youwant to make changes to the risk rank values, you will need to do so from the source Haz-ards Analysis, and then select the Risk Assessment record again via the SIS Managementmodule.

l If the Risk Assessment record is linked to a Hazards Analysis Safeguard record that is alsoan Independent Protection Layer (IPL), the PHA Risk Assessment window will containthe IPL Information section. Otherwise, this section is hidden.

l The following values are populated automatically from aRisk Assessment record from aHazards Analysis:

n Unmitigated Risk Rank

n Mitigated Risk Rank

n RiskMatrix

l If you select a Risk Assessment record from aHazards Analysis that includes safeguardsthat are independent protection layers (IPLs), the PHA Risk Assessment window con-tains an additional sections: IPL Information.

The following items appear on the PHA Risk Assessment window:

l Unmitigated Risk Rank text box: Displays the unmitigated risk rank value stored in theRisk Assessment record that is linked to the Hazards Analysis record. This text box is dis-abled.

l Mitigated Risk Rank text box: Displays themitigated risk rank value stored in the RiskAssessment record that is linked to the Hazards Analysis record. This text box is disabled.

l Risk Matrix: Displays the RiskMatrix from the Risk Assessment record for the HazardsAnalysis as read-only.

l PIF Information section: Displays values from the Instrumented Function record for whichyou are assessing risk. All the fields in this section are disabled and populated auto-matically with existing values from the corresponding fields in the Instrumented Functionrecord with the following exceptions:

n The value in the SIL Level text box is calculated automatically based on the unmit-igated andmitigated risk rank valueswhen you open the PHA Risk Assessmentwindow for the first time and then gets copied to the Selected SIL Level field in theInstrumented Function record. After the value is calculated initially, it will be stored inthe Instrumented Function record.

n The Initiating Event text box, Hazardous Description text box, and ConsequenceDescription text box are populated automatically with values that are stored in fields

Aspects of the PHA Risk Assessment Window


in Hazards Analysis Cause and Hazards Analysis Consequence records from theHazard Analysis.

l IPL Information section: Displays values that are stored in the Independent ProtectionLayer records and Hazards Analysis Safeguard records that are used to determine themit-igated risk rank in the Hazards Analysis. This section appears on the PHA Risk Assess-ment windowonly if the source Hazards Analysis includesHazards Analysis Safeguardrecords that are IPLs. Otherwise, this section is hidden. The IPL Information section con-tains the following items:

n IPL List: Displays the list of Hazards Analysis Safeguard records that are classified asIPLs and linked to the Hazards Analysis Consequence record. You can select one of theserecords in the list to view itsmitigated risk details in the Risk grid.

n Safeguard ID: This cell is disabled and populated automatically with the value that isstored in the Safeguard ID field in the Hazards Analysis Safeguard record.

n Equipment ID: This cell is disabled and populated automatically with the value that isstored in the Equipment ID field in the Equipment record to which the Hazards AnalysisSafeguard record is linked.

n IF ID: This cell is disabled and populated automatically with the value that is stored in the IFID field in the Hazards Analysis Safeguard record.

n Safeguard Type: This cell is disabled and populated automatically with the value that isstored in the Safeguard Type field in the Hazards Analysis Safeguard record.

n Safeguard Description: This cell is disabled and populated automatically with the valuethat is stored in the Safeguard Description field in the Hazards Analysis Safeguard record.

n Risk grid: Displays in grid format themitigated and unmitigated risk ranks for each RiskMatrix category (e.g., environment) and the overall unmitigated andmitigated risk ranksassociated with the IPL that is selected in the IPL List.

n IPL Credits: This value is disabled and populated automatically with the value that isstored in the IPL Credits field in the Independent Protection Layer record that is linked tothe Hazards Analysis Safeguard record that is selected in the IPL List. This numberrepresents the amount bywhich the risk is reduced because of that IPL.

n IPL Type: This value is disabled and populated automatically with the value that is stored inthe IPL Type field in the Independent Protection Layer record that is linked to the HazardsAnalysis Safeguard record that is selected in the IPL List. This cell can contain one of thefollowing values:

o Consequence Reducing IPLs: Reduce the severity of the failure (e.g., fatality toinjury).

o Frequency Reducing IPLs: Reduce how often the failures occur (e.g., every 100years to every 1,000 years).

What is a Layer of Protection Analysis (LOPA)?


What is a Layer of Protection Analysis (LOPA)?A Layer of Protection Analysis (LOPA) is type of risk assessment, which lets you determine theSIL value that is associated with the protective instruments that exist to mitigate the same risks forwhich the instrumented function exists. When you use an LOPA to assess the SIL value for aninstrumented function, you examine the granular portions of the a scenario and assess the riskassociated with each portion, and then those individual risk values are used to calculate the SILvalue for the instrumented function.

You can conduct one LOPA per risk that is associated with an instrumented function. After youhave conducted a LOPA for all the desired risks, the highest SIL value will be used to calculatethe SIL for that instrumented function.

A LOPA consists of one LOPA record and all the records that are linked to that record. For moredetails on how the LOPA family participates in the SIS Management datamodel, see the illus-tration of the datamodel where the Instrumented Function family is the predecessor.

When you conduct an LOPA, you will complete the following steps:

1. Create one LOPA record to define the risk that you are assessing.

2. Create one Independent Layer of Protection record per independent layer of protectionthat exists to mitigate the risk defined in the LOPA record.

3. Create one ConsequenceModifier record per consequencemodifier that is associatedwith the risk defined in the LOPA record.

After you complete these steps, the SIL value will be calculated automatically based on the prob-ability values defined in the Independent Layer of Protection records and ConsequenceModifierrecords.

NavigationMenu


Navigation Menu

TheNavigationmenu appears on the following pageswhen you are working with a LOPA:

l LOPA Definition

l Consequence Modifiers

In addition to these pages, the Navigation menu provides to the Instrumented Functions (IFs)page. A green arrow to the left of an option indicates the page that you are currently viewing. TheNavigation menu contains the following links:

l LOPA Definition: Displays the LOPA Definition page, where you canmanage LOPArecords and Independent Layers of Protection records.

l Modifiers: Displays the Consequence Modifiers page, where you canmanage Con-sequenceModifier records.

l Return to Functions: Displays the Instrumented Functions (IFs) page, where you canmanage Instrumented Function records.

Common Tasks


Common Tasks

TheCommon Tasks menu appears on the following pageswhen you are working with a LOPA:

l LOPA Definition

l Consequence Modifiers

The Common Tasks menu contains the following links:


l Reports: Displays a submenu that contains the caption of the Catalog itemLOPA Reportas a link. This link is enabled only if you are viewing an existing LOPA record on the LOPADefinition page. This link does not appear on the Consequence Modifiers page.

l Help: Displays the context-sensitive help topic for the current page.

About LOPA Records


About LOPA RecordsLOPA records store details about the LOPA that you are conducting to determine the SIL valuefor a risk that is associated with an instrumented function. When you create a LOPA record, it willbe linked to the Instrumented Function record that is currently selected on the InstrumentedFunctions (IFs)page.

LOPA records can be linked to records in the following families:

l Consequence Modifier: Stores details about the consequences of the risk described inthe LOPA record.

l Independent Layer of Protection: Stores details about the independent layers of pro-tection that exist to mitigate the risk associated with the consequences described in theConsequenceModifier records. Independent Layer of Protection records can be linked toEquipment and Functional Location records, which store details about the equipment orlocation with which the independent layers of protection are associated.

These families also store numeric values that present probability and failure rates. These valuesare used to calculate the SIL value of the Instrumented Function whose risks you are assessingthrough the LOPA. The calculated SIL value is stored in the Calculated SIL field in the LOPArecord.

When you create a LOPA record, you will define the following items in the record:

l The risk for which you are conducting the Layer of Protection Analysis (LOPA).

l The consequences that may occur if that risk is not prevented from proceeding into anundesirable scenario.

l The events or conditions that can initiate the undesirable event.

l How often the event may occur.

l How often it is acceptable for the event to occur.

Accessing the LOPA Definition Page


Accessing the LOPA Definition PageOn the LOPA Definition page, you can create the following items:

l One LOPA record.

l One or more Independent Layer of Protection records.

Additionally, via the LOPA Definition page, you can access the Consequence Modifiers page,where you can create one or more ConsequenceModifier records.

The following instruction provide details on accessing the LOPA Definition page for a new LOPArecord. You can also access the LOPA Definition page by opening an existing LOPA record.

To access the LOPA Definition page:


2. In the Instrumented Functions section, select the row containing the Instrumented Func-tion record for which you want to conduct the LOPA.

3. In the Associated Risk Assessments section, click the Create New LOPA button.

Aspects of the LOPA Definition Page


Aspects of the LOPA Definition PageThe LOPA Definition page contains the following items:

l Datasheet area: Contains the LOPA datasheet for the current LOPA record.

l Independent Protective Layers section: Contains a grid that displays a list of IndependentLayer of Protection records that are linked to the LOPA record whose datasheet is dis-played in the datasheet area. Each row in the grid represents one Layer of Protectionrecord. For each record that appears in the grid, the following information is displayed:

n Sequence Number: The value that exists in the Sequence Number field in the Independ-ent Layer of Protection record.

n IPL ID: The value that exists in the IPL ID field in the Independent Layer of Protectionrecord.

n Description: The value that exists in the Description field in the Independent Layer of Pro-tection record.

n Type: The value that exists in the Type field in the Independent Layer of Protection record.

n PFD: The value that exists in the PFD field in the Independent Layer of Protection record.


n Add New IPL: Displays a new blank Independent Layer of Protection record in a new win-dow.

n Delete IPL: Displays a confirmationmessage, and then deletes the selected IndependentLayer of Protection record.

You can collapse and expand the Independent Protective Layers section using the following but-tons, which appear on the top right corner of the section in turn:

: Indicates that the section is expanded. You can click this button to collapse the section.

: Indicates that the section is collapsed. You can click this button to expand the section.

The LOPA Definition page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Creating LOPA Records


Creating LOPA RecordsTo create a LOPA record:

1. Access the LOPA Definition page.

2. In the datasheet area, on the Definition tab, provide values for the fields as desired. Notethat the LOPA ID field is required.

3. Click the Details tab.

The Details tab appears.

4. Provide values for the fields as desired. Note that the following fields are required:

l Frequency of Initiating Event

l RequiredMitigated Consequence Frequency

5. Above the datasheet, click the Save button.


Opening Existing LOPA Records


Opening Existing LOPA RecordsTo open an existing LOPA record:


2. In the Instrumented Functions section, select the row containing the Instrumented Func-tion record to which the desired LOPA record is linked.

3. In the Associated Risk Assessments section, locate the LOPA record that you want toopen.

4. In the LOPA ID cell, click the hyperlinked Record ID for the desired record.

The selected LOPA record appears on the LOPA Definition page. At this point, you canmodify the LOPA record, create Independent Layer of Protection records, and access theConsequence Modifiers page.

Adding Existing LOPA Records to the Associated Risk Assessments Grid


Adding Existing LOPA Records to the Associated RiskAssessments GridThe following instructions provide details on searching for an existing LOPA record to link to anInstrumented Function record. When you search for LOPA records, the search results will con-tain only LOPA records that are not already linked to an Instrumented Function record.

To add an existing LOPA record to the Associated Risk Assessments grid:


2. In the Instrumented Functions section, select the row containing the Instrumented Func-tion record to which you want to link the LOPA record.

3. Below the Associated Risk Assessments section, click the Add Existing LOPA button.


4. Provide the desired search criteria, and then click the Find Now button.


Adding Existing LOPA Records to the Associated Risk Assessments Grid


5. In the search results, select the row containing the LOPA record that you want to link to theselected Instrumented Function record, and then click the Open button.

The LOPA record is linked to the Instrumented Functions record and appears in the Asso-ciated Risk Assessments section.

Copying LOPA Records to Create New Ones


Copying LOPA Records to Create New OnesWhen you copy a LOPA record to create a new one, you are creating a new LOPA record that ispopulated with information from the source record. If the source LOPA record is linked toIndependent Layer of Protection records or ConsequenceModifier records, those recordswillnot be linked to the new LOPA record.

To copy a LOPA record and create a new one:



3. In the Associated Risk Assessments section, select the row containing the LOPA recordthat you want to copy.

4. Click the Copy LOPA button.

A new LOPA record appears on the LOPA Definition page and is populated automaticallywith information from the source record.

5. In the datasheet area, in the LOPA ID field on the Definition tab, type an ID for the LOPA.This field is required.


The record is saved. At this point you can, link the LOPA record to Independent Layer ofProtection records and ConsequenceModifier records.

Removing LOPA Records from the Associated Risk Assessments Grid


Removing LOPA Records from the Associated RiskAssessments GridWhen you remove a LOPA record from the Associated Risk Assessments grid on the Instru-mented Functions (IFs) page, you are deleting the link between the Instrumented Functionrecord and the LOPA record, and the LOPA record will no longer be associated with the currentSIL Analysis.

To remove a LOPA record from the Associated Risk Assessments grid:



3. In the Associated Risk Assessments section, select the row containing the LOPA recordthat you want to remove.

4. Click the Remove LOPA button.

A confirmationmessage appears, asking if you really want to remove the LOPA recordfrom the SIL Analysis.


The LOPA record is removed from the Associated Risk Assessments grid.

About Independent Layer of Protection Records


About Independent Layer of Protection RecordsAn independent layer of protection is a device, system, or action that exists to prevent a risk and isindependent of the event that initiates the scenario. An independent layer of protection is externalto any other layer of protection or safety instrumented system. The effectiveness of an inde-pendent layer of protection is quantified in terms of its probability of failure data (PFD), which is anumeric value that represents the probability that the independent layer of protection will fail toperform its specified function on demand.

Independent Layer of Protection records store details on probability and failure rate data for anindependent layer of protection.When you create an Independent Layer of Protection record,you are defining the item that helpsmitigate a risk, which is alsomitigated by the instrumentedfunction. By defining these items, you canmore accurately assess the SIL value that is asso-ciated with a given instrumented function because you are taking into account all themitigatingfactors that exist for that risk.

You can use the values in the Type list to populate an Independent Layer of Protection recordautomatically with values from an IPL Type record. IPL Type records are provided in the baselinedatabase and can defined by an SIS Administrator or SIS Engineer.

You should create one Independent Layer of Protection record per layer of protection that exists.Via the Independent Layer of Protection datasheet, you can link the Independent Layer of Pro-tection record to the Equipment or Functional Location record that represents the equipment orlocation for which the layer of protection exists.

You canmanage Independent Layer of Protection records via the Independent Protective Lay-ers section on the LOPA Definition page.

Creating Independent Layer of Protection Records


Creating Independent Layer of Protection RecordsWhen you create an Independent Layer of Protection record, you are automatically linking thatrecord to the LOPA record with which you are currently working. The following instructionsprovide details on creating a new Independent Layer of Protection record. These instructionsassume that you are familiar with the fields in Independent Layer of Protection records and thatyou want to use a value in the Type list to populate the record automatically.

To create an Independent Layer of Protection record:

1. Open the LOPA record to which you want to link the Independent Layer of Protectionrecord.

2. At the bottom of the Independent Protective Layers section, click the Add New IPL but-ton.

A new blank Independent Layer of Protection record appears in a new window.

3. In the IPL ID field, type an ID for the record.

4. In the Type list, select the desired IPL type.

The Description field is populated automatically with the value stored in the Descriptionfield in the corresponding IPL Type record, and if the IPL type is associated with a:

l Fixed PFD value, the PFD field is disabled and populated automatically with the valuestored in the Default Value field in the corresponding IPL Type record.

l PFD range, the PFD field is required.

5. If the PFD field is required, enter a value in the PFD cell.

Creating Independent Layer of Protection Records


If the value does not fall within the specified PFD range, amessage will appear, indicatingthat the value you entered is not valid, and you will need to specify a value that is within thespecified range.

6. In either the Functional Location or Equipment ID field, click the button.

The Find Items window appears, and the Search In text box is populated automaticallywith either Functional Location or Equipment, depending upon the field fromwhich youaccessed the Find Items window.

7. Perform a search for the desired Equipment or Functional Location record.

8. Select the desired record, and then click the Open button.

The Record ID for the selected record appears in the Functional Location or Equipment IDfield, depending upon the family to which the record belongs.

9. ClickOK.

The record is saved and appears in the Independent Protective Layers grid.

Deleting Independent Layer of Protection Records


Deleting Independent Layer of Protection RecordsWhen you delete an Independent Layer of Protection record, you are deleting the link betweenthe Independent Layer of Protection record and the LOPA record to which it is linked and deletingthe Independent Layer of Protection record from theMeridiumAPMdatabase.

To delete an Independent Layer of Protection record:

1. Open the LOPA record that is linked to the Independent Layer of Protection record that youwant to delete.

2. In the Independent Protective Layers grid, select the row containing the IndependentLayer of Protection record that you want to delete.

3. At the bottom of the Independent Protective Layers section, click the Delete IPL button.

A confirmationmessage appears, asking if you really want to delete the Independent Layerof Protection record.


The selected record is deleted and removed from the Independent Protective Layers grid.

About ConsequenceModifier Records


About Consequence Modifier RecordsA consequencemodifier is an action or event, which can increase the probability that a riskmayoccur if the action is not mitigated and proceeds into an undesirable event. Details about a con-sequencemodifier are stored in ConsequenceModifier records, which are linked to LOPArecords.When you define a ConsequenceModifier record, you are defining the event or actionthat exists within a risk scenario and increases the probability or severity of the undesirable out-come that may occur as a result of that scenario.

For example, assume that the SIL Analysis team is conducting an LOPA to investigate the riskscenario, illustrated in the following diagram, where each box represents a portion of the scen-ario, and each label indicates the family that stores that information:

When Valve A-1001 fails, flammable gas is released into an explosive atmosphere, and if theflame ignites, causing a vapor cloud explosion in the vicinity of the operator, it could cause a fatalinjury.

In this risk scenario, the fatal injury is consequence of the valve failure, and the following events oractions are the consequencemodifiers:

l The flame igniting

l The vapor cloud exploding

l The operator being in the vicinity of the explosion

Because these actions and events appear within the risk scenario, the probability associated withthe consequence occurring is increased exponentially. In other words, if the operator was not inthe vicinity of the blast, the probability of fatal injury would be less. By examining the granularevents that are associated with a risk, the SIL Analysis team canmore accurately assess the SILvalue for the instrumented function.

Accessing the ConsequenceModifiers Page


Accessing the Consequence Modifiers PageTheConsequence Modifiers page lets youmanage the ConsequenceModifier records that arelinked to a given LOPA record.

To access the Consequence Modifiers page:

1. Open the desired LOPA record on the LOPA Definition page.

2. On the Navigationmenu, click theModifiers link.

The Consequence Modifiers page appears.

Aspects of the ConsequenceModifiers Page


Aspects of the Consequence Modifiers PageTheConsequence Modifiers page displays a grid, which contains a list of ConsequenceModifierrecords that are linked to the LOPA record with which you are currently working. Each row in thegrid represents one ConsequenceModifier record. For each ConsequenceModifier record in thegrid, the following information is displayed:

l Consequence Modifier ID: The value that exists in the ConsequenceModifier ID field inthe ConsequenceModifier record. This value appears as a hyperlink, which you can use toopen the ConsequenceModifier record.

l Description: The value that exists in the Description field in the ConsequenceModifierrecord.

l Probability: The value that exists in the Probability field in the ConsequenceModifierrecord.

l Type: The value that exists in the Type field in the ConsequenceModifier record.


l Add New Modifier: Displays a new blankConsequenceModifier record in a new window.

l Remove Modifier: Displays a confirmationmessage, and then removes the ConsequenceModifier record from the grid.

The Consequence Modifier page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Creating New ConsequenceModifier Records


Creating New Consequence Modifier RecordsWhen you create a ConsequenceModifier record, you are linking that record to the LOPA recordwith which you are currently working.

To create a new Consequence Modifier record:

1. Access the Consequence Modifier page.

2. Below the grid, click the Add New Modifier button.

A new blankConsequenceModifier record appears.

3. Provide values in the fields as desired. Note that the following fields are required:

l ConsequenceModifier ID

l Probability

4. ClickOK.

The record is saved and appears in the grid.

Removing ConsequenceModifier Records from the ConsequenceModifiers Grid


Removing Consequence Modifier Records from theConsequence Modifiers GridWhen you remove a ConsequenceModifier record from the Consequence Modifiers grid, youare deleting the ConsequenceModifier record from theMeridiumAPMdatabase and the linkbetween the ConsequenceModifier record and the LOPA record to which it is linked.

To remove a Consequence Modifier record from the Consequence Modifiers grid:

1. Access the ConsequenceModifiers page.

2. In the grid, select the row containing the ConsequenceModifier record that you want toremove.

3. Below the grid, click the Remove Modifier button.

A confirmationmessage appears, asking if you really want to remove the record from thecurrent LOPA.


The record is deleted and removed from the grid.

About Promoting Instrumented Functions to ASM


About Promoting Instrumented Functions to ASMWhen you promote an Instrumented Function record to ASM, theMeridiumAPM systemwill auto-matically create in ASMone:

l Asset Strategy for the Equipment or Functional Location record that is linked to the Instru-mented Function record and link that Asset Strategy to the Instrumented Function recordthrough theWasPromoted to ASMElement relationship.

Before you promote an Instrumented Function record to ASM, you should specify on theSIS Management Administration page whether you want theMeridiumAPM system topromote the Equipment record that is specified in the Equipment ID field or the FunctionalLocation record that is specified in the Functional Location ID field.

Note: If an Asset Strategy already exists for the record that is linked to the InstrumentedFunction record, the existing Asset Strategywill be used.

l Action record for each Inspection Task record that is linked to the Instrumented Functionrecord and links those Action records to the Instrumented Function record through theWasPromoted to ASMElementrelationship. The Action records that are created are areread-only, meaning that you cannot modify the records.

l Failure Risk record for each risk category that exists in the Risk Assessment record that islinked to the Instrumented Function record and links the Failure Risk records to the Instru-mented Function records through theWasPromoted to ASMElementrelationship. TheFailure Risk records that are created will be read-only, meaning that you cannot modify therecords.

Additionally, if you update in SIS Management the Instrumented Function record or and recordsthat are linked to that record, if you promote that Instrumented Function record again, theupdates that youmade in SIS Management will also saved in ASM. For example, if you link anadditional Inspection Task record to the Instrumented Function record that was already promotedto ASM, when you promote that Instrumented Function record again, one additional Actionrecord will be created for the new Inspection Task record and linked to the Asset Strategy thatexists for the Instrumented Function record.

Before you can promote an Instrumented Function record to ASM, the Instrumented Functionrecordmust be linked to:


l OnRisk Assessment record.

Note:You cannot promote to ASMan Instrumented Function record whose risk assess-ment method is a LOPA.

The ASM link on the Assessment Tasks menuwill be disabled until the preceding criteria aremet for an Instrumented Function record that is selected in the Instrumented Functions pane onthe Instrumented Functions (IFs) page.When you click the ASM link, a submenu appears withthe following options:

About Promoting Instrumented Functions to ASM


l Promote: If the record has not yet been promoted to ASM, the Instrumented Functionrecord will be promoted to ASM, and the Asset Strategy Overview pagewill appear, dis-playing the Asset Strategy overview for the Instrumented Function record.

-or-

If the record has already been promoted to ASM, the Asset Strategywill be updated withany changes that weremade since it was first created, and the Asset Strategy Overviewpage will appear, displaying the Asset Strategy overview for the Instrumented Functionrecord.

l View: If the record has not yet been promoted to ASM, this link is disabled.

-or-

If the record has already been promoted to ASM, the Asset Strategy Overview page willappear, displaying the existing Asset Strategy.

Promoting Instrumented Functions to ASM


Promoting Instrumented Functions to ASMTo promote an Instrumented Function record to ASM:


2. In the Instrumented Functions pane, select the row containing the Instrumented Functionrecord that you want to promote to ASM.

3. On the Assessment Tasks menu, click the ASM link.

A submenu appears.

4. On the submenu, click the Promote link.

The Asset Strategy Overview page appears, displaying the Asset Strategy overview forthe Instrumented Function record.

Viewing Asset Strategies Created from Instrumented Functions


Viewing Asset Strategies Created from InstrumentedFunctionsTo view an Asset Strategy that was created from an Instrumented Function record:


2. In the Instrumented Functions pane, select the row containing the Instrumented Functionrecord whose Asset Straegy you want to view.

3. On the Assessment Tasks menu, click the ASM link.

A submenu appears.

4. On the submenu, click the View link.

The Asset Strategy Overview page appears, displaying the Asset Strategy overview forthe Instrumented Function record.

About Proof Testing


About Proof TestingSafety instrumented systems and each instrumented function within that system needs to betested to ensure that the system is functioning to the standards for which it is designed. A prooftest consists of a set of steps that you need to perform to test safety instrumented systems andinstrumented functions. The conditions under which the test is conducted should represent thenormal conditions under which the system is intended to operate.

Depending on the group of equipment or devices that make up a safety instrumented system, youwill want to define a set of test steps that apply to a given group equipment or devices. In otherwords, you will need to define one set of test steps that you can reuse when you test similar sys-tems.

For each proof test that you want to conduct, you should create at least one record in each of thefollowing families:

l SIS Proof Test Template: Stores details about a given proof test, including the steps thatneed to be performed. For each unique set of test steps that exists, you will need to createone SIS Proof Test Template record to store those details.

l SIS Proof Test Template Detail: Stores the details on each specific step that needs to beperformed for the test. SIS Proof Test Template Detail records are linked to SIS Proof TestTemplate records through theHas Template Detail relationship. You should create oneSIS Proof Test Template Detail record for each step that is required for that test.

l SIS Proof Test: Stores details about a proof test that you perform, including the test res-ults. When you create an SIS Proof Test record, you will need to specify the SIS Proof TestTemplate record that contains the details about the proof test you want to perform.Whenyou select the SIS Proof Test Template record, one Functional Test Detail record will becreated for each SIS Proof Test Template Detail record that is linked to the SIS Proof TestTemplate record. For each proof test that you want to perform, you will need to create oneSIS Proof Test record. You can, however, reuse SIS Proof Test Template records.

You can think of the SIS Proof Test Template record and SIS Proof Test Template Detail recordsas the specification for how the test should be performed, and the SIS Proof Test record andFunctional Test Details records as a record of the test occurring.

To conduct a proof test, you will nee to complete the following steps:

1. Define the proof test steps that need to be performed for a given safety instrumented sys-tem by creating one Proof Test Template record for each type of test that will need to beperformed. Creating an SIS Proof Test Template record includes linking SIS Proof TestTemplate Detail records to the SIS Proof Test Template record.

2. Create on SIS Proof Test record, which serves as a record of the test event and storesthe results of that test.

After you have completed a proof test, you can create Risk Assessment Recommendationrecords to record recommendations for how a particular proof test can be improved. Forexample, youmaywant to suggest adding or removing a particular step from the proof testrequirements.

About Proof Testing


This section of the documentation provides details onmanaging SIS Proof Test Template andSIS Proof Test records. For details on how these families participate in the SIS Managementdatamodel, see the SIS Management datamodel image.

Common Tasks Menu


Common Tasks Menu

When you are working with SIS Proof Test Template records in SIS Management, the CommonTasks menuwill appear and contains the following links:

l View Templates: Displays the Proof Test Templates page, where you can view a list ofexisting SIS Proof Test Template records that are linked to the Safety Instrumented Sys-tem record or Instrumented Function record with which you are currently working. This linkis disabled on the Proof Test Templates page.

l Create Templates: Displays a new blank SIS Proof Test Template record on the ProofTest Template Definition page.

l Copy Template: Displays a new SIS Proof Test Template record on the Proof Test Tem-plate Definition page that is populated with information from the source SIS Proof TestTemplate record. This link is enabled only when you are viewing an existing SIS Proof TestTemplate record.

l Recommendations: Displays the Recommendations dialog box, where you canmanageRisk Assessment Recommendation records that are linked to an SIS Proof Test Templaterecord. This link is enabled only when you are viewing existing SIS Proof Test Templaterecords.

l Send To: Displays a submenuwith options that let you provide a link to the current page onyour desktop (create shortcut), in an email message, or on a HomePage.

l Reports: Displays a submenu that displays the caption of the Catalog itemProof Test Tem-plate Report as a link. The Reports link appears only on the Proof Test Template Defin-ition page and is enabled only when you are viewing an existing SIS Proof Test Templaterecord.

l Help: Displays the context-sensitive help topic for the page that you are currently viewing.

Accessing the Proof Test Template Definition Page


Accessing the Proof Test Template Definition PageAccessing the Proof Test Template Definition page:

1. Access the Safety Instrumented Systems page (if you want to link the SIS Proof TestTemplate record to a Safety Instrumented System record).

-or-

Access the Instrumented Functions (IFs) page (if you want to link the SIS Proof Test Tem-plate record to an Instrumented Function record).

2. In the grid, select the record to which you want to link the SIS Proof Test Template record.

3. On the Assessment Tasks menu, click the Test Templates link, and then click Create.

The Proof Test Template Definition page appears.

Aspects of the Proof Test Template Definition Page


Aspects of the Proof Test Template Definition PageThe Proof Test Template Definition page contains the SIS Proof Test Template datasheet,which is amaster/detail datasheet that contains two sections:

l Master record: Contains fields that you can use to describe the proof test.

l Proof Test Template Details: Contains a grid that displays a list of SIS Proof Test Tem-plate Detail records, which store details on the individual steps that need to be performedduring the proof test. Each row in the grid represents one SIS Proof Test Template Detailrecord. For each record that appears in the grid, the following information is displayed:

n Step Sequence Number

n Template Detail ID

n Step Type

n Test Criteria

n Result Criteria

n Location ID

n Equipment ID


n Add New Details: Displays a new blank SIS Proof Test Template Detail record.

n Add Existing Details: Displays the Find Items window, where you can search for an exist-ing SIS Proof Test Template Detail record to link to the SIS Proof Test Template record.

n Delete Details: Displays a confirmationmessage, and then deletes the selected SIS ProofTest Template Detail record.

The Proof Test Template Definition page contains the following taskmenus:

l Common Tasks

l Associated Pages

Creating SIS Proof Test Template Records


Creating SIS Proof Test Template RecordsWhen you create an SIS Proof Test Template record, you are defining the proof test and relatedsteps that need to be performedwhen you test a given safety instrumented system or instru-mented function within that system. You can create SIS Proof Test Template records and linkthem to records in the following families:



The following instructions provide details on creating an SIS Proof Test Template record that willbe linked automatically to a record in the preceding families. The SIS Proof Test Template data-sheet is amaster/detail datasheet. Thismeans that when you create the SIS Proof Test Tem-plate record, you will also need to create SIS Proof Test Template Detail records that will belinked automatically to the SIS Proof Test Template record.

To create an SIS Proof Test Template record:

1. Access the Proof Test Template Definition page.

2. In themaster record, provide values in the fields as desired.

3. In the Proof Test Template Details section, click the Add New Details button.

A new blank SIS Proof Test Template Detail record appears in a new window.

Creating SIS Proof Test Template Records


Note: You can link existing SIS Proof Test Template Detail records to the SIS Proof TestTemplate record via the Add Existing Details button. These instructions assume thatyou want to create a new SIS Proof Test Template Detail record. For details on addingexisting SIS Proof Test Template Detail record to SIS Proof Test Template records, seethe topic for adding existing SIS Proof Test Template Detail Records to the SIS ProofTest Template Detail record.

4. Provide values in the fields as desired, and then clickOK.

The SIS Proof Test Template Detail record is linked to the SIS Proof Test Template recordand appears in the Proof Test Template Details section.

5. Continue linking SIS Proof Test Template Detail records as desired.


The SIS Proof Test Template record is saved.

Accessing a List of Existing SIS Proof Test Template Records


Accessing a List of Existing SIS Proof Test TemplateRecordsThe following instructions provide details on accessing the Proof Test Templates page, whereyou can view a list of SIS Proof Test Template records that are linked to the currently selectedSafety Instrumented System record or instrumented function record. You can use this page toview the list of proof tests that have been defined or define a new proof test that is based on anexisting proof test.

To access the list of existing SIS Proof Test Template records:

1. Access the Safety Instrumented Systems page (if you want to view the SIS Proof TestTemplate records that are linked to a Safety Instrumented System record).

-or-

Access the Instrumented Functions (IFs) page (if you want to view the SIS Proof TestTemplate records that are linked to an Instrumented Function record).

2. In the grid, select the record whose SIS Proof Test Template records you want to view.

3. On the Assessment Tasks menu, click the Test Templates link.

A submenu appears.


The Proof Test Templates page appears.

Accessing a List of Existing SIS Proof Test Template Records


Aspects of the Proof Test Templates Page


Aspects of the Proof Test Templates PageThe Proof Test Templates page contains the Proof Test Templates grid, which displays the listof SIS Proof Test Template records that are linked to the Safety Instrumented System record orInstrumented Function record with which you are currently working. Each row in the grid rep-resents one SIS Proof Test Template record. For each record in the grid, the following inform-ation appears:

l Template ID: The value that exists in the Template ID field in the SIS Proof Test Templaterecord.

l Description: The value that exists in the Template Description field in the SIS Proof TestTemplate record.

l Author: The value that exists in the Author field in the SIS Proof Test Template record.

l Created On: The value that exists in the CreatedOn field in the SIS Proof Test Templaterecord.

l Modified Date: The value that exists in theModified Date field in the SIS Proof Test Tem-plate record.


l Create Template: Displays a new blank SIS Proof Test Template record on the ProofTest Template Definition page.

l Add Existing Template: Displays theFind Itemswindow, where you can search for anexisting SIS Proof Test Template record to link to the Safety Instrumented System recordor Instrumented Function record with which you are currently working.

l Remove Template: Displays a confirmationmessage, and then removes the selected SISProof Test Template record from the Proof Test Templates grid.

The Proof Test Templates page contains the following taskmenus:

l Common Tasks

l Associated Pages

Viewing an Existing SIS Proof Test Template Record


Viewing an Existing SIS Proof Test Template RecordWhen you are viewing the list of proof tests, you can view the details of that proof test. When youdo so, you are opening the SIS Proof Test Template record on the Proof Test Template Defin-ition page.When you are viewing the details of the record, you can alsomodify the informationthat is stored in the record.

To view the details of an existing SIS Proof Test Template record:

1. Access the Proof Test Templates page.

2. In the Proof Test Templates grid, locate the row containing the SIS Proof Test Templaterecord whose details you want to view.

3. In the Template ID cell in that row, click the hyperlinked Template ID for the desiredrecord.

The selected record appears on the Proof Test Template Definition page. At this point,you canmodify the record.

Adding Existing SIS Proof Test Template Detail Records to the SIS Proof Test Template Record


Adding Existing SIS Proof Test Template DetailRecords to the SIS Proof Test Template RecordWhen you define a proof test in an SIS Proof Test Template record, you will define the individualsteps that should be performed for that test. If desired, you can reuse a step that is associatedwith a different proof test. To do so, you will need to search for an existing SIS Proof Test Tem-plate Detail record to link to the SIS Proof Test Template record.

The following instructions provide details on linking an existing SIS Proof Test Template Detailrecord to an SIS Proof Test Template record. For details on creating a new SIS Proof Test Tem-plate Detail record to link to the SIS Proof Test Template record, see the instructions for creatingSIS Proof Test Template records.

To add an existing SIS Proof Test Template Detail record to the SIS Proof Test Templaterecord:

1. Access the SIS Proof Test Template record to which you want to add an SIS Proof TestTemplate Detail record.

2. In the Proof Test Template Details section, click the Add Existing Details button.


Adding Existing SIS Proof Test Template Detail Records to the SIS Proof Test Template Record


3. Specify the desired search criteria, and then click the Find Now button.


4. In the search results, select the SIS Proof Test Template Detail records that you want tolink to the SIS Proof Test Template record.


The selected records are linked to the SIS Proof Test Template record and appears in theProof Test Template Details section.

6. At the top of the datasheet, click the Save button.

Viewing Existing SIS Proof Test Template Detail Records


Viewing Existing SIS Proof Test Template DetailRecordsThe following instructions provide details on viewing the contents of an SIS Proof Test TemplateDetail record that is linked to an SIS Proof Test Template record.

To view an existing SIS Proof Test Template Detail record:

1. Access the SIS Proof Test Template record whose Detail records you want to view.

2. In the Proof Test Template Details section, locate the row containing the SIS Proof TestTemplate Detail record you want to view.

3. In the Template Detail ID cell, click the hyperlinked Template Detail ID.

The selected record appears in a new window.

4. If desired, you canmodify the record, and then clickOK.


Removing SIS Proof Test Template Detail Records from the SIS Proof Test Template Record


Removing SIS Proof Test Template Detail Recordsfrom the SIS Proof Test Template RecordIf desired, you can remove a step that you previously included in the test steps for a proof test. Todo so, you will need to remove the SIS Proof Test Template Detail record from the SIS ProofTest Template record. When you remove an SIS Proof Test Template Detail record from an SISProof Test Template record, you are deleting the link between the SIS Proof Test Templaterecord and the SIS Proof Test Template Detail record, and the SIS Proof Test Template recordwill no longer appear in the Proof Test Template Detail section on the SIS Proof Test Templatedatasheet.

To remove an SIS Proof Test Template Detail record from the SIS Proof Test Templaterecord:

1. Access the SIS Proof Test Template record, which is linked to the SIS Proof Test Tem-plate Detail record that you want to remove.

2. In the Proof Test Template Details grid, select the row containing the SIS Proof Test Tem-plate Detail record you want to remove.

3. Below the grid, click the Delete Details button.

A confirmationmessage appears, asking if you really want to remove the SIS Proof TestTemplate Detail record from the SIS Proof Test Template record.


The selected SIS Proof Test Template Detail record is removed from theProof Test Tem-plate Details grid.

Copying SIS Proof Test Template Records to Create New Ones


Copying SIS Proof Test Template Records to CreateNew OnesYou can use an existing proof test definition to define another similar proof test. To do so, you cancopy an existing SIS Proof Test Template record, which will create a new SIS Proof Test Tem-plate record that is automatically populated with information from the source record. When youcreate a new SIS Proof Test Template record in this way, the SIS Proof Test Template Detailrecords that are linked to the source record are also linked the new record. These recordswillnot, however, appear in the Proof Test Template Details section in the new record until afteryou save the new record.

To copy an SIS Proof Test Template record to create a new one:

1. Access the desired SIS Proof Test Template record.

2. On the Common Tasks menu, click the Copy Template link.

A new SIS Proof Test Template record appears on the Proof Test Template Definitionpage and is populated automatically with information from the source record.

3. Modify the values in themaster record as desired


The Proof Test Template Details section is populated automatically with the SIS ProofTest Template Detail records that are linked to the source record.

5. Modify the values in the detail records as desired, including creating new SIS Proof TestTemplate Detail records.

6. When you are finished, click the Save button.


Removing SIS Proof Test Template Records


Removing SIS Proof Test Template RecordsIf an existing proof test is no longer valid, you can remove that proof test from the SIL Analysis.When you do so, you are deleting the link between the SIS Proof Test Template record and theSafety Instrumented System record or Instrumented Function record to which it is linked.

To remove an SIS Proof Test Template record:

1. Access the Proof Test Templates page.

2. In the Proof Test Templates grid, select the row containing the SIS Proof Test Templaterecord that you want to remove.

3. Below the grid, click the Remove Template button.

A confirmationmessage appears, asking if you really want to remove the proof test fromthe SIL Analysis.


The selected record is removed from the Proof Test Templates grid.

About SIS Proof Test Records


About SIS Proof Test RecordsSIS Proof Test records store details about a proof test that is executed, including the results ofthe proof test. Each SIS Proof Test record will be linked to one or more Functional Test Detailrecords, which store details on the steps that you need to perform during the proof test and theresults of each test step.

When you create an SIS Proof Test record, you will need to specify an SIS Proof Test Templaterecord whose details you will use to perform the proof test. When you do so, one Functional TestDetail record will be created for each SIS Proof Test Template Detail record that is linked to theSIS Proof Test Template record that you specified in the SIS Proof Test record. The FunctionalTest Detail recordswill be populated automatically with information from the source SIS ProofTest Template Detail records.

Common Tasks Menu


Common Tasks Menu

When you are working with SIS Proof Test records in SIS Management, the Common Tasksmenuwill appear and contains the following links:

l View Tests: Displays the Proof Tests page, where you can view a list of existing SISProof Test records that are linked to the Safety Instrumented System record or Instru-mented Function record with which you are currently working. This link is disabled on theProof Tests page.

l Create Test: Displays a new blank SIS Proof Test record on the Proof Test Definitionpage.

l Recommendations: Displays the Recommendations dialog box, where you canmanageRisk Assessment Recommendation records that are linked to an SIS Proof Test record.This link is enabled only when you are viewing existing SIS Proof Test records.


l Reports: Displays a submenu that displays the caption of the Catalog itemProof TestReport as a link. The Reports link appears only on the Proof Test Definition page and isenabled only when you are viewing an existing SIS Proof Test record.

l Help: Displays the context-sensitive help topic for the page that you are currently viewing.

Accessing the Proof Test Definition Page


Accessing the Proof Test Definition PageAccessing the Proof Test Definition page:

1. Access the Safety Instrumented Systems page (if you want to link the SIS Proof Testrecord to a Safety Instrumented System record).

-or-

Access the Instrumented Functions (IFs) page (if you want to link the SIS Proof Testrecord to an Instrumented Function record).

2. In the grid, select the record to which you want to link the SIS Proof Test record.

3. On the Assessment Tasks menu, click the Proof Tests link.

A submenu appears.

4. On the submenu, click the Create link.

The Proof Test Definition page appears.

Aspects of the Proof Test Definition Page


Aspects of the Proof Test Definition PageThe Proof Test Definition page contains the SIS Proof Test datasheet, which is amaster/detaildatasheet that contains two sections:

l Master record: Contains fields that you can use to record the status of the proof test andspecify the SIS Proof Test Template record whose details you will use to perform the prooftest.

l Proof Test Details: Contains a grid that displays the list of Functional Test Detail recordsthat are linked to the SIS Proof Test record. Each row in the grid represents one FunctionalTest Detail record. For each record that appears in the grid, the following information is dis-played:

n Step Sequence Number

n Template Detail ID

n Step Type

n Test Criteria

n Result Criteria

n Location ID

n Equipment ID

If the Proof Test Status field in the SIS Proof Test record contains the value Closed or Complete,the SIS Proof Test and Functional Test Detail records are disabled on the Proof Test Definitionpage, and you can only the view the values stored in these records.

The Proof Test Definition page contains the following taskmenus:

l Common Tasks

l Associated Pages

Creating New SIS Proof Test Records


Creating New SIS Proof Test RecordsWhen you create an SIS Proof Test record, you are creating a record of the proof test that takesplace in your facility. You can create SIS Proof Test records and link them to records in the fol-lowing families:



The following instructions provide details on creating an SIS Proof Test record that will be linkedautomatically to a record in the preceding families. The SIS Proof Test datasheet is amas-ter/detail datasheet. When you create the SIS Proof Test record and specify an SIS Proof TestTemplate record, Functional Test Detail recordswill be linked automatically to the SIS Proof Testrecord that are created based on the SIS Proof Test Template Detail records that are linked tothe SIS Proof Test Template record. For details on the relationships that exist between these fam-ilies, see the datamodel image.

To create an SIS Proof Test record:

1. Access the Proof Test Definition page.

2. In themaster record, in the Functional Test Template list, select the Template ID for theSIS Proof Test Template record that contains the test information that you want to use forthe proof test. This field is required.

3. Provide values in the remaining fields in themaster record as desired.


The record is saved, and the Proof Test Details section is populated automatically withFunctional Test Detail records. At this point, you can perform the proof test and record theresults in the SIS Proof Test record.

Accessing the List of Existing SIS Proof Test Records


Accessing the List of Existing SIS Proof Test RecordsThe following instructions provide details on accessing a list of SIS Proof Test records that arecurrently linked to a given Safety Instrumented System record or Instrumented Function record.

To access the list of existing SIS Proof Test records:

1. Access the Safety Instrumented Systems page (if you want to view the SIS Proof Testrecords for a Safety Instrumented System record).

-or-

Access the Instrumented Functions (IFs) page (if you want to view the SIS Proof Testrecords for an Instrumented Function record).

2. In the grid, select the desired record.

3. On the Assessment Tasks menu, click the Proof Tests link.

A submenu appears.


The Proof Tests page appears.

Aspects of the Proof Tests Page


Aspects of the Proof Tests PageThe Proof Tests page contains the Proof Test Tests grid, which displays the list of SIS ProofTest records that are linked to the Safety Instrumented System record or Instrumented Functionrecord with which you are currently working. Each row in the grid represents one SIS Proof Testrecord. For each record in the grid, the following information appears:

l Test ID: The value that exists in the Test ID field in the SIS Proof Test record.

l Test Description: The value that exists in the Test Description field in the SIS Proof Testrecord.

l Template ID: The value that exists in the Functional Test Template field in the SIS ProofTest record.


l Create Test: Displays a new blank SIS Proof Test record on the Proof Test Definitionpage.

l Delete Test: Displays a confirmationmessage, and then deletes the selected SIS ProofTest record.

The Proof Test Templates page contains the following taskmenus:

l Common Tasks

l Associated Pages

Opening SIS Proof Test Records


Opening SIS Proof Test RecordsThe following instructions provide details on opening an existing SIS Proof Test record to view itscontents.

To open an SIS Proof Test record:

1. Access the Proof Tests page.

2. In the Proof Tests grid, locate the row containing the SIS Proof Test record whose con-tents you want to view.

3. In the Test ID cell, click the hyperlinked ID for the record.

The selected record appears on the Proof Test Definition page.

4. If desired, you canmodify the values in the fields, and then click the Save button.


Recording Proof Test Results in SIS Proof Test Records


Recording Proof Test Results in SIS Proof TestRecordsWhen you perform a proof test, you can record the results of each step that is required for thattest via the SIS Proof Test record for that proof test.

To record proof test results in an SIS Proof Test record:

1. Access the SIS Proof Test record for the current proof test.

2. In the Proof Test Details section, locate the row containing the Functional Test Detailrecord, which stores the details of the step for which you want to record the results.

3. In the Template Detail ID cell, click the hyperlinked Template Detail ID.

The selected Functional Test Detail record appears in a new window.

Recording Proof Test Results in SIS Proof Test Records


4. Provide values in the fields as desired to indicate the results of the test step.

5. ClickOK.

The record closes, revealing the Proof Test Definition page. You can continue recordingtest step results in this way.

6. When you are finished, click the Save button.


About Protective Instrument Loops


About Protective Instrument LoopsA protective instrument loop consists of interconnected instruments that work together to serve afunction that is defined for the safety instrumented system in which they exist. When you create aprotective instrument loop in SIS Management, you are creating a Protective Instrument Looprecord, and when you define the components of the protective instrument loop (i.e., the inter-connected instruments), you are creating records in the Protective Instrument Loop Element fam-ily and its subfamilies and linked them to the Protective Instrument Loop record. Throughout thisdocumentation, when we refer to the protective instrument loop, we are referring to the Pro-tective Instrument Loop record and all the records that are linked to it, and when we refer to Pro-tective Instrument Loop Element records, we are referring to the records that are linked to theProtective Instrument Loop.

When you are working with protective instrument loops in SIS Management, it is helpful to visu-alize the components of that protective instrument loop as a diagram. For example, the followingimage shows the baseline protective instrument loop diagram as it appears on the ProtectiveInstrument Loop Diagram View page.When you first access the SIL Validation feature for anSIL Analysis, this diagramwill appear by default, and you can use it as a starting point for definingyour protective instrument loop.

For more details on the components of a protective instrument loop, see the datamodel image,where the Protective Instrument Loop family is the predecessor.

Additionally, you can create protective instrument loop templates, which are protective instru-ment loops that are specified as a template via the Protective Instrument Loop record for that pro-tective instrument loop.When you are working with protective instrument loop templates in SISManagement, you will use the same features (e.g., the diagram view shown in the precedingimage). Within these features, however, the context of the pageswill specify that you are workingwith a template. For more details on the SIL Validation feature, see the topic about the SIL Val-idation feature.

About the SIL Validation Feature


About the SIL Validation FeatureThe SIL Validation feature lets you define the various components of protective instrument loopsor protective instrument loop templates so that you can see how the components will worktogether to achieve the safety integrity level that was determined based on the risks associatedwith these components.

Using the SIL Validation feature, you will complete the following steps:

1. Define the components of a protective instrument loop or template.

2. Calculate results.

3. View a summary of these results in graphical format.

The SIL Validation feature includes the following pages, which you can use to complete the pre-ceding steps:

l Protective Instrument Loop Summary: Lets you view the Protective Instrument Looprecord and graphs, which provide a summary of the calculated data that is stored in Pro-tective Instrument Loop Element records.

l Protective Instrument Loop Grid View: Lets you view hierarchically how the ProtectiveInstrument Loop Element records relate to one another in theMeridiumAPMdatabase.

l Protective Instrument Loop Diagram View: Lets you represent visually the physical com-ponents of the protective instrument loop or template and how theywork together. This isthe page that appears by default when you access the SIL Validation feature.

Each page presents a different view of the components of the protective instrument loop and con-tains the following taskmenus:

l Navigation

l SIL Validation

l Common Tasks

l Associated Pages

When you attempt to get your bearings in the SIL Validation feature, keep inmind that each pagein the feature displays a custom view of the records that exist in theMeridiumAPMdatabase.

To begin using the SIL Validation feature, you can:

l Open an existing protective instrument loop.

l Create a new protective instrument loop from scratch.

l Create a new protective instrument loop based on a template.

l Create a new protective instrument loop template from scratch.

l Create a new protective instrument loop template based on a protective instrument loop.

l Copy an existing protective instrument loop template to create a new one.

About the SIL Validation Feature


Throughout this documentation, when we refer to protective instrument loops, we are referring tothe non-template protective instrument loop.Whenwe discuss templates for protective instru-ment loops, we refer to them as protective instrument loop templates.

The SIL ValidationWorkflow


The SIL Validation WorkflowWhen you use the SIL Validation feature, you will complete the following steps:

1. Define the components of the protective instrument loop, using the diagram view.

2. Define the properties of the components, using the grid view.

3. Calculate the values that are defined in the records for the components.

4. View a summary of the data, using the summary view.

5. Define recommendations for the protective instrument loop.

The NavigationMenu


The Navigation Menu

TheNavigationmenu appears on all the pageswhere you are working with protective instrumentloops, but it does not appear when you are working with a protective instrument loop template.Thismenu contains the following links:

l Analysis Definition: Displays the SIL Analysis Definition page, where you canmodify anSIL Analysis record or create a new one.

l Systems: Displays the Safety Instrumented Systems page, where you canmanage theSafety Instrumented System records for the current SIL Analysis.

l Functions: Displays the Instrumented Functions (IFs) page, where you canmanage theInstrumented Function records for the current SIL Analysis.

l Asset Health Manager: Displays the SIS - Asset Health Manager for <Protective Instru-ment Loop Record ID> (Protective Instrument Loop) page, where you canmanageHealth Indicator records for the current protective instrument loop.

Note: The integration between SIS Management and Asset Health Manager (AHM) isnot documented.

l All Recommendations: Displays the Recommendation Management page, where youcanmanage the list of Risk Assessment Recommendation records for the current SIL Ana-lysis.

l Revision History: Displays the Analysis Revision History page, where you canmanagethe SIL Analysis Revision records that exist for the analysis. This link is enabled only if thestate of the SIL Analysis record with which you are currently working has ever been set toComplete.

The SIL ValidationMenu


The SIL Validation Menu

The SIL Validationmenu appears on all the pageswithin the SIL Validation feature. A greenarrow to the left of an option indicates the feature that you are currently viewing. The SIL Val-idationmenu contains the following links:

l Summary: Displays the Protective Instrument Loop Summary page, where you canview a summary of the protective instrument loop.

l Grid: Displays the Protective Instrument Loop Grid View page, where you can view therecords that make up the protective instrument loop.

l Diagram: Displays the Protective Instrument Loop Diagram View page, where you canillustrate the protective instrument loop in diagram form.

l Calculate: Calculates the values that are stored in the records that make up the protectiveinstrument loop.

l Recommendations: Displays the Recommendations dialog box, where you canmanageRisk Assessment Recommendation records for the protective instrument loop. This linkdoes not appear when you are working with protective instrument loop templates.

The Common Tasks Menu



TheCommon Tasks menu appears on all the pageswithin the SIL Validation features and con-tains the following links:

l Save Loop: Saves the recordswith which you are currently working.

l Delete Loop: Displays a confirmationmessage and then deletes the Protective InstrumentLoop record with which you are currently working.

l Save As Template: Displays on the Protective Instrument Loop Template page a copyof the selected Protective Instrument Loop record, where the new record is specified as atemplate.

l Apply Template: Displays the Protective Instrument Loop dialog box, where you canselect the Protective Instrument Loop record whose values you want to use to populate thecurrent Protective Instrument Loop record.

l Reference Documents: Displays the Reference Documents dialog box, where you canmanage Reference Document records that are linked to the Protective Instrument Looprecord.

l Reports: Displays a submenu that displays the caption of the Catalog itemProtective Instru-ment Loop Report as a link, which you can click to view the Protective Instrument LoopReport.


l Help: Displays the context-sensitive help topic for the current page.

About Creating Protective Instrument Loops


About Creating Protective Instrument LoopsWhen you create a protective instrument loop, you will need to complete the following steps:

1. Create the Protective Instrument Loop record and the Protective Instrument Loop Elementrecords that are linked to that record. TheMeridiumAPM systemwill create the ProtectiveInstrument Loop record and the default Protective Instrument Loop Element records auto-matically when you select to create a new protective instrument loop for an InstrumentedFunction.

2. Add components to the protective instrument loop in addition to the default components.When you add an element to the protective instrument loop, you are creating a record andlinking it to the Protective Instrument Loop record for that protective instrument loop.

To add components to a protective instrument loop, you can use either of the followingviews:

l The diagram view

l The grid view

Note: This documentation assumes that you want to use the diagram view to add com-ponents to the protective instrument loop.

3. Define the properties of each element that is included in the protective instrument loop dia-gram by providing values in the Protective Instrument Loop Element records and the Pro-tective Instrument Loop record. To define the properties of a protective instrument loop,you can use either of the following views:

l The diagram view

l The grid view

Note: This documentation assumes that you want to use the diagram view to define theproperties of the protective instrument loop.

For details on the components of a protective instrument loop, see the datamodel diagram,where the Protective Instrument Loop family is the predecessor.

Creating New Protective Instrument Loops Manually


Creating New Protective Instrument Loops ManuallyThe following instructions provide details on creating a new protective instrument loop diagramby adding elements to the default diagram.When you create a protective instrument loop dia-gram, you are creating a Protective Instrument Loop record. As you add components to the dia-gram, you are creating a record in the family that represents that element.

To create a new protective instrument loop manually:


2. In the Instrumented Functions grid, select the row containing the Instrumented Functionrecord for which you want to create a protective instrument loop diagram.

3. On the Assessment Tasks menu, click the Protective Loops link.

The Protective Instrument Loop Diagram View page appears, displaying the default pro-tective instrument loop diagram, which you can use as a starting point for creating your pro-tective instrument loop.

Note: If a Protective Instrument Loop record is already linked to the selected Instru-mented Function record, a submenu appears, displaying options that you can use to cre-ate a new Protective Instrument Loop record or view the existing one. These instructionsassume that you want to create a new Protective Instrument Loop. In this case, if the sub-menu appears, click the Create link, and the Protective Instrument Loop DiagramViewpage will appear.

4. Add the desired components to the grid.

5. Define the properties of the components as desired.

6. On the Common Tasks menu, click the Save Loop link.

The protective instrument loop is saved.

Creating New Protective Instrument Loops Based on a Template


Creating New Protective Instrument Loops Based on aTemplateThe following instructions provide details on creating a new protective instrument loop based on atemplate. When you create a protective instrument loop based on a template, theMeridiumAPMsystemwill automatically:

l Populate the Protective Instrument Loop record with the information from the ProtectiveInstrument Loop record for the template.

l Create and populate the Protective Instrument Loop Element records that are linked to theProtective Instrument Loop record, using the values in the template.

l Create the diagram.

After you create a protective instrument loop based on a template, you canmodify it as desired.

To create a new protective instrument loop based on a template:


2. In the Instrumented Functions grid, select the row containing the Instrumented Functionrecord for which you want to create a protective instrument loop.


The Protective Instrument Loop Diagram View page appears, displaying the default pro-tective instrument loop diagram.

Note: If a Protective Instrument Loop record is already linked to the selected Instru-mented Function record, a submenu appears, displaying options that you can use to cre-ate a new protective instrument loop or view the existing one. These instructions assumethat you want to create a new protective instrument loop. In this case, if the submenuappears, click the Create link, and the Protective Instrument Loop Diagram View pagewill appear.

4. On the Common Tasks menu, click the Apply Template link.

The Protective Instrument Loop dialog box appears, displaying a list of Protective Instru-ment Loop records that are specified as templates.

Creating New Protective Instrument Loops Based on a Template


5. In the grid, select the row containing the template that you want to use.

6. ClickOK.

The Protective Instrument Loop dialog box closes, and the Protective Instrument LoopDiagram View page refreshes and displays the protective instrument loop that is pop-ulated automatically with data from the template.

7. Modify the elements of the protective instrument loop as desired.


The protective instrument loop is saved.

About Opening Existing Protective Instrument Loops


About Opening Existing Protective Instrument LoopsWhen you open an existing protective instrument loop, you are accessing the Protective Instru-ment Loop record and the associated records that make up that protective instrument loop.

You can open an existing protective instrument loop from:

l Search results that return all existing Protective Instrument Loop records.

l The associated Instrumented Function record in an SIL Analysis.

Accessing a List of Existing Protective Instrument Loops


Accessing a List of Existing Protective InstrumentLoopsWhen you access a list of existing protective instrument loops, you are accessing a list of Pro-tective Instrument Loop records, which represent the protective instrument loop.

To access a list of existing protective instrument loops:

l On the SIS Management Start Page, click the SIL Validation link.

The Protective Loop Search page appears, displaying the list of existing Protective Instru-ment Loop records.

Aspects of the Protective Loop Search Page


Aspects of the Protective Loop Search PageThe Protective Loop Search page contains the Protective Loop Search workspace, which dis-plays the results of the query specified in the Protective Loop Search Query text box on the SISManagement Administration page. This documentation assumes that you are using thebaseline Safety_Loop_Search query, which contains a State prompt that appears a list at the topof the Protective Loop Analysis Search workspace. The State list contains a list of record statesthat have been configured for the Protective Instrument Loop family. You can choose from the fol-lowing baseline states:

l Approval: Displays the list of existing Protective Instrument Loop recordswhose Statefield contains the value Approval.

l Design: Displays the list of existing Protective Instrument Loop recordswhose State fieldcontains the value Design.

l In Service: Displays the list of existing Protective Instrument Loop recordswhose Statefield contains the value In Service.

l Out of Service: Displays the list of existing Protective Instrument Loop recordswhoseState field contains the value Out of Service.

l Pending Approval: Displays the list of existing Protective Instrument Loop recordswhoseState field contains the value Pending Approval.

Selecting theAll option displays the list of ALL Protective Instrument Loop records that exist in theMeridiumAPMdatabase. This is the default option.

After you select the desired state, you can click the Run Query button to run the Safety_Loop_Search query and display the results in the grid at the bottom of the page. The query results willinclude hyperlinked Record IDs, which you can click to open the protective instrument loop on theProtective Instrument Loop Diagram View - <Analysis ID>page, where<Analysis ID>is thevalue in the Analysis ID field in the SIL Analysis record with which you are currently working.


The SIL Analysis Search page contains the following taskmenus:

l Common Tasks

l Associated Pages

Using the Protective Loop Search page, you can:


l Delete a protective instrument loop.

l Calculate the SIL Validation results for one or multiple protective instrument loops.

Common Tasks


Common Tasks

TheCommon Tasks menu on the Protective Loop Search page contains the following links:

l Find Loop: This link is always disabled.

l Delete Loop: Displays a confirmationmessage, and then deletes the selected record.

l Calculate: Calculates the values that are stored in the records that make up the selectedprotective instrument loop(s).


l Help: Displays the context-sensitive help topic for the Protective Loop Search page.

Opening an Existing Protective Instrument Loop


Opening an Existing Protective Instrument LoopTo open an existing protective instrument loop:

1. Access the Protective Loop Search page.

2. In the State list, select the desired record state, and then click the Run Query button.

The results appear in the grid.

3. In the results grid, select the row containing the Protective Instrument Loop record that rep-resents the protective instrument loop that you want to open.

4. In the ID cell, click the hyperlinked Record ID.

The protective instrument loop represented by the selected Protective Instrument Looprecord appears on the Protective Instrument Loop Diagram View - <SILAnalysis>page, where<SIL Analysis>is the value in the Analysis ID field in the SIL Ana-lysis record with which the Protective Instrument Loop records is associated.

Opening Protective Instrument Loops Associated with an Instrumented Function in an SIL Analysis


Opening Protective Instrument Loops Associated withan Instrumented Function in an SIL AnalysisTo open a protective instrument loop associated with an instrumented function in an SILAnalysis:

1. Access the Instrumented Functions (IFs) page for the desired SIL Analysis.

2. In the Instrumented Functions section, select the row containing the Instrumented Func-tion record that is linked to the Protective Instrument Loop record that you want to open.


A submenu appears with options that let you create a new protective instrument loop orview the existing protective instrument loop that is associated with the selected Instru-mented Function record. These instructions assume that you want to view the existing pro-tective instrument loop.


The protective instrument loop appears on the Protective Instrument Loop DiagramView page.

Note: If the selected Instrumented Function record is associated with more than one pro-tective instrument loop, the Protective Instrument Loop Search page appears, whereyou can search for the desired Protective Instrument Loop record.

Aspects of the Protective Instrument Loop Diagram View Page


Aspects of the Protective Instrument Loop DiagramView PageWhen you select to create a new protective instrument loop or open an existing one, the Pro-tective Instrument Loop Diagram View page will appear by default. The Protective InstrumentLoop Diagram View page contains the Protective Instrument Loop workspace, which containsthe following sections:

l Explorer pane: Contains a hierarchical view of the relationships that exist between therecords that represent the components of the protective instrument loop. For each level inthe hierarchy, an associated element appears in the Diagram grid. When you select a levelin the hierarchy, the associated element will be highlighted in green in the DiagramCan-vas. You can hide and display the Explorer pane, using the icon.

l Diagram Canvas: Serves as an interactive drawing interface where you can build a dia-gram of the protective instrument loop. Each element represents a record, and each linebetween the elements represents the relationship that exists between those records.When you first access the Design Canvas, baseline elements appear and serve as a start-ing point for defining the protective instrument loop. You can double click an element to dis-play the datasheet for the record that is represented by that element. Additionally, you candouble click a blank space on the DiagramCanvas to view the Protective Instrument Looprecord for that protective instrument loop.

l Palette pane: Contains elements that represent components of a protective instrumentloop. Each element corresponds to a family whose records can be linked to the ProtectiveInstrument Loop record. You can drag an element to the DiagramCanvas to add that ele-ment to the protective instrument loop. The Palette pane contains the following elements:

n Sensor

Sensor Group

Final Element Group

Final Element

The icon for each element in the Palette pane includes a connection point to the left, right,or on both sides of the icon, which indicateswhere that element can be added to the Dia-gramCanvas. For example, an element with only a connection point to the right can beadded to the DiagramCanvas only as the first element. An element with connection pointson both sides, however, can be added anywhere in the diagram. You can hide and displaythe Palette pane using the icon.

Above the Protective Instrument Loop workspace, the button appears, which displays theState Assignments dialog box, where you canmanage the Security Users that are assigned tothe states that are defined for the Protective Instrument Loop family. To the right of the icon, thefollowing options appear:

Aspects of the Protective Instrument Loop Diagram View Page


l State indicator: Displays the current state of the Protective Instrument Loop record.

l Operations link: Displays a submenu that lists the available operations for the currentrecord. You can use this option to change the state of the Protective Instrument Looprecord.

Using the Protective Instrument Loop Diagram View page, you can:

l Add elements to the protective instrument loop diagram.

l Define the properties of each element.

l Delete elements from the protective instrument loop diagram.

l Link Risk Assessment Recommendation records to the Protective Instrument Loop recordthat represents the protective instrument loop.

Adding Elements to the Protective Instrument Loop Diagram


Adding Elements to the Protective Instrument Loop Dia-gramWhen you add an element to the protective instrument loop, you are creating a record and linkingit to the Protective Instrument Loop record that represents the protective instrument loop. Notethat adding an element to the protective instrument loop diagram does not assign properties tothat element. After you add an element to the diagram, you will still need to define its propertiesby entering values in the fields in the record that it represents.

To add an element to the protective instrument loop diagram:

1. Open the desired Protective Instrument Loop record on the Protective Instrument LoopDiagram View page.

2. In the Palette pane, select the element that you want to add to the protective instrumentloop diagram.

3. Drag the element and drop it in the desired location on the Design Canvas.

The element is added to the diagram. At this point you can define the properties of that ele-ment or link an existing Element record to the element.

Defining Element Properties in the Diagram View


Defining Element Properties in the Diagram ViewWhen you define properties for an element via the diagram view, you are entering values intofields in the record represented by that element. The following instructions provide details ondefining a new Element record from scratch. Alternatively, you can link an existing Elementrecord to an element.

To define element properties in the diagram view:

1. Open the desired protective instrument loop.


2. In the DiagramCanvas, double-click the element whose properties you want to define.

The record that is represented by that element appears in a new window. For example, thefollowing image shows a Protective Instrument Loop Sensor record.

Defining Element Properties in the Diagram View


3. Provide values in the fields on the datasheet as desired.

4. ClickOK.



Removing Elements from the Protective Instrument Loop Diagram


Removing Elements from the Protective InstrumentLoop DiagramWhen you remove an element from the protective instrument loop diagram, you are deleting:

l The link between the Protective Instrument Loop record and the record that is representedby that element.

l The record that is represented by that element.

l The records that are linked to the selected record as successors.

Note: You cannot remove an element that appears in the diagram by default.

To remove elements from the protective instrument loop diagram:

1. Access the desired protective instrument loop on the Protective Instrument Loop Dia-gram View page.

2. On the DiagramCanvas, right-click the element that you want to remove from the diagram.

A shortcut menu appears.

Note: The shortcut menu does not appear if you right-click a element that appears in thediagram by default.

3. Click the Delete link.

A confirmationmessage appears, asking if you really want to delete the selected element.


The selected element is removed from the protective instrument loop diagram.

Linking Existing Records to Elements in the Protective Instrument Loop


Linking Existing Records to Elements in the ProtectiveInstrument LoopRather than creating an Element record from scratch and linking it to the element in the protectiveinstrument loop, you can link an existing Element record to an element in the protective instru-ment loop. Additionally, if an element is already linked to an Element record, you can replace theexisting Element record with an existing Element record. When you do so:

l If the current Element record is not linked to any other protective instrument loops, that Ele-ment record will be deleted.

l If the current Element record is linked to one or more other protective instrument loops,that Element record will be unlinked from the current protective instrument loop, and willnot be deleted.

The following instructions provide details on linking an existing Element record to an element in aprotective instrument loop.

To link an existing record to an element in a protective instrument loop:

1. Open the desired protective instrument loop.




2. In the diagram canvas, double-click the element to which you want to link an existingrecord.

The record that is represented by that element appears in a new window. For example, thefollowing image shows a Protective Instrument Loop Sensor record.



3. Click the Link button.

The Protective Instrument Loop dialog box appears, displaying a list of existing Elementrecords in the same family. The header on this dialog box indicates the name of the family(e.g., Sensor). For example, the following image shows how the Protective InstrumentLoop dialog box appears when you access it from a Protective Instrument Loop Sensorrecord.



4. Select the row containing the Element record that you want to link to the element, and thenclickOK.

The Protective Instrument Loop dialog box closed, and if the element to which you are link-ing an existing Element record is already linked to an Element record that is:

l Not linked to any other Protective Instrument Loop records, amessage appears, indicatingthat the Element record you selected will replace the current Element record, and then thecurrent Element record will be deleted. Clicking OK on thismessage will delete the currentElement record and replace it with the selected Element record.

l Linked to one or more other Protective Instrument Loop records, amessage will appear,indicating that the record cannot be deleted until it is unlinked from the current protectiveinstrument loop. Clicking OK on thismessage will unlink the current Element record andlink the selected Element record.

5. If the datasheet window is still open, on the datasheet window, clickOK.

The datasheet window closes.



Unlinking Elements from a Protective Instrument Loop


Unlinking Elements from a Protective Instrument LoopThe following instructions provide details on removing the link between a record representing anelement and the Protective Instrument Loop record representing the Protective Instrument Loop.Keep inmind that every Protective Instrument Loopmust consist of at least one of ALL the fol-lowing elements by default:

l Logic Solver

l Sensor System

l Sensor Group

l Sensor

l Final Element System

l Final Element Group

l Final Element

If you remove the link between a Protective Instrument Loop record and the only record for arequired element type (listed above), theMeridiumAPM systemwill automatically create a new,default record of that element type and link it to the Protective Instrument Loop record.

You can remove any element from a Protective Instrument Loop only if the record representingthat element is linked tomore than one Protective Instrument Loop. In this case, the Unlink but-ton on the datasheet for that record will be enabled. If, however, a record representing an ele-ment is linked to only one Protective Instrument Loop, the Unlink button will be disabled. Theseinstructions assume that the Unlink button is enabled.

To unlink an element from a Protective Instrument Loop:

1. Open the Protective Instrument Loop containing the element that you want to remove.

The Protective Instrument Loop appears on the Protective Instrument Loop DiagramView page.



2. Open the record representing the element that you want to remove from the ProtectiveInstrument Loop.

The record appears. The following image shows an example of a Protective InstrumentLoop System record that is linked tomore than one Protective Instrument Loop record.



3. Click the Unlink button.

The record closes, and the link between the record representing that element and the cur-rent Protective Instrument Loop record is removed.

Accessing the Protective Instrument LoopGrid View Page


Accessing the Protective Instrument Loop Grid ViewPageThe Protective Instrument Loop Grid View page lets you view the elements of the protectiveinstrument loop by viewing the records that are represented by those elements. Unlike the dia-gram view, where you can add an element to the diagram and then define the field values in therecord that is represented by that element, in the grid view, you can add element records to theprotective instrument loop using Link and Apply buttons, which appear on the datasheet of someelement records.

To access the Protective Instrument Loop Grid View page:


2. On the SIL Validationmenu, click the Grid link.

The Protective Instrument Loop Grid View page appears.

Aspects of the Protective Instrument LoopGrid View Page


Aspects of the Protective Instrument Loop Grid ViewPageThe Protective Instrument Loop Grid View page contains the following sections:

l Datasheet area: Contains the datasheet for the record that is currently selected in theTree pane. At the top of the datasheet area, the following option appears:

Displays the State Assignments dialog box, where you canmanage the Security Usersthat are assigned to the states that are defined for the Protective Instrument Loop family.

l State indicator: Displays the current state of the Protective Instrument Loop record.

l Operations link: Displays a submenu that lists the available operations for the currentrecord.

l Tree pane: Contains a hierarchical view of the records that make up the protective instru-ment loop.When you select a level in the hierarchy, the corresponding record will appearin the datasheet area.

When you are viewing some datasheets for Protective Instrument Loop Element families, the fol-lowing buttonsmay appear:

l Link: Displays the Protective Instrument Loop dialog box, which contains a list of recordsthat you can link to the currently selected record. To link one of these records to the cur-rently selected record, you can select the row containing the record that you want to link tothe currently selected record and then click OK.

l Apply: Displays the Protective Instrument Loop dialog box, which contains a list ofrecordswhose contents that you can use to create a new record that is populated auto-matically with information from the source record and then link that record automatically tothe currently selected record. The new record will be linked automatically to the currentlyselected record. To use an existing record to create a new record and link it automaticallyto the currently selected record, you can select the row containing the desired record andthen click OK.

l Select: Displays the Protective Instrument Loop dialog box, which contains a list of LogicSolver records fromwhich you can select the desired element to link to the protective instru-ment loop.

Accessing the Protective Instrument Loop Summary Page


Accessing the Protective Instrument Loop SummaryPageThe Protective Instrument Loop Summary page lets youmanage the summarized data that isstored in the records that make up the protective instrument loop that is illustrated in the diagramon the Protective Instrument Loop Diagram View page.

To access the Protective Instrument Loop Summary page:


2. On the SIL Validationmenu, click the Summary link.

The Protective Instrument Loop Summary page appears.

Aspects of the Protective Instrument Loop Summary Page


Aspects of the Protective Instrument Loop SummaryPageThe Protective Instrument Loop Summary page displays the datasheet for the Protective Instru-ment Loop record for the protective instrument loop with which you are currently working. Belowthe datasheet, two graphs appear, which display the following calculated values per element inthe protective instrument loop:

l PFD Contribution

l MTTFS Contribution

Deleting Protective Instrument Loops


Deleting Protective Instrument LoopsWhen you delete a protective instrument loop (or protective instrument loop template), you aredeleting the Protective Instrument Loop record and all the Protective Instrument Loop Elementrecords that are linked to that record. If you try to delete a protective instrument loop that containsan element that is also linked to a different Protective Instrument Loop record, you will need toremove the link between that Protective Instrument Loop Element record and the ProtectiveInstrument Loop record before you can delete the protective instrument loop.

You can delete one or multiple protective instrument loops at one time. These instructionsprovide details on deleting onlyONE protective instrument loop at a time.

To delete a protective instrument loop:

1. Access the Protective Loop Search page (for non-template protective instrument loops)

-or-

Access the Protective Instrument Loop Template Search page (for protective instrumentloop templates).

2. In the search results, select the row containing the protective instrument loop you want todelete.

3. On the Common Tasks menu, click the Delete Loop link.

A message appears, asking if you want to delete the selected protective instrument loop.


The protective instrument loop is deleted.

Note: If the Protective Instrument Loop record is linked to any Element records that arelinked to additional Protective Instrument Loop records, amessage will appear, indic-ating that youmust remove the link between these Element records and the ProtectiveInstrument Loop record before you can delete the protective instrument loop.

About Protective Instrument Loop Templates


About Protective Instrument Loop TemplatesIf you create a protective instrument loop that you want to use as a template for creating addi-tional protective instrument loops in the future, you can use that protective instrument loop to cre-ate a template, or you can create a protective instrument loop templatemanually.

A protective instrument loop template is the same as a protective instrument loop, meaning that itconsists of a Protective Instrument Loop record and all the records that are linked to that recordas elements of the protective instrument loop. Each record that is associated with the protectiveinstrument loop for a template, however, is specified as a template via the Is Template field in therecord. Note that the Is Template field value is set by theMeridiumAPM system automaticallywhen you create a protective instrument loop template. The field does not appear on any data-sheet by default and is not meant to bemodifiedmanually.

When you save a protective instrument loop as a template, theMeridiumAPM systemwill auto-matically:

l Create a copy of the Protective Instrument Loop record.

l Create a copy of each record that is linked to the Protective Instrument Loop record as anelement of the protective instrument loop and link those records to the Protective Instru-ment Loop record for the template with one exception.When theMeridiumAPM systemcopies a Protective Instrument Loop Final Element record, the values stored on the Dan-gerous Combination of Outputs tab are not copied to the template record.

l Select the Is Template check box in each of the copied records (i.e., setting this value totrue.), which identifies the protective instrument loop as a template.

After a protective instrument loop template exists:

l Aswith a non-template protective instrument loop, you can view the records that make upthe protective instrument loop in the grid view, diagram view, and summary view.

l Aswith a non-template protective instrument loop, you can calculate the SIL Validation res-ults.

l It will not appear in the query results on the Protective Loop Search page.

l You can search for it on the Protective Instrument Loop Template Search page.

Aswith non-template protective instrument loops, when you are working with a protective instru-ment loop template, you will use the following pages to complete the tasks associated with a pro-tective instrument loop:

l Protective Instrument Loop Diagram View: Lets you view the components of the pro-tective instrument loop template as a diagram. This is the default view.

l Protective Instrument Loop Grid View: Lets you view the components of the protectiveinstrument loop in record form and in a hierarchy, which is similar to the Record Explorerpane in the RecordManager.

l Protective Instrument Loop Summary View: Lets you view the Protective InstrumentLoop record for the template and graphs, which provide a summary of the calculated datathat is stored in each Protective Instrument Loop Element record for the template.

About Protective Instrument Loop Templates


Note: Unlike working with these pages for a non-template protective instrument loop, insteadof displaying the text Protective Instrument Loop in the workspace, the text Protective Instru-ment LoopTemplate will appear, indicating that you are working with a template.

Each page presents a different view of the components of the protective instrument loop templateand contains the following taskmenus:

l SIL Validation

l Common Tasks

l Associated Pages

When you attempt to get your bearingswith templates in the SIL Validation feature, keep inmindthat each page in the feature displays a custom view of the records that exist in theMeridiumAPMdatabase.

To begin working with protective instrument loop templates, you can:

l Create a protective instrument loop template from scratch.

l Create a protective instrument loop template as a copy of an existing protective instrumentloop template.

l Save an existing protective instrument loop as a template.


About Creating Protective Instrument Loop Templates


About Creating Protective Instrument Loop TemplatesAswith non-template protective instrument loops, when you are working with a protective instru-ment loop template, you will complete the following steps:

1. Create the Protective Instrument Loop record for the template and the Protective Instru-ment Loop Element records that are linked to that record. TheMeridiumAPM systemwillautomatically create these recordswhen you select to create a template:

n Based on an existing protective instrument loop.

n From scratch.

n Based on an existing template.

2. Add elements to the protective instrument loop template in addition to the default elements(for a new template) or existing elements (for a template that is created based on an exist-ing template or non-template protective instrument loop). When you add an element to aprotective instrument loop template, you are creating a record in a family and linking thatrecord to the Protective Instrument Loop record for that protective instrument loop tem-plate.

To add elements to the protective instrument loop template, you can use either of the fol-lowing views:

n The diagram view

n The grid view

Note: You can use the same instructions for adding components to a template as addingcomponents to a non-template protective instrument loop.

3. Define the properties of each node that is included in the protective instrument loop tem-plate diagram, meaning that you will provide values in the Protective Instrument Loop Ele-ment records and the Protective Instrument Loop record for the template.

To define the properties of the protective instrument loop template, you can se the fol-lowing view:

n The diagram view

n The grid view

Note: You can use the same instructions for defining the properties of nodes for a tem-plate as defining the properties of nodes for a non-template protective instrument loop.

For details on the components of a protective instrument loop, see the datamodel diagram,where the Protective Instrument Loop family is the predecessor.

Creating Protective Instrument Loop Templates from Scratch


Creating Protective Instrument Loop Templates fromScratchTo create a protective instrument loop template from scratch:

1. Access the Protective Loop Template Search page.

2. On the Common Tasks menu, click the Create Template link.

A new protective instrument loop template appears on the Protective Instrument LoopDiagram View page.



5. On the Common Tasks menu, click the Save Template link.

The protective instrument loop template is saved.

Creating Protective Instrument Loop Templates Based on Existing Protective Instrument Loops


Creating Protective Instrument Loop Templates Basedon Existing Protective Instrument LoopsIf you create a protective instrument loop that you want to use as a template to create additionalprotective instrument loops in the future, you can save that protective instrument loop as a tem-plate.

When you save a protective instrument loop as a template, you are automatically:

l Creating a copy of the source Protective Instrument Loop record and the Protective Instru-ment Loop Element records that are linked to that record.

l Selecting the Is Template check box in the copied records.

In other words, you are creating a protective instrument loop template that is based on a non-tem-plate protective instrument loop.

To create a protective instrument loop template based on existing protective instrumentloop:

1. Open the protective instrument loop that you want to use as a template.

2. On the Common Tasks menu, click the Save As Template link.

The page refreshes and displays the protective instrument loop template, which is pop-ulated automatically with the information from the source protective instrument loop.



5. On the Common Tasks menu, click the Save Template link.

The protective instrument loop template is saved.

Copying Protective Instrument Loop Templates to Create New Ones


Copying Protective Instrument Loop Templates toCreate New OnesWhen you copy a protective instrument loop template to create a new one, theMeridiumAPMsystemwill automatically:

l Create a copy of the Protective Instrument Loop record for the template.

l Create a copy of each Protective Instrument Loop Element record that is linked to the Pro-tective Instrument Loop record for the template.

l Append the name of the protective instrument loop with copy. For example, if you copy aprotective instrument loop template namedTemplate Loop -02, the new protective instru-ment loop template will be namedTemplate Loop -02 copy.

To copy a protective instrument loop template to create a new one:


2. In the search results, select the row containing the protective instrument loop template thatyou want to copy.

3. On the Common Tasks menu, click the Copy Template link.

The Protective Instrument Loop Template Search page refreshes, and a new protectiveinstrument loop template appears in a new row in the search results.

Accessing the Protective Loop Template Search Page


Accessing the Protective Loop Template Search PageOn the Protective Loop Template Searchpage, you can search for andmanage existing pro-tective instrument loop templates.

To access the Protective Loop Template Search page:

1. Access the SIS Management Start Page.

2. Click the SIL Validation Template link.

The Protective Loop Template Search page appears.

Aspects of the Protective Loop Template Search Page


Aspects of the Protective Loop Template Search PageThe Protective Loop Template Search page contains the Protective Loop Template Searchworkspace, which displays the results of the query specified in the Protective Loop TemplateSearch Query text box on the SIS Management Administration page. This documentationassumes that you are using the baseline Safety_Loop_Template_Search query, which containsthe State prompt that appears as a list at the top of the Protective Loop Template Search work-space. The State list contains a list of record states that have been configured for the ProtectiveInstrument Loop family. You can choose from the following baseline states:

l Approval: Displays the list of existing Protective Instrument Loop recordswhose Statefield contains the value Approval.

l Design: Displays the list of existing Protective Instrument Loop recordswhose State fieldcontains the value Design.

l In Service: Displays the list of existing Protective Instrument Loop recordswhose Statefield contains the value In Service.

l Out of Service: Displays the list of existing Protective Instrument Loop recordswhoseState field contains the value Out of Service.

l Pending Approval: Displays the list of existing Protective Instrument Loop recordswhoseState field contains the value Pending Approval.

Selecting the All option will cause the query to return all Protective Instrument Loop records inany state.

After you select different criteria, you can click the Run Query button to run the Safety_Loop_Template_Search query and displays the results in the grid at the bottom of the page. The queryresults will include hyperlinked Template IDs, which you can use to open the protective instru-ment loop on the Protective Instrument Loop Diagram View page.


The Protective Loop TemplateSearch page contains the following taskmenus:

l Common Tasks

l Associated Pages

Using the Protective Loop Template Search page, you can:

l Open an existing protective instrument loop template.

l Create a new protective instrument loop template from scratch.

l Create a new protective instrument loop template by copying an existing protective instru-ment loop template.

l Delete a protective instrument loop template.

l Calculate the SIL Validation results for multiple protective instrument loop templates.




TheCommon Tasks menu on the Protective Loop Template Search page contains the fol-lowing links:

l Find Template: This link is disabled.

l Create Template: Displays on the Protective Instrument Loop Diagram View page theProtective Instrument Loop Template screen with a new protective instrument loop tem-plate.

l Copy Template: Displays in a new row in the grid on theProtective Loop TemplateSearch page a new protective instrument loop template with the same name as the sourcetemplate, appended withcopy.

l Delete Template: Displays a confirmationmessage, and then deletes the current pro-tective instrument loop.

l Calculate: Calculates the values that are stored in the records that make up the selectedprotective instrument loop template(s).


l Help: Displays the context sensitive help topic for theProtective Loop Template Searchpage.

Opening Existing Protective Instrument Loop Templates


Opening Existing Protective Instrument Loop Tem-platesThe following instructions provide details on searching for an existing protective instrument looptemplates and opening a protective instrument loop.

To open an existing protective instrument loop template:


2. In the State list, select the state that corresponds to the value in the State field in the Pro-tective Instrument Loop record for the protective instrument loop template that you want toopen.

3. Click the Run Query button.


4. In the search results, locate the row containing the protective instrument loop template thatyou want to open, and in the ID cell, click the hyperlinked Template ID for the desiredrecord.

The selected protective instrument loop template appears on theProtective InstrumentLoop Diagram View page.

About Calculating SIL Validation Results


About Calculating SIL Validation Results

Note: The details in this section of the documentation can also be used when working with pro-tective instrument loop templates.

The values that are used to calculate SIL Validation results come from the Protective InstrumentLoop Element records that are linked to the Protective Instrument Loop record. SIL Validation res-ults for a protective instrument loop can be calculatedmanually or by theMeridiumAPM system.

You can specify how you want to calculate the SIL Validation results via the SIL ValidationMethod field in the Protective Instrument Loop record. On the datasheet, this field appears as alist that contains the following values:

l Internal Calculation: Indicates that the results will be calculated by theMeridiumAPM sys-tem.When the SIL ValidationMethod field contains the value Internal Calculation, the Cal-culated Results section on the Protective Instrument Loop datasheet is disabled andpopulated automatically with the calculation results.

l External Calculation: Indicates that the results will be calculatedmanually. When the SILValidationMethod field contains the value External Calculation, the Calculated Resultssection on the Protective Instrument Loop datasheet is enabled. You can use the fields inthe Calculated Results section tomanually calculate SIL Validation results.

TheMeridiumAPM systemwill calculate SIL Validation results when you click the Calculate link,which is available in the following locations:

l SIL Validation taskmenu in the SIL Validation feature. This option lets you calculate theresults for an individual protective instrument loop.

-or-

l Common Tasks menu on the Protective Loop Search. This option lets you calculate theresults for multiple protective instrument loops at one time.

Note: You can calculate the results for multiple protective instrument loop templatesusing this option on the Protective Loop Template Search page.

Calculating SIL Validation Results for a Protective Instrument Loop


Calculating SIL Validation Results for a ProtectiveInstrument LoopThe following instructions provide details on calculating the SIL Validation results for a single Pro-tective Instrument Loop (or protective instrument loop template). The results of the calculationare stored in the Protective Instrument Loop record and can be viewed via the Protective Instru-ment Loop Summary page.

To calculate SIL Validation results for a Protective Instrument Loop:

l On any page within the SIL Validation feature, on the SIL Validationmenu, click the Cal-culate link.

n If the results were calculated successfully, a message appears, indicating that the resultswere calculated successfully.

n If the results were not calculated successfully, a message appears, indicating that the cal-culation was unsuccessful and that the results have not been updated.

n If the calculation cannot be performed because values required for the calculation have notbeen provided, theMissing Required Values dialog box appears, displaying the list offields that require a value, sorted by the record in which the field exists. You will need toprovide the required values and then calculate the results again.

Calculating SIL Validation Results for Multiple Protective Instrument Loops


Calculating SIL Validation Results for Multiple Pro-tective Instrument LoopsThe following instructions provide details on calculating the SIL Validation results for more thanone protective instrument loop at one time. These results are stored in the Protective InstrumentLoop record and can be viewed via the Protective Instrument Loop Summary page.

These instructions can also be used to calculate the results for more than one protective instru-ment loop template.

To calculate SIL Validation results for multiple Protective Instrument Loops:

1. Access the Protective Loop Search page (for non-template protective instrument loops).

-or-

Access the Protective Instrument Loop Template Search page (for protective instrumentloop templates).

2. In the search results, select the rows containing the protective instrument loopswhose SILValidation results you want to calculate.

3. On the Common Tasks menu, click the Calculate link.

The Calculation dialog box appears and displays the progress of the calculations. After theresults have been calculated, the Calculation dialog box displays amessage, indicatingthat the calculation operation is finished, as shown in the following image.

ŒHint: To view the list of protective instrument loops that were calculated and whetherthe calculation finished successfully or failed, click the Detail>> button.

4. ClickOK.

The Calculation dialog box closes.

About Calculation Details


About Calculation DetailsAfter you calculatemultiple protective instrument loops, on the Calculation dialog box, you canclick the Details>> button to view the list of protective instrument loops that you selected to cal-culate and the status of that calculation.

The details of the calculation can contain the following statusmessages:

l External Calculation: This indicates that the value in the SIL ValidationMethod field in theProtective Instrument Loop record is External.

l Failed: This indicates that the calculation failed to return results.

l Succeeded: This indicates that the calculated results were returned successfully.

l Unable to calculate: This indicates that there are some required valuesmissing from theprotective instrument loop.

About theMissing Required Values Dialog Box


About the Missing Required Values Dialog Box

TheMissing Required Values dialog boxwill appear if you try to calculate the SIL validation res-ults or save the Protective Instrument Loop record and the values required for the SIL validationcalculations have not been provided.

Note: You can save a Protective Instrument Loop record without providing the required val-ues. You cannot, however, successfully calculate SIL Validation results without providing thesevalues.

TheMissing Required Values dialog box displays a grid that contains a list of fields that arerequired for the calculation and for which a value has not been provided. These fields aregrouped by the Record ID of the record in which they exist. Each row in the grid represents onefield. For each field, the following columns are displayed:

l Caption: Displays the datasheet caption for that record family.

l Value: Displays a text box, where you can provide a value for that field.

In the Value cell in the grid, you can type a value for only someof the required fields. In somecases, you will need to navigate to the datasheet itself to provide a value. You will know that youcan type the value directly in the Value cell on theMissing Required Values dialog box if a

About theMissing Required Values Dialog Box


cursor appears in the Values cell when you click the cell. If a cursor does not appear, you willneed to navigate to the datasheet. For example, because the Actuator field on a Final Elementdatasheet contains a list, in order to provide a value in this field, you will need to do so via the data-sheet for that family.

Below the grid, the following options appear:

l OK: Closes the Missing Required Values dialog box.

l Check: Refreshes the grid, removing fields for which you have provided a valid value.

About Protective Instrument Loop Final Element Records


About Protective Instrument Loop Final ElementRecordsProtective Instrument Loop Final Element records can be defined via the <Record ID> (Pro-tective Instrument Loop Final Element) window, which contains the following tabs:

l Final Element: Displays the Protective Instrument Loop Final Element datasheet, which isa custom form datasheet that contains fields that you can use to define the final element.

l Dangerous Combination of Outputs: Allows you to define hazards associated with com-bined output states for final elements.

About Defining Hazards AssociatedWith CombinedOutput States


About Defining Hazards Associated With CombinedOutput StatesWhen you define a Protective Instrument Loop Final Element record, you will need to define thepotential hazards that can occur if the output state associated with the final element is combinedwith the output state associated with a different final element. While the output state associatedwith individual final elements is safe, in some cases, when output states associated with multiplefinal elements are combined, a hazardous event can occur. For example, if the output state asso-ciated with Final Element A has the potential to fill a tank half full, and the output state associatedwith Final Element B has the potential to fill the same tank half full, these combined output stateshave the potential to overflow the tank. In this way, Final Element A and Final Element B have acombined output state hazard.

You can document combined output state hazards that exist for final elements via the DangerousCombination of Outputs tab on the <Record ID> (Protective Instrument Loop Final Element)window. In other words, for each final element that participates in a potentially hazardous rela-tionship, you will need to define the combined output state hazard(s) for that final element.

The Dangerous Combination of Outputs tab allows you tomanage all the combined output statehazards that exist for a final element. To define combined output state hazards for a final element,you will need to:

l Link the Protective Instrument Loop Final Element record to the other Protective Instru-ment Loop Final Element record representing the final element whose output state cancause a hazard when combined with the output state of the current final element. Pro-tective Instrument Loop Final Element records can be linked to one or more other Pro-tective Instrument Loop Final Element records through the HasHazardous Eventrelationship.

l Describe the hazardous event that can occur when the output states are combined.Because some final elements can participate in multiple combined output state hazardscenarios, in each Protective Instrument Loop Final Element record, you will need todescribe the hazardous events that are associated with that final element. In other words,describing the hazardous event in one Protective Instrument Loop Final Element recordwill not automatically populate the linked Protective Instrument Loop Final Element recordwith the same description.

The following image illustrates the records that participate in a combined output state hazardscenario in which the combination of two output states can lead to a hazardous event.



Notice that the Protective Instrument Loop Final Element record to which you link other Pro-tective Instrument Loop Final Element records is the predecessor in the relationship. When youare working with Protective Instrument Loop Final Element records, it is helpful to refer to the SISManagement datamodel image where the Protective Instrument Loop family is the predecessorfamily.

The following image shows the Dangerous Combination of Outputs tab on the <Record ID>(Protective Instrument Loop Final Element)window for the final element with the RecordIDFinal Element template 1 2.

Aspects of the Dangerous Combination of Output States Tab in Protective Instrument Loop Final Element


Aspects of the Dangerous Combination of OutputStates Tab in Protective Instrument Loop Final ElementRecordsTheDangerous Combination of Outputs tab on the <Record ID> (Protective Instrument LoopFinal Element)window contains the Dangerous Combination of Outputs? check box, which letsyou indicate whether the final element represented by the current record is associated with anyhazards that result from a combination of output states. When the Dangerous Combination ofOutputs? check box is:

l Selected, the remaining options on the Dangerous Combination of Outputs tab areenabled, and amessage appears, indicating that youmust link at least one ProtectiveInstrument Loop Final Element record to the current Protective Instrument Loop Final Ele-ment record. The additional Protective Instrument Loop Final Element record representsthe final element whose output state combined with the output state of the current final ele-ment can lead to a hazardous event. After you link at least one Protective Instrument LoopFinal Element record to the current record, themessage is hidden.

l Cleared, the remaining options on the Dangerous Combination of Outputs tab are dis-abled. This indicates that the final element represented by the current Protective Instru-ment Loop Final Element record is not associated with any combined output state hazards.You will need to open the linked Protective Instrument Loop Final Element record andenter the description of the combined output state hazard.

After at least one Protective Instrument Loop Final Element record is linked to the current Pro-tective Instrument Loop Final Element record, the Dangerous Combination of Outputs? checkbox is disabled. In addition, you can clear this check box only if the Individual Output States gridis empty (i.e., there are no combined output state hazards associated with the final element).

Below the Dangerous Combination of Outputs? check box, the following sections appear:

l Individual Output States: Contains a grid that displays the list of Protective InstrumentLoop Final Element records that are linked to the current Protective Instrument Loop FinalElement record. Each row in the grid represents one final element whose output state canlead to a hazardous event if it is combined with the output state associated with the outputstate of the current final element. The following information is displayed for each ProtectiveInstrument Loop Final Element record that appears in the grid:

n Final Element ID: An ID for the final element that is stored in the Final Element IDfield in the corresponding Protective Instrument Loop Final Element record.

n Final Element Description: A description for the final element that is stored in theDescription field in the corresponding Protective Instrument Loop Final Elementrecord.

n Function ID: The value stored the IF ID field in the Instrumented Function record towhich the corresponding Protective Instrument Loop Final Element record is linked.

n Function Description: The value stored in the IF Description field in the Instru-mented Function record to which the corresponding Instrument Loop Final Elementrecord is linked.

Aspects of the Dangerous Combination of Output States Tab in Protective Instrument Loop Final Element



n Add Existing: Displays the Find Items window, which you can use to search for an exist-ing Protective Instrument Loop Final Element record and link it to the current ProtectiveInstrument Loop Final Element record. After you link a Protective Instrument Loop FinalElement record to the current Protective Instrument Loop Final Element record, a new rowwill appear in the Individual Output States grid to represent that final element.

n Remove: After displaying a confirmationmessage, deletes the link between the selectionProtective Instrument Loop Final Element record and the current Protective InstrumentLoop Final Element record and removes the final element from the grid. This button is dis-abled until at least one Protective Instrument Loop Final Element record appears in theIndividual Output States grid.

l Potential Combination of Outputs Description: Contains a field, which stores the descrip-tion of the combined output state hazards that are associated with the current final ele-ment. This field is required. If the current final element is associated with multiple combinedoutput state hazards, you should provide a description in this field for each of these haz-ards.

Defining CombinedOutput State Hazards for Final Elements


Defining Combined Output State Hazards for Final Ele-mentsTo define a combined output state hazard for final elements, you will need to:

n Link to one another the Protective Instrument Loop Final Element recordswhose asso-ciated output states can cause a hazard if they occur simultaneously.

n Describe in each of the Protective Instrument Loop Final Element records the hazardousevent that can occur if the output states associated with the final elements occur sim-ultaneously.

To define a combined output state hazard for final elements:

1. Open the Protective Instrument Loop record that contains the final element for which youwant to define a combined output state hazard.

2. In the DiagramCanvas, double-click the Final Element node representing the final elementfor which you want to define a combined output state hazard.

The Protective Instrument Loop Final Element record appears in the <Record> (Pro-tective Instrument Loop Final Element)window.



3. Click the Dangerous Combination of Outputs tab.

The Dangerous Combination of Outputs tab appears.



4. Select the Dangerous Combination of Outputs? check box.

The remaining options are enabled, and amessage appears, indicating that youmust linkat least one Protective Instrument Loop Final Element record to the current ProtectiveInstrument Loop Final Element record.



5. In the Individual Output States section, click the Add Existing button.

The Search Related Final Element dialog box appears, displaying the list of existing Pro-tective Instrument Loop Final Element records.



6. In the grid, select the rows containing the Protective Instrument Loop Final Elementrecords that you want to link to the current Protective Instrument Loop Final Elementrecord, and then clickOK. Keep inmind the records you select should represent the finalelements whose output states can lead to a hazardous event if they occur simultaneouslywith the output state of the current final element.

The Search Related Final Element dialog box closes, and the record(s) you selectedappear in the Individual Output States grid. For example, in the following image, you cansee that two Protective Instrument Loop Final Element records are linked to the ProtectiveInstrument Loop Final Element record XL0615-009 A.



7. In the Combination Hazardous Event section, enter a description for the hazardous eventthat can occur if the output states associated with the final elements occur simultaneously.

8. In the Individual Output States section, in the first row in the grid, click the hyperlinked IDin the Final Element ID cell.

The corresponding Protective Instrument Loop Final Element record appears in a new<Record ID> (Protective Instrument Loop Final Element) window.




The Dangerous Combination of Outputs tab appears. In addition, you can see that theDangerous Combination of Outputs? check box is selected automatically and the Indi-vidual Output States grid contains the Protective Instrument Loop Final Element record towhich the current record is linked (i.e., the record fromwhich you accessed the currentrecord).



10. In the Combination Hazardous Event section, enter a description for the hazardous eventthat can occur if the output states associated with the final elements occur simultaneously.This should be the same description that you entered in step 7.

11. ClickOK.

Your changes are saved, and the Protective Instrument Loop Final Element record closes,revealing the previous Protective Instrument Loop Final Element record.

12. Repeat steps 8 through 11 for each Protective Instrument Loop Final Element record thatappears in the Individual Output States grid.

13. ClickOK.

Your changes are saved, and the Protective Instrument Loop Final Element record closes.

Removing Final Elements From the Dangerous Combination of Outputs Tab


Removing Final Elements From the Dangerous Com-bination of Outputs TabWhen you remove a final element from the Dangerous Combination of Outputs tab, you aredeleting the link between the Protective Instrument Loop Final Element records.

To remove a final element from the Dangerous Combination of Outputs tab:

1. Open the Protective Instrument Loop that contains the final element whose correspondingrecord you want to modify.

2. In the DiagramCanvas, double-click the Final Element node representing the final elementfromwhich you want to remove a different final element.

The Protective Instrument Loop Final Element record appears in a new window.

Removing Final Elements From the Dangerous Combination of Outputs Tab



The Dangerous Combination of Outputs tab appears.

4. In the Individual Output States grid, select the row containing the final element that youwant to remove.

ŒHint: Youmaywant to update the text stored in the Combination Hazardous Eventsection in the corresponding Protective Instrument Loop Final Element record beforeyou remove it from the current record. To do so, click the hyperlinked value in the FinalElement ID cell in that row.



ŒHint: Youmaywant to update the text stored in the Combination Hazardous Eventsection in the current record.


Your changes are saved, and the Protective Instrument Loop Final Element record closes.

About the Protective Instrument Loop Report


About the Protective Instrument Loop ReportThe Protective Instrument Loop report provides an overview of the protective instrument loopand displays the following information:

l Loop ID: Displays the value that exists in the Loop ID field in the associated ProtectiveInstrument Loop record.

l Description: Displays the value that exists in the Description field in the associated Pro-tective Instrument Loop record.

l Long Description: Displays the value that exists in the Long Description field in the asso-ciated Protective Instrument Loop record.

l Loop Class: Displays the value that exists in the Loop Class field in the associated Pro-tective Instrument Loop record.

l Loop Type: Displays the value that exists in the Loop Type field in the associated Pro-tective Instrument Loop record.

l SIL Demand Mode: Displays the value that exists in the DemandMode field in the asso-ciated Protective Instrument Loop record.

l Systematic Capability Validation: Displays the value that exists in the Systematic Cap-ability Validation field in the associated Protective Instrument Loop record.

l Mission Time: Displays the value that exists in theMission Time field in the associatedProtective Instrument Loop record.

l Startup Time: Displays the value that exists in the Startup Time field in the associated Pro-tective Instrument Loop record.

l Required SIL: Displays the value that exists in the Required SIL field in the associated Pro-tective Instrument Loop record.

l Meets SIL Requirements:Displays the value that exists in theMeets SIL Requirement?field in the associated Protective Instrument Loop record.

l Achieved SIL: Displays the value that exists in the Achieved SIL field in the associated Pro-tective Instrument Loop record.

l Evaluated Architectural Constraints: Displays the value that exists in theMeets Archi-tectural Constraints field in the associated Protective Instrument Loop record.

l Risk Reduction Factor: Displays the value that exists in the Risk Reduction Factor field inthe associated Protective Instrument Loop record.

l MTTS (years): Displays the value that exists in theMTTFS Years field in the associatedProtective Instrument Loop record.

l Status: Displays the value that exists in the Status field in the associated Protective Instru-ment Loop record.

l Status Changed Date: Displays the date on which the value in the Status field wasupdated last.

l Status Changed By: Displays the value that exists in the Last Modified By field in the asso-ciated Protective Instrument Loop record.

About the Protective Instrument Loop Report


l Last Modified By: Displays the value that exists in the Last Modified By field in the asso-ciated Protective Instrument Loop record.

l Last Modified Date: Displays the value that exists in the Last Modified Date field in theassociated Protective Instrument Loop record.

In addition to the preceding information, the Protective Instrument Loop Report contains a table,which contains various information that is stored in the Protective Instrument Loop Elementrecords that are linked to the Protective Instrument Loop record.

Viewing the Protective Instrument Loop Report


Viewing the Protective Instrument Loop ReportTo view the Protective Instrument Loop report:

1. Open the protective instrument loop or protective instrument loop template for which youwant to view the Protective Instrument Loop report.

2. On the Common Tasks menu, click the Reports link.

A submenu appears.

3. On the submenu, click the Protective Instrument Loop Report link.

Note: The name of the link is the caption of the Catalog itemProtective Instrument LoopReport. This link is called the Protective Instrument Loop Report by default.

The Protective Instrument Loop report appears in the Report Viewer.

Viewing SIL Analysis Graphs


Viewing SIL Analysis GraphsThe following instructions provide details on viewing the graphs that appear on theGraphs sub-menu on the Common Tasks menuwhen you are viewing and SIL Analysis record. This sub-menu displays all the reports that exist in the Catalog folder \\Public\Meridium\Modules\SISManagement\SIL\Graphs.

To view an SIL Analysis graph:

1. Access the SIL Analysis record whose report you want to view.

2. On the Common Tasks menu, click the Graphs link.

A submenu appears.

3. On the submenu, click the link that corresponds to the caption of the graph that you want toview. For example, click the SIL Assignment Summary Graph link.

The selected report appears in the Graph Viewer. The following image shows an exampleof the baseline SIL Assignment SummaryGraph.

Viewing SIL Analysis Graphs


Viewing SIL Analysis Reports


Viewing SIL Analysis ReportsThe following instructions provide details on viewing the reports that appear on the Reports sub-menu on the Common Tasks menuwhen you are viewing and SIL Analysis record. This sub-menu displays the reports that exist in the Catalog folder \\Public\Meridium\Modules\SISManagement\SIL\Reports. By default, this folder contains the SIL Analysis Report.

To view an SIL Analysis report:

1. Access the SIL Analysis record whose report you want to view.


A submenu appears.

3. On the submenu, click the link that corresponds to the caption of the report that you want toview. For example, click the SIL Analysis Report link.

The selected report appears in the Report Viewer.

About the Safety Requirement Specifications Report


About the Safety Requirement Specifications ReportThe Safety Requirement Specifications report contains all the details from an SIL Analysis thatare required tomeet compliance for IEC standard 61511. You can use this report to:

l Provide proof of compliance with IEC 61511.

l Identify gaps in compliance with IEC 61511.

The Safety Requirement Specifications report displays values that are stored in the records thatmake up an SIL Analysis.

It is stored in the Catalog folder \\Public\Meridium\Modules\SIS Management\SIL\Reports andtitled SRS Report. You can access the report using the Reports link on the Common Tasksmenu on the SIL Analysis Definition page.When you access the Safety Requirement Spe-cifications report in this way, theMeridiumAPM systemwill automatically pass in the Entity Keyfor the SIL Analysis record to which all other records that make up and SIL Analysis are linked.

While you can run the Safety Requirement Specifications report directly from the Catalog folderand pass in an Entity Keymanually, we recommend that you run the report via the SIL Analysiswithin the SIS Management module. In addition, you should not modify the report or any of its sup-porting queries or subreports.

Accessing the Safety Requirement Specifications Report


Accessing the Safety Requirement SpecificationsReportThe following instructions provide details on accessing the Safety Requirement Specificationsreport for an SIL Analysis. When you run the Safety Requirement Specifications report, theMeridiumAPM systemwill automatically pass in the Entity Key of the SIL Analysis record towhich all other records that make up the SIL Analysis are linked.

To access the Safety Requirement Specification report:

1. Open the SIL Analysis for which you want to view the Safety Requirement Specificationsreport.


A submenu appears, displaying the captions of the following Catalog items as links:

l SIL Analysis Report

l SRS Report

3. Click the SRS Report link.

The Safety Requirement Specifications report appears in the Report Viewer.

Accessing the Safety Requirement Specifications Report


About Managing Validation Failure Rate Reference Data


About Managing Validation Failure Rate ReferenceDataFailure rate reference data refers to data that exists to record trends in failure rates for elementsthat exist in a protective instrument loop. Before you add an element to a protective instrumentloop, you can consider the failure rate reference data that is associated with that element andmake a decision on whether or not to use that particular element.

SIS Management provides tools that you can use to view Protective Instrument Loop Elementrecords for sensors, logic solvers, and final elements, where the Is Reference Data field in thatrecord is set to True. The Is Reference Data check box is not included on the datasheet bydefault. This field is used by theMeridiumAPM system and is not meant to bemodifiedmanually.

When you create a Protective Instrument Loop Element record via the Validation Failure RateReference Data feature, theMeridiumAPM systemwill automatically select the Is ReferenceData check box in that record.

You can use the Validation Failure Rate Reference Data feature to determine which elementsare approved for use with a protective instrument loop. After you have determined that a givenelement is approved, you can select Approve button below the datasheet. When you do so, theMeridiumAPM systemwill automatically select the Approved Custom Device check box in thatrecord, and it will be available for selection in the SIL Validation feature. To approve a ProtectiveInstrument Loop Element record, youmust be amember of the SIS Administrator or SIS Engin-eer Security Group.

Navigation


Navigation

TheNavigation menu in the Validation Failure Rate Reference Data feature contains the fol-lowing links:

l Sensors: Displays theSensor Reference Data Searchpage, where you can search forSensor records.

l Logic Solvers: Displays theLogic Solver Reference Data Searchpage, where you cansearch for Logic Solver records.

l Final Elements: Displays the Final Element Reference Data Search page, where youcan search for Final Element records.

A green arrow to the left of an option indicates the Protective Instrument Loop Element familywith which you are currently working.

Common Tasks


Common Tasks

TheCommon Tasks menu in the Validation Failure Rate Reference Data Feature contains thefollowing links, which are context-sensitive, meaning that the family with which you are currentlyworking will determine the specific context of the link:

l Create: Displays a new blank record in the family with which you are currently working.

l Copy: Displays a new record in the family with which you are currently working that is pop-ulated automatically with information from the source record.

l Delete: Displays a confirmationmessage and then deletes the selected record.


l Help: Displays the context-sensitive Help topic for the current page.

Accessing the Sensor Reference Data Search Page


Accessing the Sensor Reference Data Search PageThe Sensor Reference Data Search page appears by default when you access the ValidationFailure Rate Reference Data feature.

To access the Sensor Reference Data Search page:


2. Click theManage Validation Failure Rate Reference Data link.

The Sensor Reference Data Search page appears.

Aspects of the Sensor Reference Data Search Page


Aspects of the Sensor Reference Data Search PageThe Sensor Reference Data Search page contains the results of the Sensor_Reference_Data_Search query. This documentation assumes that you are using the baseline query, which con-tains an Approved to Use prompt that appears as a list at the top of the Sensor Reference DataSearch page. The Approved to Use list contains a list of values that correspond to the state ofthe Approved CustomDevice field in the Protective Instrument Loop Sensor records. You canchoose from the following baseline values:

l Yes: Displays all the existing Protective Instrument Loop Sensor recordswhose Is Refer-ence Data field is set toTrueand whoseApproved Custom Devicecheck box is selected.

l No: Displays all the existing Protective Instrument Loop Sensor recordswhose Is Refer-ence Data field is set toTrueand whose Approved Custom Device check box is cleared.

l Any (%): Displays all the existing Protective Instrument Loop Sensor recordswhose IsReference Data field is set to True.

This query is run automatically using the default prompt value Any (%). If you select different cri-teria, you can click the Run Query button to run the query and display the results in the grid at thebottom of the page. The query results will include hyperlinked Record IDs, which you can use toopen the Protective Instrument Loop Sensor record on the Sensor Reference Data page.

Below the query results are options that you can use to navigate the results.

The Sensor Reference Data Search page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Opening Existing Protective Instrument Loop Sensor Records


Opening Existing Protective Instrument Loop SensorRecordsTo open an existing Protective Instrument Loop Sensor record:

1. Access the Sensor Reference Data Search page.

2. Provide the desired search criteria, and then click the Run Query button.


3. In the grid, locate the row containing the Protective Instrument Loop Sensor record whosecontents you want to view.

4. In the Sensor ID cell, click the hyperlinked Record ID for the desired record.

The selected record appears on the Sensor Reference Data page.

Aspects of the Sensor Reference Data Page


Aspects of the Sensor Reference Data Page

Note: You can access the Sensor Reference Data page by opening an existing ProtectiveInstrument Loop Sensor record or creating a new one.

The Sensor Reference Data page displays the datasheet for a Protective Instrument LoopSensor record. The Protective Instrument Loop Sensor datasheet is amaster/detail datasheet,meaning that below themaster record, a Devices pane appears, which contains a list of Pro-tective Instrument Device records that are linked to the Protective Instrument Loop Sensorrecord. The Protective Instrument Device records that appear in this pane will depend on the val-ues that exist in the Sensor field in themaster record. You can collapse and expand the Devicespane using the and buttons that appears in the top right corner of the pane.

Below the datasheet, the following buttons appear:

l Save: Saves the Protective Instrument Loop Sensor record.

l Approve: Selects the Approve Custom Device check box on the Protective InstrumentLoop Sensor datasheet. After you click this button, the label changes to Revoke Approval.

l Revoke Approval: Clears the Approve Custom Device check box on the ProtectiveInstrument Loop Sensor datasheet. After you click this button, the label changes toApprove.

The Sensor Reference Data page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Using the Sensor Reference Data page, you can:

l Create new Protective Instrument Loop Sensor records from scratch.

l Create new Protective Instrument Loop Sensor records as copies of existing ProtectiveInstrument Loop Sensor records.

l Approve Protective Instrument Loop Sensor records.

l Revoke approval for Protective Instrument Loop Sensor records.

Creating New Protective Instrument Loop Sensor Records from Scratch


Creating New Protective Instrument Loop SensorRecords from ScratchThe following instructions provide details on creating a Protective Instrument Loop Sensor recordfor the Validation Failure Rate Reference Data feature. You can also create Protective Instru-ment Loop Sensor records using the SIL Validation feature.

To create a new Protective Instrument Loop Sensor record:

1. Access the Sensor Reference Data Search page.

2. On the Common Tasks menu, click the Create link.

The Sensor Reference Data page appears, displaying a new blank Protective InstrumentLoop Sensor record.

3. Provide values in the fields as desired. Note that when you select a value in the Sensor list,Protective Instrument Device recordswill appear in the Devices pane.

4. Below the datasheet, click the Save button.


Creating Protective Instrument Loop Sensor Records as Copies of an Existing One


Creating Protective Instrument Loop Sensor Recordsas Copies of an Existing OneThe following instructions provide details on creating a new Protective Instrument Loop Sensorrecord as a copy of an existing Protective Instrument Loop Sensor record. These instructionsassume that you are using the Validation Failure Rate Reference Data feature. You can also cre-ate Protective Instrument Loop Sensor records using the SIL Validation feature.

When you create a new Protective Instrument Loop Sensor record as a copy of an existing one,the new Protective Instrument Loop Sensor record will contain the same information as thesource record, with the following exceptions:

l The Approved Custom Device check boxwill be clear by default. This setting is clear bydefault in all new Protective Instrument Loop Sensor records.

l The value in the Sensor ID field will be appended with the number 1 (one). For each sub-sequent Protective Instrument Loop Sensor record that you create as a copy of the sameexisting Protective Instrument Loop Sensor record, an additional 1 (one) will be appendedto the Sensor ID. For example, if you create three new Protective Instrument Loop Sensorrecords using the Protective Instrument Loop Sensor record with the Sensor ID Fire GasSensor A, the Sensor ID values for the new recordswill be:

n Fire GasSensor A 1

n Fire GasSensor A 1 1

n Fire GasSensor A 1 1 1

You canmodify the Sensor ID value, if desired.

If the Protective Instrument Loop Sensor record is linked to Protective Instrument Devicerecords, those record will also be copied and linked to the new record. When a Protective Instru-ment Device record is copied, the value in the ID field will be appended with the number 1 (one).For each subsequent Protective Instrument Loop Sensor record that you create as a copy of thesame source record (i.e., that is linked to the same Protective Instrument Device record), an addi-tional number 1 (one) will be appended to the ID in the new Protective Instrument Device record.You canmodify the ID value, if desired.

To create a new Protective Instrument Loop Sensor record as a copy of an existing Pro-tective Instrument Loop Sensor record:

1. Open the Protective Instrument Loop Sensor record that you want to copy to create a newProtective Instrument Loop Sensor record.

The Protective Instrument Loop Sensor record appears on the Sensor ReferenceDatapage.



2. On the Common Tasks menu, click the Copy link.

The new Protective Instrument Loop Sensor record appears on the Sensor ReferenceData page.



3. If desired, you canmodify the record. When you are finished, click the Save button.


Approving and Revoking Approval for Protective Instrument Loop Sensor Records


Approving and Revoking Approval for Protective Instru-ment Loop Sensor RecordsAfter you have determined that a sensor is approved for use in a protective instrument loop, youcan specify that in the Protective Instrument Loop Sensor record. Additionally, if you later determ-ine that a sensor is no longer approved for use in a protective instrument loop, you can revokethat approval in the Protective Instrument Loop Sensor record.

To approve a Protective Instrument Loop Sensor record:

1. Open the Protective Instrument Loop Sensor record that represents the sensor that youwant to approve.

2. Below the datasheet, click the Approve button.

The Approved Custom Device check box in the Protective Instrument Loop Sensorrecord is automatically selected, and the label on the Approve button changes to RevokeApproval.



To revoke approval for a Protective Instrument Loop Sensor record:

1. Open the Protective Instrument Loop Sensor record that represents the sensor whoseapproval status you want to revoke.

2. Below the datasheet, click the Revoke Approval button.

The Approved Custom Device check box in the Protective Instrument Loop Sensorrecord is automatically cleared, and the label on the Revoke Approval button changes toApprove.



Accessing the Logic Solver Reference Data Search Page


Accessing the Logic Solver Reference Data SearchPageThe Logic Solver Reference Data Search page lets you search for existing Protective Instru-ment Loop Logic Solver records that are specified as reference data via the Is Reference Datacheck box in that family.

To access the Logic Solver Reference Data Search page:




3. On the Navigation menu, click the Logic Solvers link.

The Logic Solver Reference Data Search page appears.

Aspects of the Logic Solver Reference Data Search Page


Aspects of the Logic Solver Reference Data SearchPageThe Logic Solver Reference Data Search page contains the results of the Logic_Solver_Refer-ence_Data_Search query. This documentation assumes that you are using the baseline query,which contains an Approved to Use prompt that appears as a list at the top of the Logic SolverReference Data Search page. The Approved to Use list contains a list of values that correspondto the state of the Approved CustomDevice field in the Protective Instrument Loop Logic Solverrecords. You can choose from the following baseline values:

l Yes: Displays all the existing Protective Instrument Loop Logic Solver recordswhose IsReference Data field is set toTrue and whose Approved Custom Device check box isselected.

l No: Displays all the existing Protective Instrument Loop Logic Solver recordswhose IsReference Data field is set toTrue and whose Approved Custom Device check box iscleared.

l Any (%): Displays all the existing Protective Instrument Loop Logic Solver recordswhoseIs Reference Data field is set to True.

This query is run automatically using the default prompt value Any (%). If you select different cri-teria, you can click the Run Query button to run the query and display the results in the grid at thebottom of the page. The query results will include hyperlinked Record IDs, which you can use toopen the Protective Instrument Loop Logic Solver record on the Sensor Reference Data page.


The Logic Solver Reference Data Search page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Opening Existing Protective Instrument Loop Logic Solver Records


Opening Existing Protective Instrument Loop LogicSolver RecordsTo open an existing Protective Instrument Loop Logic Solver record:

1. Access the Logic Solver Reference Data Search page.



3. In the grid, locate the row containing the Protective Instrument Loop Logic Solver recordwhose contents you want to view.

4. In the ID cell, click the hyperlinked Record ID for the desired record.

The selected record appears on the Logic Solver Reference Data page.

Aspects of the Logic Solver Reference Data Page


Aspects of the Logic Solver Reference Data Page

Note: You can access the Logic Solver Reference Data page by opening an existing Pro-tective Instrument Loop Logic Solver record or creating a new one.

The Logic Solver Reference Data page displays the datasheet for a Protective Instrument LoopLogic Solver record. The Protective Instrument Loop Logic Solver datasheet is amaster/detaildatasheet, meaning that below themaster record, a Channels/Modules pane appears, whichcontains a list of Protective Instrument Loop Logic Solver Channel records that are linked to theProtective Instrument Loop Logic Solver record. You can link Protective Instrument Loop LogicSolver Channel records to themaster record or delete the link between these records using theAdd and Remove options that appears in this pane. You can collapse and expand the Chan-nels/Modules pane using the and buttons that appears in the top right corner of the pane.


l Save: Saves the Protective Instrument Loop Logic Solver record.

l Approve: Selects the Approve Custom Devicecheck box on the Protective InstrumentLoop Logic Solver datasheet. After you click this button, the label changes to RevokeApproval.

l Revoke Approval: Clears the Approve Custom Device check box on the ProtectiveInstrument Loop Logic Solver datasheet. After you click this button, the label changes toApprove.


l Navigation

l Common Tasks

l Associated Pages

Using the Logic Solver Reference Data page, you can:

l Create Protective Instrument loop Logic Solver records from scratch.

l Create Protective Instrument Loop Logic Solver records that are based upon an existingProtective Instrument Loop Logic Solver record.

l Create Protective Instrument Loop Logic Solver records as copies of an existing ProtectiveInstrument Loop Logic Solver record.

l Link Protective Instrument Loop Logic Solver Channel records to a Protective InstrumentLoop Logic Solver record.

l Remove the links between a Protective Instrument Loop Logic Solver record and Pro-tective Instrument Loop Logic Solver Channel records.

l Approve a Protective Instrument Loop Logic Solver record.

l Revoke approval for a Protective Instrument Loop Logic Solver record.

Creating Protective Instrument Loop Logic Solver Records from Scratch


Creating Protective Instrument Loop Logic SolverRecords from ScratchThe following instructions provide details on creating a Protective Instrument Loop Logic Solverrecord from scratch using the Validation Failure Rate Reference Data feature. You can also cre-ate Protective Instrument Loop Logic Solver records using the SIL Validation feature.

To create a new Protective Instrument Loop Logic Solver record from scratch:



The Logic Solver Reference Data page appears, displaying a new blank Protective Instru-ment Loop Logic Solver record.

3. Provide values in the fields as desired.


The record is saved. At this point, you can link the desired Protective Instrument LoopLogic Solver Channel records to the Protective Instrument Loop Logic Solver record.

Creating Protective Instrument Loop Logic Solver Records Based on Existing Ones


Creating Protective Instrument Loop Logic SolverRecords Based on Existing OnesThe following instructions provide details on creating a Protective Instrument Loop Logic Solverrecord based on an existing one, using the Validation Failure Rate Reference Data feature. Youcan also create Protective Instrument Loop Logic Solver records using the SIL Validation feature.

To create a new Protective Instrument Loop Logic Solver record based on an existing one:



The Logic Solver Reference Data page appears, displaying a new blank Protective Instru-ment Loop Logic Solver record.

3. In theMTTR text box, type the desired numeric value. This field is require before you canapply an existing record.

4. In the Proof Test Interval text box, type the desired numeric value. This field is requirebefore you can apply an existing record.

5. In the Proof Test Coverage text box, type the desired numeric value. This field is require

Creating Protective Instrument Loop Logic Solver Records Based on Existing Ones


before you can apply an existing record.

6. Click the Select button.

The Protective Instrument Loop dialog box appears, displaying the list of existing Pro-tective Instrument Loop Logic Solver records.

7. In the list, select the row containing the Protective Instrument Loop Logic Solver recordwhose contents you want to apply to the new Protective Instrument Loop Logic Solverrecord.

8. ClickOK.

The new Protective Instrument Loop Logic Solver record is populated automatically withinformation from the selected record, including the Channels/Modules pane.


The record is saved. At this point, you can link Protective Instrument Loop Logic SolverChannel records to the Protective Instrument Loop Logic Solver record.

Creating Protective Instrument Loop Logic Solver Records as Copies of an Existing One


Creating Protective Instrument Loop Logic SolverRecords as Copies of an Existing OneThe following instructions provide details on creating a new Protective Instrument Loop LogicSolver record as a copy of an existing Protective Instrument Loop Logic Solver record. Theseinstructions assume that you are using the Validation Failure Rate Reference Data feature. Youcan also create Protective Instrument Loop Logic Solver records using the SIL Validation feature.

When you create a new Protective Instrument Loop Logic Solver record as a copy of an existingone, the new Protective Instrument Loop Logic Solver record will contain the same information asthe source record, with the following exceptions:

l The Approved Custom Device check boxwill be clear by default. This setting is clear bydefault in all new Protective Instrument Loop Logic Solver records.

l The value in the Logic Solver ID field will be appended with a number that is relative to sub-sequent copies of the same source record, beginning with 1 (one). For each subsequentProtective Instrument Loop Logic Solver record that you create as a copy of the same exist-ing Protective Instrument Loop Logic Solver record, the number that is appended to theLogic Solve ID will increase by one. For example, if you create three new Protective Instru-ment Loop Logic Solver records using the Protective Instrument Loop Logic Solver recordwith the Logic Solver ID Logic Solver A, the Logic Solver ID values for the new recordswillbe:

n Logic Solver A 1

n Logic Solver A 2

n Logic Solver A 3

You canmodify the Logic Solver ID value, if desired.

If the Protective Instrument Loop Logic Solver record is linked to Protective Instrument LoopLogic Solver Channel records, these recordswill also be copied and linked to the new ProtectiveInstrument Loop Logic Solver record. When a Protective Instrument Logic Solver Channel recordis copied, the value in the ID field will be appended with a number that is relative to the sub-sequent copies of the same source Protective Instrument Logic Solver record, beginning with 1(one). For each subsequent Protective Instrument Loop Logic Solver record that you create as acopy of the same source record, the value that is appended to the ID in the new Protective Instru-ment Logic Solver Channel recordswill increase by one (as explained above).

To create a new Protective Instrument Loop Logic Solver record as a copy of an existingProtective Instrument Loop Logic Solver record:

1. Open the Protective Instrument Loop Logic Solver record that you want to copy to create anew Protective Instrument Loop Logic Solver record.

The Protective Instrument Loop Logic Solver record appears on the Logic Solver Refer-ence Data page.




The new Protective Instrument Loop Logic Solver record appears on the Logic SolverReference Data page.



3. If desired, you canmodify the record. When you are finished, click the Save button.


Linking Protective Instrument Loop Logic Solver Channel Records to Protective Instrument Loop Logic Solver


Linking Protective Instrument Loop Logic Solver Chan-nel Records to Protective Instrument Loop Logic SolverRecordsThe following instructions provide details on linking Protective Instrument Loop Logic SolverChannel records to existing Protective Instrument Loop Logic Solver records using the ValidationFailure Rate Reference Data feature. You can also link these records using the SIL Validationfeature. For details on using the SIL Validation feature, see the SIL Validation section of this Helpsystem.

ŗIMPORTANT: Before you can link a Protective Instrument Loop Logic Solver Channel recordto a Protective Instrument Loop Logic Solver record, youmust select theManual Entry checkbox in the Protective Instrument Loop Logic Solver record.

To link a Protective Instrument Loop Logic Solver Channel record to a Protective InstrumentLoop Logic Solver record:

1. On the Protective Instrument Loop Logic Solver datasheet for the record to which you wantto link a Protective Instrument Loop Logic Solver Channel record, in the Chan-nels/Modules pane, click the Add button.

A new Protective Instrument Loop Logic Solver Channel record appears in a new window.

2. Provide values in the fields on the datasheet as desired, and then clickOK.

Linking Protective Instrument Loop Logic Solver Channel Records to Protective Instrument Loop Logic Solver


The record is linked to themaster record and appears in the grid in the Channels/Modulespane.

3. You can continue adding records in this way.When you are finished, below the datasheet,click the Save button.


Removing Protective Instrument Loop Logic Solver Channel Records from Protective Instrument Loop Logic


Removing Protective Instrument Loop Logic SolverChannel Records from Protective Instrument LoopLogic Solver RecordsWhen you remove a Protective Instrument Loop Logic Solver Channel record from a ProtectiveInstrument Loop Logic Solver record, you are deleting the link between the two records andremoving the Protective Instrument Loop Logic Solver Channel record from the grid in the Chan-nels/Modulespane on the Protective Instrument Loop Logic Solver datasheet.

To remove a Protective Instrument Loop Logic Solver Channel record from a ProtectiveInstrument Loop Logic Solver record:

1. Open the Protective Instrument Loop Logic Solver record that is linked to the ProtectiveInstrument Loop Logic Solver Channel record that you want to remove.

2. In the Channels/Modules pane, select the row containing the Protective Instrument LoopLogic Solver Channel record that you want to remove.

3. Below the grid, click the Remove button.

A message appears, asking if you are sure you want to remove the selected record.


The record is removed from the grid.



Approving and Revoking Approval for Protective Instrument Loop Logic Solver Records


Approving and Revoking Approval for Protective Instru-ment Loop Logic Solver RecordsAfter you have determined that a logic solver is approved for use in a protective instrument loop,you can specify that in the Protective Instrument Loop Logic Solver record. Additionally, if youlater determine that a logic solver is no longer approved for use in a protective instrument loop,you can revoke that approval in the Protective Instrument Loop Logic Solver record.

To approve a Protective Instrument Loop Logic Solver record:

1. Open the Protective Instrument Loop Logic Solver record that represents the logic solverthat you want to approve.


The Approved Custom Device check box in the Protective Instrument Loop Logic Solverrecord is automatically selected, and the label on the Approve button changes to RevokeApproval.



To revoke approval for a Protective Instrument Loop Logic Solver record:

1. Open the Protective Instrument Loop Logic Solver record that represents the logic solverwhose approval status you want to revoke.


The Approved Custom Device check box in the Protective Instrument Loop Logic Solverrecord is automatically cleared, and the label on the Revoke Approval button changes toApprove.



Accessing the Final Element Reference Data Search Page


Accessing the Final Element Reference Data SearchPageThe Final Element Reference Data Search page lets you search for existing Protective Instru-ment Loop Final Element records that are specified as reference data via the Is Reference Datacheck box in that family.

To access the Final Element Reference Data Search page:




3. On the Navigation menu, click the Final Elements link.

The Final Element Reference Data Search page appears.

Aspects of the Final Element Reference Data Search Page


Aspects of the Final Element Reference Data SearchPageThe Final Element Reference Data Search page contains the results of the Final_Element_Reference_Data_Search query. This documentation assumes that you are using the baselinequery, which contains an Approved to Use prompt that appears as a list at the top of the FinalElement Reference Data Search page. The Approved to Use list contains a list of values thatcorrespond to the state of the Approved CustomDevice field in the Protective Instrument LoopFinal Element records. You can choose from the following baseline values:

l Yes: Displays all the existing Protective Instrument Loop Final Element recordswhose IsReference Data field is set toTrue and whose Approved Custom Device check box isselected.

l No: Displays all the existing Protective Instrument Loop Final Element recordswhose IsReference Data field is set toTrue and whose Approved Custom Device check box iscleared.

l Any (%): Displays all the existing Protective Instrument Loop Final Element recordswhoseIs Reference Data field is set to True.

This query is run automatically using the default prompt value Any (%). If you select different cri-teria, you can click the Run Query button to run the query and display the results in the grid at thebottom of the page. The query results will include hyperlinked Record IDs, which you can use toopen the Protective Instrument Loop Final Element record on the Sensor Reference Data page.


The Final Element Reference Data Search page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Opening Existing Protective Instrument Loop Final Element Records


Opening Existing Protective Instrument Loop Final Ele-ment RecordsTo open an existing Protective Instrument Loop Final Element record:

1. Access the Final Element Reference Data Search page.



3. In the grid, locate the row containing the Protective Instrument Loop Final Element recordwhose contents you want to view.

4. In the Final Element ID cell, click the hyperlinked Record ID for the desired record.

The selected record appears on the Final Element Reference Data page.

Aspects of the Final Element Reference Data Page


Aspects of the Final Element Reference Data Page

Note: You can access the Final Element Reference Data page by opening an existing Pro-tective Instrument Loop Final Element record or creating a new one.

The Final Element Reference Data page displays the datasheet for a Protective InstrumentLoop Final Element record. The Protective Instrument Loop Final Element datasheet is amas-ter/detail datasheet, meaning that below themaster record, a Devices pane appears, which con-tains a list of Protective Instrument Device records that are linked to the Protective InstrumentLoop Final Element record. The Protective Instrument Device records that appear in this panewill depend on the values that exist in the Final Element field in themaster record. You can col-lapse and expand the Devices pane using the and buttons that appears in the top rightcorner of the pane.


l Save: Saves the Protective Instrument Loop Final Element record.

l Approve: Selects theApprove Custom Device check box on the Protective InstrumentLoop Final Element datasheet. After you click this button, the label changes to RevokeApproval.

l Revoke Approval: Clears the Approve Custom Device check box on the ProtectiveInstrument Loop Final Element datasheet. After you click this button, the label changes toApprove.


l Navigation

l Common Tasks

l Associated Pages

Using the Final Element Reference Data page, you can:

l Create new Protective Instrument Loop Final Element records from scratch.

l Create new Protective Instrument Loop Final Element records as copies of an existing Pro-tective Instrument Loop Final Element record.

l Approve a Protective Instrument Loop Final Element record.

l Revoke approval for a Protective Instrument Loop Final Element record.

Creating New Protective Instrument Loop Final Element Records from Scratch


Creating New Protective Instrument Loop Final Ele-ment Records from ScratchThe following instructions provide details on creating a Protective Instrument Loop Final Elementrecord for the Validation Failure Rate Reference Data feature. You can also create ProtectiveInstrument Loop Final Element records using the SIL Validation feature.

To create a new Protective Instrument Loop Final Element record:

1. Access the Final Element Reference Data Search page.


The Final Element Reference Data page appears, displaying a new blank ProtectiveInstrument Loop Final Element record.

3. Provide values in the fields as desired. Note that when you select a value in the Final Ele-ment list, Protective Instrument Device recordswill appear in the Devices pane.



Creating Protective Instrument Loop Final Element Records as Copies of an Existing One


Creating Protective Instrument Loop Final ElementRecords as Copies of an Existing OneThe following instructions provide details on creating a new Protective Instrument Loop Final Ele-ment record as a copy of an existing Protective Instrument Loop Final Element record. Theseinstructions assume that you are using the Validation Failure Rate Reference Data feature. Youcan also create Protective Instrument Loop Final Element records using the SIL Validation fea-ture.

When you create a new Protective Instrument Loop Final Element record as a copy of an existingone, the new Protective Instrument Loop Final Element record will contain the same informationas the source record, with the following exceptions:

l The Approved Custom Device check boxwill be clear by default. This setting is clear bydefault in all new Protective Instrument Loop Final Element records.

l The value in the Final Element ID field will be appended with the number 1 (one). For eachsubsequent Protective Instrument Loop Final Element record that you create as a copy ofthe same existing Protective Instrument Loop Final Element record, an additional 1 (one)will be appended to the Final Element ID. For example, if you create three new ProtectiveInstrument Loop Final Element records using the Protective Instrument Loop Final Ele-ment record with the Final Element ID Final Element A, the Final Element ID values for thenew recordswill be:

n Final Element A 1

n Final Element A 1 1

n Final Element A 1 1 1

You canmodify the Final Element ID value, if desired.

If the Protective Instrument Loop Final Element record is linked to Protective Instrument Devicerecords, those record will also be copied and linked to the new record. When a Protective Instru-ment Device record is copied, the value in the ID field will be appended with the number 1 (one).For each subsequent Protective Instrument Loop Final Element record that you create as a copyof the same source record (i.e., that is linked to the same Protective Instrument Device record),an additional number 1 (one) will be appended to the ID in the new Protective Instrument Devicerecord. You canmodify the ID value, if desired.

To create a new Protective Instrument Loop Final Element record as a copy of an existingProtective Instrument Loop Final Element record:

1. Open the Protective Instrument Loop Final Element record that you want to copy to createa new Protective Instrument Loop Final Element record.

The Protective Instrument Loop Final Element record appears on the Final Element Refer-ence Data page.

Creating Protective Instrument Loop Final Element Records as Copies of an Existing One



The new Protective Instrument Loop Logic Solver record appears on the Logic SolverReference Data page.

Approving and Revoking Approval for Protective Instrument Loop Final Element Records


Approving and Revoking Approval for Protective Instru-ment Loop Final Element RecordsAfter you have determined that a final element is approved for use in a protective instrument loop,you can specify that in the Protective Instrument Loop Final Element record. Additionally, if youlater determine that a final element is no longer approved for use in a protective instrument loop,you can revoke that approval in the Protective Instrument Loop Final Element record.

To approve a Protective Instrument Loop Final Element record:

1. Open the Protective Instrument Loop Final Element record that represents the final ele-ment that you want to approve.


The Approved Custom Device check box in the Protective Instrument Loop Final Elementrecord is automatically selected, and the label on the Approve button changes to RevokeApproval.



To revoke approval for a Protective Instrument Loop Final Element record:

1. Open the Protective Instrument Loop Final Element record that represents the final ele-ment whose approval status you want to revoke.


The Approved Custom Device check box in the Protective Instrument Loop Final Elementrecord is automatically cleared, and the label on the Revoke Approval button changes toApprove.



About SIS Trip Reports


About SIS Trip ReportsSIS Trip Reports are records that store details on events, which occurred on a safety instru-mented system such as a trip alarm. For example, if during a process, the gas pressure levelincreased to an unmanageable level and the safety instrumented system turned off the gas feed,you would create one SIS Trip Report record to record the details of that trip alarm event.

Using SIS Management, you canmanage the SIS Trip Report records that exist for all yoursafety instrumented systems.

When you create an SIS Trip Report record, you will link the record to a Safety Instrumented Sys-tem record. When you link the SIS Trip Report record to a Safety Instrumented System record,the list of Instrumented Function records that are linked to the Safety Instrumented Systemrecord will automatically appear in the SIS Trip Report record. You can select the InstrumentedFunction records that you want to associate with the SIS Trip Report record. When you selectInstrumented Function records on the SIS Trip Report datasheet, theMeridiumAPM systemwillautomatically create one SIS Trip Report Detail record for each Instrumented Function recordthat you select and automatically link the SIS Trip Report Detail record to the SIS Trip Reportrecord.

SIS Trip Report Detail records store details on the Instrumented Function with which it is asso-ciated. They also contain the decision that ismade around the particular trip event, which isstored in the Action text box. For example, you can specify a trip event asDangerousorSafe.

Accessing the SIS Trip Report Search Page


Accessing the SIS Trip Report Search PageThe SIS Trip Report Search page lets you search for and open an existing SIS Trip Reportrecord. Using this page, you can also access features that you can use to create new SIS TripReport records.

To access the SIS Trip Report Search page:


2. Click the SIS Trip Report link.

The SIS Trip Report Search page appears.

Aspects of the SIS Trip Report Search Page


Aspects of the SIS Trip Report Search PageThe SIS Trip Report Search page contains the results of the SIS_Trip_Report_Search query.This documentation assumes that you are using the baseline query, which contains a Stateprompt that appears as a list at the top of the SIS Trip Report Search page. The State list con-tains a list of record states that have been configured for the SIS Trip Report family. You canchoose from the following baseline states:

l All: Displays all the existing SIS Trip Report records that are in any state.

l Active: Displays the SIS Trip Report records that are in the Active state.

l Complete: Displays the SIS Trip Report records that are in theComplete state.

l Pending Approval: Displays the SIS Trip Report records that are in the Pending Approvalstate.

l Review: Displays the SIS Trip Report records that are in the Review state.

This query is run automatically using the default prompt value All. If you select different criteria,you can click the Run Query button to run the query and display the results in the grid at the bot-tom of the page. The query results will include hyperlinked Record IDs, which you can use toopen the SIS Trip Report record on the SIS Trip Report page.


The SIS Trip Report Search page contains the following taskmenus:

l Common Tasks

l Associated Pages

Opening Existing SIS Trip Report Records


Opening Existing SIS Trip Report RecordsTo open an existing SIS Trip Report record:

1. Access the SIS Trip Report Search page.

2. In the State list, select the record state for the desired SIS Trip Report record, and thenclick the Run Query button.

The search results appear in the grid.

3. In the grid, locate the row containing the SIS Trip Report record that you want to view.

4. In the Report ID cell in that row, click the hyperlinked Record ID.

The selected SIS Trip Report record appears on the SIS Trip Report page.

Navigation


Navigation

TheNavigationmenu on the SIS Trip Report pages contains the following links:

l SIS Trip Report Definition: Displays the SIS Trip Report page.

l SIS Trip Report Details: Displays theSIS Trip Report Details page. This link is enabledonly when you are viewing an existing SIS Trip Report record.

l Documents: Displays the Reference Documents page.This link is enabled only when youare viewing an existing SIS Trip Report record.

l All Recommendations: Displays a list of Risk Assessment Recommendation records onthe Recommendation Management page. This link is enabled only when you are viewingan existing SIS Trip Report record.

A green arrow to the left of a link indicates the feature that you are currently viewing.

Common Tasks


Common Tasks

TheCommon Tasks menu on the SIS Trip Report pages contains the following links:

l Find SIS Trip Report: Displays the SIS Trip Report Search page, where you can searchfor an existing SIS Trip Report record. This link is disabled on the SIS Trip Report Searchpage.

l Create SIS Trip Report: Displays a new blank SIS Trip Report record on the SIS TripReport page.

l Delete: Displays a confirmationmessage and then deletes the selected SIS Trip Reportrecord, and the SIS Trip Report Search page appears. This link does not appear on theSIS Trip Report Details page or the SIS Trip Report Search page.

l Recommendations: Displays the Recommendations dialog box, where you canmanageRisk Assessment Recommendation records that are linked to the SIS Trip Report record.This link is enabled only when you are viewing an existing SIS Trip Report record. This linkdoes not appear on the SIS Trip Report Details page or the SIS Trip Report Searchpage.


l Reports: Displays a submenu that displays the caption of the Catalog item SIS Trip Reportas a link. This link is enabled only when you are viewing an existing SIS Trip Report record.This link does not appear on the SIS Trip Report Details page or the SIS Trip ReportSearch page.

l Help: Displays the context-sensitive Help topic for the current page.

Aspects of the SIS Trip Report Page


Aspects of the SIS Trip Report PageThe SIS Trip Report page contains the SIS Trip Report datasheet. You can access the SIS TripReport page by opening an existing SIS Trip Report record or creating a new one.When youaccess the SIS Trip Report page by creating a new SIS Trip Report record, the Record ID of theSIS Trip Report record will not appear in the page title until after you save the new record.

Above the datasheet, the following options are enabled:

Saves the current SIS Trip Report record.

Displays the State Assignments dialog box, where you canmanage the Security Usersthat are assigned to the states that are defined for the SIS Trip Report family. To the rightof the icon, the following items appear:

n State Indicator: Displays the current state of the SIS Trip Report record.

n Operations menu: Displays the operations that are available for selection. You can usethis option to change the state of the SIS Trip Report record. This link is enabled only whenyou are viewing an existing SIS Trip Report record.

The SIS Trip Report page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Creating New SIS Trip Report Records


Creating New SIS Trip Report RecordsTo create a new SIS Trip Report record:

1. Access the SIS Trip Report Search page.

2. On the Common Tasks menu, click the Create SIS Trip Report link.

The SIS Trip Report page appears, displaying a new blank SIS Trip Report record.

3. In the Trip Report ID text box, type a name for the SIS Trip Report record. This field isrequired.

4. In the Trip Type list, select the type of trip event that the SIS Trip Report record rep-resents. This field is required.

5. Provide values in the remaining fields on the SIS Trip Report tab as desired.

6. Click the Associated Instrumented Functions tab,

The Associated Instrumented Functions tab appears.



7. In the SIS ID text box, click the button. This field is required.

The Find Items window appears, and the Search In list contains the Safety InstrumentedSystem family by default.

8. Specify the desired search criteria, and then click the Find Now button.


9. In the search results, select the desired Safety Instrumented System record, and then clickthe Open button.

The Instrumented Functions dialog box appears, displaying a list of Instrumented Func-tion records that are linked to the selected Safety Instrumented System record. The Instru-mented Function records that appear in this list automatically appear in the AssociatedInstrumented Functions list on the Associated Instrumented Functions tab.



10. In the list, select the Instrumented Function records that you want to associated with theSIS Trip Report record, and then clickOK.

The Instrumented Functions dialog box closes, revealing the SIS Trip Report datasheet,where the Record ID of the Safety Instrumented System record appears in the SIS ID textbox and the Instrumented Function records that you selected on the Instrumented Func-tions dialog box are selected in the Associated Instrumented Functions list.

Note: In the Associated Instrumented list, if you want to associate additional Instru-mented Function recordswith the SIS Trip Report record, you can select the check boxto the left of the desired record.


The record is saved, and the following links are enabled on the Navigationmenu:

l SIS Trip Report Details

l Documents

l All Recommendations

Accessing the SIS Trip Report Details Page


Accessing the SIS Trip Report Details PageThe SIS Trip Report Details page lets youmanage the SIS Trip Report Detail records that werecreated automatically based on the Instrumented Function records that are specified in the SISTrip Report record to which the SIS Trip Report Detail records are linked.

To access the SIS Trip Report Details page:

1. Open on the SIS Trip Report page the SIS Trip Report whose details you want to view.

2. On the Navigationmenu, click the SIS Trip Report Details link.

The SIS Trip Report Details page appears, displaying a list of SIS Trip Report Detailrecords that are linked to the SIS Trip Report record fromwhich you accessed the SIS TripReport Details page.

Aspects of the SIS Trip Report Details Page


Aspects of the SIS Trip Report Details PageThe SIS Trip Report Details page contains the SIS Trip Report Details workspace, which dis-plays a grid with a list of SIS Trip Report Detail records that are linked to the SIS Trip Report fromwhich you accessed the SIS Trip Report Details page. Each row in the grid represents one SISTrip Report Detail record. By default, the grid contains the following columns:

l Trip Report Detail ID: Displays the value that exists in the Trip Report Detail ID field in theSIS Trip Report Detail record. This value appears as a hyperlink, which you can click toopen the SIS Trip Report Detail record.

l Instrumented Function ID: Displays the value that exists in the Instrumented Function IDfield in the SIS Trip Report Detail record. This value appears as a hyperlink, which you canuse to open the Instrumented Function record.

l Action: Displays the value that exists in the Action field in the SIS Trip Report Detailrecord.


l Add Trip Detail: Displays theAdd Trip Details dialog box, where you can select the Instru-mented Function record that you want to use for the SIS Trip Report Detail record.

l Remove Trip Detail: Displays a confirmationmessage, and then deletes the selected SISTrip Report Detail record.

The SIS Trip Report Details page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

Using the SIS Trip Report Details page, you can:

l View an existing SIS Trip Report Details record.

l Create a new SIS Trip Report Details record.

l Delete an SIS Trip Report Details record.

Creating New SIS Trip Report Details Records


Creating New SIS Trip Report Details RecordsTo create a new SIS Trip Report Details record:

1. Access the SIS Trip Report Details page.

2. In the SIS Trip Report Details workspace, below the grid, click the Add Trip Detail button.

The Add Trip Details dialog box appears, displaying the list of Instrumented Functionrecords that are linked to the Safety Instrumented System record that is linked to the SISTrip Report record to which the SIS Trip Report Details record is linked.

3. In the list, select the Instrumented Function record that you want to use to create the SISTrip Report Details record, and then clickOK.

The Add Trip Details dialog box closes, the new SIS Trip Report Detail record is created,saved, and appears at the bottom of the list. At this point, you can open the SIS Trip ReportDetail record andmodify its contents.

Viewing SIS Trip Report Detail Records


Viewing SIS Trip Report Detail RecordsTo view an SIS Trip Report Detail record:

1. Access the SIS Trip Report Details page.

2. In the SIS Trip Report Details workspace, locate the row containing the SIS Trip ReportDetail record whose contents you want to view.

3. In the Trip Report Detail ID cell, click the hyperlinked Record ID for the desired record.

The SIS Trip Report Detail record appears in a new window.

4. Modify the values in the fields as desired, and then clickOK.


Deleting SIS Trip Report Detail Records


Deleting SIS Trip Report Detail RecordsWhen you delete an SIS Trip Report Detail record, the record and all relationships in which it par-ticipateswill be deleted from theMeridiumAPMdatabase.

To delete an SIS Trip Report Detail record:

1. Access the SIS Trip Report Detail page.

2. In the SIS Trip Report Details workspace, select the row containing the SIS Trip ReportDetail record that you want to delete.

3. Below the grid, click the Remove Trip Detail button.

A confirmationmessage appears, asking if you really want to delete the selected record.


The selected record is deleted from theMeridiumAPMdatabase and no longer appears inthe grid.

About Revision History in SIS Management


About Revision History in SIS ManagementIn addition to theMeridiumAPMFramework Tool that provides revision history for field values,which you can use tomanage revisions that aremade on individual fields in a family, SIS Man-agement provides a Revision History feature that you can use tomanage the revisionsmade foran entire SIL analysis. When you create an analysis, you link records inmultiple families to theSIL Analysis record, which represents the entire analysis. When you complete an analysis, youwill change the state of the SIL Analysis record to Complete. When you do so, a snapshot istaken of the SIL Analysis record and each record to which it is linked, either directly or indirectly.

When the SIL Analysis record state is changed to Complete, one record in the associated Revi-sion family for each family that participates in the SIS Management datamodel will be created. Inother words, one Revision record is created for each record that is linked to the SIL Analysisrecord (with the exception of the HumanResource, Risk Assessment Recommendation, andRisk Assessment families). Each Revision record stores a snapshot of the source record as itappeared when the state of the SIL Analysis record was changed. For details on how these fam-ilies are related to one another, see the illustration of the SIS Management datamodel.

If the analysis requires reassessment, after the reassessment takes place, the state of the SILAnalysis record will be changed again to the Complete state and a second set of Revisionrecordswill be created, and so on.

You can access the SIL Analysis Revision records via the Revision History link on the Nav-igationmenu.

Accessing SIL Analysis Revisions


Accessing SIL Analysis RevisionsThe following instructions provide details on accessing the Analysis Revision History page,where you can view the Revision records that exist for a given SIL Analysis.

To access the Analysis Revision History page:

1. Open the desired SIL Analysis.

2. On the Navigationmenu, click the Revision History link.

The Analysis Revision History page appears.

Note: TheRevision History link is enabled only if the SIL Analysis record for the currentanalysis has ever been set to the Complete state.

Aspects of the Analysis Revision History Page


Aspects of the Analysis Revision History PageThe Analysis Revision History page contains the following panes:

1. Revisions pane: Contains a list of all SIL Analysis Revision records that have been cre-ated for the SIL Analysis fromwhich you accessed the Analysis Revision History page.Each row in the list represents one SIL Analysis Revision record, and each item in the list islabeled using the value that exists in the Revision Date field in that SIL Analysis Revisionrecord. The rows appear in the reverse order in which theywere created and arenumbered, starting with 0, where 0 is the first revision. In other words, themost recent revi-sion will appear first in the list. When you select a row in the list:

l A hierarchical view of the SIL Analysis that existed at the time that revision was cre-ated will appear in the Selected Revision pane.

l The corresponding SIL Analysis revision record will be displayed in the Datasheetpane.

2. Selected Revisions pane: Displays a hierarchical view of the records that belong to theSIL Analysis whose revision is selected in the Revisions pane.

At the bottom of this section, the Show Changes button appears, which you can click toview the changes that weremade to the selected record during this revision. This button isenabled only if the selected record contains values that were changed since the previousrevision.

3. Datasheet pane: Displays the SIL Analysis Revision record that is currently selected in theRevisions pane or the Selected Revisions pane. Above the datasheet, the Print button

appears, which you can use to print the record that is displayed in the Datasheet pane.

The following image shows the Analysis Revision Historypage, where callouts have beenprovided to identify the numbered panes described above.

Aspects of the Analysis Revision History Page


The Analysis Revision History page contains the following taskmenus:

l Navigation

l Common Tasks

l Associated Pages

The options that appear on these taskmenus is consistent with the options that appear on thatmenu when you are viewing it on other pages in SIS Management.

On the Analysis Revision History page, you can:

l View the Revision record for the desired record.

l View the specific changes that weremade to a given Revision record.

Common Tasks Menu


Common Tasks Menu

TheCommon Tasks menu on the Analysis Revision History page contains the following links:






l Help: Displays the context-sensitive help topic for the Analysis Revision History page.

Viewing the Datasheet for a Revision Record


Viewing the Datasheet for a Revision RecordTo view the datasheet for a Revision record:

1. Access the Analysis Revision History page.

2. In the Revisions pane, select the row that represents the revision of the SIL Analysis thatyou want to view.

The corresponding SIL Analysis Revision record appears in the Datasheet pane, and thecorresponding revisions appear in the Selected Revision pane.

3. In the Selected Revisions pane, select the Revision record whose datasheet you want toview.

The Revision record for the selected record appears in the Datasheet pane.

Viewing Changes That WereMade Between Revisions


Viewing Changes That Were Made Between RevisionsTo view changes that were made between revisions:

1. Access the Analysis Revision History page.

2. In the Revisions pane, select the revision for which you want to see themodified values.

3. In the Selected Revisions pane, select the record for which you want to see themodifiedvalues.

4. At the bottom of the Selected Revisions pane, click the Show Changes button.

The Changes dialog box appears.

5. Review the changes and clickOK when you are finished.

The Changes dialog box closes.

About Risk Assessment Recommendation Records and the SIL Analysis


About Risk Assessment Recommendation Recordsand the SIL AnalysisRisk Assessment Recommendation Recordsstore recommendations for an action that youshould be taken on the item that is represented by the record to which the Risk AssessmentRecommendation record is linked. In SIS Management, you can link Risk Assessment Recom-mendation records to records in the following families:



l SIS Proof Test

l SIS Proof Test Template

You canmanage Risk Assessment Recommendation records for individual recordswithin SISManagement via the Recommendations dialog box. Additionally, via RecommendationMan-agement, you canmange Risk Assessment Recommendation records for:

l One SIL Analysis

l ALL SIL Analyses

The Risk Assessment Recommendation datasheet contains two tabs:

l General Information: Contains fields that you can use to describe the recommendation,assign the recommendation to aMeridiumAPMuser, and specify due dates for the recom-mendation.

l Alert: Contains fields that you can use to schedule alerts to be sent to specified recipientswhen a recommendation or reevaluation is due.

After you link a Risk Assessment Recommendation record to an individual record, the RiskAssessment record is part of the SIL Analysis.

Accessing the Recommendations Dialog Box


Accessing the Recommendations Dialog BoxTheRecommendations dialog box lets youmanage Risk Assessment Recommendationrecords that are linked to individual recordswithin the SIL Analysis. Using the Recom-mendations dialog box, you can:

l View the Risk Assessment Recommendation records that are currently linked to a record.

l Create new Risk Assessment Recommendation records and link them to a record.

l Link existing Risk Assessment Recommendation records to a record.

l Remove Risk Assessment Recommendation records from the analysis.

The following instructions assume that you are viewing one of the following pageswithin SIS Man-agement and that the Recommendations link is enabled on a taskmenu on that page:

l Instrumented Functions (IFs)

l Proof Tests

l Proof Test Templates


Note: The Recommendations link should not be confused with the All Recommendationslink, which appears on the Navigationmenu.

To access the Recommendations dialog box:

l On the appropriate taskmenu, click the Recommendations link.

The Recommendations dialog box appears.

Accessing the Recommendations Dialog Box


Aspects of the Recommendations Dialog Box


Aspects of the Recommendations Dialog BoxTheRecommendations dialog box displays a list of Risk Assessment Recommendation recordsthat are linked to the record that is currently selected. Each row in the list represents one RiskAssessment Recommendation records. For each Risk Assessment Recommendation recordthat appears in the list, the following information is displayed:

l Recommendation ID: The ID for the recommendation as it appears in the Recom-mendation ID field in the Risk Assessment Recommendation record.

l Recommendation Headline: The description of the recommendation as it appears in theRecommendation Headline field in the Risk Assessment Recommendation record.

Below the list, the following buttons appear:

l Add new Recommendation: Displays a new Risk Assessment Recommendation recordin a new window, where you can create a new Risk Assessment Recommendation record.After you save the new record, it will appear in the list on the Recommendations dialogbox.

l Add Existing Recommendations: Displays the Find Items window, where you cansearch for an existing Risk Assessment Recommendation record to link to the selectedrecord.

l Delete Recommendations: Displays a confirmationmessage, and then removes the RiskAssessment Recommendation record from the SIL Analysis. This link is enabled only if aRisk Assessment Recommendation record appears in the list.

l Close: Closes the Recommendations dialog box, revealing the page fromwhich it wasaccessed.

Creating New Risk Assessment Recommendation Records


Creating New Risk Assessment RecommendationRecordsThe following instructions provide details on creating a new Risk Assessment Recommendationrecord via the Recommendations dialog box. These instructions assume that you are familiarwith the fields in the Risk Assessment Recommendation family.

To create a new Risk Assessment Recommendation record:

1. Access the Recommendations dialog box.

2. Below the grid, click the Add New Recommendation button.

A new Risk Assessment Recommendation record appears in a new window.

Creating New Risk Assessment Recommendation Records


3. On theGeneral Information tab, in the Target Completion Date box, type or select thedate that corresponds to the date on which the recommended task should be completed.This field is required.

4. On theGeneral Informationtab, provide values in the remaining fields as desired.

5. If desired, on the Alert tab, provide values in the fields to schedule an alert to be sent to theassignee when the recommendation is due.

Note: On the Alert tab, you can also schedule an alert to be sent to a list of recipientswhen the recommendation is due for reevaluation.

5. ClickOK.

The selected record appears in the list on the Recommendations dialog box and is linkedto the record that is currently selected on the page fromwhich you accessed the Recom-mendations dialog box.

Adding Existing Risk Assessment Recommendation Records to the SIL Analysis


Adding Existing Risk Assessment RecommendationRecords to the SIL AnalysisThe following instructions provide details on searching for an existing Risk Assessment Recom-mendation record to add to the SIL Analysis. When you add an existing Risk Assessment Recom-mendation record to the SIL Analysis, you are linking the Risk Assessment Recommendationrecord to an individual record within the SIL Analysis.

To add an existing Risk Assessment Recommendation record to the SIL Analysis:


2. Below the grid, click the Add Existing Recommendations button.


3. If desired, in the Look For text box, provide search criteria, and then click the Find Now but-ton.


4. In the search results list, select the desired record, and click the Open button.

Adding Existing Risk Assessment Recommendation Records to the SIL Analysis


The selected record appears in the list on the Recommendations dialog box and is linkedto the record that is currently selected on the page fromwhich you accessed the Recom-mendations dialog box.

Removing Risk Assessment Recommendation Records from the SIL Analysis


Removing Risk Assessment Recommendation Recordsfrom the SIL AnalysisWhen you remove a Risk Assessment Recommendation record from the SIL Analysis, you aredeleting the link between the Risk Assessment Recommendation record and the record to whichit is linked that belongs to the SIL Analysis. After you delete this link, the Risk Assessment Recom-mendation record is no longer part of the SIL Analysis.

To remove a Risk Assessment Recommendation record from the SIL Analysis:


2. In the grid, select the row containing the Risk Assessment Recommendation record thatyou want to remove from the SIL Analysis.

3. Click the Delete Recommendations button.

A confirmationmessage appears, asking if you really want to remove the link between theRisk Assessment Recommendation record and the record to which it is linked.


The selected Risk Assessment Recommendation record is removed from the Recom-mendations list and the SIL Analysis.

Using the Status Field in Recommendations


Using the Status Field in RecommendationsYou can use the values in the Status list in a Risk Assessment Recommendation record to facil-itate a workflow to track the progress of the recommendation.

The Status list contains the following values:

l Approved: You can use this status to indicate that the recommended action has beenapproved and can be assigned to someone to implement in your facility.

l Created: This status indicates that the Risk Assessment Recommendation record and theassociated recommendation are new. This is the default state.

l Pending Review: You can use this status to indicate that the recommended action isassigned to someone so that they can review it and obtain approval to implement the sug-gested action.

l Reviewed: You can use this status to indicate that the recommended action has beenreviewed and is waiting for approval.

l Rejected: You can use this status to indicate that the recommended action has been notbeen approved.

l Cancelled: You can use this status to indicate that the previously approved or reviewedaction will no longer be implemented.

l Superseded: You can use this status to indicate that the previously approved or reviewedaction will no longer be implemented because a different action supersedes it.

Depending on the value that exists in the Status field, you will need to assign the Risk Assess-ment Recommendation to an analysis teammember or the individual within your organizationwho is responsible for the current task associated with that recommendation. Additionally, whenthe Status field contains a certain value, in order to change that value, youmust be logged in asthe user to whom the record is assigned based on the current value in the Status field. Forexample, only the person whose name appears in the Reviewer Name field can change the valuein the Status field toReviewed.

The following diagram illustrates the workflow that you can use when working with the Statusfield to track the progress of a given recommendation. The boxes represent a Status value thatappears in the Status field, and the arrows represent actions taken by the current assignee.

Using the Status Field in Recommendations


About Scheduling Risk Assessment Recommendation Alerts


About Scheduling Risk Assessment RecommendationAlertsThe Alerts tab on the Risk Assessment Recommendation datasheet contains fields that you canuse to schedule an email message to be sent to aMeridiumAPMuser (i.e., a user who has aHumanResource record in theMeridiumAPMdatabase). You can schedule alerts to be sentwhen:

l A recommendation is due.

l A recommendation is due for reevaluation.

When you save a Risk Assessment Recommendation record that is in the Approved or In Pro-gress state and whose alert schedule has been defined on the Alerts tab, the following items areautomatically created in theMeridiumAPMdatabase:

l One Alert record that is linked to the Risk Assessment Recommendation record.

l One Scheduled Item in theMeridiumAPMScheduleManager.

After these items exist, the email message will be sent to the specified recipients according to theschedule that is defined in the Risk Assessment Recommendation record.

Scheduling Alert to Notify an AssigneeWhen a Recommendation is Due


Scheduling Alert to Notify an Assignee When a Recom-mendation is DueVia the Alert tab on the Risk Assessment Recommendation datasheet, you can schedule an alertto be sent to an email addresswhen a recommendation is due or when it is due for reevaluation.The following instructions provide details on using the fields on the Alert tab on the Risk Assess-ment Recommendation datasheet to schedule an alert to be sent to a recipient when a recom-mendation is due.

These instructions assume that you are familiar with adding Risk Assessment Recommendationrecords to an SIL Analysis.

To schedule an Alert to notify an assignee when a recommendation is due:

1. Open the Risk Assessment Recommendation record for which you want to configurealerts.

2. Click the Alert tab.

The Alert tab appears.

3. If desired, select the Alert Assignee When Due? check box, and then click in a differentfield.

The following fields are enabled and required:

l Days Before Due Date to be Notified

l Frequency of Alert After Due Date

4. In the Days Before Due Date to be Notified field, type a numeric value that represents thenumber of days prior to the due date that the assignee should be notified.

5. In the Frequency of Alert After Due Date list, select the value that represents the fre-quency bywhich an assignee should be notified after the due date has passed.

6. In the Implementation Alert Text field, type themessage that you want to appear in thealert email message that is sent to the assignee.

Note: These instructions assume that you have specified aMeridiumAPMuser as theassignee on theGeneral Information tab and that a valid email address stored in thatuser's HumanResource record.

7. At the bottom of the Risk Assessment Recommendation datasheet, clickOK.


Scheduling an Alert to Notify Assignees When a Recommendation is Due for Reevaluation


Scheduling an Alert to Notify Assignees When aRecommendation is Due for ReevaluationVia the Alert tab on the Risk Assessment Recommendation datasheet, you can schedule an alertto be sent to an email addresswhen a recommendation is due or when it is due for reevaluation.The following instructions provide details on using the fields on the Alert tab on the Risk Assess-ment Recommendation datasheet to schedule an alert to be sent to a recipient when a recom-mendation is due for reevaluation.

To schedule an alert to notify assignees when a recommendation is due for reevaluation:

1. Open the Risk Assessment Recommendation record for which you want to configurealerts.

2. Click the Alert tab.

The Alert tab appears.

3. If desired, select the Reevaluate? check box, and then click in a different field.

The following fields are enabled and required:

l Reevaluation Date

l Reevaluation Alert Body Text

4. In the Reevaluation Date box, type or select the date on which the reevaluation is due.

5. In the Reevaluation Notification List, select the check box to the left of theMeridiumAPMuser who will receive the reevaluation alert.

Note: A valid email addressmust be stored in this user's HumanResource record toreceive a reevaluation alert.

6. In the Reevaluation Alert body Text field, type themessage that you want to appear in thealert email message that is sent to the assignee.

Viewing the List of Risk Assessment Recommendation Records for the Current SIL Analysis


Viewing the List of Risk Assessment RecommendationRecords for the Current SIL AnalysisThe following instructions provide details on viewing the list of Risk Assessment Recom-mendation records that are associated with the current SIL Analysis.

To view the list of all Risk Assessment Recommendation records the current SIL Analysis:

1. Open the desired SIL Analysis record.

2. On the Navigationmenu, click the All Recommendations link.

The Recommendation Management page appears, displaying the results of the SIL Ana-lysis Recommendationsquery, which returns a list of all the Risk Assessment Recom-mendation records that are associated with the SIL Analysis with which you are currentlyworking.

Viewing the List of Risk Assessment Recommendation Records for All SIL Analyses


Viewing the List of Risk Assessment RecommendationRecords for All SIL AnalysesThe following instructions provide details on viewing the list of Risk Assessment Recom-mendation records that are associated with ALL SIL Analyses in theMeridiumAPMdatabase.

To view the list of Risk Assessment Recommendation records all SIL Analyses:

l On the SIS Management Start Page, click theManage Recommendations link.

The Recommendation Management page appears, displaying the results of the All SILAnalysesRecommendations query, which returns the list of Risk Assessment Recom-mendation records that are currently associated with an SIL Analysis.

About Inspection Tasks Records


About Inspection Tasks RecordsInspection Task records store details on when a task should be performed on the item rep-resented by the record to which the Inspection Task record is linked, including the due date forthe task. For example, you can create an Inspection Task to perform a Proof Test.

In SIS Management, you can link Inspection Tasks records to records in the following families:



You canmanage Inspection Task records for individual recordswithin SIS Management via theView option on theTasks submenu. Additionally, you can view a list of the Inspection Taskrecords for ALL SIL Analysis via TaskManagement. After you link an Inspection Task record toan individual record, the Inspection Task record is part of the SIL Analysis.

Creating Inspection Task Records


Creating Inspection Task RecordsWhen you create an Inspection Task record, you are linking that record to the currently selectedrecord on the page fromwhich you accessed the Inspection Task record. Doing so automaticallyadds the Inspection Task record to the SIL Analysis. These instructions assume that you are famil-iar with the fields in the Inspection Task family.

To create an Inspection Task record:


2. Access either the Instrumented Functions (IFs) page or the Safety Instrumented Sys-tems page, depending on the family to which you want to link the Inspection Task record.

3. In the grid, select the row containing the record to which you want to link the InspectionTask record.

4. On the Assessment Tasks menu, click the Tasks link.

A submenu appears with options that you can use to create a new Inspection Task recordor view a list of existing Inspection Task records that are already linked to the currentlyselected record.

5. On the submenu, click the Create link.

A new Inspection Task record appears in the Task Builder.

Creating Inspection Task Records


Note: The Next button is disabled on this screen.

6. Provide values in the fields as desired. Note that the Task ID field is required.



Viewing the List of Inspection Task Records that are Linked to an Individual Record


Viewing the List of Inspection Task Records that areLinked to an Individual RecordThe following instructions provide details on viewing the list of all the Inspection Task records thatare linked to an individual record.

To view the list of Inspection Task records that are linked to an individual record:


2. Access either the Instrumented Functions (IFs) page or the Safety Instrumented Sys-tems page, where you can locate the record whose Inspection Task records you want toview.

3. In the grid, select the row containing the record to which you want to link the InspectionTask record.

4. On the Assessment Tasks menu, click the Tasks link.

A submenu appears with options that you can use to create a new Inspection Task recordor view a list of existing Inspection Task records that are already linked to the currentlyselected record.


The Task List page appears, displaying the list of existing Task records that are linked tothe currently selected record. At this point you canmodify the records as desired by clickingthe hyperlinked Task ID in theTask ID cell.

Viewing the List of Inspection Task Records for All SIL Analyses


Viewing the List of Inspection Task Records for All SILAnalysesThe following instructions provide details on viewing the list of Inspection Task records that areassociated with ALL SIL Analyses.

To view the list of Inspection Task Records for all SIL Analyses:

l On the SIS Management Start Page, click theManage Tasks link.

TheTasks List page appears, displaying the results of theAll SIL Analyses Tasksquery,which returns a list of Task records that are associated with all existing SIL Analyses. Atthis point you canmodify the Task records by clicking the hyperlinked Task ID in theTaskID cell.

Associated Pages


Associated PagesThe Associated Pagesmenu appears throughout SIS Management and displays AssociatedPages that have been configured for the families that participate in the SIS Management datamodel. The baselineMeridiumAPMdatabase does not contain Associated Pages for SIS Man-agement families by default.

About the SIS Management Catalog Folder Structure


About the SIS Management Catalog Folder StructureThe SIS Management Catalog folders contain queries, graphs, and reports that appear through-out SIS Management and display information contained in the records that make up an SIL Ana-lysis. The Catalog folder \\Public\Meridium\Modules\SIS Management contains the followingsubfolders:

l Dashboards: Contains the Asset Safety dashboard.

l LOPA: Contains the following subfolders:n Queries: Contains queries that are used by a Layer of Protection Analysis.

n Reports: Contains theLOPA Reportand one subfolder, Subreports, which contains thesupporting reports for the LOPA Report.

l PIF: Contains the following subfolders:n Queries: Contains queries that support the reports in the Reports folder.

n Reports:Contains the reports that are available when you are viewing Instrumented Func-tion records on theInstrumented Functions (IFs) page.

l Proof Test Templates: Contains the following subfolders:n Queries: Contains the Proof Test Template Query, which supports the Proof Test Tem-

plate Report, which is stored in the Reports folder.

n Reports: Contains the Proof Test Template Report.

l Proof Tests: Contains the following subfolders:n Queries: Contains queries that support the Proof Test Report, which is stored in

theReports folder.

n Reports:Contains the Proof Test Report.

l Protective Instrument Loop: Contains the following subfolders:n Queries: Contains queries that support the Protective Instrument Loop Report, which is

stored in the Reports folder.

n Reports: Contains theProtective Instrument Loop Report and one subfolder, Subreports,which contains a report that supports the Protective Instrument Loop Report.

l Queries: Contains queries that appear on various pages throughout SIS Managementand are used to display search results for records in an individual family and the followingsubfolder:

n Dashboard Queries: Contains queries that are used to display results on the AssetSafety dashboard.

l SIL: Contains the following subfolders:n Graphs: Contains graphs that are available when you are viewing an SIL Analysis record

on the SIL Analysis Definition page.

n Queries: Contains queries that support baseline SIL Analysis graphs.

n Reports: Contains the SIL Analysis Report, which is available when you are viewing anSIL Analysis record on the SIL Analysis Definition page.

l SIS Trip Report: Contains the following subfolders:

About the SIS Management Catalog Folder Structure


n Queries: Contains queries that support the SIS Trip Report, which is stored in theReports folder.

n Reports: Contains the SIS Trip Report, which is available when you are viewing anSIS Trip Report record on theSIS Trip Report page.

Dashboards Folder


Dashboards FolderThe dashboard that is listed in the following table is stored in the Catalog location \\Public\Meridi-um\Modules\SIS Management\Dashboards. In this table, the value listed in the Dashboardcolumn refers to the dashboard name. The baseline caption is the same as the dashboard name.

Dashboard Behavior and Usage

Asset Safety Dash-board

Displays the Asset Safety dashboard on the Dashboard page.

LOPA Folder


LOPA FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\LOPA contains the followingsubfolders:

l Queries: The following table displays the queries that exist in theQueries subfolder.

Query Name Behavior and Usage

LOPA Con-sequenceModifiersSearch

A search that displays a prompt for the Entity Key for a LOPA recordand then displays a list of ConsequenceModifier records that are linkedto the specified LOPA record. The results of this query appear bydefault on the Consequence Modifiers page.

LOPA ILP Search A search that displays a prompt for the Entity Key for a LOPA recordand then displays a list of Independent Layer of Protection records thatare linked to the specified LOPA record. The results of this queryappear by default in the Independent Protective Layers pane on theLOPA Definition page.

LOPA_Analysis_Search

A search that displays a prompt for the Entity for a LOPA record andthen displays the LOPA records that are linked to a given InstrumentedFunction record. The result of this query appears by default in the Asso-ciated Risk Assessments pane on the Instrumented Functions (IFs)page.

l Reports: The following table displays the items that exist in the Reports subfolder.

ItemName Behavior and Usage

LOPA Report Displays a prompt for the Entity Key for a LOPA record and then dis-plays in the Report Viewer information about the Layer of ProtectionAnalysis that exists in the LOPA record and records that are linked tothat LOPA record.

Subreports A subfolder that contains the reports with the following names:

o LOPA Consequence Modifiers Report: Supports the LOPAReport.

o LOPA ILP Report: Supports the LOPA Report.

PIF Folder


PIF FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\PIF contains the followingsubfolders:

l Queries: The following table displays the queries that exist in the Queries subfolder.


PIF Query Displays a prompt for the Entity Key for an Instrumented Functionrecord and then displays information that is stored in the fields in thatInstrumented Function record. The results of this query appear bydefault on the Instrumented Functions (IFs) page.

PIF RiskMatrix Res-ult Query

Displays a prompt for the Entity Key for an Instrumented Functionrecord and then displays the risk rank values that are linked to thatInstrumented Function record.

l Reports: The following table displays the reports that exist in the Reports subfolder.

Report Name Behavior and Usage

If Report Displays a prompt for the Entity Key for an Instrumented Functionrecord and then displays in the Report Viewer information about theInstrumented Function that exists in the Instrumented Function recordand records that are linked to that Instrumented Function record.

If RiskMatrix ResultReport

Supports the IF Report.

Proof Test Template Folder


Proof Test Template FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\Proof Test Template con-tains the following subfolders:

l Queries: The following table displays the query that exists in theQueries subfolder.


Proof Test Tem-plate Query

Displays a prompt for the Entity Key for an SIS Proof Test Templaterecord and then displays information that is store in that SIS Proof TestTemplate record. The results of this query appear by default on theProof Test Templates page.

l Reports: The following table displays the report that exists in the Reports subfolder.


Proof Test Tem-plate Report

Displays a prompt for the Entity Key for an SIS Proof Test Templaterecord and then displays in the Report Viewer summary informationthat is stored in that SIS Proof Test Template record.

Proof Tests Folder


Proof Tests FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\Proof Tests contains the fol-lowing subfolders:



SIS Proof TestQuery

Displays a prompt for the Entity Key for an SIS Proof Test record andthen displays information that is store in that SIS Proof Test record.The results of this query appear by default on the Proof Tests page.

SIS Proof TestQuery UNION

Supports the SIS Proof Test Query.



Proof Test Report Displays a prompt for the Entity Key for an SIS Proof Test record andthen displays in the Report Viewer summary information that is storedin that SIS Proof Test record.

Protective Instrument Loop Folder


Protective Instrument Loop FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\Protective Instrument Loopcontains the following subfolders:



Protective InstrumentLoopQuery

Displays a prompt for the Entity Key for a Protective InstrumentLoop record and then displays information that is stored in thatProtective Instrument Loop record. This query supports the Pro-tective Instrument Loop Report that is stored in the Reports folder.

Protective InstrumentLoop Sensor SystemSubquery

Displays a prompt for the Entity Key for a Protective InstrumentLoop record and then displays information that is stored in the Pro-tective Instrument Loop System records that are linked to the Pro-tective Instrument Loop record. This query supports the ProtectiveInstrument Loop Report that is stored in the Reports folder.


ItemName Behavior and Usage

Protective Instru-ment Loop Report

Displays a prompt for the Entity Key for a Protective Instrument Looprecord and then displays in the Report Viewer summary informationthat is stored in that Protective Instrument Loop record.

Subreports A subfolder that contains the PIL Sensor SystemReport, which sup-ports the Protective Instrument Loop Report.

About TheQueries Folder


About The Queries FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\Queries contains:

l Queries that support various featureswith the SIS Management module, including thosethat support the reports that make up the SRS Report.

l A subfolder, Dashboard Queries, that contains queries that are used to display content onthe Asset Safety dashboard.

To simplify the documentation, the items that are stored in this folder are split up into the followinggroups:

l Queries that support modules-specific pages.

l Queries that support the SRS Report.

l Dashboard Queries folder.

Queries That Support Module-Specific Pages


Queries That Support Module-Specific PagesThe following queries are stored in the Catalog folder \\Public\Meridium\Modules\SIS Man-agement\Queries and support module-specific pageswithin SIS Management.

Query Name Behavior and Usage Notes

Add_SIS_Trip_Report_Detail_Search

A search that displays prompts for theEntity Key for a Safety Instrumented Sys-tem record and an SIS Trip Report recordand then displays information that isstored in both records.

None

ALL SIL AnalysesRecom-mendations

Displays a list of all the Risk AssessmentRecommendation records that are linkedto any SIL Analysis record.

None

ALL SIL Analyses Tasks Displays the following prompts and thendisplays a list of all the Task records thatmeet the specified criteria.

n Asset ID: The IDs for the Equip-ment and Functional Location fam-ilies in theMeridiumAPMdatabase.

n Task Family: The names of theTask families that exist in theMeridiumAPMdatabase.

The results of thisquery appear bydefault on theTask List pagewhen you accessit from an SILAnalysis in SISManagementand display onlyInspection Taskrecords that areassociated withan SIL Analysis.

Export_SIL_Analysis_Search Displays a prompt for the record state ofan SIL Analysis, and then displays a list ofSIL Analysis records that meet the spe-cified criteria. The State prompt containsa list of record states that are configuredfor the SIL Analysis family. By default, thislist contains the following baseline values:

n All

n Active

n Complete

n Pending Approval

n Planning

n Review

This query isused by the SISManagementExport Builder.



QueryName Behavior and Usage Notes

Final_Element_Reference_Data_Search

A search that displays a prompt and thendisplays a list of Final Element recordswhose Is Reference Data field value is setto True.

The results of thisquery appear bydefault on theFinal ElementReference DataSearch page.

IF_Safety_Loop_Search A search that displays a prompt for therecord state of a Protective InstrumentLoop record, and then displays a list ofProtective Instrument Loop records thatare linked to a particular InstrumentedFunction record. The State prompt con-tains a list of record states that are con-figured for the Protective Instrument Loopfamily. By default, this list contains the fol-lowing baseline values:

n All

n Approval

n Design

n In Service

n Out of Service

n Pending Approval

The results of thisquery appear bydefault on theProtective LoopSearch pagewhen you searchfor protectiveinstrument loopsassociated withan instrumentedfunction.

Logic_Solver_Reference_Data_Search

A search that displays a prompt and thendisplays a list of Logic Solver recordswhose Is Reference Data field value is setto True.

The results of thisquery appear bydefault on theLogic SolverReference DataSearch page.




Safety_Loop_Search A search that displays a prompt for therecord state of a Protective InstrumentLoop record and then displays a list of Pro-tective Instrument Loop records that meetthe specified criteria. The State promptcontains a list of record states that are con-figured for the Protective Instrument Loopfamily. By default, the list contains the fol-lowing baseline values:

n All

n Approval

n Design

n In Service

n Out of Service

n Pending Approval

The results of thisquery appear bydefault on theProtective LoopSearch page.

Safety_Loop_Template_Search

A search that displays a prompt for therecord state of a Protective InstrumentLoop record, where the Is Template fieldvalue in that record is Yes, and then dis-plays a list of Protective Instrument Looprecords that are specified as templatesandmeet the specified criteria.

The results of thisquery appear bydefault on theProtective LoopTemplateSearch page.

Sensor_Reference_Data_Search

A search that displays a prompt and thendisplays a list of Logic Solver recordswhose Is Reference Data field value is setto True.

The results of thisquery appear bydefault on theSensor Refer-ence DataSearch page.

SIL Analysis Recom-mendations

Displays a prompt for the Entity Key for anSIL Analysis record and then displays alist of Risk Assessment Recommendationrecords that are linked to the specified SILAnalysis record.

None




SIL_Analysis_Search A search that displays the followingprompts and then displays a list of SILAnalysis records that meet the specifiedcriteria.

n State: The record states that havebeen configured fro the SIL Ana-lysis family. By default, this list con-tains the following values:

o Allo Activeo Completeo Pending Approvalo Planningo Review

n SIL Analysis Owner: The namesof the users whose names appearin the Owner field in a SIL Analysisrecord.

By default, thisquery appears onthe SIL AnalysisSearch page andis used by theSIS Man-agement ImportBuilder.

SIS Find ASMActions for IF Displays a prompt for the Entity Key for anInstrumented Function record and is usedto find ASMActions that were createdwhen the specified Instrumented Functionrecord was promoted to ASM.

None

SIS Find ASMRisk for IF Displays a prompt for the Entity Key for anInstrumented Function record and is usedto find ASMRisks that were created whenthe specified Instrumented Functionrecord was promoted to ASM.

None

SIS_Trip_Report_IF_Search A search that displays a prompt for theEntity Key for a Safety Instrumented Sys-tem record and then displays informationthat is stored in the SIS Trip Reportrecord that is linked to the specified SafetyInstrumented System record.

None




SIS_Trip_Report_Search A search that displays a prompt for therecord state of an SIS Trip Report recordand then displays a list of SIS Trip Reportrecords that meet the specified criteria.The State list contains a list of recordstates that are configured for the SIS TripReport family. By default, this list containsthe following baseline values:

n All

n Active

n Complete

n Pending Approval

n Review

The results of thisquery appear bydefault on theSIS Trip ReportSearch page.

Queries That Support The SRS Report


Queries That Support The SRS ReportThe following queries are stored in the Catalog folder \\Public\Meridium\Modules\SIS Man-agement\Queries and support the SRS Report and subreports stored in the \SIL\Reports folder.


SRS_Report_Query Displays a prompt for the Entity Key of the SIL Ana-lysis record to which all the records that make up anSIL Analysis are linked and then displays valuesstored in fields that are required in the followingrecords:

n Instrumented Function

n Safety Instrumented System

n SIL Analysis

This query supports themain SRS Report.

SIL_Analysis_Doc_Query Displays a prompt for the Entity Key of the SIL Ana-lysis record to which all the records that make up anSIL Analysis are linked and then displays all the Refer-ence Document records that are linked to that record.This query supports the subreport SIL_Doc_Report.

SRS_SubReport_Query Displays a prompt for the PIF ID for an InstrumentedFunction record and then displays values stored inrecords that make up a protective instrument loop.This query supports the subreport Loop_Report.

SRS_Sensor_Query Displays a prompt for the PIF ID for an InstrumentedFunction record and then displays values stored inrecords that make up a protective instrument loop.This query supports the subreport Loop_Report.

Final_Element_Query Displays a prompt for the PIF ID for an InstrumentedFunction record and then displays values stored inrecords that make up a protective instrument loop.This query supports the subreport Loop_Report.

Queries That Support The SRS Report


QueryName Behavior and Usage

IF_Common_Cause_Failures Displays a prompt for the PIF ID for an InstrumentedFunction record to which SIF CommonCause Failurerecords are linked and then displays the values storedin the following fields in the SIF CommonCause Fail-ure records that are linked to the specified Instru-mented Function record.

n CCF ID

n CCFDescription

n CCFMitigation

This query supports the subreportIF Subreport.

IF_Concurrent_Safe_State Displays a prompt for the PIF ID for the InstrumentedFunction record to which Instrumented Functionrecords are linked and then displays the values storedin the following fields in the Instrumented Functionrecord:

n Concurrent Safe State Hazard

n PIF Description

n Safe State Description

n PIF ID

This query supports the subreportIF Subreport.

Final_Element_Hazardous_Event_Comb

Displays a prompt for the PIF ID for the InstrumentedFunction record and then displays values stored inrecords that make up a protective instrument loop.This query supports the subreport Final_Element_Subreport.

Dashboard Queries Folder


Dashboard Queries FolderThe queries listed in the following table are stored in the Catalog location \\Public\Meridi-um\Modules\SIS Management\Queries\DashboardQueries. In this table, the values listed in theQuery column refer to the query names. The baseline query captions are the same as the querynames.

Query Behavior and Usage

Analysis States Used to return results that are displayed in the Hazards AnalysisSchedule section on the Asset Safety dashboard. In the baselinedatabase, this query is configured to return Hazards Analysisrecords by state.

Calibration Recom-mendations

Used to return results that are displayed in the CalibrationRecommendations section on the Asset Safety dashboard.

Calibration Recom-mendations - All

Used by the Calibration Recommendations source query to dis-play content on the Asset Safety dashboard.

Calibration Results - Fail Used by the Calibration Results for Graph source query to displaycontent on the Asset Safety dashboard.

Calibration Results -Pass as Found

Used by the Calibration Results for Graph source query to displaycontent on the Asset Safety dashboard.

Calibration Results -Pass as Left

Used by the Calibration Results for Graph source query to displaycontent on the Asset Safety dashboard.

Calibration Results All Used by the Calibration Results for Graph source query to displaycontent on the Asset Safety dashboard.

Calibration Results forGraph

Used to return results that are displayed in the CalibrationPass/Fail Results for Last 12 Months section on the AssetSafety dashboard.

Calibration Tasks Used to return results that are displayed in the Calibration Sched-ule section on the Asset Safety dashboard.

Calibration Tasks - All Used by the Calibration Tasks source query to display content onthe Asset Safety dashboard.

Filter Widget Used to return results that are displayed in the Content Filter sec-tion on the Asset Safety dashboard.

HAZOP Analyses Used by one or more source queries to the Asset Safety dash-board.

Last 5 Years Used by one or more source queries to the Asset Safety dash-board.




Overdue Hazards Ana-lysis

Used to return results that are displayed in the Hazards AnalysisSchedule section on the Asset Safety dashboard.

Overdue Proof TestTasks

Used to return results that are displayed in the Proof Test Sched-ule section on the Asset Safety dashboard.

Proof Tests States Used by one or more source queries to the Asset Safety dash-board.

Proof Tests States byState

Used by one or more source queries to the Asset Safety dash-board.

Proof Tests States forGraph


Proof Test States withFunctional Location


Protective InstrumentLoop States

Used by theQuantity of Protective Instrumented Loops by Statefor Graph source query to display content on the Asset Safetydashboard.

Proven In Use DeviceTypes

Used by the Proven In Use Devices by Type for Graph sourcequery to display content on the Asset Safety dashboard.

Proven In Use Devicesby Type

Used by the Proven In Use Devices by Type for Graph sourcequery to display content on the Asset Safety dashboard.

Proven In Use Devicesby Type for Graph

Used to return results that are displayed in the Proven in UseDevices by Type section on the Asset Safety dashboard.

Quantity of Hazards Ana-lysis


Quantity of ProtectiveInstrumented Loops


Quantity of ProtectiveInstrumented Loops byState


Quantity of ProtectiveInstrumented Loops byState for Graph

Used to return results that are displayed in the Quantity of Pro-tective Instrumented Loops section on the Asset Safety dash-board.

Quantity of SIF Trips Used to display results that are displayed in the Quantity of SIFTrips section on the Asset Safety dashboard.




Quantity of SIL Analysis Used by one or more source queries to the Asset Safety dash-board.

Quantity of SIL Analysisby State


SIF Spurious TripReports


SIF Trip Report Types Used by theQuantity of SIF Trips source query to display contenton the Asset Safety dashboard.

SIF Unsafe Trip Reports Used by one or more source queries to the Asset Safety dash-board.

SIL Analysis States Used by one or more source queries to the Asset Safety dash-board.

SIL Distribution Used by the SIL Distribution for Graph source query to display con-tent on the Asset Safety dashboard.

SIL Distribution forGraph

Used to return results that are displayed in the View SIL Dis-tribution section on the Asset Safety dashboard.

SIS Proof Test Pass Fail Used to return results that are displayed in the Proof TestsPass/Fail section on the Asset Safety dashboard.

SIS Proof Tests Failed Used by the SIS Proof Test Pass Fail source query to display con-tent on the Asset Safety dashboard.

SIS Proof Tests Passed Used by the SIS Proof Test Pass Fail source query to display con-tent on the Asset Safety dashboard.

What If Analyses Used by one or more source queries to the Asset Safety dash-board.

SIL Folder


SIL FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\SIL contains the following sub-folders:

l Graphs: The following table displays the graphs that exist in theGraphs subfolder.

GraphName Behavior and Usage Notes

SIL Ana-lysis RiskGraph

A bar chart that displays a summaryof the Risk Rank values that are asso-ciated with each Instrumented Func-tion record that is linked to thespecified SIL Analysis. When youopen this graph from the SIL Ana-lysis Definition page, the value forthe SIL Analysis that you are cur-rently viewing is passed in to theENTY_KEY prompt to return the res-ults for that analysis.

None

SIL Assign-ment Sum-maryGraph

A pie chart that shows a breakdownof the Selected SIL Level values inthe Instrumented Function recordsthat are linked the specified SIL Ana-lysis. This graph is based upon thequery SIL Assignment SummaryQuery, which is stored in the folder\\Public\Meridium\Modules\SIS Man-agement\SIL\Queries and returns acount for each Selected SIL Levelvalue. For example, if five Instru-mented Function records that arelinked to the SIL Analysis record con-tain the value 2 in the Selected SILLevel field, the count for level 2 wouldbe 5. Each count is displayed as apercentage in the SIL AssignmentSummaryGraph.

When you open this graph from the SILAnalysis Definition page, the value forthe SIL Analysis that you are currentlyviewing is passed in to the ENTY_KEYprompt to return the results for that ana-lysis.



SIL AnalysisMit-igated RiskQuery

Displays risk assessment details that are associated with all SIL Ana-lysis records.

SIL Folder


QueryName Behavior and Usage

SIL Analysis Query Displays a prompt for the Entity Key for an SIL Analysis record andthen displays information that is stored in the specified SIL Analysisrecord.

SIL Analysis RiskQuery

Displays a prompt for the Entity Key for an SIL Analysis and then dis-plays risk rank details for the Instrumented Functions that are linked tothe specified SIL Analysis record.

SIL AssignmentSummaryQuery

Supports the graph SIL Assignment SummaryGraph and returns acount for each Selected SIL Level value in the Instrumented Functionrecords that are linked to the specified SIL Analysis.



SIL AnalysisReport

Displays a prompt for the Entity Key for an SIL Analysis record andthen displays in the Report Viewer summary information for the spe-cified SIL Analysis record.

SRS Report Displays a prompt for the Entity Key for the SIL Analysis record towhich all the records that make up an SIL Analysis are linked and thendisplays in the Report Viewer the Safety Requirement Specificationsreport for the specified SIL Analysis. While you can run the report fromthe Catalog andmanually enter the Entity Key for the SIL Analysisrecord, we recommend that you access the report only fromwithin theSIS Management module. You should not modify the SRS Report orany of the supporting queries and subreports.

Subreports The SubReports folder stores the following reports that support theSRS Report, and are supported by queries stored in the Queriesfolder:

n Final_Element_Subreport

n IF Subreport

n Loop_Report

n SIL_Doc_Report

SIS Trip Report Folder


SIS Trip Report FolderTheCatalog folder \\Public\Meridium\Modules\SIS Management\SIS Trip Report contains thefollowing subfolders:

l Queries: The following table displays the queries that exist in theQueriessubfolder.


SIS Trip ReportRecommendations

Displays a prompt for the Entity Key for an SIS Trip Report record andthen displays the list of Risk Assessment Recommendation recordsthat are linked to the specified SIS Trip Report record.

SIS Trip ReportsQuery

Displays a prompt for the Entity Key for an SIS Trip Report record andthen displays the list of SIS Trip Report records and information that isstored in each record.



SIS Trip Report Displays a prompt for the Entity Key for an SIS Trip Report record andthen displays in the Report Viewer summary information that is asso-ciated with the specified SIS Trip Report record and the records thatare linked to that SIS Trip Report record.

ConsequenceModifier


Consequence ModifierConsequenceModifier records store information about an event or action that can increase theprobability that a riskmay occur if the risk is not mitigated and proceeds into an undesirable event.The following table provides an alphabetical list and description of the fields that exist for the Con-sequenceModifier family and appear on the ConsequenceModifier datasheet, unless otherwisespecified. The information in the table reflects the baseline state and behavior of these fields. Thislist is not comprehensive.

Field Cap-tion Data Type Description Behavior and Usage

ConsequenceModifier ID

Character The ID for the con-sequencemodifier.

Youmust type your own valuemanually. This value appears inthe Consequence Modifier IDcell on the Consequence Modi-fiers page and is used to dis-tinguish the ConsequenceModifier record from other Con-sequenceModifier records. Thisfield is required.

Description Character The description of the con-sequencemodifier.

You can type your own valuemanually.

Type Character The type of consequencemodifier.

You can type your own valuemanually.

Independent Layer of Protection


Independent Layer of ProtectionIndependent Layer of Protection records store details about a device, system, or action thatexists to prevent a risk and is independent of the event that initiates the scenario. The followingtable provides an alphabetical list and description of the fields that exist for the Independent Layerof Protection family and appear on the Independent Layer of Protection datasheet, unless oth-erwise specified. The information in the table reflects the baseline state and behavior of thesefields.

Field Cap-tion

DataType Description Behavior and Usage

Description Character A description of the inde-pendent layer of pro-tection.

On the datasheet, this field appears asa text box labeled Description. Whenyou select a value in the Type list, thisfield is populated automatically with thevalue stored in the Description field inthe corresponding IPL Type record.

EquipmentID

Character The ID for the Equipmentrecord that is linked to theIndependent Layer of Pro-tection record through theSafety Analysis HasEquipment Relationshipfamily.

On the datasheet, this field is disabledand contains a button, which youcan click to search for the Equipmentrecord that you want to link to theIndependent Layer of Protectionrecord.

EquipmentEntity Key

Number The Entity Key for theEquipment record that islinked to the IndependentLayer of Protectionrecord.

TheMeridiumAPM system uses thisvalue to populate the Equipment IDfield in the Independent Layer of Pro-tection record. This field does notappear on the Independent Layer ofProtection datasheet by default.

FunctionalLocation

Character The ID for the FunctionalLocation record that islinked to the IndependentLayer of Protection recordthrough the Has Func-tional Location Rela-tionship family.

On the datasheet, this field is disabledand contains a button, which youcan click to search for the FunctionalLocation record that you want to link tothe Independent Layer of Protectionrecord.

FunctionalLocationEntity Key

Number The Entity Key for theFunctional Locationrecord that is linked to theIndependent Layer of Pro-tection record.

TheMeridiumAPM system uses thisvalue to populate the Functional Loca-tion field. This field does not appear onthe Independent Layer of Protectiondatasheet by default.



Field Cap-tion


IPL ID Character The ID for the inde-pendent layer of pro-tection (IPL).

On the datasheet, this field appears asa text box labeled IPL ID, in which youcan enter your own value. This valueappears in the Independent ProtectiveLayers section on the LOPA Definitionpage and is used to distinguish theIndependent Layer of Protection recordfrom the other Independent Layer ofProtection records. This field isrequired.

PFD Number A number representingthe probability that theindependent layer of pro-tection will fail to mitigatethe risk.

On the datasheet, this field appears asa text box labeled PFD. Dependingupon the IPL type that you select in theType list, the PFD field will be:

l Disabled and populated auto-matically with a default value.

-or-

l Required. If the PFD field isrequired. A rule is applied to thisfield that checks the value youenter against a range that isdefined by the selected IPL type.

If you do not select a value in theTypelist and type a custom value in the Typetext box, the PFD field is required, buttheMeridiumAPM systemwill beunable to prevent you from entering aninvalid PFD value.



Field Cap-tion


SequenceNumber

Number A number indicating theorder in which theIndependent Layer of Pro-tection recordmustappear in the grid in rela-tion to the other Independ-ent Layers of Protectionrecords.

On the datasheet, this field appears asa text box labeled Sequence Numberand is populated automatically with anumber relative to the existingIndependent Layer of Protectionrecords that are already linked to thesame LOPA record. For example, if twoIndependent Layer of Protectionrecords are already linked to a LOPArecord, when you create a third Layerof Protection Analysis record and it linkit to the same LOPA record, theSequence Number field will be pop-ulated automatically with the value3.You canmodify this value, if desired.

Type Character The type of independentlayer of protection.

On the datasheet, this field appears asa list labeled Type and contains the IPLType records that exist in the database.The IPL Type record that you select inthis list is used to determine the PFDvalue that is associated with the inde-pendent layer of protection representedby the Independent Layer of Protectionrecord. Alternatively, you can enter acustom value in the Type field.

Instrumented Function


Instrumented FunctionInstrumented Function records store details about a specific function of an SIS. The followingtable provides an alphabetical list and description of the fields that exist for the Instrumented Func-tion family. The information in this table reflects the baseline state and behavior of these fields.This list is not comprehensive.

Field Cap-tion

DataType Description Behavior and Usage Datasheet/Tab

AbnormalState

Character A short descrip-tion of the spe-cific abnormalstate of the oper-ation.

On the datasheet, thisfield appears as a listlabeled AbnormalStates and contains thefollowing values:

l Start-Up

l Shutdown

l Bypass

l Maintenance

l Emergency

l Other

This field is enabled andrequired only ifABNORMAL is selectedin the Operation Modeslist. Otherwise, this fieldis disabled.

Safety Require-ment Specificationdatasheet

ConcurrentSafe StateHazard

Text A description ofthe hazardousevent that couldoccur if the safestate associatedwith the instru-mented functionoccurs sim-ultaneously withthe safe state ofa different instru-mented function.

In the UI, this field is dis-played without a fieldcaption, and the value isset by default. You canremove this text andenter your own value.This field contains abutton, which you canclick to access the TextEditor.

Potential Con-current Safe StateHazard section ontheConcurrentSafe Statestab onthe <Record ID>(InstrumentedFunction) window



Field Cap-tion


ConcurrentSafe StateHazard?

Logical A logical fieldthat stores thevalue True orFalse and indic-ates whether thesafe state asso-ciated with theinstrumentedfunction cancause a haz-ardous event if itoccurs con-currently with asafe state of a dif-ferent instru-mented function.By default, thisfield contains thevalue False.

In the UI, this fieldappears as a check boxlabeled Hazard for Con-current Safe States?,which you can select toindicate that the safestate for the instru-mented function canlead to a hazardousevent if that safe stateoccurs simultaneouslywith the safe state of adifferent instrumentedfunction.

Concurrent SafeStates tab on the<Record ID>(InstrumentedFunction) window



Field Cap-tion


ConsequenceDescription

Text A description ofthe risk that isassociated withthe hazardousevent that existsin the HazardousEvent field.

On the InstrumentedFunction datasheet, thisfield appears as a textbox labeled Con-sequence Descriptionand contains a but-ton, which you can clickto access the TextEditor.

If the value in the SILAssessment Methodfield is PHA - Internal,after you select a RiskAssessment recordfrom aHazards Ana-lysis, this field is pop-ulated automaticallywith the value in theConsequence Descrip-tion field in the HazardsAnalysis Consequencerecord that is linked tothe Risk Assessmentrecord you selected.

Instrumented Func-tion datasheet

Demand Rate(Source)

Character The demand rate(i.e., Lowdemand or Highdemand).

On the datasheet, thisfield contains the textLow Demand bydefault. You canremove this text andenter your own values.




Field Cap-tion


Equipment ID Character The ID of theEquipmentrecord whoseEntity ID isstored in theEquipment Keyfield.

On the datasheet, thisfield is disabled and con-tains a button, whichyou can click to searchfor the desired Equip-ment record. After youselect an Equipmentrecord, a link is createdbetween the selectedEquipment record andthe Instrumented Func-tion record. In addition,the Equipment ID willappear automatically inthe Equipment ID field.


EquipmentKey

Number The Entity Key ofthe Equipmentrecord that islinked to theInstrumentedFunction record.

TheMeridiumAPM sys-tem uses this value topopulate the EquipmentID field that appears onthe Instrumented Func-tion datasheet.

None

Failure RateUOM

Character The unit of meas-ure that is asso-ciated with thevalue in theRequired Prob-ability of Failurefield.

On the datasheet, thisfield appears as a listlabeled Failure RateUOM and contains thefollowing values:

l PFD Avg.

l PFH

When the value in theSILMode field is HighDemandorContinuous,this value is disabledand populated auto-matically withPFH.When the value in theSILMode field isLowDemand, this value isdisabled and populatedautomatically withPFH.




Field Cap-tion


Frequency ofInitiatingEvent (Per yr)

Number The number oftimes per yearthat the initiatingevent occurs.

On the datasheet, thisfield appears as a textbox labeled Frequencyof Initiating Event (peryr), in which you canenter your own value.

If the value in the SILAssessment Methodfield is PHA - Internal,after you select a RiskAssessment recordfrom aHazards Ana-lysis, this field is pop-ulated automaticallywith the value in theCause Frequency (peryear) field in the Haz-ards Analysis Causerecord that is linked tothe Hazards AnalysisConsequence recordthat is linked to the RiskAssessment record youselected.


FunctionType

Character The type ofinstrumentedfunction.

On the datasheet, thisfield appears as a listlabeled Function Typeand contains the fol-lowing baseline values:

l Safety

l Protective




Field Cap-tion


FunctionalLocation ID

Character The ID of theFunctional Loca-tion recordwhose EntityKey is stored inthe FunctionalLocation Keyfield.

On the datasheet, thisfield is disabled and con-tains a button, whichyou can click to searchfor the desired Func-tional Location record.After you select a Func-tional Location record, alink is created betweenthe Functional Locationrecord and the Instru-mented Functionrecord. In addition, theFunctional Location IDwill appear auto-matically in the Func-tional Location ID field.


FunctionalLocation Key

Number The Entity Key ofthe FunctionalLocation recordthat is linked tothe InstrumentedFunction record.

TheMeridiumAPM sys-tem uses this value topopulate the FunctionalLocation ID field.

None



Field Cap-tion


HazardousEvent

Character A description ofthe event forwhich the instru-mented functionexists to preventor mitigate risk.

On the datasheet, thisfield appears as a textbox labeled HazardousEvent, in which you canenter your own value.

If the value in the SILAssessment Methodfield is PHA - Internal,after you select a RiskAssessment recordfrom aHazards Ana-lysis, this field is pop-ulated automaticallywith the value in theConsequence Typefield in the Hazards Ana-lysis Consequencerecord that is linked tothe Risk Assessmentrecord you selected.


Hazards Ana-lysis Date

Date The date theHazards Ana-lysis record towhich the Instru-mented Functionrecord is linkedwas last mod-ified.

On the datasheet, thisfield is disabled and pop-ulated automaticallywith the value stored inthe Last Modified Datefield in the Hazards Ana-lysis record that is linkedto the InstrumentedFunction record andwhose ID appears in theHazards Analysis Refer-ence field.




Field Cap-tion


Hazards Ana-lysis Refer-ence

Character The Record ID ofthe Hazards Ana-lysis record thatis linked to theInstrumentedFunction record.

On the datasheet, thisfield is disabled and pop-ulated automaticallywith the value stored inthe Hazards AnalysisReference field in theSIL Analysis record.Theremust be a valuein this field before youselect the PHA -Internal option in theSIL Assessment field.Otherwise, an error mes-sage will appear.


Hazards Ana-lysis Refer-ence Key

Number The Entity Keyfor the HazardsAnalysis recordthat is linked tothe InstrumentedFunction record.

This field is used by theMeridiumAPM systemto populate the Instru-mented Function recordwith information fromthe Hazards Analysisrecord that is linked tothe Instrumented Func-tion record.

None

I/O FunctionalRelationshipDetails

Text A description ofthe relationshipbetween theinputs and out-puts for the pro-cess, includingdetails such aslogic andmath-ematical func-tions.

On the datasheet, thisfield appears as a textbox labeled I/O Func-tional RelationshipDetails and contains a

button, which youcan click to access theText Editor.




Field Cap-tion


InitiatingEvent

Character A short descrip-tion of the ini-tiating eventwhose descrip-tion exists in theInitiating EventDescription field.

On the datasheet, thisfield appears as a textbox labeled InitiatingEvent, in which you canenter your own value.

If the value in the SILAssessment Methodfield is PHA - Internal,after you select a RiskAssessment recordfrom aHazards Ana-lysis, this field is pop-ulated automaticallywith the value in theCause Type field in theHazards AnalysisCause record that islinked to the HazardsAnalysis Consequencerecord that is linked tothe Risk Assessmentrecord you selected.




Field Cap-tion


InitiatingEventDescription

Text A description ofthe event whichcould initiate aseries of eventsthat present therisk whosedescription existsin the Con-sequenceDescription field.

On the datasheet, thisfield appears as a textbox labeled InitiatingEvent Description andcontains a button,which you can click toaccess the Text Editor.

If the value in the SILAssessment Methodfield is PHA - Internal,after you select a RiskAssessment recordfrom aHazards Ana-lysis, this field is pop-ulated automaticallywith the value in theCause Description fieldin the Hazards AnalysisCause record that islinked to the HazardsAnalysis Consequencerecord that is linked tothe Risk Assessmentrecord you selected.


Last ModifiedBy

Character The name of theuser who lastmodified therecord.

On the datasheet, thisfield is disabled andupdated automaticallywhenever the record ismodified.


Last ModifiedDate

Date The date onwhich the recordwas last mod-ified.

On the datasheet, thisfield is disabled and pop-ulated automatically.




Field Cap-tion


Maintenanceand TestRequirements

Text A description ofthe requirementsfor maintenanceand testing pro-cedures for theinstrumentedfunction.

On the datasheet, thisfield appears as a textbox labeledMain-tenance and TestRequirements, and thevalue is set by default.You can remove thistext and enter your ownvalues. This field con-tains a button, whichyou can click to accessthe Text Editor.


MaintenanceOverride

Logical A logical fieldthat stores thevalueTrueorFalseandindicateswhether the pro-cess requiresoverride pro-cedures for main-tenanceactivities.

None None

Manual Shut-down

Logical A logical fieldthat stores thevalueTrueorFalseandindicateswhether the pro-cess requiresmanual shut-down.

None None



Field Cap-tion


Max ProcessVariable

Number A number rep-resenting theupper value forthe process vari-able range.

On the datasheet, thisfield appears as a textbox labeledMax Pro-cess Variable, in whichyou can enter your ownvalue. This value com-bined with the valuestored in theMin Pro-cess Variable field makeup the process variablerange.


Min ProcessVariable

Number A number rep-resenting thelower value forthe process vari-able range.

On the datasheet, thisfield appears as a textbox labeledMin Pro-cess Variable, in whichyou can enter your ownvalue. This value com-bined with the valuestored in theMaxPro-cess Variable field makeup the process variablerange.


Normal Oper-ation Mode

Text A description ofthe normal oper-atingmode forthe instrumentedfunction.

On the datasheet, thisfield appears as a textbox labeled NormalOperation Mode, andthe values is set bydefault. You canremove this text andenter your own values.This field contains abutton, which you canclick to access the TextEditor.




Field Cap-tion


OperationMode

Character Themode ofoperation for theinstrumentedfunction.

On the datasheet, thisfield appears as a listlabeledOperationModes and contains thefollowing values:

l NORMAL: This isthe value that isselected bydefault.

l ABNORMAL: Ifyou select thisvalue, the fol-lowing fields areenabled:

n AbnormalStates

n OperationModeDescription


Operator Inter-face Require-ment

Text A description ofthe OperatorInterface require-ments.

On the datasheet, thisfield appears as a textbox labeledOperatorInterface Requirement,and the value is set bydefault. You canremove this text andenter your own values.This field contains abutton, which you canclick to access the TextEditor.




Field Cap-tion


PIF ID Character An ID for theinstrumentedfunction.

On the datasheet, thisfield appears as a textbox labeled IF ID, inwhich you can enteryour own value. Thisvalue will appear in thelist of InstrumentedFunction records on theInstrumented Functions(IFs) page. This field isrequired.


PIF Descrip-tion

Character Stores a descrip-tion of the instru-mented function.This field is dis-played on theInstrumentedFunction data-sheet by default.

On the datasheet, thisfield appears as a textbox labeled IF Descrip-tion, in which you canenter your own value.


Pre Alarm Number A number rep-resenting thepoint on the pro-cess variablerange at whichthe pre-alarmshould betriggered.

On the datasheet, thisfield appears as a textbox labeled Pre Alarm,in which you can enteryour own value.




Field Cap-tion


Process Ser-vice Descrip-tion

Text A description ofthe specificationsfor the processservice.

On the datasheet, thisfield appears as a textbox labeled ProcessService Description,and the value is set bydefault. You canremove this text andenter your own values.This field contains abutton, which you canclick to access the TextEditor.


ProcessSpeed

Number A number rep-resenting thetime in secondsthat the processfor which theinstrumentedfunction existstakes to com-plete.

On the datasheet, thisfield appears as a textbox labeled ProcessSpeed with an addi-tional label, (Seconds)to the right of the field.You can enter your ownvalue directly in thePro-cess Speedcell.




Field Cap-tion


RequiredProbability ofFailure

Number A number thatrepresents thetarget probabilitythat an instru-mented functionfailure will occur.

If the value in the SISAssessment Methodfield is RiskMatrix -Internal, this field is dis-abled and populatedautomatically based onthe SIL requirementsfrom the RiskMatrix.

If the value in the SISAssessment field isLayer of Protection Ana-lysis Internal, this field isdisabled and populatedautomatically with thedifference between thevalues in theMitigatedConsequence Fre-quency field and theRequiredMitigated Con-sequence Frequencyfield on the LOPA data-sheet.

For all other SIS Assess-ment methods, you cantype a value directly intothe Required Prob-ability of Failure cell.Note that:

l The value youtypemust fallwithin a certainrange, which isdetermined bythe value in theSelected SILLevel field. If youmodify the valuein the SelectedSIL Level field,the value in thisfield will beupdated auto-




Field Cap-tion


matically to fallwithin the correctrange of valuesfor that level.

l If you try to type avalue into theRequired Prob-ability of Failurecell without firstselecting a valuefrom the Selec-ted SIL Level listor you type avalue that is out-side of the accept-able range, anerror messagewill appear.

l If the value in theSILMode field isLow Demand,when you type avalue into theRequired Prob-ability of Failurecell, the value inthe Risk Reduc-tion Factor fieldwill be populatedautomatically withthe inverse of thevalue you type.Likewise, if youtype a value in theRisk ReductionFactor cell, thevalue in theRequired Prob-ability of Failurefield will be pop-ulated auto-matically with theinverse of the



Field Cap-tion


value that youtype.

After you type a value inthe Required Probabilityof Failure field, it is con-verted automatically toscientific notation form(e.g., 1E-07).



Field Cap-tion


Required SIFAction

Text A description ofthe action thatthe instrumentedfunction per-forms inresponse to atriggered alarm.

On the datasheet, thisfield appears as a textbox labeled RequiredSIF Action and containsa button, which youcan click to access theText Editor.


ResetRequirement

Text A description ofthe requirementsfor resetting aprocess after ithas beentripped.

On the datasheet, thisfield appears as a textbox labeled ResetRequirement, and thevalue is set by default.You can remove thistext and enter your ownvalues. This field con-tains a button, whichyou can click to accessthe Text Editor.


ResponseTime

Number A numeric valuethat representsthe time inseconds that ittakes for theinstrumentedfunction torespond to the ini-tiating event andbring the processto a safe state.

On the datasheet, thisfield appears as a textbox labeled ResponseTimewith an additionallabel,(Seconds), to theright of the field. Youcan enter your ownvalue directly in theResponse Time cell.




Field Cap-tion


Risk Reduc-tion Factor(RRF)

Number A number rep-resenting thefactor bywhichthe risk shouldbe reduced forthe instrumentedfunction.

If the value in the SILMode field is LowDemand and the valuein the SIS AssessmentMethod field is Layer ofProtection Analysis -Internal or RiskMatrix -Internal, this value is dis-abled and populatedautomatically with theinverse of the value inthe Required Probabilityof Failure field.

For all other SISWhenthe value in the SILMode field is LowDemand and the valuein the SIS AssessmentMethod field is not Layerof Protection Analysis -Internal or RiskMatrix -Internal, this field isenabled and you cantype a value directly intothe Risk ReductionFactor cell. Note that:

l The value youtypemust fallwithin a certainrange, which isdetermined bythe value in theSelected SILLevel field. If youmodify the valuein the SelectedSIL Level field,the value in thisfield will beupdated auto-matically to fallwithin the correctrange of values




Field Cap-tion


for that level.

l If you try to type avalue into theRisk ReductionFactor cellwithout first select-ing a value fromthe Selected SILLevel list or youtype a value thatis outside of theacceptablerange, an errormessage willappear.

l If you type a valueinto the RiskReductionFactor cell, thevalue in theRequired Prob-ability of Failurefield will be pop-ulated auto-matically with theinverse of thevalue that youtype. Likewise, ifyou type a valueinto the RequiredProbability ofFailure cell, thevalue in the RiskReduction fieldwill be populatedautomatically withthe inverse of thevalue that youtype.

If the value in the SILMode field isHighDemand



Field Cap-tion


orContinuous,this fieldis disabled and does notcontain a value.

Safe StateDescription

Text A description ofthe safe state towhich the pro-cess should betaken via theinstrumentedfunction.

On the datasheet, thisfield appears as a textbox labeled Safe StateDescription and con-tains a button, whichyou can click to accessthe Text Editor.


Selected SILLevel

Number A number rep-resenting the SILvalue that isrequired for theinstrumentedfunction.

On the datasheet, thisfield is disabled and pop-ulated automatically ifthe value in the SILAssessment Methodfield is anything otherthan External.

If the SIL AssessmentMethod field contains anExternal value, this fieldis enabled and appearsas a list that is populatedwith values from theMI_SAFETY_INDEX_LEVEL SystemCodeTable. You can select avalue from the list.

If a value exists in theRequired Probability ofFailure field, and you tryto delete the value in theSelected SIL Level field,an error messageappears, and you willnot be able to delete thevalue.




Field Cap-tion


SIL AnalysisKey

Number The Entity Key ofthe SIL Analysisrecord to whichthe InstrumentedFunction recordis linked.

This field is used intern-ally by theMeridiumAPM system.

None

SIL Assess-ment Method

Character Themethodused to assessthe risk asso-ciated with theinstrumentedfunction.

On the datasheet, thisfield appears as a listlabeled SIL Assess-ment Method and con-tains the followingvalues:

l RiskMatrix -Internal

l Layer of Pro-tection AnalysisInternal

l PHA - Internal

l ALARP -External

l Event Tree

l Fault Tree

l LOPA - External

l RiskGraph

l RiskMatrix -External

If you select the PHA -Internal option, theremust be a value in theHazards Analysis Refer-ence field. Otherwise,an error message willappear.




Field Cap-tion


SIL Mode Character The SILmodethat is defined forthis instrumentedfunction basedon the code IEC-61508.

On the datasheet, thisfield appears as a listlabeled SIL Mode andcontains the followingbaseline values:

l Low Demand

l High Demand

l Continuous


SIS SystemID

Character The ID of theSafety Instru-mented Systemrecord to whichthe InstrumentedFunction recordis linked.

On the datasheet, thisfield appears as a listlabeled SIS ID and con-tains the values thatexist in the SIS ID fieldin the Safety Instru-mented System recordsthat are linked to the SILAnalysis record withwhich you are currentlyworking.


Site Descrip-tion

Character A description ofthe site that isspecified in theSite ID field.

None None

Site ID Character The ID of the sitethat is associatedwith the instru-mented function.

On the datasheet, thisfield is disabled and pop-ulated automaticallywith the value in the SiteID field of the asso-ciated SIL Analysisrecord.




Field Cap-tion


Spurious TripLimit (per yr)

Number A number rep-resenting thenumber of timesper year it isacceptable for aspurious trip tooccur for thisinstrumentedfunction.

On the datasheet, thisfield appears as a textbox labeled SpuriousTrip Limit (per yr), inwhich you can enteryour own value. Thisvalue is used to determ-ine the value in theMeets STR Limit field ina Protective InstrumentLoop record that islinked to the Instru-mented Functionrecord.


Startup AndRestart Pro-cedure

Text A detaileddescription of thestartup andrestart pro-cedures for theprocess.

On the datasheet, thisfield appears as a textbox labeled Startup andRestart Procedure, andthe value is set bydefault. You canremove this text andenter your own values.This field contains abutton, which you canclick to access the TextEditor.


SurvivalRequirement

Text A description ofthe requirementsfor the instru-mented functionto survive a cata-strophic event,such as an earth-quake.

On the datasheet, thisfield appears as a textbox labeled SurvivalRequirement, and thevalue is set by default.You can remove thistext and enter your ownvalues. This field con-tains a button, whichyou can click to accessthe Text Editor.




Field Cap-tion


Trip Mode Character A short descrip-tion of the tripmode (i.e., ener-gize to trip or de-energize to trip).

On the datasheet, thisfield appears as a textbox labeled Trip Mode,and the values is set tode-energize to trip bydefault. You canremove this text andenter your own value.


Trip Point Number A number rep-resenting thepoint on the pro-cess variablerange at whichthe trip alarmshould betriggered.

On the datasheet, thisfield appears as a textbox labeled Trip Point,in which you can enteryour own value.


Unit Descrip-tion

Character Adescription ofthe unit that isspecified in theUnit ID field.

None None

Unit ID Character The ID for theunit where theinstrumentedfunction exists.

On the datasheet, thisfield appears as a textbox labeled Unit ID, inwhich you can enteryour own value.


Functional Test Detail


Functional Test DetailThe following table provides a list of the fields that exist in the Functional Test Detail family. Thislist is not comprehensive.

Field Cap-tion


As FoundTravelTime Limit

Number Themaximumas-foundtravel time allowed, inseconds. For example,the valuemight indicatethemaximumamount oftime it takes a switch tochange from open toclose.

This field is enabled only in Func-tional Test Detail records that arelinked to records representingfinal elements.

As FoundTrip Point

Number A value that indicates theperformance of the prooftest (i.e., the value youfound in the field).

You can type a value in this fieldmanually. This field is enabledonly in Functional Test Detailrecords that are linked to recordsrepresenting sensors, final ele-ments, or logic solvers.

As FoundTrip PointError

Number The error between thevalue you found in the field(i.e., As Found Trip Point)and the acceptable range(i.e., Trip Point ErrorLimit).

This field is enabled only in Func-tional Test Detail records that arelinked to records representingsensors, final elements, or logicsolvers.

As LeftTravelTime Limit

Number Themaximumas-lefttravel time allowed, inseconds.

This field is enabled only in Func-tional Test Detail records that arelinked to records representingfinal elements.



Field Cap-tion


As LeftTrip Point

Number A value that indicates thefinal performance of theproof test. If the value inthe As Found Trip Pointfield is within the TripPoint Error Limit, youmight not make adjust-ments, and the As LeftTrip Point will be thesame. If the As Found TripPoint is not within the TripPoint Error Limit, youmaymake adjustments, andwill enter the new adjus-ted trip point as the As LeftTrip Point.

You can type a value in this fieldmanually. This field is enabledonly in Functional Test Detailrecords that are linked to recordsrepresenting sensors, final ele-ments, or logic solver.

As LeftTrip PointError

Number The error between thevalue you left in the field(i.e., As Left Trip Point)and the acceptable range(i.e., Trip Point ErrorLimit).

This field is enabled only in Func-tional Test Detail records that arelinked to recordsrepresentingsensors, final ele-ments, or logic solvers.

EquipmentID

Character The Record ID of theEquipment record againstwhich the step should beperformed.

You can select the associatedEquipment record by clicking the

in the Equipment ID field.

LocationID

Character The Record ID of theFunctional Locationrecord against which thestep should be performed.

You can select the associatedFunctional Location record byclicking the in the Location IDfield.



Field Cap-tion


Pass/Fail Character The status of the prooftest step.

This value indicates the status ofthe proof test step identified in theStep Sequence Number andStep Type fields. This field willcontain one of the following val-ues: Pass, Fail, Skip, Complete.This field is populated auto-matically based upon other val-ues in the record. The value inthis field will be set automaticallyto Pass if any of the following con-ditions is true:

l The Trip Point, Trip PointError, and Travel Time Limitfields are empty.

l For logic solvers, sensors, andfinal elements, the value in theAs Found Trip Point field iswithin the range establishedby the Trip Point Limit field.

l For final elements, the value inthe As Found Travel Time iswithin the range establishedby the Travel Time Limit.

l If the Trip Point and Trip PointError fields are empty but theTravel Time Limit field is not,the pass/fail status will bedetermined solely by TravelTime Limit. The opposite istrue aswell.

Result Cri-teria

Text A description of an accept-able result of the test.

This field is populated auto-matically and cannot bemodified.

StepSequenceNumber

Number A number that representsthe order in which the stepshould be performed, rel-ative to other steps.

This field is populated auto-matically.



Field Cap-tion


Step Type Character The type of step. This field is populated auto-matically. When this field containsthe value Sensor or Final Ele-ment, the following fields will beenabled: Trip Point, Trip Point Dir-ection, Trip Point Error Limit, andTrip Point Units. The Travel TimeUnits field is also enabled whenthis field contains the value FinalElement.

Test Cri-teria

Text The nature of the test. This field is populated auto-matically and cannot bemodified.

TemplateDetail ID

Character An alphanumeric valuethat identifies the Func-tional Test Detail record.

This value is generated auto-matically and cannot bemodified.

TravelTime Limit

Number Themaximumacceptabletravel time for this step, inseconds.

This field is populated auto-matically with the value in theTravel Time Limit field in the asso-ciated SIS Proof Test TemplateDetail record and disabled unlessthe value in the Step Type field isFinal Element.

Trip Point Number A value that defineswhenthe element will activatean SIS shutdown. Forexample, a trip point on awater heater might be 140degrees, a temperaturethat would scaldsomeone.

This field is populated auto-matically with the value in the TripPoint field in the associated SISProof Test Template Detailrecord and disabled unless thevalue in the Step Type field isFinal Element.

Trip PointDirection

Character The trend of Trip Point val-ues.

This field is populated auto-matically with the value in the TripPoint Direction field in the asso-ciated SIS Proof Test TemplateDetail record and disabled unlessthe value in the Step Type field isSensor or Final Element.



Field Cap-tion


Trip PointError Limit

Number Anumber identifying therange from the Trip Point,plus or minus, withinwhich the As Found TripPoint valuemust fall to beacceptable. For example,if the Trip Point is5, andthe Trip Point Error Limitis 3, the As Found TripPoint must fall within plusor minus three of the TripPoint (i.e., from 2 to 8).

This field is populated auto-matically with the value in the TripPoint Error Limit field in the asso-ciated SIS Proof Test TemplateDetail record and disabled unlessthe value in the Step Type field isSensor or Final Element.

Trip PointUnits

Character The unit of measure asso-ciated with the value in theTrip Point field.

This field is populated auto-matically with the value in the TripPoint Units field in the associatedSIS Proof Test Template Detailrecord and disabled unless thevalue in the Step Type field isSensor or Final Element.

LOPA


LOPALOPA records store details about the Layer of Protection Analysis they represent. The followingtable provides an alphabetical list and description of the fields that exist for the LOPA family andappear on the LOPA datasheet, unless otherwise specified. The information in the table reflectsthe baseline state and behavior of these fields. This list is not comprehensive.

Field Caption DataType Description Behavior and Usage Datasheet/Tab

Analysis Type Character The type ofanalysis thatyou are con-ducting.

This field does not appearon the datasheet by defaultand is populated auto-matically with the valueLOPA.

This field doesnot appear onthe LOPA data-sheet.

Calculated SIL Number The SIL valuethat isrequired tomitigate therisk that isassociatedwith the Instru-mented Func-tion record towhich theLOPA recordis linked.

This field is disabled andpopulated automaticallywith the SIL value that isassociated with the value inthe Required PIF PHDfield.


Comments Text Additionalinformationabout theLayer of Pro-tection Ana-lysis.

On the datasheet, this fieldappears as a text boxlabeled Comments andcontains a button, whichyou can click to access theText Editor.

Definition tab

Description Text A descriptionfor the Layerof ProtectionAnalysis.

On the datasheet, this fieldappears as a text boxlabeled Description andcontains a button, whichyou can click to access theText Editor.

Definition tab

LOPA



Description ofInitiating Event

Character A descriptionof the ini-tiating eventthat is spe-cified in the Ini-tiating Eventfield.

This field is populated auto-matically with the value inthe Initiating Event Descrip-tion field in the associatedInstrumented Functionrecord. You canmodify thisvalue if needed.

Details tab

EnablingEvent/ConditionDescription

Character A descriptionof the eventthat will allowthe risk that isassociatedwith the ini-tiating event,which isdescribed inthe InitiatingEvent field, tobemitigated(e.g., theequipmentonly operatesninemonthsof the year).

You can type your ownvaluemanually.

Details tab

EnablingEvent/ConditionProbability

Number A number thatrepresentsthe probabilityvalue that isassociatedwith theenablingevent and theinitiatingevent. Thisvalue is usedto determinethe probabilityof an unmit-igated eventoccurring.

You can type your ownvaluemanually. The valuemust be greater than 0(zero) and less than orequal to 1 (one).

This value ismultiplied bythe value in the Frequencyof Initiating Event field todetermine the value inUnmitigated ConsequenceFrequency field. If this fieldis empty, a default valueof1will be used in that cal-culation.

Details tab

LOPA



Frequency ofInitiating Event

Number A number rep-resenting thenumber oftimes per yearthat the ini-tiating eventthat is spe-cified in the Ini-tiating Eventfield willoccur.

This field is required and ispopulated automaticallywith the value in the Fre-quency of Initiating Event(per yr) field in the asso-ciated Instrumented Func-tion record.

You canmodify this value,but it must be greater than0 (zero). If you type a valueless than 0 (zero), a mes-sage will appear, and whenyou clickOK, themodifiedvalue will be reverted backto its original value.

This value ismultiplied bythe value in the EnablingEvent/Condition Probabilityfield to determine the valuein Unmitigated Con-sequence Frequency field.

Details tab

Initiating Event Character A briefdescription ofthe event thatcould causethe risk that isdescribed inthe Unac-ceptable Con-sequencefield to bemit-igated.

This field is populated auto-matically with the value inthe Initiating Event field inthe associated Instru-mented Function record.You canmodify this value ifneeded.

Details tab

LOPA ID Character The ID for theLayer of Pro-tection Ana-lysis.

You can type your ownvaluemanually. The valuewill appear on the Instru-mented Functions (IFs)page and is used to dis-tinguish the LOPA recordfrom other LOPA records.This field is required.

Definition tab

LOPA



Mitigated Con-sequence Fre-quency

Number A number rep-resenting themitigated con-sequence fre-quency, or theconsequencefrequencyafter layers ofprotectionhave beenadded.

This field is disabled andpopulated automatically.The value is calculated bymultiplying the value in theUnmitigated ConsequenceFrequency field by thevalue in the Total IPL PFDfield.

Definition tab

Required Mit-igated Con-sequenceFrequency

Number Themax-imum allow-ablefrequency atwhich the ini-tiating eventcan occur forthe risk that isdescribed inthe Unac-ceptable Con-sequencefield.

This field is required. Onthe datasheet, this fieldappears as a list labeledRequired Mitigated Con-sequence Frequencyandcontains the following hard-coded values:

l 1E-04

l 1E-05

l 1E-06

You can select a value fromthe list or type your ownvalue. If you type your ownvalue, it must be greaterthan 0 (zero). If youmodifythis value to be less than 0(zero), a message willappear, and when you clickOK, themodified value willrevert back to its originalvalue. If you enter a valueother than the baseline val-ues in the list, it will then beadded to the list.

Definition tab

LOPA



Required PIFPFD

Number A number rep-resenting thetarget prob-ability that afailure willoccur.

This field is disabled andpopulated automatically.This value is calculatedautomatically as the dif-ference between the valuein theMitigated Con-sequence Frequency fieldand the value in theRequiredMitigated Con-sequence Frequency Field.This value is used todetermine the values in theRequired PIF Risk Reduc-tion Factor and CalculatedSIL Level fields.

Details tab

Required PIFRisk ReductionFactor

Number A number rep-resenting thefactor bywhich the riskshould bereduced.

This field is disabled andpopulated automaticallywith the inverse of the valuein the Required PIF PHDfield.

Details tab

Title Character A shortdescription forthe Layer ofProtectionAnalysis.


Definitiontab

Total IPL PFD Number The PFDvalue asso-ciated with allthe IPLs inplace for thisconsequence.

This field is disabled andpopulated automatically.The value is calculated bymultiplying the values in thePFD fields of eachIndependent Layer of Pro-tection record associatedwith the LOPA Analysistogether.

Details tab

LOPA



Total CM Prob-ability

Number The sum ofthe valuesthat exist inthe Prob-ability fields inthe Con-sequenceModifierrecords thatare linked tothe LOPArecord.

This field is disabled andpopulated automatically.This field does not appearon the LOPA datasheet bydefault.


UnacceptableConsequence

Character A descriptionof the risk forwhich you areconductingthe Layer ofProtectionAnalysis.

This field is populated auto-matically with the value inthe Consequence Descrip-tion field in the associatedInstrumented Functionrecord. You canmodify thisvalue if needed.

Details tab

UnmitigatedConsequenceFrequency

Number A number rep-resenting theunmitigatedconsequencefrequency, orthe con-sequence fre-quencybefore layersof protectionhave beenadded.

This field is disabled andpopulated automatically.The value is calculated bymultiplying the value in theFrequency of InitiatingEvent field by the value inthe Enabling Event/Condi-tion Probability field.

Details tab

Protective Instrument Loop


Protective Instrument LoopProtective Instrument Loop records store details about protective instrument loops for a safetyinstrumented system. The following table provides an alphabetical list and description of the fieldsthat exist for the Protective Instrument Loop family and appear on the Protective Instrument Loopdatasheet by default. The information in this table reflects the baseline state and behavior ofthese fields.

Field Data Type Description Behavior and Usage

Achieved SIL Number A number rep-resenting theoverall SIL valuefor the protectiveinstrument loop.

This field appears as a list in the Cal-culated Results section on the datasheetand contains the following options:

l 0 (zero)

l 1

l 2

l 3

l 4

When the value in the SIL ValidationMethod field is External Calculation, theAchieved SIL field is enabled, and you canselect a value from the list.

When the value in the SIL ValidationMethod field is Internal Calculation, theAchieved SIL field is disabled and pop-ulated automatically with the lowest valueof the values stored in the following fields:

l Calculated SIL

l Calculated SIL Architectural Con-straints

l Calculated SIL Systematic Cap-abilities

For example, if the value in each of thesefields was 2, the value in the Achieved SILfield would be 2. If the value in two of thefields was 2 and the value in one of thefields was 1, the value in the Achieved SILfield would be 1.




Availability Number A number rep-resenting the per-centage of timebetween prooftests that the pro-tective instru-ment loop isprotecting thesafety instru-mented system.

This field appears as a text box, which isdisplayed in the Calculated Results sec-tion on the datasheet and is enabled or dis-abled based upon the following criteria:

l When the value in the SIL Val-idationMethod field is External Cal-culation, the Availability field isenabled, and you can type a valuedirectly into the Availability cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin the Availability field.

CalculatedSIL

Number A number rep-resenting the SILvalue for the pro-tective instru-ment loop, whichis the valuestored in theLoop PFD Avgfield.

This field appears as a text box, which isdisplayed in the Calculated Results sec-tion on the datasheet and is enabled or dis-abled based upon the following criteria:

l When the value in the SIL Val-idationMethod field is External Cal-culation, the Calculated SIL field isenabled, and you can type a valuedirectly into the Calculated SIL cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automatically,based on the value in the Loop PFDAvg field, and displays one of the fol-lowing values as read-only in theCalculated SIL field:

o 0 (zero)o 1o 2o 3o 4




CalculatedSIL Archi-tectural Con-straints

Number The SIL value forthe protectiveinstrument loop,which is basedon architecturalconstraintsdefined in theTest ArchitectureConstraints field.

This field appears as a text box in the Cal-culated Results section on the datasheetand is enabled or disabled based upon thefollowing criteria:

l When the value in the SIL Val-idationMethod field is External Cal-culation, the Calculated SILArchitectural Constraints field isenabled, and you can type a valuedirectly into the Calculated SILArchitectural Constraints cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automatically,based on the value in the Test Archi-tecture Constraints field, and dis-plays one of the following values asread-only in the Calculated SILArchitectural Constraints field:





CalculatedSIL Sys-tematic Cap-abilities

Number The SIL value forthe protectiveinstrument loop,which is basedon systematiccapabilitiesdefined in the fail-ure rate dataassociated witheach protectiveinstrument loopelement.


l When the value in the SIL Val-idationMethod field is External Cal-culation, the Calculated SILSystematic Capabilities field isenabled, and you can type a valuedirectly into the Calculated SIL Sys-tematic Capabilities cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automatically,based on the systematic capabilitiesdefined in the failure rate data asso-ciated with each protective instru-ment loop element, and displaysone of the following values as read-only in the Calculated SIL Sys-tematic Capabilities field:


If the value in the Systematic CapabilityValidation field is False, this value is set toNA.




CalculatedSTR

Number A number rep-resenting thespurious trip ratefor the protectiveinstrument loop.


l When the value in the SIL Val-idationMethod field is External Cal-culation, the Calculated STR field isenabled, and you can type a valuedirectly into the Calculated STRcell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin the Calculated STR field.

DemandMode

Character A value that indic-ates how fre-quently theprotective instru-ment loop will bein demand. Inother words,how frequentlythe protectiveinstrument loopwill be needed toprotect the safetyinstrumented sys-tem as a result ofa failure.

This field is disabled and populated auto-matically with the value stored in the SILMode field in the Instrumented Functionrecord that is linked to the ProtectiveInstrument Loop record.

Description Character A brief descrip-tion of the pro-tectiveinstrument loop.

You can type a value directly into theDescription cell.




Final ElementMCI

Number A percentagethat representstheMaintenanceCapability Index.

This field appears as a list labeled FinalElement MCI and contains the followingoptions:

l MCI 0 (0%): Indicates that repairactions are never performed.

l MCI 1 (60%): Indicates that repairactions are effective 60 percent ofthe time.



l MCI 4 (100%): Indicates that repairactions are always performed per-fectly.

ID Character The ID of the pro-tective instru-ment loop.

You can type a value directly into the IDcell. This value is required andmust beunique. If you do not type a unique valueinto the ID cell, you will not be able to savethe Protective Instrument Loop record.

Last ModifiedBy

Character The name of theuser who lastmodified therecord.

This field is disabled and populated auto-matically with the name of theMeridiumAPMSecurity User who last modified theProtective Instrument Loop record.

Last ModifiedDate

Date The date onwhich the recordwas last mod-ified.

This field is disabled and populated auto-matically with the date on which the Pro-tective Instrument Loop record was lastmodified.




Logic SolverMCI

Number A percentagethat representstheMaintenanceCapability Index.

This field appears as a list labeled LogicSolver MCI and contains the followingoptions:






Loop Class Character A value that indic-ates whether theprotective instru-ment loop isdesigned tomit-igate safety risksor commercialrisks.

This field appears as a list labeled LoopClass and contains the following options:

l Safety: Indicates that the protectiveinstrument loop is designed tomit-igate risks related to safety. Forexample, a safety loopmight pre-vent a highmotor current from caus-ing a fire.

l Protective: Indicates that the pro-tective instrument loop is designedtomitigate commercial risks only.For example, a protective loopmight prevent low lube pressurefrom causing amechanical failurewhere there is no safety riskinvolved.




Loop PFDAvg

Number A number rep-resenting theprobability thatthe protectiveinstrument loopwill fail.

This field appears as a text box in the Cal-culated Results section on the datasheet,which is enabled or disabled based uponthe following criteria:

l When the value in the SIL Val-idationMethod field is External Cal-culation, the Loop PFD Avg field isenabled, and you can type a valuedirectly into the Loop PFD Avg cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin the Loop PFD Avg field.

Loop PFH Number A number rep-resenting theprobability perhour that the pro-tective instru-ment loop willfail.


l When the value in the SIL Val-idationMethod field is External Cal-culation, the Loop PFH field isenabled, and you can type a valuedirectly into the Loop PFH field cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin the Loop PFH field.




Loop Type Character A value rep-resenting the cat-egory of theprotective instru-ment loop, basedon the type ofdata that thesensor ismeas-uring.

This field appears as a list labeled LoopType and contains the following options:

l Analysis

l Flow

l Level

l Load

l Pressure

l Speed

l Temperature




Meets Archi-tectural Con-straints

Character A value that indic-ates whether theprotective instru-ment loop's archi-tecturalconstraintsmeetthe requirementdefined by thevalue in theRequired SILfield.

This field appears as a list labeledMeetsArchitectural Constraints in the Cal-culated Results section on the datasheetand contains the following options:

l Incomplete

l Yes

l No

l NA

This value is set to Incomplete by default.

When the value in the SIL ValidationMethod field is External Calculation, theMeets Architectural Constraints field isenabled, and you can select a value fromthe list.

When the value in the SIL ValidationMethod field is Internal Calculation, theMeets Architectural Constraints field is dis-abled and populated automatically. Afteryou calculate the SIL Validation results,theMeets Architectural Constraints field ispopulated using the following logic:

l If the value in the Calculated SILArchitectural Constraints field isgreater than or equal to the value inthe Required SIL field, this value isset to Yes.

l Otherwise, this value is set to No.

If the value in the Test Architectural Con-straints field is Not Consider, this value isset to NA.




Meets Avail-ability Target

Character A value that indic-ates whether theprotective instru-ment loop's avail-abilitymeets theavailabilityrequirementdefined in theInstrumentedFunction recordthat is linked tothe ProtectiveInstrument Looprecord.

This field appears as a list labeledMeetsAvailability Target in the Calculated Res-ults section on the datasheet and containsthe following options:

l Incomplete

l Yes

l No

l NA


When the value in the SIL ValidationMethod field is External Calculation, theMeets Availability Target field is enabled,and you can select a value from the list.

When the value in the SIL ValidationMethod field is Internal Calculation, theMeets Availability Target field is disabledand populated automatically. After you cal-culate the SIL Validation results, theMeets Availability field is populated usingthe following logic:

l If the value in the DemandModefield is Low Demand, and the valuein the Availability field is greaterthan or equal to the value stored inthe Availability Target field in theInstrumented Function record thatis linked to the Protective Instru-ment Loop record, this value is setto Yes.


If the value in the DemandMode field isHigh Demand or Continuous, this value isNA.




Meets SILRequirement

Character A value that indic-ates whether theprotective instru-ment loop's SILvaluemeets theSIL requirementdefined in theRequired SILfield.

This field appears as a list labeledMeetsSIL Requirement in the Calculated Res-ults section on the datasheet and containsthe following options:

l Incomplete

l Yes

l No

l NA


When the value in the SIL ValidationMethod field is External Calculation, theMeets SIL Requirement field is enabled,and you can select a value from the list.

When the value in the SIL ValidationMethod field is Internal Calculation, theMeets SIL Requirement field is disabledand populated automatically. After you cal-culate the SIL Validation results, theMeets SIL Requirement field is populatedusing the following logic:

l If the value in the Achieved SIL fieldis greater than or equal to the valuein the Required SIL field, this valueis set to Yes.





Meets STRLimit

Character A value that indic-ates whether theprotective instru-ment loop's spuri-ous trip ratemeets the spuri-ous trip raterequirementdefined in theInstrumentedFunction recordthat is linked tothe ProtectiveInstrument Looprecord.

This field appears as a list labeledMeetsSTR Limit in the Calculated Results sec-tion on the datasheet and contains the fol-lowing options:

l Incomplete

l Yes

l No

l NA


When the value in the SIL ValidationMethod field is External Calculation, theMeets STR Limit field is enabled, and youcan select a value from the list.

When the value in the SIL ValidationMethod field is Internal Calculation, theMeets STR Limit field is disabled and pop-ulated automatically. After you calculatethe SIL Validation results, theMeets STRLimit field is populated using the followinglogic:

l If the inverse of the value stored intheMTTS field is greater than orequal to the value stored in theSpurious Trip Limit (per yr) field inthe Instrumented Function recordthat is linked to the Protective Instru-ment Loop record, the value in theMeets STR Limit field is set to No.

l Otherwise, the value in theMeetsSTR Limit field is set to Yes.

If the Protective Instrument Loop record ispart of a protective instrument loop tem-plate, this value is set to NA.




Meets Sys-tematic Cap-abilities

Character A value that indic-ates whether theprotective instru-ment loop's sys-tematic capabilitymeets the sys-tematic capabilityrequirementdefined in theRequired SILfield.

This field appears as a list labeledMeetsSystematic Capabilities in the Cal-culated Results section on the datasheetand contains the following options:

l Incomplete

l Yes

l No

l NA


When the value in the SIL ValidationMethod field is External Calculation, theMeets Systematic Capabilities field isenabled, and you can select a value fromthe list.

When the value in the SIL ValidationMethod field is Internal Calculation, theMeets Systematic Capabilities field is dis-abled and populated automatically. Afteryou calculate the SIL Validation results,theMeets Systematic Capabilities field ispopulated using the following logic:

l If the value in the Calculated SILSystematic Capabilities field isgreater than or equal to the value inthe Required SIL field, this value isset to Yes.


If the value in the Systematic CapabilityValidation field is False, this value is set toNA.

Mission Time Number A number thatrepresents inyears the timethat the pro-tective instru-ment loop will bein use before it isreplaced.

You can type a value into this field manu-ally. This value ismeasured in years.




MTTFS Number A number thatrepresentsMeanTime To FailSafe (i.e., theaverage amountof time betweenprotective instru-ment loop fail-ures that occurduring safe scen-arios).


l When the value in the SIL Val-idationMethod field is External Cal-culation, theMTTFS field isenabled, and you can type a valuedirectly into theMTTFS cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin theMTTFS field.

This value ismeasured in years.

Required SIL Number A number rep-resenting the SILvalue that isrequired for theprotective instru-ment loop.

This field is disabled and populated auto-matically with the value stored in the Selec-ted SIL Level field in the InstrumentedFunction record that is linked to the Pro-tective Instrument Loop record.

Risk Reduc-tion Factor

Number A number rep-resenting thefactor bywhichthe risk shouldbe reduced forthe protectiveinstrument loop.


l When the value in the SIL Val-idationMethod field is External Cal-culation, the Risk Reduction Factorfield is enabled, and you can type avalue directly into the Risk Reduc-tion Factor cell.

l When the value in the SIL Val-idationMethod field is Internal Cal-culation, theMeridiumAPM systemcalculates this value automaticallyand displays that value as read-onlyin the Risk Reduction Factor field.




Sensor MCI Number A value that rep-resents theMain-tenanceCapability Index.

This field appears as a list labeled SensorMCI and contains the following options:






SIL ValidationMethod

Character A value that rep-resents the typeof method usedto calculate theSIL Validationresults for theprotective instru-ment loop.

This field appears as a list labeled LoopClass and contains the following options:

l Internal Calculation: Indicates thattheMeridiumAPM systemwill cal-culate the SIL Validation results.When this option is selected, theMeridiumAPM system calculatesthe values in all cells in the Cal-culated Results section auto-matically and displays them asread-only.

l External Calculation: Indicatesthat you will type SIL Validation res-ults directly into cells on the Pro-tective Instrument Loop datasheet.When this option is selected, allcells in the Calculated Results sec-tion are enabled, and you can typevalues directly into those cells.




Startup Time Number A number rep-resenting theamount of timeneeded for theprotective instru-ment loop to berestored after afailure.

You can type a value into this field manu-ally. This value ismeasured in hours.

SystematicCapability Val-idation

Logical A value that indic-ates whether theSIL value for theprotective instru-ment loop willaccount for sys-tematic cap-abilities, whichare defined in thefailure data foreach protectiveinstrument loopelement.

If this value is True, the protective instru-ment loop will use systematic capabilities.If this value is False, the protective instru-ment loop will not use systematic cap-abilities.

Test Archi-tecture Con-straints

Character A value that indic-ates the level ofsafety cer-tification that isassociated withthe elements inthe protectiveinstrument loop.

This field appears as a list labeled TestArchitecture Constraints and containsthe following options:

l IEC 61508: Indicates that the ele-ments in the protective instrumentloop have been certified accordingto the IEC 61508 standard.

l IEC 61511: Indicates that the ele-ments in the protective instrumentloop have been certified accordingto the IEC 61511 standard.

l Not Consider: Indicates that thearchitectural constraints will not beconsidered in the SIL calculation.

Protective Instrument Loop Final Element


Protective Instrument Loop Final ElementProtective Instrument Loop Final Element records store details about final elements for a pro-tective instrument loop. The following table provides an alphabetical list and description of thefields that exist for the Protective Instrument Loop Final Element family. The information in thistable reflects the baseline state and behavior of these fields. This list is not comprehensive.

Field Cap-tion

DataType Description Behavior and

Usage Datasheet/Tab

CustomPVSTCoverage

Number A numeric value rep-resenting the per-centage of possiblefailures that could bedetected by the par-tial valve stroke test.

On the datasheet,this field appearsas a text boxlabeled CustomPVST Coverage,in which you canenter your ownvalue.

Final Element data-sheet

Description Character A description for thefinal element.

On the datasheet,this field appearsas a text boxlabeled Descrip-tion, in which youcan enter your ownvalue.


Dangerouscombinationof outputs?

Logical Stores the valueTrue orFalse indic-ating whether the out-put associated withthe final element canlead to a hazardousevent if it occurs sim-ultaneously with theoutput associatedwith a different finalelement.

In the UI, this fieldappears as a checkbox labeled Dan-gerous Com-bination ofOutputs?, whichyou can select toindicate that thefinal element isassociated with acombination of out-puts hazard. Thischeck box is clearby default. Whenyou select thischeck box, the Haz-ardous Events fieldis enabled andrequired.

Dangerous Com-bination of Outputstab on the <RecordID> (ProtectiveInstrument LoopFinal Element) win-dow



Field Cap-tion


Usage Datasheet/Tab

Final Ele-ment ID

Character An ID for the final ele-ment.

On the datasheet,this field appearsas a text boxlabeled Final Ele-ment ID, in whichyou can enter yourown value. Thisvalue is displayedin the diagram toidentify the final ele-ment. This field isrequired.


HazardousEvents

Text A description of thehazardous event thatcan occur if the out-put associated withthe final elementoccurs sim-ultaneously with theoutput of a differentfinal element.

In the UI, this fieldappears as a textboxwithout a cap-tion and contains a

button, whichyou can click toaccess the TextEditor. When theDangerous Com-bination of Out-puts? check box isselected, this fieldis enabled andrequired. Other-wise, this field is dis-abled.

Potential DangerousCombination of Out-puts Description sec-tion ontheDangerous Com-bination of Outputstab on the <RecordID> (ProtectiveInstrument LoopFinal Element) win-dow

PVST Inter-val

Number A numeric value rep-resenting the fre-quency at which thepartial valve stroketest should be per-formed.

On the datasheet,this field appearsas a text boxlabeled PVST Inter-val, in which youcan enter your ownvalue. This field isenabled only if thePartial ValveStroke Testingcheck box is selec-ted.




Field Cap-tion


Usage Datasheet/Tab

PVST Inter-val UOM

Character The unit of measureassociated with thevalue stored in thePVST Interval field.

On the datasheet,this field appearsas a list labeledPVST IntervalUOM. You canselect a value inthis list. This field isenabled only if thePartial ValveStroke Testingcheck box is selec-ted.


Protective Instrument Loop Logic Solver


Protective Instrument Loop Logic SolverProtective Instrument Loop Final Element records store details about logic solvers for a pro-tective instrument loop. The following table provides an alphabetical list and description of thefields that exist for the Protective Instrument Loop Logic Solver family and appear on the Pro-tective Instrument Loop Logic Solver datasheet. The information in this table reflects the baselinestate and behavior of these fields. This list is not comprehensive.

Field Cap-tion

DataType Description Behavior and Usage Datasheet Tab

ApprovedCustomDevice

Logical Indicateswhether or notthe logic solverthat is identifiedin the ExidaName field isapproved foruse in the pro-tective instru-ment loop.

This field appears as acheck box labeledApproved CustomDevice. This value is dis-abled and populated auto-matically by theMeridiumAPM systemwith one ofthe following values:

l If this value is True, itindicates the deviceis an approveddevice.

l If this value is False,it indicates that thedevice is not anapproved device.

Logic SolverDetails tab

ArchitecturalType

Character Indicates thelevel of safetycertification ofthe logic solverbased on com-pliance withstandard IEC61508.

If the value in theManualEntry field is False, thisvalue is disabled and pop-ulated automatically withone of the following valuesbased on the device iden-tified in the Exida Namefield:

l A

l B

If the value in theManualEntry field is True, this fieldis enabled, and you cantype a value directly into theArchitectural Type cell.




Field Cap-tion


Availability Number A number rep-resenting thepercentage oftime betweenproof tests thatthe logic solveris operating inthe protectiveinstrumentloop.

This field appears as a textbox labeled Availability.TheMeridiumAPM systemcalculates this number auto-matically and displays it asread-only in the Avail-ability text box.

Calculated Res-ults section on theLogic SolverDetails tab

CalculatedPFD Avg

Number A number rep-resenting theprobability thatthe logic solverwill fail.

This field appears as a textbox labeled CalculatedPFD Avg. TheMeridiumAPM system calculates thisnumber automatically anddisplays it as read-only inthis cell.


CalculatedPHF

Number A number rep-resenting thecalculated prob-ability of failureper hour for thelogic solver.

This field appears as a textbox labeled CalculatedPHF. TheMeridiumAPMsystem calculates this num-ber automatically and dis-plays it as read-only in thiscell.


CalculatedSTR

Number A number rep-resenting thespurious triprate for thelogic solver.

This field appears as a textbox labeled CalculatedSTR. TheMeridiumAPMsystem calculates this num-ber automatically and dis-plays it as read-only in thiscell.


Description Character A brief descrip-tion of the logicsolver.

You can type a value dir-ectly into the Descriptioncell.




Field Cap-tion


Equipment Character The Record IDof the Equip-ment record towhich the Pro-tective Instru-ment LoopLogic Solverrecord is linked.

This field contains anbutton, which you can clickto search for the desiredEquipment record.


Exida Name Character The name ofthe logic solverdevice.

This field appears as a textbox labeled Device Nameand is disabled. This valueis populated automatically.


FunctionalLocation

Character The Record IDof the Func-tional Locationrecord to whichthe ProtectiveInstrumentLoop LogicSolver record islinked.

Tthis field contains anbutton, which you can clickto search for the desiredFunctional Location record.


Logic SolverID

Character An ID for thelogic solver.

You can type a value dir-ectly into the LogicSolverID cell. This value isrequired andmust beunique.




Field Cap-tion


ManualEntry

Logical Indicateswhether youwill enter datain a ProtectiveInstrumentLoop LogicSolver Channelrecordmanu-ally or theMeridiumAPMsystemwill pop-ulate this valueautomatically.

This field appears as acheck box labeledManualEntry. If this value is True,the Add button in the Chan-nels/Modules section onthe Protective InstrumentLoop page is enabled. Youcan use the Add button toadd a Protective Instru-ment Logic Solver Channelrecord to the ProtectiveInstrument Loop. If thisvalue is False, the Add but-ton is disabled.


MTTFS Number A number rep-resentingMeanTime To FailSafe for a logicsolver (i.e., theaverageamount of timebetween logicsolver failuresthat occur dur-ing safe scen-arios).

This field appears as a textbox labeledMTTFS. TheMeridiumAPM system cal-culates this number auto-matically and displays it asread-only in this cell. Thisvalue ismeasured in years.


MTTR Number A number rep-resentingMeanTime ToRepair, or thetime it takes torepair the logicsolver after afailure is detec-ted.

You can type a number dir-ectly into theMTTR cell.The value that you entermust be between 4 and336.

Otherwise, an error mes-sage will appear. Thisvalue is required.




Field Cap-tion


Proof TestCoverage

Number A number rep-resenting thepercentage offailures that aredetected by theproof test (i.e.,how effectivelythe proof testidentifies fail-ures). Forexample, 100%proof test cov-erage indicatesthat the prooftest wouldidentify 100%of the failuresthat occurred.

You can type a number dir-ectly into the Proof TestCoverage cell. The num-ber that you enter must bebetween 0 and 100.

Otherwise, an error mes-sage will appear. Thisvalue is required.


Proof TestInterval

Number A number rep-resenting themonthlyinterevals atwhich the prooftest should beperformed.

You can type a number dir-ectly into the Proof TestInterval cell. The numberthat you enter must bebetween 1 and 360, or anerror message will appear.This value is required.




Field Cap-tion


ReferenceData Date

Date The date onwhich that thereference datawas publishedfor the devicethat is identifiedin the ExidaName field.

This field appears as a textbox labeled ReferenceData Date and displays theCalendar feature.

When the value in theManual Entry field is True,this field is enabled, andyou can select a datemanu-ally. When the value in theManual Entry field is False,this value is disabled andpopulated automaticallywith the date on which thereference data was pub-lished for the device that isidentified in the ExidaName field.

Failure Data Refer-ence tab

ReferenceData Refer-ence

Character The specific fail-ure data ref-erence as itappears in theExida datasource that isidentified in theReferenceData Sourcefield.

This field appears as a textbox labeled ReferenceData Reference.

When the value in theManual Entry field is True,this value is enabled, andyou can type a value dir-ectly into the ReferenceData Reference cell.

When the value in theManual Entry field is False,this field is populated auto-matically with the data ref-erence for the device that isidentified in the ExidaName field and displayedas read-only in this cell.




Field Cap-tion


ReferenceData Revi-sion

Character A number thatrepresents thenumber oftimes the ref-erence datahas beenrevised in theExida data-base.

This field appears as a textbox labeled ReferenceData Revision.

When the value in theManual Entry field is True,this value is enabled, andyou can type a value dir-ectly into the ReferenceData Revision cell.

When the value in theManual Entry field is False,this field is populated auto-matically with the data revi-sion for the deviceidentified in the ExidaName field and is displayedas read-only in this cell.


ReferenceData Source

Character The source ofthe referencedata (e.g.,Exida).

This field appears as a textbox labeled ReferenceData Source.

When the value in theManual Entry field is True,this value is enabled, andyou can type a value dir-ectly into the ReferenceData Source cell.

When the value in theManual Entry field is False,this field is populated auto-matically with the datasource for the device iden-tified in the Exida Namefield and is displayed asread-only in this cell.




Field Cap-tion


SIL Archi-tectural Con-straints

Number A number thatrepresents theSIL value forthe logic solver,which is basedon the archi-tectural con-straints that aredefined in theTest Archi-tecture Con-straints field.

This field appears as a textbox labeled SIL Archi-tectural Constriants. TheMeridiumAPM system cal-culates this number auto-matically and displays it asread-only in this cell.




Field Cap-tion


SIL Sys-tematic Cap-ability

Number A number thatrepresents theSIL value forthe logic solverwhich is basedon the sys-tematic cap-abilities that aredefined in thefailure ratedata.

This field appears as a textbox labaled SIL Sys-tematic Capabilities and isenabled or disabled basedupon the following criteria:

l When the value in theManual Entry field isTrue, the SIL SytematicCapabilities field isenabled, and you canttype a value directly intothe SIL SystematicCapabilities cell.

l When the value in theManual Entry field isFalse, theMeridiumAPM system calculatesthe number auto-matically, based on thesystematic capabilitiesthat are defined in thefailure rate data asso-ciated with the logicsolver device, and dis-plays one of the fol-lowing values as read-only in the SIL Sys-tematic Capability field:o 0 (zero)o 1o 2o 3o 4


Safety Instrumented System


Safety Instrumented SystemSafety Instrumented System records store details about the safety instrumented system they rep-resent. The following table provides an alphabetical list and description of the fields that exist forthe Safety Instrumented System family and appear on the Safety Instrumented System data-sheet, unless otherwise specified. The information in this table reflects the baseline state andbehavior of these fields. This list is not comprehensive.

Field Caption DataType Description Behavior and Usage

Abnormal ModeDescription

Text A detailed description ofthe abnormalmode ofoperation.

On the datasheet, this fieldappears as a text box labeledAbnormal Mode Descrip-tion and contains a but-ton, which you can click toaccess the Text Editor. Thisfield is enabled only ifABNORMAL is selected inthe Operation Modes list.Otherwise, this field is dis-abled.

Abnormal State Character A short description of thespecific abnormal state ofthe operation.

On the datasheet, this fieldappears as a list labeledAbnormal State and con-tains the following values:

l Start-Up

l Shutdown

l Bypass

l Maintenance

l Emergency

l Other

This field is enabled andrequired only if ABNORMALis selected in the Plant Oper-ation Mode list. Otherwise,this field is disabled.




CommunicationLinks

Character The type of com-munication link that existsbetween componentswithin the logic solverand any other networkdevice. For example, Eth-ernet.

On the datasheet, this fieldappears as a text box labeledCommunication Links, inwhich you can enter yourown value.

Is Default SIS Logical Indicateswhether theSafety Instrumented Sys-tem record is the default.

This field does not appear onthe datasheet by default.

Last ModifiedBy

Character The name of the userwho last modified therecord.

On the datasheet, this field isdisabled and updated auto-matically whenever therecord ismodified.

Last ModifiedDate

Date The date on which therecord was last modified.

On the datasheet, this field isdisabled and populated auto-matically.

Logic Solver ID Character The ID for the logic solverthat is associated withthe safety instrumentedsystem.

On the datasheet, this fieldappears as a text box labeledLogic Solver ID, in whichyou can type your own value.This value should cor-respond to the value storedin the Logic Solver ID field inthe Protective InstrumentLoop Logic Solver recordthat represents the desiredlogic solver.

Logic SolverType

Character The type of logic solver. On the datasheet, this fieldappears as a list labeledLogic Solver Type and con-tains the following baselineSystemCodes in theMI_LOGIC_SOLVER_TYPESystemCode Table :

l PLC

l BPCS

l Relay




Long Descrip-tion

Text A statement describingthe purpose of the safetyinstrumented system.

On the datasheet, this fieldappears as a text box labeledLong Description and con-tains a button, which youcan click to access the TextEditor.

Manual Shut-down Descrip-tion

Text A description of themethod bywhich thesafety instrumented sys-tem can bemanually shutdown.

On the datasheet, this fieldappears as a text box labeledManual Shutdown Descrip-tion and contains a but-ton, which you can click toaccess the Text Editor.

Mission Time Number A numeric value in yearsthat represents the timethat the safety instru-mented systemwill be inuse before it is replacedor remanufactured.

On the datasheet, this fieldappears as a text box labeledMission Timewith an addi-tional label,Years, to the rightof the text box. You can enteryour own value directly in theMission Time cell. Thisvalue should be equal to orgreater than the length oftime specified in the TargetSIS Test Interval field.

OperationMode

Character Themode of operationfor the safety instru-mented system.

On the datasheet ,this fieldappears as a listlabeled Plant OperationMode and contains the fol-lowing values:

l NORMAL: This is thevalue that is selected bydefault.

l ABNORMAL: If youselect this value, the fol-lowing fields are enabled:

l Abnormal State

l AbnormalModeDescription




Plant ID Character The ID of the plant inwhich the safety instru-mented system exists.


Power Source Character A description of thepower supply to thesafety instrumented sys-tem.

On the datasheet, this fieldappears as a text box labeledPower Source, in which youcan enter your own value.

Reset Pro-cedure

Text A description of themethod bywhich thesafety instrumented sys-tem can be reset.

On the datasheet, this fieldappears as a text box labeledReset Procedure and con-tains a button, which youcan click to access the TextEditor.

SIS Description Character A description for thesafety instrumented sys-tem.

On the datasheet, this fieldappears as a text box labeledSIS Description, in whichyou can enter your ownvalue.

SIS ID Character A name for the safetyinstrumented system.

On the datasheet, this fieldappears as a text box labeledSIS ID, in which you canenter your own value. Thisfield is required, and a ruleexists on the field that checksto see if the value that youenter is unique. If the valuethat you enter is already spe-cified for an existing SafetyInstrumented System record,amessage will appear, indic-ating that the value is alreadyin use. You will need to spe-cify a different value beforeyou can save the record.

Site Descrip-tion

Character A description of the sitethat is specified in theSite ID field.





Site ID Character The ID of the Site recordassociated with thesafety instrumented sys-tem.

On the datasheet, this field isdisabled and populated auto-matically with the valuestored in the Site ID field inthe associated SIL Analysisrecord. You should notmodify this value.

Target SIS TestInterval

Number A number that rep-resents the interval inmonths bywhich regulartesting will be performedon the safety instru-mented system.

On the datasheet, this fieldappears as a text box labeledTarget SIS Test Interval, inwhich you can enter yourown value.

Unit Descrip-tion

Character A description of the unitspecified in the Unit IDfield.


Unit ID Character A description of the areain which the safety instru-mented system exists.

On the datasheet, this fieldappears as a text box labeledUnit ID, in which you canenter your own value.

SIF CommonCause Failure


SIF Common Cause FailureSIF CommonCause Failure records store details about a failure or a condition within a plant thatcan affect the operation of multiple instrumented functions (i.e., common cause failures). The fol-lowing table provides an alphabetical list and description of the fields that exist for the SIF Com-monCause Failure family and appear on the SIF CommonCause Failures datasheet. Theinformation in the table reflects the baseline state and behavior of these fields.

Field Cap-tion Data Type Description Behavior and Usage

CCFDescription

Text The description of the com-mon cause failure.

This field is required. On the SIFCommonCause Failure datasheet,you can click the button to

define this valuemanually via theCCF Description dialog box.

CCF ID Character The ID for the commoncause failure.

This field is required. On the Com-mon Cause Failures tab on the<Record ID> (Instrumented Func-tion) window, this value appears asa hyperlink, which you can click toview the contents of the cor-responding SIF CommonCauseFailure record in a new window.

CCF Mit-igation

Text A brief description of waystomitigate the effect of thecommon cause failure.

This field is required. On the SIFCommonCause Failure datasheet,you can click the button to

define this valuemanually via theCCF Mitigation dialog box.

SIL Analysis


SIL AnalysisSIL Analysis records store details about an SIL Analysis. The following table provides an alpha-betical list and description of the fields that exist for the SIL Analysis family. The information in thistable reflects the baseline state and behavior of these fields. This list is not comprehensive.

Note: The field captions that are displayed in the following tablemay differ from the datasheetcaptions.


AnalysisDescription

Character A brief descriptionfor the SIL Ana-lysis.


SIL Analysis tabon the SIL Ana-lysis datasheet

Analysis EndDate

Date The date on whichthe SIL Analysiswill end.

You can type or selectthe desired date. Thestart datemust be laterthan the date in the Ana-lysis Start Date field, oran error message willappear.

When you copy a SILAnalysis record, thevalue in this field isnotcopied to the newrecord.


SIL Analysis



Analysis ID Character The ID for the SILAnalysis.

You can type your ownvaluemanually. Thisfield is required, and thevalue you enter must beunique with respect tothe Analysis ID in otherSIL Analysis records.Note that if you open anexisting SIL Analysisrecord and delete thevalue in the Analysis IDfield, if you then retypethat same value and tryto save the record, anerror message willappear indicating thatthe Analysis ID alreadyexists.


SIL Analysis



Analysis Re-evaluation

Number A number indic-ating how manyyears after thecompletion of theHazards Analysisthat is associatedwith the SIL Ana-lysis that the Haz-ards Analysisshould be re-eval-uated.

On the datasheet, thisfield appears as a textbox that is labeled Haz-ards Next Ree-valuation Interval withan additional label,Years, to the right of thetext box. If the SIL Ana-lysis record is linked to aHazards Analysisrecord, this field is pop-ulated automaticallywith the value in the Ree-valuation Interval field inthe Hazards Analysisrecord that is linked tothe SIL Analysis record.

If the SIL Analysisrecord is not linked to aHazards Analysisrecord, this field isenabled and you canpopulate it manually.


Analysis StartDate

Date The date on whichthe SIL Analysiswill begin.

You can type or selectthe desired date. Theanalysis end datemustbe earlier than the datein the Analysis StartDate field, or an errormessage will appear.

When you copy an SILAnalysis record, thisfield is populated auto-matically with the cur-rent date.


SIL Analysis



Equipment ID Character The ID for theEquipment recordthat is linked to theSIL Analysis.

On the datasheet, thisfield is disabled and con-tains a button, whichyou can click to searchfor an existing Equip-ment record to link to theSIL Analysis record.After you select anEquipment record, theEquipment ID field ispopulated automaticallywith the ID stored in thecorresponding Equip-ment record.

The Equipment ID valueappears as a hyperlink,which displays in a newwindow the Equipmentrecord with that ID. Theselected Equipmentrecord should representthe equipment for whichthe SIS exists to mit-igate the risk of failureon that equipment.

When you copy an SILAnalysis record, thevalue in this field is notcopied.


EquipmentKey Number The Entity Key ofthe Equipmentrecord that islinked to the SILAnalysis record.

This field does notappear on the SIL Ana-lysis datasheet bydefault.

None

SIL Analysis



Facilitator Character The name of theSIL Analysis teammember who isspecified as theFacilitator on theSIL AnalysisTeam page.


None

FunctionalLocation ID

Character The ID for theFunctional Loca-tion record that islinked to the SILAnalysis record.

On the datasheet, thisfield is disabled and con-tains a button, whichyou can click to searchfor an existing Func-tional Location record tolink to the SIL Analysisrecord. After you selecta Functional Locationrecord, the FunctionalLocation ID field is pop-ulated automaticallywith the ID from the cor-responding FunctionalLocation record.

The Functional LocationID appears as a hyper-link, which displays in anew window the Func-tional Location recordwith that ID. The selec-ted Functional Locationrecord should representthe location for whichthe SIS exists to mit-igate the risk of failureon that location.

When you copy an SILAnalysis record, thevalue in this field is notcopied.


SIL Analysis



FunctionalLocation Key

Number The Entity Key ofthe FunctionalLocation recordthat is linked to theSIL Analysisrecord.


None

Hazards Ana-lysis Date

Date The value thatexists in the LastModified Date fieldin the HazardsAnalysis recordwhose record IDappears in theHazards AnalysisReference field.

If the SIL Analysisrecord is linked to a Haz-ards Analysis record,this field is populatedautomatically with thevalue in the Last Modi-fied Date field in thatHazards Analysisrecord. If the SIL Ana-lysis record is not linkedto a Hazards Analysisrecord, this field isenabled, and you canpopulate it manually.


SIL Analysis



Hazards Ana-lysis Refer-ence

Character The ID of the Haz-ards Analysisrecord that islinked to the SILAnalysis record.

On the datasheet, thisfield is disabled and con-tains a button, whichyou can click to searchfor an existing HazardsAnalysis record to link tothe SIL Analysis record.After you select the Haz-ards Analysis record,the Hazards AnalysisReference field is pop-ulated automaticallywith the Record ID fromthe corresponding Haz-ards Analysis record.

The Hazards AnalysisID appears as a hyper-link, which opens in anew window the Haz-ards Analysis recordwith that ID.

Note: In order to linka Hazards Analysisrecord to an SIL Ana-lysis record, youmusthave at least View priv-ileges to the HazardsAnalysis family.


Hazards Ana-lysis Refer-ence Key

Number The Entity Key forthe Hazards Ana-lysis record that islinked to the SILAnalysis record.


None

SIL Analysis



Hazards Ana-lysis Revision

Character The numeric valuethat exists in theRevision Numberfield in the Haz-ards Analysisrecord whoseRecord IDappears in theHazards AnalysisReference field.

If the SIL Analysis islinked to a Hazards Ana-lysis record, this field ispopulated automaticallywith the value in theRevision Number field inthat Hazards Analysisrecord. If the SIL Ana-lysis record is not linkedto a Hazards Analysisrecord, this field isenabled, and you canpopulate it manually.


Hazards Ree-valuation Date

Date The date on whichthe Hazards Ana-lysis that is asso-ciated with the SILAnalysis should bere-evaluated.

This field is populatedautomatically with theoutput of the followingcalculation:

Hazards ReevaluationDate = Hazards Ana-lysis Date + AnalysisRe-evaluation

If the SIL Analysisrecord is not linked to aHazards Analysisrecord (i.e., the recordfromwhich the values inthe calculation shownabove aremapped), thisfield is enabled, and youcan populate itmanually.

On the datasheet, thisfield is labeled HAZOPSReevaluation Date.


SIL Analysis



HAZOP State Character The current stateof the HazardsAnalysis recordthat is linked to theSIL Analysisrecord.

If the SIL Analysisrecord is linked to a Haz-ards Analysis record,this field is populatedautomatically with thestate of that HazardsAnalysis record. If theSIL Analysis record isnot linked to a HazardsAnalysis record, thisfield is enabled, and youcan populate itmanually.


Is Deleted Logical Specifies whetherthe SIL Analysisrecord has beenremoved from theSIL AnalysisSearch page.

The value in this field isused by theMeridiumAPM system. Youshould not modify thisvalue. This field doesnot appear on the SILAnalysis datasheet bydefault.

None

Last ModifiedBy

Character The name of theMeridiumAPMSecurity User wholast modified therecord.

This field is disabled andpopulated automaticallywith the name of theuser who was logged inwhen the record waslast modified. When youcopy an SIL Analysisrecord, the value in thisfield is notcopied.


Last ModifiedDate

Date The date on whichthe record waslast modified.

This field is disabled andpopulated automatically.When you copy an SILAnalysis record, thevalue in this field isnotcopied.


SIL Analysis



Long Descrip-tion

Text A detailed explan-ation of the SILAnalysis that youwant to conduct.

On the datasheet, thisfield contains a but-ton, which you can clickto access the TextEditor.


Loss of SISEnergySources

Text A description ofhow the safetyinstrumented sys-tem responds to aloss of energy.

On the datasheet, thefield appears as a textbox labeled Loss ofEnergy Sources, andthe value is set bydefault. You can removethe default text and typeyour own values. Thisfield contains a but-ton, which you can clickto view the Text Editor.

General SISRequirementstab on the SILAnalysis data-sheet

Normal Oper-ation Require-ment

Text A description ofthe requirementsfor the normalmode of the instru-mented function.

The value in this field isset by default. You canremove the defaultvalue and type your ownvalues. This field con-tains a button, whichyou can click to view theText Editor.

Safety Require-ment Spe-cifications tabon the SIL Ana-lysis datasheet

Owner Character The name of theSIL Analysis teammember who isspecified as theProcessOwner onthe SIL AnalysisTeam Memberspage.

This field is disabled andpopulated automaticallywith the first and lastname of the teammem-ber as it appears in theFirst Name and LastName fields in the user'sHumanResourcerecord.


SIL Analysis



ProcessOwner

Character The name of theSIL Analysis teammember who isspecified as theProcessOwner onthe SIL AnalysisTeam Memberspage.

This value is used to pop-ulate the Owner fieldand does not appear onthe SIL Analysis data-sheet by default.

None

Requirementfor SRSReview

Text A description ofthe requirementfor the safetyrequirementreview.

The value in this field isset by default. You canremove the defaultvalue and type your ownvalues. This field con-tains a button, whichyou can click to view theText Editor.


SIF BypassRequirements

Text A description ofthe bypass require-ments for theinstrumented func-tion.

The value in this field isset by default. You canremove the defaultvalue and type your ownvalues. This field con-tains a button, whichyou can click to accessthe Text Editor.

General SIFRequirementstab on the SILAnalysis data-sheet

SIF CommonCauseSources

Text A description ofthe sources forcommon cause fail-ures in instru-mented functions.



SIL Analysis



SIF DemandMode of oper-ation

Text A description ofthe demandmodeassociated with aninstrumented func-tion.



SIF Dia-gnostics

Text A description ofcomponent dia-gnostics for aninstrumented func-tion.



EmergencyRequirement

Text A description ofthe requirementfor an instru-mented function inthe case of emer-gency.



SIF FailureModes

Text A description ofthe configurationof instrumentedfunction failuremodes.



SIL Analysis



SIF ManualShutdown

Text A description ofthemanual shut-down operationfor an instru-mented function.



SIF Main-tenance Over-rides

Text A description ofthemanual over-ride proceduresneeded for main-tenance on aninstrumented func-tion.



SIF Pre-Alarms

Text A description ofthe pre-alarms foran instrumentedfunction.



SIF ProcessInterfaces

Text A description ofprocess interfacesfor instrumentedfunctions.



SIL Analysis



SIF Proof TestProcedures

Text A detailed descrip-tion of the prooftest proceduresassociated with aninstrumented func-tion.



SIF ProtectionMode

Text A description ofthe way in whichthe instrumentedfunction willrespond in pro-tectionmode.



SIF Regu-lations andStandards

Text A description of allthe regulationsand standardsassociated with aninstrumented func-tion.



SIF SpuriousTrip Rate

Txt A description ofthe acceptablespurious trip ratefor an instru-mented function.



SIL Analysis



SIF Trip Reset Text A description ofthe reset pro-cedures in thecase of a trippedinstrumented func-tion.



SIS DesignRequirements

Text A description ofthe design require-ments for thesafety instru-mented system.



SIS ElectricalPower

Text A description ofthe specific elec-trical requirementsfor the safetyinstrumented sys-tem.



SIS Envir-onmentalConditions

Text A description ofthe environmentaloperating con-ditions of thesafety instru-mented system.



SIL Analysis



SIS Interfaces Text A description ofthe interfaces forthe safety instru-mented system.



Logic SolverFailureResponse

Text A description ofhow the logicsolver responds toa failure.



SIS Sequenceof EventsRecording

Text A description ofsequence of eventrecordings thatexist for the safetyinstrumented sys-tem.

This field is populatedautomatically. You canremove the defaultvalue and type your ownvalues if needed. On thedatasheet, the SISSequence of EventsRecordingtext box con-tains a button, whichyou can click to accessthe Text Editor.


SIS SoftwareRequirements

Text A description ofthe software pro-graming lan-guages that arepermitted for use.

This field is populatedautomatically. You canremove the defaultvalue and type your ownvalues if needed. On thedatasheet, the SIS Soft-ware Requirementstext box contains abutton, which you canclick to access the TextEditor.


SIL Analysis



Site Descrip-tion

Character A description ofthe site specifiedin the Site ID field.


None

Site ID Character The ID of the siteassociated withthe SIL Analysis.

On the datasheet, thisfield appears as a listlabeled Site ID and con-tains IDs for existingSite Reference recordsas they appear in theName field in the asso-ciated Site Referencerecord. The record thatyou select here is usedto identify which riskmat-rix to display when youcreate Risk Assessmentrecords in SIS Man-agement. If this field isempty, the default riskmatrix will be used.

SIL Analysistab on the SILAnalysis data-sheet

SRS Meth-odology

Text A long descriptionof themeth-odology for theSafety Require-ment Specificationreport.



SRS Purposeand Scope

Text A long descriptionof the purpose andscope of theSafety Require-ment Specificationreport for the SILAnalysis.



SIL Analysis



SRS Stand-ards Use

Text A description ofthe standards thatare used withinthe SafetyRequirement Spe-cification report.



System Defin-ition

Text A description ofthe safety instru-mented system.



Unit Descrip-tion

Character Adescription of theunit that is spe-cified in the Unit IDfield.


None

Unit ID Character The ID for the unitwhere the safetyinstrumented sys-tem for which youare conducting theSIL Analysisexists.

On the datasheet, thisfield appears as a textbox labeled Unit ID, inwhich you can type yourown value.


SIS Proof Test


SIS Proof TestSIS Proof Test records store details about a proof test that is executed, including the results ofthe proof test. The following table provides an alphabetical list and description of the fields thatexist for the SIS Proof Test family and appear on the SIS Proof Test datasheet, unless otherwisespecified. The information in the table reflects the baseline state and behavior of these fields.


Cleared AllBypasses andForced Logic

Logical Indicateswhether or not youhave cleared all bypasses andforced logic while performingthe proof test.

On the datasheet, thisfield appears as acheck box labeledCleared AllBypasses andForced Logic, whichyou can select to spe-cify that you havecleared all bypassesand forced logic whileperforming the prooftest.

CommencementDate

Date The date on which you beganperforming the proof test.

On the datasheet, thisfield appears as a textbox, where you cantype or select thedesired date and time.

CompletionDate

Date The date on which you com-pleted the proof test.

On the datasheet, thisfield appears as a textbox, where you cantype or select thedesired date and time.

SIS Proof Test



Equipment Oper-ating State

Character The current state of the equip-ment that you are testing.

On the datasheet, thisfield appears as a listlabeled EquipmentOperating State andcontains the SystemCodes that exist in theMI_EQUIP_OP_STATE SystemCodeTable. You canchoose from the fol-lowing baseline val-ues:

l On-Line (ON-LINE)

l Off-Line (OFF-LINE)

l Not Applicable(NA)

Functional TestClosed

Logical A value that indicateswhetheror not the proof test has beencompleted.

On the datasheet, thisfield appears as acheck box labeledFunctional TestClosed, which youcan select to specifythat you are finishedwith the proof test,meaning it is closed.When you select thischeck box, all fields onthe SIS Proof Testdatasheet become dis-abled automatically.

SIS Proof Test



Functional TestStatus

Character Stores the current status of theproof test.

On the datasheet, thisfield appears as a listlabeled FunctionalTest Status and con-tains the SystemCodes that exist in theMI_FUNCTIONAL_TEST_STATUS Sys-temCode Table. Youcan choose from thefollowing baseline val-ues:

l Active

l Complete

l Closed

Functional TestTemplate

Character The Record ID of the SIS ProofTest Template record that wasused to create the SIS ProofTest record.

On the datasheet, thisfield appears as a listlabeled FunctionalTest Template andcontains a list ofRecord IDs for theexisting SIS ProofTest Templaterecords. When youcreate an SIS ProofTest record, this fieldis required. After youselect an SIS ProofTest record in the listand save the record,the field is disabled.

SIS Proof Test



SIS TesterName

Character The name of the user who isresponsible for performing theproof test.

On the datasheet, thisfield appears as a listlabeled SIS TesterName and containsthe names of the:

l Security User whocreated the SISProof Test record.

-and-

l Members of theMISIS Administrator,MI SIS Engineer,or MI SIS UserSecurity Groups.

Task Addressed Number The Record ID of the Inspec-tion Task record that isaddressed by the proof test.

On the datasheet, thisfield appears as a listlabeled TaskAddressed and con-tains the Record IDsof the Inspection Taskrecords that are linkedto the InstrumentedFunction record orSafety InstrumentedSystem record towhich the SIS ProofTest record is linked.

Test Description Character A description of the proof test. On the datasheet, thisfield appears as a textbox labeled TestDescription, in whichyou can enter yourown value.

Test ID Character The ID for the proof test. On the datasheet, thisfield appears as a textbox labeled Test ID,in which you can enteryour own value.

SIS Proof Test



Test Summary Text A summary of the proof testthat was performed.

On the datasheet, thisfield appears as a textbox labeled Test Sum-mary and contains a

button, which youcan click to access theText Editor.

Type of Test Character The type of proof test that youperformed.

On the datasheet, thisfield appears as a listlabeled Type of Testand contains the fol-lowing baseline val-ues:

l Functional Test

l SystemValidation

SIS Or PIF Key Number The Entity Key of the Instru-mented Function record orSafety Instrumented Systemrecord to which the SIS ProofTest record is linked.

This field does notappear on the data-sheet by default.

SIS Proof Test Template


SIS Proof Test TemplateThe following table provides a list of the fields that exist in the SIS Proof Test Template family.

Field Cap-tion


Author Character The name of the user whodefined the proof test.

On the datasheet, this fieldappears as a list labeledAuthor and contains thenames of users who have anassociated HumanResourcerecord in theMeridiumAPMdatabase.When you createan SIS Proof Test Templaterecord, by default, this fieldcontains the name of the userwho is currently logged.

ModifiedBy

Character The name of the user whowas logged in when the SISProof Test Template recordwas last modified.


ModifiedDate

Date The date on which the SISProof Test Template recordwas last modified.


Pre-TestConditions

Text A description of the requiredconditions of the equipmentor system onwhich the prooftest will be performed.

On the datasheet, this fieldappears as a text box labeledPre-Test Conditions and con-tains a button, which youcan click to access the TextEditor.

TemplateDescription

Character A brief description of theproof test.

On the datasheet, this fieldappears as a text box labeledTemplate Description, inwhich you can enter your ownvalue.

SIS Proof Test Template


Field Cap-tion


TemplateID

Character The ID for the proof test tem-plate.

On the datasheet, this fieldappears as a text box labeledTemplate ID, in which youcan enter your own value.When you create an SISProof Test Template record,this field is populated auto-matically withPPTand the cur-rent date and time. You canremove the default value andenter your own value directlyin theTemplate ID cell.

SIS Proof Test Template Detail


SIS Proof Test Template DetailThe following table provides a list of the fields that exist in the SIS Proof Test Template Detail fam-ily. This list is not comprehensive.

Field Cap-tion


EquipmentID

Character The Record ID of the Equip-ment record against whichthe step should be per-formed.

You can select the associatedEquipment record by clickingthe in the Equipment IDfield.

LocationID

Character The Record ID of the Func-tional Location recordagainst which the stepshould be performed.

You can select the associatedFunctional Location record byclicking the in the LocationID field.

Result Cri-teria

Text A description of what is con-sidered to be an acceptableresult of the step.

None

StepSequenceNumber

Number A number that representsthe order in which the stepshould be performed, rel-ative to other steps.

When you create a new SISProof Test Template Detailrecord this value is set auto-matically based upon the val-ues in existing SIS Proof TestTemplate Detail records. Youcanmodify this valuemanuallyin both new and existingrecords.

Step Type Character The type of step. On the datasheet, you canselect the step type from a listof the following options:

l Pretest Setup

l Sensor

l Logic Solver

l Final Element

l Post Test Procedure

TemplateDetail ID

Character An alphanumeric value thatidentifies the SIS Proof TestTemplate Detail record.

None

SIS Proof Test Template Detail


Field Cap-tion


TravelTime Limit

Number A number that quantifies themaximumacceptable traveltime for this step, inseconds.

This field is enabled only in SISProof Test Template Detailrecords that are linked torecords representing final ele-ments.

Trip Point Number A number that defineswhenthe element will activate anSIS shutdown.

This field is enabled only in SISProof Test Template Detailrecords that are linked torecords representing sensors,final elements, or logic solvers.

Trip PointDirection

Character The trend of Trip Point val-ues.


Trip PointError Limit

Number A value that defines therange, plus or minus, withinwhich the Trip Point valuemust fall to be acceptable.


Trip PointUnits

Character The unit of measure asso-ciated with the value in theTrip Point field.

This field is populated with a listof SystemCodes that exist inthe UOME SystemCode table.This field is enabled only inSISProof Test Template Detailrecords that are linked torecords representingsensors,final elements, or logic solvers.

System Code Tables Used by SIS Management


System Code Tables Used by SIS ManagementThe following table provides and alphabetical list and description of the SystemCode Tables thatare used by the SIS Management module. This list is not comprehensive.

SystemCode TableDescription

SystemCodeTable ID Notes

LOPA IPL TYPE MI_IPL_TYPE Used to populate the Type field in IndependentLayer of Protection records.

SIL AssessmentMethod

MI_SIL_ASSESSMENT_METHOD

Used to populate the SIL Assessment Methodfield in Instrumented Function records.

SIL FinalElement VoteMI_SIL_FINALELEMVOTE

Used to populate the Voting field in ProtectiveInstrument LoopGroup recordswhen thegroup type is Final Element.

SIL Sensor VoteMI_SIL_SENSORVOTE

Used to populate the Voting field in ProtectiveInstrument LoopGroup recordswhen thegroup type is Sensor.

Unit of Measure UOME Used to populate Trip Point Units field in SISProof Test Template Detail record.

Parameters for the SIS Management URL


Parameters for the SIS Management URLThere is one root URL associated with SIS Management: meridium://SIS. A link constructedfrom the path alone will open the SIS Management Start Page. In addition, you can use any ofthe parameters described in the following table.



ParameterName Description Accepted Value(s) Notes

Page Specifies thepage that youwant to view.

Search

Definition

Team

Documents

SIS

PIF

SILValidation

SILValidationView

LopaDefinition

LopaModifiers

HealthIndicator

PTTemplateList

ProofTestList

ReferenceDataList

ReferenceData

Admin

The Page parameter isrequired.

Displays the <Family> Searchpage, where <Family>specifiesthe family of the records forwhich you can search using thepage (e.g.,Protective LoopSearchpage). The family isdetermined by theModule orAnalysisType parameter value.

If noModule or AnalysisTypeparameter is provided in theURL, SIL Analysis Searchpage will be displayed.

Displays a new or existingrecord on the <Family> Defin-itionpage, where<Family>spe-cifies the family to which therecord belongs. The family isdetermined by theModule orAnalysisType parameter.

If the EntyKey parameter isincluded in the URL, the pagewill display the existing recordwith the specified Entity Key. If,however, the EntyKey para-meter is omitted from the URL,the page will display anewrecord in the family iden-tified by theModule or Ana-lysisType parameter value.2

If noModule or AnalysisTypeparameter is provided in theURL, you will need to provideadditional parameters to...

l Specify to relationshipbetween the record youare creating and therecord to which it will belinked.




l Specify the record thatyou want to modify byidentifying the record towhich it is linked.

For details on these para-meters, see the notes for theModule and AnalysisType para-meters.

Displays the TeamMemberspage for the SIL Ana-lysis that is specified by theEntyKey parameter. If the Teamparameter is included, theEntyKey parameter is required.

Displays the Reference Docu-mentspage for the SIL Analysisspecified by the EntyKey para-meter. If the Documents para-meter is included, the EntyKeyparameter is required.

Displays the SafetyInstru-mented Systemspage for theSIL Analysis that is specified bythe EntyKey parameter. If theSIS parameter is included, theEntyKey parameter is required.

Displays the InstrumentedFunctionspage for the SIL Ana-lysis that is specified by theEntyKey parameter. If the PIFparameter is included, theEntyKey parameter is required.

Displays on the ProtectiveInstrument Loop DiagramView page the Protective Instru-ment Loop record that is linkedto an Instrumented Functionrecord for an SIL Analysis.

When Page=SILValidation, the




following parameters arerequired:

l EntyKey: Specifies theEntityKey of the Pro-tective Instrument Looprecord that is displayed.

l AnalKey: Specifies theEntity Key of the SIL Ana-lysis record to which theInstrumented Functionrecord is linked.

l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the ProtectiveInstrument Loop record islinked.

Displays on the ProtectiveInstrument Loop Grid Viewpage the Protective InstrumentLoop record that is linked to anInstrumented Function recordfor an SIL Analysis.

When Page-e=SILValidationView, the fol-lowing parameters are required:

l EntyKey: Specifies theEntity Key of the Pro-tective Instrument Looprecord that is displayed.

l AnalKey: Specifies theEntity Key of the SIL Ana-lysis record to which theInstrumented Functionrecord is linked.

l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the ProtectiveInstrument Loop record is




linked.

Displays on the LOPA Defin-ition page the LOPA record thatis linked to an InstrumentedFunction record for an SIL Ana-lysis.

When Page=LopaDefinition,the following parameters arerequired:

l LopaKey: Specifies theEntity Key of the LOPArecord that is displayed.

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Instrumented Func-tion record is linked.

l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the LOPA recordis linked.

Displays on the ConsequenceModifiers page the Con-sequenceModifier records thatare linked to a LOPA record thatis linked to an InstrumentedFunction for an SIL Analysis.

When Page=LopaModifiers, thefollowing parameters arerequired:

l LopaKey: Specifies theEntity Key of the LOPArecord that is displayed.

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Instrumented Func-tion record is linked.




l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the LOPA recordis linked.

Displays on the SIS - AssetHealth Manager page theHealth Indicator record for anSIL Analysis.

When Page=HealthIndicators,the following parameters arerequired:

l EntyKey: The Entity Keyof the Health Indicatorrecord that is displayed.

l AnalysisKey: The EntityKey of the SIL Analysisrecord to which theHealth Indicator record islinked.

Displays on the Proof Test Tem-plates page the SIS Proof TestTemplate records that arelinked to a Safety InstrumentedSystem record or InstrumentedFunction record for an SIL Ana-lysis.

When Page=PTTemplateList,the following parameters arerequired:

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Safety InstrumentedSystem record or Instru-mented Function recordis linked.

l SISKey: Specifies theEntity Key of the Safety




Instrumented Systemrecord to which the SISProof Test Templaterecords are linked.

-OR-

PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the SIS ProofTest Template recordsare linked.

Displays on the Proof Testspage the SIS Proof Testrecords that are linked to aSafety Instrumented Systemrecord or Instrumented Func-tion record for an SIL Analysis.

When Page=ProofTestList, thefollowing parameters arerequired:

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Safety InstrumentedSystem record or Instru-mented Function recordis linked.

l SISKey: Specifies theEntity Key of the SafetyInstrumented Systemrecord to which the SISProof Test records arelinked.

-OR-

PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the SIS ProofTest records are linked.




Displays the <Family> Refer-ence Data Search page, where<Family> specifies the family ofthe Reference Data records forwhich you can search using thepage (e.g., Logic Solver Refer-ence Data Search page). Thefamily is determined by the Typeparameter value.

When Page-e=ReferenceDateList, the Typeparameter is required.

Displays a new or existingrecord on the <Family> Refer-ence Data page, where <Fam-ily> specifies the family to whichthe record belongs. The familyis determined by the Type para-meter value.

If the EntyKey parameter isincluded in the URL, the pagewill display the existing recordwith the specified Entity Key. If,however, the EntyKey para-meter is omitted from the URL,the page will display a newrecord in the family identified bythe Type parameter value.

If no Type is provided in theURL, theSensor ReferenceDatapage will be displayed.

Displays the SIS ManagementAdministrationpage.

To see examples of URLs thatinclude these parameters, seethe topic Examples of SIS Man-agement URLs.




Module Specifies thefamily of therecords that youwant to view onthe page spe-cified by thePage para-meter.

SA

SV

SVTP

PTTemplate

ProofTest

Displays SIL Analysis recordson the page specified by thePage parameter value.

Displays Protective InstrumentLoop records on the page spe-cified by the Page parametervalue.

Displays Protective InstrumentLoop records that are specifiedas templates on the page spe-cified by the Page parametervalue.

Displays on the Proof Test Tem-plate Definition page a newSIS Proof Test Template recordthat will be linked to the Instru-mented Function record orSafety Instrumented Systemrecord for the SIL Analysis.

When Page=Definition andModule=PTTemplate, the fol-lowing parameters are required:

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Instrumented Func-tion record or SafetyInstrumented Systemrecord is linked.

l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the SIS ProofTest Template record willbe linked.

-OR-

SISKey:Specifies theEntity Key of the SafetyInstrumented System




record to which the SISProof Test Templaterecord will be linked.

Displays on the Proof TestDefinition page a new SISProof Test record that will belinked to the Instrumented Func-tion record or Safety Instru-mented System record for anSIL Analysis.

When Page=Definition andModule=ProofTest, the fol-lowing parameters are required:

l AnalysisKey: Specifiesthe Entity Key of the SILAnalysis record to whichthe Instrumented Func-tion or Safety Instru-mented System is linked.

l PIFKey: Specifies theEntity Key of the Instru-mented Function recordto which the SIS ProofTest record will be linked.

-OR-

SISKey:Specifies theEntity Key of the SafetyInstrumented Systemrecord to which the SISProof Test record will belinked.

To see examples of URLs thatinclude these parameters, seethe topic Examples of SIS Man-agement URLs.




AnalysisType Specifies thatyou want to viewrecords in theSIS Trip Reportfamily ratherthan records inthe SIL Analysisfamily.

SISTripReport The AnalysisType parameterLets you view records in the SISTrip Report family instead of thedefault SIL Analysis family.

You can use the AnalysisTypeparameter with any of the fol-lowing Page parameter valuesto specify that SIS Trip Reportrecords should be displayed onthose pages instead of SIL Ana-lysis records:

l Search

l Definition




EntyKey Specifies thespecific recordthat you want toview.

A numeric EntityKey

This parameter is required if:

l Page=Definition and youwant to view a specificrecord. You can use theModule parameter,EntyKey parameter orAnalysisType parameter.If you do not use theEntyKey parameter inthis case, a new recordwill appear according totheModule parametervalue. I you do not useone of these parameters,a new SIL Analysisrecord will appear on theSIL Analysis Definitionpage by default.

l Page=Team

l Page=Documents

l Page=SIS

l Page=PIF

l Page=SILValidation

l Page=SILValidationView

l Page=HealthIndicator

l Page=ReferenceDate

AnalysisKey Specifies theSIL Analysisrecord that islinked to therecords that youwant to view.

A numeric EntityKey


l Page=LopaDefinition

l Page=LopaModifiers

l Page=HealthIndicator

l Page=PTTemplateList

l Page=ProofTestList

l Module=ProofTest




PIF Key Specifies theInstrumentedFunction recordthat is linked tothe record thatyou want toview.

A numeric EntityKey

This parameter is required if youwant to view a specific Instru-mented Function record that islinked to another record spe-cified in the URL. This para-meter can be used with theAnalysisKey, AnalKey, orEntyKey parameters. If Mod-ule=PTTemplate or Mod-ule=ProofTest, the EntyKey,AnalysisKey, and PIF Key para-meters are required.

AnalKey Specifies theSIL Analysisrecord that islinked to therecords that youwant to view.

A numeric EntityKey

The AnalKey parameter isrequired if:

l Page=SILValdiation

l Page=SILValidationViewand EntyKey=<EntityKey value>

When you use the AnalKeyparameter, the PIFKey orSISKey parameter is required.You can use the PIFKey para-meter with the AnalysisKeyparameter, AnalKey parameter,or EntyKey parameter. Whereyou use the PIFKey parameterdepends upon the URL that youwant to construct.

SISKey Specifies theSafety Instru-mented Systemrecord that islinked to therecord that youwant to view.

A numericEntityKey value foran SIL Analysisrecord.

This parameter is required if youwant to view a specific recordthat is linked to a Safety Instru-mented System record and canbe used with the AnalysisKey,AnalKey, or EntyKey para-meters.




LopaKey Specifies theLOPA recordthat you want toview.

A numeric EntityKey


l Page=LopaDefinition

l Page=LopaModifiers

When you use the LopaKeyparameter, the AnalysisKey andPIFKey parameters arerequired. You can use thePIFKey parameter with the Ana-lysisKey parameter, AnalKeyparameter, or EntyKey para-meter. Where you use thePIFKey parameter dependsupon the URL that you want toconstruct.




Type Specifies therecords that youwant to view inthe ValidationReference Datafeature.

FinalElement

LogicSolver

Sensor

The Type parameter is requiredif Page=ReferenceDataList.

If Page=ReferenceData, youcan optionally use the followingType parameter values to viewa record in a family other thanthe default Sensor family:

l Final Element: DisplaysFinal Element records.

l Logic Solver: DisplaysLogic Solver records.

l Sensor: Displays Sensorrecords.

If Page=ReferenceData andyou omit the Type parameter, aSensor record will be displayedby default. If you include it, thevalue can be set to either Fin-alElement or LogicSolver.

In other words, omitting theType parameter when Page-e=ReferenceDate has thesame effect as setting it toSensor.

Note that if Page-e=ReferenceData and the Typeparameter is included, theEntyKey parameter is required.

Examples of SIS Management URLs


Examples of SIS Management URLsl meridium://SIS

Displays the SIS Management Start Page.

l meridium://SIS?Page=Search

Displays the SIL Analysis Search page.

l meridium://SIS?Page=Search & Module=SV

Displays the Protective Loop Search page.

l meridium://SIS?Page=Search & AnalysisType=SIS Trip Report

Displays the SIS Trip Report Search page.

l meridium://SIS? Page=Definition

Displays a new SIL Analysis record on theSIL Analysis Definition page.

l meridium://SIS?Page=Definition&Mod-ule=PTTemplate&AnalysisKey=123456&SISKey=789101

Displays on the Proof Test Template Definition page a new SIS Proof Test Templaterecord that will be linked to the Safety Instrumented System record with the Entity Key123456 that is linked to the SIL Analysis record with the Entity Key 789101.

l meridium://SIS?Page=LopaModifiers&Lo-paKey=123456&AnalysisKey=789101&PIFKey=111213

Displays in the Consequence Modifiers page list of ConsequenceModifier records thatare linked to the Instrumented Function record with the Entity Key 111213 that is linked tothe SIL Analysis record 789101.

l meridium://SIS?Page-e=SILValidation&EntyKey=123456&AnalKey=789101&PIFKey=111213

Displays the Protective Instrument Loop record with the Entity Key 123456 that is linked tothe Instrumented Function record with the Entity Key 111213, which is linked to the SILAnalysis record with the Entity Key 789101.

l meridium://SIS?Page=ReferenceDataList & Type=Logic Solver

Displays the Logic Solver Reference Data Search page.



Instrumented FunctionA specific need required of a safety instrumented system tomonitor the conditions of a process.

Maintenance Capability Index (MCI)


Maintenance Capability Index (MCI)A value 0 through 4 that measures the effectiveness of the repair processes for an element in aprotective instrument loop. The following list defines eachMCI value:

l MCI 0: Indicates that repair actions are never performed.

l MCI 1: Indicates that repair actions are effective 60 percent of the time.



l MCI 4: Indicates that repair actions are always performed perfectly.

Proof Test


Proof TestA test that consists of a set of steps that you need to perform to test safety instrumented systemsand instrumented functions. The conditions under which the test is conducted should representthe normal conditions under which the system is intended to operate.



Protective Instrument LoopA set of interconnected instruments that work together to serve a function that is defined for thesafety instrumented system in which they exist.

SIL Value


SIL ValueA numeric rating representing the overall level of protection that a safety instrumented systemprovides.