APM Release Notes for the First Quarter of 2019
Action Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance usability, in the Recommended Actions section, the email address value entered in the From field in the Email Settings page is now used when you configure a Recommended Action to send an alert. | US296242 |
| To maintain consistency, in the Recommendations pane, State Management is now controlled by the same functionality as other GE Digital APM modules. | US283474 |
| Description | Tracking ID |
|---|---|
| Previously, when you accessed Predix APM, if you attempted to navigate to Action Management, the Enter Parameter Values window appeared. This issue has been resolved. | DE98575 |
| Previously, if your culture setting had a culture other than English, and you accessed the Recommendation Filters window, the States were not translated to the language based on your culture setting. This issue has been resolved. | DE96432 |
| Previously, if your database contained a large number of actions, and you navigated to the Strategy Actions workspace, the process sometimes timed out. This issue has been resolved. | DE93594 |
Previously, in the Recommended Actions tab, if you selected the Filter button ( ), the list of possible options was not properly localized. This issue has been resolved. | DE93359 |
| Previously, in the Recommended Actions pane, the state of Recommended Actions was not properly localized. This issue has been resolved. | DE89662 |
Alerts
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can now perform maintenance of SmartSignal analytics from alerts and change the status of the alerts to In Process Maintenance to indicate the analytics maintenance activity. | F42107 |
| Alert escalation and de-escalation have been introduced on latched alerts. They help you prioritize the alert for processing. | F27584 |
| You can now group columns in an alerts grid to organize data for easy access. | F18466 |
| Description | Tracking ID |
|---|---|
| Previously, in an alert email notification that you received, the link to access the alert details in the GE Digital APM application did not work. This issue has been resolved. | DE98905 |
| Previously, if an asset contained an associated alert and the name of the asset was changed, the alert still contained the old name of the asset instead of the new name. This issue has been resolved. | DE98778 |
| Previously, in an alerts grid, when you sorted the Density column in descending order, all the records did not appear. This issue has been resolved. | DE94960 |
| Previously, when you released a claimed alert, the alert did not appear in the list of unclaimed alerts. This issue has been resolved. | DE94631 |
| Previously, in the Create an Alert window, even though an inactive alert template was selected, the Create Alert button was available for selection. This issue has been resolved. | DE94173 |
| Previously, if you modified the Alert Received Time or Event Time values of a filter, and applied the changes, the changes were not saved. This issue has been resolved. | DE91869 |
| Previously, when you accessed an alert that contained recommendations and work order data, the Recommendations and Work History sections failed to load, and an error message appeared in these sections. This issue has been resolved. Note: This issue is not applicable to legacy Predix APM.
| DE87602 |
| Description | Tracking ID |
|---|---|
| You cannot sort grouped columns in an alerts grid. | NA |
Release Date: February 08, 2019
| Description | Tracking ID |
|---|---|
| The charts in the Analysis and Evidence sections of an alert now appear as images in the generated PDF report. |
|
| Description | Tracking ID |
|---|---|
| Only a PDF file of size up to 5 MB will be generated for an alert. | DE101558 |
| A generated PDF report for an alert can contain up to eight charts of an analysis or evidence. | DE101488 |
| If an analysis or evidence of an alert contains multiple cards, only the charts of the first card appear in the generated PDF report. | DE100856 |
| Export of alert details to a PDF file may take up to five minutes. | NA |
Release Date: January 23, 2019
| Description | Tracking ID |
|---|---|
| Previously, if you had selected an asset name from the Asset Hierarchy and then applied the Asset Id or Asset Site Name filter criteria, alerts were not displayed in the Alert Inbox or Grid view. This issue has been resolved. | DE98602 |
| Previously, when you attempted to delete two evidences of an alert consecutively, an error occurred. This issue has been resolved. | DE98276 |
| Previously, for an alert that belonged to another tenant, when you selected the Asset ID or name of the asset to access the Asset Instance page, an error occurred. This issue has been resolved. | DE97583 |
| Previously, if you had selected an asset name from the Asset Hierarchy, the asset name did not appear in the Alert Inbox or Grid view. This issue has been resolved. | DE96218 |
| Previously, the internal link did not appear in the Alert Details page of the subscriber tenant even though the template that was used to create the alert had an internal link. This issue has been resolved. | DE95378 |
| Previously, if you had accessed a linked alert from a case, you could not mark the alert as processed and release the claim for the alert. This issue has been resolved. | DE91357 |
Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can enable the Y-axis ranges for SmartSignal, allowing you to view a tag's Y Min and Y Max values. | F42602 |
| You can enable point mode for SmartSignal cards, allowing the X-axis to display the number of data points selected instead of a date-time range. | F42537 |
| Analysis views from an alert now include both contributing and non-contributing tags displayed on the charts. | F41386 |
| You can filter the tag data on a SmartSignal chart by threshold. | F41139 |
| You can view the analytic tags that are On Monitor. | F40892 |
| You can select a system of measure for analysis cards. | F40891 |
| You can resize the tag panel, allowing you to view the full tag names shown in the expanded form of the tag browser. | F40890 |
| You can plot up to 40 SmartSignal tags singly or in groups. | F40889 |
| F39094 |
| You can add one or more reference lines to a SmartSignal chart. | F33718 |
| You can display one or more Alerts for an asset or group of assets along with the contributing and non-contributing tags associated with the generated Alerts from the Tag Browser. The listed alerts for an asset display the alert's severity and color categorization. | F33508; F41116 |
| Description | Tracking ID |
|---|---|
| When you have multiple Y-axes enabled on a time series chart, Y zoom and XY Zoom provide an inconsistent user experience because all the axes do not scale correctly to reflect the zoomed-in state. | DE104375 |
| If you click on a diagnostic marker on a SmartSignal chart, the hover information on the markers does not appear. In order to get out of the mode, you can refresh the charts and the hover information reappears. | DE101633 |
| If you enable the cross-hair mode in an analysis and then added new charts to the template, the cross-hair information is not reflected on the new charts, and the cross-hair markers are no longer visible on the existing charts. To prevent this, disable cross-hair mode, add the charts, and then enable cross-hair mode again. | DE99126 |
| When you delete tags on a time series chart after you have plotted pin markers, the deleted tags appear in the marker data table. The workaround for this is to delete the tags, and then set the pins on the charts. | DE95436 |
| When making changes to the time series chart in multiple Y-axes mode, select Cancel, not Apply. If you select Apply, the changes are not applied nor are they visible in chart settings. The workaround for this is to select Cancel and to create the template for an ad-hoc view. Or, save the template, and then make your changes for an existing template. | DE93811 |
| Description | Tracking ID |
|---|---|
| You must use Google Chrome to add multiple charts to a SmartSignal card. Other browsers, including Internet Explorer, are not supported when adding multiple charts to a single SmartSignal card. | N/A |
Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance the usability in analytic template and deployments, you can now download a .zip file of logs containing all analytic deployments for the current version of the Analytic Template. | F42079 |
| To enhance the usability in analytic deployments, you can now configure your tenant to connect to an instance of PostgreSQL that has been previously configured on Spark runtime as one of the input data source. |
|
| To enhance the usability in analytic orchestrations, you can now schedule analytic orchestrations to run in a recurring mode for Spark runtime. | F42076 |
| To enhance the asset applicability during deployment, the asset applicability can now be derived from existing deployments and asset filters associated with each deployment. Newly commissioned assets that fit the filter criterion are automatically available for selection during deployment. | F42074 |
| To enhance the I/O Mapping step during deployment, you can now configure the Entity Type for inputs, outputs, and constants in the analytics template. During the I/O mapping step in deployment, the Entity Type tells Application Analytics to retrieve the tags and attributes of all assets and their children starting at the defined level. Note: This is not available for all runtimes. | F42072 |
| To enhance the usability in the analytic template creation, you can now associate a Machine Learning (ML)/Artificial Intelligence (AI) model to an analytic or blue print. This is only available for the PowerDataFabric runtime. | F42071 |
| To enhance the Scheduling step during deployment, you can now trigger an analytic to run when a specific alert event happens. Note: This is not available for all runtimes. | F18922 |
| Description | Tracking ID |
|---|---|
| Previously, when a deployment used more than 1000 assets but did not have all outputs explicitly mapped, then the error ConcurrentModificationException occurred and the deployment failed. This issue has been resolved. | DE97332 |
| Previously, on dedicated tenants, administrators could not access the audit logs for Analytics using the Audit Log Management. This issue has been resolved. | DE94501 |
| Previously, sometimes, even though there were no current deployments associated with the version of the analytic templates you were trying to delete, an error occurred asking you to first delete any associated deployments before you can delete the version of the analytic artifact in the template. This issue has been resolved. You can now delete analytic templates which have no current deployments. | DE77551 |
| Previously, when you modified an Analytic Template configuration after it had already been used in a deployment, the deployment status in the Deployments page was expected to display Updates Not Deployed. Sometimes, the status did not automatically refresh. This issue has been resolved. | DE63501 |
| Description | Tracking ID |
|---|---|
| If a deployment uses more than 250 assets that generate alerts at frequent intervals of less than one hour, you may not be able to access these alerts. There are some known limitations when using a combination of high-volume and high-frequency alerts generated by analytics. If you have a need to deploy analytics that are expected to produce alerts at high frequencies and for large volume of assets (over 250), please contact the Analytics Support Team prior to deploying such analytics. This limitation is limited to the Predix runtime environment. A future enhancement for rendering high-frequency, high-volume analytics alerts is scheduled for a future release. At that time, all existing deployments must be re-deployed to benefit from the enhancement. | DE105943 |
Limitations
- Application Analytics does not support cross-tenancy; therefore, you will not be able to access assets from a different tenant.
APM Connect
This topic provides a list of product changes released for this module on the dates listed below.
Important: To prevent processing failures, you must upgrade your on-premises, client-side jobs within two months of a GE Digital APM release to the most current version of the APM Connect client jobs. The current versions of the jobs are UDLP 2.5.0 or V2.5.1 and V2.6.0. For additional information, see UDLP Versions.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| The Automatic Data Loader now provides a way to change the processing order of the directories. | US312179 |
| Description | Tracking ID |
|---|---|
| Previously, EAM or data loader jobs would occasionally end without updating the status correctly. This issue has been resolved. |
|
APM Mobile Application
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| The GE Digital APM mobile application now supports iOS 12 devices. | US290963 |
| Description | Tracking ID |
|---|---|
| Previously, when you uninstalled the GE Digital APM mobile application from a Windows device, the uninstall script attempted to remove the application package from the WindowsApps folder. As a result of client or security restrictions, this sometimes caused the app package to be corrupted, and the uninstallation only partially succeeded. This issue has been resolved. | DE88027 |
| Previously, the GE Digital APM mobile application sometimes appeared as unavailable on a Windows device. This issue has been resolved. | DE88027 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To maintain consistency in the <Asset Name> page, Asset Criticality Analysis has been moved to the Strategy section. | US325270 |
To enhance usability in the Assessment workspace, the Assess button ( ) has been updated to  . | US318204 |
| To enhance usability when loading checklist records, the Asset Criticality Analysis (ACA Checklist) Data Loader has been added. | US316936 |
| To enhance usability, in the Assessment workspace, you can select multiple assets contained within a single analysis for assessment. | US316803 |
| To enhance usability, a new relationship family, Asset Criticality Analysis Has Assets, has been added. | US310611 |
| To enhance usability, in the Assessment workspace, an Add Asset button has been added. | US310611 |
| To enhance usability, a new column, Criticality, has been added to the Analyses section of the Asset Criticality Overview page. | US309200 |
| To enhance usability in the Assessment workspace, functionality to export an analysis has been added. | US302496 |
| From the ACA Overview page, you can now link assets to a new or existing ACA Analysis, Asset Strategy, FMEA Analysis, RBI Asset View, RCM Analysis, or System Strategy. To facilitate this enhancement, a Send To button has been added in the Assets section. |
|
| To enhance usability, the performance of the Asset Criticality Analysis (ACA) Data Loader has been improved. | US300817 |
| To enhance usability in the Analysis Details section, functionality to access Reference Documents has been added. | US300551 |
| To enhance usability in the Assessment workspace, you can now simultaneously assess multiple assets in an analysis. |
|
| To enhance usability, in the Assessment workspace, you can now add assets to and unlink assets from an analysis. | US300392 |
| To enhance usability in the Analysis Details page, the Assessment section now contains a table that displays all assets associated with the selected analysis. | US300152 |
| To enhance usability, in the Analysis Details page, in the Assessment section, the Asset Criticality Distribution chart has been added. | US300151 |
| To aid in efficiency, the State Configuration workflow that is defined for the ACA family has been simplified. | US300148 |
| To enhance usability, in the Asset Criticality Overview page, the Analyses section has been redesigned. | US300143 |
| To enhance usability, in the Asset Criticality Overview page, the new Assets section replaces the My Analyses section, which has been deprecated. | US299979 |
| To enhance usability, a new chart, Assets Assessed, has been added to the Overview page. The Assets Assessed chart displays a breakdown of the numbers of pieces of equipment that are ranked based on criticality. |
|
| To enhance usability in the Analysis Details page, the maximum Criticality value is now displayed in the page header. | US299694 |
| To enhance usability, AMS Asset integration has been added to populate the Assessment field in Criticality records. | US294959 |
| Description | Tracking ID |
|---|---|
| Previously, if you attempted to update the criticality indicator values in SAP to reflect the criticality value that you determined in GE Digital APM and the connection failed, the incorrect error message appeared. This issue has been resolved. | DE89715 |
| 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. | DE89669 |
| Description | Tracking ID |
|---|---|
| All administrative Asset Criticality Analysis functions, previously accessed via the Application Settings page, have been deprecated. | US300819 |
| AMS Asset integration is no longer supported by the Risk Assessment family, as it is now used by the Criticality family. | US294959 |
Asset Health Manager
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| In the AHM Admin page, in the Health Indicator Source Management workspace, the Include All Matching and Exclude All Matching buttons have been removed. These buttons have been replaced by the Resync Health Indicators button, which you can use to resync health indicators if the list of health indicator sources becomes out of sync with the actual list of available health indicators. |
|
| To enable more efficient navigation of health indicator sources, the Status and Do not automatically create health indicator columns have been removed from the Health Indicator Source Management workspace in the AHM Admin page. These two columns have been replaced by one new column, Included, which displays a check mark when a health indicator source is used to create health indicators and which appears empty when a source is not used to create health indicators. To facilitate this enhancement, a new field, Include as Health Indicator Source Field, has been added to the Health Indicator Mapping family. In addition, a new field, Include as Health Indicator Source, has replaced the Do Not Automatically Create Health Indicator field in the following families:
|
|
| Description | Tracking ID |
|---|---|
| If Home was selected in the Asset Hierarchy, when you attempted to access the Health Summary page, the page could take a long time to load, and, in some cases, the page failed to load. | DE100129 |
| Previously, if you loaded a large number of assets into a database, the Health Indicator Status by Asset graph loaded very slowly or, in some cases, timed out and did not load at all. This issue has been resolved. Now, the performance of the Health Indicator Status by Asset graph is significantly improved. | DE93292 |
Asset Hierarchy
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
In the Hierarchy section, for the following scenarios, a message appears at the bottom of the hierarchy, indicating that there are too many records available in the hierarchy, and you can use the search or filter option to find the required equipment or functional location.
| US322281 |
| Description | Tracking ID |
|---|---|
| Previously, while accessing the data for an asset in the <Asset Name> workspace, if you navigated away from the workspace and then attempted to access the data for the asset, an error occurred. This issue has been resolved. | DE92693 |
| Previously, if you specified filter criteria and selected an asset to view the data in the <Asset Name> workspace, when you navigated away from the workspace, and then attempted to access the data in the <Asset Name> workspace, the filter criteria that you specified was cleared. This issue has been resolved. | DE92877 |
Asset
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| When using the <attributeName> modifier while searching for a tag instance, results appear for both custom and reserved attributes. | F680 |
| Description | Tracking ID |
|---|---|
| IE 11 experiences a long-running script error when attempting to navigate to the details of an object in APM (Asset, Site, Segment, or Enterprise). | DE95900 |
| Associate/Disassociate actions are logged as Create/Delete in the Audit Logs. | DE44416 |
| Description | Tracking ID |
|---|---|
|
In Predix APM, adding or modifying assets using the Legacy Predix APM user interface, APIs, or Asset Ingestion Service, or bypassing the Unified Asset Ingestion Data Loader, causes the asset databases to become out-of-sync. In Predix APM:
In Legacy Predix APM:
| N/A |
| Description | Tracking ID |
|---|---|
| Previously, in the Select Context window, when you attempted to search for an asset, sometimes, the asset did not appear in the search results. This issue occurred because the search results displayed only the first 10 records in a sequence that matched the search string you specified, and the asset that you attempted to search did not match any of these records. Search results appear as expected. | DE102986 |
| Select and Cancel were not visible upon resize. The Context Browser resizes to show the options to 'Select' or 'Cancel' when a user resizes the browser window. | DE96140 |
| The GET call from /sites was returning all the attributes, including the deleted ones, because of the cache. This has been moved to the GEDA backlog. | DE94480 |
| When you passed anything other than the allowed parent entity CCOM Class, the task status failed. This has been moved to the GEDA backlog. | DE83773 |
| You were unable to ingest a tag with tagType as computed or sensor. Ingestion for a tagType as computed or sensor works as expected. | DE76027 |
| If a network was part of a sub-network, then it was not searchable. This feature is being deprecated in April 2019. | DE75564 |
| The Reserved Attributes Advanced search was not working when system had large volumes of reserved attributes. The Reserved Attributes Advanced search works as expected when the system has large volumes of reserved attributes. | DE75378 |
| You were intermittently unable to see ingestion logs in IE. Ingestion logs in IE are displayed as expected. | DE73709 |
| An internal server error displayed if the user sent a request with a Malformed URL. The correct error message now displays if the user sends a request with a Malformed URL. | DE68896 |
| A newly created alert (count) was not seen immediately without refreshing the page; the Date picker was not reflecting the current time. A newly created alert (count) is now reflected in the alert count. | DE61811 |
| The Timestamp was incorrect if the time zone in user preferences is set to UTC + 14(Kiritimati). The Timestamp now displays correctly in the asset faceplate. | DE57601 |
Release Date: January 17, 2019
| Description | Tracking ID |
|---|---|
| The asset hierarchy component (context browser) has been replaced for use with legacy Predix APM modules. | F38575 |
| You can now search for tag instances from an asset instance. | F680 |
| You can now add and delete groups for classifications using the user interface. | F443 |
| You can now remove members of a group using the user interface. | F443 |
| You can now select and add classifications to an existing group. | F443 |
| Description | Tracking ID |
|---|---|
| Select and Cancel are not visible upon resize of the browser page to a smaller size. | DE96140 |
| The GET call from /sites is returning all the attributes, including the deleted ones, because of the cache. | DE94480 |
| When you pass anything other than the allowed parent entity CCOM Class, the task status fails. | DE83773 |
| You are unable to ingest a tag with tagType as computed or sensor. | DE76027 |
| If a network is part of a sub-network, then it is not searchable. | DE75564 |
| The Reserved Attributes Advanced search is not working when system has large volumes of reserved attributes. | DE75378 |
| You are intermittently unable to see ingestion logs in IE (in the unified tenant). | DE73709 |
| Associate/Disassociate actions are logged as Create/Delete in the Audit Logs. | DE44416 |
| An internal server error displays if the user sends a request with a Malformed URL. | DE68896 |
| A newly created alert (count) is not seen immediately without refreshing the page; the Date picker is not reflecting the current time. | DE61811 |
| The Timestamp is incorrect if the time zone in the user preferences is set to UTC + 14(Kiritimati). | DE57601 |
| Description | Tracking ID |
|---|---|
| On the Tags tab of the asset details page, users cannot search for tags using reserved attributes. | N/A |
| Description | Tracking ID |
|---|---|
| The Asset page loads properly when Tags are from Site or Segment. | DE36446 |
Asset Strategy Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
To enhance usability, the Criticality Value button ( ) has been updated to  . | US318204 |
| A new query, Asset Strategy Action Revisions Query, has been added to the Catalog folder \\Public\Meridium\Modules\Asset Strategy Management\Management\Queries. The Asset Strategy Action Revisions Query is used by the ASM Implement Actions workspace to allow customizations of columns representing fields from the Action family. | US307521 |
| To enhance usability, in the ASM Overview page, you can now export one or more Asset Strategy Templates. | US294957 |
| To enhance usability, in the ASM Overview page, you can now export one or more Asset Strategies. | US291223 |
| To enhance usability, in the Implement Actions section, you can now apply updates to Actions that are implemented by EAM Plan or EAM Plan Details records. | US165018 |
| To enhance integration, in the ASM Overview page, you can now create Actions from an EAM Plan. | US164318 |
| To enhance integration, in the ASM Overview page, you can now link Actions to an EAM Plan. | US164312 |
| Description | Tracking ID |
|---|---|
| Previously, when applying a template in ASM, an error may have occurred which caused one or more Actions to not be linked to Risks. This issue has been resolved. | DE103599 |
Calibration Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| You can now perform a manual calibration on tasks with Fluke 74X templates. To facilitate this enhancement, in the Calibration Queue section, the Manual Calibration button is enabled for tasks whose device type is Fluke 74X. | US306467 | ||||||||||||||||||||||||||||||||
| You can now use Kilopascal (KPA) and Megapascal (MPA) as units of measurement (UOM) in a calibration template while performing calibration on the Fluke device. To facilitate this enhancement, KPA and MPA UOMs are now available for you to add to the CALIBRATION UOM PRESSURE reference table by selecting the MI_CALIBRATION_REFERENCES system code table. | US298314 | ||||||||||||||||||||||||||||||||
To enhance usability, the Calibration Data Loader worksheets have been renamed as follows:
Note: Data Loaders with old worksheet names will also be supported. | US294225 | ||||||||||||||||||||||||||||||||
|
The Calibration Management module now supports calibration of Functional Location and custom asset. You can now map any of the fields of the Equipment, Functional Location, or custom asset family as an asset ID, which is used to construct the Applied Template ID and in the data loader to find the asset. To facilitate this enhancement, the following changes have been made:
|
F40674 |
| Description | Tracking ID |
|---|---|
| Previously, in the Channel/Modules section, when you tried to access the Protective Instrument Loop Logic Solver Channel for a Protective Instrument Loop or a PIL Template, a blank datasheet appeared. This issue has been resolved. | DE103480 |
Previously, when you accessed a localized version of the Calibration Management module, the following issues occurred:
These issues have been resolved. |
|
| Previously, if the Task ID field in a Calibration Task contained a slash (/) character, and you attempted to perform an automated calibration using a CMX device or a manual calibration, an error occurred. This issue has been resolved. | DE101587 |
| Previously, when CalibrationDataModelUpgradeUtility was run to upgrade to V4.2.0.0 or later, an error occurred. This issue has been resolved. | DE101561 |
| Previously, if you sent calibration data to a GE Druck calibrator and performed only the as-found calibration, you could not receive data from the calibrator. This issue has been resolved. | DE101348 |
| Previously, in the Calibration Queue section in the Calibration Management Overview page, if you filtered for a specific asset, although the number in the Calibration Queue tab was updated with the number of records for the new asset, the list of records in this section remained the same. This issue has been resolved. | DE100627 |
| Previously, in the Calibration Data Loader, for each Recommendation that you wanted to create in a batch, only the first Recommendation was created. Due to this, multiple records were created for the first Recommendation in the batch, and no records were created for the rest of the Recommendations. This issue has been resolved. | DE94856 |
| Previously, in the Calibration Admin Preferences page, in the Default Configurations workspace, when you did not select a value in the Input Damping Setting, Output Damping Setting, or Input Min Max Mode drop-down list box, and then tried to add a calibration template, an error occurred. The issue occurred because these fields were being populated by the MI_DAMPING_TYPE system code table, which did not match the default values provided in the Input Damping Setting, Output Damping Setting, or Input Min Max Mode fields in the Calibration Setup Defaults record. This issue has been resolved. Now, the fields are populated by the MI_STATUS system code table instead of the MI_DAMPING_TYPE system code table. | DE93938 |
| Previously, in the Calibration Data Loader, in the MI_EVENTS worksheet, when you added a Cylinder ID column with a cylinder ID value, and then attempted to import data for a Calibration, Multi-Component Analyzer event, an error occurred. This issue has been resolved. | DE91121 |
|
Previously, if you sent data to a Fluke calibrator using a template with the following settings, the output UOM was set to mV:
Due to this, the output value in the calibrator was recorded in mV. This issue has been resolved. | DE91098 |
|
Previously, in the Download Calibration Checklists section of the Receive From Device window, after receiving data from the GE Druck calibrator, the following issues existed:
These issues have been resolved. | DE82718 |
| Description | Tracking ID |
|---|---|
| The MI_DAMPING_TYPE system code table is no longer used in Calibration Management. This is because the values in the system code table did not match with the values in the baseline default configuration. | DE93938 |
Cases
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can now refresh the cases inbox, cases grid, and case details to view the latest information. | F41109 |
| You can now release the claim from a case that you own. The case can belong to the same tenant or another tenant. | F38744 |
| Description | Tracking ID |
|---|---|
| Previously, in a cases grid, the Asset Alias column was blank. This issue has been resolved. | DE100785 |
| Previously, if your user name was modified, when you updated the Notes or Evidence section of a case, the user details in these sections still contained your previous user name. This issue has been resolved. | DE94606 |
| Previously, you could not change the state of a case that belonged to another tenant. This issue has been resolved. | DE94595 |
| Previously, you could assign cases to an administrator of another tenant even though the administrator did not have the permission to access cases. This issue has been resolved. | DE94443 |
| Previously, if you ingested cases from an external source, the Created On field for each case contained the date when the case was ingested instead of the date on which the case was created. This issue has been resolved. | DE92236 |
| Description | Tracking ID |
|---|---|
| The comments that are added to the Recommendations section of a case are not saved. Note: This issue is not applicable to legacy Predix APM. | DE44506 |
Release Date: February 08, 2019
| Description | Tracking ID |
|---|---|
| The generated PDF report for a case now contains the Notes section of the case. | US312894 |
| The charts in the Analysis and Evidence sections of a case now appear as images in the generated PDF report. | US275488 |
| Description | Tracking ID |
|---|---|
| If an analysis or evidence of a case contains multiple cards, only the charts of the first card appear in the generated PDF report. | DE100856 |
| Export of case details to a PDF file may take may take up to five minutes. | NA |
| When you export the details of multiple cases to a PDF file using the Bulk Actions menu, analysis charts in the Analysis and Evidence sections of a case does not appear in the generated PDF report. | NA |
Release Date: January 23, 2019
| Description | Tracking ID |
|---|---|
| Previously, if a Closure Code or Status was available in the case configuration file of your tenant, but the code or status was not available in the case configuration file of another tenant, when you attempted to select the Closure Code or Status for a case that belonged to the other tenant, an error occurred. This issue has been resolved. | DE96086 |
Compliance Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
|
The Compliance Management module has been introduced in V4.3.0.7.0. You can use this module to create Inspection Plans that adhere to inspection requirements set by regulatory bodies, corporate guidelines, or industry best practices. | F38782 |
APM Data Extraction
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| APM Data Extraction service has been introduced in this release. This service has been implemented based on OData v4.01 specification. Using this service, you can expose your APM database, enabling entities to be accessed using an Open Data interface. Reporting and Business Intelligence tools using OData requests can read this exposed data with the help of simple queries, enabling you to visualize and analyze the data. | F40154 |
| Description | Tracking ID |
|---|---|
| Data filters are not supported in Unit of Measurement (UOM) fields. | DE103033 |
| Data formatting options such as time zone conversions, currency formats, and number formats are not supported. | DE102126 |
Data Loaders UDLP V2.6.0
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, when a request from a data loader job running in the database timed out, the job status incorrectly appeared as Dataloader Enqueued. Now, the job status correctly appears as Cancelled. | DE91700 |
Data Permissions
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| In the Assign Users window, you can now search for a Security User using the User ID of the Security User. | US291131 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to search for a family, the search results displayed only the families whose names started with the exact string that you specified in the search criteria. This issue has been resolved. Now, you can search for all the families whose names contain the string that you specify in the search criteria. | DE87016 |
eLog
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
|
To define your work routine, you can now perform the following tasks:
To facilitate this enhancement, the following changes have been made:
|
|
You can now manage settings for the eLog module using the eLog Administration page. To facilitate this enhancement, the eLog module has been added to the Application Settings. In addition, the following changes have been made:
|
|
|
You can now access, create, and delete a Shift. To facilitate this enhancement, the Shifts section is added to the eLog Administration page. In addition, the following fields have been added to the Shift family:
| US281062 |
|
In the Shift Records topic, the following fields have now been included:
In addition, the Shift ID field has been named the Shift Name field. | US281062 |
| Description | Tracking ID |
|---|---|
| The Log Entry family and its subfamilies have been replaced with a new family, eLog Entry. | US311105 |
| In the Graphs folder, the Log Entries by Type item has been deprecated. | US311105 |
In the Queries folder, the following items have been deprecated:
| US311105 |
The following System Code Tables have been deprecated:
| US311105 |
Family Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| When you attempt to update the existing records for a given family with the modified record ID, now, a new job, UpdateTemplateIDJob, is created in the Schedule Logs page to update the existing records. This enhancement significantly improves the performance of the system while updating the records in bulk. | US299142 |
| The first report that you associate with a family becomes the default report for the family. | US293868 |
| You can now hide a datasheet belonging to a family that you do not want to appear for the corresponding records. To facilitate this functionality, the Hide check box has been added to the Datasheet Information window of the Datasheet Builder page. | US290738 |
| Description | Tracking ID |
|---|---|
| Previously, if a newly created field had been added to a datasheet belonging to the Checklist Findings family, and you attempted to access a checklist category for an inspection belonging to a checklist inspection family, an error message appeared, indicating that the datasheet failed to load. This issue has been resolved. | DE101578 |
Previously, in the Manage ID Template window, while entering a delimiter for a field in the Delimiter box, if you entered a space, the space did not appear in the New ID Template value in the following scenarios:
| DE92913 |
Failure Modes and Effects Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
To enhance usability, in the Analysis Details pane, the following lists are now sorted alphabetically:
| US302942 |
To enhance usability, in the Analysis Details page, the number of associated records now appears as a count in the following sections:
| US301505 |
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | US291070 |
| To maintain consistency, in the Recommendations pane, State Management is now controlled by the same functionality as other GE Digital APM modules. | US283474 |
| To enhance usability, in the Analysis Details page, in the Decision Logic section of the Failure Effect workspace, the decision logic workflow has been condensed and simplified. | US274365 |
| Description | Tracking ID |
|---|---|
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
| Previously, in the Import Data section, when you attempted to execute the Failure Modes and Effects Analysis (FMEA) Data Loader, an error could appear in the log. This issue has been resolved. | DE95839 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
Family Policies
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To improve the performance of the Predix Time Series node, the default number of readings that the Predix Time Series node retrieves from a Time Series data source has been reduced from 500000 to 10000. | US327520 |
| The Edit Entity node now updates records from a collection of values irrespective of the name of the collection column containing the entity keys. To facilitate this enhancement, the Entity Key Column drop-down list box has been added to the Properties window for the Edit Entity node where you can specify the collection column containing the entity keys. | US314481 |
| The minimum time interval that you can configure to run a job that deletes the execution history logs from the database is now increased to one hour. Note: If you had specified the time interval value for the job in minutes, the specified value is rounded up to the nearest value in hours, and the updated value appears in the Execution History Settings workspace. However, the job will continue to run at the time intervals that you had specified until you save the modified settings for the job. | US311726 |
| You can now access the execution details of a sub policy from the calling policy. To facilitate this enhancement, the View Execution Details link, which can be used to view the policy model and execution details of the sub policy in a separate window, has been added to the Node Execution Details window for the Sub Policy node. | US306756 |
| You can now configure a policy to apply an asset strategy template to an asset or asset strategy. To facilitate this enhancement, the Apply Strategy Template node has been added to the Actions section of the toolbar in the Design workspace. | US298658 |
| You can now convert the output value of a node to another data type. To facilitate this enhancement, the Convert Type node has been added to the Calculations section of the toolbar in the Design workspace. | US297271 |
While configuring the properties of a Create Alert node, you can now select the following values for the Boolean attributes:
| DE97664 |
| In the Properties window for the Create Alert and Query Alerts nodes, the Asset UUID field has been renamed Asset Unique ID. |
|
| Description | Tracking ID |
|---|---|
| Previously, if Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the Policy Trigger Service and Policy Execution Service failed to automatically reconnect with MSMQ even after it became available again. This issue has been resolved. | US307302 |
| Previously, if the Time Series data contained a non-numeric value, the Predix Time Series node could not retrieve the data, and the execution of the policy failed. Now, in this scenario, the Predix Time Series node can retrieve both numeric and non-numeric values from the Time Series data source. | DE104977 |
| Previously, the collection of values returned by a sub policy was incorrectly mapped to the columns of the collection output of the corresponding Sub Policy node in the calling policy. This issue has been resolved. | DE102425 |
| Previously, in a policy that contained a Predix Time Series node and a primary node configured to represent an asset, if an error occurred when you specified a Time Series tag for an instance, an error message appeared every time you added or deleted any node from the policy model. This issue has been resolved. Now, in this scenario, the error message appears only when you add or delete an Input node from the policy model. | DE101979 |
| Previously, if you mapped the collection output of a node to a Last node that was not its immediate successor node in the policy model, and then mapped the output of the Last node to an Is Null node, the input mappings of the Is Null node were not retained. This issue occurred when you saved and then reloaded the policy. This issue has been resolved. | DE101761 |
| Previously, if you configured a Case node or Is Null node to pass a time stamp value to an Add Value to Health Indicator node, the validation and execution of the Add Value to Health Indicator node failed, and an error message appeared in the Execution Details window indicating that the date is not in Coordinated Universal Time (UTC). This issue has been resolved. | DE98447 |
| Previously, if you validated or executed a policy that contained a Math node with an invalid mathematical expression, an incorrect error message appeared, indicating an R Server connection issue. This issue has been resolved. | DE98244 |
| Previously, if you executed a policy that contained an Edit Entity node from another GE Digital APM module, an incorrect value was updated in the record mapped to the node. This issue occurred if your user account was configured with Metric Unit of Measure (UOM) preferences, and the base UOM configured for the field updated by the policy was not a Metric unit. This issue has been resolved. | DE98240 |
| Previously, in the Properties window for a Create Alert node, when you specified any value other than true or false for a Boolean attribute, no error message appeared to indicate that the specified values were invalid for the attribute. However, when you executed the policy, the execution failed. This issue has been resolved. Now, the Value box corresponding to the Boolean attributes has been replaced by the Yes and No options so that you cannot specify any invalid value for the attributes. | DE97664 |
| Previously, duplicate policies for the same family and trigger could exist in the GE Digital APM database. In this scenario, you could not delete the duplicated policy. This issue has been resolved. | DE95827 |
| Previously, when you attempted to access an imported policy that contained a Create Entity node for a family that did not exist in the GE Digital APM database, the policy did not load. This issue has been resolved. Now, the policy loads regardless of the family is specified for the Create Entity node. | DE92631 |
| Previously, if you configured a policy with a Baseline Rule node for a family whose ID contained a space, the validation and execution of the policy failed. This issue has been resolved. | DE91542 |
Previously, if you did not update the memory cache after creating or deleting a family policy, the following issues occurred:
| DE91303 |
| Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved. | DE91301 |
Previously, in the Properties window, if you attempted to map a column of a query result to an input field, the drop-down list box to specify the column of the query result did not appear for the following nodes:
| DE90835 |
| Previously, irrespective of the display language configured for your user account, the name of the Sub Policy node always appeared in US English. This issue has been resolved. | DE89416 |
| Previously, in the Properties window for the Create Relationship node, if you specified duplicate predecessor or successor entity keys to create multiple one-to-one relationships, and then validated or executed the policy, a validation error occurred for the node. This issue has been resolved. | DE89330 |
Previously, when you attempted to access a policy, the policy did not load if it contained the following nodes:
| DE88744 |
| Previously, in the toolbar of the Design workspace, nodes configured to be available only for specific licenses were available even if you did not have the corresponding licenses. This issue has been resolved. | DE87323 |
| Previously, if you had specified a time zone other than Coordinated Universal Time (UTC) for a policy with a Predix Time Series node, and then executed the policy, the time stamp values provided by the Predix Time Series node to the successor nodes were offset by the time difference between UTC and the policy time zone. This issue has been resolved. | DE86461 |
| Description | Tracking ID |
|---|---|
| In the Properties window for the Create Alert node, the Recurring option has been removed from the Field drop-down list box. | DE91756 |
Foundation
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| GE Digital APM has been tested with Google Chrome versions 72 and 73. | US336340 |
| Description | Tracking ID |
|---|---|
| Previously, when you logged in to GE Digital APM and did not access certain modules for an hour, the user session ended when you attempted to access these modules. This issue has been resolved. | DE104442 |
GE Dashboards
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, when filtering or searching, the Context Browser listed assets in a flat, non-hierarchical view. With this release, the Context Browser displays the hierarchies of assets in a tree view when filtering or searching. | US319710 |
The following widgets add support for asynchronous queries when the timespan configuration option is set to six months or more:
|
|
| You can now set the home dashboard from the dashboard browser or dashboard menu. Note: This feature is not available in Legacy Predix APM. | US211742 |
Release Date: February 6, 2019
| Description | Tracking ID |
|---|---|
| Previously, when a dashboard was created with no asset context and an Unclaimed Alerts widget was subsequently added to the dashboard, the widget did not display the correct number of unclaimed alerts. Now, the Unclaimed Alerts widget performs correctly on dashboards that do not have an asset context. | DE98875 |
General Dashboards
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
You can now export the contents of a dashboard to a PDF. When viewing a dashboard, you can now select the More Options button ( ), and then select Export to PDF. | US290439 |
Generation Availability Analysis (GAA)
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can no longer create a log entry from an Event if you are not signed in to the Shift for which you want to create a log entry. | US316276 |
Generation Availability Analysis Wind (GAA Wind)
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
For a given Sub Group, month, and year, you can now see the distribution of the generation values (that is, gross actual generation and net actual generation) in a bar chart. To facilitate this enhancement, the following changes have been made:
| US319750 |
| You can now access Events that need review (that is, Events whose value in the NERC Type field is neither CTH nor RUTH). To facilitate this enhancement, the Events Needing Review section has been added to the GAA Wind Overview page. | US318255 |
To improve the accuracy of the data used to create or regenerate Performance Records, the following changes have been made:
| US308241 |
| To enhance usability, the date and time values now appear according to the culture and time zone settings in your user profile. | US308239 |
| You can now access information about the error that appears in the Error Code column. To facilitate this enhancement, the error value in the Error Code column has been made a link. | US308237 |
| You can no longer create a Performance Record if the IU time percentage for the associated Events exceeds 2%. | US308235 |
| You can now modify Events from the GAA Wind Overview page. To facilitate this enhancement, the Edit Events button has been introduced in the All Events, Edited Events, and Events Needing Review sections in the GAA Wind Overview page. | US299742 |
|
For a Unit in a Sub Group, if the imported Events have a gap in time, you can now create one or more Events for the missing period.
Note: For a Unit, for the specified period (that is, the report time), if the value in the Start Date field of an Event is different from that in the End Date field of the previous Event, the two Events are considered to have a gap in time. In addition, for the Unit, if the imported Events do not account for the complete duration of the specified period, the Events are considered to have a gap in time. To facilitate this enhancement, the following changes have been made:
|
|
|
To enhance usability, in the GAA Wind Event Import page, the following columns have been added:
| US295385 |
|
You can now split an Event into two or more Events. To facilitate this enhancement, the following changes have been made:
| US295338 |
|
To improve usability, the following fields have been added to the GAA Wind Performance family:
In addition, with the exception of the Gross Actual Generation and Net Actual Generation fields, the fields that appear in the GAA Wind Performance datasheet are now disabled. |
|
|
To enhance usability, the Event Duration field has been added to the GAA Wind Events family. This field appears as a column in the tables in:
| US295324 |
) has been added.
) has been added.Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
|
You could not create a Performance Record for a month in the previous year.
Note: You can create a Performance Record only for the current month and the two months prior. | DE98725 |
Graphs
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
You can now export a graph to a PDF file. To facilitate this enhancement, the Export to PDF button ( ) has been added to the Graph Result workspace. | US297381 |
| You can now define where the legend for a graph should appear in the Graph Result workspace. To facilitate this enhancement, in the graph settings pane, the Show Legend check box is now the Legend drop-down list box, where you can select a location for the legend or hide the legend. | US290781 |
| For a numeric value in the tooltip of a graph, commas now appear as the thousands delimiter. To facilitate this enhancement, the format of the numeric value for a tooltip has been changed to match the format of the numeric value in the y-axis of the graph. | US283101 |
| Description | Tracking ID |
|---|---|
| Previously, for a pie chart with more than two pie slices, if the State management enabled Family for captions or System code table for captions option was selected in the Dimension for Category window, when you removed a row in the Series section of the Settings pane and saved the graph, multiple slices were removed from the graph. This issue has been resolved. | DE103948 |
| Previously, for a pie chart with two pie slices, if the State management enabled Family for captions or System code table for captions option was selected in the Dimension for Category window, when you removed a row in the Series section of the Settings pane and saved the graph, an error message appeared. This issue has been resolved. | DE103809 |
| Previously, after a database upgrade, when you attempted to access a graph based on a query that contained a family whose state management was enabled for captions, a spinner appeared, and the graph did not load. This issue can be resolved. For information on how to fix this issue, refer to KBA 6616. | DE101475 |
| Previously, when you accessed a pie chart based on a query that contained family state IDs, the state IDs incorrectly appeared as graph labels. This issue has been resolved. | DE100709 |
| Previously, if you created a graph using a Crosstab query and mapped fields containing site data to the vertical axis, the graph legend and tooltips contained values from the first field in the list, regardless of the site to which you are assigned. This issue has been resolved. | DE98265 |
Help System
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To improve accessibility and navigability of reference documentation for URLs, all URLs topics have been combined into the following section in the documentation: . Note: You can still also access the URLs topic for a module in the documentation for that module. | N/A |
Import and Export
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, if a policy that was scheduled to be executed was imported, when you updated the policy, a job to execute the policy was created in addition to the existing job that was created while importing the policy. This issue has been resolved. | DE98204 |
| Previously, when you attempted to export a family that had a field with a list of valid values associated with an APM Query, and if the APM Query had a prompt configured for it, an error occurred. This issue has been resolved. | DE94684 |
| Previously, if no rules were available in a rule library project, and you attempted to export the project, an error occurred and an incorrect message appeared in the error log. This issue has been resolved. Now, an appropriate error message appears in the error log, indicating that the rules are not available in the rule library project. | DE89799 |
Inspection Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
You can now generate and download multiple Inspection Reports at a time. To facilitate this enhancement, the following changes have been made:
| US278869 |
| Description | Tracking ID |
|---|---|
| Previously, if you used State Management and downloaded an inspection in offline mode along with the Inspection History Report, the Inspection Recommendations did not appear in the Recommendation History section of the report. This issue has been resolved. To facilitate this fix, the MI_INSPHIST_RECINSP query has been modified to include the State column. | US292248 |
| Previously, when you modified the queries in the Underlying Inspection Tasks and Underlying Recommendations sections in the Inspection Management Overview page, the counts in the Inspection Management tabs did not appear. This issue has been resolved. Now, you can add or delete columns from the Inspection Overview queries, but you cannot change the IDs of the query parameters. | DE105398 |
| Previously, when you configured an Inspection record to use a master/detail datasheet, an error occurred when saving the Detail section of the datasheet. This issue has been resolved. | DE104166 |
| Previously, if the Asset Hierarchy was configured to use the Equipment Has Equipment relationship, the Asset Hierarchy navigation links could not differentiate between a parent Equipment and a child Equipment. This issue has been resolved. | DE103536 |
| Previously, when you added a Bundle Sub-Inspection, General Finding, or Pressure Test Sub-Inspection to a parent Inspection record, you were unable to navigate back to the parent record without saving the new related record. This issue has been resolved. Now, when you navigate back to the parent inspection without saving the related record, a message appears, asking you to confirm whether you want to save the unsaved changes. | DE103287 |
| When you used a Samsung Galaxy Tab Active 3 with Android version 5.1.1 to create an Inspection, the Inspection Tasks drop-down list box did not appear within the visible portion of the window. | DE102573 |
| Previously, when you created a non-recurring Inspection Task using the Inspection Management (IM) Assets or Inspection Management (IM) Functional Location data loader, an error message appeared in the log even though the Desired Interval cell was blank or contained the value 0. This issue has been resolved. | DE95976 |
| Previously, when you saved a record in the Inspection Confidence Evaluation section and then attempted to navigate to any other section (such as the Team Members or Inspection Data sections) quickly, an error occurred. This issue has been resolved. Note: This issue occurred only if network connectivity was poor when using GE Digital APM. | DE93365 |
| Previously, when you accessed an Inspection record and then attempted to navigate to any other page within GE Digital APM quickly, an error occurred. This issue has been resolved. Note: This issue occurred only if network connectivity was poor when using GE Digital APM. | DE93361 |
| Previously, when you attempted to print a General Inspection Report or NR13 General Inspection Report with blank values in the Commencement Date or Completion Date fields, the report did not print. This issue has been resolved. | DE89775 |
| Previously, when you attempted to select a value in the Type of Inspection drop-down list box that contained more than 50 characters, an error occurred, and the value was not selected. This issue has been resolved. | DE82361 |
| Previously, when you attempted to create an inspection for equipment, the Inspection Tasks that were associated with the functional location of the equipment did not appear in the Inspection Tasks drop-down list box of the Create Inspection window. This issue has been resolved. | DE82621 |
| Previously, when you created or updated an Inspection record using the Inspection Management (IM) Assets or Inspection Management (IM) Functional Location data loader without any value in the Final Inspection Lock column, the Inspection Lock check box was not selected even if you set the value as True in the data loader template. This issue has been resolved. | DE81521 |
Life Cycle Cost Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance usability, in the Summary section of the Analysis Summary workspace, the Total Cost chart has been added to the drop-down list box. The Total Cost chart displays a cumulative summary trend of the associated capital costs and operating costs for a scenario. | US254827 |
| Description | Tracking ID |
|---|---|
| Previously, in the Scenario Definition section of the Analysis Summary page, if you assigned an asset group to either the Primary Element Name or Secondary Element Name fields of the datasheet and then saved the analysis, if you navigated to the LCC Overview page and attempted to use the Asset Hierarchy to filter to the asset group you selected in the Scenario Definition section, the new analysis did not appear in the LCC Analyses section. This issue has been resolved. | DE93382 |
| Previously, in the LCC Overview page, if you accessed an analysis by selecting an item from a chart in the LCC Overview page, the Analysis Summary page for that analysis appeared; however, one or more errors occurred. This issue has been resolved. | DE93217 |
| Previously, in an Operating Cost row of the Cost Data grid, if you added a new Resource, and if the value in the Cost Per Period column for that new Resource was greater than 1000, the value that appeared in the Cost Per Period column was 1000 times less than the entered value. This issue has been resolved. Now, when you enter a value in the Cost Per Period column for a new Resource in the Cost Data Grid, the value in the Cost Per Period column appears as expected. | DE92991 |
Previously, if you selected  to search for a specific LCC analysis, if you selected a result that was returned by the global search, the selected LCC analysis did not appear. This issue has been resolved. You can now use the button to search for and to navigate to a specific LCC analysis. | DE88780 |
| Previously, after upgrading Life Cycle Cost Analysis (LCC) from a prior version of GE Digital APM, if you accessed the Cost Data Report from the Analysis Summary page, an error occurred. This issue has been resolved. | US285838 |
Maximo UDLP V2.6.0
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| APM Connect now supports customized mappings for Maximo Notification Management. | US258012 |
Metrics and Scorecards
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
To improve usability, GE Digital APM users can now map the event and asset criticality data available in their database to the standard event and asset criticality data defined for a work history cube using the corresponding families. To facilitate this enhancement, the following baseline families have been created in Family Management. You can run an update query for each of these families to modify and map the Event and Asset criticality data available in your database to the standard data available in GE Digital APM.
| US297906 |
| Description | Tracking ID |
|---|---|
Previously, if your culture setting had a culture other than English and you accessed the following windows while creating a metric view or a Key Performance Indicator (KPI), the names of the windows were not translated to the appropriate language for your culture setting.
| DE93383 |
Policy Designer
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To improve the performance of the Predix Time Series node, the default number of readings that the Predix Time Series node retrieves from a Time Series data source has been reduced from 500000 to 10000. | US327520 |
The following policies are now available as part of the baseline GE Digital APM:
|
|
| The Edit Entity node now updates records from a collection of values irrespective of the name of the collection column containing the entity keys. To facilitate this enhancement, the Entity Key Column drop-down list box has been added to the Properties window for the Edit Entity node where you can specify the collection column containing the entity keys. | US314481 |
| The minimum time interval that you can configure to run a job that deletes the execution history logs from the database is now increased to one hour. Note: If you had specified the time interval value for the job in minutes, the specified value is rounded up to the nearest value in hours, and the updated value appears in the Execution History Settings workspace. However, the job will continue to run at the time intervals that you had specified until you save the modified settings for the job. | US311726 |
| You can now view the execution result of a Sub Policy node in the execution summary of the policy. To facilitate this enhancement, the policy execution summary has been modified to display the number of times the Sub Policy node executed the associated sub policy. | US306760 |
| You can now access the execution details of a sub policy from the calling policy. To facilitate this enhancement, the View Execution Details link, which can be used to view the policy model and execution details of the sub policy in a separate window, has been added to the Node Execution Details window for the Sub Policy node. | US306756 |
| You can now configure a policy to apply an asset strategy template to an asset or asset strategy. To facilitate this enhancement, the Apply Strategy Template node has been added to the Actions section of the toolbar in the Design workspace. | US298658 |
| You can now convert the output value of a node to another data type. To facilitate this enhancement, the Convert Type node has been added to the Calculations section of the toolbar in the Design workspace. | US297271 |
| The R Scripts module now supports Machine Learning Server 9.2.1 in addition to R Server 8.0.0. To facilitate this enhancement, in the Connections page, the R Server Version drop-down list box has been added to enable you to select the version of your R Server. | US283973 |
| When you deploy Policy Designer for the first time or upgrade to version 4.3.0.7.0, you must configure the Meridium Notification Service to enable the Policy Execution Service. | DE103226 |
While configuring the properties of a Create Alert node, you can now select the following values for the Boolean attributes:
| DE97664 |
| In the Properties window for the Create Alert and Query Alerts nodes, the Asset UUID field has been renamed Asset Unique ID. |
|
| Description | Tracking ID |
|---|---|
| Previously, if multiple entities were associated with an entity ID that you specified in the Policy Instance Data Loader, no records associated with the entity ID were mapped to the instance. Now, in this scenario, if one of the records associated with the entity ID is linked to the primary record of the instance, the record that is linked to the primary record is mapped to the instance. | US311492 |
| Previously, if Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the Policy Trigger Service and Policy Execution Service failed to automatically reconnect with MSMQ even after it became available again. This issue has been resolved. | US307302 |
| Previously, if the Time Series data contained a non-numeric value, the Predix Time Series node could not retrieve the data, and the execution of the policy failed. Now, in this scenario, the Predix Time Series node can retrieve both numeric and non-numeric values from the Time Series data source. | DE104977 |
| Previously, the collection of values returned by a sub policy was incorrectly mapped to the columns of the collection output of the corresponding Sub Policy node in the calling policy. This issue has been resolved. | DE102425 |
Previously, if you frequently switched between pages, workspaces, windows, or sections while using Policy Designer for a long period of time, the following issues occurred:
| DE102142 |
| Previously, in a policy that contained a Predix Time Series node and a primary node configured to represent an asset, if an error occurred when you specified a Time Series tag for an instance, an error message appeared every time you added or deleted any node from the policy model. This issue has been resolved. Now, in this scenario, the error message appears only when you add or delete an Input node from the policy model. | DE101979 |
| Previously, if you mapped the collection output of a node to a Last node that was not its immediate successor node in the policy model, and then mapped the output of the Last node to an Is Null node, the input mappings of the Is Null node were not retained. This issue occurred when you saved and then reloaded the policy. This issue has been resolved. | DE101761 |
| Previously, after successfully processing data, the data loader log displayed a record count of 0. Now, the data loader log displays the correct record count. | DE100703 |
| Previously, if you deleted the Input node that represented the primary record for an instance and saved the policy, when you specified the primary record for any instance using the Policy Instance Data Loader, the primary record was not mapped to the instance. This issue has been resolved. | DE99335 |
| Previously, if you configured a Case node or Is Null node to pass a time stamp value to an Add Value to Health Indicator node, the validation and execution of the Add Value to Health Indicator node failed, and an error message appeared in the Execution Details window indicating that the date is not in Coordinated Universal Time (UTC). This issue has been resolved. | DE98447 |
| Previously, if you validated or executed a policy that contained a Math node with an invalid mathematical expression, an incorrect error message appeared, indicating an R Server connection issue. This issue has been resolved. | DE98244 |
| Previously, if you executed a policy that contained an Edit Entity node from another GE Digital APM module, an incorrect value was updated in the record mapped to the node. This issue occurred if your user account was configured with Metric Unit of Measure (UOM) preferences, and the base UOM configured for the field updated by the policy was not a Metric unit. This issue has been resolved. | DE98240 |
Previously, when you imported instances for multiple policies using the same Policy Instance Data Loader workbook, the following issues occurred:
| DE98002 |
| Previously, in the Properties window for a Create Alert node, when you specified any value other than true or false for a Boolean attribute, no error message appeared to indicate that the specified values were invalid for the attribute. However, when you executed the policy, the execution failed. This issue has been resolved. Now, the Value box corresponding to the Boolean attributes has been replaced by the Yes and No options so that you cannot specify any invalid value for the attributes. | DE97664 |
| Previously, in the Instances section of a policy, if you specified a Predix Time Series tag for an instance and saved the policy, when you reloaded the policy, the specified tag did not appear in the Predix Time Series box corresponding to the instance. However, the specified tag was correctly mapped to the Predix Time Series node in the GE Digital APM database, and you could successfully validate and execute the instance. This issue occurred if the instance contained a primary record and if the specified tag was not available among the first 25 tags that appeared in the Select a Time Series Tag window for the Predix Time Series box. This issue has been resolved. Now, in this scenario, the specified tag appears in the Predix Time Series box when you reload the policy. | DE97202 |
Previously, if the deletion of an instance failed for any reason, the following issues occurred:
| DE96251 |
| Previously, when you accessed the Policy Designer Overview page, the page did not load or took a long time to load. This issue occurred when the GE Digital APM database contained a large number of execution history records. This issue has been resolved. Note: If the issue persists, configure the Policy Designer Overview page to use the alternative query (Policy Overview – Policies Alternate Query) that has been added to the GE Digital APM Catalog. For more information on configuring the alternative query, contact Global Support Services. | DE95004 |
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
|
|
| Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved. | DE94085 |
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
| DE93538 |
| Previously, when you attempted to import policy instance data using the Policy Instance Data Loader, the data was not imported and an error message appeared in the data loader log, indicating that the Instance ID value exceeded the maximum character limit. This issue occurred if you assigned the first field sequence number for the Policy Instance family to a field with a maximum character limit less than the number of characters in the Instance ID specified in the data loader. This issue has been resolved. Now, in this scenario, the data is successfully imported. | DE93209 |
| Previously, when you attempted to access an imported policy that contained a Create Entity node for a family that did not exist in the GE Digital APM database, the policy did not load. This issue has been resolved. Now, the policy loads regardless of the family is specified for the Create Entity node. | DE92631 |
| Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your GE Digital APM user account instead of the policy time zone. This issue has been resolved. | DE91644 |
| Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved. | DE91301 |
| Previously, if you mapped the output of a Health Indicator node to a Comparison node, and then mapped the logical result of the Comparison node to an And or Or node, validation and execution of the policy failed. This issue has been resolved. | DE90937 |
Previously, in the Properties window, if you attempted to map a column of a query result to an input field, the drop-down list box to specify the column of the query result did not appear for the following nodes:
| DE90835 |
| Previously, if a policy was executed by a family-level rule or another GE Digital APM module multiple times within a short duration, the execution results for the Math and Text nodes were intermittently incorrect after the first execution. This issue has been resolved. | DE89726 |
Previously, irrespective of the display language configured for your user account, the text always appeared in US English for the following items:
| DE89416 |
| Previously, in the Properties window for the Create Relationship node, if you specified duplicate predecessor or successor entity keys to create multiple one-to-one relationships, and then validated or executed the policy, a validation error occurred for the node. This issue has been resolved. | DE89330 |
Previously, when you attempted to access a policy, the policy did not load if it contained the following nodes:
| DE88744 |
| Previously, in the toolbar of the Design workspace, nodes configured to be available only for specific licenses were available even if you did not have the corresponding licenses. This issue has been resolved. | DE87323 |
| Previously, if you had specified a time zone other than Coordinated Universal Time (UTC) for a policy with a Predix Time Series node, and then executed the policy, the time stamp values provided by the Predix Time Series node to the successor nodes were offset by the time difference between UTC and the policy time zone. This issue has been resolved. | DE86461 |
| Description | Tracking ID |
|---|---|
| In the Properties window for the Create Alert node, the Recurring option has been removed from the Field drop-down list box. | DE91756 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| The R Scripts module now supports Machine Learning Server 9.2.1 in addition to R Server 8.0.0. To facilitate this enhancement, in the Connections page, the R Server Version drop-down list box has been added to enable you to select the version of your R Server. | US28397 |
Production Loss Analysis (PLA)
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Production Data workspace, when you modified the value in the Actual column, the value in the Unit Key field of the Production Data record changed to 0. This issue has been resolved. | DE103340 |
| Previously, after successfully processing data, the data loader log displayed a record count of 0. Now, the data loader log displays the correct record count. Note:
| DE100708 |
| Previously, you could remove the mapping between an Event Code and a Production Unit if that Event Code was used in a Production Event. This issue has been resolved. | DE88958 |
Queries
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, if your culture setting was anything other than English and you ran a query with a field that was added twice with different aliases, if one of the fields was configured such that it did not appear in the query results, no values were displayed in the query results. This issue has been resolved. | DE103503 |
| Previously, when you used the ORDER BY clause to sort a column in a query that contained the UNION operator or a SELECT DISTINCT statement and ran the query, an incorrect column was sorted in the query results. This issue occurred when the ORDER BY clause referenced an expression column by its alias. This issue has been resolved. | DE101497 |
| Previously, when you ran a query that used the UNION operator as a formatted query, an error occurred, and the query did not return any results. This issue has been resolved. | DE101292 |
| Previously, when you ran a query that used the UNION operator to combine the result set of two SELECT statements containing a WHERE clause, if the WHERE clause did not contain an AND operator, an error occurred, and the query did not return any results. This issue has been resolved. | DE100416 |
| Previously, when you ran a formatted query with the limit results to top condition, the query did not return the expected results. This issue has been resolved. | DE99794 |
| Previously, in the Conditions section of the Design workspace, when you hovered over a Hyperlink, Criteria or Or cell, a tooltip did not appear. This issue has been resolved. | DE94420 |
| Previously, when you attempted to export a query result set to a dataset, only the first 100 records in the query result set were exported. This issue has been resolved. | DE93641 |
| Previously, when you ran a query that joined a family to multiple sub-families and the relationship family caption contained a hyphen, an error occurred, and the query did not return any results. This issue has been resolved. | DE89510 |
| Previously, when you accessed a Crosstab query in which a Total cell contained an aggregate function, incorrect values appeared in the Field and Alias cells. This issue has been resolved. | DE88704 |
| Previously, when you exported the results of a formatted query that contained the ENTY_KEY and FMLY_KEY fields to a dataset, the ENTY_KEY and FMLY_KEY columns in the dataset were blank. This issue has been resolved. | DE88523 |
| Previously, when you ran a formatted query where the same family was selected as the source and the related source, and the same field was selected from both sources, the related source field incorrectly displayed the source field value in the query results. This issue has been resolved. | DE88332 |
| Previously, when you ran a formatted query to create left joins on two subqueries that pull data from the same family, the query did not return the expected results. This issue has been resolved. | DE88141 |
| Previously, after selecting the Limit Results to Top check box and entering a value, if you ran an unformatted query and exported the query results to a Microsoft Excel file, the exported data in the file was different from the actual query results. This issue has been resolved. | DE79754 |
Record Manager
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, if you had uploaded a reference document that had a file name with Chinese characters and then downloaded the same document using the Internet Explorer browser, the name of the downloaded document was incorrect. This issue has been resolved. | DE90473 |
| Previously, while creating or modifying a record, the drop-down list boxes available in the datasheet were not highlighted with red borders, although a value was required for each drop-down list box. This issue has been resolved. | DE90469 |
| Previously, if a query had a field displaying date and time, if you used the query as a data source for a record that belonged to the Conditional Alerts family and scheduled the conditional alert, the time for a specific date displayed in the query result did not match the corresponding time displayed in the email that was sent when the conditional alert was executed. This issue has been resolved. | DE87509 |
| Previously, when you attempted to upload a reference document that had a file name with Russian characters, an error message appeared, indicating that the file type was not supported. This issue has been resolved. Now, you can upload a reference document with a Russian file name. | DE87014 |
| Previously, in the Record Explorer page, when you attempted to access a record that had a large number (approximately 30000) of successor records that are associated with the same family, an error occurred. This issue has been resolved. | US316553 |
Reliability Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
|
To enhance accuracy in System Reliability analyses, the Action Optimization section has been added to the Analysis Summary page. The Action Optimization section allows you to optimize a group of actions associated with an analysis to determine the optimum interval at which to perform inspection or preventative maintenance. After you have found the optimal interval for an action, you can apply it to that action. When you do so, the value in the Interval field in the System Action record will be overwritten with the value that exists in the Optimal Interval field. After you apply the optimal interval, you can then run the simulation for the System Reliability Analysis to update the result based upon the optimized interval. To facilitate this enhancement, a new family, System Action Optimization, has been added to System Reliability. | F39608 |
|
To enhance usability, the System Reliability Data Loader has been added to Reliability Analytics. Using the System Reliability Data Loader, you can import the following types of primary and third-party data from a fixed-format Excel workbook into the System Reliability Data Model:
| US317337 |
In the Simulation Results workspace of the Analysis Summary page, you can now view charts in full-screen mode by selecting the Expand button ( ). | US312695 |
| To enhance usability in Reliability Analytics, if you navigate away from an open page without saving your changes, the Unsaved Changes window now appears, prompting you to save. | US307526 |
| Description | Tracking ID |
|---|---|
| Previously, in the Simulation Results workspace, if there were invalid values in the Simulation, a warning message appeared that overlapped the column headings in the Simulation Results workspace. This issue has been resolved. Now, if there are invalid values in the Simulation, the warning message that appears does not overlap the column headings. | DE104107 |
| Previously, when using Internet Explorer, if you exported Simulation Results to a PDF, the resulting PDF did not contain any content. This issue has been resolved. | DE104091 |
| Previously, in the RA Overview page, if you selected the Spares Analysis tab before the RA Overview page finished loading, no analyses appeared in the Spares Analysis section. This issue has been resolved. | DE101856 |
| Previously, in the Definition section of a Spare Application, if you added an Application and with blank value in the Application Name box and then saved the Application, an error occurred. This issue has been resolved. Now, you cannot save an Application without entering a value in the Application Name box. | DE101854 |
| Previously, in the Diagram section of the workspace for a Scenario in a System Reliability Analysis, if you selected an asset and then navigated to the Actions section, your selection was not retained and Actions that were not associated with the selected asset appeared in the Actions section. This issue has been resolved. Now, if you select an asset in the Diagram section and navigate to the Actions section, only the Actions associated with the selected asset appear. | DE100207 |
Previously, when creating a new Risk record in System Reliability, if you saved the new Risk record multiple times, a Risk record was created each time that you selected the Save button ( ). This issue has been resolved. | DE98759 |
| Previously, in the Risks section of a System Reliability scenario, if you selected the link in a cell in either the Planned Resource Usages or the Unplanned Resource Usages column, the grid that appeared after selecting that link did not display the Fixed Cost and the Variable Cost fields, and you could not modify those fields in the datasheet. This issue has been resolved. | DE97078 |
| Previously, in the Resources section of a System Reliability Analysis, if the value in either the Fixed Cost or the Variable Cost cell was greater than 1000, the value that actually appeared in that cell was improperly truncated. This issue has been resolved. | DE97077 |
Previously, in the Assets section of the Reliability Distribution Data Editor window of a new Reliability Distribution analysis: These issues have been resolved.
| DE97069 |
| Previously, in the Number of Iterations field in the Definition section of the Analysis Summary page, you could enter a value less than 400 and save the record. If you entered a value in the Number of Iterations field that was less than 400, if you then accessed the Risks workspace of a Scenario, an error occurred. This issue has been resolved. Now, in the Definition section of the Analysis Summary page, you cannot enter a value less than 400 in the Number of Iterations field. | DE96567 |
| Previously, in the Reliability Analytics page, if you selected the Spares Analyses tab before the Reliability Analytics page finished loading, an error occurred. This issue has been resolved. | DE94260 |
| Previously, in a Google Chrome browser, when creating a new Reliability Distribution in the Reliability Distribution Builder window by manually entering data, an error sometimes occurred, and the Asset ID field could not be modified. This issue has been resolved. | DE93728 |
| Previously, when viewing plots in Analysis Summary page, if the value for the datapoint on the plot was less than one (for example, 0.01), the value plotted for the datapoint was incorrectly rounded to zero. This issue has been resolved. Now, datapoints with values less than one plotted in the Analysis Summary page appear as expected. |
|
| Previously, in the RA Overview page, after creating a new System Reliability analysis, no message appeared indicating whether or not your new analysis was created successfully. This issue has been resolved. | DE88121 |
), you could not add an asset to the Reliability Distribution.Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| Previously, when creating a new Risk record in System Reliability, if you saved the new Risk record multiple times, a Risk record was created each time that you selected the Save button (). This issue has been resolved. | DE96452 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
To enhance usability, in the Analysis Details pane, the following lists are now sorted alphabetically:
| US302942 |
To enhance usability, in the Analysis Details page, the number of associated records now appears as a count in the following sections:
| US301505 |
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | US291070 |
| To maintain consistency, in the Recommendations pane, State Management is now controlled by the same functionality as other GE Digital APM modules. | US283474 |
| To enhance usability, in the Analysis Details page, in the Decision Logic section of the Failure Effect workspace, the decision logic workflow has been condensed and simplified. | US274365 |
To enhance usability and to allow you to incorporate related Failure Mode Asset ID values that make family records unique, you can now include the related Asset ID value of the Failure Mode family in the following worksheets of the Reliability Centered Maintenance (RCM) Data Loader:
| DE94412 |
| Description | Tracking ID |
|---|---|
Previously, if your culture setting was anything other than English, and you accessed the following sections of the Reliability Centered Maintenance page, some of the column names were not translated to the language based on your culture setting.
|
|
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
| Previously, in the Import Data section, when you attempted to execute the Reliability Centered Maintenance (RCM) Data Loader, an error sometimes appeared in the log. This issue has been resolved. | DE95839 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
Report Configuration
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
You can now print and export SSRS reports in bulk, and you can configure the following:
| US305882 |
Risk Based Inspection (RBI) 581
This topic provides a list of product changes released for this module on the dates listed below.
RBI 580 and RBI 581
Release Date: March 25, 2019
| Note | Tracking ID(s) |
|---|---|
| Previously, when you were using a Risk Matrix other than Default or Standard Practice Risk Matrix, the categories defined in the MI_RISK_CATEGORY System Code Table had to be capitalized to correctly map RBI risk values. This issue has been resolved. Now, the values do not have to be capitalized. | DE104014 |
Release Date: March 29, 2019
| Note | Tracking ID(s) |
|---|---|
|
To enhance usability, the datasheet content for the following families has been reorganized:
|
|
| When viewing an analysis in the RBI module, you can now make changes to the analysis only if it is in the Created state. When you change the state of the analysis to any other state, the analysis and related records cannot be modified, and the Save button () is not available. Note:
The following fields in the Degradation Mechanism family are no longer editable:
| US304996 |
| You can now use a utility to generate Risk Assessment records for active RBI Criticality Analyses and RBI 581 Risk Analyses that do not have Risk Assessment records. Also, for the active RBI Criticality Analyses, the utility will calculate and set Half-Life for any related Ext. Corr. Deg. Mech Evaluations where the value is blank. After the utility is executed, the RBI 580 and RBI 581 analyses can be promoted to ASM, and RBI Recommendations can be generated for the active RBI 580 analyses with Ext. Corr. Deg. Mech Evaluations. | US272821 |
To reflect the changes in Addendum-1 of API-581 3rd Edition, the Component Damage and Personal Injury Area calculations for Type-1 flammable fluids have been modified as follows:
| US322083 |
You can now promote an Asset to Asset Strategy Management if all the RBI Components within the Asset contain an RBI Analysis in any of the following states:
| US272476 |
| You can now show or hide the analyses that are in the Archived state in the Component Overview page. To facilitate this enhancement, a new option, Hide Archived Analyses has been added to the Component Overview page. | F38674 |
| Note | Tracking ID(s) |
|---|---|
| Previously, when you were using a Risk Matrix other than Default or Standard Practice Risk Matrix, the categories defined in the MI_RISK_CATEGORY System Code Table had to be capitalized to correctly map RBI risk values. This issue has been resolved. Now, the values do not have to be capitalized. | DE103968 |
| Previously, if the Asset Hierarchy was configured to use the Equipment Has Equipment relationship, the Asset Hierarchy navigation links could not differentiate between a parent Equipment and a child Equipment. This issue has been resolved. | DE103536 |
| Previously, in an RBI Consequence Evaluation, in the Design Details section, the Consequence field was not translated. This issue has been resolved. Now, the Consequence field is populated by the MI_CONSEQUENCE_TYPES System Code Table, which is translated to the appropriate culture setting. | DE94112 |
| Previously, when you attempted to select an RBI Component from the Asset Details page, an error occurred. This issue has been resolved. | DE90981 |
| Previously, in an RBI Component or RBI Analysis, in the Design Details section, the Stress Lookup Table field was not translated. This issue has been resolved. Now, the Stress Lookup Table field is populated by the MI_STRESS_LOOKUP_TABLE System Code Table, which is translated to the appropriate culture setting. | DE90270 |
| Previously, in an Oracle database, when you calculated multiple assets in bulk that had more than 500 collective analyses, a timeout error occurred. This issue has been resolved. | DE88531 |
Previously, the allowable stress and flow stress values for a Pressure Vessel component were populated incorrectly if you used the following combination of values:
This issue has been resolved. | DE87370 |
| Previously, if a component had an analysis in the Approved state and, in the same component, you changed the status of another analysis to make it active, the previously active analysis was not moved to the Archived state automatically. This issue has been resolved. | DE92905 |
Previously, if your culture setting had a culture other than English, and you accessed the Risk Based Inspection Overview page, the following elements were not translated to the language based on your culture setting:
| US310483 |
Risk Based Inspection (RBI) 580
Release Date: March 29, 2019
| Note | Tracking ID(s) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
You can now configure the calculation of RBI Criticality Analysis as per your requirement without modifying the baseline rules. You can configure the calculation in one or more of the following steps:
To facilitate this enhancement, following changes have been made:
| F38674 |
Release Date: March 29, 2019
| Note | Tracking ID(s) |
|---|---|
|
Previously, when you calculated an RBI Criticality Analysis for a Heat Exchanger Bundle component, the following incorrect validations were performed:
These issues have been resolved. Now, the following validations are performed:
| DE94278 |
| Previously, in an RBI Consequence Evaluation, the Consequence field was not translated. This issue has been resolved. The Consequence field now displays the system code description of the MI_CONSEQUENCE_TYPES system code table and is translated to the appropriate culture setting. | DE94112 |
| Previously, in an RBI Component or RBI analysis, the Stress Lookup Table field was not translated. This issue has been resolved. Now, the Stress Lookup Table is populated with the MI_STRESS_LOOKUP_TABLE system code table description, which is translated to the appropriate culture setting. | DE90270 |
| Previously, the information on the valid values for the Selected Corrosion Rate field was incorrect in the Data Loaders section of the Risk Based Inspection (RBI) 580 user documentation. This issue has been resolved. | DE98980 |
Risk Based Inspection (RBI) 581
Release Date: March 29, 2019
| Note | Tracking ID(s) |
|---|---|
The following RBI 581 DM calculations are no longer dependent on the R Server:
|
|
| Note | Tracking ID(s) |
|---|---|
Previously, the fluid type of the following representative fluids was incorrectly marked as Reactive instead of Flammable:
This issue has been resolved. Now, the fluid type of these fluids is marked as Flammable. | DE101410 |
| Previously, in an RBI 581 Risk Analysis, if the time specified in the RBI Date field was later than the time specified in the Plan Date field, the Target Inspection Date field was updated incorrectly when you calculated the analysis. This issue has been resolved. Note: This issue was applicable to both the main RBI 581 Risk Analysis and the What-if Analysis. | DE83090 |
| Note | Tracking ID(s) |
|---|---|
The following R Scripts have been removed from RBI 581 policies:
|
|
Risk Matrix
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, if the Not Applicable check box was selected for a Risk Matrix category, the overall risk would not update until the Risk Matrix was saved. This issue has been resolved. | DE89701 |
Root Cause Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance usability, a new analysis type, the 5 Whys Analysis, has been added to Root Cause Analysis. Using this analysis, you can ask a series of questions to determine how an issue was reached and the root cause of that issue. To facilitate this enhancement, five Why fields and five Reason fields have been added to the baseline RCA Event Records family and appear in the Event datasheet when viewing a 5 Whys Analysis. | F42438 |
| To enhance usability, the Event Timeline has been added to the Analysis Summary page. Using this timeline, you can view Failure Events and plot them by their dates and times. | F39698 |
| To enhance usability, 5 Whys Analyses now appear in the Comprehensive Analysis Report. |
|
| The RCA Administrator page has been enhanced. A new workspace, Event Color Setting, has been added. In the Event Color Setting workspace, you can select and map specific colors to event types in the Event Timeline. | US316991 |
| The RCA Administrator page has been enhanced. A new workspace, RCA Pages Setting, has been added. In the RCA Pages Setting workspace, you can select the specific diagrams and process pages that you want to appear in the RCA module. | US316744 |
| In the Email Settings workspace of the RCA Administrator page, you can now define the source email address for a user to receive alerts for Preserve records. | US315309 |
| To enhance usability, in the RCA Analysis Summary page, in the Overview section, if you select the Recommendations chart, a list of recommendations for the selected analysis appears in the grid. | US279567 |
|
To enhance security, to update, insert, or delete an RCA Recommendation record, you must now be a member of either the MI PROACT Administrator Security Group or a member of the MI PROACT Team Member Security Group for the selected analysis.
Note: All members of RCA Security Groups can view RCA Recommendation records.
| US254542 |
| Description | Tracking ID |
|---|---|
| Previously, in the Track workspace, if you added a Tracking Item and then navigated to the Analysis Summary page, the Track Item chart was not updated with Tracking Item that you added. This issue has been resolved. | DE103448 |
| Previously, when viewing the Logic Tree diagram in the Comprehensive Analysis Report, the diagram appears in multiple pages. This issue has been resolved. Now, the Logic Tree diagram appears in a single page in the Comprehensive Analysis Report. | DE103237 |
| Previously, when viewing the Logic Tree Diagram, depending on the size of your screen, the Auto Arrange check box overlapped other elements in the Manage Diagram section. This issue has been resolved. To facilitate this fix, the Auto Arrange option has been moved to the More Options () menu. | DE101794 |
| Previously, after successfully processing data, the data loader log displayed a record count of 0. Now, the data loader log displays the correct record count. | DE100707 |
| Previously, in a Logic Tree Diagram, you could reposition the nodes even if the Auto Arrange check box was selected. This issue has been resolved. Now, if the Auto Arrange check box is selected, the nodes in the Logic Tree cannot be repositioned. | DE100121 |
| Previously, in the Analysis Summary page for an RCA Analysis that had more than two linked Recommendation records, if you selected the Recommendations chart, the grid that appeared below the chart only included two Recommendations records because the grid did not include a vertical scroll bar. This issue has been resolved. Now, a vertical scroll bar appears, and all linked Recommendation records appear in the grid. | DE91498 |
| Previously, in an RCA Logic Tree, if you enabled the Show Logic Gates option, an OR Logic Gate appeared below each node in the Logic Tree by default. This behavior occurred even if there was only one child node below the parent node. This issue has been resolved. Now, if you enable the Show Logic Gates option when there is only one child node below a parent node, the OR Logic Gate does not appear. | DE90271 |
| Previously, in an RCA Logic Tree, if the Show Logic Gates option was enabled, and if you added a single child Hypothesis node under either a parent Hypothesis node or a Failure Mode node, the Logic Gate incorrectly appeared between the single child and the parent nodes. This issue has been resolved. Now, if the Show Logic Gates option is enabled and you add a single child Hypothesis node under either a parent Hypothesis node or a Failure Mode node, the Logic Gate does not appear between the single child and the parent nodes. | DE90090 |
| Previously, when viewing reports in RCA, the Logic Tree Diagram contained in the report was often disjointed and spanned multiple pages. This issue has been resolved. Now, when viewing a Logic Tree Diagram within an RCA report, the Logic Tree Diagram appears on a single page. | DE90089 |
| Previously, if you exported a Logic Tree diagram, the exported diagram did not load properly, and you could not save the exported diagram. This issue has been resolved. | DE89932 |
Previously, when viewing the Logic Tree workspace in a browser in full-screen mode, the text from the Auto Arrange check box overlapped the Properties button ( ). This issue has been resolved. | DE89929 |
| Previously, when viewing an RCA Analysis, if you selected the Event Diagram tab, the Decision node was not available in the Palette section, and no other nodes could be dragged from the Palette section. This issue has been resolved. Now, if you access the Event Diagram tab from an existing RCA Analysis, all nodes appear and can be dragged from the Palette section as expected. | DE89734 |
Rounds Data Collection
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| The performance when uploading readings and marking Routes done has been improved. | F38995 |
| To improve usability, when you access the Rounds Data Collection Overview page, Routes are no longer automatically filtered based on settings in the Asset Hierarchy. Additionally, the Edit Filters button () has been removed from the Rounds Data Collection Overview page. | US321122 |
| To improve user experience, when you upload a large amount of data to the GE Digital APM database, the progress of the upload is displayed as a percentage. | US320799 |
| To ensure Route information is updated before you begin data collection for Routes that have been enabled for offline access, data is now synchronized with the GE Digital APM database both when you initially enable offline access and when you access the Rounds Data Collection Overview page. | US315644 |
| To improve usability, the page layout of the Rounds Data Collection module now switches between portrait and landscape modes when you rotate your device, regardless of the screen resolution of the device. This enables small screen devices, which use an adjusted page layout in portrait mode, to use the standard page layout in landscape mode. | US291178 |
|
To improve usability in areas where network connectivity is intermittent, you can now force the Rounds Data Collection module to behave as if your device is offline by selecting the Disable Network Connection check box in the following locations:
| US290533 |
| The next date for a Checkpoint is now updated when you mark the Route on which it appears done. | US290514 |
| To improve usability, in the page for a Route, in the Route Map pane, the Asset ID is now displayed across two lines of text to avoid truncation. | US283079 |
|
To improve usability, you can now filter Lubrication Requirements on a Route by the specific Lubricant needed. | US278464 |
) in the large screen page layout| Description | Tracking ID |
|---|---|
Previously, in the Rounds Data Collection Overview page, if you marked a Route done without first taking any readings, one of two issues occurred:
These issues have been resolved. | DE100699 |
Previously, while using a handheld device to collect data for a route, the following issues occurred:
| DE100680 |
| Previously, if you cleared the reading for the first Checkpoint on a Route after having closed and reopened that Route, that Checkpoint was removed from the Route Map pane until you closed and opened the Route again. This issue has been resolved. | DE99777 |
| Previously, if you navigated away from and back to the workspace for a Route, and then closed the workspace for the Route after marking it done, the Route History record for the Route was deleted. This issue has been resolved. | DE99181 |
| Previously, if you deleted readings while completing a Route, some readings could be deleted unintentionally. This issue has been resolved. | DE98984 |
| Previously, while disconnected from a network, in the workspace for a Route for which offline access was enabled, if you marked the Route done after entering a comment, and then closed the workspace, you could still access the Route from the Rounds Data Collection Overview page, take readings for it, and mark it done. This issue has been resolved. | DE97409 |
| Previously, on small screen devices, there was no indicator that the device was disconnected from a network. This issue has been resolved. Now, an indicator is present when the device is disconnected from a network. | DE95458 |
| Previously, deleted Recommendations reappeared in the Recommendations pane in a Route if you created a new Recommendation without first refreshing or closing and reopening the Rounds Data Collection Overview page. If you then saved a deleted recommendation in the Recommendations pane, it also reappeared in the Recommendations section in the Rounds Data Collection Overview page. These issues have been resolved. | DE94281 |
| Previously, if creating an Operator Rounds Recommendation in offline mode failed, multiple Operator Rounds Recommendation In Error records were created after you synchronized the Route. This issue has been resolved. Now, only one Operator Rounds Recommendation In Error record is created. | DE94304 |
| Previously, while disconnected from a network, if you took readings on multiple devices for Routes with large numbers of readings, and then attempted to simultaneously upload the data to the GE Digital APM database on those devices after reconnecting to a network, an error occurred. This issue has been resolved. | DE91520 |
| Previously, when you collected data offline for all checkpoints on a Route and then closed the Route without marking the Route done, the progress bar in the Rounds Data Collection Overview page erroneously displayed a value less than 100%. Additionally, if you then marked the Route done, the Route History section in the workspace for the Route in the Rounds Designer module displayed a value that was one fewer than the actual number of readings taken. This issue has been resolved. | DE90935 |
| Previously, in the Device Settings window, if you set the device settings by selecting the Use Default Settings check box, and then signed out of and back in to the GE Digital APM mobile application, the Use Default Settings check box did not remain selected, and the device settings were reverted to their previous state. This issue has been resolved. Additionally, in the Rounds Designer module, if an administrator sets the default device settings, the settings will take effect only after you have signed out of and back in to the GE Digital APM mobile application. | DE89212 |
| Previously, when you marked a Route done while offline and then went online, the Route disappeared from the device, as expected, and readings were uploaded to the server; however, if you went back offline before the sync interval was met, the device storage was not updated, and the Route appeared in the Due section despite not being due. This issue has been resolved. | DE89050 |
| Previously, when you collected data for all Checkpoints on a Route and then closed the workspace for the Route without marking the Route done, the Route's progress bar in the Rounds Data Collection Overview page was not at 100%. Additionally, if you marked the Route done, the Route History section in the workspace for the Route in the Rounds Designer module was incorrect. This issue has been resolved. | DE88747 |
| Previously, on a small screen device, the percentage of the Route that was complete did not appear above the progress bar in the Rounds Data Collection Overview page when you were online. This issue has been resolved. | DE88164 |
| Previously, on a mobile device, after you cleared Route data from local storage, Routes stored on your device resynchronized with the server, but, once the data was cleared, there was no indication that Routes were still synchronizing. As a result, if you went offline while the Routes were still synchronizing, you were unable to access any Routes that were not finished synchronizing. This issue has been resolved. Now, while Routes are synchronizing with the server, a spinner appears next to the Route names in the Due Items or Overdue Items section of the Rounds Data Collection Overview page, indicating that synchronization is in progress. | DE87172 |
| Previously, a child conditional Checkpoint with a parent conditional Checkpoint appeared in the Route Map pane even if the necessary condition for the child conditional Checkpoint to appear was not satisfied. This issue has been resolved. | DE86998 |
| Previously, in the Rounds Data Collection Overview page, if you were disconnected from a network, Routes for which offline access was enabled did not appear when they became due. This issue has been resolved. | DE86306 |
| Previously, on small screen devices, in the Rounds Data Collection Overview page, in the Assigned Routes section, you could not view the full contents of the Route ID column. This issue has been resolved. Now, the Route ID column has been lengthened, and you can scroll horizontally to view its full contents. | DE85257 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| Previously, if you navigated away from and back to the workspace for a Route, and then closed the workspace for the Route after marking it done, the Route History record for the Route was deleted. This issue has been resolved. | DE99181 |
| Previously, in the Rounds Data Collection Overview page, if you were disconnected from a network, Routes for which offline access was enabled did not appear when they became due. This issue has been resolved. | DE95420 |
Rounds Designer
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To improve user experience, in the Rounds Designer Overview page, in the Allowable Values section, you can no longer delete allowable values. | US325981 |
| To improve user experience, when you upload a large amount of data to the GE Digital APM database, the progress of the upload is displayed as a percentage. | US320799 |
| To improve stability, the Rounds Designer module now detects and attempts to resolve issues related to mismatched Checkpoints on a Route, as well as provides details on such Checkpoints to enable further action as needed. | US315644 |
| To enable more efficient navigation of health indicator sources, the Status and Do not automatically create health indicator columns have been removed from the Health Indicator Source Management workspace in the AHM Admin page. These two columns have been replaced by one new column, Included, which displays a check mark when a health indicator source is used to create health indicators and which appears empty when a source is not used to create health indicators. To facilitate this enhancement, a new field, Include as Health Indicator Source Field, has been added to the Health Indicator Mapping family. In addition, a new field, Include as Health Indicator Source, has replaced the Do Not Automatically Create Health Indicator field in the following families:
|
|
To improve the performance of uploading readings, the following fields have been removed from the ID Template in the Reading family:
| US295428 |
| Description | Tracking ID |
|---|---|
| Previously, in the workspace for a Route, if you repeatedly navigated between the Values and Route History sections, an error occurred. This issue has been resolved. | DE102022 |
|
Previously, if you added a Lubrication Requirement to a Route and then added a Checkpoint Template, the workspace for the Lubrication Requirement appeared, as opposed to the workspace for the Checkpoint Template. This issue has been resolved. | DE98780 |
| Previously, when loading records using the Route data loader, if you did not provide a specific load sequence for the Route records, when you imported records containing multiple conditional Checkpoints, and then opened the Route containing those conditional Checkpoints, the conditional Checkpoints did not appear in the same order in which they appeared in the data loader. This issue has been resolved. Now, conditional Checkpoints for which a load sequence has not been provided appear in a Route in the same order in which they appear in the data loader, as expected. | DE97625 |
| Previously, in the Rounds Readings data loader workbook, if you entered a numeric value in the Reading Value Character column and then completed a data load, a null value was loaded to the Rounds Reading record. If you tried to correct this value by reloading the workbook with the numeric value in the correct column, the value was not updated. This issue has been resolved. | DE94293 |
| Previously, when you attempted to import a Checkpoint with a related asset whose assigned site was Global via a Rounds Data Loader, an error occurred. This issue has been resolved. | DE94130 |
| Previously, when you imported a Lubrication Requirement template, an error occurred. This issue has been resolved. | DE93007 |
| Previously, in the workspace for a Route, if you selected a conditional Checkpoint in the pane and then attempted to add a new Checkpoint using a template, an error occurred. This issue has been resolved. | DE91821 |
Previously, when you attempted to apply a Template Group to a Route, if the site assigned to the Template Group differed from the site assigned to a Template within the Template Group, the page did not load. This issue has been resolved. Now, you can add a Template to a Template Group only if one of the following statements is true:
| DE89348 |
| Previously, if you added a Checkpoint to a Route and selected the associated Checkpoint node before saving the new Checkpoint, the page entered an indefinite loading state. This issue has been resolved. | DE85706 |
| Previously, in the Rounds Designer Overview page, in the Allowable Values section, if you modified the name of a category and selected Save, an error occurred. This issue has been resolved. Now, you can no longer modify the name or allowable values of a category. | DE83485 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Rounds Designer Overview page, in the Allowable Values section, if you modified the name of a category and selected Save, an error occurred. This issue has been resolved. Now, you can no longer modify the name or allowable values of a category. | DE97102 |
R Scripts
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| The R Scripts module now supports Machine Learning Server 9.2.1 in addition to R Server 8.0.0. To facilitate this enhancement, in the Connections page, the R Server Version drop-down list box has been added to enable you to select the version of your R Server. | US283973 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| The R Scripts module now supports Machine Learning Server 9.2.1 in addition to R Server 8.0.0. To facilitate this enhancement, in the Connections page, the R Server Version drop-down list box has been added to enable you to select the version of your R Server. | US314350 |
SAP and SAP PI UDLP V2.6.0
This topic provides a list of product changes released for this module on the dates listed below.
SAP and SAP PI - Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| The SAP Adapter now provides a Planned Work Adapter that enables you to plan maintenance work for assets. | US318099 |
| Description | Tracking ID |
|---|---|
| Previously, when using the Work Management adapter, after a confirmation record was created for an inspection, the Work Order Number field was not cleared from the Inspection record. Now, the Work Order Number field is cleared correctly. | DE105082 |
| Previously, the SAP PI adapter incorrectly populated the Last Date and Next Date fields when the adapter created a Work Order record. Now, the SAP PI adapter no longer populates these fields. | DE102158 |
| Previously, the documentation did not provide sufficient information about the ABAP package required to support migrating from V3.6 to V4.3 of GE Digital APM. Now the documentation correctly identifies the V3.6 ABAP package as 0.7, 360_600 Level 10. | DE101136 |
| Previously, Work History records associated with Technical Objects displayed incorrect Site data. Now, the Site data displays correctly. |
|
| When you attempted to save an updated Inspection record, the record failed to save and the following error message was displayed: Failed to save entity: "RFC_GET_STRUCTURE_DEFINITION" | DE90036 |
Schedule Logs
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| In the Description column of the Schedule Logs page, you can now view the ID of a scheduled Strategy Macro. | US290782 |
Search
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Now, when you perform a global search, the records belonging to the Equipment and Functional Location families appear at the top in the search results. | US313364 |
| Description | Tracking ID |
|---|---|
| Previously, when you logged in to GE Digital APM as a Polish user and performed an advanced search on a family, the IDs that appeared in the Record ID column did not contain links. This issue has been resolved. | DE85104 |
Single Sign-On
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Previously, if SSO was configured for GE Digital APM, and you attempted to access a page using the corresponding GE Digital APM URL that is generated by the Hyperlink Utility tool, the GE Digital APM login page appeared instead of the SSO login page. This issue has been resolved. | DE92791 |
SIS Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
|
The SIS Management module now uses the latest database version of the Exida Safety Equipment Reliability Handbook (SERH): version 2017.4.01. | US299935 |
| Description | Tracking ID |
|---|---|
|
Previously, if you created a Protective Instrument Loop record, and immediately tried to modify the record, an error message appeared. This issue has been resolved. | DE89049 |
|
Previously, when you accessed GE Digital APM on a mobile device, and then attempted to download a Proof Test Task, a blank window appeared. This issue has been resolved. Now, in this scenario, the Assign Template for Download window appears, and the template for Offline Proof Test Task is downloaded successfully. | DE89021 |
Sites
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can no longer create or update sites in the Sites page. You can use the Unified Asset Ingestion data loader to create new sites and populate the data of the newly created sites in GE Digital APM. | DE99526 |
SmartSignal
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can now add Chart Y Min and Chart Y Max values to an analytic template to override automatic Y-axis scaling in Analysis charts. | F42784 |
| You can now export an analytic template as a .zip file. | F40124 |
| You can now use correlation charts to exclude data from model training. Additionally, data points in correlation charts are now color coded based on the colors in the stripe and filter legend. | F34015 |
The following improvements have been to the tables in SmartSignal Maintenance to make it easier to detect which tag values have been modified in an analytic instance or model:
| F32280 |
| Administrative users can now grant a user view-only permission for SmartSignal analytics. To facilitate this enhancement, a new permission, View SmartSignal Analytic, has been added in the SmartSignal Mappings section in the page for modifying permission sets. | F28777 |
| Description | Tracking ID |
|---|---|
| The deployment process in the GE Digital APM Analytics module limits the ability to update analytic templates when deployments contain more than one APM asset. Therefore, when you create a new analytic instance using the deployment process in the GE Digital APM Analytics module, do not include more than one APM asset in your deployment. Note that if you create a deployment using multiple assets, when you modify your SmartSignal analytic template, any associated analytic instances will not remain in sync with the template, and you will need to deploy new instances to have instances that are synced with the template. | N/A |
| In the SmartSignal Maintenance module, if you have an analytic instance with a large amount of data, you may experience performance issues. To improve performance, use Google Chrome as your browser; you may also need to close other applications to increase available memory. | N/A |
Release Date: January 23, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you imported an analytic instance into GE Digital APM, if the APM asset associated with the analytic instance had an output tag with a time series link defined, that time series link value was not maintained in the output tag in the analytic instance. This issue has been resolved. Now, in this scenario, the time series link value is included as the source tag value in the analytic instance. | DE91623 |
State Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
In the State Assignments window, the following enhancements have been made:
| US287182 |
Strategy Macros
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| You can now schedule the family-level rules associated with the families to be executed at specified intervals. To facilitate this functionality, a new feature, Strategy Macros, has been added in Operations Manager. | US313705 |
System Requirements
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
Previously, while accessing the help content for the system requirements of SQL Server Analysis Services, the following issues were found in the Software Requirements section:
| DE101559 |
Teams
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
While assigning teams to a shift or a route, you can now access the details of a team in the Teams page and perform various operations, such as creating, modifying, or deleting a team. To facilitate this enhancement, a hyperlink has been added to the following windows for each team:
Note: This enhancement is applicable only to the Rounds and eLog modules. | US285276 |
| Description | Tracking ID |
|---|---|
Previously, in the eLog Administrator page, the following issues occurred:
These issues have been resolved. | DE92405 |
Tenant Preferences
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
You can now select which applications appear in the module navigation menu by selecting a module navigation profile. A new page, Module Navigation Menu, was added to Tenant Preferences to facilitate this change. The following navigation profiles are available:
| US304693 |
| Description | Tracking ID |
|---|---|
| When a navigation profile is selected, the applications that are not accessible to a user no longer appear in the module navigation menu. | US315324 |
Thickness Monitoring
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| Thickness Monitoring now supports TML Groups with linked child TML Groups. You can configure this feature in the TM Family Preferences. | US312372 |
| The time required to load the Analysis Overview page for an asset has been reduced. | US312357 |
| The Thickness Monitoring (TM) Equipment and Thickness Monitoring (TM) Functional Location Data Loaders have been enhanced to skip any blank cells when you create or update records using the data loaders. | US300470 |
| To enhance the data loading process for large amounts of data and to prevent the failure of data load batches that take longer than five minutes, the Thickness Measurement (TM) Equipment data loader and the Thickness Measurement (TM) Functional Location data loader have been enhanced. To facilitate this enhancement and to prevent timeouts, the TM Equipment Data Loader and the TM Functional Location Data loader now split large amounts of data into the following transaction scopes:
In addition to these default values, you can modify these transaction scopes if required. | US309806, DE98795 |
To prevent failure of TML batches that took longer than five minutes, the TML renewal functionality has been enhanced to perform the renewal job through a scheduler. Performing the job through a scheduler provides the following advantages:
| US310307 |
To prevent failure of TML batches that took longer than five minutes, the TML nominal measurement creation functionality has been enhanced to perform the renewal job through a scheduler. Performing the job through a scheduler provides the following advantages:
| US312370 |
| Description | Tracking ID |
|---|---|
| Previously, if the Asset Hierarchy was configured to use the Equipment Has Equipment relationship, the Asset Hierarchy navigation links could not differentiate between a parent Equipment and a child Equipment. This issue has been resolved. | DE103536 |
| Previously, when you attempted to send TML data to a DMS Go, DMS Go+, and DMS2 datalogger devices, the data was not sent to the device if the logged in user culture was set to any culture other than English (United States). This issue has been resolved. | DE94734 |
| Previously, in the Receive From section, if you received readings from the datalogger and then navigated away from the Receive From section, the readings were not retained. This issue has been resolved. | DE94438 |
| Previously, if the number format of the user account that is used to run the Meridium Device Service is different from the number format of the English (United States) culture, when you received thickness measurement data from a TM Datalogger, the measurement values were incorrect. This issue has been resolved. | DE92138 |
| Previously, when you performed any operation that created new records, such as renew TMLs, bulk analysis of TM assets, or other such operations, multiple scheduler jobs were created, which resulted in creation of duplicate records. This issue has been resolved. | DE88871 |
Previously, the allowable stress value for a Pressure Vessel component was populated incorrectly if you used the following combination of values::
This issue has been resolved. | DE87370 |
Release Date: January 25, 2019
| Description | Tracking ID |
|---|---|
| To enhance the data loading process for large amounts of data and to prevent the failure of data load batches that take longer than five minutes, the Thickness Measurement (TM) Equipment data loader and the Thickness Measurement (TM) Functional Location data loader have been enhanced. To facilitate this enhancement and to prevent timeouts, the TM Equipment Data Loader and the TM Functional Location Data loader now split large amounts of data into the following transaction scopes:
In addition to these default values, you can modify these transaction scopes if required. | US310233 |
Time Series Data
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance usability when retrieving time series data archived in S3 storage, queries can now run asynchronously. Asynchronous queries enable applications to continually poll the Time Series Data service to obtain the query results. This feature is available only in new Predix Time Series service schema; currently, it is not supported in AWS West. | F34716 |
| To enable users to permanently delete time series data, a new DELETE endpoint has been added. The endpoint enables users to free up storage space and reduce storage costs. This feature is available only in new Predix Time Series service schema; currently, it is not supported in AWS West. | F20644 |
Units of Measure and Conversions
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| A new destination Unit of Measure (UOM), Years (YR), has been added to the Months (MO) UOM to specify a conversion of time from months to years. | DE84965 |
Users and Permissions
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| If your tenant has multiple identity providers configured, you can now select an identity provider in a drop-down list box when adding users individually or in bulk. When adding a user, the domain of the email address provided must match what is configured for the selected identity provider. | US336292 |
A new window for assigning assets has been implemented. This update provides improvements to overall usability when assigning assets and permissions, including the following:
| US332524 |
A tenant can now be configured with multiple identity providers, each restricted by a set of email domains. As a result of this enhancement:
| US332523 |
In the User Management page, the following permissions have been added for the Mechanical Integrity module. When these permissions are assigned to Security Users, the users are granted privileges to manage the states for inspection recommendations.
| US307829 |