V4.3.0.4.0 Release Notes

Advanced Search

Table 1. Resolved Issues
Description	Tracking ID
Previously, if you selected the same family in the Family and Linked To boxes, an advanced search returned no results even if results should have been returned. This issue has been resolved.	TFS350742

Asset Criticality Analysis (ACA)

Table 2. Enhancements
Description	Tracking ID
To enhance usability, if you modified the ACA All query, the numbers displayed in the tabs in the ACA Overview page now reflect the results of the modified query.	TFS348579

Table 3. Resolved Issues
Description	Tracking ID
Previously, when linking Equipment or Functional Location records to an ACA System, the selected Equipment or Functional Location records were erroneously added to a different ACA System than the ACA System that was selected. This issue has been resolved.	TFS353573

Table 4. Deferred Features
Description	Tracking ID
Promoting ACA Systems to RCM, FMEA, and ASM.	TFS177103

Asset Health Manager (AHM)

Table 5. Resolved Issues
Description	Tracking ID
Previously, if you did not have an Operator Rounds license, you did not have access to the Checkpoint or Measurement Location families, and when you accessed the Health Indicator Source Management page, health indicators for Measurement Locations did not load as expected. This issue has been resolved. Now, the license policy is updated to include the Checkpoint family for all license types.	TFS345925
Previously, for a Health Indicator, when you refreshed any of the following workspaces, the count of records in the Reading History workspace was incorrect: Configuration Reading History Trend Chart As a result, the chart in the Trend Chart workspace appeared incorrectly. This issue has been resolved.	TFS348033
Previously, for a Health Indicator, in certain scenarios, the chart in the Trend Chart workspace appeared incorrectly. This issue has been resolved.	TFS348033
Previously, for a Health Indicator, when you modified the date range using the Filter button (), and then selected the Apply button, the data in the Reading History and Trend Chart workspaces was not updated. This issue has been resolved.	TFS347746
Previously, when a Health Indicator did not contain a reading for the specified date range, a message did not appear in the Trend Chart workspace to indicate that there was no data. This issue has been resolved.	TFS347746
Previously, on the Health Summary page, in the Events section, all the events associated with the selected asset did not appear in the grid. As a result, the number on the Eventstab was incorrect. This issue has been resolved.	TFS347544

Table 6. Deferred Features
Description	Tracking ID
Asset Hierarchy sorting and filtering based on health indicator status, filtering based on health indicator family field values, and filtering based on assets with or without health indicators.	TFS91046 TFS86625 TFS86430
The display of health indicator statuses in Asset Hierarchy.	TFS86796

Asset Strategy Implementation (ASI)

Table 7. Enhancements

Description

Tracking ID

To enhance usability, if you modify the ASI Overview Filter Query, the numbers displayed in the tabs in the ASI Overview page now reflect the results of the modified query.

TFS348579

In the Manage Actions section in ASI, you can now add multiple actions from different Asset Strategies to an ASI package at the same time.

TFS348542

To enhance usability, the Interval and the Interval Units columns have been added to the grid on the Manage Actions section of the ASI Package page.

TFS347810

When using the Apply Updates feature in ASM or ASI to update ASM Action intervals to the corresponding Maintenance Plan intervals in ASI, the following values are now updated automatically.


Plan type	Value update by Maintenance Plan interval
Single Cycle Plans	Cycle for the corresponding Maintenance Plan
Multiple Counter Plans	Cycle for the corresponding time-based Maintenance Plan
Strategy Plans	Cycle for the corresponding Maintenance Package

TFS347029

The SAP import feature for ASI has been enhanced to allow for customization. When importing items from an external SAP system, you can now modify the import process to include custom fields or to execute custom logic.

TFS302117

Table 8. Resolved Issues
Description	Tracking ID
Previously, in the Maintenance Plans workspace of the ASI Overview page, the ID column did not contain hyperlinks to the implemented SAP systems. This issue has been resolved.	TFS353153
Previously, if you configured the rules for a field that used the ValueHelperDialog and then compiled the database, an error occurred. This issue has been resolved.	TFS349680
Previously, when you attempted to update the cycle of a Multiple Counter plan that had been imported from SAP, an error occurred indicating that the cycle contained invalid Time Units. This issue has been resolved.	TFS347899
Previously, if you did not have the SAP Work Management license and attempted to search for an SAP record in ASI, an error occurred. This issue has been resolved. The SAP Work Management license is no longer required to search for SAP records in ASI.	TFS338141

Table 9. Deferred Features
Description	Tracking ID
Creating implementation roles and filtering the WMI tree by each role.	TFS243573
Using a link to manage the object list records that are linked to maintenance item records represented by the selected node.	TFS238443
The option to exclude child items when copying Work Management Items.	TFS147790
Managing asset and action assignments when executing copy/paste operations.	TFS144110
Searching in SAP for the standard text value that you want to append to the value in the Long Text field of a Maintenance Item record.	TFS117765

Asset Strategy Management (ASM)

Table 10. Enhancements
Description	Tracking ID
To enhance usability, while applying or approving a template in ASM, the percentage of completion now appears at the top of the page.	TFS351506 TFS227555
To enhance usability, if you modify the ASM – Filter Query, the numbers displayed in the tabs in the ASM Overview page now reflect the results of the modified query.	TFS348579
To enhance usability, the Interval and the Interval Units columns have been added to the grid on the Implement Actions page.	TFS347810
When sending an EAM Work Request for an Action or group of Actions in ASM, a link corresponding to the associated EAM Work Request now appears in the Implementationcolumn of the grid in the Implement Actions section of the Strategy Details page.	TFS347761
When viewing an analysis in Asset Strategy Management (ASM), you can now navigate to the Life Cycle Cost Analysis Overview page to view any existing LCC Analyses associated with the Asset Strategy.	TFS345682
When viewing an asset strategy in Asset Strategy Management (ASM), you can now navigate to the Reliability Analytics Overview page to view existing Reliability Analyses associated with the asset for the strategy.	TFS345680
To enhance usability when using mass state management in a System or Unit strategy, the percentage of completion now appears in the Review Strategy workspace of the Strategy Details page.	TFS274188

Table 11. Resolved Issues
Description	Tracking ID
Previously, when using the ASM Data Loader, when you imported data with an invalid Field ID, the data import job succeeded; however, the data loaded for the Field ID was invalid, and no warning message appeared in the error log. This issue has been resolved. Now, if the data import job encounters an invalid Field ID, a warning is recorded in the error log.	TFS351418
Previously, if you applied updates for an ASM Action that was linked to an Asset Strategy Implementation Work Management Item (ASI WMI), the state configuration of the associated ASI WMI package was not updated. This issue has been resolved. Now, if you apply updates for an ASM Action that is linked to an ASI WMI, the state configuration of the associated package updates as expected.	TFS347623
Previously, with an active Asset Strategy Management license, you were unable to access the Action Task Mapping workspace from the ASM Admin page unless you also had active Calibration and Inspection licenses. This issue has been resolved.	TFS346583
Previously, if you opened an Asset Strategy and navigated away from that Asset Strategy before the page finished loading, an error occurred. This issue has been resolved.	TFS335976

Table 12. Obsolete Features
Description	Tracking ID
To simplify the process of applying templates in ASM, you can no longer manually add controlled strategies in the Controlled Strategies workspace of the Strategy Details page. Now, all the steps required to apply a template are performed via the Apply Template window. Also, on the Controlled Strategies workspace, the Delete button () has been replaced with the Unlink button ().	TFS351505

Table 13. Deferred Features
Description	Tracking ID
Migrating strategies between databases.

Asset Strategy Optimization (ASO)

Table 14. Resolved Issues
Description	Tracking ID
Previously, if you accessed the Risks or the Actions workspace for an Analysis Summary, the icons in the Status column did not render properly. This issue has been resolved.	TFS352691

Table 15. Deferred Features
Description	Tracking ID
Optimizing Actions.	TFS112125

Calibration Management

