General Reference

SIS Management Data Model

The following diagram shows how the families used in SIS Management are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor. The box to which the arrow head points is the successor.

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

  • One Equipment or Functional Location record.
  • One or more Human Resource records.
  • One or more Reference Document records.
  • One or more Instrumented Function records.
  • One or more Logic Solver records.

Each Logic Solver is linked to:

  • One or more Instrumented Function records.
  • One or more SIS Proof Test records.
  • One or more SIS Proof Test Template records.

Each Instrumented Function is linked to:

  • One Equipment or Functional Location record.
  • One or more Protective Instrument Loop records.
  • One or more Inspection Task records.
  • One Risk Assessment record.
  • One LOPA Assessment record.
  • One Process Hazards Analysis (PHA) Assessment record.
  • One or more External Assessment records.
  • One or more SIS Proof Test records.
  • One or more SIS Proof Test Template records.

To simplify the data model images, the following families are not included:

  • Risk Assessment Recommendation: Within the SIS Management data model, the Risk Assessment Recommendation family participates as the successor in the Has Recommendations relationship definition with the following families:
    • Instrumented Function
    • Protective Instrument Loop
    • SIS Proof Test
    • SIS Proof Test Template
  • Hazards Analysis: The Hazards Analysis family participates as the successor in the Has HAZOP Reference relationship definition with the SIL Analysis and Instrumented Function families.

SIL Analysis Data Model

The following diagram shows how the families used in an SIL Analysis are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of the each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

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

  • Human Resource : Stores information about the people who will participate in the analysis as SIL analysis team members.
  • Reference Document : Stores the URL path to a document that is external to APM and contains reference information related to the SIL analysis.
  • Instrumented Function : Stores information about the instrumented functions of the safety instrumented system that you are analyzing.
  • Logic Solver : Stores information about the safety instrumented systems that you are analyzing.

Additionally, Logic Solver) records and Instrumented Function) records are linked to 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 the Logic Solvers and Instrumented Functions.

Instrumented Function Data Model

The following diagram shows how the families used to create an Instrumented Function are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

Instrumented Function records are linked directly to records in the following families:

  • Inspection Task: Stores details on when a proof test should be performed on the Equipment that is linked to the Inspection Task, including the due date for the task.
  • SIS Proof Test: Stores details about a test that is performed on a logic solver or an instrumented function and serves as a record of the event.
  • SIS Proof Test Template: Stores details about the steps that should be taken when testing an instrumented function. When you create an SIS Proof Test, you must select an SIS Proof Test Template, and the details from the SIS Proof Test Template will be populated in the SIS Proof Test.
  • SIS Proof Test Task: Stores details of proof test tasks that are scheduled for logic solvers or instrumented functions. SIS Proof Test Tasks can be linked to SIS Proof Tests.
  • Risk Assessment: Stores the unmitigated risk associated with the item represented by the record to which the Risk Assessment record is linked.
  • Protective Instrument Loop: Stores the details of the protective instrument loop and its components, including the calculated results of the proof test associated with the Logic Solver that is linked to the Protective Instrument Loop.
  • LOPA Assessment: Stores the details of the Layer of Protection Analysis (LOPA) that conducted, including a description of the initiating event that is indicative of a process failure. The LOPA stores details of the risk assessment that is determined after conducting the Layer of Protection Analysis. The LOPA Assessment is linked to a LOPA record and the LOPA records are linked to Risk Assessment record.
  • PHA Internal Assessment: Stores the details of the Process Hazards Analysis (PHA) assessment that you want to conduct, including the target Safety Integrity Level (SIL), Required Probability of Failure, Risk Reduction Factor, and the SIL Mode. These values are calculated based on the overall risk rank of the selected Hazards Analysis Consequence.
  • Risk Matrix Internal Assessment: Stores the details of the risk matrix assessment that you want to conduct, including the target Safety Integrity Level (SIL), Required Probability of Failure, Risk Reduction Factor, and the SIL Mode. These values are calculated based on the risk rank that you specify using the risk matrix.
  • External Assessment: Stores the details of the external assessment that you want to conduct, including the target SIL, Required Probability of Failure, Risk Reduction Factor, and the SIL Mode.
  • SIF Common Cause Failure: Stores the details of a failure that affects the operation of multiple instrumented functions.
  • Instrumented Function: Indicates that if both the instrumented functions represented by the two records are in their safe states at the same time, a hazardous event may occur.

Logic Solver Data Model

The following diagram shows how the families used to create a Logic Solver are related to one another.

In the diagram, the relationships between the Instrumented Function family and the SIS Proof Test, SIS Proof Test Task, and SIS Proof Test Template families are not included.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of the each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

As shown in the image, Logic Solvers are linked to Instrumented Functions, which store information about the specific functions associated with the Logic Solver. Logic Solvers are also linked to records in the following families:

  • SIS Proof Test : Stores details of proof tests that are performed on logic solvers or instrumented functions. SIS Proof Tests can be linked to Functional Test Details, which store the detailed steps that need to be performed during proof tests.
  • SIS Proof Test Task : Stores details of proof test tasks that are scheduled for logic solvers or instrumented functions. SIS Proof Test Tasks can be linked to SIS Proof Tests.
  • SIS Proof Test Template : Stores details of the steps that should be taken when testing a logic solver or an instrumented function. When you create an SIS Proof Test, you can select an SIS Proof Test Template and the details from the SIS Proof Test Template will be populated in the SIS Proof Test.

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

The SIS Proof Test, SIS Proof Test Template, and Reference Document families participate as successors in other relationships within the SIS Management data model. This means that these families appear in another portion of the data model.

Protective Instrument Loop Data Model

The following diagram shows how the families used in a Protective Instrument Loop are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of the each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

The following protective instrument loop elements are defined in the APM system:

  • Logic Solver
  • Sensor System
  • Sensor Group
  • Sensor
  • Final Element System
  • Final Element Group
  • Final Element

By default, every protective instrument loop consists of at least one of each element. When you create a Protective Instrument Loop, the APM system creates one record for each of these elements, and links to the Protective Instrument Loop as shown in the data model.

