V4.4.0.0.0
Action Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To improve performance, the Action Management Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh ( ) to update the page. | US379897 |
| To improve usability, in the Action Management page, in the Strategy Actions section, the Interval and Interval Units columns have been added. | US362720 |
| You can now view the Active Work Order information for Actions in Action Management. | US352943 |
| You can now view the Execution (Work) History for Actions in Asset Strategy Management and Action Management. | US352942 |
| Description | Tracking ID |
|---|---|
| Previously, when you created a notification from a General Recommendation, the Work Request Reference field was not populated even if the Create EAM Notification? check box was selected. This issue has been resolved. | DE122114 |
| Previously, in the General Recommendation family, the Case ID hyperlink did not route you to the specific case as expected. This issue has been resolved. | DE120347 |
APM Connect
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in APM Now, certain EAM jobs were not successfully run??and the status of the jobs appeared as In Progress in the Status and Log column since the name??of the latest log file was not found.??This issue has been resolved. | DE129039 |
| Previously, when performing an extraction job to update WMI, Work History, or Technical Characteristic records, if you changed an SAP data attribute to NULL, the corresponding field in GE Digital APM was not updated. This issue has been resolved. | DE111371 |
| Description | Tracking ID |
|---|---|
| When you extract SAP characteristics to create Technical Characteristic records in GE Digital APM, single-value date and time characteristic values are not populated. | DE131202 |
| Description | Tracking ID |
|---|---|
| The Tags to Assets Relationship data loader is no longer available in GE Digital APM. | US400538 |
APM Mobile Application
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, individual reading was lost when changing the filter settings for APM Mobile. This issue has been resolved. Now, you can manage better reading and upload workflow. Additionally, messaging and logging have been enhanced around the reading upload process. | DE128269 |
| Description | Tracking ID |
|---|---|
| When using the Safari browser on iOS 13 mobile devices to access GE Digital APM, you may experience degraded performance. | DE129229 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now apply an Asset Strategy Template while creating one or many Asset Strategies from Asset Criticality Analysis. | US388608 |
| You can now send criticality updates to SAP in batches instead of updating individual assets. | US382019 |
| To improve performance, criticality values for only the assets that have new or modified values are sent to SAP. | US381407 |
| Asset Criticality Analysis for SAP is now supported in GE Digital APM. You can now update the ABC Indicator field in an Equipment or Functional Location in SAP with the Asset Criticality value from a Criticality Assessment in Asset Criticality Analysis. | US381294 |
| You can now send a maximum of 5000 assets to SAP. | US380173 |
| To improve performance, the Asset Criticality Analysis Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US379897 |
| You can now view revisions of a criticality assessment for a given asset in Asset Criticality Analysis. | US313016 |
| You can now view the criticality value for all the assets in an analysis. | US309602 |
| In Asset Criticality Analysis, you can now apply the assessment of an asset in an analysis to other assets within the same analysis. | US300483 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to send criticality values in a batch to SAP, only errors were logged with the success and failure count of the assets. This issue has been resolved. Now, you can view the results of the criticality values that are successfully sent to SAP. | US381408 |
| Previously, when you accessed the ACA Overview page, the data took longer than expected to load. This issue has been resolved. | DE124940 |
| Previously, even though the number of team members associated with an Asset Criticality Analysis (ACA) was more than 20, you could view a maximum of 20 team members in the Team Members section until you added a team member to the ACA team. This issue has been resolved. | DE122640 |
| Previously, when multiple send to SAP jobs were running, the analysis did not track the correct job. This issue has been resolved. | DE121671 |
| Previously, if you attempted to import an Asset Criticality Analysis record for an asset that did not exist in GE Digital APM, an incorrect error message appeared in the error log. This issue has been resolved. Now, an appropriate error message appears, indicating that the asset does not exist in GE Digital APM. | DE120766 |
| Previously, if you changed the state of an Asset Criticality Analysis, if you modified a value in the Analysis Definition section, and then attempted to save the datasheet, an error occurred. This issue has been resolved. | DE120765 |
| Previously, when a criticality mapping was linked to an EAM, if you attempted to send the criticality indicator to an EAM system other than the target EAM system, an error occurred. This issue occurred only if you had multiple EAM systems. This issue has been resolved. Now, an appropriate error message appears. | DE115402 |
| Previously, when you saved a new analysis, duplicate requests were created. This issue has been resolved. | DE108892 |
| Description | Tracking ID |
|---|---|
For the Asset Criticality Analysis and Asset Criticality Analysis System families, the following fields are no longer available:
| US274720 |
Asset Health Manager (AHM)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| In the Risks section of the Health Summary page, performance has been significantly improved. | US393789 |
To improve performance, the Asset Health Manager Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh ( ) to update the page. | US379915 |
| The OT Connect Source Tags can now be used to update Health Indicators and the Health Indicator Trend Chart from your process historian. A Health Indicator Mapping for the Content Map (MI_CONTENT_MAP) family supports the OT Connect Source Tag (MI_SOURCE_TAG) family. |
|
| Description | Tracking ID |
|---|---|
| Previously, the system allowed the creation of duplicate health indicators for a single source and asset. If multiple instances of the Health Service were running, the system sometimes created multiple health indicators when a source was added or modified. This issue has been resolved. The upgrade removes duplicate health indicators and health indicators that do not have health indicator mapping, asset, or source. | DE126108 |
| Previously, when you implemented an action as a health indicator related to a risk, the health indicator did not appear in the Risks section of the Health Summary page. This issue has been resolved. | DE124614 |
| Previously, when you accessed the Health Indicator Source Trend page from Rounds Designer and modified the date range in the date filter, the date range changes were not applied. This issue has been resolved. | DE117098 |
| Previously, when two source mappings for the same health indicator source family had different settings for the Include as Health Indicator Source Field, duplicate entries appeared in the Health Indicator Source Management workspace, and a warning message did not appear. This issue has been resolved. Now, in this scenario, a warning message appears indicating that the source mappings are inconsistent. | DE105772 |
| Description | Tracking ID |
|---|---|
| Configuring the Meridium Notification service is no longer needed as part of the deployment workflow of Asset Health Manager. | US357092 |
Asset Hierarchy
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve the performance of GE Digital APM, the data of the <Asset Name> workspace is no longer refreshed automatically when you navigate away from the workspace, and then access the data in the <Asset Name> workspace. However, you can now manually refresh the data of the <Asset Name> workspace. To facilitate this enhancement, a new button, Refresh (), has been added to the <Asset Name> workspace. | US397034 |
To improve usability, the following enhancements have been made to the Asset Hierarchy panel:
| US394566 |
, has been added to the Asset Hierarchy panel to collapse the panel.
, has been added to the <Asset Name> workspace to expand the panel.| Description | Tracking ID |
|---|---|
| Previously, you could not create an Asset Hierarchy for an equipment or a functional location that contained multiple parent equipment or functional locations, and no error message appeared to indicate the same. Now, in this scenario, an error message appears indicating that there are multiple parent-level??equipment or functional locations for the equipment or functional location and the Asset Hierarchy??cannot??be created. | DE132361 |
| Previously, when you created an Asset Group based on a query, you could add a maximum of 25 assets to the group. This limitation has been removed. Now, you can add all the assets that are part of a query result. | DE124562 |
| Previously, when the name of an asset contained a long string, the asset name was truncated in GE Digital APM.??This issue has been resolved. Note: In the Asset Hierarchy panel, you can view the complete name of such assets in a tooltip only when you hover over the asset name. | DE119251 |
Asset Strategy Implementation (ASI)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve performance, specified field level rules use value helper instead of??picklist. Note: You can also manually enter a valid value. | US386736 |
| To improve performance, the Asset Strategy Implementation Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US379897 |
| Performance when loading the counts on the tabs in the ASI Overview page has been improved. | US343623 |
| Description | Tracking ID |
|---|---|
| Previously, accessing all the action records in the Manage Actions and Linked Actions sections took longer than expected. This issue has been resolved. | DE123023 |
| Previously, in the Asset Strategy Implementation module, the Get Actions for CMMS System query, which is used to add actions in the Manage Actions section was timing out. This issue has been resolved. | DE122025 |
| Previously, in the Asset Strategy Implementation module, if you made any changes to a child work management item and saved the record, the icon for its parent work management item was not getting refreshed. This issue has been resolved. | DE121845 |
| Previously, when the Work Management Item (WMI) update was in progress, you could navigate away from the current page because the page was not locked. This issue has been resolved. | DE121074 |
| Previously, in Asset Strategy Implementation, within the Japanese culture, the long text was not formatted correctly and could not be opened in SAP. This issue has been resolved. | DE116441 |
Asset Strategy Management (ASM)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
You can now perform the following actions in the Asset Strategies section of the Asset Strategy Management page:
| US399019 |
| You can now view the default asset information in the datasheet while creating a General Recommendation from the Recommendation Side Panel in Asset Strategy Management and Asset Health Manager. | US382839 |
| To improve performance, the Asset Strategy Management Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US379897 |
| When you use the Import option from the SAP feature, you can now exclude Operations while importing Maintenance Plans, Maintenance Items, and Task Lists, thus improving performance. | US371630 |
| You can now configure the text of probability and consequence through system code in risk matrix, using Consequence Label and Probability Label that are now added to the system code table. | US368150 |
| You can now implement an action as an EAM Maintenance Plan without sending an EAM Work Request. To facilitate this enhancement, sending an EAM Work Request has been made optional. | US362758 |
| You can now view the Active Work Order information for Actions in ASM. | US352943 |
| You can now view the Execution (Work) History for Actions in Asset Strategy Management and Action Management. | US352942 |
| When loading the counts on the tabs in the ASM Overview page, performance has been improved. | US343623 |
| Description | Tracking ID |
|---|---|
| Previously, in Asset Strategy Search indexing, only a few families were excluded in the Strategy modules. This issue has been resolved. Now, all the sub-families in the Strategy modules are excluded. | US383087 |
| Previously, in the Strategy data loaders, the columns supporting Boolean values incorrectly contained Y or N as field values. This issue has been resolved. Now, the values in the columns appear as TRUE or FALSE. | US363422 |
| Previously, you could not set a value for an additional parameter in the EAM Plan Import initial asset query (that is, Public\Meridium\Modules\Asset Strategy Management\Management\Queries\Locate Assets By EAM System For Import). This issue has been resolved. Now, you can add an additional parameter to the EAM Plan Import initial asset query and set its value through the parameter prompt when importing. | US363249 |
| Previously, you could not set a value for an additional parameter in the EAM Plan Import asset query (that is, Public\Meridium\Modules\Asset Strategy Management\Management\Queries\All_Assets_For_Import). This issue has been resolved. Now, you can add an additional parameter to the EAM Plan Import asset query and set its value through the parameter prompt when importing. | US362755 |
| Previously, when you accessed the Asset Strategy Approval Report, you were prompted to select a Strategy ID. This issue has been resolved. | US310320 |
| Previously, when creating a general recommendation, if the update notification was disabled, multiple notifications were sent to EAM system, and an error occurred. This issue has been resolved. | DE126319 |
Previously, an error occurred in Risk Analysis in the following scenarios:
These issues have been resolved. | DE126188 |
| Previously, in the Risk Analysis workspace, data appeared in the Financial Risk graph even when the Financial category was not associated with the Risk Matrix. This issue has been resolved. | DE126099 |
| Previously, when you copied an Asset Strategy Template, the Action ID associated with the template appeared in the new template instead of a new Action ID. This issue has been resolved. | DE125256 |
| Previously, if a Risk Matrix was not associated with a financial Risk Category, when you accessed the risk analysis for a strategy or a template associated with the Risk Matrix, you could not perform any action in the Risk Analysis workspace. This issue has been resolved. | DE123509 |
| Previously, state control was enabled when update SAP job was run for an analysis. This issue has been resolved. | DE121672 |
| Previously, after applying a template as a master to an asset or functional location, if you made changes to the probability and consequence values for a given risk category without affecting its overall risk rank, the changes were not reflected in the controlled strategy. This issue has been resolved. | DE121492 |
| Previously, if your culture setting had a culture other than English, when you specified filter criteria to filter the system strategies by states in the Review Strategy workspace, the strategies were incorrectly filtered. This issue has been resolved. | DE121286 |
| Previously, there was inconsistency in Asset ID, Asset Description, FLOC ID and FLOC Description fields while creating and updating the General Recommendation. This issue has been resolved. | DE121197 |
| Previously, when implementing Actions as an EAM Maintenance Plan, incorrect URL was generated and added to the Recommendation Description field. This issue has been resolved. | DE119002 |
Previously, when you attempted to assess risk using a risk matrix that was associated with the following categories, an error occurred.
This issue has been resolved. | DE118408 |
| Description | Tracking ID |
|---|---|
The following deprecated fields are no longer available in the Asset Strategy Approval report:
| DE121048 |
Asset Strategy Optimization (ASO)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you promoted a Reliability Centered Maintenance (RCM) or Failure Modes and Effects Analysis (FMEA) analysis to a strategy, and then attempted to optimize the actions of the strategy, the optimization of the actions took longer than expected. This issue has been resolved. | DE122631 |
| Previously, when you attempted to optimize a strategy with an action type other than condition-based maintenance and do run simulation, an error message appeared. This issue has been resolved. | DE120644 |
| Previously, when loading the proposed risk in Asset Strategy Optimization, if the risk assessment was done with risk matrix having less than three categories, an error occurred. This issue has been resolved. | DE118410 |
Calibration Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
You can now create or link a calibration task with more than one Calibration Template, enabling you to define and use multiple templates to perform calibration for the same asset and task combination. To facilitate this enhancement, the following changes have been made:
| US384941 |
| You can now perform pressure calibration using Fluke 729 Automatic Pressure Calibrator. Note: Fluke 729 Automatic Pressure Calibrator supports both analog and discrete calibration. | US384751 |
| Description | Tracking ID |
|---|---|
| Previously, after you upgraded the GE Digital APM database from V3 to V4, you could not update the applied templates when you changed the Calibration Strategy in a Calibration Profile. This issue has been resolved. | US379741 |
| Previously, after you upgraded the GE Digital APM database from V3 to V4, certain fields in the Calibration Profile were set to empty. Also, you could not change the Calibration Strategy or link additional assets to the upgraded Calibration Profile. This issue has been resolved. | US379739 |
| Previously, when performing automated calibration using a Fluke Calibrator connected to a computer with a culture setting other than English, the task list was not updated in the Fluke Calibrator device. This issue has been resolved. | DE131106 |
| Previously, when you create a Calibration Event record using a Functional Test template, with the Response Type as Selection in the template detail record, an error occurred. This issue has been resolved. | DE129885 |
| Previously, when you created a Functional Test template, the users associated with the sites other than your default site could not access the records in the Details section of the template. This issue has been resolved. | DE127061 |
| Previously, while creating a Calibration Event, if the mandatory fields were blank, an error occurred. This issue has been resolved. | DE124768 |
| Previously, when you performed a manual square-root calibration, the RMS Error was incorrectly calculated because the Input Measure AF and Input Measure AL values were not square-rooted. This issue has been resolved. | DE121916 |
| Previously, when you tried to run the Device Mapping Upgrade Utility with duplicate Device Mapping records present in the database, an error occurred. This issue has been resolved. | DE116215 |
Catalog
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to create or modify a Catalog Item, the Name and Caption fields in the Save As window could contain a maximum of 100 characters. Now, the field size has been increased to 255 characters. | DE50672 |
| Previously, in the Catalog Item Properties window for a Catalog item, when you modified a value, the updated value did not appear for the corresponding tool. This issue has been resolved. | DE50673 |
Compliance Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
Previously, you could search records from all the Compliance Management families in the Global Search. Now, all families from Compliance Management have been excluded from Global Search, except for the following families:
However, you can configure a family to be included or excluded from Global Search using the Search Configuration. | US384419 |
| Description | Tracking ID |
|---|---|
Previously, in the Inspection Plan page, if the RBI Recommendations were in a Proposed state and did not have a baseline state ID, the following buttons were not enabled or disabled correctly:
This issue has been resolved. | DE119883 |
| Description | Tracking ID |
|---|---|
| The relationship family Compliance Template Has Mapping has been deprecated. | DE129072 |
Data Loaders
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when running data loaders for non-English users, for example German users, numeric values for that culture were not being formatted correctly. This issue has been resolved. | DE127333 |
| Previously, when you canceled a data loader job that was in progress, the job was intermittently locked and prevented other data loader jobs from running. This issue has been resolved. | DE121444 |
| Previously, if a relationship was created between two families using a Foreign Key, and you attempted to import records into the families using the APM Family data loader, an error occurred. This issue has been resolved. | DE118025 |
Datasets
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when creating a dataset using a Microsoft Excel file, if you selected the Import specific range values check box in the Choose Worksheet section, the default value, zero, did not appear in the Start and End boxes. This issue has been resolved. | DE50653 |
Documentation
This topic provides a list of documentation changes released in this version.
| Description | Tracking ID |
|---|---|
| GE Digital APM documentation is now available at https://www.ge.com/digital/documentation/apm-classic/ instead of https://www.meridium.com/secure/documentation/WebHelp/Home.htm or https://apps-docs.predix.io/en-US/apm_classic. The new portal offers:
| US385911 |
eLog
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve performance, the eLog Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US380127 |
European Inspection Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| New content is added to Compliance Management to support the European Inspection requirements. European Inspection Management provides a solution to categorize the inspection activities according to government regulation, based on the pressure, volume, and fluid characteristics. According to this categorization, the Compliance Management module of GE Digital APM can recommend applicable inspection task types along with a recommended interval based on each asset type. It also helps you to identify the certification requirements of Inspectors, such as Z??S (Approved Inspection Body) or bP (Qualified Person), based on the criticality of the asset. This functionality is fully integrated with the Compliance Management module and the Inspection Management module. | F39687 |
Failure Modes and Effects Analysis (FMEA)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve performance, the Failure Modes and Effects Analysis Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US379897 |
You can now export FMEA analyses, FMEA analysis templates, and asset templates to Excel workbooks. To facilitate this enhancement, the following changes have been made:
| US352432 |
| Performance when loading the counts on the tabs in the FMEA Overview page has been improved. | US343623 |
| The performance when promoting an FMEA template to an ASM Template has been improved. | US298396 |
) has been added to the | Description | Tracking ID |
|---|---|
| Previously, in the Risk Summary window, the risk assessment record was saved even if you selected the Cancel button. This issue has been resolved. | DE126496 |
| Previously, when you attempted to import large analyses using the Failure Modes and Effects Analysis (FMEA) data loader, the operation exceeded the timeout period, causing the import process to fail. This issue has been resolved. | DE120356 |
| Previously, when you created a Failure mode for an FMEA analysis, duplicate HTTP GET requests were created, thereby affecting performance. This issue has been resolved. | DE117612 |
| Previously, when you created an FMEA analysis, duplicate HTTP GET requests were created, thereby affecting performance. This issue has been resolved. | DE117611 |
| Previously, while loading FMEA analyses through data loader, an error message appeared. This issue has been resolved. | DE116618 |
| Previously, while creating an analysis, when you imported data using the Failure Modes and Effects Analysis (FMEA) Data Loader with the same name as the FMEA Analysis Template, the FMEA Analysis Template was unexpectedly updated. This issue has been resolved. | DE89674 |
| Previously, you could promote FMEA analyses to ASM regardless of the state. Now, you can promote only analyses which are in the approved state. In addition, analyses in the approved state will not be editable. | US382363 |
Family Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The record IDs are no longer stored in the ENTY_ID field in the database. Now, record IDs are virtual, and are calculated at runtime based on the ID template. The following changes have been made:
| US359355 |
| Description | Tracking ID |
|---|---|
| Previously, when you created a Foreign Key relationship definition between two families, you could not create additional relationship definitions with a different cardinality. This issue has been resolved. | DE120671 |
Family Policies
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now view the end time for policy executions in the Execution History pane of the Design workspace. | US383244 |
|
You can now access the query specified in a Query node or the R script specified in an R Script node directly from the node. To facilitate this enhancement, the Open in New Window button ( | US374240 |
| You can now configure different policy execution history retention duration settings for executions that result in Errors, Warnings (Action Taken), Warnings (No Action Taken), Success (Action Taken), or Success (No Action Taken). When the GE Digital APM database is upgraded, if an overall policy execution history retention duration setting was previously configured, this setting will be applied for all execution results. | US330806 |
| To improve the performance of the Query node, the result set of the node is now restricted to the first 10,000 rows of the query result. | DE117522 |
) has been added to the | Description | Tracking ID |
|---|---|
Previously, when the job configured to delete old policy execution history records from the GE Digital APM database ran, the following issues intermittently occurred:
| US374943 |
| Previously, in APM V4.3.1.x, when you modified a family policy containing multiple Create Event nodes configured to use the same Event name, the policy model was corrupted, and the policy did not execute as expected. This issue has been resolved. Note: Family policies that were corrupted continue to execute incorrectly. For assistance to correct affected policies, contact GE Digital Support. | DE131111 |
| Previously, in the Math node, an error occurred when you modified an equation containing an indexed variable name conflicting with an input variable name. This issue has been resolved. | DE125923 |
| Previously, if the policy model contained a node that must not be executed if its output is not used by any successor node, and if you mapped the output of such a node to only a Case node, the node was not executed. This issue has been resolved. | DE120494 |
| Previously, if the execution or validation of an Email node in a sub policy resulted in an error, no execution details were displayed for the node, and the policy execution history did not indicate that an error had occurred. This issue has been resolved. | DE117263 |
| Previously, if you added a field to a family, and then added the same field to a query that is represented by a Query node, the execution of the Query node failed. This issue has been resolved. | DE115326 |
| Previously, if you used an Edit, Create, or Delete Entity, Create or Delete Relationship node in a sub policy, the execution history details did not include the node's results, and the policy-level execution history may not have indicated that an error or warning occurred. This issue has been resolved. | DE114017 |
| Description | Tracking ID |
|---|---|
| In order to improve the performance of the policy execution service, the Math node execution time out is not enforced. Policy executions that run for an extended time due the Math node will be canceled by the policy execution time out feature. | DE131899 |
General Dashboards
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now filter the results in a Query widget in a dashboard. | US369440 |
To improve the performance of GE Digital APM, the data of the dashboard is no longer refreshed automatically when you select  . You can now manually refresh the data of the dashboard. To facilitate this enhancement, a new button, Refresh (), has been added to the dashboard. | US350211 |
Hazards Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
You can now remove the assets that are specified in the Functional Location ID and Equipment ID fields of a Hazards Analysis Cause or Hazards Analysis Safeguard datasheet. To facilitate this enhancement, the Remove button ( ) has been enabled in the Asset Finder window that appears for the Functional Location ID and Equipment ID fields in the datasheet for the Cause or Safeguard. | US372072 |
| Description | Tracking ID |
|---|---|
| Previously, if you accessed an unmitigated risk matrix for a Consequence associated with a hazards analysis, and then selected Save or Cancel without modifying any value in the Unmitigated Risk Assessment window, the values in the Mitigated Risk fields of the Hazards Worksheet section disappeared. This issue has been resolved. | DE120203 |
| Description | Tracking ID |
|---|---|
The following fields have been removed from the Risk Assessment Recommendation datasheet because you cannot create an SAP notification for a Risk Assessment Recommendation:
| DE116587 |
Inspection Field Data Collection
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
The Inspection Field Data Collection module has new enhancements in this release and enables you to perform the following actions:
| F45130 |
Inspection Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The relationship family Has NR13 Technical Data defines a relationship between a Functional Location or Equipment and Asset Technical Data as part of a European requirement in Inspection Management. To facilitate this change, the family caption of the relationship family is now updated to Has Technical Data. | US399166 |
| Description | Tracking ID |
|---|---|
| Previously, the Inspection Management Overview page was filtered based on the Asset Hierarchy context even if you had provided the unit key in the Uniform Resource Locator (URL). This issue has been resolved. Now, the Inspection Management Overview page is filtered based on the unit key that you provide. | US376475 |
| Previously, in APM Now, the users set up in LDAP were unable to manage Inspection Plans. This issue occurred because the Security Role IDs were changed to make them unique across multiple tenants. This issue has been resolved. You can now add the users to the following Security Groups that have been created with the same privileges of the corresponding Security Roles to enable them to manage Inspection Plans:
For more information on how to assign the Security Groups to the users, follow the steps in https://digitalsupport.ge.com/communities/en_US/Article/V4-3-1-0-1-Compliance-Management-and-Risk-Based-Inspection-How-to-configure-Inspection-Plans-to-be-managed-by-users-with-a-Security-Groups. | DE120718 |
Previously, in the Inspection Management Overview page, the master detail sheet associated with an Inspection family did not appear when the following conditions were met:
| DE120155 |
| Previously, when accessing an Inspection that contained exactly 25 General Finding related records, if you scrolled through the General Findings in the left pane, the system performed an infinite scroll. This issue has been resolved. | DE119768 |
Previously, the Inspection Confidence value was incorrectly populated on an Inspection Confidence Evaluation record, if you selected Ultrasonic Shear Wave Testing in the Type of Inspection field, and selected one of the following values in the Extent field:
This issue has been resolved. | DE119766 |
| Previously, in the Manage Inspection Profiles page, in the Sequence Definition window, the values in the Item Category column were not properly localized. This issue has been resolved. | DE94113 |
| Previously, in the Family Management page, Inspection Taxonomy Configuration family did not have any defined ID Templates associated with it. This issue has been resolved. | DE91702 |
| Description | Tracking ID |
|---|---|
| Time-Based Inspection (TBI) Settings functionality has been removed from Inspection Management due to low adoption. This functionality has been replaced by Compliance Management. | US376040 |
Manage Translation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| When you modify any metadata string in GE Digital APM, the metadata string is updated for the first time. However, if you modify the same metadata string again, it is not updated because the associated metadata cache is not updated. | DE132259 |
Management of Change
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you did not have the license for Hazard Analysis, SIS Management, or any related module, you could not add or view the changed elements in the Changed Elements workspace of a Change Project. This issue has been resolved. | DE131618 |
Maps
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To improve performance, the Map page is no longer updated automatically when you return to the previously opened tab. You must now select the Refresh icon ( )??? to update the page. | US378221 |
OT Connect
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Process Data Integration (PDI) has been functionally replaced by OT Connect. OT Connect allows you to connect to and synchronize Tag metadata from an OPC-compliant historian. This also allows you to enable Tag subscriptions to view, analyze, and act on process data. OT Connect uses new entities and relationships that are unique to this feature. When GE Digital APM is upgraded to V4.4.0.0.0, existing data in OPC families will be upgraded to reference the new structure, and the families that were associated with PDI will become obsolete. Note:
| F50865 |
Policy Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve performance, the Policy Designer Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US396407 |
|
Configuration settings for the Policy Trigger and Policy Execution Services have been modified:
Note: For more information, refer to the Policy Designer deployment documentation.
|
|
|
The OPC Tag node has been replaced by the OT Connect Tag node. The OT Connect Tag node retrieves readings from your process historian using the OT Connect service. When GE Digital APM is upgraded to V4.4.0.0.0, existing Policies using the OPC Tag node will be upgraded to use the OT Connect Tag node and Policy Instances for these policies will be upgraded to reference new OT Connect records created during the upgrade process. New features of the OT Connect Tag node:
Note:
|
|
| The Policy Trigger and Policy Execution Services have been modified to use ActiveMQ queues instead of MSMQ queues. |
|
| You can now view the end time for policy executions in the Execution History pane of the Design workspace. | US383244 |
|
You can now access the query specified in a Query node or the R script specified in an R Script node directly from the node. To facilitate this enhancement, the Open in New Window button ( | US374240 |
| You can now configure different policy execution history retention duration settings for executions which result in Errors, Warnings (Action Taken), Warnings (No Action Taken), Success (Action Taken), or Success (No Action Taken). When the GE Digital APM database is upgraded, if an overall policy execution history retention duration setting was previously configured, this setting will be applied for all execution results. | US330806 |
| To improve the performance of the Query node, the result set of the node is now restricted to the first 10,000 rows of the query result. | DE117522 |
| Description | Tracking ID |
|---|---|
Previously, when the job configured to delete old policy execution history records from the GE Digital APM database ran, the following issues intermittently occurred:
| US374943 |
| In APM V4.3.1.x, when you modified a policy containing multiple Create Event and/or Close Event nodes configured to use the same Event name, the policy model was corrupted, and the policy did not execute as expected. This issue has been resolved. Note: Policies that were corrupted continue to execute incorrectly. For assistance to correct affected policies, contact GE Digital Support. | DE131111 |
| Previously, when a super user searched for a record to assign to a Policy Instance, the results in the Search window included only the records for Sites to which the super user was explicitly assigned. This issue has been resolved. | DE129861 |
|
Previously, on the Policy Designer Overview page, the Overdue Recommendations list did not display the correct State Assignee user. This issue has been resolved. Note: To facilitate this change, the query used by the Overdue Policy Recommendations list has been updated. If you have previously customized this query, copy the new query from the baseline folder to the public folder and apply the customizations again.
| DE128404 |
| Previously, on the Policy Designer Overview page, the tiles did not display any results, and the My Policy Recommendations list did not display any results for users other than super users. This issue has been resolved. | DE126120 |
| Previously, in the Math node, an error occurred when you modified an equation containing an indexed variable name conflicting with an input variable name. This issue has been resolved. | DE125923 |
| Previously, if you added a new family, or added a field to an existing family, and then used the family or field in an Entity, Create Entity, Edit Entity, Create Relationship, or Delete Relationship node, an error indicating that the node was inactive occurred during execution of the policy. This issue has been resolved. | DE122975 |
| Previously, if the policy model contained a node that must not be executed if its output is not used by any successor node, and if you mapped the output of such a node to only a Case node, the node was not executed. This issue has been resolved. | DE120494 |
| Previously, if you assigned multiple users to a policy, the number of instances associated with the policy appeared incorrectly in the Policies section of the Policy Designer Overview page. This issue has been resolved. | DE119853 |
| Previously, if the execution or validation of an Email node in a sub policy resulted in an error, no execution details were displayed for the node, and the policy execution history did not indicate that an error had occurred. This issue has been resolved. | DE117263 |
| Previously, if you added a field to a family, and then added the same field to a query that is represented by a Query node, the execution of the Query node failed. This issue has been resolved. | DE115326 |
| Previously, if you used an Edit, Create, or Delete Entity, Create or Delete Relationship node in a sub policy, the execution history details did not include the results for the node, and the policy-level execution history may not have indicated that an error or warning occurred. This issue has been resolved. | DE114017 |
| Description | Tracking ID |
|---|---|
|
While using Internet Explorer 11 browser, when you attempt to open a Policy with a large number of instances it might fail. Note: GE Digital recommends you to use Chrome or Edge browser. If you are unable to access GE Digital APM using Chrome or Edge browser, make additional copies of the Policy and divide the required instances between them.
| US412940 |
| In order to improve the performance of the policy execution service, the Math node execution time out is not enforced. Policy executions that run for an extended time due the Math node will be canceled by the policy execution time out feature. | DE131899 |
| In a policy, where an OT Connect Tag node is followed by a Collection Filter, and the Collection Filter compares the timestamps in the reading collection with a date value mapped from the output of a Sub Policy node, an error occurs in policy validation or execution. Date values mapped into a Collection Filter node following an OT Connect Tag node must be evaluated in the calling policy. | DE129690 |
Production Loss Analysis (PLA)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now reconcile the production loss for multiple production data at a time. To facilitate this enhancement, a new button, Bulk Data Entries, has been added to the PLA Overview page. | US388394 |
| To improve performance, the Production Loss Analysis overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US380127 |
| Description | Tracking ID |
|---|---|
| Previously, if you imported the Standard Batch Cycle Time and Standard Batch Size for a Production Profile using the Production Loss Analysis (PLA) 1-Admin Data Loader, the Maximum Sustained Capacity Rate (MSCR) and Maximum Sustained Hourly Rate (MSHR) values were not updated. This issue has been resolved. | DE126436 |
| Previously, in Production Loss Analysis, with the Maximum Sustained Hourly Rate (MSHR) set to be calculated automatically, the calculation was based on the Maximum Demonstrated Rate. When the batch cycle time was less than or greater than a day, it displayed incorrect values. This issue has been resolved. Now, the MSHR auto-calculation is based on the Maximum Sustained Hourly Rate and the batch cycle time is displayed correctly. | DE122813 |
| Previously, using the Production Event data loader, you could not update the production event code under the related families. This issue has been resolved. | DE122393 |
| Previously, in the Production Profile datasheet, the value in the Planning Rate box appeared without a description due to which you could not interpret the data. This issue has been resolved. Now, the value in the Planning Rate box appears with the full description of the selected units in the Standard Batch Size and Standard Batch Cycle Time boxes (for example, 12345 Barrels/0.25 Day). | DE121266 |
| Previously, in the Production Profile datasheet, in the Max Demonstrated Rate box, you could not enter a value that was less than that in the Standard Batch Size box. This issue has been resolved. | DE121266 |
| Previously, when modifying a Plan Template or creating a Production Plan using a Plan Template, if you modified the Plan Start Time, the Plan End Time was not automatically updated based on the duration specified in the template. This issue has been resolved. | DE120291 |
| Previously, in a Production Event record, you could not remove the Production Event Code associated with the Production Event. This issue has been resolved. | DE117125 |
Queries
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
In the Results workspace, the wordwrap feature has been added to the columns containing text values. In addition, you can now perform the following actions:
| US396364 |
| Description | Tracking ID |
|---|---|
| Previously, certain queries that contained parameter prompts and referenced other queries would unnecessarily recompute parameter values. This issue has been resolved. Now, parameter values are only recomputed when needed. | DE127230 |
| Previously, when you attempted to select a query prompt value in the prompt filter, the prompt values intermittently took longer than expected to appear and there was no indication that the operation of loading the values was in progress. This issue has been resolved. Now, a spinner appears while the values are being loaded. | DE127229 |
| Previously, the queries with a column comparison to a date constant that did not contain a time returned partial results, or no records were returned. This issue has been resolved. | DE125046 |
| Previously, in GE Digital APM while saving the Catalog items, you could use a forward slash / and a back slash \ in the Catalog item name. This issue has been resolved. Now, you cannot use them (/ and \) while saving a Catalog item. | DE122149 |
| Previously, the exported queries displayed dates in the Coordinated Universal Time (UTC). This issue has been resolved. Now, the exported queries display dates in the time zone specified for your GE Digital APM user account. | DE119140 |
| Previously, an error occurred when executing a saved append query, which is referenced to another query as a source. This issue has been resolved. Now, the query runs as expected. | DE118487 |
|
Previously, if you were assigned to the MI Power User Role Security Group or MI Foundation Power Security Role, you could not create the following types of queries:
This issue has been resolved. | DE112398 |
Record Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
You can now perform the following actions on a Recommended Action:
 ) menu. | DE121710 |
