V3.6.1.7.X Patch Release Notes
V3.6.1.7.5
This topic provides a list of product changes included in this patch.
RBI 581
| Description | Tracking ID |
|---|---|
| Previously, release rate calculation in RBI 581 Consequence Evaluation was based on the value in Release Fluid Phase field of the related RBI 581 Risk Analysis. This issue has been resolved. Now, the Release Rate calculation is based on the Initial Fluid Phase field value in RBI 581 Risk Analysis. | TFS394258 |
V3.6.1.7.4
This topic provides a list of product changes included in this patch.
mobileAPM
| Description | Tracking ID |
|---|---|
| Previously, if the Close Date and Reading Taken Date fields were set to Coordinated Universal Time, and if your time zone in mobileAPM differed from the time zone of the server to which you uploaded a reading in a completed Route, those fields displayed an incorrect time. This issue has been resolved. | TFS374643 |
| Previously, if your culture setting was a variant of English other than English (United States), when you attempted to create a recommendation whose Target Completion Date value contained a value for the day that was greater than 12, the recommendation was not created. This issue has been resolved. | TFS373169 |
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
| Description | Tracking 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
| Description | Tracking 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
| Description | Tracking 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:
| TFS368057 |
).Risk Based Inspection - RBI 581
| Description | Tracking ID |
|---|---|
The following enhancements have been made in RBI 581 Risk Analysis calculation:
|
|
| 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 |
| Description | Tracking 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
| Description | Tracking 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
| Description | Tracking 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 |
V3.6.1.7.2
This topic provides a list of product changes released for this module on the dates listed below.
mobileAPM
| Description | Tracking ID |
|---|---|
| Previously, if the Close Date and Reading Taken Date fields were set to Coordinated Universal Time, and if your time zone in mobileAPM differed from the time zone of the server to which you uploaded a reading in a completed Route, those fields displayed an incorrect time. This issue has been resolved. | TFS374643 |
| Previously, in the localized version of mobileAPM, when you accessed a Health Indicator, navigated to a different page, and then accessed the Health Indicator again, the date format changed. This issue has been resolved. | TFS370664 |
| Previously, the date format in the date fields in an Operator Rounds Recommendation record was not updated based on the culture setting. This issue has been resolved. | TFS370072 |
| Previously, in the localized version of mobileAPM, the text was not translated. This issue has been resolved. | TFS370071 |
| Previously, the font size of the text in the More Information field in a Measurement Location record was too small. This issue has been resolved. | TFS369929 |
| Previously, after you marked a Route done and refreshed the page, an error occurred. This issue has been resolved. Now, in this scenario, the Route History appears. | TFS369928 |
V3.6.1.7.1
This topic provides a list of product changes released for this module on the dates listed below.
Risk Based Inspection
| Description | Tracking ID |
|---|---|
| Previously, the baseline RBI Risk Matrix could be customized by modifying values in the corresponding Risk Matrix record and the records to which it was linked. However, you were limited to using five Probability records and five Consequence records, which restricted the size of the RBI Risk Matrix and prohibited adding additional columns or rows. This issue has been resolved. Now, in compatible Meridium APM environments, you can select a larger 8x8 RBI Risk Matrix that accommodates eight Probability and eight Consequence records. Before using an 8x8 RBI Risk Matrix, however, contact GSS to configure the Meridium APM environment to ensure that the RBI Risk Matrix appears and functions as expected. | TFS365030 |