SRS Project Data Model

The following diagram shows how the families used in an SRS Project are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of the each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

SRS Project records are linked directly to records in the following families:

  • Environment
  • General Data
  • Electrical
  • Hardware
  • IF SRS
  • Interfaces
  • Operations
  • Performance Data
  • SIL SRS
  • Software
  • Testing/Faults
  • SIL Analysis
  • Instrumented Function
  • Logic Solver
  • Protective Instrument Loop

SIS Management Security Groups

The following table lists the baseline Security Groups available for users within this module, as well as the baseline Roles to which those Security Groups are assigned.

Important: Assigning a Security User to a Role grants that user the privileges associated with all of the Security Groups that are assigned to that Role. To avoid granting a Security User unintended privileges, before assigning a Security User to a Role, be sure to review all of the privileges associated with the Security Groups assigned to that Role. Also, be aware that additional Roles, as well as Security Groups assigned to existing Roles, can be added via Security Manager.
Security GroupRoles
MI SIS Administrator

MI Safety Admin

MI SIS Administrator

MI SIS Engineer

MI Safety Admin

MI Safety Power

MI Safety User

MI SIS Engineer

MI SIS User

MI Safety Admin

MI Safety Power

MI Safety User

MI SIS User

MI SIS Viewer

MI APM Viewer

MI Safety Admin

MI Safety Power

MI Safety User

MI SIS Engineer

MI SIS Viewer

The baseline family-level privileges that exist for these Security Groups are summarized in the following table.

Note: The baseline family-level privileges available in the LOPA module are also applicable to Security Groups in SIS Management module.
FamilyMI SIS AdministratorMI SIS EngineerMI SIS UserMI SIS Viewer
Entity Families
Asset Criticality AnalysisViewNoneNoneView
Asset Criticality Analysis SystemView NoneNoneView
ConsequenceView, Update, Insert, DeleteViewViewView
EquipmentViewViewViewView
External AssessmentView, Update, Insert, DeleteView, Update, Insert, DeleteNoneView
Functional LocationViewViewViewView
Functional SystemsView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Functional Test DetailView, Update, Insert, DeleteView, Update, Insert, DeleteView, Update, Insert, DeleteView
Human ResourceView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Instrumented FunctionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
LOPA AssessmentView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Proven In Use JustificationView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Safety Integrity LevelView, Update, Insert, DeleteViewViewView
Relationship Families
Analysis Has Human ResourceView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Asset Criticality Analysis Has SystemViewNoneViewView
Equipment Has EquipmentViewViewViewView
Functional Location Has EquipmentViewViewViewView
Functional Location Has Functional LocationViewViewViewView
Has EquipmentView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Functional LocationView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Functional Location DetailView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Functional TestView, Update, Insert, DeleteView, Update, Insert, DeleteView, Update, Insert, DeleteView
Has_Functional_Test_DetailView, Update, Insert, DeleteView, Update, Insert, DeleteView, Update, Insert, DeleteView
Has Hazard EventView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has HAZOP ReferenceView, Update, Insert, DeleteView, Update, Insert, DeleteView, Update, Insert, DeleteView
Has IFView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Instrumented Function RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Instrument LoopView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Instrument Loop RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has LOPAView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has LOPA RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL DeviceView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL Device RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL GroupView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL Group RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL SubsystemView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has PIL Subsystem RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Proven In Use JustificationView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has RBI ComponentsView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has RecommendationsView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Reference DocumentsView, Update, Insert, DeleteView, Update, Insert, DeleteView, InsertView
Has Reference ValuesView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has RiskView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Risk CategoryView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Risk MatrixView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has SIF Common Cause FailuresView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has SIL AssessmentView, Update, Insert, DeleteView, Update, Insert, DeleteNoneView
Has SIS Analysis RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has SIS RevisionView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has SIS Trip Report DetailView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Site ReferenceView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Task HistoryView, Update, Insert, DeleteView, Update, Insert, DeleteView, InsertView
Has TasksView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Task RevisionViewViewViewView
Has Template DetailView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has TemplatesView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Has Time Based Inspection IntervalViewViewViewView
Migrates RiskView, Update, Insert, DeleteView, Update, Insert, DeleteViewView
Was Promoted to ASMView, Update, Insert, DeleteView, Update, Insert, DeleteViewView

Security Permissions for SRS Families

The security permissions for the SRS Project and SRS Template families are summarized in the following table.

Security GroupTypePermissions
MI SIS Administrator Group View, Update, Insert, Delete
MI SIS EngineerGroup View, Update, Insert, Delete
MI SIS UserGroup View

SIS Management URLs

There is one URL route associated with SIS Management: asset-safety/sis. The following table describes the various paths that build on the route, and the elements that you can specify for each.

Tip: For more information, refer to the URLs section of the documentation.
ElementDescriptionAccepted Value(s)Notes
asset-safety/sis/overview: Displays the SIS Management Overview page.
asset-safety/sis/sil/<EntityKey>: Displays the Analysis Summary workspace of the SIL Analysis with the specified Entity Key.
<EntityKey> Specifies the Entity Key of the analysis that you want to access.Any numeric Entity Key that corresponds to an existing analysis.

Opens the specified SIL Analysis in a new tab.

This value is required to access an existing analysis from a URL.

asset-safety/sis/sil/prooftesttask/<EntityKey1>/<EntityKey2>: Displays the Proof Test Task datasheet with the specified Entity Key and linked to the the specified Instrumented Function or the Logic Solver.
<EntityKey1> Specifies the Entity Key of the Instrumented Function or the Logic Solver that is linked to the Proof Test Task that you want to access.Any numeric Entity Key that corresponds to an existing Instrumented Function or Logic Solver.None
<EntityKey2> Specifies the Entity Key of the Proof Test Task that you want to access.0Opens the blank datasheet of a Proof Test Task, allowing you to create a new one.
Any numeric Entity Key that corresponds to an existing Proof Test Task.