Table 16. Enhancements
Description	Tracking ID
For Calibration Events (i.e., Calibration records) that were created in a version earlier than V4.2.0.0, if the Calibration Closed check box was selected, then, when you upgrade to V4.3.0.4.0, the state of the Calibration is modified to Approved.	TFS351201
In the Calibration Management page, in the Calibration Profiles section, the Type column now displays the value in the Device Type field in each Calibration Profile. In addition, when you access a Calibration Profile, in the Linked Assets section, the Type column now displays the value in the Object Type field in each Equipment record.	TFS351198
After receiving data from a calibrator, if creating a Calibration Event fails, the error message now specifies the reason for failure.	TFS343848

Table 17. Resolved Issues
Description	Tracking ID
Previously, when you unlinked a Calibration Task from a Calibration Template, the Calibration Task was also erroneously unlinked from the Equipment. This issue has been resolved.	TFS353304
Previously, in a Calibration Template, Analog record used in a GE Druck calibrator, if the value in the Temperature Element Type was NI100 (672), PT100 (385), or PT50 (385), the RTD Wiring Configuration field was not enabled. This issue has been resolved.	TFS351275
Previously, in a Calibration Profile, when you attempted to link a Calibration Task to an Equipment record, an error occurred. This issue has been resolved.	TFS350385
Previously, if you attempted to link a Calibration Template, Analog record to an asset, an error occurred. This issue occurred only if the Calibration Template, Analog record was linked to a Calibration Profile, and contained the value None in the Temperature Element Type field.	TFS350326
Previously, when you attempted to send a Calibration Task to a calibrator, an error occurred. This issue occurred only if the associated asset was linked to another Calibration Task whose value in the Template ID field was blank. This issue has been resolved.	TFS350325
Previously, on the Calibration Management Overview page, in the Calibration Profiles section, the count of linked assets in the Linked Assets Count column was incorrect. Instead of the total number of only the Equipment records linked to the associated Calibration Templates, the total number of the Equipment, Functional Location, and other asset records linked to the Calibration Templates appeared. This issue has been resolved. To facilitate this fix, the following query has been modified: \Public\Meridium\Modules\Calibration Management\Queries\Applied Profiles Count.	TFS350107
Previously, in the Linked Assets section in a Calibration Profile, the count of the linked assets was incorrect. This issue has been resolved. To facilitate this fix, the following query has been modified: \Public\Meridium\Modules\Calibration Management\Queries\Calibration Profile Linked Asset Query.	TFS350107
Previously, in the Calibration Management Overview page, in the Calibration Profiles section, duplicate records appeared in the grid. This issue occurred only if each Calibration Template in the Calibration Profile was in a different state. This issue has been resolved. To facilitate this fix, in the Calibration Profiles section, the State column has been removed from the grid.	TFS350106
Previously, the MI Foundation User Security Role was assigned the MI Calibration Administrator and MI Calibration User Security Groups. As a result, a user who was assigned the MI Foundation User Security Role could use Calibration Management. This issue has been resolved. Now, the MI Foundation User Security Role is not assigned the MI Calibration Administrator or the MI Calibration User Security Group.	TFS349848
Previously, in a Calibration Template, Analog record that contained the value Temperature in the Output Type field, if you selected the value None in the Temperature Element Type field, an error occurred when you attempted to save the record. This issue has been resolved.	TFS349380
Previously, if you attempted to link a Calibration Template, Analog record to an asset, an error occurred. This issue occurred only if the Calibration Template, Analog record was linked to a Calibration Profile, and contained the value None in the Temperature Element Type field. This issue has been resolved.	TFS349265
Previously, you could delete a Calibration Strategy that was used in a Calibration Profile, Calibration Template, or a Calibration Event. This issue has been resolved.	TFS348517
Previously, for a profile template linked to an asset, if you selected Restore Template Defaults on the Edit Default from Template window, an error occurred. This issue occurred only if the Calibration Profile was not associated with a master template. This issue has been resolved. Now, the Restore Template Defaults button appears only if the Calibration Profile is associated with a master template.	TFS348136
Previously, if you attempted to delete a Calibration, Functional Test record, an error occurred. Additionally, if you attempted to delete a Calibration, Analog record, although the record was deleted from the database, an error message appeared, and the record still appeared in the Calibration Events section. These issues have been resolved.	TFS346874

Table 18. Restored Features
Description	Tracking ID
If receiving data from a calibrator fails, the error message now specifies the reason for failure.	TFS343848

Table 19. Obsolete Features
Description	Tracking ID
On the Calibration Management Overview page, in the Calibration Profiles section, the State column has been removed.	TFS350106
The following fields in the Calibration Setup Defaults family have been removed from the datasheet because they are no longer used: Default Analog Strategy Default Discrete Strategy	TFS347138

Table 20. Deferred Features
Description	Tracking ID
Automated Calibration using Beamex and Meriam documenting process calibrators. Note: Automated calibration using Beamex documenting process calibrators, Beamex MC5 and Beamex MC6, is supported using Beamex Business Bridge (B3) Version 1 (1.2.0) software for Beamex CMX Calibration software.	TFS61319 TFS61334

Configuration Manager

Table 21. Deferred Features
Description	Tracking ID
Global number and date format.	TFS160148
Global Preferences- Background Colors.	TFS65297

Data Loaders

Table 22. Enhancements
Description	Tracking ID
The Rounds Route and Rounds Template data loader workbooks now support checkpoint conditions. To facilitate this enhancement, the following updates have been made to these workbooks: New Checkpoint Condition worksheets have been added to the Rounds Route and Rounds Template data loader workbooks. New fields have been added to the following worksheets: The Checkpoint Template Sequence worksheet in the Rounds Template workbook The Measurement Location worksheet in the Rounds Route workbook	TFS349035

Table 23. Resolved Issues
Description	Tracking ID
Previously, when you used the Rounds Route data loader workbook to create a Route, in the Measurement Location worksheet, if you entered a value in the Template field but did not enter a value in the Template Group Key field, the checkpoint was not created. This issue has been resolved.	TFS353864
Previously, when you used the Rounds Route data loader workbook to create a Route, checkpoints were not linked to assets as expected. This issue has been resolved.	TFS353571

Data Permissions

Table 24. Enhancements
Description	Tracking ID
You can now access the Data Permissions feature from the Configuration Manager page instead of the Security Manager page.	TFS353742

Export

Table 25. Resolved Issues
Description	Tracking ID
Previously, when you attempted to export a security group that was associated with a family for which the license was inactive, an error occurred. This issue has been resolved.	TFS346578
Previously, when you exported a security group or role, the data permissions that were applied to the security group or role were not exported. This issue has been resolved.	TFS342428

Failure Modes and Effects Analysis (FMEA)

Table 26. Enhancements
Description	Tracking ID
To enhance usability, if you modified the FMEA Overview Filter Query, the numbers displayed in the tabs in the FMEA Overview page now reflect the results of the modified query.	TFS348579

Table 27. Resolved Issues
Description	Tracking ID
Previously, when you imported data with an invalid Field ID, the data import job succeeded; however, the data loaded for the Field ID was invalid, and no warning message appeared in the error log. This issue has been resolved. Now, if the data import job encounters an invalid Field ID, a warning is recorded in the error log.	TFS351418
Previously, when using the Template Builder window to create a FMEA Template with a non-English culture setting, an error occurred. This issue has been resolved.	TFS350038
Previously, when using the Failure Modes and Effects Analysis (FMEA) Asset Templates Data Loader to import FMEA template data, the associated ID fields for the asset and its child records were not generated. This issue has been resolved. Now, when importing records using the FMEA data loader, all ID fields are automatically populated as expected.	TFS346982
Previously, when you accessed an asset, the list of Failure Modes could take a long time to appear. This issue has been resolved.	TFS346581
Previously, when you promoted to ASM an FMEA Analysis that was created from a template in the Apply Template Builder and assigned to a specific site, an error occurred. This issue has been resolved. Now, all FMEA Analyses that were created from templates and assigned to specific sites are promoted to ASM as expected.	TS345206

Family Management

Table 28. Resolved Issues
Description	Tracking ID
Previously, although the license for a module was activated, the associated parent families were not appearing in the Family Management page, and when you attempted to access a child family, an error occurred. These issues have been resolved.	TFS353926

Family Policies and Policy Designer

