V3.6.1.6.0 Release Notes

V3.6.1.6.0

Datasets

Table 1. Resolved Issues
DescriptionTracking ID
Previously, when you saved a new dataset on the Dataset Editor page and then viewed it in the Meridium APM Catalog, the Owner field was empty. This issue has been resolved.TFS338573

Documentation

Table 2. Resolved Issues
DescriptionTracking ID
Previously, in the Meridium APM Supported Software and Devices topic and the About Devices in Thickness Monitoring topic, the 37DL and 38DL Plus Ultrasonic Thickness Gage devices did not include both the previous (Panametrics) and current (Olympus) brand names. This issue has been resolved. Now the device names are listed as follows:
  • Olympus (Panametrics) 37DL Plus Ultrasonic Thickness Gage
  • Olympus (Panametrics) 38DL Plus Ultrasonic Thickness Gage
TFS331925

Installation

Table 3. Resolved Issues
DescriptionTracking ID
Previously, the Meridium APM distribution package included a 32-bit installer that was not required for installation. This issue has been resolved.TFS336859

mobileAPM

Table 4. Resolved Issues
DescriptionTracking ID
Previously, when you added a Comment to a Measurement Location, the window that appeared displayed only the Action aligned with the Measurement Location Limit Value with which the current reading value was associated. This issue has been resolved. Now, the window displays all Actions defined in the Limit Values section for the Measurement Location.TFS332707
Previously, when you resized the Asset Hierarchy Tool and decreased the size of the window, the Application Server and Datasource names were truncated. This issue has been resolved.TFS290215

Operator Rounds (OPR)

Table 5. Resolved Issues
DescriptionTracking ID
Previously, when you scanned a tag to unlock a measurement location using an Ecom i.roc handheld device with a low frequency reader, the device stopped responding. This issue has been resolved.TFS315068

Production Loss Analysis (PLA)

Table 6. Resolved Issues
DescriptionTracking ID
Previously, when you sorted a column in ascending or descending order on the Production Event Management page, columns containing numeric data or dates were sorted incorrectly. This issue has been resolved.TFS338102
Previously, when you accessed PLA from a Meridium APM Framework machine and attempted to open a Production Unit record, the specified data source was not found. This issue has been resolved.TFS323932
Previously, users belonging to the MI Production Loss Accounting Manager Security Group received an error stating that they did not have update privileges when they tried to access Production Plan or Production data. This issue has been resolved.TFS323703

Risk Based Inspection (RBI)

Table 7. Enhancements and New Features
DescriptionTracking ID
The performance of bulk calculation of RBI 581 Risk Analyses has been improved. It now takes less time to calculate an analysis. In addition, changes made in Risk Based Inspection 581 in V3.6.0.12.0 and later have been included in V3.6.1.6.0.TFS316372
Table 8. Resolved Issues
DescriptionTracking ID
Previously, when you calculated an RBI PRD Analysis associated with a Criticality Leak Deg. Mech. Eval. or Criticality Over Pressure Deg. Mech. Eval., the Probability of Leak field or the Probability of Failure field calculations may have been incorrect. This issue has been resolved.TFS327946
Previously, when you calculated an RBI PRD analysis, the Recommended Inspection Interval was calculated incorrectly and exceeded the maximum intervals defined for each Risk Category. This issue has been resolved.TFS324645
Previously, when you modified Meridium APM baseline security for RBI users by removing update privileges on the PV Stress, Piping Stress, or Tank Stress reference tables, the RBI Allowable Stress value was not calculated as expected. This issue has been resolved.TFS312225

RBI 580

Table 9. Resolved Issues
DescriptionTracking ID
Previously, if you assigned an inspection that satisfied the following conditions to a Criticality Over Pressure Deg. Mech. Eval. record, then the value in the Probability of Failure on Demand field increased instead of decreasing or remaining the same:
  • The inspection was performed within one year of the previous inspection.
  • The value in the Over Pressure Test Results field was Pass and the value in the Weibull Updated Characteristic Life field decreased.

    -or-

    The value in the Over Pressure Test Results field was Fail and the value in the Weibull Updated Characteristic Life field increased.
Similarly, if you assigned an inspection that satisfied the following conditions to a Criticality Leak Deg. Mech. Eval. record, then the value in the Probability of Leak field increased instead of decreasing or remaining the same:
  • The inspection was performed within one year of the previous inspection.
  • The value in the Leak Test Results field was No Leak and the value in the Weibull Updated Characteristic Life field decreased.

    -or-

    The value in the Leak Test Results field was Leak and the value in the Weibull Updated Characteristic Life field increased.
These issues have been resolved. If the inspection satisfies the aforementioned conditions, then the previous inspection date is used to calculate the value in the Weibull Updated Characteristic Life field.
TFS324646

RBI 581

Table 10. Resolved Issues
DescriptionTracking ID
Previously, the RBI Criticality Analysis Allowable Stress value was not calculated when the Material Grade had an associated Material Type in the Piping Stress family. This issue has been resolved.TFS324791

Root Cause Analysis (RCA)

Table 11. Resolved Issues
DescriptionTracking ID
Previously, when a team member was removed from the RCA Analysis Team, all RCA Preserve Item records were assigned to the Principal Analyst instead of the records previously assigned to the team member who was removed. This issue has been resolved.TFS313412

Thickness Monitoring

Table 12. Resolved Issues
DescriptionTracking ID
Previously, when your Security User account was associated with a Metric UOM Conversion Set and you uploaded data from a supported device, reading values in the list of datapoints on the Devices page may have been incorrectly displayed in inches. This issue has been resolved.TFS327712