Opens the specified Proof Test Task in a new tab.

This value is required to access an existing Proof Test Task from a URL.

asset-safety/sis/sil/verification/<EntityKey>: Displays the Protective Instrument Loop Template with the specified Entity Key.
<EntityKey> Specifies the Entity Key of the Protective Instrument Loop Template that you want to access.Any numeric Entity Key that corresponds to an existing Protective Instrument Loop Template.

Opens the specified Protective Instrument Loop Template in a new tab.

This value is required to access an existing Protective Instrument Loop Template from a URL.

asset-safety/sis/FDM/<CustomDeviceType>/<EntityKey>: Displays the datasheet of a Custom Device of the specified type and Entity Key.
<CustomDeviceType>  Specifies the type of the Custom Device whose Failure Data you want to access.All None
sensor
logic-solver
final-element
<EntityKey> Specifies the Entity Key of the Custom Device whose Failure Data you want to access.Any numeric Entity Key that corresponds to an existing Custom Device.

Opens the specified Custom Device in a new tab.

This value is required to access an existing Custom Device from a URL.

Example URLDestination
asset-safety/sis/overview The SIS Management Overview page
asset-safety/sis/sil/2355677 The Analysis Summary workspace of the SIL Analysis with the Entity Key 2355677
asset-safety/sis/sil/prooftesttask/73443556/34545566 The Proof Test Task datasheet with the Entity Key 34545566, linked to an Instrumented Function or a Logic Solver with the Entity Key 73443556
asset-safety/sis/sil/verification/35945456 The Protective Instrument Loop Template datasheet with the Entity Key 35945456
asset-safety/sis/FDM/sensor/75334565 The Sensor Custom Device datasheet with the Entity Key 75334565

SIS Management System Code Tables

The following table lists the System Code Tables that are used by SIS Management.

Table ID

Table Description

Function

MI_IPL_TYPE LOPA IPL TYPE Populates the Type field in an Independent Layer of Protection.
MI_SIL_ASSESSMENT_METHOD SIL Assessment Method Populates the SIL Assessment Method field in an Instrumented Function.
MI_SIL_FINALELEMVOTE SIL FinalElement Vote Populates the Voting field in a Protective Instrument Loop Final Element Group.
MI_SIL_SENSORVOTE SIL Sensor Vote Populates the Voting field in a Protective Instrument Loop Sensor Group.
UOME Unit of Measure Populates the Trip Point Units field in a SIS Proof Test Template Detail.

About SIL Analysis State Configuration

This topic describes attributes of the State Configuration that is defined for the SIL Analysis family in the baseline APM database.

The following baseline states are defined in the APM application:

  • Planning
  • Active
  • Review
  • Pending Approval
  • Complete

The following baseline operations are defined in theAPM application:

  • Begin
  • Propose
  • Submit
  • Accept
  • Reject
  • Modify/Reassess

These baseline states and operations are reserved, which means you cannot modify or remove them. You can, however, add your own states and operations to the state configuration.

The following flow diagram illustrates the State Configuration for the SIL Analysis family. In this image, a box represents a state, and an arrow represents an operation. The state to which an arrow points represents a successor state.

By default, the MI SIS Administrator and MI SIS Engineer State Configuration roles are assigned to all states in the SIL analysis state configuration. You can assign State Configuration roles to any state. In addition, for each state, the Require a specific user to be assigned to a state check box is selected.

About Protective Instrument Loop State Configuration

This topic describes attributes of the State Configuration that is defined for the Protective Instrument Loop family in the baseline APM database.

The following baseline states are defined in the APM application:

  • Design
  • Pending Approval
  • Approval
  • In Service
  • Out of Service

The following baseline operations are defined in the APM application:

  • Submit
  • Accepted
  • Rejected
  • Commissioned
  • Modify
  • Reinstate

These baseline states and operations are reserved, which means you cannot modify or remove them. You can, however, add your own states and operations to the state configuration.

The following flow diagram illustrates the State Configuration for the SIL Analysis family. In this image, a box represents a state, and an arrow represents an operation. The state to which an arrow points represents a successor state.

By default, the MI SIS Administrator and MI SIS Engineer State Configuration roles are assigned to all states in the SIL analysis state configuration. You can assign State Configuration roles to any state.

Note:
  • If Baseline or Custom State Management is used, the Protective Instrument Family Datasheet is enabled only in the Initial state defined in the State Machine Configuration. Datasheet is disabled for editing in the subsequent states. Additionally, the related records exhibit the following behaviour:
    • Link and Copy buttons for Sensor Group details tab is disabled
    • Protected Instrument Loop Sensor Datasheet is disabled
    • Link and Copy buttons for Protective loop Sensor is disabled
    • Link and Copy buttons for Final Element group details tab is disabled
    • Protected Instrument Loop Final Element Datasheet is disabled
    • Link and Copy buttons for Protective Instrument Loop Final Element is disabled
    • Protective Instrument Device Datasheet is disabled
    • Proven In Use Justification Datasheet is disabled
  • If State Management is disabled for Protective Instrumented Loop family, the restriction to modify the Protected Instrument Loop and related records based on the state is removed.

About the SIS Trip Report State Configuration

This topic describes attributes of the State Configuration that is defined for the SIS Trip Report family in the baseline APM database.

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

None of these states and operations are reserved, which means you can remove or modify any of them. You can also add your own states and operations to the state configuration.

State Configuration Roles

By default, the MI SIS Administrator and MI SIS Engineer State Configuration roles are assigned to all states in the SIS Trip Report state configuration. You can assign State Configuration roles to any state. In addition, for each state, the Require a specific user to be assigned to a state check box is selected.

About State Management of an SRS Project