Table 29. Enhancements
Description	Tracking ID
To enhance usability of the policy model for mathematical operations, a new calculation node, Math (), has been added. (ID: )	TFS350766

Table 30. Resolved Issues
Description	Tracking ID
Previously, when you attempted to delete a Case node or an Is Null node from a policy, an error occurred, and the node was not deleted as expected. This issue has been resolved.	TFS354504
Previously, on the Properties window of a Text node, when you added more than 9 indexes, the additional Index numbers did not appear in a numeric order. This issue has been resolved.	TFS352248
Previously, for a Data Frame type of Constant node to which a value was passed from another node, in the Edit Data Frame window, when you attempted to map that value to a column whose data type was Decimal, an error occurred. This issue occurred when the data type of the mapped value was undetermined. This issue has been resolved.	TFS351455
Previously, for a Collection Filter node in a policy model, if you selected any of the following operators for Timestamp on the Properties window, and then validated or executed the policy, a validation error occurred: > >= < <= This issue has been resolved.	TFS349996
Previously, for a policy model where an R Script node was connected to a Data Frame type of Constant node, when you copied the two nodes, along with the connection, and pasted them to the model canvas, the input value for the pasted R Script node appeared blank in the Properties window. This issue has been resolved.	TFS343648
Previously, for a policy model, when you attempted to map an output value whose data type was undetermined (for example, a value from a Case node) to a node that enforced data type checking (for example, an Add node), the policy could not be activated. This issue has been resolved.	TFS342485
Previously, on the Properties window of a Text node, when you added more than 11 indexes, the additional Index numbers appeared as {2}. As a result, the output of the Text node was incorrect. This issue has been resolved.	DE63168

Foundation

Table 31. Resolved Issues
Description	Tracking ID
Previously, when you attempted to log in to GE Digital APM while you were offline, your account would not get locked although the number of failed attempts exceeded the limit specified in the Password Policies page. This issue has been resolved. Now, based on the password policy, if the number of failed attempts exceed the limit, your account will be locked.	TFS345306

Generation Availability Analysis (GAA)

Table 32. Enhancements
Description	Tracking ID
To identify the type of GAA Company, a new field, GAA Type, has been added to the GAA Company family.	TFS353337

Table 33. Resolved Issues
Description	Tracking ID
Previously, for a GAA Unit associated with a Maintenance Outage (MO) event, in the Breakdown of Period Hours section, the MO period was included in the Planned Outage slice instead of the Unplanned Outage slice of the doughnut chart. This issue has been resolved.	TFS351385
Previously, if you created Performance records for all events and events that were not outside management control (OMC), in the Unit Summary workspace, in the Frequency of Event types graph, events that were not OMC were considered twice. This issue has been resolved. Now, events in only the Performance record for all events are considered in the graph.	TFS348744

Table 34. Obsolete Features
Description	Tracking ID
The Contributing Incidents Count column has been removed from the Revision History page of a Primary Event. Additionally, the Count of Contributing Events box has been removed from the Primary Event datasheet.	TFS353109

Table 35. Deferred Features

Description

Tracking ID

The following fields and related functionality from the GAA Plant and GAA Unit record:


Datasheet	Fields
GAA Plant	Date/Time Alternate Format GADS Region GADS Subregion
GAA Unit	Demonstrated Maximum Gross Capacity Demonstrated Maximum Net Capacity Summer Net Capacity Winter Net Capacity

TFS229627

The following fields and related functionality from the Performance record:


Tab	Fields
Unit Identification	Capacity History Statistics Type Zone Refresh Incident Rollup
Unit Generation Performance	Demonstrated Max Capacity (G) Demonstrated Max Capacity (N) Override Reserve Shutdown Hours Sum of fuel BTUs Heat Rate
Unit Starting Characteristics	YTD attempted unit starts YTD actual unit starts YTD start reliability
Unit Primary Fuel Information	EIA Fuel Reporting Primary Quantity Burned Unit of Measure Primary Fuel BTUs - Contract Primary Fuel BTUs - Electrical Generation Primary Fuel BTUs - Plant Heating and Cooling Primary Fuel BTUs - Process Steam Primary Fuel BTUs - Total
Unit Secondary Fuel Information	EIA Fuel Reporting Secondary Quantity Burned Unit of Measure Secondary Fuel BTUs - Contract Secondary Fuel BTUs - Electrical Generation Secondary Fuel BTUs - Plant Heating and Cooling Secondary Fuel BTUs - Process Steam Secondary Fuel BTUs - Total

TFS234410
TFS234310

The following families in GAA:

Generation Forecast
Generation Fuel Annual Report
Generation Fuel Monthly Report
Generation Fuel Report
Generation Nameplate
Generation Nameplate Combined Cycle
Generation Nameplate Diesel
Generation Nameplate Fluidized Bed
Generation Nameplate Fossil Steam
Generation Nameplate Gas Turbine
Generation Nameplate Hydro
Generation Nameplate Miscellaneous
Generation Nameplate Nuclear
Generation Role
Generation Role Assignment
Generation Role Definition
Generation Role Field Configuration
Generation Unit Loading Profile
Generation Unit Starting Profile

TFS184663
TFS184661
TFS184660
TFS184659
TFS184657
TFS184656
TFS184655
TFS184653
TFS184652
TFS184646

The following Security Groups in GAA:

MI Generation Management Forecast
MI Generation Management Nameplate
MI Generation Management Security

TFS184663
TFS184661
TFS184660
TFS184659
TFS184657
TFS184656
TFS184655
TFS184653
TFS184652
TFS184646

GE Analytics

Table 36. Deferred Features
Description	Tracking ID
KPIs for GE Analytics.	TFS162791

Graphs

Table 37. Deferred Features
Description	Tracking ID
Exporting to a PDF and printing graphs.	TFS81015

Hazards Analysis

Table 38. Resolved Issues
Description	Tracking ID
Previously, for a newly-created Hazards Analysis Safeguard, the IPL Checklist record was not created. As a result, the corresponding fields in the IPL Checklist section of the datasheet did not appear. This issue has been resolved.	TFS353620
Previously, after you unlinked an asset from a Hazards Analysis System/Node, the count of assets on the Linked Assets tab was not updated. This issue occurred only for a HAZOP Analysis. This issue has been resolved.	TFS348489
Previously, you could unlink an asset from a Hazards Analysis regardless of its state. This issue has been resolved. Now, you can unlink an asset only if the Hazards Analysis is in the Planning state.	TFS348282

Inspection Field Data Collection

Table 39. Resolved Issues
Description	Tracking ID
Previously, a user whose culture setting was Chinese could not download an offline inspection. This issue has been resolved.	TFS346633

Inspection Management

Table 40. New Features
Description	Tracking ID
The Taxonomy Configurations feature is now available. This feature allows an Inspection administrator to create Taxonomy Configurations that define the available collection of Checklist Templates and/or Inspection Families that are available for an asset from a given taxonomy.	TFS337314
The Checklist Configuration Templates feature is now available. This feature allows an Inspection administrator to configure custom Checklist Templates that include user-defined checklist categories and items.	TFS336625

Table 41. Enhancements
Description	Tracking ID
The performance when loading the Inspection Management Overview page has been improved.	TFS353289
The performance of the Inspection Management (IM) Assets and the Inspection Management (IM) Functional Location Data Loaders has been improved.	TFS348827
You can now access inspections with the Pending Approval status in the Open Inspections section in the Inspection Management Overview page.	TFS345341
You can now create an Inspection with a system-generated value in the Inspection Reference field using the Inspection Management (IM) Assets and Inspection Management (IM) Functional Location Data Loaders. To facilitate this enhancement, a new column, Use System Generated ID, has been added to the Inspections worksheet in the data loader workbooks.	TFS344201

