Fourth Quarter of 2021

Release Date: December 17, 2021

This topic provides a list of product changes released for this module on this date.

Table 1. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, in SIL Analysis, when you defined a negative value for Trip Point in the Proof Test Template Details and performed a Proof Test task, the calculated result appeared as Fail in the Pass/Fail column. This issue has been resolved.DE171455
Previously, for a Protective Instrument Loop, when you set a Logic Solver device (for example, Triconex Tricon) for which one or more failure rates were not defined in the Analog Input, Analog Output, Digital Input, or Digital output modules, an error appeared. This issue has been resolved.DE170898
Previously, when you added a custom device with a linked equipment to the Final Element or a Sensor, and then attempted to update the related sensor group or final element group, an error occurred. This issue has been resolved.DE168136

Release Date: October 8, 2021

This topic provides a list of product changes released for this module on this date.

Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you attempted to add a team member to an SIL Analysis, users across all sites were displayed. This issue has been resolved. Now, only the users linked with the site of the SIL Analysis are displayed.US483318
Previously, in the Definition tab of the SIL Verification section, if IEC 61508 was selected from the drop-down list of the Test Architecture Constraints, SIL-Achieved value was not calculated correctly for a Protective Instrument Loop. This issue has been resolved.DE165806
Previously, for a Protective Instrument Loop that used the ExSILentia V4 Calculation Engine, the SIL-Achieved and Architectural Constraints fields were not displayed correctly. This issue has been resolved.DE164599
Previously, when you attempted to save a Protective Instrument Device, if any error occurred, an incorrect error message was displayed. This issue has been resolved.DE164133
Previously, when you created a new or updated an existing SIL Analysis, Instrumented Function, Safety Instrumented System, or Protective Instrument Loop Element, the Modified By and the Modified Date fields did not display correct values. This issue has been resolved.DE164107
Previously, the following fields in LOPA did not display the accurate values:
  • Mitigated Consequence Frequency
  • Unmitigated Consequence Frequency
  • Required PIF Risk Reduction Factor
This issue has been resolved. Now, these fields are displayed in exponential value, if the output has more than 15 decimal digits.
DE162635
Previously, when a user assigned to SIS Administrator or SIS Engineer security group attempted to create a Risk Assessment Recommendation, an error occurred. This issue has been resolved.DE162163
Previously, in the Risk Assessment Recommendation datasheet, the Interval and Interval Units fields appeared in the Alert tab instead of the General Information tab. This issue has been resolved.DE161964
Previously, when you created a new or updated an existing SIS Proof Test Template, SIS Proof Test Template Detail, or SIS Proof Test, the following fields were not populated with the correct values:
  • Modified By
  • Modified Date
  • Test ID

This issue has been resolved.

DE161957
Previously, after importing a Protected Instrument loop into the APM, when you attempted to modify the Protected Instrument loop record, an error occurred. This issue has been resolved.DE160394
Previously, when you updated the state of a Protective Instrument Loop to a state other than Design, the fields in the Protective Instrument Device datasheet were still available for editing. This issue has been resolved.DE160302
Previously, when you used the Import from Exida functionality in SIL Analysis, the performance of the APM was not as expected if there were many analyses present in APM. This issue has been resolved.DE158244
Previously, in the SIL Assessments, when you entered values for the Probability of Failure on Demand (PFD) and Risk Reduction Factor (RRF) fields, the associated SIL level value was not displayed correctly. This issue has been resolved.DE157711
Previously, when you attempted to promote a recommendation to ASM, a blank message appeared in the following scenarios:
  • If the Recommendation Headline was missing and you attempted to Promote to ASM.
  • If the Recommendation was Accepted by ASM and you attempted to promote it again.

These issues have been resolved.

DE157630
Previously, when you entered values for the Risk Reduction Factor (RRF) field for an External SIL assessment, an incorrect validation error occurred. This issue has been resolved.DE157629
Previously, Promote To ASM operation failed for Recommendations in which the Instrumented Function was linked to a LOPA Assessment or External Assessment. This issue has been resolved.DE157627
Previously, in SIL verification, when you selected a sensor, a final element, or a logic solver device for a protective instrument loop, an error may have occurred. This issue has been resolved.DE157621
Previously, when you used the Export to Exida functionality in SIL Analysis, the performance of the APM was not as expected, if there were many analyses present in APM. This issue has been resolved.DE157620