The following states are configured for an SRS Project:

  1. In Progress: Indicates that the SRS Project is in progress or yet to be sent for approval. You can modify an SRS Project only if it is in the In Progress state. After you have entered all the required information in the SRS Project, you can send it for approval by changing the state to Pending Approval.
  2. Pending Approval: Indicates that the SRS Project has been sent for approval. If you approve the SRS Project, the state of the SRS Project changes to Approved. If you reject the SRS Project, the state of the SRS Project changes to In Progress.
  3. Approved: Indicates that the SRS Project has been approved. After the state of an SRS Project is set to Approved:
    • The associated SRS Project is cycled. That is, the Last Date field is set to the date on which the state of the SRS Project is set to Approved. The Next Date field is set to the date on which the SRS Project must be performed again (in case of a recurring task).

Illustration of the State Management of SRS Projects

By default, the following states exists for an SRS Project:

About State Management of SRS Templates

The following states are configured for SRS templates:

  1. In Progress: Indicates that the SRS Template is in progress or yet to be sent for approval. You can modify an SRS Template only if it is in the In Progress state. After you have entered all the required information in the SRS Template, you can send it for approval by changing the state to Pending Approval.
  2. Pending Approval: Indicates that the SRS Template has been sent for approval. If you approve the SRS Template, the state of the SRS Template changes to Approved. If you reject the SRS Template, the state of the SRS Template changes to In Progress.
  3. Approved: Indicates that the SRS Template has been approved. After the state of an SRS Template is set to Approved:
    • The associated SRS Template is cycled. That is, the Last Date field is set to the date on which the state of the SRS Template is set to Approved. The Next Date field is set to the date on which the SRS Template must be performed again (in case of a recurring task).

Illustration of the State Management of SRS Templates

By default, the following states exists for SRS Templates:

SIS Management Site Filtering

In SIS Management, an SIL Analysis is assigned a site on the Definition workspace and spread to all the related records, such as Instrumented Function records and Logic Solver records.

Tip: For more information, refer to the Site Filtering section of the documentation.

In SIS Management, users will see only SIL Analysis that are assigned to their site(s) or that are global records.

Consider an organization that has three sites, Site X, Site Y, and Site Z. The following SIL Analysis records exist:

  • SIL Analysis A: Assigned to Site X
  • SIL Analysis B: Assigned to Site Y
  • SIL Analysis C: Assigned to Site Z
  • SIL Analysis D: No site assigned (global records)

Scenario 1: User assigned to only Site X

This user will see SIL Analysis A and SIL Analysis D.

Scenario 2: User assigned to both Site X and Site Y

This user will see SIL Analysis A, B and D.

Scenario 3: Super User

This user will see SIL Analysis A, B, C and D.

Important: If a multi-site user, or a Super User, links child records from multiple sites to a parent record designated as Global, another user who does not have access to all sites may only see a portion of the data associated with that record. In the example above, if a child record assigned to Site X and a child record assigned to Site Y are linked to SIL Analysis D, the Site X user will not be able to see all the records associated with SIL Analysis D.

About Reports in SIS Management

The SIS Management module provides the following types of baseline reports.

SIL Analysis Report

The SIL Analysis report contains the information from the following fields stored in the SIL Analysis records:

Report ColumnField Name in SIL Analysis Record
Analysis DescriptionAnalysis Description
Analysis IDAnalysis ID
Analysis Long DescriptionLong Description
Analysis Owner NameOwner
End DateAnalysis End Date
Last Modified ByLast Modified By
Last Modified DateLast Modified Date
Process Hazards Analysis ReferenceHazards Analysis Reference
Process Hazards Analysis Rev DateHazards Analysis Date
Process Hazards Analysis Rev NoHazards Analysis Revision
Site DescriptionSite Description
Site IDSite ID
Start DateAnalysis Start Date
Unit DescriptionUnit Description
Unit IDUnit ID

SRS Project Report

The SRS report contains all the details from an SIL Analysis that are required to meet compliance for IEC standard 61511. You can use this report to:

  • Provide proof of compliance with IEC 61511.
  • Identify gaps in compliance with IEC 61511.

The SRS report displays values that are stored in the SIL Analysis records, and related records that comprise an SIL Analysis. Information in the SRS report is organized in the following sections:

  • Introduction
  • General Requirements for the Safety Instrumented System
  • General Requirements for the Safety Instrumented Functions
  • Summary of Safety Instrumented Functions
  • SIF Safety Requirement Specification
  • Process & Operational Requirements
  • Loop Components
    • Sensor Part
    • Logic Solver Part
    • Final Element Part

Instrumented Function Report

The Instrumented Function report contains information from the following fields stored in the Instrumented Function records:

Report ColumnField Name in Instrumented Function Record
Availability TargetAvailability Target
Consequence DescriptionConsequence Description
Failure Rate UOMFailure Rate UOM
Frequency of Initiating Event (per yr)Frequency of Initiating Event (per yr)
Function TypeFunction Type
Hazardous EventHazardous Event
Hazards Analysis RefHazards Analysis Reference
Hazards Analysis Rev DateHazards Analysis Date
IF DescriptionPIF Description
IF IDPIF ID
Initiating EventInitiating Event
Initiating Event DescriptionInitiating Event Description
Last Modified ByLast Modified By
Last Modified DateLast Modified Date
Maximum Probability of FailureRequired Probability of Failure
Process SpeedProcess Speed
Response TimeResponse Time
Risk Reduction FactorRisk Reduction Factor
Safe State DescriptionSafe State Description
Selected SIL LevelSelected SIL Level
SIL Assessment MethodSIL Assessment Method
SIL ModeSIL Mode
SIS System IDSIS System ID
Site IDSite ID
Spurious Trip LimitSpurious Trip Limit (per yr)
Unit IDUnit ID

Protective Instrument Loop Report

The Protective Instrument Loop report contains a summary of results for the selected Protective Instrument Loop (PIL). This report also includes a summary of calculated results for the Logic Solver, Sensor System, and Final Element System associated with the Protective Instrument Loop.

The PIL report displays the following information from the Protective Instrument Loop records:

