V4.3.0.6.5 Release Notes

V4.3.0.6.5

This topic provides a list of product changes included in this patch.

Family Policies

DescriptionTracking ID
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
  • Duplicate predecessor entity keys and the output of the Create Entity node as the successor entity key.
  • The collection output of a Create Entity node as the predecessor or successor entity key.
This issue has been resolved.
  • DE94996
  • DE94795
Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved.DE94085
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
  • The policy took a long time to load.
  • The policy did not load.
This issue has been resolved.
DE93538
Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your GE Digital APM user account instead of the policy time zone. This issue has been resolved.DE91644

Foundation

Life Cycle Costing

DescriptionTracking ID
To enhance accuracy in the Cost Data grid, when creating a new Resource for or adding an existing Resource to a Cost Element, the values in the Year <Number> columns (after the Year 0 column) now reflect estimations based on inflation. The escalated inflation values in the Year <Number> columns are based on the Annual Escalation Rate field in the Definitions section. US256920

Policy Designer

DescriptionTracking ID
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
  • Duplicate predecessor entity keys and the output of the Create Entity node as the successor entity key.
  • The collection output of a Create Entity node as the predecessor or successor entity key.
This issue has been resolved.
  • DE94996
  • DE94795
Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved.DE94085
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
  • The policy took a long time to load.
  • The policy did not load.
This issue has been resolved.
DE93538
Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your GE Digital APM user account instead of the policy time zone. This issue has been resolved.DE91644

Reliability Analytics

DescriptionTracking ID
Previously, when viewing the Reliability Distribution Analysis Report for an analysis for which a PM Optimization had been performed, the values entered for the Planned Cost and Unplanned Cost did not appear in the report. This issue has been resolved. DE93870
Previously, when creating a new Risk record in System Reliability, if you saved the new Risk record multiple times, a Risk record was created each time that you selected the Save button (). This issue has been resolved.DE92376
To enhance analysis accuracy, when viewing the details of a Scenario in System Reliability, the following Distribution Types can now be selected for TTF and TTR Distributions in the Risks section and the Show Risk/Mitigated Actions grid:
  • Generalized Extreme Value Distribution
  • Gumbel Distribution
  • Triangular Distribution
US271178
To enhance analysis accuracy, when viewing the details of a Spare Application in a Spares Analysis, the following Distribution Types can now be selected in the Update Distribution section:
  • Generalized Extreme Value Distribution
  • Gumbel Distribution
  • Triangular Distribution
US271175

Reliability Centered Maintenance

DescriptionTracking ID
To enhance usability and to allow you to incorporate related Failure Mode Asset ID values that make family records unique, you can now include the related Asset ID value of the Failure Mode family in the following worksheets of the Reliability Centered Maintenance (RCM) Data Loader:
  • Failure Effects Worksheet
  • Failure Modes Worksheet
  • Recommendations Worksheet
DE94412
Previously, if you tried to promote an RCM Analysis with multiple assets that contained recommendations, only the recommendations in the first asset were promoted. This issue has been resolved.DE93758

Root Cause Analysis

DescriptionTracking ID
Previously, in the Create Verification pane, if you selected a team member in the Assigned To drop-down list box, that team member did not receive email notifications when the assigned task was due or overdue because the scheduled email job was not properly executed. This issue has been resolved.US291622
The values in the Alerts drop-down list box in the Add/Edit Tracking Items window are now populated with the Human Resource Record of the team members assigned to the specified RCA. US254549

Rounds Data Collection

DescriptionTracking ID
Previously, if you entered a reading value that satisfied a condition of a checkpoint other than the first condition, successor conditional checkpoints did not appear as expected. This issue has been resolved.DE96113
Previously, if you marked a Route done in the Rounds Data Collection Overview page while the workspace for that Route was open, when you navigated back to the workspace for that Route, the Route reappeared in the Due Items or Overdue Items section in the Rounds Data Collection Overview page. This issue has been resolved.DE92165
Previously, if you changed the GE Digital APM password for a user, and that user then performed a sync operation on a Windows Mobile device, the user was unable to sign in to the GE Digital APM mobile application on a Windows Mobile device with the new GE Digital APM password. This issue has been resolved.DE88896

Rounds Designer

DescriptionTracking ID
Previously, if you deleted a checkpoint that contained a successor conditional checkpoint, and then attempted to add the successor conditional checkpoint to a Route by selecting the Add button (), the conditional checkpoint did not appear in the Existing ML / LR window. This issue has been resolved.DE93915

Risk Based Inspection

DescriptionTracking ID
Previously, when you calculated an RBI Criticality Analysis for a Heat Exchanger Bundle component, the following incorrect validations were performed:
  • The values in the Operating Pressure and Operating Temperature fields, which were mapped from the shell side values on the RBI component were compared with the values in the Design Pressure and Design Temperature fields respectively, which were mapped from the channel side values from the component.
  • The values in the Tube Operating Press Channel and Tube Operating Temp Channel fields were not compared with the design values.
These issues have been resolved. Now, the following validations are performed:
  • The values in the Operating Pressure and Operating Temperature fields that are mapped to the shell side values on the RBI Component are not compared with the design values.
  • The values in the Tube Operating Press Channel and Tube Operating Temp Channel fields are compared with the values in the Design Pressure and Design Temperature fields respectively.
DE94266

Thickness Monitoring

DescriptionTracking ID
Previously, if the number format of the user account that is used to run the Meridium Device Service is different from the number format of the English (United States) culture, when you received thickness measurement data from a TM Datalogger, the measurement values were incorrect. This issue has been resolved.DE92436