| Description | Tracking ID |
|---|---|
| Previously, when you entered a value that contained an HTML tag in any field of a datasheet, no error message appeared even though the value was invalid. This issue has been resolved. Now, in this scenario, an error message appears and you cannot save the record. | DE123809 |
Reliability Analytics
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in some reliability modules, the charts in a report did not contain legends. This issue has been resolved. | US384858 |
| Previously, as a Reliability User in Reliability Analytics, you could not reload data from the chart pages for Analyses based on a query or dataset. This issue has been resolved. | DE130909 |
| Previously, in a Reliability Distribution Analysis or Reliability Growth Analysis, in the Analysis Period window, when you modified the values in the Start Date and End Date boxes, and then accessed the Analysis Period window, the start and end date values were modified according to another time zone. This issue has been resolved. | DE129711 |
| Previously, if your language setting in GE Digital APM was not English, the options in the Frequency of Alert after due date list of an RCA Verification contained unknown values. This issue has been resolved. Now, the list contains the translated values based on your language setting. | DE128988 |
| 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. | DE128031 |
| Previously, if your culture was set to Russian, when creating an analysis, you could not assign an asset to the analysis in the <Analysis Type> Data Editor window. This issue has been resolved. | DE128027 |
| Previously, when creating a Reliability Distribution Analysis from a query containing parameters, an error message appeared when opening an analysis chart. This issue has been resolved. | DE125965 |
| Previously, when creating a Reliability Analysis from a Query, if a parameter (for example; start date) had no ID, an error occurred. This issue has been resolved. | DE123880 |
| Previously, in APM Now, in System Reliability Analysis, under certain conditions, when you selected a subsystem from a System Scenario Diagram, an error message appeared, and the page failed to load. This issue has been resolved. | DE123157 |
| Previously, when an SAP notification was created for a Reliability Recommendation, the Work Request Reference field was not automatically populated with the corresponding value in the notification. This issue has been resolved. | DE121857 |
| Previously, when using Internet Explorer, if you attempted to access the diagram for a System Scenario associated with a System Reliability Analysis, the diagram intermittently took longer than expected to appear and there was no indication that the operation of loading the diagram was in progress. This issue has been resolved. Now, a spinner appears while the diagram is being loaded. | DE121668 |
| Previously, in a Reliability Recommendation record, if you selected the Create Work Request check box, and then saved the record, the SAP Notification that was created did not contain the Equipment and Functional Location values associated with the record. This issue has been resolved. | DE119938 |
Reliability Centered Maintenance (RCM)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve performance, the Reliability Centered Maintenance Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh () to update the page. | US379897 |
You can now import or export the RCM analysis templates. To facilitate this enhancement, the following changes have been made:
| US376411 |
You can now export RCM analyses to an Excel workbook. To facilitate this enhancement, the following changes have been made:
| US352432 |
| The performance when loading the counts on the tabs in the RCM Overview page has been improved. | US343623 |
| The performance when promoting an RCM template to an ASM Template has been improved. | US298396 |
), has been added to the | Description | Tracking ID |
|---|---|
| Previously, after applying a template to an RCM analysis, if you navigated away from the <Analysis Name> page, and then attempted to access the data in the <Analysis Name> page, an error message appeared. This issue has been resolved. | DE127626 |
| Previously, in the Risk Summary window, the risk assessment record was saved even if you selected the Cancel button. This issue has been resolved. | DE126496 |
| Previously, when you attempted to import large analyses using the Reliability Centered Maintenance (RCM) data loader, the operation exceeded the timeout period, causing the import process to fail. This issue has been resolved. | DE120356 |
| Previously, when you consolidated the Recommendations that were created using the Reliability Centered Maintenance (RCM) data loader, the recommendation ID was not generated. This issue has been resolved. | DE119947 |
| Previously, while loading RCM analyses through data loader, an error message appeared. This issue has been resolved. | DE116618 |
| Previously, while creating an analysis, when you imported data using the Reliability Centered Maintenance (RCM) data loader with the same name as the RCM Analysis Template, the RCM Analysis Template was unexpectedly updated. This issue has been resolved. | DE89674 |
| Previously, you could promote RCM analyses to ASM regardless of the state. This issue has been resolved. Now, you can promote only analyses that are in the approved state. In addition, you cannot modify the analyses that are in the approved state. | US382363 |
Results Grid
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| A new indicator has been added to the Results Grid that displays the number of columns to which filters are applied. | US399967 |
Risk Based Inspection
This topic provides a list of product changes released for this module in this version.
RBI 580 and 581
| Description | Tracking ID |
|---|---|
| Previously, on the Risk Based Overview page, in the Assets section, when you selected Finalize Risk button, the PRD analyses did not appear. This issue has been resolved. | US399824 |
| Previously, if you updated any of the Global Preferences in the RBI Admin Preferences page, the RBI Overview Table Preference was cleared and the selected columns were no longer displayed for RBI 580 or RBI 581. This issue has been resolved. Now, editing Global Preferences will not affect a previously saved RBI Overview Table Preference. | DE127917 |
| Previously, in RBI Corrosion Loop datasheet and RBI System datasheet, the Created By and Last Updated By fields were not populated. This issue has been resolved. | DE121950 |
| Previously, in the Degradation Mechanisms section, the horizontal scroll bar overlapped with the last row of the grid. This issue has been resolved. Now, the scroll bar appears at the bottom of the section. | DE119942 |
Previously, in the Inspection Plan page, if the RBI Recommendations were in a Proposed state and did not have a baseline state ID, the following buttons were not enabled or disabled correctly:
This issue has been resolved. | DE119883 |
| Previously, when generating recommendations in Risk Based Inspection (RBI), if the Name of a policy used for strategy mapping was longer than 50 characters, an error occurred. This error was due to the length of the Policy Name field in RBI Strategy Mapping Configuration family being configured to less than the length of the Name field in the Policy family. This issue has been resolved. Now, the length of the Policy Name field in RBI Strategy Mapping Configuration family and the Name field in Policy Family are the same. | DE116375 |
RBI 580
| Description | Tracking ID |
|---|---|
You can now calculate the RBI PRD Criticality Analyses in bulk from the Assets section of the following pages:
| US398540 |
Previously, all families were included in the global search. Now all families from Risk Based Inspection (RBI) 580 have been excluded from the global search except the following:
Note: You can use search configuration to enable or disable Global Search for families. |
|
| Description | Tracking ID |
|---|---|
| Previously, if both the Risk Based Inspection (RBI) and RBI 581 licenses were not applied in the Risk Based Inspection module, when using the Upgrade Analyses utility from the RBI Admin Preferences page, an error occurred. This issue has been resolved. | DE123165 |
| Previously, if an RBI Criticality Analysis contained a Chloride Stress Corrosion Cracking (CI SCC) or Hydrogen Stress Cracking (HSC) - Hydrofluoric Acid Degradation Mechanism, the value in the output fields were incorrectly calculated. This issue has been resolved. | DE121801 |
| Previously, when calculating an RBI Criticality Analysis, the value in the Estimated Half Life field in the Criticality Ext. Corr. Deg. Mech. Eval. family was set incorrectly if you had defined UOM conversion set for any field used for the calculation of estimated half-life. This issue has been resolved. | DE119596 |
Previously, if your culture setting had a culture other than English, and you linked a Degradation Mechanism to an RBI Criticality Analysis, the values contained in the following boxes of the Degradation Mechanism record were not translated to the language based on your culture setting:
| DE93275 |
| Previously, when generating recommendation on an RBI Criticality Analysis linked to a Wet H2S (Blistering, SOHIC, HIC, SSC) Degradation Mechanism, the Appendix _G policy was not executed. This issue has been resolved. | DE82211 |
RBI 581
| Description | Tracking ID |
|---|---|
Previously, all families were included in the global search. Now all families from Risk Based Inspection (RBI) 581 have been excluded from the global search except the following:
Note: You can use search configuration to enable or disable Global Search for families. | US395686 |
| The Non-Flammable Non-Toxic (NFNT) Consequence Area calculations for caustic and acid fluids have been modified to adhere to the API-581 3rd Edition, Addendum 1. | US384625 |
| Description | Tracking ID |
|---|---|
Previously, when calculating the mitigated risk on the plan date for External Cracking Degradation Mechanism Evaluation on an RBI 581 Risk Analysis, the age calculation did not consider the Target Inspection Date. As a result, the Total Damage Factor With Plan (RBI Degradation Mechanisms) displayed incorrect values for the following damage mechanisms:
This issue has been resolved. | DE128159 |
| Previously, when the value in the Liner is Present field was set to Yes (Y), and Degradation Mechanism Evaluation (DME) was not 581-Internal Component Lining Damage, the Online Monitoring Adjustment field in RBI 581 Thinning and Lining Damage Mechanism Evaluation record was incorrectly calculated. This affected the value in the Final Damage Factor field. This issue has been resolved. | DE125927 |
| Previously, when the Allow Override of Total Financial Consequence field was set to true on RBI 581 Consequence Evaluation records, the User Total Financial Consequence field was incorrectly excluded for the calculation of financial risks on the related RBI Degradation Mechanisms (DMs) records. The User Total Financial Consequence field was also excluded from RBI 581 ISO-Risk Plot. This issue has been resolved. | DE123065 |
| Previously, when you calculated an RBI 581 Risk Analysis on a Storage Tank component that contained a toxic mixture, the calculation failed. This issue has been resolved. | DE121404 |
|
Previously, when the UOM conversion set was assigned to you, while calculating an RBI 581 Risk Analysis, the Risk Category field was calculated incorrectly. In addition, the output fields were calculated incorrectly for any of the following conditions:
This issue has been resolved. | DE121778 |
| Previously, when you viewed the RBI 581 ISO-Risk Plot Preferences page on a low-resolution device, the RBI 581 ISO-Risk Plot Medium-High Category Limit field was not visible if the browser was zoomed to 100 percent. This issue has been resolved. | DE118013 |
Previously, if your culture setting had a culture other than English, and you linked a Degradation Mechanism to an RBI 581 Risk Analysis, the values contained in the following boxes of the Degradation Mechanism record were not translated to the language based on your culture setting:
| DE93275 |
Risk Matrix
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now export or import Risk Matrices. To facilitate this enhancement, the Export option has been added to the Risk Matrix Admin page. You can import Risk Matrices through the Risk Matrix data loader. | US378546 |
| Risk management now supports having no Probabilities defined (that is, unrestricted Probabilities) for a financial category. | US337727 |
| Description | Tracking ID |
|---|---|
| Previously, you could create a Risk Matrix containing the same index for two different categories, due to which you could not perform risk assessment. This issue has been resolved. Now in this scenario, the index is always unique, and you cannot create a Risk Matrix containing duplicate indexes. | DE112939 |
Root Cause Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in the Cause Details section of the RCA Overview page, when you attempted to access an RCA Analysis record, the RCA Overview page appeared instead of the <Analysis Summary> workspace. This issue has been resolved. Now, when you select the RCA Analysis record, the <Analysis Summary> workspace for the record appears, displaying the logic tree of the RCA analysis. | US398535 |
| Previously, in an RCA Logic Tree, even after specifying the hypothesis causes for Human, Physical, or Latent, when you returned to the design canvas, the red line was lost and reverted to black. This issue has been resolved. | DE130968 |
| Previously, when logged in to RCA Module with view-only permission, you could rearrange nodes in the RCA Logic Tree and RCA Event Diagram and changes were saved to the RCA record when you exited the page. This issue has been resolved. Now, with view-only rights you cannot change the node position in the Event diagram and logic tree. | DE130838 |
| Previously, users with view-only permission were able to add, assign, or unassign nodes from the Logic Tree Properties window.??This issue has been resolved. | DE130339 |
| Previously, when you attempted to access an RCA Analysis without an active PLA license, an error occurred. This issue has been resolved. | DE128152 |
| Previously, in an RCA Analysis with state management enabled, you could create duplicate states in customer databases, which resulted in double images in the user interface. This issue has been resolved. | DE127245 |
| Previously, when completing a verification and setting the completed field to Yes, the completed action was not retained after saving. This issue has been resolved. | DE127225 |
| Previously, when creating an RCA from a template, if the assigned name was not unique, the analysis details were not saved, and you were forced to restart the process. This issue has been resolved. | DE126529 |
| Previously, when saving an RCA Analysis from a template, the page would appear to freeze while the content was being saved to the analysis. This issue has been resolved. Now, a waiting wheel appears to inform the user that the analysis is being saved. | DE126447 |
| Previously, when creating an Event timeline in an RCA Analysis, the Event Flag spanned out of the canvas area. This issue has been resolved. | DE123975 |
| Previously, when you created a Tracking Item, the Start Date appeared twice in the <Track Items> workspace.??This issue has been resolved. | DE123413 |
| Previously, when an SAP notification was created for an RCA Recommendation, the Work Request Reference field was not automatically populated with the corresponding value in the notification. This issue has been resolved. | DE121855 |
| Previously, if a team member associated with an RCA analysis no longer existed, and you attempted to create an RCA Recommendation for the analysis, the associated Cause drop-down list box was not automatically populated. This issue has been resolved. | DE121016 |
| Previously, when you accessed the Reliability section for an asset from the Asset Hierarchy, in the Root Cause Analysis row, the counts of the analyses that were in the In Progress and Published states were incorrect. This issue occurred when some of the analyses were linked to assets from sites for which you did not have the necessary permissions. This issue has been resolved. | DE120439 |
| Previously, in an RCA Recommendation record, if you selected the Create Work Request check box, and then saved the record, the SAP Notification that was created did not contain the Equipment and Functional Location values associated with the record. This issue has been resolved. | DE119937 |
Rounds Data Collection
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The product has been modified to avoid losing individual reading while changing the filter settings for Mobile Rounds Data Collection. Now, you can manage better reading and upload workflow. Additionally, messaging and logging have been enhanced around the readings upload process. | US414479 |
Rounds Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The GE Digital APM Rounds uses a System Code Table instead of the Unit of Measure conversion feature. | US382461 |
| Description | Tracking ID |
|---|---|
| Previously, the wizard for adding existing ML/LR was not showing all the available checkpoints and experienced performance issues. This issue has been resolved. Now, the product has been modified to ensure that the correct checkpoints are included in the wizard results. Additionally, the wizard has been improved to retrieve the results more efficiently. | DE128041 |
SAP and SAP PI
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The data loader framework in UDLP V2.8.0 is compatible with GE Digital APM. | US401928 |
| APM Connect SAP and SAP PI adapters now support the SAP S/4Hana 1909. | US401899 |
| Description | Tracking ID |
|---|---|
| Previously, when you ran the SAP PI or SAP PI/PO Work History extraction job, the files were intermittently transferred from SAP to GE Digital APM even before the extraction was complete. This issue has been resolved. Now, the folder structure for SAP adapters has been modified to transfer the files only after their extraction is complete. | US330411 |
| Previously, record locked messages failed to appear in APM error messages, and did not enable you to know why the Notification is not being created in SAP. This issue has been resolved. | DE128819 |
| Previously, the SAP Adapters Help documentation did not contain the information that the Planned Work Adapter supports only the Single Cycle Maintenance Plans in the Planned Work Interface with SAP. This issue has been resolved. | DE123655 |
| Previously when creating a General Recommendation record, multiple calls were made to SAP resulting in duplicate entries in the Long Text field in SAP.??This issue has been resolved. | DE123054 |
| Previously, the sequence of the work history status codes in GE Digital APM did not match the sequence of the work history status codes in SAP. Also, in some cases, the status codes that were hidden in SAP appeared in GE Digital APM. These issues have been resolved. Note: User status is available for Work History only. | DE114333 |
Schedule Logs
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| While scheduling jobs in monthly intervals, you can now schedule a recurring job on the last day for selected months. To facilitate this enhancement, a new option, Last Day of the month(s), has been added to the Edit Schedule window. | US373531 |
| You can now manually recover failed jobs that appear in the In Progress section of the Schedule Logs page. To facilitate this enhancement, a new button, Recover Jobs, has been added that appears when you select the In Progress tab. | DE120857 |
| Description | Tracking ID |
|---|---|
| Previously, when you scheduled jobs, some of the jobs did not successfully run and appeared in the In Progress section. This issue occurred because the application server was disconnected from GE Digital APM when the jobs were run. This issue has been resolved. Now, GE Digital APM automatically restarts the jobs when the application server is restored. | DE120857 |
Security Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now configure the preferred language of a security user without affecting the culture assigned to the user. To facilitate this enhancement, a new drop-down list box, Language, has been added to the Details section of the Users page. Additionally, a new drop-down list box, Default Language, has been added to the User Defaults page, which allows you to configure a default language for the users. Important: The culture associated with a user no longer determines the language that is displayed when the user signs in to GE Digital APM. | US386929 |
Single Sign-On
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can no longer use the saml.config file to configure the SSO URL. A new file saml.json has been added to the existing path to configure the SSO URL. | US340890 |
SIS Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The SIS Management module now uses Exida???s Safety Equipment Reliability Handbook (SERH) latest database version 2020.1.01. | US398088 |
| You can now remove the assets that are specified in the Functional Location ID and Equipment ID fields of an Instrumented Function. To facilitate this enhancement, the Remove button () has been enabled in the Asset Finder window that appears for the Functional Location ID and Equipment ID fields in the datasheet for the Instrumented Function. | US292115 |
| Description | Tracking ID |
|---|---|
| Previously, when performing an SIL Assessment using the??Risk Matrix Internal Assessment method, if you??did not select a risk value in the Environment section of the Risk Matrix, you could not??select a??value in??the Operations section of the Risk Matrix. This issue has been resolved. | DE131771 |
Previously, when modifying a Final Element associated with a Protective Instrument Loop, if you selected the Remote Actuated Valve option in the Select a Final Element window, the More Options button ( ) appearing next to the Actuator box did not function as expected. This issue has been resolved. | DE127647 |
| Previously, if you created an external SIL Assessment for an SIL Analysis, the value that appeared in the Availability Target field of the Assessment Details section was incorrect. This issue has been resolved. | DE115055 |
System Requirements
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
The GE Digital APM V4.4.0.0.0 is now deployed on the .NET Core platform and now supports the following operating systems and relational database management systems:
| US408564 |
| Description | Tracking ID |
|---|---|
If you install the following applications on the GE Digital APM Server using Microsoft Visual Studio 2017, the applications do not work as expected.
Workaround: Perform the following:
| DE134150 |
Thickness Monitoring
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
To enhance usability of the Thickness Monitoring (TM) Assets and Thickness Monitoring (TM) Functional Location Data Loaders, the following values are now updated on the Interface Log record generated by the data loader execution.
| US390890 | ||||||||||
Previously, you could search records from all the Thickness Measurement families in the Global Search. Now, all families from Thickness Measurement have been excluded from Global Search, except for the following families:
However, you can configure a family to be included or excluded from the Global Search using the Search Configuration. | US384419 | ||||||||||
| The performance of the Analysis Overview workspace and the TMLs section has been significantly improved. To facilitate this enhancement, the Based on field now appears as a hyperlink that allows you to access the Thickness Measurement Locations (TMLs) associated with the analyses in the Based on window. | US373718 |
| Description | Tracking ID | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Previously, the Thickness Monitoring Overview page was filtered based on the asset hierarchy context, even though the unit key was passed in the Uniform Resource Locator (URL). This issue has been resolved. Now, the Thickness Monitoring Overview page is filtered based on the provided unit key. | US384797 | ||||||||||||||||||||||||
| To enhance usability, the performance of Thickness Monitoring data loader has been improved when creating TML records that are directly linked to the equipment or functional location. | DE131763 | ||||||||||||||||||||||||
| Previously, in the Thickness Monitoring Analysis Overview page, the More Options button () did not appear after certain workflows, such as deleting a nested TML Group. This issue has been resolved. | DE131708 | ||||||||||||||||||||||||
| Previously, in the TM Dataloggers page, in the Send To and Receive From sections, the Thickness Measurement Locations (TMLs) were not sorted. This issue has been resolved. Now, the TMLs are sorted in alphanumerical order of the corresponding TML IDs. | DE128017 | ||||||||||||||||||||||||
Previously, in the TMLs section of the Analysis Overview page, the values in the following columns displayed the system code ID instead of the description:
| DE125402 | ||||||||||||||||||||||||
| Previously, in a Thickness Measurement Location (TML), if the first two measurements were of equal value, and the value was less than the value in the Minimum Thickness field, and the Use Minimum Corrosion Rate was not selected in the Corrosion Analysis Settings, the Scheduled Next Inspection Date value was calculated incorrectly. This issue has been resolved. Now, the Scheduled Next Inspection Date is calculated as per the value in the Last Measurement Date field. | DE123762 | ||||||||||||||||||||||||
| Previously, when you performed the Minimum Thickness (T-Min) calculation for more than 400 thickness measurement locations from the T-Min Calculator workspace, an error occurred. This issue has been resolved. Now, a pagination has been introduced to the T-Min Calculator workspace to load 100 thickness measurement locations per page. | DE123305 | ||||||||||||||||||||||||
Previously, the values in the Nominal Wall Thickness and Internal Diameter fields were incorrect in two records in the Pipe Properties family. This issue has been resolved. Now, the values in the records are updated as below:
| DE123035 | ||||||||||||||||||||||||
| Previously, on the Corrosion Analysis Settings page, when a user entered numeric values using comma as the decimal separator (for example: 1,9) the numeric value was not saved correctly. This issue has been resolved. | DE122373 | ||||||||||||||||||||||||
| Previously, if the measurements of a Thickness Measurement Location are at high loss, and you attempted to organize the Thickness Measurement Locations from the Organize TMLs workspace, an error occurred indicating that the calculation failed. This issue has been resolved. | DE120290 | ||||||||||||||||||||||||
| Previously, when you calculated an asset corrosion analysis in Thickness Monitoring, where the Maximum Allowable Working Pressure (MAWP) was calculated against the Thickness Measurement Locations, the following error was logged in the application log file even though the calculation of the MAWP was successful: System.Xml.XmlException: Root element is missing This issue has been resolved. | DE118767 | ||||||||||||||||||||||||
|
Previously, when you selected a Thickness Measurement Location (TML) group from the Analysis Overview page, and then selected the Organize TMLs option, the TMLs present in the selected TML Group were displayed along with the TMLs from the other TML Groups in the Organize TMLs section. This issue has been resolved. Now, the TMLs from the selected TML Group does not display in the Organize TMLs section. | DE83358 |