Report ColumnField Name in Protective Instrument Loop Record
Achieved SIL Achieved SIL
Evaluated Systematic CapabilitiesCalculated SIL Systematic Capabilities
Last Modified By Last Modified By
MTTS (years)MTTFS
Status Changed ByStatus By
Systematic Capability Validation Systematic Capability Validation
DescriptionDescription
Evaluated Architectural ConstraintsCalculated SIL Architectural Constraints
Last Modified DateLast Modified Date
Long DescriptionLong Description
Loop ClassLoop Class
Loop IDID
Loop TypeLoop Type
Meets SIL RequirementsMeets SIL Requirement?
Mission TimeMission Time
Probability of FailureLoop PFH
Required SILRequired SIL
Risk Reduction FactorRisk Reduction Factor
SIL Demand ModeDemand Mode
SIL Validation MethodSIL Validation Method
Startup TimeStartup Time
StatusStatus
Status Changed DateStatus Date
Test Architectural ConstraintsTest Architecture Constraints

The Protective Instrument Loop report also includes a table, which contains the following information that is stored in the Protective Instrument Loop Logic Solver records, and Protective Instrument Loop System records linked to the Protective Instrument Loop record:

Report Column  Field Name in Protective Instrument Loop Logic Solver RecordField Name in Protective Instrument Loop System Record
for Sensor Systemfor Final Element System
Arch ConsSIL Architectural ConstraintsSIL Architectural ConstraintsSIL Architectural Constraints
AvailAvailabilityAvailabilityAvailability
MTTFSMTTFSMTTFSMTTFS
MTTFS ContMTTFS ContributionMTTFS ContributionMTTFS Contribution
PFD AvgCalculated PFD AvgCalculated PFD AvgCalculated PFD Avg
PFD ContPFD ContributionPFD ContributionPFD Contribution
PFHCalculated PFHCalculated PFHCalculated PFH
PTIProof Test IntervalN/AN/A
Sys CapSIL Systematic CapabilitySIL Systematic CapabilitySIL Systematic Capability

Family Fields that are Updated While Importing Data from Exida

This topic maps the exSILentia fields with the corresponding Family Fields that gets updated when you import data from Exida.

The Protective Instrument Loop family

Property NameField IDField CaptionexSILentia Class/Field
CalculatorNoneNoneNone
DiagramMI_PRE_I_LP_DIAGRAM_BDiagramNone
DemandModeMI_PRE_I_LP_DEMAND_MODE_CDemand_ModeclsSILverData_DemandMode
LoopIDMI_FNCL_SYS_ID_CIDNone
MissionTimeMI_PRE_I_LP_MISSION_TIME_NMission_TimeclsSILverData_calctime
StartupTimeMI_PRE_I_LP_STARTUP_TIME_NStartup_TimeclsSILverData_startup
TestArchitectureContraintsMI_PRE_I_LP_TST_ARCHTCTE_CNS_CTest_Architecture_ConstraintsNone
SystematicCapabilityValidationMI_PRE_I_LP_SYSTMTC_CPBY_VLN_LSystematic_Capability_ValidationclsSILverData_ConsiderSILCapability
SensorMCIMI_PRE_I_LP_SENSOR_MCI_NSensor_MCIclsSILverData_MCI_Sensors
FinalElementMCIMI_PRE_I_LP_FINALELEMENT_MCI_NFinal_Element_MCIclsSILverData_MCI_FinalElements
LogicSolverMCIMI_PRE_I_LP_LOGICSOLVER_MCI_NLogic_Solver_MCIclsSILverData_MCI_LogicSolver
RequiredSILMI_PRE_I_LP_REQUIRED_SIL_NRequired_SILclsSILverData_TargetSILV

The Protective Instrument Loop Final Element family

Property NameField IDField CaptionexSILentia Class/Field
GUIDMI_PRE_ELT0_GUID_CGUIDNone
RAVMI_PRE_FLT0_RAV_LRemote_Actuated_ValveclsFinalElemLegData_RAV_
TightShutOffRequiredMI_PRE_FLT0_TIGHT_SHTFF_RQRD_LTight_Shutoff_RequiredclsFinalElemLegData_TShutoffReq_
UncleanServiceMI_PRE_FLT0_UNCLEAN_SERVICE_LSevere_ServiceclsFinalElemLegData_UncleanService
UseCombinationMI_PRE_FLT0_USE_COMBINATION_LUse_CombinationclsFinalElemLegData_UseActValCombo
UsePVSTMI_PRE_FLT0_USE_PVST_LPartial_Valve_Stroke_TestingclsFinalElemLegData_UsePVST_
UsePVSTCovMI_PRE_FLT0_USE_PVSTCOV_LUse_Custom_PVST_CoverageclsFinalElemLegData_UsePVSTCov
ValveTripOpenMI_PRE_FLT0_VALVE_TRIP_OPEN_LValve_Trip_OpenclsFinalElemLegData_ValveTripOpen
CustomPVSTCoverageMI_PRE_FLT0_CUSTM_PVST_CVRGE_NCustom_PVST_CoverageclsFinalElemLegData_AT_Coverage_
CustomPVSTIntervalMI_PRE_FLT0_PVST_INTER_NPVST_IntervalclsFinalElemLegData_AT_Interval
CustomPVSTIntervalUOMMI_PRE_FLT0_PVST_INTER_UOM_CPVST_Interval_UOMNone

The Protective Instrument Loop System family

Property NameField IDField CaptionexSILentia Class/Field
SystemTypeMI_PRE_SYM0_SYSTEM_TYPE_CSystem_TypeNone
GUIDMI_PRE_ELT0_GUID_CGUIDNone
ParentNoneNoneNone
CommonCauseBetweenGroupsBetaMI_PRE_SYM0_COMMON_CAUSE_NCommon_Cause_(Beta)clsSILverData_GroupBetaSens
NumberofGroupsMI_PRE_SYM0_NUMBEROF_GROUPS_NNumber_of_GroupsclsSILverData_numsensors
GroupVotingMI_PRE_SYM0_VOTING_BTWN_GRPS_CVoting_Between_GroupsclsSILverData_sensorvote_

The Protective Instrument Loop Sensor family