Table 42. Resolved Issues
Description	Tracking ID
Previously, if you updated an inspection with a Completion Date that was earlier than the Last Date of the inspection task, the Last Date was not updated. This issue has been resolved. Now, the Last Date is updated with the most recent Completion Date of an inspection that has the Inspection Task Complete check box selected.	TFS354976
Previously, if you modified a Checklist Finding record and then navigated away from the page, your changes were not saved. This issue has been resolved. Now, if you modify a Checklist Finding record and attempt to navigate away from the page before saving, a confirmation message appears, prompting you to save.	TFS350663
Previously, if you had a Human Resource record without a Security User record, then the following fields were not populated on their respective datasheets: On the Pressure Test Inspection datasheet: Witnessed By - Shell Side Witnessed By – Tube Side On the Inspection datasheet: Inspection Report Owner Reviewers Name This issue has been resolved. Now, a Human Resource record without a corresponding Security User record is displayed in the following format: <Last Name>, <First Name> ~.	TFS349807
Previously, for a Team Member record associated with an inspection, the value in the Full Name field was not populated with the associated Human Resource record. This issue has been resolved. Now, in the Team Member record, the Full Name field displays the Human Resource record in the following format: <Last Name>, <First Name> ~ <User ID>. If the Human Resource record does not have an associated User ID record, the Full Name field is populated with a value in the following format: <Last Name>, <First Name> ~.	TFS349794
Previously, while modifying an Inspection Task using the Inspection Management (IM) Assets or the Inspection Management (IM) Functional Location Data Loader, even if you entered the same value as the previous one in the Reoccurring column, an error message appeared. This issue has been resolved. Now, the error message appears only if you enter a different value in the Reoccurring column.	TFS348599
Previously, if the value in the Desired Interval field in an Inspection Task was 0, you could not update the value even if the value in the Override Interval field was True. This issue occurred only if you attempted to update the Inspection Task using the Inspection Management (IM) Assets or the Inspection Management (IM) Functional Location Data Loader. This issue has been resolved.	TFS348522
Previously, you could not add a Reference Document to an archived Inspection using the Inspection Management (IM) Assets or the Inspection Management (IM) Functional Location Data Loader. This issue has been resolved. Now, in this scenario, although you cannot update the Inspection, you can add a Reference Document.	TFS342304
Previously, when you deleted an Inspection, Inspection Task, or Work Pack, a message appeared indicating that the record was successfully deleted. However, the busy indicator remained on the page. Also, the record did not appear to have been deleted until you refreshed the page. These issues have been resolved.	TFS337652
Previously, in a checklist inspection, Checklist Findings were not sorted. This issue has been resolved. Now, Checklist Findings are sorted based on their sequence in the System Code Table for their respective checklist family.	TFS214338

Life Cycle Cost Analysis

Table 43. Enhancements
Description	Tracking ID
To enhance usability, if you modify the LCC Page Filter query, the numbers displayed in the tabs in the LCC Overview page now reflect the results of the modified query.	TFS348689
Reliability Recommendations can now be created and associated with an LCC Primary Element or Secondary Element.	TFS252021

Table 44. Resolved Issues
Description	Tracking ID
Previously, when you navigated from the MI Human Resource datasheet to another human resource datasheet while adding a new team member, the Add Team Member button disappeared. If you returned to the previous datasheet, the button remained absent. This issue has been resolved.	TFS345264

Map

Table 45. Resolved Issues
Description	Tracking ID
Previously, when you attempted to close the location details on a map, the window did not close. This issue has been resolved.	TFS337811

Metrics and Scorecards

Table 46. Deferred Features
Description	Tracking ID
Export/Import of KPI Schedules.	TFS173886
Selecting columns to include in a Scorecard.	TFS70641
GM (Generation Management) cube is deferred from V4.0.0.0. Any previously deployed GM (Generation Management) cube, which worked in V3.6 and earlier releases, will continue to work in V4.0.0.0 after upgrading the product. You will be able to use the existing GM cube and the support will continue.	TFS160446

Policy Designer

Table 47. Enhancements
Description	Tracking ID
To indicate the status of a module workflow policy on the Policy Designer Overview page, the Active column, which contains a check box, has been added to the table in the Module Workflow Policies section. A selected check box indicates that the status is active; a cleared check box indicates that the status is not active. You can filter and sort the policies in the table based on the Active column.	TFS351328

Table 48. Resolved Issues
Description	Tracking ID
Previously, Policy Designer displayed only the first 1,000 Instances in the Instances, Execution, and Validation panes, and when you searched for Instances that were not already displayed, the search did not return the correct results. This issue may have resulted in errors when you saved new Instances, where the new Instance ID was identical to an existing Instance that was not currently displayed in Policy Designer. This issue has been resolved. Now, up to 10,000 instances can be displayed in Policy Designer. As a result, you may encounter longer load times for policies with a large number of Instances.	TFS354793
Previously, in V4.3.0.3.07, in the Policy Designer Overview page, in the Active Policies and Inactive Policies sections, references to other records in the Execution Result Summarycolumn did not appear as links. This issue has been resolved.	TFS352646
Previously, for a policy model that included a primary record and an Input node, in the Instances section, when you accessed the Search window of the Input node, no records appeared. This issue occurred when a relationship was not defined between the family used in the primary record and that used in the Input node. This issue has been resolved.	TFS352234
Previously, if you modified the time zone of a Policy from Coordinated Universal Time (UTC) to any other value, and then executed an Email Contact node that contained a timestamp value in the Message section, the timestamp in the email message did not reflect the new time zone. This issue has been resolved.	TFS350432
Previously, prior to an upgrade, if your database contained a scheduled policy with an invalid time for the most recent Last Date or Next Date, an error occurred, and the upgrade did not continue as expected. This issue has been resolved. Now, when you upgrade your database, the Policy Upgrade Utility clears the value from the Last Date or Next Date field where invalid times were encountered so that you can manually update the execution schedules in Policy Designer as needed.	TFS349531
Previously, in the Security section, when you added a duplicate User or Security Group in the grid, an error message did not appear, asking you to remove the duplicate entry. This issue has been resolved.	TFS348227
Previously, if an erroneous policy configuration resulted in input values for a node being derived from nonexistent output fields of a predecessor node, the Policy Designer page did not load after the policy was saved. This issue has been resolved. Now, in this scenario, when you access the policy, the Policy Designer page loads as expected.	TFS346260

Production Loss Analysis (PLA)

Table 49. Enhancements

Description

Tracking ID

For a Production Event, in the Search window that appears when you attempt to add or remove a value from the Work History Link box, the OK button is now disabled until you add or remove a value. Additionally, to improve clarity, the number of values that will appear in the Work History Link box is now indicated on the Search window.

TFS350932

To improve clarity, in the Production Summary workspace, the y-axis of the Production Summary Plot is now labeled Production %, instead of Production Amount.

TFS350908

When you create a Production Profile, a warning message now appears, asking you to add a margin value because it is required to calculate production losses. Additionally, the Margins datasheet appears so that you can add the margin value.

TFS350222

For a quantity-based or time-based plan, when you attempt to remove an entry from the Plan Details workspace using the Remove Last Row button, a warning message now appears. Additionally, after you remove the entry from the Plan Details workspace, the corresponding entry is removed from the Production Data workspace.

TFS349543

In the Production Data workspace, the Production Loss grid has been redesigned to improve usability. To facilitate this enhancement:

