V3.6.1.7.3 Release Notes

V3.6.1.7.3

This topic provides a list of product changes released for this module on the dates listed below.

Asset Criticality Analysis

DescriptionTracking ID
Previously, in the Risk section of the Analysis Summary page, if you belonged to an ACA Security Group whose family-level privileges for the Risk Assessment family were limited to View, and you accessed a Risk Assessment whose assessment had the Not Applicable check box selected, an error occurred. This issue has been resolved.TFS369020
Previously, in the Systems section, if you accessed a system containing 3,000 or more assets and then attempted to modify that system, a process timed out. This issue has been resolved.TFS362605

Metrics and Scorecards

DescriptionTracking ID
Previously, when you attempted to access a Key Performance Indicator (KPI) from the View <Name of the Scorecard> page, the details of a different KPI appeared intermittently in the View Key Performance Indicator page than the details of the KPI that you wanted to access. This issue has been resolved.TFS366792

mobileAPM

DescriptionTracking ID
Previously, on an iOS 12 device, when you attempted to access a Route or checkpoint by scanning the barcode assigned to it, an error occurred, and you were unable to scan the barcode. These issues have been resolved.TFS372729
The GE Digital APM mobile application now supports iOS 12 devices.TFS372060
To improve usability, in the Area page, in the Inspection section, you can now filter Routes:
  • By keyword using the Keyword Search box.
  • By due date using the Filter button ().
Additionally, you can now subscribe to or unsubscribe from all filtered Routes.		TFS368057

Risk Based Inspection - RBI 581

Table 1. Enhancements and New Features
DescriptionTracking ID
The following enhancements have been made in RBI 581 Risk Analysis calculation:
  • The Total Damage Factor calculation has been enhanced to adhere to Addendum 1 of the API RBI 581 specification. The Total Damage Factor calculation now takes the sum of the external damage factor and internal damage factor for the following scenarios:
    • External Damage is localized and Internal Damage is general.
    • Internal Damage is localized and External Damage is general.
    Previously, the Total Damage Factor calculation only considered the maximum of the external and internal damage factor.
  • The following fields in the RBI 581 Consequence Evaluation family are now populated upon calculation with the values from API RBI 3rd Edition Addendum 1 when the component type is not Storage Tank or Tank Bottom:
    • Release Hole Diameter (Large)
    • Release Hole Diameter (Medium)
    • Release Hole Diameter (Rupture)
    • Release Hole Diameter (Small)
  • The Leak Duration Max calculation now adheres to API RBI 3rd Edition Addendum 1. As a result, the values in the following fields may change upon calculation:
    • Release Mass (Large)
    • Release Mass (Medium)
    • Release Mass (Rupture)
    • Release Mass (Small)
  • TFS370924
  • TFS370923
  • TFS370922
  • TFS370920
The performance of the RBI 581 Risk Analysis calculation has been improved. To facilitate this enhancement, the policies and R Scripts that were previously used to calculate consequence of failure are no longer used.
Note: The policies and R Scripts used to calculate thinning supplements and cracking susceptibility for damage mechanisms that belong to RBI 581 Thinning and Lining Evaluation, RBI 581 Cracking Damage Evaluation, and RBI 581 External Cracking Damage Evaluation are still used.
TFS370923
Table 2. Resolved Issues
DescriptionTracking ID
Previously, if you modified the value in a field that was used to calculate the value in the Inventory Component Mass field in an RBI 581 Consequence Evaluation record, then the value in the Inventory Component Mass field was not updated even after you calculated the analysis. This issue has been resolved.TFS370922

Root Cause Analysis

DescriptionTracking ID
Previously, if a user with a culture setting other than English accessed the My PROACT page after creating a new record, the values in the Data Category Type field were not localized. This issue has been resolved.TFS364216

Tools

DescriptionTracking ID
Previously, when creating a configured explorer via the Definable Explorer Wizard, if you chose to specify family sorting, items in the Specify Family Sorting list were unnecessarily duplicated. This issue has been resolved.TFS371287