Property NameField IDField CaptionexSILentia Class/Field
GUIDMI_PRE_ELT0_GUID_CGUIDNone
IsAnalogMI_PRE_SNR0_ISANALOG_LAnalog_InputNone
AnalogTripMI_PRE_SNR0_ANALOG_TRIP_NAnalog_TripclsSensorLegData_AnalogTrip
ExternalComparisonMI_PRE_SNR0_EXTERNAL_COMPRSN_LExternal_ComparisonclsSensorLegData_ExternalComp_
ExternalComparisonValueMI_PRE_SNR0_EXTER_COMPA_VALUE_NExternal_Comparison_ValueclsSensorLegData_ExternalCompCov
AlarmSettingMI_PRE_SNR0_HIGH_ALARM_LAlarm_Setting(High/Low)clsSensorLegData_Jumper
RangeCheckingMI_PRE_SNR0_RANGE_CHECKING_LOver/Under_RangeclsSensorLegData_RangeChecking
InputFiltersMI_PRE_SNR0_INPUT_FILTER_LAlarm_FilterclsSensorLegData_InputFiltering
SensorTripOnAlarmMI_PRE_SNR0_SNSR_TRP_ON_ALRM_LAlarm_Voted_as_TripclsSensorLegData_TripOnAlarm
SensorTypeMI_PRE_SNR0_SENSOR_TYPE_CSensor_TypeclsSensorLegData_SensType
EnableTripMI_PRE_SNR0_ENABLETRIP_LEnableTripNone

The Protective Instrument Loop Group family

Property NameField IDField CaptionexSILentia Class/Field
GUIDMI_PRE_ELT0_GUID_CGUIDNone
ParentNoneNoneNone
GroupTypeMI_PRE_GRP0_GROUP_TYPE_CGroup_TypeNone
LegsNumberMI_PRE_GRP0_SUBSYSTEM_NUMBER_NSubsystem_NumberNone
NMI_PRE_GRP0_N_NCustom_Vote_NclsFinalElemGroupData_CustVoteN
MMI_PRE_GRP0_M_NCustom_Vote_MclsFinalElemGroupData_CustVoteM_
FinalElementVoteMI_PRE_GRP0_VOTING_CVotingclsFinalElemGroupData_Vote
CommonCauseBetaMI_PRE_GRP0_COMMON_CAUSE_BTA_NCommon_Cause_(Beta)clsFinalElemGroupData_Beta
MTTRMI_PRE_GRP0_MTTR_NMTTRclsFinalElemGroupData_MTTR_
ProofTestCoverageMI_PRE_GRP0_PROOF_TEST_CVRGE_NProof_Test_CoverageclsFinalElemGroupData_ProofTestCov
PrrofTestIntervalMI_PRE_GRP0_PROOF_TST_INTRVL_NProof_Test_IntervalclsFinalElemGroupData_ProofTestInt
VoteTypeMI_PRE_GRP0_DIVERSE_LDiverseclsFinalElemGroupData_IsVoteDiverse

The Protective Instrument Loop Logic Solver Channel family

Property NameField IDField CaptionexSILentia Class/Field
ParentNoneNoneNone
EntityNoneNoneNone
ChannelTypeMI_PRE_CHL0_CHANNEL_TYPE_CChannel_TypeclsLogicSolverPartData_ChannelType
ExidalDMI_PRE_DVE0_EXIDA_ID_NExida_IDclsLogicSolverPartData_EID
DangerousDetectedMI_PRE_DVE0_DANGEROUS_DETCTD_NDangerous_DetectedclsLogicSolverPartData_FailDD
DangeroudUndetectedMI_PRE_DVE0_DANGEROS_UNDTCTD_NDangerous_UndetectedclsLogicSolverPartData_FailDU
FailureAnnunciationDetectedMI_PRE_DVE0_FLRE_ANNNCTN_DTD_NFailure_Annunciation_DetectedclsLogicSolverPartData_FailAD
FailureAnnunciationUndetectedMI_PRE_DVE0_FLRE_ANNNCTN_UND_NFailure_Annunciation_undetectedclsLogicSolverPartData_FailAU
FailureDetectedMI_PRE_DVE0_FAILURE_DETECTED_NFailure_DetectedclsLogicSolverPartData_FailDetected
FailureHighMI_PRE_DVE0_FAILURE_HIGH_NFailure_highclsLogicSolverPartData_FailHigh
FailureLowMI_PRE_DVE0_FAILURE_LOW_NFailure_LowclsLogicSolverPartData_FailLow
ResidualMI_PRE_DVE0_RESIDUAL_NResidualclsLogicSolverPartData_FailNoEffect
SafeDetectedMI_PRE_DVE0_SAFE_DETECTED_NSafe_DetectedclsLogicSolverPartData_FailSD
SafeFailureFractionMI_PRE_DVE0_SSF_NSafe_Failure_FractionclsLogicSolverPartData_SFF
SafeUndetectedMI_PRE_DVE0_SAFE_UNDETECTED_NSafe_UndetectedclsLogicSolverPartData_FailSU
ChannelsNoneNoneclsLogicSolverPartData_Channels
NameMI_PRE_DVE0_NAME_CModule_NameclsLogicSolverPartData_Model
ReferenceDateSourceTitleMI_PRE_ELT0_REFRNCE_DTA_SRCE_CReference_Data_SourceNone
ReferenceDateSourceMI_PRE_ELT0_RFRNCE_DTA_RFRNE_CReference_Data_ReferenceNone
ReferenceDataDateMI_PRE_ELT0_REFERNCE_DTA_DTE_DReference_Data_DateNone
ReferenceRevisionMI_PRE_ELT0_REFRNCE_DTA_RVSN_CReference_Data_RevisionNone

The Protective Instrument Loop Logic Solver family