The Production Loss datasheet has been added to the Production Loss family to facilitate the creation of Production Losses.
The following fields have been added to the Production Loss family:
- Production Data Entity Key: Stores the entity key of the Production Data for which the Production Loss is added.
- Production Event Entity Key: Stores the entity key of the Production Event to which the Production Loss is linked.
The Add Loss button and the Delete Loss button have been removed from the Production Loss grid and replaced with the Add button () and the Delete button (respectively.
The following buttons have been added to the Production Loss grid:
- Edit button (): You can use this button to modify a Production Loss.
- Search button (): You can use this button to search for a Production Loss based on the specified filter.

TFS347162

The Production Loss Analysis (PLA) Data Loader has been enhanced to improve the performance of the data load operation. To facilitate this enhancement, the Production Loss Analysis (PLA) Data Loader is replaced with the following data loaders:


Data Loader	Records Loaded
Production Loss Analysis (PLA) 1-Admin	Production Unit Production Event Code Production Profile Profile Margin
Production Loss Analysis (PLA) 2-Event	Production Event
Production Loss Analysis (PLA) 3-Plan	Production Plan Production Data Production Loss

TFS347100

The Event ID field of a Production Event now appears as a text box on the Add New Production Event datasheet and in the Production Events workspace, and it is populated with a value in the following format: Event-<unique ID>. This field was previously populated with the date and time when the Production Event was created.

TFS312123

When you create a Production Loss, in the Production Event drop-down list box, the Production Events are now sorted chronologically in descending order based on Start Date.

TFS274911

Table 50. Resolved Issues
Description	Tracking ID
Previously, in the PLA Overview page, in the TOP 10 BAD ACTORS graph, the total cost of losses was plotted incorrectly. This issue has been resolved. To facilitate this fix, the following query has been modified: Public\Meridium\Modules\PLA\Queries\Top10BadActors.	TFS355530
Previously, when creating a manual Production Plan, if you attempted to add a row using the Insert Row Above or the Insert Row Below option, an error occurred. This issue occurred only if values in the Related Product Name and Alternate Product Name fields in the associated Production Profile were different. This issue has been resolved.	TFS353883
Previously, in the Codes workspace or in the Production Event Code box on the Production Event datasheet, when you scrolled down the list of child Production Event Codes, duplicate values appeared in the list. This issue has been resolved.	TFS350316
Previously, if a Production Event Code that was linked to a Production Event was deleted, then the deleted code still appeared in: The Event Code column in the Production Events section on the PLA Overview page. The Production Event Code box on the Production Events datasheet. The Production Event Code column in the Production Events workspace. This issue has been resolved. Now, in this scenario, a blank value appears.	TFS348792
Previously, if an Impact Code that was linked to a Production Loss was deleted, then the deleted code still appeared in: The Impact Code box on the Production Loss datasheet. The Impact Code column in the Production Loss grid in the Production Data workspace. This issue has been resolved. Now, in this scenario, a blank value appears.	TFS348791
Previously, if an OEE Code that was linked to a Production Loss was deleted, then the deleted code still appeared in: The OEE Code box on the Production Loss datasheet. The OEE Code column in the Production Loss grid in the Production Data workspace. This issue has been resolved. Now, in this scenario, a blank value appears.	TFS348790

Table 51. Obsolete Features
Description	Tracking ID
The Production Loss Analysis (PLA) Data Loader has been deprecated. To load data, you can now use the following enhanced data loaders, which are introduced in V4.3.0.4.0: Production Loss Analysis (PLA) 1-Admin Production Loss Analysis (PLA) 2-Event Production Loss Analysis (PLA) 3-Plan	TFS347100

Queries

Table 52. Resolved Issues
Description	Tracking ID
Previously, when you sent a Conditional Alert email, the web query link was unresponsive. This issue has been resolved. The server parameter for the MI_ProcessConditionalAlerts rule has been corrected.	TFS352126
Previously, for a query that contained one or more compound join conditions, if you attempted to modify a compound join condition via the Design workspace, you were unable to modify the join, and the query was corrupted and could not be run. This issue has been resolved. Now, if a previously existing query contains one or more compound join conditions, you can access and run the query as expected unless you first access the Design workspace for the query. If you access the Design workspace for such a query before running the query, the query will be executed based only on the information in the SQL workspace, and will ignore any modifications normally applied by selections made in the Design workspace. If the query is executed in this way, columns whose Display check boxes are cleared appear in the query results, and hyperlinks do not appear in the query results. Also, now, if you create a query that contains one or more compound join conditions, you cannot access the Design workspace for that query.	TFS347790
Previously, when you exported query results as an Excel file: If your query was not formatted, date and time values in the exported file were incorrect and no longer in the time zone associated with your Security User account. If you selected the Formatted check box in the Design workspace for the query, decimal marks were represented by decimal points in the exported file, regardless of your culture setting. An error may have occurred when you attempted to open the file. These issues have been resolved.	TFS346707
Previously, if a query contained logical OR criteria, then, in the Design workspace for the query, the information displayed when hovering over any expression in the column displayed the value stored in the first line of the criteria rather than the appropriate hyperlink value. This issue has been resolved.	TFS346706
Previously, if you created a query containing a date prompt and you selected a default value for the date prompt, when the query was run, the default date did not appear in the prompt. This issue has been resolved.	TFS346704
Previously, when you exported query results as an Excel file, in some scenarios, an error occurred when you attempted to open the file. This issue has been resolved.	TFS346579
Previously, if you exported query results as a .csv file, only 1000 results appeared in the exported file even if the query results should have contained more than 1000 records. This issue has been resolved.	TFS346359
Previously, joins against non-family tables did not appear correctly in the Design workspaces of queries and produced invalid query results. This issue has been resolved.	TFS346192
Previously, the results of a formatted query containing two instances of the same column displayed the Unit of Measurement (UOM) associated with the Security User in the first instance of the column, but displayed the unconverted UOM in the second instance of the column. This issue has been resolved. Now, in this scenario, the results display the (UOM) associated with the Security User in both columns.	TFS333690

R Scripts

Table 53. Resolved Issues
Description	Tracking ID
Previously, if you accessed the R Scripts page via the Catalog folder, and then modified any of the following Catalog Item Properties of an R script in the grid, the R script editor and the Parameters pane of the R script appeared blank: Catalog Description Name This issue has been resolved.	TFS348806

Recommendation Management

Table 54. Enhancements
Description	Tracking ID
o enhance performance in module-specific recommendation datasheets, you can now access the Select Users window from the following fields in the Recommendations family: Author Name Assigned To Name Final Approver Name Reviewer Name The Select User window allows you to select a user from a list of Human Resource records.	TFS348723

Table 55. Resolved Issues
Description	Tracking ID
Previously, when using GE Digital APM with an Oracle database, if you performed a search in the Recommendations pane, an error occurred. This issue has been resolved.	TFS354990
Previously, if you used the search feature to find a record within the Recommendations pane, and then attempted to select the check box next to one of the search results, the check box could not be selected. This issue has been resolved.	TFS348658
Previously, when assigning an asset to a General Recommendation, the site key of the asset was not inherited by the General Recommendation record. This has been resolved.	TFS347725
Previously, when you searched Performance Recommendations, a maximum of 1,000 records appeared on the Recommendation Management page, even when there were more than 1,000 records. This issue has been resolved. Now, all records appear when more than 1,000 Performance Recommendations are returned.	TFS346703
Previously, if a Security User belonged to only the MI Recommendation Management Security Group, the Asset Health button in the left navigation menu was disabled and the user could not access recommendations. This issue has been resolved.	TFS346582

Record Manager

Table 56. Resolved Issues
Description	Tracking ID
Previously, execution of the strategy rule for Conditional Alerts could fetch expired user data, causing an error to occur. This issue has been resolved.	TFS352137
Previously, selecting the Send Web Query check box for a Conditional Alert resulted in an error, and, even if the check box was cleared, each email sent using the Conditional Alert included a link to the query. This issue has been resolved. Now, emails sent using a Conditional Alert will include a link to the query only if the Send Web Query check box for the Conditional Alert is selected.	TFS352129
Previously, when you used the Variable Distribution list to add recipients to a Conditional Alert, the email was not sent. This issue has been resolved.	TFS352124
Previously, if only the Allow for Unlinking datasheet-level permissions option was enabled in the Create New Master Form window, the Unlink option was available when you selected the Options button () in Record Manager. This issue has been resolved. Now, the Unlink option will appear only if the Allow For Deletion and Allow For Unlinking options are enabled in the Create New Master Form window.	TFS349546

Reliability Analytics

Table 57. New Features
Description	Tracking ID
Using Reliability Application Settings, you can now configure Reliability reports to use your own logo and title.	TFS346264

Table 58. Enhancements
Description	Tracking ID
In Production Analysis, the Confidence Level display values are no longer rounded.	TFS353416
To enhance usability, if you modify the RAPageFilter query, the numbers displayed in the tabs in the RA Overview page now reflect the results of the modified query.	TFS348689
To avoid performance issues, when you attempt to execute an Automation Rule with more than 100 analyses, a warning message now appears stating your database may stop responding if the rule is executed.	TFS341062
A new specific confirmation message stating "Automation Rule has been executed" now appears when you execute an Automation Rule.	TFS327447

Table 59. Resolved Issues
Description	Tracking ID
Previously, if you saved a Production Analysis with an invalid value in the Analysis Name field, an error message appeared and the analysis name was saved as New Analysis. This issue has been resolved.	TFS354388
Previously, in Probability Distribution, Production Analysis, Reliability Distribution, and Reliability Growth, when you selected View Data after merging two or more analyses, an error occurred. This issue has been resolved.	TFS353984
Previously, when you entered a negative value in the Random Variable box on the Specify the Random Variable window and selected OK, an error occurred. This issue has been resolved.	TFS353421
Previously, if you renamed a Production Analysis without entering a value in the Analysis Name field, no error message appeared and the analysis was saved. This issue has been resolved. Now, in this scenario, a warning message appears and the analysis is not saved.	TFS352560
Previously, if you saved a Probability Distribution with an invalid value in the Analysis Name field, an error message appeared and the analysis name was saved as New Analysis. This issue has been resolved.	TFS352559
Previously, when you created a new Automation Rule based on a Reliability Distribution, an error occurred. This issue has been resolved.	TFS351839
Previously, in System Reliability, when you created a new scenario and accessed the diagram, the default nodes did not appear in the Palette section. This issue has been resolved.	TFS351818
Previously, when you selected multiple Ignore check boxes in the Reliability Distribution Data Editor window, only the last check box selection was saved. This issue has been resolved.	TFS351721
Previously , if you saved a Reliability Growth Analysis without entering a value in the Analysis Name field, no error message appeared and the analysis name was set to New Analysis. This issue has been resolved. Now, if the Analysis Name field is blank when you attempt to save a Reliability Growth Analysis, a warning message appears and the analysis is not saved.	TFS351600
Previously, when you accessed a localized version of Reliability Distribution, the Probability Plot was not properly localized for different cultures and an error occurred. This issue has been resolved.	TFS351483
Previously, when a member of the MI Reliability Administrator Security Group selected the Automation Rules tab on the RA Overview page, an error occurred. This issue has been resolved.	TFS350871
Previously, in System Reliability, if you selected on the new risk datasheet, the list of actions associated with the selected scenario appeared, rather than the expected list of mitigating risks. This issue has been resolved.	TFS350735
Previously, in System Reliability, if you selected on the new action datasheet, the list of risks associated with the selected scenario appeared, rather than the expected list of mitigating risks. This issue has been resolved.	TFS350735
Previously, in the Actions section of a System Scenario, when you navigated away from the System Reliability Analysis page and then returned, the Action Type list appeared blank. This issue has been resolved.	TFS349679
Previously, when you extrapolated a plot in Reliability Growth with an extrapolate date or time set before the analysis end date or time, the page did not respond until it was refreshed. This issue has been resolved.	TFS348548
Previously, when you added an Action to a System Reliability Analysis, the value in the Action Type list selection appeared as No Name if the option was not a baseline System Code. This issue has been resolved.	TFS346974
Previously, when a user without a Production Loss Analysis license selected the Production Analysis tab, an error occurred and the Production Analysis list did not appear. This issue has been resolved.	TFS345627

Table 60. Deferred Features
Description	Tracking ID
Action optimization in System Reliability Analysis.

Reliability Centered Maintenance (RCM)

Table 61. Enhancements
Description	Tracking ID
To enhance usability, if you modify the RCM Overview Filter Query, the numbers displayed in the tabs in the RCM Overview page now reflect the results of the modified query.	TFS348579

Table 62. Resolved Issues
Description	Tracking ID
Previously, the RCM Analysis Data Loader Template that appeared in the APM Strategy grid of the Data Loader Templates workspace did not include the template enhancements made to the RCM Analysis Data Loader Template in an earlier version of GE Digital APM. This issue has been resolved. Now, the APM Strategy grid in the Data Loader Templatesworkspace reflects the most up-to-date version of the RCM Analysis Data Loader Template.	TFS351481
Previously, when you promoted to ASM an RCM Analysis that was created from a template in the Apply Template Builder and assigned to a specific site, an error occurred. This issue has been resolved.	TS345206
Previously, when using the RCM Data Loader, when you imported data with an invalid Field ID, the data import job succeeded; however, the data loaded for the Field ID was invalid, and no warning message appeared in the error log. This issue has been resolved. Now, if the data import job encounters an invalid Field ID, a warning is recorded in the error log.	TFS351418
Previously, when using the Template Builder window to create an RCM Template with a non-English culture setting, an error occurred. This issue has been resolved.	TFS350038

Risk Based Inspection

Table 63. RBI 580 and RBI 581- Enhancements
Description	Tracking ID
The performance when loading the Risk Based Inspection Overview page has been improved.	TFS353289
To enhance usability, the Calculate button () no longer appears on the Risk Based Inspection Overview page. Now, the Calculate button () appears above the grid in the Assets section.	TFS348697
To enhance usability, the following fields have been added to the Recommendations pane when accessed from the Risk Based Inspection (RBI) module: Damage Mechanism Non-Recurring? Target Completion Date Task Type	TFS346643
In some of the PV Stress records that contain the value SA/AS 1548, SB-187, SB-308, or SB-211 in the Material Specification field, values in the Minimum Yield Strength field have been added based on ASME 2010 standards.	TFS345628
In Oracle databases, when you attempt to calculate multiple analyses, if the calculation time exceeds the allowed timeout limit, there is now an error message that specifies the reason.	TFS345520
For an RBI Analysis, when determining values for Long Term Avg. Corr. Rate and Short Term Avg. Corr. Rate, if the corrosion rate in a TML Corrosion Analysis is negative, then, to calculate the values in these fields, the value in the Minimum Corrosion Rate field in the TML Corrosion Analysis Settings is now used instead of the negative value. In RBI 580, Minimum Corrosion Rate is used in a related Criticality Int. Corr. Deg. Mech. Eval. In RBI 581, Minimum Corrosion Rate is used in Thinning and Lining Evaluations.	TFS343791

Table 64. RBI 580- Enhancements
Description	Tracking ID
After you generate and consolidate RBI Recommendations for an asset, the validation message that appears now includes the following information: The number of recommendations that have been consolidated (i.e., recommendations in the Consolidated state) The number of recommendations that have been created after consolidating (i.e., recommendations in the Proposed state) For example, if two recommendations have been created by consolidating four recommendations, then the validation message includes the following text: 2 consolidated recommendations have been created from 4 recommendations based on Task Type and Degradation Mechanism.	TFS346653
The Risk Based Inspection Overview page now contains the RBI RISK MATRIX BY RBI COMPONENT graph, which plots the total number of components based on their consequence of failure and probability of failure values. If you select a cell in the graph, a new page appears, displaying the list of components, along with their equipment details, inspection priority, risk category, consequence of failure, and probability of failure. To facilitate this enhancement: A new graph, RBI Risk Matrix, has been added to the following Catalog folder: Public\Meridium\Modules\Risk Based Inspection\Overview Graphs. Two new queries, RBI Risk Matrix Query and RiskMatrix, have been added to the following Catalog folder: Public\Meridium\Modules\Mechanical Integrity\Queries\Dashboard Queries.	TFS345450

Table 65. RBI 581- Enhancements
Description	Tracking ID
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 damage factor and 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.	TFS346991

Table 66. RBI 580 and RBI 581- Resolved Issues
Description	Tracking ID
Previously, if the Equipment ID field in an analysis was blank, you could not calculate the analysis. This issue has been resolved. To facilitate this fix, the Equipment ID field has been added to the following datasheets: RBI Criticality Analysis RBI PRD Criticality Analysis RBI Pipeline Analysis RBI 581 Risk Analysis In addition, the Equipment box has been removed from the RBI 581 Risk Analysis datasheet.	TFS348552
Previously, if the value in the Flow Stress field was 0, the validation message did not specify the reason. This issue has been resolved. Now, in this scenario, the validation message suggests that you verify if values in the Minimum Tensile Strength and Minimum Yield Strength fields are correct.	TFS345620

Table 67. RBI 580- Resolved Issues
Description	Tracking ID
Previously, the values in the Operating Pressure – Shell, Operating Temperature – Shell, and Process Fluid fields in a Criticality RBI Component – Exchanger Bundle were not copied to their respective Operating Pressure, Operating Temperature, and Representative Fluid fields in the associated RBI Criticality Analysis. This issue has been resolved. To facilitate this fix, mappings for the aforementioned fields have been added to the following query: RBI-CNAFC Query MI_CCRBICEB. When you upgrade to V4.3.0.4.0, the Data Mapping Group record that satisfies the following conditions, along with its child records, will be reverted to baseline: The value in the Source Family field is Criticality RBI Component - Exchanger Bundle. The value in the Target Family field is RBI Criticality Analysis.	TFS347032 TFS335351
Previously, after consolidating RBI Recommendations, in some scenarios, a few fields in the new proposed Recommendation were blank. This issue has been resolved. Now, in these scenarios, the fields are populated with values in the corresponding fields in the source recommendation with the most conservative interval (i.e., the recommendation with the least value in the Interval field among all the source recommendations that have been consolidated).	TFS346654
Previously, on the Risk Based Inspection Overview page, while generating RBI Recommendations for analyses associated with all the assets, if you attempted to consolidate the RBI Recommendations, they were not consolidated. This issue has been resolved.	TFS346378
Previously, when you applied an RBI Criticality Analysis, the values in the following fields in the associated Criticality Int. Corr. Deg. Mech. Eval. were copied to the corresponding fields in the Criticality Int. Corr. Deg. Mech. Eval. of the new analysis: Long Term Avg. Corr. Rate Short Term Avg. Corr. Rate Controlling Corrosion Rate This issue occurred only if the value in the Source of Calculated Corrosion Rates field in the target RBI Component was Manual Entry. This issue has been resolved. Now, in this scenario, the aforementioned fields will be blank, and you can enter a value manually.	TFS215396

Table 68. RBI 581- Resolved Issues
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.	TFS350655
Previously, if the DensityLiq field in the RepresentativeFluids record for a fluid was blank or contained the value 0, there was no validation message. This issue has been resolved. Now, in this scenario, a validation message appears when you attempt to calculate an analysis performed on the fluid.	TFS347855
Previously, if the value in the Minimum Tensile Strength or the Minimum Yield Strength field in a PV Stress or a Piping Stress record was 0, then the value in the Flow Stress field was not calculated. Instead, the Flow Stress field was populated with the value 0. This issue has been resolved. In addition, if the value in the Flow Stress field is 0, a validation message appears, asking you to verify if values in the Minimum Tensile Strength and Minimum Yield Strength fields are correct.	TFS345620
Previously, in an RBI 581 Consequence Evaluation, if you cleared the Use Calculated Inventory check box, the Inventory Component Mass field was updated with a null value. This issue has been resolved.	TFS345618
Previously, when you applied an RBI 581 Risk Analysis, the values in the following fields in the associated RBI 581 Thinning and Lining Evaluation were copied to the corresponding fields in the RBI 581 Thinning and Lining Evaluation of the new analysis: Long Term Avg Corr Rate Short Term Avg Corr Rate Controlling Corrosion Rate This issue occurred only if the value in the Source of Calculated Corrosion Rates field in the target RBI Component was Manual Entry. This issue has been resolved. Now, in this scenario, the aforementioned fields will be blank, and you can enter a value manually.	TFS215396

Table 69. RBI 581- Obsolete Features
Description	Tracking ID
In the RBI 581 Risk Analysis datasheet, the Equipment box has been replaced with the Equipment ID box.	TFS348552
To improve performance while calculating an RBI 581 Risk Analysis, the policies and R Scripts that were previously used to calculate damage factor and consequence of failure are no longer used.	TFS346991

Table 70. Deferred Features
Description	Tracking ID
Creating a bulk What-If analysis.	TFS73475

Risk Matrix

Table 71. Enhancements
Description	Tracking ID
The following System Code Tables have been added to the Risk Matrix feature and can be accessed from the Risk Matrix Admin page: MI_RISK_CATEGORY_DESC MI_RISK_CONSEQUENCE_DESC MI_RISK_MATRIX_AXIS MI_RISK_MATRIX_SORT_ORDER MI_RISK_PROBABILITY_DESC MI_RISK_PROTECTION_LEVEL_DESC	TFS347758

Table 72. Resolved Issues
Description	Tracking ID
Previously, if the Hide Probability and Consequence Name check box was selected for a Risk Matrix record, all rows other than the first row of that Risk Matrix were hidden, and the row and column headers remained on the Risk Matrix. This issue has been resolved. Now, in this scenario, all rows of the Risk Matrix appear, and the Consequence and Probability names are hidden from the column and row headers as expected.	TFS346089

Root Cause Analysis

Table 73. Enhancements
Description	Tracking ID
In RCA application settings, you can now enable mappings to automatically update the value in the Recommendation Status field when the Recommendation state is modified.	TFS349797
The error message that you define in the Rules Editor now appears when you attempt to link an asset with an RCA.	TFS353731
You can now restrict analysis access based on team membership via Application Settings. Only RCA Principal Analysts can modify the analysis restrictions in the Analysis Summary workspace.	TFS350794 TFS350761
You can now use reference documents to add images to the Comprehensive Analysis Report.	TFS350412
Full State Management capability is now available for Root Causes Analyses. The following states have been added: Not Started, In Progress, On Hold, Deferred, and Completed.	TFS348778
To enhance usability, if you modify either of the following queries, the numbers displayed in the tabs in the RCA Overview page now reflect the results of the modified query: TileQueryInProgress TileQueryTemplate	TFS348689
You can now create your own Hypothesis state and assign it an image. The new state will appear as an option in the State list in the Properties pane for a Hypothesis, and in the Hypothesis States () menu in the Logic Tree diagram for a Hypothesis.	TFS345311
When creating an Event Diagram, you can now build the diagram in any order, and the arrows now point in the direction that you specify.	TFS254315

Table 74. Resolved Issues
Description	Tracking ID
Previously, when you linked an asset to an RCA, the Last Update By field was erroneously populated with the MIJOB SEUS KEY. This issue has been resolved.	TFS351898
Previously, when you created an RCA from a Production Event with no start date, and error occurred. This issue has been resolved.	TFS351258
Previously, when a user without edit permissions for an RCA Recommendation attempted to modify the recommendation in Recommendation Management, an error message appeared and the page did not respond. This issue has been resolved.	TFS349894
Previously, when you created an RCA Recommendation Alert and assigned it to someone who was not a team member of the analysis, the alert was not sent. This issue has been resolved.	TFS349882
Previously, an MI FE User who was not an RCA Team Member for a specific RCA Analysis could update the analysis. This issue has been resolved.	TFS347563
Previously, when you created an RCA Recommendation Alert, the alert was not sent because the assignee email address was not found in the human resource table rules. This issue has been resolved.	TFS347343
Previously, when you sent a link to an RCA via email, the link did not contain the full domain name. This issue has been resolved.	TFS346651
Previously, when you accessed a Logic Tree, an error occurred if a node in the diagram did not contain a value in the Label field. This issue has been resolved.	TFS346365
Previously, an MI FE User who was not an RCA Team Member for a specific RCA Analysis could create a Failure Event for that analysis. This issue has been resolved.	TFS345509
Previously, when you imported nodes from one Root Cause Analysis to the Logic Tree in another Root Cause Analysis, Auto Arrange was not applied. This issue has been resolved.	TFS345174
Previously, when you exported a Logic Tree using a browser with a popup blocker enabled, an unhelpful error message appeared. This issue has been resolved and the message now indicates that the popup blocker is enabled.	TFS343632

Table 75. Deferred Features
Description	Tracking ID
Emailing capability to notify and track changes in an Asset in an RCA.	TFS175610
Sending email notifications for alerts configured in RCA for Hypothesis Verifications.	TFS175610
Standard APM State Management functionality in RCA.	TFS63432

Rounds

Table 76. Resolved Issues
Description	Tracking ID
Previously, when you attempted to install Operator Rounds on a Windows Mobile Device, the installation did not work as expected. This issue has been resolved.	TFS354564
Previously, if you were logged in to GE Digital APM as a Calibration Admin and you attempted to delete a reference document, an error occurred, and you were unable to delete the reference document. This issue has been resolved.	TFS351255

Table 77. Deferred Features
Description	Tracking ID
Selecting multiple nodes in the Route pane in Route Management.	TFS173671
Ad hoc inspection of a single asset.	TFS160740
Offline access to the five most recent Recommendations in Rounds.	TFS153853
Support for Bluetooth-connected barcode scanners.	TFS124935
Unlinking a Measurement Location from a Measurement Location Template.	TFS61751
Accessing a list of recent Routes.	TFS61638

Rounds Data Collection

Table 78. Enhancements
Description	Tracking ID
The fields in the Lubrication Requirement Summary section for a Lubrication Requirement are now rearranged to enhance usability.	TFS352490
The default sync interval for a device is now 20 minutes.	TFS344878

Table 79. Resolved Issues
Description	Tracking ID
Previously, when you created a recommendation for a checkpoint, the Source ML or LR Description box was not populated automatically with the value stored in the ML or LR Description field in the checkpoint record for which the recommendation was created. This issue has been resolved.	TFS355476
Previously, when you accessed the Recommendations section, the value in the Created On column did not appear in the format appropriate to your Culture setting. This issue has been resolved.	TFS354360
Previously, when you filtered a Route by one or more filters that were not applicable to any checkpoints on the Route, error messages appeared, and filtering did not work as expected. This issue has been resolved.	TFS353831
Previously, when you entered a reading for a checkpoint with successor conditions, the successor checkpoints of those conditions did not appear in the expected order. This issue has been resolved.	TFS352245
Previously, if anything other than Home was selected in the Asset Hierarchy, no recommendations appeared in the Recommendation pane. This issue has been resolved. Now, the Recommendation pane functions as expected regardless of the selection in the Asset Hierarchy.	TFS351507
Previously, if your database contained a very large number of readings, when you attempted to download routes to the Windows APM Mobile Framework, the synchronization process failed. This issue has been resolved.	TFS341628

Rounds Designer

Table 80. Enhancements
Description	Tracking ID
You can now create a query that links a checkpoint to the template group that was used to create it. To facilitate this enhancement, a new field, Template Group Key, has been added to the Checkpoint, Measurement Location, and Lubrication Requirement families.	TFS346156
For the Rounds feature area, you can now more easily configure URLs to display as hyperlinks in the query results. To facilitate this enhancement, in the URL Builder window, the following options are now available in the Select URL Type section when you select Rounds in the Select URL Feature Area section: Open route in data collection Open route in designer Open existing template group in designer Open existing checkpoints by template	TFS241247

Table 81. Resolved Issues
Description	Tracking ID
Previously, when you attempted to modify the default device settings for all devices, if your database did not contain a Security Group named Super Users, an error occurred, and you were unable to modify settings for all devices. This issue has been resolved.	TFS347078
Previously, there was no way to view more than 100 checkpoint records for any checkpoint template on the Update Existing Checkpoints page. This issue has been resolved. Now, on this page, a drop-down list box appears, allowing you to view checkpoint records in increments of 100.	TFS355369
Previously, in the Template section, if you selected a Lubrication Requirement Template and then selected Update Existing Checkpoints, an error occurred, and you could not update existing checkpoints to reflect changes made in a source Lubrication Requirement Template. This issue has been resolved.	TFS352414
Previously, when you had a large number of checkpoints in a noncompliant state, noncompliant readings were not created. This issue has been resolved.	TFS352125
Previously, when you added a large checkpoint template group to multiple assets on a Route, the action timed out before the template group was completely added, and the Route was not updated as expected. This issue has been resolved. Now, in this scenario, performance is significantly improved, and a progress bar appears, indicating the number of assets to which the template or template group is being applied.	TFS351657 TFS350738 TFS349892
Previously, when you added multiple existing checkpoints to a Route simultaneously, if the first checkpoint you selected in the Existing ML/LR window had a description but a subsequent checkpoint you selected did not have a description, an error occurred, and, after closing the Route, when you attempted to access the Route again, the Route did not load as expected. This issue has been resolved.	TFS351331
Previously, when you added multiple existing checkpoints to a Route simultaneously, if you closed the Route before all checkpoints were successfully added, when you attempted to access the Route again, the Route did not load as expected. This issue has been resolved. Now, when you add multiple existing checkpoints, a progress bar appears, preventing you from closing the Route until the checkpoints are added.	TFS351327
Previously, when you added a condition to a Route as a successor of a numeric checkpoint with numeric allowable values defined, the allowable values did not appear in the Select Value box in the workspace for the condition. This issue has been resolved.	TFS349599
Previously, when you updated Measurement Locations belonging to an ML Template and your Culture setting was defined as anything other than Invariant, an error occurred. This issue has been resolved.	TFS348540

Security Manager

Table 82. Enhancements
Description	Tracking ID
The MI ASM Analyst security group has been added to the MI Foundation Power role.	TFS350699

Table 83. Resolved Issues
Description	Tracking ID
Previously, after synchronizing user records from Microsoft Active Directory, although you had cleared the Enable Password Change check box in the LDAP Manager page, the users whose passwords would expire within 30 days were prompted to change their passwords. This issue has been resolved. Now, if you clear the Enable Password Changecheck box, the users whose passwords would expire in 30 days will not be prompted to change their passwords after synchronization.	TFS347875
Previously, in versions 4.3.0.1.0 or later, the Roles tab was unavailable in the Security Groups page. This issue has been resolved.	TFS340710

Search

Table 84. Resolved Issues
Description	Tracking ID
Previously, if the value in the Query Location field of a Conditional Alert ended in a backslash (\), you could not access the Conditional Alert. This issue has been resolved.	TFS346921
Previously, if you attempted to access a Functional Location record via global search, an Object expected error may have occurred. This issue has been resolved.	TFS346897
Previously, in global search, special characters such as hyphens included in search strings were disregarded (for example, a search for P-6 would not return a record whose name was P-656). This issue has been resolved.	TFS346191

SIS Management

Table 85. Resolved Issues
Description	Tracking ID
Previously, in a Protective Instrument Loop Sensor, if you modified values in any of the following fields, then the values in the Base SFF and SFF fields were not updated automatically: Sensor Connection Interface A Interface B Similarly, in a Protective Instrument Loop Final Element, if you modified values in the Final Element, Interface Module, or any other related fields, then values in the Base SFF and SFF fields were not updated automatically. This issue has been resolved.	TFS345275

Sites

Table 86. Resolved Issues
Description	Tracking ID
Previously, if a data source had two or less than two sites, the site selector was unavailable. This issue has been resolved.	TFS335811

Table 87. Obsolete Features
Description	Tracking ID
You can no longer delete sites.	TFS346154

Systems and Tags

Table 88. Deferred Features
Description	Tracking ID
Viewing trends for multiple OPC Tags simultaneously (i.e., the Process Data Viewer feature in V3).	TFS62299

Thickness Monitoring

Table 89. Resolved Issues
Description	Tracking ID
Previously, in the TMLs section in the Analysis Overview workspace, if a numeric field contained a value of zero, that field appeared to be blank. This issue has been resolved.	TFS355464
Previously, when you performed a bulk analysis on assets in the Thickness Monitoring Overview page, selections did not clear after navigating away from the page. When you performed another bulk analysis, although no check boxes appeared to be selected, the previously selected assets were analyzed. This issue has been resolved. Now, all selections clear when you navigate away from the Thickness Monitoring Overview page.	TFS355271
Previously, in a Thickness Monitoring (TM) Equipment or Thickness Monitoring (TM) Functional Location Data Loader, even if you entered an invalid value in the Measurement Date column on the Measurements worksheet, the Measurement record was created after you loaded data. And, the Measurement Date field was populated with the date on which the Measurement record was created. This issue has been resolved. Now, in this scenario, the Measurement record is not created.	TFS347513
Previously, when you used a Thickness Monitoring (TM) Equipment or Thickness Monitoring (TM) Functional Location Data Loader to update measurements in a different time zone than the time zone in which the original measurements were created, new measurement records were created, and the existing measurements were not updated. This issue has been resolved.	TFS345242

Table 90. Deferred Features
Description	Tracking ID
Corroded Area Measurements.	TFS101752
Dataset integration with dataloggers.	TFS83553
Exporting data to Excel via the TM Dataloggers interface.