V4.3.1.0.0 Release Notes
Action Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now implement one or more strategy actions by creating a Proof Test Task or linking the actions to existing Proof Test Tasks. | US352739 |
In the RBI Admin Preferences page, if the Implement Recommended Actions to Tasks in ASM check box is cleared, the Apply Updates (), Unlink Implementation (), Send to ASI Package (), and Implement buttons are now disabled in the Strategy Actions section of the Action Management page. This is applicable for actions sourced from the Risk Based Inspection or Compliance Management modules. | US352738 |
The performance of the Strategy Actions query has been improved. | US338510 |
Description | Tracking ID |
---|---|
Previously, in the General Recommendation datasheet, when the Alert Assignee When Due check box was selected for a record, alert email messages were not sent. This issue has been resolved. | DE116027 |
Previously, in the Recommended Actions section, when you entered the search criteria in a filter box, the row containing the filter boxes disappeared from the grid. This issue has been resolved. | DE115075 |
Previously, in the Recommended Actions pane, if you selected a Recommended Action and attempted to create an EAM Notification from a General Recommendation and it failed, an incorrect message appeared. | DE105557 |
Previously, even though the Meridium Core license was activated, the following options appeared in the Implement drop-down list box of the Strategy Actions section:
| DE102170 |
Previously, in the expanded view of the Recommended Actions pane, the search function worked only on the RECOMMENDATION HEADLINE column. This issue has been resolved. Now, the search function works on all the columns in the Recommended Actions section. | DE79684 |
Activate Licenses
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you activated a license, you had to manually switch the data source to which you applied the license to offline, and then to online. Now, you do not have to perform this action. After activating the license, you must log off from GE Digital APM and log in again. | DE109678 |
AMS Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The AMS Analytics feature is not available in GE Digital APM V4.3.1.0.0. | F45351 |
APM Connect
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID |
---|---|
APM Connect now supports UDLP V2.7.0. The data loader framework in UDLP V2.6.1 is compatible with GE Digital APM V4.3.1.0.0. | US354669 |
The automatic data loaders are now supported in APM Now. Using these data loaders, you can automatically import data into GE Digital APM. | US354406 |
The SAP Equipment and Functional Location technical characteristics are now supported for multiple language data extraction. | US351143 |
To enhance the performance of data loading processes, the default severity level for logging events has been changed from DEBUG to ERROR. | F42056 |
Description | Tracking ID |
---|---|
Previously, for the Web API tests on the staging database, the Check connection failed as the staging database password was always passed as an empty value in payload. This issue has been resolved and the staging database password is now sent as an encrypted value in payload. | DE117063 |
Previously, when using Work Management Interface (WMI), all tasks were created in the EAM system that was marked as default, restricting the WMI to a single EAM system. This issue has been resolved. Now, WMI can be used with multiple EAM systems. | DE115487 |
Previously, when a connection failure occurred during data loading, the EAM job failed. This issue has been resolved. | DE115409 |
Previously, in a Work History record, the values from the Event Short Description field were not extracted when Object Lists were involved. This issue has been resolved. | DE114806 |
Previously, when using automatic data loaders, if multiple records were imported at the same time, sometimes, a few records were skipped. This issue has been resolved. | DE111514 |
Previously, Apache Karaf crashed in the cloud environment because of the way the APM Connect data loader job handled the conversion of the .xlsx file to a .csv file. This issue has been resolved. Now, the .xlsx file is converted to a .csv file before it is sent to Apache Karaf. | DE111512 |
Previously, when using automatic data loaders, an error message appeared although the records were imported successfully. This issue has been resolved. | DE111339 |
Previously, the Planned Work and Work Management Interface integration did not allow filtering by Maintenance Plant. This has been resolved. You can now use Maintenance Plant as a filter for Planned Work and Work Management Interface. | DE110851 |
Previously, if the connection between the PDI service and the OPC servers was lost for longer than the restart wait time (as configured in the ServiceRestartDelay parameter in the PDI configuration file), the connection was not restored. This issue has been resolved. | DE110733 |
Previously, when you saved a recommendation that was not associated with any asset and whose EAM Notification check box was selected, a notification was created in the EAM without an asset. This issue has been resolved. Now, when you save a recommendation that is not associated with any asset, an error occurs. | DE110716 |
Previously, in the configuration page for the Data Loaders staging (IR) database, the behavior of the Sub Object Number was defined incorrectly. As a result, cardinality errors occurred when importing data. This issue has been resolved. | DE110612 |
Previously, if you accessed GE Digital APM in Japanese culture, data loaders were not downloaded correctly. This issue has been resolved. | DE108822 |
Previously, in a Work History record, the value in the Equipment Class Description field was not extracted when Object Lists were included. This issue has been resolved. | DE107281 |
Previously, in a Work History record, the value in the Location Description field was not extracted when Object Lists were included. This issue has been resolved. | DE107277 |
Previously, when using the Unified Asset Ingestion Data Loader to load assets into GE Digital APM, the Predix Asset Model was populated with the value of Unique ID instead of the Equipment ID. Now, the Predix Asset Model correctly displays the Equipment ID of the asset. | DE103245 |
Previously, in an ABAP Extraction patch, if the data fields contained text with multiple spaces, the text was truncated to include only one space. Due to this, there was a mismatch in the data between SAP and APM. This issue has been resolved. Now, the text in the data fields is not condensed. | DE97438 |
Previously, if an SAP Equipment contained a Functional Location and Predecessor Equipment, the Asset Hierarchy was not built as expected after you imported the data loader workbook. This issue has been resolved. Note: If an SAP Equipment contains a Functional Location and Predecessor Equipment, only a relationship to the equipment is created. | US351203 |
APM Data Extraction
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you tried to fetch navigation (relationship) property data using a property request call, the service returned an HTTP 404 error. This issue has been resolved. | DE109958 |
APM Mobile Application
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you attempted to sync a route, the readings were not loaded. In addition, the route was marked done, thus preventing you to unlock the route and load the readings again. This issue has been resolved. | US363216 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
If the SAP Criticality Assessment license is active, criticality values from an assessment are automatically updated in SAP after you move the associated analysis to the Approved state. | US364277 |
To improve performance, the SQL join clauses corresponding to the Asset Group families have been removed from the following catalog queries:
| US354330 |
To improve usability, the risk assessment window has been modified as follows:
| US345815 |
In the ACA Overview page, the performance when loading the tile counts has been improved. | US342276 |
To improve usability, the Description column has been removed from the ACA Analyses query. | US322347 |
You can now access the reference documents for an ACA Analysis by selecting the Reference Documents tab from the Asset Criticality Analysis page. | US318203 |
To enhance usability in the Assessment workspace, functionality to export an analysis assessed using a Criticality Checklist has been added. | US316934 |
To enhance usability in the Asset Criticality Overview page, functionality to export analyses assessed using a Criticality Checklist has been added. | US316933 |
Description | Tracking ID |
---|---|
Previously, when you attempted to update SAP from the Analysis View, incorrect error logs were created. This issue has been resolved. Now, in this scenario, the correct error logs are created. | DE115040 |
Previously, when you attempted to access an assessment that contained double quotes in the Basis for Assessment field, an error occurred, and the assessment did not load. This issue has been resolved. | DE108039 |
Previously, in the Risk section of the Analysis Summary page, if you accessed an analysis whose associated Risk Matrix record had the Use Aliases? check box selected, the Total Risk value on the risk assessment appeared as a numeric value instead of an alias value. | DE105758 |
Previously, while using the ACA data loaders, the logs sometimes did not capture the data that was successfully loaded. This issue has been resolved. | DE104003 |
Previously, column headings and fields were not properly localized in the following locations:
| DE101533 |
Previously, regardless of your culture settings, the values in the State column were displayed in English. This issue has been resolved. Now, the values in the State column are displayed in the language that is based on your culture settings. | DE99458 |
Previously, if a field in a checklist was updated by a policy, the corresponding entity was not updated with the latest field value. This issue has been resolved. | US358409 |
Previously, in the ACA Admin page, if you locked the Probability, Consequence, or Protection Level fields for an ACA System Criticality Analysis, and then accessed the Risk Matrix for that analysis, the fields were not locked. This issue has been resolved. | US334389 |
Description | Tracking ID |
---|---|
For the Asset Criticality Analysis and Asset Criticality Analysis System families, the following fields are no longer available:
| US274720 |
Asset Health Manager
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Performance in the Risks section of the Health Summary page has been significantly improved. | US338922 |
To improve performance when determining whether health indicator records are up to date, the Out of Sync status has been removed from the Health Summary page, and a new section, General Settings, has been added to the AHM Admin page. In this section, you can select the Check Last Health Indicator Update button to view a window that displays the date and time of the last health indicator update. |
|
To prevent users from accidentally deleting mappings, the Health Indicator Has Mapping (MIR_HT_IN_HS_MP) relationship has now been converted to use a foreign key. | US272028 |
To improve usability, the default time range in the Health Indicator trend chart is now MAX (that is, maximum) instead of 1Y (that is, one year). | US265481 |
Description | Tracking ID |
---|---|
Previously, in the Health Indicator Details page, when you clicked the Configuration Tab, the Configuration workspace did not display the Health Indicator Source datasheet on the initial page load. This issue has been resolved. | DE117339 |
Previously, in the Health Summary page, when you attempted to view the data for the Home level of the Asset Hierarchy, an error message appeared, stating that the risks could not be loaded. This issue has been resolved. | DE114318 |
Previously, in the <Asset Name> workspace, links for Asset Health Manager did not appear. Additionally, when you accessed the Health Summary page, the page loaded slowly, and error messages appeared. This issue has been resolved. | DE108371 |
Previously, because time stamp values for health indicator readings were truncated, health indicator readings were sometimes duplicated, and sometimes health indicators erroneously appeared to be out of sync. This issue has been resolved. | DE106890 |
Previously, in the Health Summary page, sometimes a No Status icon () erroneously appeared next to health indicators that had a valid status. This issue has been resolved. | DE106606 |
Previously, in the Asset Health Overview page, the results in the pie chart were incorrect. This issue has been resolved. | DE106562 |
Asset Hierarchy
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now view the number of alerts created for an asset when you access the module-specific data for the asset. To facilitate this enhancement, a new row, Predictive Analytics Life Cycle, has been added in the Reliability section of the <Asset Name> workspace. | US361533 |
Description | Tracking ID |
---|---|
Previously, in the Group section of the Asset Finder window, when you attempted to add a group of assets, an error occurred. This issue has been resolved. | DE107347 |
Asset Strategy Implementation
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The performance of the Manage Actions section in the ASI Package page has been improved. To facilitate this enhancement, the Manage Actions section has been modified to use the following Catalog query: Public\Meridium\Modules\Asset Strategy Management\Implementation\Queries\Get Actions For Package | US350918 |
To enhance usability, in the ASI Package workspace, importing a task list is now a background operation. | US337748 |
To enhance performance and scalability, the implement package operation has been converted to a job. | US337746 |
In the ASI Overview page, the Create New Package button has been renamed New Package. | US306105 |
To enhance usability, in the ASI Overview page, performance when loading large implementation packages has been improved. | DE105551 |
Description | Tracking ID |
---|---|
Previously, an Asset Strategy Implementation package with large number of plans, took a long time to load. This issue has been resolved. | US347269 |
Previously, when you attempted to create an Operation from a Task List, the value in the Plant box of the Task List was not inherited by the Operation. This issue has been resolved. | US318590 |
Previously, if you deleted an imported task list for a maintenance item, and then attempted to import any task list, an error occurred. This issue has been resolved. | DE109359 |
Previously, if you implemented a strategy maintenance plan in SAP, the unit for scheduling period appeared incorrectly. This issue has been resolved. | DE108948 |
Previously, if your Culture setting was not English and if you imported an action from Asset Strategy Management, in the Cycle UOM drop-down list box of the Manage Cycles window, the value Years was not translated into the language corresponding to your Culture setting. This issue has been resolved. | DE108368 |
Previously, when you attempted to link an action to a tasklist operation, an error occurred if the action interval unit was modified. This issue has been resolved. | DE108366 |
Previously, using the Locate Task List window, when you attempted to search for a task list by using a search term that consisted of * and a combination of other characters, search results were not returned. This issue has been resolved. | DE104921 |
Previously, if you had sent actions to an ASI Implementation Package in the Implemented state, the state of the package remained Implemented. This issue has been resolved. Now, in this scenario, the state of the package is changed to Partially Implemented to indicate that all the actions are not yet implemented. | DE100782 |
Previously, regardless of your culture settings, the values in the State column were displayed in English. This issue has been resolved. Now, the values in the State column are displayed in the language that is based on your culture settings. | DE99458 |
Previously, in certain conditions, when a task list with operations was sent to SAP, an error occurred. This issue has been resolved. | DE95210 |
Previously, if a Maintenance Plan contained a cycle, you could still access the Maintenance Strategy field in the Maintenance Item workspace. | DE95201 |
Previously, when you attempted to update linked Actions with the same action interval units, the Actions that were previously linked to the Work Management Item were no longer linked to the item. This issue has been resolved. | DE88859 |
Asset Strategy Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now select the Source link in the Action section for an Action promoted from another module. | US352757 |
You can now implement one or more strategy actions by creating a Proof Test Task or linking the actions to existing Proof Test Tasks. | US352739 |
In the RBI Admin Preferences page, if the Implement Recommended Actions to Tasks in ASM check box is cleared, the Apply Updates (), Unlink Implementation (), Send to ASI Package (), and Implement buttons are now disabled in the Implement Actions section of the Strategy Details page. This is applicable for actions sourced from the Risk Based Inspection or Compliance Management modules. | US352738 |
You can now perform Risk Analysis functions for the Asset Strategies that are optimized in ASO. | US352463 |
To improve usability, the risk assessment window has been modified as follows:
| US345815 |
To enhance usability, the performance when loading the Risk Profile chart has been improved. | US335378 |
You can now hide the Baseline activate operation from the Strategy Details workspace. To facilitate this enhancement, the ASM Preferences tab has been added to the ASM Admin page. | US333722 |
You can now create strategies and actions from existing Measurement Locations. To facilitate this enhancement, the Import button has been added to the ASM Overview page. | US311299 |
Description | Tracking ID |
---|---|
Previously, when you applied a template to an Asset Strategy, new Risk IDs and Action IDs were not generated. This issue has been resolved. | US337882 |
Previously, if you were assigned to the MI ASM Viewer Security Group, you could create or modify the records of some families. This issue has been resolved. Now, the MI ASM Viewer Security Group has been modified to remove the insert and update privileges for the applicable families. | US335762 |
Previously, in the Asset Strategy Approval report, the labels of axes in the graph were not generic. For example, by default, the labels for currency and risk axes were $ and Risk Rank, respectively. This issue has been resolved. | US333482 |
Previously, you could modify the value in the Plan Length field of the Asset Strategy record that was in the Pending Review state. Consequently, you could also modify the record. This issue has been resolved. Now, the Plan Length field of the Asset Strategy record that is in the Pending Review state is disabled. | US305127 |
Previously, when you implemented an Action as an EAM Maintenance Plan, and then exported the record in a CSV format, the value in the Description field of the Action incorrectly appeared in the exported file. This issue has been resolved. | DE117099 |
Previously, if your culture setting was Japanese, when you accessed the Review Strategy workspace for a Unit Strategy, no values were populated in the State and Operations drop-down list boxes. This issue has been resolved. | DE114831 |
Previously, the Mitigated Financial Risk for an asset was incorrectly calculated. This issue has been resolved. | DE114245 |
Previously, actions generated by applying a template to a Strategy were not linked to the EAM Plan and EAM Plan Details records. This issue has been resolved. | DE113906 |
Previously, if your culture setting was not English, in the Risk Matrix section, the Financial Risk value was calculated incorrectly. This issue has been resolved. | DE113868 |
Previously, in the Strategy Details page, in the Risk Analysis section, the COST PROJECTION chart was plotted with incorrect values for users whose culture setting was not English. This issue has been resolved. | DE113740 |
Previously, for a Risk sourced from the Risk Based Inspection module, in the Risks and Actions section, you could modify the Unmitigated Risk values. This issue has been resolved. | DE112872 |
Previously, you could not activate the Asset Strategy template that had a custom state between the Pending Review and Active states and had controlled strategies. This issue has been resolved. Now, you can transition the template from a custom state to the Active state. | DE112836 |
Previously, if your culture setting had a culture other than English, and you accessed the Review Strategy workspace for a system or unit strategy, the following drop-down list box captions were not translated to the language based on your culture setting.
| DE108776 |
Previously, in the Risks and Actions page, if you attempted to consolidate RCM or FMEA actions, the process could time out. This issue has been resolved. | DE108037 |
Previously, if you used a localization setting other than English, and then attempted to modify the state of a System or Unit Strategy in the Review Strategy workspace, an error message appeared. This issue has been resolved. | DE108015 |
Previously, when you attempted to apply a template as a master strategy template to an Asset Strategy, an error occurred if the template was created using a strategy with risks or actions sourced from other modules. This issue has been resolved. | DE95408 |
Previously, in the Risks and Actions sections of the ASM Overview page, some of the column headings were not translated. This issue has been resolved. | DE93789 |
Previously, when using Internet Explorer, in the Strategy Details page, if you attempted to access the Review Strategy workspace, an error message appeared. | DE88696 |
Asset Strategy Optimization
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, in the Simulation Results workspace, in the Elements section, the value in the Element column was truncated if the strategy ID was long. Now, if the strategy ID is long, the value in the Element column contains the partial strategy ID. | US301529 |
Previously, if a value in the Element column of a Simulation Result exceeded the width of the column, you could not view the complete description of the element. This issue has been resolved. Now, in this scenario, you can hover over the value to view the complete description of the element in a screen tip. | DE118150 |
Previously, when you created a Scenario, the names of the Actions and Risks associated with other Scenarios were changed to the name of the new Scenario. This issue has been resolved. | DE116536 |
Calibration Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID |
---|---|
Calibration Management module now supports all the Unit of Measurements that are supported by Fluke 74x -75x calibrators. To facilitate this enhancement, the following changes have been made:
| F45470 |
Description | Tracking ID |
---|---|
Previously, a user with APM Viewer role could not access the Calibration module. This issue has been resolved. | DE119038 |
Previously, while receiving the Calibration results from a Control Valve, Magnetic Flow, or pH Calibration template with Custom Input or Custom Output values, the AF error or AL error were calculated incorrectly. This issue has been resolved. | DE117646 |
Previously, after you upgraded the GE Digital APM database from V3 to V4, certain Calibration Events did not appear in the Calibration Events section. This issue has been resolved. | DE116610 |
Previously, after you upgraded the GE Digital APM database from V3 to V4, in the Calibration Queue section, the records that existed in the database before the upgrade did not appear because the existing Calibration Templates were not directly linked to the Calibration Tasks. This issue has been resolved. | DE116609 |
Previously, after you upgraded the GE Digital APM database from V3 to V4, when you created a Calibration (Event) manually from a Calibration Task, saved the record, and entered values for As Found or As Left in the Calibration section, the error percentages were not calculated. This issue has been resolved. | DE116608 |
Previously, after you upgraded the GE Digital APM database from V3 to V4, when you attempted to create a Calibration (Event) manually from a Calibration Task, an error message appeared. This issue has been resolved. | DE116606 |
Previously, when you added assets to a Calibration Profile, the applied profile that was created was in the Development state; the Template State value was not copied from the Profile Template to the applied profile. This issue has been resolved. | DE116365 |
Previously, for a newly created Calibration Event received from an automated calibrator, the mapping type value appeared in the Instrument Manufacturer field and Instrument Model Number field, instead of the linked asset manufacturer and model number. This issue has been resolved. | DE110348 |
Previously, when CalibDeviceMappingsUpgradeUtility was run to upgrade to 4.3.0.0.0 or later for replacing the old Device Mapping IDs with the new Device Mapping IDs on all the existing templates, an error occurred. Due to this, you could not perform calibration on the old templates using a Fluke calibrator. This issue has been resolved. Note: The upgrade was required only if you wanted to use the Fluke documenting process calibrator. | DE110216 |
Previously, when you sent a record to a Fluke calibrator to perform a square-root calibration, the calibration results were sent to GE Digital APM with the following issue in the RMS error calculation: The Input Measure AF and Input Measure AL values were not square-rooted although they were square-rooted in the Fluke device. This issue have been resolved. | DE109414 |
Previously, in the Calibration Event family, when you configured the Test Equipment ID field as a required field, and then attempted to save a Calibration Event record, an error occurred because the Test Equipment section of the record that contained the Test Equipment ID field was disabled. This issue has been resolved. | DE109327 |
Previously, if you sent data to a Fluke calibrator, and performed a calibration using a Calibration Template, Analog or Calibration Template, Discrete record with the input UOM set to Degrees Celsius (DEG C), an error occurred. This issue has been resolved. | DE108264 |
Previously, when you accessed a localized version of the Calibration Management module, and then attempted to link a task with a calibration profile, the values in the Look in drop-down list box in the Search window loaded after a long time. This issue occurred because all the families and records were loaded, instead of only the Calibration Task family. This issue has been resolved. | DE108051 |
Previously, after uploading a reference document for a standard gas cylinder or component, if you attempted to modify a field value in a standard gas cylinder, an error occurred. This issue has been resolved. | DE107367 |
Previously, after receiving multiple records from a calibrator, if you did not save all the records that were received, the values for the saved records were always picked from the first record in the list. This issue has been resolved. | DE106591 |
Previously, when you simultaneously sent multiple records with the same number of test points and different custom test point percentages to a calibrator, the test point percentages of the last record were copied to the remaining records. Due to this, only the last record displayed the correct result. This issue has been resolved. | DE106004 |
Previously, in a calibrator, if you entered the name of a user who was not a member of the MI Calibration Administrator or MI Calibration User Security Group, and tried to receive data from a calibrator, although you received the data, instead of an error message, a blank screen appeared. This issue has been resolved. | DE105634 |
Catalog
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
If you log in to GE Digital APM as a Super User, you can now perform the following operations in the Catalog page:
| US201765 |
Description | Tracking ID |
---|---|
Previously, after you renamed a folder within the Public folder using the Catalog Folder Properties window, if you attempted to rename the folder consecutively, an error message appeared. This issue has been resolved. | DE50686 |
Compliance Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Inspection Plan is now integrated with Risk Based Inspection in addition to Compliance Management. To facilitate this enhancement:
| US367968 |
Previously, the Assets with Inspection Plan section of the Compliance Management Overview page displayed the assets that were associated with an Inspection Plan. Now, this section displays the assets that are associated with an Inspection Plan and linked to a Compliance Strategy Template. Additionally, the Update Inspection Plans button in this section has been renamed Update Compliance Recommendations. | US367595 |
When you update Compliance Recommendations on the Inspection Plan that is in the Modified state, the existing Compliance Recommendations are now deleted, and new Compliance Recommendations are generated based on the mapped policy in the Compliance Strategy Template. | US360461 |
You can now implement Compliance recommendations that belong to an Inspection Plan in:
| US335134 |
Description | Tracking ID |
---|---|
Previously, after creation or update of multiple Inspection Plan records, one or more of the inspection plans might not have been able to be transitioned to the Approved state. An error message appeared during approval indicating that the inspection plan was currently being updated. This issue has been resolved. | DE116073 |
Data Loaders
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you imported a data loader workbook that contained a date, the corresponding date field in GE Digital APM was not updated according to the GE Digital APM time zone (that is, Coordinated Universal Time (UTC)). This issue has been resolved. | DE116147 |
Previously, when you attempted to import large analyses using the following data loaders, the operation exceeded the timeout period, causing the import process to fail.
| DE113578 |
Previously, in a cloud environment, when you tried to load a .zip file containing .csv files using the Data Loader interface, the load intermittently failed with the message access denied. Now, the files load without errors. | DE109151 |
Datasets
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, if your culture setting was not English, and if you accessed the Dataset page, the following elements were not translated into the language based on your culture setting:
| DE105420 |
Previously, in a dataset that contained multiple rows with same values, the following issues existed:
| DE105172 |
eLog
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID |
---|---|
You can now access the assignments that have been approved. To facilitate this enhancement, a new section, Completed Assignments, has been added to the My Assignments workspace of the Shift Summary page. | US363803 |
You can now generate a report for one or more Shifts for a given period. To facilitate this new feature, the Shift Reports section has been added to the eLog Overview page. | US359960 |
Description | Tracking ID |
---|---|
Previously, when creating a Shift, if you navigated away from the Add New Shift page without saving your changes, a warning message did not appear. This issue has been resolved. Now, in this scenario, a warning message appears, asking if you want to save your changes. | DE103893 |
Failure Modes and Effects Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
To improve usability, the risk assessment window has been modified as follows:
| US345815 |
You can now restrict modifying an FMEA Analysis and its child record to team members only. To facilitate this enhancement, the RCM FMEA Preferences tab has been added to the RCM FMEA Admin page. | US340645 |
You can now modify the Recommendation at all the levels in the analysis hierarchy. | US313842 |
In the FMEA Overview page, the Create New Analysis and Create New Template buttons have been renamed New Analysis and New Template, respectively. | US306105 |
Previously, in the FMEA Recommendation report, the Interval and Resource columns were not translated. This issue has been resolved. Now, the values selected for Interval Units will always be translated. The values of Recommended Resource will be translated only if they are selected from the drop-down list box. If you enter a value that is not in the drop-down list box of Recommended Resource, it will not be translated. | US301684 |
To enhance performance and scalability, the apply template operation has been converted to a job. | US293368 |
Description | Tracking ID |
---|---|
Previously, when you attempted to promote a Recommendation that was created using the Failure Modes and Effects Analysis (FMEA) data loader, an error occurred. This issue has been resolved. | DE116212 |
Previously, you could not consolidate the Recommendations that were created using the Failure Modes and Effects Analysis (FMEA) data loader. This issue has been resolved. | DE116023 |
Previously, the Driving Risk Category for Mitigated Risk Assessments was determined by the Unmitigated Risk Assessment. This issue has been resolved. | DE115096 |
Previously, in Internet Explorer, if the Equipment or Functional Location datasheets took a long time to load, the risk summary did not appear in the Recommendation window. This issue has been resolved. | DE110148 |
Previously, when you added a failure mode for an equipment or functional location, the Related Asset Type field was not populated with the correct Taxonomy Type. This issue has been resolved. | DE109409 |
Previously, the count of Recommended Actions that appeared in the Recommended Actions pane was incorrect. This issue has been resolved. | DE108791 |
Previously, in the FMEA Overview page, if you selected the Help button when you attempted to create a template, the Help documentation did not appear. This issue has been resolved. Now, the Help button does not appear when you attempt to create a template. | DE108018 |
Previously, you encountered database errors when using FMEA data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders. | DE105997 |
Previously, you could delete Recommendations that were not at the Failure Effect level. This issue has been resolved. Now, you can delete only the Recommendations that are at the Failure Effect level. | DE104267 |
Previously, while using the FMEA data loaders, the logs sometimes did not capture the data that was successfully loaded. This issue has been resolved. | DE104003 |
Previously, regardless of your culture settings, the values in the State column were displayed in English. This issue has been resolved. Now, the values in the State column are displayed in the language that is based on your culture settings. | DE99458 |
Previously, the FMEA Recommendations report contained ambiguous text for undefined values. This issue has been resolved. Now, undefined values in the report are represented by zeros. | DE93935 |
Previously, you could promote a non-global FMEA asset template to an ASM template. This issue has been resolved. Now, only global FMEA asset templates can be promoted to ASM templates. | DE88303 |
Previously, when you created an Analysis from a template, the template builder did not retain the selected assets. This issue has been resolved. | DE88189 |
Previously, in the Recommended Actions pane, you could select the Linked Recommended Actions tab before saving a new recommended action. This issue has been resolved. | DE85488 |
Previously, if you searched for the FMEA template record in the hierarchy, an error occurred. This issue has been resolved. Now, you can search for a child node of the selected parent record from the hierarchy. | DE79677 |
Family Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The following enhancements have been made to the Behavior section of the <Field Name> workspace:
| F44331 |
In an offline form, if you enter a value in a field, the values in the subsequent fields are now populated based on the value you entered. To facilitate this enhancement, the drop-down list boxes are now dynamically populated with values from the system code table that references values from the related family field. | US343642 |
Description | Tracking ID |
---|---|
Previously, when creating a family field, if you selected the Always Required option, the Spread to SubFamily check box was automatically selected. This issue has been resolved. | DE106515 |
Previously, when you changed the field length for a character field using Family Management, the change did not reflect in the physical table of the data source. This issue has been resolved. | DE102614 |
Previously, you could create a family that contained invalid data (Microsoft SQL Server reserved keywords) as the family caption even though an error message appeared. This issue has been resolved. | DE97431 |
Previously, while executing a query in the State Configuration field in the RBI Recommendation family, the field value returned by the query was not formatted correctly, although the Formatted check box had been selected. This issue has been resolved. | DE77356 |
Family Policies
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now use a reserved parsing keyword, such as the name of a function or a mathematical constant, as an input variable name in a Math node. | US359538 |
When you update the execution schedule of a policy other than in the Details workspace, the Policy Trigger Job is now configured according to the updated schedule. | US339892 |
You can now validate and execute a policy that contains a Collection Filter node with an empty collection. However, a warning message appears in the Node Execution Details window for the node, indicating that the collection is empty. | US334152 |
To enhance the usability of the model canvas in the Design workspace, the following enhancements have been made:
|
|
To improve the performance of policy execution, a node whose output is not used by any node of the policy model is no longer executed during the execution of the policy. This enhancement has been made to the following nodes:
| US327421 |
In the Properties window for a node, when you specify a family ID, the name of the family associated with the family ID is now added to the default name of the node. However, if you modify the default name of the node before specifying the family ID, the modified name of the node is not updated with the name of the family. This enhancement has been made to ensure consistent behavior of the following nodes:
| US325425 |
You can now download the image of a policy model to your local drive. To facilitate this enhancement, the Download button () has been added to the model canvas in the Design workspace. | US325413 |
To enhance the usability of the Design workspace, the following enhancements have been made:
| US321474 |
You can now refresh the metadata used by a policy and its nodes without refreshing the policy. To facilitate this enhancement, the Refresh Policy Metadata button () has been added to the following elements of the Design workspace:
| US315588 |
You can now revert the transaction that triggers a family policy. To facilitate this enhancement, the Cancel Transaction node has been added to the Actions section of the toolbar in the Design workspace. | US236247 |
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels. | US184916 |
Description | Tracking ID |
---|---|
Previously, in the Validation section, if you copied the null value of an instance to use it as an ad hoc test value for validation, the validation results of the policy were incorrect. This issue has been resolved. | US306739 |
Previously, if you configured the Policy input of a Sub Policy node, then copied and pasted the node, the copy of the Sub Policy node did not display the input fields for the specified Policy. This issue has been resolved. | DE116740 |
Previously, if you attempted to access a policy containing an Entity, Create Entity, or Edit Entity node referencing an entity family that did not exist in GE Digital APM, the policy failed to load. This issue has been resolved. | DE113400 |
Previously, if you entered a value in the Value section of a Text node that could be interpreted as a date or time span (for example, Sunday or 30d), the value was converted to the standard display format for a date or time span prior to being inserted into the Text Pattern. This issue has been resolved. Now, the Text node treats these values as strings. Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the Text node is configured so that the date and time and the time span values are mapped from the Constant node. | DE113062 |
Previously, if a sub policy contained multiple Return Value nodes with the same name, when you mapped the results from the sub policy to a successor node, the successor node input value list displayed the Return Value name multiple times, even though a single value was returned from the sub policy. This issue has been resolved. Now, the Return Value name is displayed only once in the input value list. | DE113041 |
Previously, if you specified an input value in a Constant node that could be interpreted as a date or a time span (for example, today or 700D) and specified string as the data type for the node, the input value was converted to a date or time span. This issue has been resolved. Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the correct data type is specified in all the Constant nodes. | DE112424 |
Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved. | DE111238 |
Previously, when you attempted to modify a record that triggered an After Update family policy containing a Baseline Rule node, and if the baseline rule configured for the Baseline Rule node updated the same record that triggered the policy, a time-out error occurred and the record was not modified. This issue has been resolved. | DE110458 |
Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved. | DE110279 |
Previously, in the Properties window for an Edit Entity node, in the Auto-map field values section, if you selected Yes, the Entity Key Column box was enabled as a required field. This issue has been resolved. Now, in this scenario, the Entity Key Column box is enabled as an optional field, and a warning message appears in the notification bar, indicating that you have not specified any value in the Entity Key Column box. | DE107430 |
Previously, in the Properties window for a Math node, when you specified the variable names, an error message appeared in the notification bar, indicating a conflict between the variable names, even when there was no conflict in the names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
| DE107317 |
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
|
|
Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value that matched the default value for the corresponding field, the execution of the policy failed. This issue has been resolved. | DE106599 |
Description | Tracking ID |
---|---|
When you export a policy from GE Digital APM V4.3.1.0.0, and then access the exported policy in an older version of GE Digital APM, the connectors in the policy model do not appear even though you can successfully validate and execute the policy. The workaround for this is to manually redraw the connectors between the nodes before making any modifications to the policy. | DE116734 |
Description | Tracking ID |
---|---|
The Close Event node has been removed from Family Policies. Note: The functionality of the Close Event node depends on the Policy Events associated with a policy instance. As family policies do not contain any policy instances, the Close Event node did not function as expected. | DE114843 |
Foundation
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
GE Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The GE Analytics feature is not available in GE Digital APM V4.3.1.0.0. | F45351 |
General Dashboards
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, if the catalog path for a query or a graph is used in a dashboard and if it contained an ampersand (&), the widget failed to load. This issue has been resolved. | DE118708 |
Previously, in the edit mode of the Dashboard page, you could not drag a Graph widget that did not contain a name to another location in the canvas. This issue has been resolved. | DE105211 |
Graphs
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
In the Settings pane, in the Series section, in the Color column, the colors have been updated. Note: The colors in the existing graphs remain unchanged. | US313324 |
Description | Tracking ID |
---|---|
Previously, on a Stock Chart Graph with multiple lines, the tooltip labels were incorrect. This issue has been resolved. | DE113773 |
Previously, the results displayed in a graph were incorrect if the associated query included the same family as both a predecessor and a successor to a JOIN clause, and if the query result contained the same field from each instance of the family. This issue has been resolved. | DE106005 |
Previously, hyperlinks in a heat map did not work correctly. This issue has been resolved. | DE105558 |
Previously, if you accessed a graph from the Catalog folder for which you had the permission to view, but if you did not have the permission to view the Catalog folder where the data source query of the graph was stored, an incorrect error message appeared. This issue has been resolved. Now, a correct error message appears, indicating that you do not have the permission to view the query result used by the graph. | DE101164 |
Inspection Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
To enhance usability, when the Inspection Management (IM) Assets and Inspection Management (IM) Functional Location data loaders are run, the following values are now updated in the Interface Log record.
| US366047 | ||||||||||||||||||
To enhance usability when using a UOM conversion set, the values in the numeric fields are rounded off according to the type of the numeric field as described in the following table.
| US358876 | ||||||||||||||||||
A new Human Resource role, Contract Inspector, is now available. A Contract Inspector can update the Status field in Inspection records to Pending Approval without being the user defined in the Inspection Report Owner field if they are a Team Member in the associated Inspection record. | US344314 | ||||||||||||||||||
Using the Equipment and Functional Location data loaders, a Contract Inspector who is a Team Member in the associated Inspection record can now change the value in the Status field to Pending Approval without being the user defined in the Inspection Report Owner field. | US344314 | ||||||||||||||||||
If you are using Status to manage your Inspection Recommendation records and you are a Team Member in the associated Inspection record, you can now transition the Inspection Recommendation to the Pending Review status without being the user defined in the Author field. | US344314 | ||||||||||||||||||
You can now implement Recommended Actions that belong to an Inspection Plan in:
| US335134 |
Description | Tracking ID |
---|---|
Previously, the Inspection Lock field was disabled unless you were the Inspection Report Owner. This field is now enabled if you are a Team Member in the associated Inspection record. | US344314 |
Previously, if your culture setting was not English, when you accessed the checklist inspections for pre-defined API checklists or configured checklist templates, the values in the Name and Category fields of the Checklist Finding records were not translated to the language based on your culture setting. This issue has been resolved. | DE116950 |
Previously, you could not print Inspection Reports in bulk if the Inspection ID contained special characters that were not supported by the Windows operating system in a file name. This issue has been resolved. | DE115279 |
Previously, if the Inspection ID field of an Inspection Event contained special characters, which were not supported by Windows operating system for a file name, you could not bulk-print the Inspection Event from the Inspection Management Overview page. This issue has been resolved. | DE114406 |
Previously, for the Inspection Task record that did not contain an Inspection Document Type, when you selected a link in the CREATE INSPECTION column in the Results section of the query associated with the Underlying Inspection Tasks section, an error message appeared. This issue has been resolved. Now, in this scenario, a window appears to prompt you to select the Inspection Document Type for the record. | DE113031 |
Previously, when you switched from the Bulk Review Inspections workspace to a different tab or page, and then returned to the Bulk Review Inspections workspace, you could not approve the Inspection records. This issue has been resolved. | DE111741 |
Previously, even if the Keep History check box was selected for a field in the Inspection Task family, you could not access the history of the field in an Inspection Task. This issue has been resolved. | DE110746 |
Previously, in the Inspection Data section of the Full Inspection: <Inspection ID> workspace for an inspection, if you updated a master/detail datasheet that was created for the Full Inspection family, and then attempted to save the datasheet, two spinners appeared, indicating that the data was being updated for the inspection. This issue has been resolved. Now, in this scenario, only one spinner appears. | DE104168 |
Previously, when adding items to a Checklist Configuration template, when you searched for and added an item to the template, the item was successfully added. However, when you searched for a second item, it did not appear in the search results, even if it was available in the list of items. This issue has been resolved. | DE101414 |
Previously, you could modify the site assigned to the Resource Role records because the Resource Role family was enabled for site filtering. When the site assigned to a Resource Role for a given user was modified, the name of that user did not appear in the drop-down list boxes in the respective datasheets. This issue has been resolved. Now, the Resource Role family is no longer enabled for site filtering and the user names appear correctly. Note: The fields containing the user names will continue to be filtered based on the site to which the respective record is assigned. | DE91540 |
Previously, for an Inspection Profile, in the Inspection Profile Details section, if the Item ID box contained a special character, GE Digital APM could not automatically generate the General Finding report that was based on the associated Inspection Scope. This issue has been resolved. | DE83319 |
Previously, when an inspection event was created for an asset for which the Inspection Profile records were defined and sequenced, and when the auto-generate findings feature for the selected inspection event family was enabled, the automatically created General Finding records were not arranged in the order of the values in the assigned Sequence field. This issue also existed in Inspection Field Data Collection when the inspection event was downloaded. This issue has been resolved. Now, when viewing an inspection event in Inspection Management or in Inspection Field Data Collection, the General Finding records are arranged in the order of the values in the assigned Sequence field. Note: If the Inspection Profile records do not contain a value in the Sequence field, or if the General Finding records have been manually created, the General Finding records are arranged in alphabetical order of the values in the Inspection Profile Item field. | DE82618 |
Previously, when you used the IM Functional Location Data Loader to load Inspection Methods, if the Inspection Methods did not have a Method Category defined in the data loader, subsequent Inspection Methods that shared an Inspection Profile did not load. This issue has been resolved. | DE82397 |
Installation
This topic provides a list of product changes released for this module on the dates listed below.
Version: <number>
Description | Tracking ID |
---|---|
Elasticsearch is no longer included in the GE Digital APM distribution package. | US343529 |
Life Cycle Cost Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, in an LCC Fleet Management analysis, the amount of life that remained for an element was incorrectly calculated. This issue has been resolved. | DE112731 |
Manage Translations
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, if your culture was set to Russian, if you accessed a datasheet that had fields with Units of Measure (UOM) available as the field values, the UOM, Meters, was incorrectly translated. This issue has been resolved. | DE102506 |
Maps
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, if your GE Digital APM system used an Oracle schema, the Baseline Map Query did not return any results, and no points were displayed on the Map. In addition, regardless of the database type, points were not displayed on the Map if the Description field of the Functional Location was empty. These issues have been resolved. Note: If you have previously modified the Baseline Map query in the Public folders, you must copy the updated Baseline Map Query found in the Baseline\Meridium\Modules\Core\Queries\Map Queries folder to the Public folders in order for this change to be applied. | DE116158 |
Previously, when you accessed a map, and then selected the Edit Filters button (), the Enter Parameter Values window did not appear. This issue has been resolved. | DE81563 |
Description | Tracking ID |
---|---|
Bing Maps is no longer supported in the Maps tool. | DE118148 |
Policy Designer
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now execute any one or all the active instances associated with a Policy on demand without modifying the existing execution settings configured for the policy. To facilitate this enhancement:
| US359689 |
You can now use a reserved parsing keyword, such as the name of a function or a mathematical constant, as an input variable name in a Math node. | US359538 |
You can now configure a policy to create an execution history log record for all the executions or only the executions that result in an error. | US345229 |
You can now set a time limit for executing a policy instance. To facilitate this enhancement, a setting has been added to the Policy Execution Service configuration file. | US344236 |
When you update the execution schedule of a policy other than in the Details workspace, the Policy Trigger Job is now configured according to the updated schedule. | US339892 |
You can now validate and execute a policy that contains a Collection Filter node with a blank collection. However, a warning message appears in the Node Execution Details window for the node, indicating that the collection is blank. | US334152 |
To enhance the usability of the model canvas in the Design workspace, the following enhancements have been made:
|
|
To improve the performance of policy execution, a node whose output is not used by any node of the policy model is no longer executed during the execution of the policy. This enhancement has been made to the following nodes:
| US327421 |
In the Properties window for a node, when you specify a family ID, the name of the family associated with the family ID is now added to the default name of the node. However, if you modify the default name of the node before specifying the family ID, the modified name of the node is not updated with the name of the family. This enhancement has been made to ensure consistent behavior of the following nodes:
| US325425 |
You can now download the image of a policy model to your local drive. To facilitate this enhancement, the Download button () has been added to the model canvas in the Design workspace. | US325413 |
To enhance the usability of the Design workspace, the following enhancements have been made:
| US321474 |
If the execution of the Math node takes a very long time for some mathematical expressions, the execution now times out after a pre-defined duration. To facilitate this enhancement, the MATH_NODE_EXECUTION_TIMEOUT key, which defines the duration after which the execution must time out, has been added to the Meridium.Policies.ExecutionService.exe.config and web.config files, and the default value of the key has been set to 60000 milliseconds. | US320254 |
You can now refresh the metadata used by a policy and its nodes without refreshing the policy. To facilitate this enhancement, the Refresh Policy Metadata button () has been added to the following elements of the Design workspace:
| US315588 |
When you define the execution settings for a policy that does not contain an active instance, a warning message now appears in the notification bar, indicating that the policy does not contain any active instance to execute. | US311955 |
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels. | US184916 |
Description | Tracking ID |
---|---|
Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved. | US335128 |
Previously, if an entity that was specified as a trigger for automatic policy execution was modified more than once within a short time span (that is, less than one second), only one policy execution was triggered. This feature, which was implemented to prevent unintended duplicate policy executions, resulted in some intended policy executions being skipped. This issue has been resolved. Now, policy execution is triggered each time an entity is modified, except for policies that are triggered by new Readings added to a Measurement Location. Note: For policies that are triggered by new Readings added to a Measurement Location, duplicate policy executions are still prevented because the insertion of new Readings using the Rounds Data Collection module results in multiple entity updates. | US324385 |
Previously, in the Validation section, if you copied the null value of an instance to use it as an ad hoc test value for validation, the validation results of the policy were incorrect. This issue has been resolved. | US306739 |
Previously, while accessing GE Digital APM using Internet Explorer 11, when you accessed a policy that contained a Health Indicator node, the policy did not load or took a long time to load. This issue has been resolved. | DE117337 |
Previously, a policy that was configured to be triggered when an Entity was created or modified was intermittently not triggered when the trigger event occurred. This issue has been resolved. |
|
Previously, if you configured the Policy input of a Sub Policy node, then copied and pasted the node, the copy of the Sub Policy node did not display the input fields for the specified Policy. This issue has been resolved. | DE116740 |
Previously, if the Microsoft Message Queuing (MSMQ) service had insufficient resources, the Policy Trigger Service failed to send messages to the policy execution queue, and this action was attempted several times until the messages were sent. Due to this, a large log file was generated by the Policy Trigger Service. This issue has been resolved. Now, a delay has been introduced between consecutive attempts so that the number of error messages added to the log file is reduced. | DE113750 |
Previously, if you attempted to access a policy containing an Entity, Create Entity, or Edit Entity node referencing an entity family that did not exist in GE Digital APM, the policy failed to load. This issue has been resolved. | DE113400 |
Previously, if you entered a value in the Value section of a Text node that could be interpreted as a date or time span (for example, Sunday or 30d), the value was converted to the standard display format for a date or time span prior to being inserted into the Text Pattern. This issue has been resolved. Now, the Text node treats these values as strings. Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the Text node is configured so that the date and time and the time span values are mapped from the Constant node. | DE113062 |
Previously, if a sub policy contained multiple Return Value nodes with the same name, when you mapped the results from the sub policy to a successor node, the successor node input value list displayed the Return Value name multiple times, even though a single value was returned from the sub policy. This issue has been resolved. Now, the Return Value name is displayed only once in the input value list. | DE113041 |
Previously, if you specified an input value in a policy instance for a Point Value node or specified a value in a Constant node that could be interpreted as a date or a time span (for example, today or 700D), and if you specified string as the data type for the node, the input value was converted to a date or time span. This issue has been resolved. Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the correct data type is specified in all the Constant and Point Value nodes.
| DE112424 |
Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved. | DE111238 |
Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved. | DE110279 |
Previously, when you accessed a policy, the following issues may have occurred:
| DE110027 |
Previously, if you copied and renamed an Input node of the policy model, and then saved the policy, the following issues occurred until you reloaded the policy:
| DE109329 |
Previously, in the Properties window for an Edit Entity node, in the Auto-map field values section, if you selected Yes, the Entity Key Column box was enabled as a required field. This issue has been resolved. Now, in this scenario, the Entity Key Column box is enabled as an optional field, and a warning message appears in the notification bar, indicating that you have not specified any value in the Entity Key Column box. | DE107430 |
Previously, in the Properties window for a Math node, when you specified the variable names, an error message appeared in the notification bar, indicating a conflict between the variable names, even when there was no conflict in the names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
| DE107317 |
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
|
|
Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value that matched the default value for the corresponding field, the execution of the policy failed. This issue has been resolved. | DE106599 |
Previously, if the GE Digital APM database contained an active policy configured for automatic execution, and if you added the database as a new data source on the GE Digital APM server, the policy was not executed as per the execution schedule until you updated the policy. This issue has been resolved. | DE53608 |
Description | Tracking ID |
---|---|
When you export a policy from GE Digital APM V4.3.1.0.0, and then access the exported policy in an older version of GE Digital APM, the connectors in the policy model do not appear even though you can successfully validate and execute the policy. The workaround for this is to manually redraw the connectors between the nodes before making any modifications to the policy. | DE116734 |
Process Data Integration (PDI)
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The Process Data Integration (PDI) feature is not available in GE Digital APM V4.3.1.0.0. | F45351 |
Description | Tracking ID |
---|---|
Previously, if you specified that you wanted to store zero readings in the GE Digital APM database, the PDI service stored a reading and then deleted it, which caused performance degradation. This issue has been resolved. Now, the PDI service no longer adds and deletes extraneous readings, and, as a result, database performance is significantly improved. | DE107755 |
Production Loss Analysis (PLA)
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can no longer modify or delete the baseline Impact Codes and Production Event Codes. | US357670 |
When creating a concurrent time-based Production Plan from a plan template, if you modify the start date, the end date is now automatically updated based on the duration defined in the template. | US357386 |
In the Units workspace, in the Production Profile datasheet, you can no longer modify the values in the Product and Product Alias boxes if this Production Profile is associated with a Production Plan. | US351643 |
You can now perform the following tasks if you enable the State Management functionality for the Production Event family:
Note: By default, the State Management functionality is disabled for the Production Event family. | US347103 |
You can now perform the following tasks if you enable the State Management functionality for the Production Plan family:
Note: By default, the State Management functionality is disabled for the Production Plan family. | US338910 |
To enhance usability, the values that appear in the Product drop-down list box in the Production Profile datasheet and the Products column in the Production Plan Builder window are now sorted primarily in numeric order and secondarily in alphabetical order. | US322774 |
You can now deactivate and activate Products. To facilitate this enhancement, the Status field has been added to the Product family. In addition, the Deactivate button () and the Activate button () have been added to the Products workspace in the PLA Administrator page. Note: By default, all the Products are active. | US295390 |
You can now access a set of baseline Production Event Codes. To facilitate this enhancement, in the Event Codes section, the following parent Production Event Codes, along with their child codes, have been added:
| US292952 |
You can no longer modify or delete the baseline OEE Codes. | US289763 |
To enhance usability, in the PLA Administrator page, a warning message now appears when you navigate away from the Codes and Units workspaces without saving your changes. | US281138 |
When creating a Production Plan for a given Production Unit and start date, if another Production Plan already exists for the same Production Unit and start date, a warning message now appears to indicate the possibility of creating a duplicate Production Plan. | US258520 |
Description | Tracking ID |
---|---|
Previously, in the Production Event family, the Unit Key was stored in the Unit field. When you ran a query for Unit Name from Production Event family, the Unit Key was returned. This issue has been resolved. | DE118908 |
Previously, if you were assigned to the Production Loss Accounting Administrator Security Role and you attempted to remove the mapping between an Impact Code and an OEE Code, an error occurred if the mapping was used in a Production Loss record. This issue has been resolved. | DE117124 |
Previously, if the values in the Product Name and Product Alias fields of a Production Profile were different in GE Digital APM or in the Production Loss Analysis (PLA) 1-Admin Data Loader, when you attempted to import Production Plans for the Production Profile using the Production Loss Analysis (PLA) 3-Plan Data Loader, the import job failed. This issue has been resolved. | DE117122 |
Previously, when reconciling Production Losses, you could not modify the value in the Equivalent Downtime Hours field. This issue has been resolved. | DE116667 |
Previously, the Event ID was automatically generated in the format <Event ID> ~ <Unique Sequence Number>. The format has been changed to <Unit Name> ~ <Headline> ~ <Unique Sequence Number>, so that you can add information from the Headline field. | DE116525 |
Previously, the State Management functionality was not activated even if you had enabled the State Management functionality. This issue has been resolved. | DE115597 |
Previously, the list of active Products that appeared while creating or modifying Production Profiles, Plan Templates, and Production Plans were not sorted numerically. That issue has been resolved. | DE114902 |
Previously, when you attempted to create a Production Plan using a Plan Template, the Plan End Time was not automatically set based on the Plan Start Time. This issue has been resolved. | DE114901 |
Previously, all the monetary and quantity values did not appear according to the number of decimal places (that is, precision values) specified in the Settings window. | DE105830 |
Queries
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now use the general form of the CASE expression to create a Meta-SQL conditional query. Example: Use of the general form of the CASE expression in a query
| US311695 |
To make larger queries easier to understand and maintain, you can now define multiple CTE query definitions in a single query. | US304986 |
Description | Tracking ID |
---|---|
Previously, the Number/Mathematical Functions MOD and % did not function and returned an error message. Due to this, you could not determine the remainder from a division operation. This issue has been resolved. Now, the Modulus Meta-SQL function has been introduced for determining the remainder from a division operation. | DE113169 |
Previously, if you were assigned to the MI Power User Role Security Group, and if you accessed APM Now, you could not create the following types of queries:
This issue has been resolved. | DE112398 |
Previously, if conditions were defined for a query, and if you attempted to add a condition in the Or row of the Conditions section, an error occurred. This issue has been resolved. | DE112501 |
Previously, if you selected a null date from the query parameter window, an error message appeared in an Oracle database. This issue has been resolved. Now, null dates are excluded from the query parameter values. | DE107985 |
Previously, when you ran an aggregate query that performed a calculation on the results column of a stored query that contained both TOP and ORDER BY clauses, the aggregate query returned an incorrect value. This issue has been resolved. | DE104815 |
Previously, in an Oracle database, when you ran a query that contained the TOP clause but no ORDER BY clause in formatted mode, the records that appeared in the Results workspace were different from the records that appeared when you ran the same query in unformatted mode. This issue has been resolved. | DE104520 |
Previously, when you ran a query with the Limit Results to Top condition, if the number of records that were returned was less than the value specified in the Limit Results to Top box, this value appeared as the record count in the Results workspace, instead of the actual record count. This issue has been resolved. | DE104519 |
Previously, for a query other than the SELECT query, in the View Query column of the Query page, when you selected a link to access the results-only view of the query, an incorrect error message appeared. This issue has been resolved. | DE103993 |
Previously, in the Condition section of the Design workspace, when you accessed a simple expression in the Criteria or Or cell, the expression appeared in the Advanced section instead of the Simple section of the Expression Builder window, and the Simple tab was disabled. This issue has been resolved. | DE103971 |
Previously, in an Oracle database, when you ran a query that contained the MI_DatePart function, incorrect values appeared in certain columns containing the parts of the date in the query results. This issue has been resolved. | DE102611 |
Previously, when you attempted to run a formatted query containing multivalue fields, an error message appeared, and no results were returned. This issue has been resolved. Note: For limitations in running queries containing multivalue fields in an Oracle data source, refer to: Known Issue KBA V4 – Error message appears when you run a query with multivalue fields. | DE102144 |
Previously, in the Design workspace, when you saved a query for which the Show Totals check box was selected, in the Conditions section, the column that contained the value Group By in the Total row and a value in the Criteria row was duplicated. This issue has been resolved. | DE101176 |
Previously, you could access a query that contained the EXISTS condition for the SELECT subquery in the Design workspace.
Note: The Meta-SQL code cannot be represented in the Design workspace because the EXISTS condition does not have an associated column. Therefore, it should not be accessible from the Design workspace. This issue has been resolved. Now, when you attempt to access the query from the Design workspace, a message appears, stating that the query cannot be displayed in the Design workspace. | DE100395 |
Previously, when you accessed a query in the Design workspace and cleared the Include check box for a column, the code related to the column was deleted from the SQL workspace when the query was saved. This issue has been resolved. | DE97437 |
Previously, in the Design workspace, in the Conditions section, when you selected the Show Totals check box, and then selected the value Count in the Total cell for a field that contained an expression, the COUNT function was not added to the SQL code in the SQL workspace. In addition, when you cleared the Show Totals check box for a query that contained the COUNT function in the SQL code in the SQL workspace, the COUNT function was not deleted from the SQL code. These issues have been resolved. | DE93645 |
Previously, when you ran a query that contained a prompt, the following issues existed in the Enter Parameter Values window:
These issues have been resolved. | DE50924 |
Description | Tracking ID |
---|---|
The fields that appeared when the Include check box was cleared no longer appear in the Entity Key drop-down list box in the Specify Parameters section of the URL Builder window. This change has been made because when you selected a field when the Include check box was cleared, an invalid link was created. | US313866 |
Record Manager
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, in a user session, if you created a user account for a Security User with the email ID associated with the user account, and then accessed a record for the Conditional Alert family, the email ID did not appear in the Fixed Distribution List and Optional Distribution drop-down list boxes. This issue has been resolved. | DE103178 |
Previously, if you had accessed GE Digital APM using Internet Explorer, the horizontal scroll bar in the bulk data form did not operate as expected. This issue has been resolved. | DE90472 |
Description | Tracking ID |
---|---|
You can no longer create a site reference record by selecting the Create New Record button () and entering a value in the Name box in the Site Reference datasheet. Site reference records can be created only from the Sites page. | US348948 |
Reliability Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now define the complete System Reliability diagram in the System Reliability Data Loader. To facilitate this enhancement, the following changes have been made to the System Reliability Data Loader:
| US324023 |
Description | Tracking ID |
---|---|
Previously, in Spares Analysis, an error occurred when you attempted to associate a Reliability Distribution with a Spare Application. This issue has been resolved. | DE118879 |
Previously, when you attempted to apply any filters using the Reliability Automation Rule Builder, the Define Filters drop-down list box displayed an insufficient number of characters for you to make a selection. This issue has been resolved. | DE117508 |
Previously, in the Reliability Analytics page, the record counts on the tabs did not correspond to the selected filter in the Asset Hierarchy. This issue has been resolved. Now, the record counts are as follows:
| DE115896 |
Previously, in a Probability Plot, when you modified the start date of the Analysis Period, an error message appeared. This issue has been resolved. | DE115718 |
Previously, in the System Reliability Analysis page, when you attempted to delete an action, and then selected No in the confirmation window, the action was still deleted. This issue has been resolved. Now, in this scenario, the delete workflow is canceled and the action is retained. | DE115717 |
Previously, in the Reliability Analytics Overview page, when you changed the asset hierarchy level from home to another level, the counts that appeared on the tabs did not change according to the new level. This issue has been resolved. | DE114824 |
Previously, when you accessed a Reliability Analysis, in the workspace for the selected analysis, the site reference was initially displayed as Global. The correct site name was displayed after some delay. This issue has been resolved. | DE114231 |
Previously, in the Production Analysis page, when reviewing the production output data using the Show Data button (), the values in the X and Y columns were not based on the value in the POINTDATE column. This issue has been resolved. Now, the values in the X and Y columns are based on the value in the POINTDATE column. | DE113748 |
Previously, in System Reliability, you could not run a simulation for a System Analysis with frequent failures in risks or with a value in the Last Failure field. An error message appeared, stating that the p parameter must contain a value between zero and one. This issue has been resolved. | DE110846 |
Previously, in the Failure Probability workspace, if you selected Future Probability and then entered a value in the Set Future Probability window, the value in the Future Failure Probability column was not properly updated. | DE109848 |
Previously, when you attempted to access the Reliability Analytics page, the page took longer to load because duplicate API calls were made to the GE Digital APM server. This issue has been resolved. | DE109380 |
Previously, in the Failure Probability workspace of a Reliability Distribution Analysis, if you modified the bounds of the axes, and then modified the Future Probability value for that asset contained within that analysis, the new Future Probability value was not retained for the selected asset. | DE107174 |
Previously, in the Failure Rate Plot workspace of a Reliability Distribution Analysis, if you modified the bounds of either the Adjust Axes or Confidence Level distribution options for that plot and then navigated away from the plot, your selections were not retained. | DE107173 |
Previously, when running a simulation on a complex analysis with a large number of buffer components in System Reliability, the simulation did not complete. | DE105903 |
Previously, in the Definition workspace of a System Reliability Analysis, if the Time Analysis Type field was set to Monthly, when you accessed the Simulation Results workspace of that analysis, the Trend Plot displayed the data in years (for example, YYYY) instead of months (for example, MM). | DE105521 |
Previously, when you created an RCA for a Production Event from the Production Loss Analysis (PLA) module, in the Analysis Summary workspace, in the Linked Assets section, the Causing Asset associated with the Production Event did not appear in the Record ID column. | DE103249 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
To improve usability, the risk assessment window has been modified as follows:
| US345815 |
You can now restrict modifying an RCM Analysis and its child record to team members only. To facilitate this enhancement, the RCM FMEA Preferences tab has been added to the RCM FMEA Admin page. | US340645 |
You can now modify the Recommendation at all the levels in the analysis hierarchy. | US313842 |
In the RCM Overview page, the Create New Analysis and Create New Template buttons have been renamed New Analysis and New Template, respectively. | US306105 |
To enhance performance and scalability, the apply template operation has been converted to a job. | US293368 |
Description | Tracking ID |
---|---|
Previously, if your culture setting had a culture other than English, the values in the System Criticality Basis column of the RCM Analysis Description report were not translated to the language based on your culture setting. This issue has been resolved. | US301689 |
Previously, in the RCM Recommendation report, the Interval and Resource columns were not translated. This issue has been resolved. Now, the values selected for Interval Units will always be translated. The values of Recommended Resource will be translated only if they are selected from the drop-down list box. If you enter a value that is not in the drop-down list box of Recommended Resource, it will not be translated. | US301684 |
Previously, when you attempted to promote a Recommendation that was created using the Reliability Centered Maintenance (RCM) data loader, an error occurred. This issue has been resolved. | DE116212 |
Previously, you could not consolidate the Recommendations that were created using the Reliability Centered Maintenance (RCM) data loader. This issue has been resolved. | DE116023 |
Previously, the Driving Risk Category for Mitigated Risk Assessments was determined by the Unmitigated Risk Assessment. This issue has been resolved. | DE115096 |
Previously, when you selected an asset in the RCM failure mode, the Related Asset Type field was not populated with the correct Taxonomy Type of the equipment or functional location. This issue has been resolved. | DE109409 |
Previously, when you attempted to access an asset from the Linked Assets section of an analysis, an error occurred. This issue has been resolved. | DE109220 |
Previously, the count of Recommended Actions that appeared in the Recommended Actions pane was incorrect. This issue has been resolved. | DE108791 |
Previously, in the RCM Overview page, if you selected the Help button when you attempted to create a template, the Help documentation did not appear. This issue has been resolved. Now, the Help button does not appear when you attempt to create a template. | DE108018 |
Previously, you encountered database errors when using RCM data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders. | DE105997 |
Previously, the Apply Template Builder window took a long time to load when the template was complex. This issue has been resolved. Now, when creating an analysis from a template, the Apply Template Builder window loads more quickly. | DE105577 |
Previously, you could delete Recommendations that were not at the Failure Effect level. This issue has been resolved. Now, you can delete only the Recommendations that are at the Failure Effect level. | DE104267 |
Previously, regardless of your culture settings, the values in the State column were displayed in English. This issue has been resolved. Now, the values in the State column are displayed in the language that is based on your culture settings. | DE99458 |
Previously, when you created an analysis from a template, the template builder did not retain the selected assets. This issue has been resolved. | DE88189 |
Previously, in the Recommended Actions pane, you could select the Linked Recommended Actions tab before saving a new recommended action. This issue has been resolved. | DE85488 |
Previously, if you searched for an RCM template record in the hierarchy, an error occurred. This issue has been resolved. Now, you can search for a child node of the selected parent record from the hierarchy. | DE79677 |
Report Configuration
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
GE Digital APM now supports Microsoft Visual Studio 2017. | US260698 |
Description | Tracking ID |
---|---|
GE Digital APM no longer supports Microsoft Visual Studio 2013 and Microsoft Visual Studio 2015. | US260698 |
Results Grid
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The user interface of the Results Grid feature has been enhanced with a new look and feel. Additionally, the performance of the Results Grid feature has been improved. Note: The images for the following modules in the GE Digital help system have been updated. Images for the remaining modules will be updated in a future release.
| F44103 |
Description | Tracking ID |
---|---|
With the Web accessibility feature enabled in Chrome, performance degradation is observed in filtering and sorting of Data grids which have configured multiple selection of rows. By default the Web accessibility flag is off, in case you see degradation, you can check the status of the flag and disable it. To disable the flag and check the status, enter chrome://accessibility/ in your chrome browser and clear the option Web accessibility. | DE118458 |
Risk Based Inspection (RBI)
This topic provides a list of product changes released for this module on the dates listed below.
RBI 580 and RBI 581
Version: 4.3.1.0.0
Description | Tracking ID | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Security Users who were members of the MI RBI Analyst Security Group are now automatically assigned the MI Inspection Plan Approver Role. | US360378 | ||||||||||
To enhance usability when superseding RBI Recommendations, the Completion Comments box has now been added to the RBI Recommendation datasheet. | US358589 | ||||||||||
You can now re-promote an asset from Risk Based Inspection (RBI) to Asset Strategy Manager (ASM) when the asset has been previously promoted to ASM and the resulting actions have been consolidated on the Asset Strategy. To facilitate this enhancement, any consolidated actions on the Asset Strategy will now be unlinked during the promotion of an asset. | US353336 | ||||||||||
To enhance usability and readability, the Process Unit navigation in the RBI 581 Inventory Groups workspace has been updated to display the Functional Location Entity ID instead of the Functional Location ID. | US348279 | ||||||||||
To enhance performance, the queries used in the Risk Based Inspection Overview page, which referenced MI_ENTITIES directly, now reference the Equipment family. To facilitate this enhancement, the following queries have been updated:
| US343930 | ||||||||||
You can now implement RBI recommendations that belong to an Inspection Plan in:
| US335134 |
Description | Tracking ID |
---|---|
Previously, for a Criticality RBI Component - Exchanger Bundle, when you copied an RBI Criticality Analysis or created a What-If Analysis from an RBI Criticality Analysis, and then calculated the analysis, the Final Phase and Final Phase Shell Side fields in the related Criticality Consequence Evaluation record were not populated. This issue has been resolved. | DE117340 |
Previously, the value in the Desired Interval field in an Inspection Task was recalculated when the related RBI Recommendation was either deleted or transitioned to the Archived state. This issue has been resolved. | DE117062 |
Previously, when you applied a Criticality RBI Component – Cylindrical Shell component that contained the value Storage Tank in the Component Type field, an error message appeared. This issue has been resolved. | DE109897 |
Previously, when calculating inventory for the Criticality RBI Component – Cylindrical Shell component that contained the value Storage Tank in the Component Type field, an error occurred. This issue has been resolved. Now, the Calculated Inventory field is populated with the correct inventory value. | DE100794 |
Previously, when you attempted to finalize risk of multiple analyses that belonged to multiple Assets or Corrosion Loops, the operation failed completely when there were multiple analyses that belonged to a single component. This issue has been resolved. Now, in this scenario, the analyses that belong to different components are updated to Risk Completed and an error message appears to indicate the number of failed analyses. | DE95713 |
Previously, you could unexpectedly modify unmitigated risk values on Failure Risks with a source of RBI in Asset Strategy Manager (ASM). This issue has been resolved. | DE83069 |
RBI 580
Version: 4.3.1.0.0
Description | Tracking ID | ||||||||
---|---|---|---|---|---|---|---|---|---|
To enhance usability of the Risk Based Inspection (RBI) 580 Data Loader, the following values are now updated in the Interface Log record generated by the data loader:
| US366675 | ||||||||
To enhance usability, in the RBI Recommendation, the value in the RBI Recommendation Methodology field has been changed from Criticality Calculator to RBI 580. | US353694 | ||||||||
To enhance usability when using a UOM conversion set, the values within numeric fields are rounded off according to the type of the numeric field as follows:
| US352458 | ||||||||
The properties of the following representative fluids that are valid for RBI Criticality Analysis have been updated as per the API 581, 3rd Edition, Addendum 1 specification:
| US349921 |
Description | Tracking ID | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Previously, if the Override Minimum Required Thickness check box was selected for an RBI Criticality Analysis, the value specified in the Specified Tmin box was not considered while calculating the Estimated Half-Life for the Criticality Calculator External Corrosion Degradation Mechanism Evaluation. This issue has been resolved. | DE117296 | ||||||||||||||||||||
Previously, in the Risk Based Inspection (RBI) 580 Data Loader template, in the Consequence_Evaluation worksheet, the Consequence field contained the default value RBI. Due to this, an error occurred when importing data using the data loader. Now, the default value in the Consequence field has been changed to RBI Consequence. Note: The error message that appears when importing data using the Risk Based Inspection (RBI) 580 Data Loader that contains an invalid value in the Consequence field has now been updated to include the invalid value and the associated Analysis ID. | DE111087 | ||||||||||||||||||||
Previously, in Criticality Calculator RBI Components, the value in the Calculated Inventory field was rounded off to the nearest whole number. Due to this behavior, if the value in the Calculated Inventory field was less than or equal to 0.5, the value was rounded off to 0, which resulted in incorrect calculations. This issue has been resolved. Now, the calculated inventory field displays up to two decimal values. A similar change has been made to the Inventory field in the Criticality Consequence Evaluation and Criticality Calculator RBI Components. | DE107865 | ||||||||||||||||||||
Previously, in the Criticality Consequence Evaluation datasheet, two required fields for Heat Exchanger Bundles, Flammable Leak Type and Toxic Leak Type, did not contain the Not Applicable (N/A) option in their respective drop-down list boxes. This issue has been resolved. Additionally, the following validation changes have been made:
| DE107646 | ||||||||||||||||||||
Previously, the Material Grade boxes in the records of the following families contained incorrect values:
This issue has been resolved. Now, the correct values appear in the Material Grade boxes, as specified in the following table.
| DE96435 | ||||||||||||||||||||
Previously, in an RBI Criticality Analysis for a Heat Exchanger Bundle component, the values in the following drop-down list boxes were not translated:
| DE94111 | ||||||||||||||||||||
Previously, when creating a What-If Analysis, the Long Term Avg. Corr. Rate, Short Term Avg. Corr. Rate, and Controlling Corrosion Rate fields in the Criticality Calculator Internal Corrosion Degradation Mechanism were not populated with the calculated values from the Thickness Monitoring module. This issue has been resolved. | DE86408 |
RBI 581
Version: 4.3.1.0.0
Description | Tracking ID | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
To enhance usability of the Risk Based Inspection (RBI) 581 Data Loader, the following values are now updated in the Interface Log record generated by the data loader:
| US366675 | ||||||||||
The formula for calculating the Expected Metal Loss Fraction (Art) for components with or without cladding or weld overlay now adheres to API 581 3rd Edition, Addendum 1. | US356898 | ||||||||||
To enhance usability, in the RBI Recommendation, the value in the RBI Recommendation Methodology field has been changed from RBI 581 Recommendation to RBI 581. | US353694 | ||||||||||
To enhance usability when using a UOM conversion set, the values within numeric fields are rounded off according to the type of the numeric field as follows:
| US352458 | ||||||||||
The properties of the following representative fluids that are valid for RBI 581 Risk Analysis have been updated as per the API 581 3rd Edition, Addendum 1 specification:
| US349921 | ||||||||||
You can now generate recommendations irrespective of the value in the Inspection Will Mitigate field. To facilitate this enhancement, the Inspection Will Mitigate check has been removed from the following module workflow policies:
| US343660 |
Description | Tracking ID | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Previously, in an RBI 581 Analysis, when the Representative Fluid field was changed to a fluid with ambient state other than Liquid or Gas, the Release Fluid Phase field was not cleared. This issue has been resolved. | DE112859 | ||||||||||||||||||||
Previously, in the Risk Based Inspection (RBI) 581 Data Loader template, in the RBI_581_Consequence worksheet, the Consequence field contained the default value RBI. Due to this, an error occurred when importing data using the data loader. Now, the default value in the Consequence field has been changed to RBI Consequence. Note: The error message that appears when importing data using the Risk Based Inspection (RBI) 581 Data Loader that contains an invalid value in the Consequence field has now been updated to include the invalid value and the associated Analysis ID. | DE111087 | ||||||||||||||||||||
Previously, irrespective of the Unit of Measure (UOM) Conversion Set configured for your user account, the Consequence of Failure and Risk Values on the RBI 581 ISO-Risk Plot appeared in imperial units. This issue has been resolved. | DE110866 | ||||||||||||||||||||
Previously, you could not create a Quantitative (581) analysis if the logged-in user culture was set to Russian. This issue has been resolved. | DE107414 | ||||||||||||||||||||
Previously, in an RBI 581 Risk Analysis, if you selected a fluid in the Representative Fluid box that did not have a value in any of the following tables, the analysis calculation failed:
This issue has been resolved. Now, in this scenario, the analysis calculation proceeds considering the constant values as 0. | DE103262 | ||||||||||||||||||||
Previously, the Material Grade boxes in the records of the following families contained incorrect values:
This issue has been resolved. Now, the correct values appear in the Material Grade boxes, as specified in the following table.
| DE96435 | ||||||||||||||||||||
Previously, if the Insulated check box was selected, you could not generate RBI Recommendations for the RBI 581 Risk Analyses with the following degradation mechanisms:
| DE82239 | ||||||||||||||||||||
Previously, in an RBI 581 Risk Analysis, if you selected a Toxic fluid in the Representative Fluid field, the application did not calculate the Weighted Component Damage Consequence and Weighted Personnel Injury Consequence even if the fluid had a value in the following tables:
| US337384 |
Risk Matrix
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
In the default risk matrix, the colors associated with risk thresholds have been modified to improve contrast. | US335434 |
Description | Tracking ID |
---|---|
Previously, in the financial risk control, you could not calculate the financial consequence if the following fields did not contain a value:
This issue has been resolved. Now, you can calculate the financial consequence if any one of the fields contain a value. | US333940 |
Root Cause Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
To improve usability, the RCA Logic Tree design has been modified. This enhancement provides greater design canvas space, improves visibility of the node content, and enables Teams to define and list the node items before adding them into the Logic Tree. | US361852 |
Description | Tracking ID |
---|---|
Previously, if you had created a customized message using a custom rule, when you attempted to publish an RCA that was refrained from being published, the Internal Server Error message appeared, instead of the customized message. This issue has been resolved. | DE116153 |
Previously, when you attempted to link an asset to an analysis, you could not find a list of Production Events associated with the asset in the Linked Events section. This issue has been resolved. Now, you can find a list of events associated with the asset and link them to the analysis. | DE115273 |
Previously, after linking grouped elements in the RCA Event diagram, the connections were lost when you exited the page. This issue has been resolved. | DE114790 |
Previously, when exporting the RCA Event Diagram to the SSRS Comprehensive Analysis Report, the resolution of large diagrams was poor when you zoomed in on them. This issue has been resolved. | DE113894 |
Previously, if APM Now sent an alert message for an RCA Preserve Item Record, and if you attempted to access the URL in the alert message, an error occurred because the URL contained the domain name of the Virtual Machine (VM) instead of the domain name of the load balancer. This issue has been resolved. | DE113040 |
Previously, if the user account of a Security User who was a member of the RCA team was inactive, the remaining members of the RCA team could not create a recommendation. This issue has been resolved. | DE110615 |
Previously, in the My Analysis section, if you published an analysis that was in the In Progress state, an error occurred. This issue has been resolved. | DE105523 |
Previously, when viewing an RCA Template, the State Assignment drop-down list box appeared erroneously. This issue has been resolved. | DE104893 |
Previously, when you created an RCA for a Production Event from the Production Loss Analysis (PLA) module, in the Analysis Summary workspace, in the Linked Assets section, the Causing Asset associated with the Production Event did not appear in the Record ID column. This issue has been resolved. | DE103249 |
Rounds Data Collection
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
In the Recommendations section of the RDC Overview page, you can now view only the Recommendation records that contain your user name in one of the following fields:
| US343516 |
Description | Tracking ID |
---|---|
Previously, when you used the GE Digital APM mobile application to collect data, you could view a list of Routes that were not assigned to you. This issue has been resolved. | DE112478 |
Previously, while using the GE Digital APM mobile application to collect data, you could not scan bar codes longer than 11 characters. This issue has been resolved. Now, you can scan bar codes with a length of up to 20 characters. | DE110128 |
Previously, if you created an Operator Rounds Recommendation record without the Create Work Request? check box selected, and then selected that check box later when updating the recommendation, the work request was entered into your SAP system, but the recommendation was not updated with the data of the work request. | DE108362 |
Previously, when attempting to create an Operator Rounds Recommendation, if you selected the Create EAM Work Request? check box prior to saving the recommendation, an error occurred, and the recommendation record would not be created. This issue has been resolved. | DE105520 |
Previously, when you accessed a Lubrication Requirement checkpoint for a Route using devices with smaller screens or lower screen resolution, the data in the Lubrication Requirement Summary section was truncated. This issue has been resolved. | DE100891 |
Previously, while disconnected from a network, if you created a recommendation for a Route, the time stamp of the recommendation displayed the time at which your device reconnected to a network, not the time at which the recommendation was created. | DE98858 |
Rounds Designer
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
A Route Revision check has been added to prevent concurrent updates to a Route by two different users. | US354168 |
To create Checkpoint conditions for a character Measurement Location, a new relational operator, is not, has been added to the Select Relation drop-down list box that appears in the workspace for the Measurement Location. | US254766 |
Description | Tracking ID |
---|---|
Previously, when you used the Rounds Routes Data Loader to import Routes that contained Checkpoint Tasks, the schedules were not populated correctly. This issue has been resolved. Note: To fix this issue for Routes that were imported in a previous version, reimport the Routes with complete data in the MI_CP_TASK0 worksheet. | DE112728 |
Previously, in the Rounds Designer Overview page, in the Routes section, when you attempted to access a Route by selecting the Route ID link, an error occurred, and you could not access the Route datasheet. This issue has been resolved. | DE111834 |
Previously, if a Measurement Location Template Group contained Measurement Location Templates assigned to different sites, an error occurred when you attempted to modify the values in the following fields of a template in the template group:
| DE110379 |
Previously, if you created a Route using the Rounds Route Data Loader, the Route sequence did not load as expected. | DE108351 |
Previously, in the condition of a Checkpoint template, you could not enter a value in the Allowable Values or Select Value fields unless allowable values were defined. | DE108709 |
Previously, if you attempted to use a data loader to add a Checkpoint to a Route, the sequence of existing Checkpoints on the Route was unintentionally modified. | DE106752 |
Previously, loading a small number of records using the Rounds Routes Data Loader occasionally resulted in time-out errors. | DE106749 |
Previously, if you attempted to move a Checkpoint node by dragging and dropping it into a header, an error occurred. | DE106403 |
Previously, running the Aging Query - Oracle and Aging Query - SQL Server queries, stored in the \\Public\Meridium\Modules\Operator Rounds\Queries and \\Baseline\Meridium\Modules\Operator Rounds\Queries folders, returned an error. This issue has been resolved. Now, these queries return a list of Measurement Locations that are overdue. | DE102602 |
Previously, when you modified a Checkpoint, a different Checkpoint was selected than the Checkpoint you modified. This issue has been resolved. | DE85258 |
Previously, if you moved a Checkpoint condition to a new Checkpoint, or if you modified and saved the condition or the successor Checkpoint of the condition, the predecessor Checkpoint of the condition was selected afterwards, as opposed to the condition itself. This issue has been resolved. | DE82246 |
Previously, Rounds Designer repeatedly switched between Checkpoints if you:
| DE78766 |
Previously, while adding a reading for a Checkpoint with the character ML type and the allowable values defined, the Reading Value Character box appeared as a text box instead of a drop-down list box until the reading was created. When you attempted to modify the reading later, the Reading Value Character drop-down list box appeared with appropriate values. This issue has been resolved. | DE74228 |
R Scripts
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Microsoft Machine Learning Server 9.3.0 is now supported for R Script execution. | US326009 |
Description | Tracking ID |
---|---|
Previously, in the Parameters pane of a new parameter, when you selected a value in the Type column and saved the R Script, the value was not saved. This issue has been resolved. | DE97066 |
Rules
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now compile only the family rules that you added or modified, instead of compiling all the family rules in a rules library project. To facilitate this enhancement, the data source ID is now used instead of GUID. This enhancement also resolves possible errors when compiling rules with references to other rule projects. Note: You must compile all the family rules only if you modify the data source ID. | US352396 |
Schedule Logs
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
You can now delete the historical Schedule Logs entries. | US337522 |
Description | Tracking ID |
---|---|
Previously, a policy was not executed as per schedule until you updated the policy, if the following changes had been made to the GE Digital APM database that contained the policy:
| DE102150 |
Scripts
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
The Cognitive Analytics and Scripts modules are no longer available in GE Digital APM. Note: The catalog items and families used by the two modules have not been removed from GE Digital APM. | F44508 |
Search
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you performed an advanced search by defining a numeric field condition where the numeric field had a UOM associated with it, the records returned by the search did not contain a UOM. This issue has been resolved. | DE98915 |
Security Manager
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, you could access a Map query in the Maps tool only if you had one of the following privileges:
This issue has been resolved. Now, all the GE Digital APM users can access the Map queries in the Maps tool. | DE115905 |
Description | Tracking ID |
---|---|
You will no longer receive a password change prompt 30 days before the password expiry date. After the password expires, you must change the password in the Active Directory and run the LDAP sync. After the sync is successful, you will be able to log in with the new credentials. | US367105 |
SIS Management
This topic provides a list of product changes released for this module on the dates listed below.
Version: V4.3.1.0.0
Description | Tracking ID |
---|---|
The SIS Proof Test feature now supports integration with Work Management. You can perform Proof Tests for Proof Test Tasks created from SAP or Asset Strategy Management (ASM). In addition, a confirmation record will now be created when SIS Proof Tests are closed. | US352931 |
System Codes and Tables
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, in the System Codes and Tables page, after you modified the properties of an existing table and saved the table, if you selected the Search button () in the System Tables section, an error message appeared. This issue has been resolved. | DE104335 |
System Requirements
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
APM Mobile is now compatible with Zebra TC-75X touch computer and utilizes both the integrated barcode scanning and the NFC RFID tag scanning. | US351912 |
Thickness Monitoring
This topic provides a list of product changes released for this module on the dates listed below.
Version: 4.3.1.0.0
Description | Tracking ID | ||||||
---|---|---|---|---|---|---|---|
You can now view, add, and delete the Thickness Measurements related to a Thickness Measurement Location in the table in the TMLs section. | US371494 | ||||||
To enhance usability when using a UOM conversion set, the values in the numeric fields are rounded off according to the type of the numeric field as described in the following table.
| US358876 | ||||||
When you calculate thickness measurement for an asset, you can now close the window that displays the progress of calculation. This enables you to perform other operations while the calculation is in progress. After you close the window, the calculation continues in the back end and you can view the calculation details from the scheduler window. | US348278 | ||||||
You can now save the TML measurements and calculate the corrosion analysis for an asset from the Measurement Data Entry workspace. To facilitate this enhancement, a new option, Save and Analyze () has been added to the Measurement Data Entry workspace. | US346563 | ||||||
For Thickness Measurement Locations, you can now modify the sequence of the default columns except the TML ID column using Column Chooser. The configuration is saved as a user preference in the database. | US343673 | ||||||
To enhance the performance of the Thickness Monitoring Analysis Overview workspace, duplicate network calls have been removed. | DE115278 |
Description | Tracking ID | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Previously, in the following scenarios, only the first 100 TML records were displayed, instead of all the related TML records:
| DE114781 | ||||||||||||||||||||
Previously, after collecting data using the DMS Go+ device, if you pressed the Send button for more than two seconds, the device also stored an A-Scan reading. In addition, the GE Digital APM Thickness Monitoring Datalogger could not process the file containing an A-Scan or display the readings. These issues have been resolved. Note: GE Digital APM Thickness Monitoring does not store the A-Scan data stored on the device. You must upgrade the Meridium Device Service application to the latest version. | DE113273 | ||||||||||||||||||||
Previously, in the Analysis Overview workspace, when you selected the Manage RBI Components option, you could not access the active RBI Components to map to Thickness Measurement Location (TML) Groups. This issue has been resolved. | DE112036 | ||||||||||||||||||||
Previously, if your culture was set to Russian, and if you accessed a TML for an asset in the Analysis Overview page, the Calculated Date field in the Analysis Output section was incorrectly translated. This issue has been resolved. | DE109440 | ||||||||||||||||||||
Previously, in the Measurement Data Entry workspace, if you specified values in the Measurement Taken Date and Measurement Taken By boxes, when you navigated away from the workspace, and then accessed the Measurement Data Entry workspace, the specified values were not retained. This issue has been resolved. | DE108534 | ||||||||||||||||||||
Previously, in the Thickness Monitoring Dataloggers page, users had to select all the records individually in multiple pages of the TMLs table to select all the records on all pages before transferring data between GE Digital APM and the datalogger. This issue has been resolved. Now, if you select the Select All check box, all the records on all pages of the TMLs table are selected. | DE107158 | ||||||||||||||||||||
Previously, if you used the TM Equipment or TM Functional Location data loaders to load data that consisted only of measurements, the Analysis Required check box in the TML Corrosion Analysis datasheet was not selected, and the Calculate button () did not turn orange. If you tried to calculate the analysis, the newly loaded measurements were not included in the calculation. This issue has been resolved. Now, when you load measurements, the Analysis Required check box is selected, and the Calculate button () turns orange, indicating the analysis is ready to be calculated. When you calculate the analysis, the newly loaded measurements are included in the calculation. Also, the affected assets are available in the Assets Requiring a Calculation section of the Thickness Monitoring Overview page, ready for bulk calculation. | DE105931 | ||||||||||||||||||||
Previously, the Material Grade boxes in the records of the following families contained incorrect values:
This issue has been resolved. Now, the correct values appear in the Material Grade boxes, as specified in the following table.
| DE96435 | ||||||||||||||||||||
Previously, when you modified the value in the Status Indicator box of a previously inactive Thickness Measurement Location (TML) record to Active, and then saved the record, the Calculate icon () in the Analysis Overview workspace did not retain the orange highlight after the page was refreshed. This issue has been resolved. Now, in this scenario, the icon remains highlighted in the orange color even after the page is refreshed. Note: Before you modify the status of a previously inactive TML to Active, we recommend that you calculate the TML so that the Analysis Required field of the TML Corrosion Analysis resets properly prior to the reactivation of the TML. | DE96015 | ||||||||||||||||||||
Previously, you could modify the site assigned to the Resource Role records because the Resource Role family was enabled for site filtering. When the site assigned to a Resource Role for a given user was modified, the name of that user did not appear in the drop-down list boxes in the respective datasheets. This issue has been resolved. Now, the Resource Role family is no longer enabled for site filtering and the user names appear correctly. Note: The fields containing the user names will continue to be filtered based on the site to which the respective record is assigned. | DE91540 | ||||||||||||||||||||
Previously, the TML Asset ID field was not available in the Choose Columns window, due to which you could not view the TML Asset ID column in the TML grid. This issue has been resolved. Now, TML Asset ID column is available in the TML grid by default. | DE87019 |
Units of Measure and Conversions
Version: 4.3.1.0.0
Description | Tracking ID |
---|---|
Previously, when you converted the original UOM value to a new UOM value, the calculation was based on the last value instead of the original value. This issue has been resolved. Now, when you convert a UOM using the Unit of Measure Converter window, the calculation is based on the original value. | DE96069 |
Version: 4.3.0.7.6
Description | Tracking ID |
---|---|
Previously, in the UoM field, when you searched for a converted value, the search was applied on the original UoM data instead of the converted value in a query result. In addition, the issue data was not filtered correctly. This issue has been resolved. Now, the search on the UoM field works according to the User conversion set. | DE113353 |