Property NameField IDField CaptionexSILentia Class/Field
GroupTypeMI_PRE_GRP0_GROUP_TYPE_CGroup_TypeNone
GUIDMI_PRE_ELT0_GUID_CGUIDNone
ParentNoneNoneNone
MTTRMI_PRE_GRP0_MTTR_NMTTR.clsSILverData_LogicSolver.MTTR
ProofTestCoverageMI_PRE_GRP0_PROOF_TEST_CVRGE_NProof_Test_CoverageclsSILverData_LogicSolver.ProofTestCoverage
ProofTestIntervalMI_PRE_GRP0_PROOF_TST_INTRVL_NProof_Test_IntervalclsSILverData_LogicSolver.ProofTestInterval
EnableAutoPTSMI_PRE_SLR0_ATMTC_PRFTST_SWR_LAutomatic_Prooftest_SwitchoverclsSILverData_LogicSolver.AT_Enabled
AutoPTSIMI_PRE_SLR0_ATMC_PRT_SWR_INL_NAutomatic_Prooftest_Switchover_IntervalclsSILverData_LogicSolver.AT_Interval
AutoPTSICovMI_PRE_SLR0_ATMC_PRT_SWR_INL_NAutomatic_Prooftest_Switchover_ConverageclsSILverData_LogicSolver.AT_Coverage
ArchitecturalConstraintsMI_PRE_GRP0_SL_ARCHTCTRL_CNS_NSIL_Architectural_ConstraintsclsSILverData_LogicSolver.HFT
EquipmentFailureModeTypeAsPerIEC61508MI_PRE_SLR0_EQUIPMENT_TYPE_CArchitectural_TypeclsSILverData_LogicSolver.ArchType
CommonCauseBetaMI_PRE_GRP0_COMMON_CAUSE_BTA_NCommon_Cause_(Beta)clsSILverData_LogicSolver.Beta
SILCapabilityMI_PRE_GRP0_SIL_CAPABILITY_NSIL_Systematic_CapabilityclsSILverData_LogicSolver.LimitingSIL
VotingMI_PRE_GRP0_VOTING_CVotingclsSILverData_LogicSolver.MyVoting
IsCustomerizedMI_PRE_SLR0_ISCUSTOMERIZED_LManual_EntryNone
ExidaIDMI_PRE_SLR0_EXIDA_ID_NExida_IDclsSILverData_LogicSolver.EquipmentID
ExidaNameMI_PRE_SLR0_EXIDA_NAME_CExida_NameclsSILverData_LogicSolver.exidaName
ReferenceDateSourceTitleMI_PRE_ELT0_REFRNCE_DTA_SRCE_CReference_Data_SourceNone
ReferenceDateSourceMI_PRE_ELT0_RFRNCE_DTA_RFRNE_CReference_Data_ReferenceNone
ReferenceDataDateMI_PRE_ELT0_REFERNCE_DTA_DTE_DReference_Data_DateclsSILverData_LogicSolver.SERHVer
ReferenceRevisionMI_PRE_ELT0_REFRNCE_DTA_RVSN_CReference_Data_RevisionclsSILverData_LogicSolver.SERHVer
AutomaticMI_PRE_SLR0_AUTOMATIC_LAutomatic_Channel_CountclsSILverData_LogicSolver.Automatic
LogicSolverChannelsNoneNoneNone

The Protective Instrument Device family

Property NameField IDField CaptionexSILentia Class/Field
ExidalDMI_PRE_DVE0_EXIDA_ID_NExida_IDclsSILverDeviceData_EquipmentID
IsCustomerizedMI_PRE_DVE0_ISCUSTOMED_LManual_EntryNone
TagMI_PRE_DVE0_DEVICE_TAG_CDevice_TagNone
IsApprovedMI_PRE_ELT0_APPROVEDTOUSE_LApproved_Custom_DeviceNone
AnalogAI_AOMI_PRE_DVE0_ANALOG_CHANNELS_NAnalog_ChannelsclsSILverDeviceData_ChannelCount
DigitalDI_DOHighMI_PRE_DVE0_DIGTL_HGH_CHNNLS_NDigital_High_ChannelsclsSILverDeviceData_ChannelCount
DigitalDI_DOLowMI_PRE_DVE0_DIGITL_LW_CHNNLS_NDigital_Low_ChannelsclsSILverDeviceData_ChannelCount
NameMI_PRE_DVE0_NAME_CExida_NameclsSILverDeviceData_exidaName
ArchitecturalTypeMI_PRE_DVE0_ARCHITECTRL_TYPE_CArchitectural_TypeclsSILverDeviceData_ArchType
CertifiedSILMI_PRE_DVE0_CERTIFIED_SIL_NCertified_SILclsSILverDeviceData_CertifiedForSIL
DangerousDetectedMI_PRE_DVE0_DANGEROUS_DETCTD_NDangerous_DetectedclsSILverDeviceData_FailDD
DangerousUndetectedMI_PRE_DVE0_DANGEROS_UNDTCTD_NDangerous_UndetectedclsSILverDeviceData_FailDU
DeviceTypeMI_PRE_DVE0_DEVICE_TYPE_CDevice_TypeclsSILverDeviceData_DeviceType
FailureAnnunciationDetectedMI_PRE_DVE0_FLRE_ANNNCTN_DTD_NFailure_Annunciation_DetectedclsSILverDeviceData_FailAD
FailureAnnunciationUndetectedMI_PRE_DVE0_FLRE_ANNNCTN_UND_NFailure_Annunciation_undetectedclsSILverDeviceData_FailAU
FailureDetectedMI_PRE_DVE0_FAILURE_DETECTED_NFailure_DetectedclsSILverDeviceData_FailDetected
FailureHighMI_PRE_DVE0_FAILURE_HIGH_NFailure_highclsSILverDeviceData_FailHigh
FailureLowMI_PRE_DVE0_FAILURE_LOW_NFailure_LowclsSILverDeviceData_FailLow
ResidualMI_PRE_DVE0_RESIDUAL_NResidualclsSILverDeviceData_FailNoEffect
SafeDetectedMI_PRE_DVE0_SAFE_DETECTED_NSafe_DetectedclsSILverDeviceData_FailSD
SafeUndetectedMI_PRE_DVE0_SAFE_UNDETECTED_NSafe_UndetectedclsSILverDeviceData_FailSU
SuggestedPTCMI_PRE_DVE0_SUGGESTEDPTC_NSuggested_PTCclsSILverDeviceData_SuggestPTC
TripRestrictMI_PRE_DVE0_TRIPRESTRICT_CTrip_RestrictclsSILverDeviceData_TripRestrict
ReferenceDataSourceTitleMI_PRE_ELT0_REFRNCE_DTA_SRCE_CReference_Data_SourceNone
ReferenceDataDateMI_PRE_ELT0_REFERNCE_DTA_DTE_DReference_Data_DateclsSILverDeviceData_SERHVer
ReferenceRevisionMI_PRE_ELT0_REFRNCE_DTA_RVSN_CReference_Data_RevisionclsSILverDeviceData_SERHVer

