APM Release Notes for the Second Quarter of 2019
Activate Licenses
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you activated a license, you had to manually switch the data source to which you applied the license to offline, and then to online. Now, you do not have to perform this action. After activating the license, you must log off from GE Digital APM and log in again. | DE109678 |
Alerts
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| To optimize the analysis of an issue with an asset, in the alerts grid and alerts inbox, you can now select the asset and thereby, only the alerts associated with the asset appear. | F44283 |
| Description | Tracking ID |
|---|---|
| Previously, a few of the alerts were missing from the alerts grid. However, you could access the details of the alerts using the URL of the alert. This issue has been resolved. | DE109706 |
| Previously, even though no filter was applied, only consumable alerts appeared in the alerts grid. This issue has been resolved. Now, if no filter is applied, all the alerts appear in the alerts grid. | DE109443 |
| Previously, two users could claim the same alert. If one of the users updates the alert, it overwrites the data of the alert that was updated by the other user. This issue has been resolved. | DE101223 |
Release Date: April 22, 2019
| Description | Tracking ID |
|---|---|
| The Asset Customer Name column is now available for grouping in an alerts grid. | DE105263 |
| Description | Tracking ID |
|---|---|
| Previously, for SmartSignal and latched alerts, when you attempted to sort or filter the First Occurrence and Last Occurrence columns in an alerts grid, the columns were not sorted or filtered based on the criteria specified. This issue has been resolved. | DE79592 |
Analysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| You can now plot up to 60 tags on a single SmartSignal card in the analysis view. | F45091 |
| You can now view the diagnostics markers on the residual charts if only the residual chart is plotted for a tag, and the actual and estimates charts are not plotted for the tag. | F43839 |
| In the Analysis view, in addition to the name, alias, and description of the contributing or noncontributing tag, you can now view the name of the asset and the name of the alert associated with the tag. | F43838 |
| For SmartSignal charts, you can now configure your preferred mode of visualization of data plotting as either date and time mode or points mode. To facilitate this enhancement, in the SmartSignal Chart and Marker Settings section of the My Preferences page, the Plotting Preferences section has been added. | F43836 |
| You can now plot a Time-Series (Scatter) chart in Analysis templates. This new chart type has the same functionality as that of the Time-Series (Line) chart. | F43750 |
| You can now view the name of the parent asset in addition to the name of the asset in context when you access the analysis information related to an Alert. If the asset belongs to a complex hierarchy, you can also open the Context Browser in the view mode. | F43740 |
| You can now define the diagnostics markers in your SmartSignal Analytics and show them on the Analysis charts when you view the data associated with the analytics tags. You can also point to the diagnostics markers in the charts to view the details of the diagnostics events. | F43723 |
| The performance in loading Analysis templates from Alerts and Cases has now been improved. | F43722 |
| You can now use infinite scrolling instead of pagination in the data table view in an Analysis template. | F42051 |
| You can now zoom in on the bar charts in an EBQ Analysis template. | F42051 |
| You can now set the y-axis limits on Parallel Axis and Spider charts. | F42051 |
| You can now search for an element in any drop-down list box of an Analysis that has more than 10 elements. | F42051 |
| You can now add an asset to the analysis view from an Alert to allow you to use the data from additional assets in your analysis of the Alert. | F42051 |
| You can now view SmartSignal Cycle Watch Events in an Analysis and plot analytics tags based on Event Frames. | F41913 |
| Description | Tracking ID |
|---|---|
| Previously, with the cross-hair mode enabled on an Analysis template, if you added a new chart to the Analysis template, the cross-hair information did not appear on the new chart, and the cross-hair markers did not appear on the existing charts. This issue has been resolved. | DE99126 |
| Description | Tracking ID |
|---|---|
| If you point to a diagnostic marker on a SmartSignal chart, no information appears. To exit the mode and view the information about the marker, refresh the charts. | DE101633 |
| 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 |
| When you delete tags on a Time-Series chart after you have plotted pin markers, the deleted tags appear in the marker data table. To prevent this issue, delete the tags, and then set the pins on the charts. | DE95436 |
| While modifying the Time-Series chart in multiple y-axes mode, if you select Apply, your changes are neither applied nor visible in the chart settings. To prevent this issue, select Cancel, and then create the template for an ad hoc view. Alternatively, you can save the template, and then modify the existing template as needed. | DE93811 |
| You must now use Google Chrome to add multiple charts to a SmartSignal card. Note: Other browsers, including Internet Explorer, do not support adding multiple charts to a single SmartSignal card.
| None |
Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
|
Using the common analytics framework, you can now generate multiple alerts at the same time to analytics that are deployed on the Predix Insights and Predix Framework runtime environments. You can also associate one or more alert templates with an analytic using the Output Events section.
Note: To associate an alert template with an analytic and to generate multiple alerts, you must enable the template in the I/O Mapping page. | US355437 |
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, you could not access Asset Filters through the module navigation menu if you selected a navigation profile from the Module Navigation section under Tenant Preferences. This issue has been resolved. | DE109144 |
APM Connect
This topic provides a list of product changes included in this patch.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| APM Connect now supports UDLP V2.6.1. The data loader framework in UDLP V2.6.1 is compatible with GE Digital APM V4.3.0.7.5. | US354669 |
| The automatic data loaders are now supported in APM Now. Using these data loaders, you can automatically import data into GE Digital APM. | US354406 |
| The SAP Equipment and Functional Location technical characteristics are now supported for multiple language data extraction. | US351143 |
| Description | Tracking ID |
|---|---|
| Previously, when using automatic data loaders, if multiple records were imported at the same time, sometimes, a few records were skipped. This issue has been resolved. | DE111514 |
| Previously, Apache Karaf crashed in the cloud environment because of the way the APM Connect data loader job handled the conversion of the .xlsx file to a .csv file. This issue has been resolved. Now, the .xlsx file is converted to a .csv file before it is sent to Apache Karaf. | DE111512 |
| Previously, when using automatic data loaders, an error message appeared although the records were imported successfully. This issue has been resolved. | DE111339 |
| Previously, the Planned Work and Work Management Interface integration did not allow filtering by Maintenance Plant. This has been resolved. You can now use Maintenance Plant as a filter for Planned Work and Work Management Interface. | DE110851 |
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, Site records created using the Unified Asset Ingestion Data Loader did not synchronize with the Meridium database for the entire system if you did not refresh the Intermediate Repository database. Now, the Unified Asset Ingestion Data Loader synchronizes with the Meridium database correctly even if you do not refresh the Intermediate Repository database. | DE109166 |
APM Data Extraction
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you tried to fetch navigation (relationship) property data using a property request call, the service returned an HTTP 404 error. This issue has been resolved. | DE109958 |
Asset Health Manager
This topic provides a list of product changes included in this patch.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Performance in the Risks section of the Health Summary page has been significantly improved. | US338922 |
| Description | Tracking ID |
|---|---|
| Previously, in the <Asset Name> workspace, links for Asset Health Manager did not appear. Additionally, when you accessed the Health Summary page, the page loaded slowly, and error messages appeared. This issue has been resolved. | DE108371 |
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, because time stamp values for health indicator readings were truncated, health indicator readings were sometimes duplicated, and sometimes health indicators erroneously appeared to be out of sync. This issue has been resolved. | DE106890 |
Previously, in the Health Summary page, sometimes a No Status icon ( ) erroneously appeared next to health indicators that had a valid status. This issue has been resolved. | DE106606 |
| Previously, if you specified that you wanted to store zero readings in the GE Digital APM database, the PDI service stored a reading and then deleted it, which caused performance degradation. This issue has been resolved. Now, the PDI service no longer adds and deletes extraneous readings, and, as a result, database performance is significantly improved. | DE107755 |
Asset Hierarchy
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Group section of the Asset Finder window, when you attempted to add a group of assets, an error occurred. This issue has been resolved. | DE107347 |
Asset Strategy Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Risks and Actions page, if you attempted to consolidate RCM or FMEA actions, the process timed out. | DE108490 |
Calibration Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, when CalibDeviceMappingsUpgradeUtility was run to upgrade to 4.3.0.0.0 or later for replacing the old Device Mapping IDs with the new Device Mapping IDs on all the existing templates, an error occurred. Due to this, you could not perform calibration on the old templates using Fluke calibrator. This issue has been resolved. Note: The upgrade was required only if you wanted to use the Fluke documenting process calibrator. | DE109864 |
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| Previously, in a calibrator, if you entered the name of a user who was not a member of the MI Calibration Administrator or MI Calibration User Security Group, and tried to receive data from a calibrator, although you received the data, instead of an error message, a blank screen appeared. This issue has been resolved. | DE108620 |
| Previously, after receiving multiple records from a calibrator, if you did not save all the records that were received, the values for the saved records were always picked from the first record in the list. This issue has been resolved. | DE108612 |
| Previously, if you sent data to a Fluke calibrator, and performed a calibration using a Calibration Template, Analog or Calibration Template, Discrete record with the input UOM set to Degrees Celsius (DEG C), an error occurred. This issue has been resolved. | DE108500 |
Cases
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
For collaborative analysis of a case, you can now easily share the case with other users or user groups by sending an email notification with the link to the case. To facilitate this enhancement, the Notify User button ( ) has been added to the details section of a case. | F44281 |
| For a better analysis of a case, you can now add an analysis template to the case so that you can save it as one of the data points. | F44077 |
| Description | Tracking ID |
|---|---|
| Previously, in a cases grid, when you attempted to change the cases filter set, the loading symbol appeared, however, the list of cases for the selected filter set did not appear in the grid. This issue has been resolved. | DE109676 |
| Previously, when you filtered the cases grid by a case, the filtered list contained duplicate records. This issue has been resolved. | DE108723 |
| Previously, in a cases grid, the grouped column selection persisted until a first-time user grouped the columns in a cases grid for one of the cases filters set. This issue has been resolved. | DE107402 |
| Previously, for a first-time user, the cases did not appear in the cases grid even though the GE Digital APM application indicated that the cases were being loaded. This issue has been resolved. | DE107396 |
| Previously, if a note was added to a case, the Timeline view of the case did not contain any information about the note being added to the case. This issue has been resolved. | DE103410 |
| Previously, in a cases grid, the Asset Alias column appeared blank. This issue has been resolved. | DE100785 |
Release Date: April 22, 2019
| Description | Tracking ID |
|---|---|
| You can now group columns in a cases grid to organize data for easy access. | F34245 |
| Description | Tracking ID |
|---|---|
| For security reasons, you cannot share a case report from the GovCloud environment. | US337829 |
| You cannot sort grouped columns in a cases grid. | NA |
Catalog
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, after you upgraded an Oracle data source, certain custom folders did not appear in the catalog under . This issue has been resolved. | DE106796 |
Compliance Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you configured the module navigation menu in the Tenant Preferences page, the Compliance Management module did not appear in the module navigation menu, even if you used a navigation profile that included APM modules. This issue has been resolved. Now, the Compliance Management module appears if you select a navigation profile that includes APM modules. | DE108241 |
Data Loaders UDLP V2.7.0
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, in a cloud environment, when you tried to load a .zip file containing .csv files using the Data Loader interface, the load intermittently failed with the message access denied. Now, the files load without errors. | DE109151 |
Failure Modes and Effects Analysis (FMEA)
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, the user experienced database errors when using FMEA data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders. | DE109688 |
Family Policies
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved. | DE111238 |
| Previously, when you attempted to modify a record that triggered an After Update family policy containing a Baseline Rule node, and if the baseline rule configured for the Baseline Rule node updated the same record that triggered the policy, a time-out error occurred and the record was not modified. This issue has been resolved. | DE110458 |
| Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved. | DE110279 |
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels. | US347947 |
| Description | Tracking ID |
|---|---|
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
|
|
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved. | US341549 |
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
| DE107317 |
| Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value which is same as the default value of the corresponding field, the execution of the policy failed, and an error message appeared in the Node Execution Details window for the node, indicating that the index size is incorrect. This issue has been resolved. | DE106599 |
| Previously, in the Properties window for a Create Recommendation node, in the Create Work Request section, if you selected Yes, the execution of the policy failed, and no work request was created in the configured Enterprise Asset Management (EAM) system for the new Policy Recommendation record. This issue has been resolved. | DE99104 |
Foundation
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| You can now continue to work on a module even if a message stating that your session has expired appears erroneously. To facilitate this enhancement, the Cancel button has been added to the window that contains the message so that you can close the window. | US346689 |
GE Dashboards
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
The following enhancements have been made to the Generic Graph Widget:
| F45365 |
Release Date: May 23, 2019
| Description | Tracking ID |
|---|---|
| The Save As New Dashboard feature enables you to make a complete copy of a dashboard, including the cards, widgets, tags, tag expressions, availability, and metadata of the original dashboard. Only the permissions are not copied; the copy is created with default permissions. Use the copy as the basis for modifications that provide new dashboard capabilities. You can create a copy of any dashboard (with the exception of General Dashboards), even those you do not have permission to modify. | US321194 |
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: June 28, 2019
| Description | Tracking ID |
|---|---|
|
You can now create or regenerate a Performance Record even if any of the following conditions are met:
In addition, if any of these conditions are met, a warning message now appears when you create or regenerate a Performance Record. | DE111165 |
| In the GAA Wind Edit Events page and the Events workspace in the Sub Group Summary page, the Actual Production (MWh) column has now been added. You can modify the value in this column. In addition, you can now modify the value in the Error Code column. | DE111164 |
| The start time and the end time of the month for which a Performance Record is created are now considered in the time zone of the associated Sub Group, instead of the Coordinated Universal Time (UTC). | DE111345 |
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| You can now generate or regenerate a Performance Record and a Performance Report for any month. | DE106610 |
| You can now create or regenerate a Performance Record even if the IU time percentage for the associated Events exceeds 2%. When you attempt to create or regenerate such a Performance Record, however, a warning message appears, stating that the IU time percentage for the associated Events exceeds 2%. | DE106297 |
Graphs
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, hyperlinks in a heat map did not work as expected. This issue has been resolved. | DE106778 |
Inspection Management
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| A new Human Resource role, Contract Inspector, is now available. A Contract Inspector can modify the Inspection Document Status field in Inspection records to Pending Approval without being the user defined in the Inspection Report Owner field if they are a Team Member in the associated Inspection record. | US346807 |
| Using the Inspection Management (IM) Assets and Inspection Management (IM) Functional Location data loaders, a Contract Inspector who is a Team Member in the associated Inspection record can now modify the Status field to Pending Approval without being the user defined in the Inspection Report Owner field. | US346807 |
| If you are using Status to manage your Inspection Recommendation records and you are a Team Member in the associated Inspection record, you can now transition the Inspection Recommendation to the Pending Review status without being the user defined in the Author field. | US346807 |
| Previously, the Inspection Lock field was disabled unless you were the Inspection Report Owner. This field is now enabled if you are a Team Member in the associated Inspection record. | US346807 |
Policy Designer
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved. | DE111238 |
| Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved. | DE110279 |
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels. | US347947 |
| Description | Tracking ID |
|---|---|
Previously, if you copied and renamed an Input node of the policy model, and then saved the policy, the following issues occurred until you reloaded the policy:
| DE109329 |
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
|
|
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved. | US341549 |
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
| DE107317 |
| Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value which is same as the default value of the corresponding field, the execution of the policy failed, and an error message appeared in the Node Execution Details window for the node, indicating that the index size is incorrect. This issue has been resolved. | DE106599 |
| Previously, in the Properties window for a Create Recommendation node, in the Create Work Request section, if you selected Yes, the execution of the policy failed, and no work request was created in the configured Enterprise Asset Management (EAM) system for the new Policy Recommendation record. This issue has been resolved. | DE99104 |
Reliability Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Previously, in System Reliability, you could not run a simulation for a System Analysis with frequent failures in risks or with a value in the Last Failure field. An error message appeared, stating that the p parameter must contain a value between zero and one. This issue has been resolved. | DE110846 |
Release Date: May 29, 2018
| Description | Tracking ID |
|---|---|
| Previously, in the Failure Probability workspace, if you selected Future Probability and then entered a value in the Set Future Probability window, the value in the Future Failure Probability column was not properly updated. | DE109848 |
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, when running a simulation on a complex analysis with a large number of buffer components in System Reliability, the simulation did not complete. This issue has been resolved. | DE106782 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, the apply template builder took a long time to load when the template was complex. This issue has been resolved. Now, when creating an analysis from a template, the Apply Template Builder window loads more quickly. | DE109690 |
| Previously, the user experienced database errors when using RCM data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders. | DE109688 |
Risk Based Inspection
This topic provides a list of product changes released for this module on the dates listed below.
RBI 580
Release Date: June 7, 2019
| Note | Tracking ID(s) |
|---|---|
| Previously, in the Criticality Consequence Evaluation datasheet, two required fields for Heat Exchanger Bundles, Flammable Leak Type and Toxic Leak Type, did not have the Not Applicable (N/A) option in their respective drop-down list boxes. This issue has been resolved. Additionally, the following validation changes have been made:
| DE109171 |
RBI 581
Release Date: June 7, 2019
| Note | Tracking ID(s) |
|---|---|
| Previously, you could not create a Quantitative (581) analysis if the logged in user culture was Russian. This issue has been resolved. | DE109168 |
Root Cause Anlysis
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: May 29, 2018
| Description | Tracking ID |
|---|---|
| Previously, when you created an RCA for a Production Event from the Production Loss Analysis (PLA) module, in the Analysis Summary workspace, in the Linked Assets section, the Causing Asset associated with the Production Event did not appear in the Record ID column. | DE109585 |
Rounds Data Collection
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Previously, while using the GE Digital APM mobile application to collect data, you could not scan bar codes longer than 11 characters. This issue has been resolved. Now, you can scan bar codes with a length of up to 20 characters. | DE110128 |
Release Date: May 24, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the condition of a Checkpoint template, you could not enter a value in the Allowable Values or Select Value fields unless allowable values were defined. | DE108709 |
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| Previously, while disconnected from a network, if you created a recommendation for a Route, the time stamp of the recommendation displayed the time at which your device reconnected to a network, not the time at which the recommendation was created. | DE108482 |
| Previously, if you created an Operator Rounds Recommendation record without the Create Work Request? check box selected, and then selected that check box later when updating the recommendation, the work request was entered into your SAP system, but the recommendation was not updated with the data of the work request. | DE108362 |
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, when attempting to create an Operator Rounds Recommendation, if you selected the Create EAM Work Request? check box prior to saving the recommendation, an error occurred, and the recommendation record would not be created. This issue has been resolved. | DE105520 |
Rounds Designer
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 7, 2019
| Description | Tracking ID |
|---|---|
| Previously, in the condition of a Checkpoint template, you could not enter a value in the Allowable Values or Select Value fields unless allowable values were defined. | DE108709 |
Release Date: May 10, 2019
| Description | Tracking ID |
|---|---|
| Previously, if you created a Route using the Rounds Route Data Loader, the Route sequence did not load as expected. | DE108351 |
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
| Previously, if you attempted to use a data loader to add a Checkpoint to a Route, the sequence of existing Checkpoints on the Route was unintentionally modified. | DE106752 |
| Previously, loading a small number of records using the Rounds Routes Data Loader occasionally resulted in timeout errors. | DE106749 |
| Previously, if you attempted to move a Checkpoint node by dragging and dropping it into a header, an error occurred. | DE106403 |
SAP and SAP PI UDLP V2.7.0
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Previously, GE Digital APM created placeholder records for assets that did not exist when a Work History record was loaded. Now, the system does not create the placeholder records, but logs such records as 'Work History records need to be reprocessed'. | US347758 |
| Previously, Maintenance Plan records without Task Lists or Operation Objects were not discontinued by the Work Management Adapter. Now, the adapter correctly discontinues the Maintenance Plan records. | DE105578 |
| Previously, Inspection Task records with long text that exceeded 1,000 characters created long text in SAP with invalid characters in the format field. Now, the format field contains valid characters. | DE105547 |
| Previously, the system incorrectly mapped MI_REC_TARGE_COMPL_DATE_DT entity to Target Completion Date in SAP. This resulted in failed creation of Notification records. Now, the system maps the MI_REC_TARGE_COMPL_DATE_DT entity to the correct date, resulting in the successful creation of a Notification record. | DE105459 |
| Previously, SAP PI source files were not deleted from the shared folder. Now, the system deletes these files. | DE79645 |
Schedule Logs
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
Previously, a policy was not executed as per schedule until you updated the policy, if the following changes had been made to the GE Digital APM database that contained the policy:
| DE102150 |
SmartSignal
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| You can now verify your input tag mapping health before deploying an analytic instance. | F44075 |
| You can now access the SmartSignal analytic template and GE Digital APM asset that are associated with an analytic instance from the SmartSignal Maintenance module. | F43875 |
| You can now configure custom chart markers for diagnostic rules and tag rules from the analytic template editor. | F43802 |
| You can now view the name of the user who has locked an analytic template or analytic instance. |
|
| You can now have more control over the use of the automatic data filtering while rebuilding models for an analytic instance. | F42235 |
| A new function has been added to support standard deviation based on the mode. | F40084 |
| You can now clean your analytic instance training data to reduce its disk space usage and to improve the performance during addition model maintenance. | F28782 |
| You can now configure the maximum carry forward duration for the SmartSignal tenant. | F22781 |
Thickness Monitoring
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: April 18, 2019
| Description | Tracking ID |
|---|---|
Previously, if you used the TM Equipment or TM Functional Location data loaders to load data that consisted only of measurements, the Analysis Required check box in the TML Corrosion Analysis datasheet was not selected, and the Calculate button ( ) did not turn orange. If you tried to calculate the analysis, the newly loaded measurements were not included in the calculation. This issue has been resolved. Now, when you load measurements, the Analysis Required check box is selected, and the Calculate button () turns orange, indicating the analysis is ready to be calculated. When you calculate the analysis, the newly loaded measurements are included in the calculation. Also, the affected assets are available in the Assets Requiring a Calculation section of the Thickness Monitoring Overview page, ready for bulk calculation. | DE106600 |
Time Series Data
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: June 28, 2019
| Description | Tracking ID |
|---|---|
| Queries now support up to 100 tags in the Time Series Data Retrieval Service v4 and v5 APIs and the v2/time_series/delete endpoint. Previously, the maximum number of tags in a single query was 40. Note: The Time Series Data Retrieval Service v2 and v3 APIs still support a maximum of only 40 tags. | US341163 |