The Protective Instrument Loop Element family

Property NameField IDField CaptionexSILentia Class/Field
ParentNoneNoneNone
ConstantineNoneNoneNone
DisplayInfoMI_PRE_ELT0_VISUAL_ATTRIBUTS_TVisual_AttributesNone

The Instrumented Function family

Property NameField IDField CaptionexSILentia Class/Field
SafetyLoopsNoneNoneNone
UnitIDMI_PIF00000_UNIT_ID_CUnit_IDclsSILverData_UnitName
DescriptionVS)MI_PIF00000_DESC_CPIF_DescriptionclsSILverData_SIFDesc
HazardousEventMI_PIF00000_HAZAR_EVENT_CHazardous_EventclsSILverData_HazardDesc
ConsequenceDescriptionMI_PIF00000_CONS_DESC_TConsequence_DescriptionclsSILverData_ConseqDesc
SafeStateDescriptionMI_PIF00000_SAFE_STATE_DESCR_TSafe_State_DescriptionclsSILverData_SafeState
ResponseTimeMI_PIF00000_RESPO_TIME_NResponse_TimeclsSILverData_RespTime
SpuriousTripLimitMI_PIF00000_SPURI_TRIP_LIMIT_NSpurious_Trip_Limit_(per_yr)clsSILverData_ReqSTR_
SelectedSILLevelMI_PIF00000_SELEC_SIL_LEVEL_NSelected_SIL_LevelclsSILverData_TargetSIL
SILModeMI_PIF00000_SIL_MODE_CSIL_ModeNone
SILAssessmentMethodMI_PIF00000_SIL_ASSES_METHO_CSIL_Assessment_MethodNone
ProcessHazardsAnalysisReferenceMI_PIF00000_PROC_HAZ_AN_REF_CHazards_Analysis_ReferenceNone
ProcessHazardsAnalysisDateMI_PIF00000_PROC_HAZ_AN_DATE_DHazards_Analysis_DateNone
SiteIDMI_PIF00000_SITE_ID_CSite_IDNone
SILAnalysisKeyMI_PIF00000_SIL_ANALY_KEY_NSIL_Analysis_KeyNone

About Upgrade of LOPA and Safeguards to V4.3.0.0.0

In versions prior to V4.3.0.0.0, you could create a LOPA to assess SIL value for an Instrumented Function from the SIL Analysis. In V4.3.0.0.0, you can create and manage LOPAs using the Layers of Protection Analysis module. To assess the SIL value for an Instrumented Function using LOPA, you can create a LOPA Assessment record for the Instrumented Function by linking the LOPA.

When you upgrade the module to V4.3.0.0.0, LOPA Assessment records are created automatically by copying values from the existing LOPAs. The LOPA Assessments are then linked to the corresponding Instrumented Functions and LOPAs. The following table contains the fields in LOPA that are mapped to fields in LOPA Assessment:

Values in the Following Fields in the LOPA...Copied to the following fields in the LOPA Assessment
LOPA ID LOPA Assessment ID
LOPA ID Linked LOPA ID
Entity KeyLinked LOPA Key
Frequency of Initiating Event Frequency of Initiating Event
Mitigated Consequence Frequency Mitigated Consequence Frequency
Required Mitigated Consequence Frequency Required Mitigated Consequence Frequency
Required PIF PFD Required Probability of Failure
Required PIF Risk Reduction Factor Risk Reduction Factor (RRF)
Unmitigated Consequence FrequencyUnmitigated Consequence Frequency
Total IPL PFDTotal IPL PFD
Calculated SILSelected SIL Level

Also, in V4.3.0.0.0, the Hazards Analysis Safeguard records is used to store the details of Independent Layer of Protection. Hence, when you upgrade to V4.3.0.0.0, Hazards Analysis Safeguards records are created by copying values from the Independent Layer of Protection records associated with the existing LOPA records. The Safeguards created are then associated with the corresponding LOPA.

Values in the Following Fields in the Independent Layer of Protection ...Copied to the following fields in the associated Hazards Analysis Safeguard
PFDPFD
IPL IDSafeguard ID
TypeIPL Type

In V4.3.0.0.0, for each Safeguard, IPL Checklist records are created to store your selection for the criteria that are used to determine if a Safeguard is an IPL. When you upgrade to V4.3.0.0.0, for each previously existing Independent Layer of Protection record, IPL Checklist records are created and associated with the corresponding Safeguard in V4.3.0.0.0.

Supported SERH/SERHx Library Versions

The following table lists the supported versions of the SERH/SERHx library provided by Exida.

APM VersionexSILentia Calculation Engine v3exSILentia Calculation Engine v4SERH VersionSERHx Version
APMV5.0.0.0.0v3.0.5.3v1.02022.01.012022.01.01
APM V4.5.1.0.0v3.0.5.3v1.02020.04.012020.04.01
APM V4.5.0.0.0v3.0.5.3v1.02019.04.012019.04.01
APM V4.4.0.0.0v3.0.5.3N/A2020.1.01 N/A
APM V4.3.0.0.0v3.0.5.3N/A2017.4.01N/A
APM V4.2.0.0v3.0.5.3N/A2015.3.01N/A
APM V4.1.0.0v3.0.5.1N/A2015.2.01N/A
APM V3.6.0.11.3 v3.0.5.1N/A2012.4.01N/A