V4.6.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 usability, you can now manage the state recommendations directly from the Recommendation panel. | US498684 |
In the Rounds Pro module, you can now implement an action using one of the following methods:
| US490809 |
You can now edit recommendations even if the EAM Notification is sent to the EAM system and completed in SAP. To facilitate this enhancement, the following changes have been made:
| US488762 |
| To improve usability, you can now manage the state assignments for a recommended action in the Recommended Actions pane. To facilitate this enhancement, the State drop-down menu has been added to the Recommended Actions pane. | US484631 |
You can now export Recommended Actions to an Excel file. To facilitate this enhancement, the Export button  has been added to the Recommended Actions section. | US484091 |
| You can now access the work management items in the SAP web GUI from the EAM Plan or EAM Plan Details record. To facilitate this enhancement, a URL is provided for each item that connects to the SAP web GUI. | US325245 |
| Description | Tracking ID |
|---|---|
| Previously, the Recommendation dialog was not closed when you selected the hyperlink from the recommendation datasheet. This issue has been resolved. | DE160417 |
| Previously, in the results grid, if the value in the Headline column was long, the column width was extended instead of truncating the recommendation value. This issue has been resolved. | DE154373 |
APM Connect
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The Data Loaders V2 module has been introduced. You can use this module with the enhanced ability to load assets into the APM environment. The APM Family Data Loader that is used to ingest assets into APM has been rearchitected to improve reliability and performance. The new framework is more performant and aligns with the future direction of APM. | F59536 |
| Description | Tracking ID |
|---|---|
| Previously, since there was no validation of connectionString to the APM Connect Server, you could enter a malicious connectionString and capture credentials to the APMC Staging Database. This issue has been resolved. | DE154306 |
| Previously, for a family field with numeric data type, if the value was set to 0, the APM Family Data Loader could not update this value to NULL. This issue has been resolved. | DE146802 |
| Previously, when you accessed Work Management Interface and attempted to generate APM inspection tasks for SAP strategy maintenance plans, the next inspection due date was incorrectly calculated. This issue has been resolved. | DE145957 |
APM Mobile Application
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you used a comma based decimal separator in the localized numeric value, the readings field did not respond correctly. This issue has been resolved. | DE161750 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve usability, you can now apply an Asset Template to multiple assets when sending assets to the FMEA Analysis. | US498016 |
| To improve usability, a new window, Confirm Bulk Assessment?, now appears when you perform bulk assessment to assess the criticality of the assets assigned to the ACA via the Criticality Checklist or via the Risk Matrix. | US497488 |
| To improve performance, the process of deleting an analysis has been converted to a background job. | US484617 |
The ability to perform criticality assessment on a system has been enhanced. To facilitate this enhancement, the following changes have been made:
Note: This feature is available only for sites using the risk matrix method for criticality assessment. | US484487 |
| To improve usability, you can now configure and manage the ACA Criticality Definitions from the ACA Admin page in the Application Settings. | US484094 |
You can now clear the criticality assessments for one or more assets. To facilitate this enhancement, a new button, Clear Assessment  has been added in the Assessment workspace for the analysis. | US484015 |
The ability to send an asset to System Strategy has been enhanced. To facilitate this enhancement, the following changes have been made:
| US465066 |
To enhance usability, you can now access the ACA Summary Report from the Analyses workspace. To facilitate this enhancement, the View Report option has been added to the More Options ( ) menu. | US433974 |
| To improve usability, in the Asset Criticality Overview page, the Criticality Distribution graph now displays Assessed instead of Defined and Not Assessed instead of Undefined. | US388927 |
| You can now view the criticality of an asset in SAP. To facilitate this enhancement, a new column EAM Criticality has been added to the Assessment tab. | US315537 |
| Description | Tracking ID |
|---|---|
| Previously, in an existing Asset Criticality Analysis you could change the site. This issue has been resolved. | DE170529 |
| Previously, in an Asset Criticality Analysis with multiple assets, when you attempted to filter it to one assessment, the Apply Assessment button was disabled. This issue has been resolved. | DE162547 |
| Previously, the status of Update SAP job overlapped with the status of Send To job. This issue has been resolved. | DE162487 |
| Previously, if ACA was configured to use Checklist Family and State Management functionality was enabled on Criticality Checklist Family, an error occurred when you opened an existing assessment for an asset. This issue has been resolved. | DE159580 |
| Previously, in the Risk Assessment window, if the value in the Basis for Assessment box was in any language other than English, the value appeared incorrectly. This issue has been resolved. | DE158055 |
| Previously, in the Analyses section of the ACA Overview page, when you specified a filter criterion in the Criticality column, the data in the grid was not filtered based on the filter criterion. This issue has been resolved. | DE157835 |
| Previously, when you added, linked, unlinked, or deleted the reference document, the Reference Documents tab that displayed the available number of reference documents was not updated. This issue has been resolved. | DE152268 |
| Previously, users with view-only access to ACA module (MI ACA Member), could see the team member remove icon. This issue has been resolved. Now the icon is disabled for users with view-only access. | DE139166 |
Asset Health Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you created a new Health Indicator Mapping that used readings from the same relationship family as an existing Health Indicator Mapping, an error may have occurred during Health Service update process. This issue has been resolved. | DE163641 |
| Previously, when you used OT Connect data to visualize trends for a health indicator, and if you accessed the reading history of the health indicator, the oldest reading appeared at the top. This issue has been resolved. Now, the readings are sorted in ascending order, with the most recent reading at the top. | DE157900 |
Asset Hierarchy
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to create a query-based Asset Group using a query that returned a large number of results, an error occurred, and the group was not saved. This issue has been resolved. | DE164894 |
| Previously, when you accessed the asset hierarchy selector in a modal dialog, and you attempted to search for an asset group, the list of all asset groups was displayed in addition to the search results. This resulted in usability issues. This issue has been resolved. Now, only the search results are displayed. | DE162993 |
| Previously, when you searched for an asset in the Asset Hierarchy, the search failed if more than 2100 assets matched the search term. This issue has been resolved. | DE162129 |
| Previously, when you added a new datasource, the Asset Hierarchy service repeatedly logged an error that the new datasource was invalid even though it was valid which increased the logs in the log file rapidly. This issue has been resolved. | DE160478 |
Asset Strategy Implementation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance the readability, in the ASI Package workspace, when you select the Manage Maintenance Package field, the Manage Maintenance window now displays the maintenance cycle text along with the package number. | US491126 |
| To improve usability, you can now create multiple Object List Items for a Maintenance Item. | US484630 |
| To enhance the usability and performance, you can now import multiple Object List Items for Equipment or Functional Location for a given Maintenance Item. This import functionality has been implemented to run as a background job. | US274702 |
| To improve performance, Action implementations will now relate to the Action family instead of the Action Revision family. | DE157745 |
| Description | Tracking ID |
|---|---|
| Previously, when the PRT feature was enabled, the Unlink Implementation option was not available in the Manage Actions section of a package. This issue has been resolved. | US499494 |
| Previously, when you updated an ASI Package with changes to its maintenance item, the Last Changed Date of its corresponding maintenance plan was also updated in SAP. This issue has been resolved. Note: For this change to take effect, SAP notes 3062714 and 3071508 are required. | US469281 |
| Previously, the standard texts were incorrectly sent to SAP during package implementation. This issue has been resolved. | US440329 |
| Previously, as a non-English language user, when you attempted to transmit data to and from SAP, an error occurred. This issue has been resolved. | DE169536 |
| Previously, in an ASI Package, when you imported an operation with maintenance package, some maintenance packages were not imported as expected. This issue has been resolved. | DE168519 |
| Previously, in an ASI package, when you imported an operation that included materials, duplicate material entries were created. This issue has been resolved. | DE167224 |
| Previously, when you attempted to delete a custom work management record, an error occurred. This issue has been resolved. | DE163117 |
| Previously, when you attempted to create a new package and save it, the Details section did not load. This issue has been resolved. | DE159080 |
| Previously, when you deleted a Maintenance Plan from the Work Management Item (WMI) tree associated with an ASI Package, the actions associated with the child maintenance items were not unlinked. This issue has been resolved. | DE158070 |
| Previously, there were performance issues while loading maintenance item datasheet. This issue has been resolved. | DE158068 |
| Previously, if your culture setting had a culture other than English, when you attempted to add Task List from SAP in ASI package, the GE Digital APM application did not respond. This issue has been resolved. | DE158063 |
| Previously, when you attempted to add an Operation to an ASI Implementation Package, APM stopped responding. This issue has been resolved. | DE158062 |
| Previously, when you linked an Action to an operation or maintenance item, the Action name did not appear in the WMI tree. This issue has been resolved. | DE158061 |
| Previously, the Operation description did not appear in the Operation name in the WMI hierarchy, if the operation description had special characters, < or >. This issue has been resolved. | DE158060 |
| Previously, in an ASI package, if you navigated quickly through the tree hierarchy, the datasheet and add children options were not in synchronization with the selection. This issue has been resolved. | DE158046 |
| Previously, in an ASI Package, you were able to select values in the Work Unit and Normal Duration Unit even when the fields were disabled in the operation datasheet. This issue has been resolved. | DE157905 |
| Previously, in ASI Package, when you created a maintenance item and selected an Equipment that was associated with a Functional Location that had an ampersand (&) in its name, an error message appeared indicating that the selected value is invalid. This issue has been resolved. | DE153580 |
| Previously, when you modified long text in the Notification datasheet in ASI, the updated text was incorrectly appended to the existing text in the Notification datasheet in SAP. This issue has been resolved. Now, when you modify the long text, it is overwritten in the Notification datasheet in SAP. | DE109896 |
Asset Strategy Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
In the Rounds Pro module, you can now implement an action using one of the following methods:
| US490809 |
| To improve performance, the strategy or template deletion job has been converted to a background job. You can now view the status of the delete job under the job status component. Additionally, you can now delete multiple strategies or templates from the ASM Overview page. | US489964 |
| You can now view the EAM plans imported to the APM. To facilitate this enhancement, the EAM Plans tab is added in the ASM Overview page. | US487027 |
| APM now delivers an improved performance when you attempt to add assets during the creation of a strategy. To facilitate this enhancement, a new window, Select Asset, now appears when you select Create Asset Strategy in the ASM Overview page. | US484612 |
| To improve performance, in the ASM Overview page, the query for ACTIVE ACTIONS BY SOURCE graph has been optimized. | US484610 |
| To improve usability, the search functionality has been introduced for risks and actions. To facilitate this enhancement, a Search box has been added in Risks and Actions workspace. | US484559 |
| To improve usability, the Template ID column has been added to the Asset Strategies section of the ASM Overview page. If a strategy is controlled by a master template, the ID of the template with a link appears in the header section of the ASM Overview page. | US484089 |
| To enhance usability, the hierarchical vertical navigation pane to the left has been converted to a horizontal navigation. | US397809 |
| To enhance usability, the Strategy Identification tab and the Strategy Overview tab have been interchanged. In addition, the Strategy Overview tab and Strategy Identification tab have been renamed to Summary and Details respectively. | US388158 |
| To improve performance, Action implementations will now relate to the Action family instead of the Action Revision family. For more information on Catalog Queries, refer to KBA 000038716. | DE157745 US512870 |
| Description | Tracking ID |
|---|---|
| Previously, when you unconsolidated one or more mitigating Actions, the links between the Actions and Risks were not restored. This issue has been resolved. | US484628 |
| Previously, in Risks and Mitigating Actions cards, the risk values expressed in decimal format were not rounded as expected. This issue has been resolved. | US484111 |
| Previously, the save as template functionality had performance issues. These issues have been resolved. | US347545 |
| Previously, if your culture setting was Japanese, the Description field available in the Link Existing section of the Send to ASI Package window was displayed as MI_IMPPACKG_DESC_T. This issue has been resolved. Now, the Description field name is localized. | DE486503 |
| Previously, the Import button was enabled even for the users with view-only access. This issue has been resolved. Now, the button is disabled for users with view-only access. | DE165797 |
| Previously, in Revisions section of asset strategy, the ID column on the Risks Revision tab was populated incorrectly. This issue has been resolved. | DE165974 |
| Previously, in the Secondary Actions section of the Risks and Actions workspace of a strategy, the number of secondary actions associated with the primary action was displayed incorrectly. This issue has been resolved. | DE165935 |
| Previously, Asset Strategy Approval report had some alignment issues. These issues have been resolved. | DE162354 |
| Previously, when importing actions from Rounds, some measurement locations were not listed for the selected route. This issue has been resolved. | DE162007 |
| Previously, when you created an Asset Strategy from the master template, the Risks did not populate correctly. This issue has been resolved. | DE161787 |
| Previously, if the value of the Culture field in your user settings was set to Spanish, and you attempted to apply an ASM Template to the available assets, an error occurred. This issue has been resolved. | DE159771 |
| Previously, if the risk matrix categories contained a hyphen (-) character, and you attempted to load data through the ASM data loader, an error occurred. This issue has been resolved. | DE158549 |
| Previously, in the Recommended Actions pane, you could modify data in the Implementation Alert box even when the Alert Responsible Party When Due? check box was cleared. This issue has been resolved. Now, in this scenario, you cannot modify data in the Implementation Alert box. | DE158193 |
| Previously, in the ASM Overview page, the Import from Rounds feature was enabled even though the Operator Rounds license was not active in the APM. This issue has been resolved. | DE158067 |
| Previously, when using the Import from EAM feature, you could update a strategy that was controlled by a master template. This has been resolved. | DE157906 |
| Previously, in the Risks and Actions workspace of the Strategy Details workspace, the name of the button, Consolidate, which was used to supersede actions was incorrect. This issue has been resolved. Now, the action Consolidate has been renamed to Supersede across the Asset Strategy Management module. | DE157904 |
| Previously, when you attempted to export one or more Asset Strategies that were controlled by a master template, an error occurred. This issue has been resolved. Now, an appropriate error message appears, and you can use the new Template ID column to filter the controlled strategies based on your selection. | DE157903 |
| Previously, saving an action in a strategy took a long time. This issue has been resolved. | DE157887 |
Asset Strategy Optimization
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, after strategy optimization, the unit for the Interval Units field was getting modified to Days, irrespective of the actual unit set in the strategy. This issue has been resolved. Now, the unit for the Interval Units field in ASO matches the Units field in the strategy. If no action interval is available, the default unit is set to Months. | DE160754 |
Calibration Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
You can now generate and download multiple Calibration Template Reports or Calibration Event reports at a time. To facilitate this enhancement:
| US492248 |
| You can now validate the calibration template records before you download the records to the calibrator. To facilitate this enhancement, the Validate button has been added to the Send for Calibration window. You can select Validate to identify the errors or warnings in each template. You can also view the errors or warnings in the Device Log window or in the log file of the Meridium Device Service. | US484999 |
| You can now exclude an asset-specific applied profile from getting updated when the related profile template is updated. In addition, you can now choose which data in the profile template gets updated to the applied profile. | US483331 |
) is added in the | Description | Tracking ID |
|---|---|
| Previously, you could not modify the fields in the applied equipment profile template datasheet. This issue has been resolved. Now, the fields in the datasheet are enabled for editing. In addition, the datasheet selection control to select other datasheets has been enabled. | US483332 |
| Previously, when you created an Applied Profile Template of type Analog-Manual with the Perform Square Root field value set to Yes, the values in the Percent of Scale Test Point field in the Template Detail records were generated as linear values. This issue has been fixed. Now, the test point values are generated as square root values. | DE169615 |
| Previously, when you created a Functional Test Calibration template, you were not able to add more than 25 steps to the template. This issue has been resolved. Now, you can add additional steps by creating calibration strategies. | DE162191 |
| Previously, when you entered values (As Found or As Left) in a Single Switch Discrete Calibration event result, which calculated the AF error % or AL error % to zero, the Overall AF Pass/Fail or Overall AL Pass/Fail result did not show as either PASS or FAIL. This issue has been resolved. | DE161826 |
| Previously, some URLs in the Calibration Management URLs section were incorrect. This issue has been resolved. | DE161513 |
| Previously, if your culture setting had a culture other than English, when you sent data to a Fluke 754 calibrator using a template, the data in the Fluke 754 calibrator device contained invalid characters. This issue has been resolved. | DE160377 |
| Previously, the Associated Pages functionality for Calibration Event, Calibration Results, Calibration Template, Calibration Template Detail, Standard Gas Cylinder, and Standard Gas Components families was not working as expected. This issue has been resolved. The Associated Pages functionality has now been removed for these families. Note: This functionality can be achieved using the normal Calibration workflow. | DE157634 |
| Description | Tracking ID |
|---|---|
| The Calibration Template Bulk Report and Calibration Event Bulk Report and their associated queries are no longer used and have been removed from the database. Previously, for the Combined Report feature, the Calibration Template Bulk Report and Calibration Event Bulk Report were used to combine the individual reports into a single file. Now, the default reports generated for each selected Calibration families are combined into a single PDF file. Also, the MHTML file type is no longer supported to view or download the Combined Report. | US507332 |
Compliance Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you approved an Inspection Plan with a Superseded Master Recommended Action in the Not Required state, an action was erroneously created and linked to the Master Recommended Action. This issue has been resolved. Now, when you approve an Inspection Plan, no actions are created for Recommended Actions in the Not Required state. | DE165764 |
| Previously, for an Inspection Plan, when you were viewing the Linked Recommendations window for a recommendation that was superseding at least one other recommendation, duplicate recommendations appeared. This issue has been resolved. | DE165397 |
| Previously, users with the MI Inspection Plan Approver group permissions added to their security roles were unable to approve an Inspection Plan. This issue has been resolved. | DE161150 |
| Previously, when you created or updated an Inspection Plan based on a Compliance Strategy Template, and executed a policy associated with the template, no error message appeared if the returned output node value did not match the Compliance Strategy ID field value of the associated Compliance Strategy records. This issue has been resolved. | DE159036 |
Data Sources
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve usability, in APM Classic, if the Data Source section contains invalid data source(s), all the invalid data sources are made offline and are not available for selection. | US186051 |
Datasets
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you imported a dataset using an Excel file, if the file contained formula field, the values in the field were imported as formulas instead of computed values. This issue has been resolved. | DE157828 |
| Previously, when you exported numeric values that contained a decimal from a German dataset, the number did not retain the decimal points. This issue has been resolved. | DE156430 |
eLog
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve usability, when linking an asset to a general log entry associated with a shift, the functional location associated with the shift is automatically selected as the hierarchy level in the Asset Finder window. This allows the team members associated with the shift to easily find the assets available in their production unit. | US485307 |
| To improve usability in the eLog Admin pages, you can now create a custom family name as a child of the eLog Assignment Family and add a drop-down picklist to the assignment template forms. | US485280 |
| The shift filter has now been added to the Record of Assignments and Shift Sign-In/Out Logs tables in the eLog Shift Report. You can access the details about the source of log entries in the report. | US477510 |
To enhance usability, in the Templates section of the eLog Administrator page, in the Generated On dropdown list, the following options have been added:
| US468340 |
Failure Modes and Effects Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To enhance the usability of the baseline datasheet, the following fields have been removed:
| US485341 |
| The performance when adding assets to an analysis for assessment has been improved. To facilitate this enhancement, a new window, Add Assets, now appears when you attempt to add assets to an analysis. | US484611 |
| To improve performance, the Save as Template functionality has been converted to a background job. In case of an error, the corresponding details are now available in the job status, which appears in a separate window on the same page. | US484123 |
| To improve usability, you can now apply an Asset template to multiple assets at the same time. | US424474 |
| Description | Tracking ID |
|---|---|
| Previously, the Decision Logic Builder was not working as expected. This issue has been resolved. | DE170570 |
| Previously, you could consolidate recommendations linked to different assets in FMEA. This issue has been resolved. | DE166051 |
Previously, when you uploaded the RCM Template,
FMEA Analysis Template, or FMEA Asset Template through the data loader, a warning message was displayed for the below fields:
| DE161367 |
| Previously, users with MI RCM User security group permission were unable to access the FMEA analysis. This issue has been resolved. | DE160674 |
| Previously, when you uploaded data using data loader, financial details were not updated as per the dataloader worksheet. This issue has been resolved. | DE158069 |
| Previously, in the FMEA Analysis Details section, when you accessed the Risk card of the Failure Effect, the Risk Category ID appeared instead of the Description alias. This issue has been resolved. | DE154478 |
Family Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you configured the family metadata, and if the corresponding configurations changed during the runtime, the family metadata became stale. This issue has been resolved. | DE169671 |
| Previously, for workflow use cases where Many to Many relationships with large number of updates were processed, an error may have occurred. This issue has been resolved. | DE159157 |
| Previously, when you attempted to update the Template ID, you had to save the changes twice to see the updates across all the family records. This issue has been resolved. | DE157815 |
Family Policies
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, the execution duration for each node is now displayed in a policy. When you select each node of a policy in Validation mode or in Execution History view mode, the Node Execution Details window displays the Execution duration. | US491145 |
| To improve the usability of the Execution History pane, the execution summary now displays links to the first five entities created by a Create Entity node. Note: You can access the links to all the created entities by selecting the Create Entity node in the execution history details displayed on the policy canvas. | US475170 |
| Description | Tracking ID |
|---|---|
| Previously, when you executed a policy that called a sub policy that contained a Create Entity node, if the entity was not created due to an error on another node, the execution details in the Create Entity node were incorrect. This issue has been resolved. | DE168085 |
| Previously, if your APM system used the Machine Learning Server to execute R Scripts, and you executed or validated a policy where the R Script had an error, the R Script node did not show the error message and null output values were passed to any successor nodes in the policy. This issue has been resolved. Now, the R Script node shows an error message, the successor nodes are not executed, and the policy execution results in an error. | DE163897 |
Previously, the Constant node icon size did not match with the other icons in the application. This issue has been resolved. The icon for the Constant node has been updated to  . | DE163680 |
| Previously, when you selected Policy Recommendation, Production Event or Health Indicator Value in the Family ID section of a Create Entity node, and then added a new Create Recommendation, Create Production Event or Add Value to Health Indicator node, respectively, the fields in the new node were not displayed as expected. This issue has been resolved. | DE144639 |
Foundation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to transition the state of a record, the users in the state assignment drop-down list box were loaded all at once, which resulted in performance issues. This issue has been resolved. Now, the list of users is loaded and displayed as you scroll, and is now searchable. | DE161669 |
| Previously, if your language settings and culture settings in the APM application were not the same, the decimal separators did not appear correctly in the values for the field to which business rules were applied. This issue has been resolved. | DE158499 |
General Dashboards
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To improve usability, in the edit mode, you can now open the selected filter query in the query design page from the dashboard. To facilitate this enhancement, the Open in New Tab ( ) button has been added to the Filter Query section. | US508136 |
| You can now open a graph from the Edit Widget window in the Graph Result workspace . To facilitate this enhancement, a new button Open in Graph Editor () is added in the Edit Widget window. | US497983 |
| You can now open a query from the Edit Widget window in the Design workspace. To facilitate this enhancement, a new button Open in Query Editor () is added in the Edit Widget window. | US497981 |
| To enhance usability, when you select the Open in New Tab () button in a query widget, the query now opens in the results-only view and the currently selected dashboard filter parameter values are automatically applied to the query. | US483540 |
| You can now export the results of any query directly from the dashboard. To facilitate this enhancement, a new option, Export all data has been added in the Query widget, under More button (). | US483539 |
You can now specify the parameter values for a multi-value filter in the URL while accessing a dashboard via a hyperlink. To facilitate this enhancement, the following URL formats with Parameter Name[] are now supported for accessing a dashboard:
| DE164609 |
| Description | Tracking ID |
|---|---|
| Previously, you could enter an invalid value and save the Filter Query field in a dashboard. This issue has been resolved. Now, you must select the Select a Query button and choose the filter query in the Select an APM Query from the Catalog window. | DE113032 |
| Previously, when you selected the Open in New Tab button () in a graph widget, the graph opened in the same tab as the dashboard. You could not access the dashboard at the same time. This issue has been resolved. Now, the graph opens in a new view-only tab, based on the selected dashboard filter parameters. | US497986 |
| Previously, when a dashboard used a filter query that contained an asset hierarchy (:ah) filter parameter, and you accessed it using a URL that specified the key of the asset (for example, #dashboard/64252603546?asset=345728389), the dashboard did not display the specified asset unless the parameter ID was entityKey or enty_key. This issue has been resolved. Now, the dashboard displays the specified asset regardless of the parameter ID used in the filter query. | US489039 |
| Previously, when the date filter parameter was set, both the date and the default time (00:00:00) were displayed in the dashboard heading. This issue has been resolved. Now, when the date option is selected, only the date is displayed. | US483541 |
| Previously, if you accessed a dashboard using a URL that specified filter parameter values, for example, #dashboard/64252603546?asset=345728389&days=90, the specified values may have been overridden by the global asset context or your stored user preferences. If you then attempted to change the values in the Enter Parameter Values window, the parameters values were reverted to the values specified in the URL. These issues have been resolved. Now, if you access the dashboard using a URL that specifies filter parameter values, these values take precedence over any stored preferences, default parameter values, and the global asset context. You can then change the filter parameter values in the Enter Parameter Values window and select Done to update the data displayed in the dashboard. Note: The filter parameters are also applied when you use a URL that specifies parameter values to access a graph, for example #graph-preview/64252603546?asset=345728389&days=90, a query, for example #qdetail/64252603546?asset=345728389&days=90), or, when you open a graph or query in a new tab from the dashboard widget. | US433974 |
| Previously, when you navigated to a dashboard tab that was already open, the graph widget in the dashboard did not display as expected. This issue has been resolved. | DE171544 |
| Previously, when you configured a Graph widget on a dashboard to use a multi-value filter parameter, and then opened the graph in a new tab, an error occurred. The selected parameter values were not applied to the graph. This issue has been resolved. | DE158984 |
| Previously, when you accessed the calendar in a new tab, you could not scroll down to view the full list of the event categories, if there were multiple categories. This issue has been resolved. | DE152911 |
| Previously, when you configured the Calendar widget, in the Edit Widget window, when you selected a query with an aggregate function, you were unable to select any values in the fields appearing in the Event Mappings section. This issue has been resolved. | DE150934 |
| Previously, when you accessed APM, if the dashboard or metrics view that was previously configured as your home page was no longer accessible, a script error occurred. This issue has been resolved. Now, in this scenario a message appears specifying the issue. | DE138719 |
Generation Availability Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now view Event Number for the corresponding event in the NERC GADS Event Report 07. By default, the Event Number field in an event report shows sequential numbers. To facilitate this enhancement, a new query, Get the Record Order Preference for Event Report, has been added to the Catalog folder \\Public\Meridium\Modules\Generation Management\Queries. You can now modify the query to return Event ID for the Event Number field. For more information on modifying the query, refer to KBA 000037247. | US492759 |
| To enhance usability, in the HEADER and TRAILER fields of the CEA Event Report, value from the Primary Utility Code field is included instead of value from the Company Name field. | US489816 |
| To enhance performance, in CEA Events, when the state of the event is moved to Unit Approved, for the CEA Event Types 11-1,11-2,14,14-1,14-2, the Cause Code System, Cause Code Component, Cause Code, Amplification Code, and Verbal Description fields in the Primary Event datasheet are no longer required fields. For more information on modifying the query, refer to KBA 000037693. | US489811 |
| Description | Tracking ID |
|---|---|
| Previously, when you created a primary event with an Event Start Date value as the first or the last date of the month, the capacity values populated from the unit capacity record would not get populated as expected. This issue has been resolved. Now, irrespective of your time zone while creating a primary event, the capacity values get populated for all the Event Start Date. | DE163196 |
| Previously, when you created a Primary Event record, and then selected an event type, the value of the fields Gross Available Capacity and Net Available Capacity were calculated incorrectly. This issue has been resolved. | DE160176 |
Graphs
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, you can now open a graph for editing in the Graph Result workspace from the view-only graph page. To facilitate this enhancement, the Open in Graph Editor
button has been added to the view-only graph page. | US497984 |
| To enhance usability, the display order for legend entries in a horizontal bar graph has changed. Now, the first entry in the legend represents the top bar in a clustered bar graph or the left segment in a stacked bar graph. | US489988 |
| To enhance usability, in a Graph, when you select a hyperlinked area or a point that references another Graph, the hyperlinked Graph now opens in a new tab. | US487712 |
| Description | Tracking ID |
|---|---|
| Previously, if you selected a series that included zero values in a bar graph, nothing was displayed for the zero values. This issue has been resolved. Now, a single width line appears with a tooltip that shows the zero value when you hover over the line. | US501452 |
| Previously, when you created a Stock Chart Graph, and selected the Stack Tool tips option, the tooltips were incorrectly displayed. This issue has been resolved. | DE117569 |
Hazards Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to add a team member to a Hazard Analysis (HAZOP and What If), users across all sites were displayed. This issue has been resolved. Now, only the users linked with the site of the Hazard Analysis are displayed. | US483320 |
| Previously, when you attempted to create the first System/Node for a HAZOP Analysis or a What If Analysis, an error occurred intermittently. This issue has been resolved. | DE159426 |
| Previously, when creating a Risk Assessment Recommendation, the Functional Location ID box in the General Information section was incorrectly populated with the key associated with the functional location instead of the ID of the functional location. This issue has been resolved. | DE157635 |
Previously, when you attempted to promote a recommendation to ASM, a blank message appeared in the following scenarios:
These issues have been resolved. | DE157630 |
Import and Export
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now save the selected metadata items into an export template and reuse the template while exporting the metadata. To facilitate this enhancement, the Save as Template option is added to the export page. You can view a saved template using the Select a Template option. | US489934 |
| Description | Tracking ID |
|---|---|
| Previously, when you were connected to an Oracle Database, and then imported a family for which State Functionality was enabled, the import failed. This issue has been resolved. | DE167586 |
| Previously, the import and export schedule logs were not sorted as per the start time. This issue has been resolved. Now, the logs are sorted in ascending order, with the most recent schedule at the bottom. | DE158317 |
Inspection Field Data Collection
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you added a system code to a drop-down list box associated with the Checklist Finding family, and then added the drop-down list box to an offline form associated with the family, the system code value did not appear in the drop-down list box, when you accessed an inspection for the family in the Inspection Field Data Collection page. This issue has been resolved. | DE167899 |
Inspection Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
The following enhancements have been added to capture the asset health information in the Inspection Management module:
| F61227 |
To enhance the usability, Inspection ID has been added to the following reports:
| US491005 |
The following enhancements have been added to European Inspection Management:
| US488180 |
The following enhancements have been added to Work Packs:
|
|
To enhance the usability of viewing images created using the mobile Field Data Collection feature, or created manually as reference documents, the following enhancements have been made:
| US481174 |
You can now generate and download multiple Inspection Reports at a time. To facilitate this enhancement:
| US480277 |
You can now embed image files under the Reference Images section in the printed reports of the following Baseline Checklist Inspection families:
| US467663 |
You can now configure the %TimeOut; within the SSRS section in appsettings.json. The default TimeOut is set to 60 minutes. | DE165612 |
| Description | Tracking ID | ||||||
|---|---|---|---|---|---|---|---|
| Previously, if you did not have an active Risk Based Inspection license, and you attempted to open an inspection record, an error was incorrectly logged in the MI_EXCEPTION_LOG_ENTRIES table. This issue has been resolved. | DE169120 | ||||||
| Previously, in the IM Admin Preferences, when you modified the options in the Date Filter section of the Overview Configuration page and saved them, a message indicating a successful save appeared. However, the changes were not saved and when you refreshed the page, the values reverted to the previous settings. This issue has been resolved. | DE165869 | ||||||
| Previously, for non-reoccurring Inspection Tasks, the Task Execution records were not created when you selected the Inspection Task Complete option for the associated inspection event. This issue has been resolved. | DE163900 | ||||||
Previously, some queries incorrectly included direct joins to the Equipment family. This issue has been resolved. Now, Inspection Management supports both Equipment and Functional Location families in the baseline product and these queries have been corrected. The following table provides a comprehensive list of the queries affected and their corresponding Inspection Management Overview widget or tile by title.
| DE157675 | ||||||
| Previously, in the Inspection Confidence Evaluation record, the values in the Type of Inspection field were not sorted alphabetically. This issue has been resolved. | DE157674 | ||||||
| Previously, when you attempted to access an Asset Technical Data record using global search, an error occurred. This issue has been resolved. | DE157666 | ||||||
| Previously, when you were switching from one tab to another in an inspection event, if there was any unsaved data in the tabs, the Save window did not appear consistently. This issue has been resolved now. | DE154418 |
| Description | Tracking ID |
|---|---|
The Combined Bulk Inspection Report in the following path is no longer used and has been removed from the database.Also, the MHTML file format is no longer supported to view and download the files. | US504783 |
Installation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in the MeridiumAppSettings file, you were unable to encrypt your Redis password using the MeridiumCachePasswordUtility.exe, when the password included a special character. This issue has been resolved. | DE157817 |
Layers of Protection Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you changed the state of a Layers of Protection Analysis (LOPA) from Planning to another state, the IPL Checklist datasheet was not disabled. This issue has been resolved. | DE157928 |
| Previously, when you upgraded the APM from V3.6 to V4.5 and you attempted to modify the Layers of Protection Analysis, the Calculated SIL value changed. This issue has been resolved. | DE157636 |
| Previously, in the IPL Checklist section of the Safeguard and IPLs workspace, the value displayed in the PFD field while loading was the calculated value instead of the database value. This issue has been resolved. | DE157623 |
Life Cycle Cost Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now navigate through the fields in the datasheet for creating an LCC Analysis using the Tab key on the keyboard. | US484617 |
| Description | Tracking ID |
|---|---|
| Previously, in the Analysis Summary page, a newly added scenario was displayed at the beginning in the scenarios list. This issue has been resolved. Now, the newly added scenario is appended at the end in the scenarios list. | US485081 |
| Previously, when you attempted to update a profile in a scenario and left the page without saving the changes, the profile was not updated. This issue has been resolved. Now, when you leave the page without saving, an Unsaved Changes window appears prompting you to save the changes. | US483931 |
| Previously, in the result grid for an Operating Costs Breakdown chart, you could not see the Scenario Element for which the Operating Cost was being displayed. This issue has been resolved. Now, an additional column has been added which identifies the Scenario Element for the displayed costs. | US473595 |
| Previously, you could not modify an LCC Recommendation in which the Target Completion Date was in the past. This issue has been resolved. | DE166383 |
| Previously, as a non-English language user, you were unable to apply Declining Balance Factor for the Depreciation Method. This issue has been resolved. | DE163497 |
| Previously, in the LCC Analysis Overview workspace, the results grid for the Total Costs chart was not populated with data. This issue has been resolved. | DE162408 |
| Previously, in the Analysis Summary page, when you imported valid secondary elements into a scenario, the imported elements could not be saved. This issue has been resolved. | DE159312 |
| Previously, in the Equivalent Unit Cost Chart (EUC) of Analysis Summary page, the result grid for the data displayed an incorrect column header, Depreciated Value. This issue has been resolved. The column header is now updated to Equivalent Unit Cost. | DE159282 |
Manage Translations
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
Previously, the following issues existed in localization:
| DE162547 |
Management of Change
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to add a team member to a Change Project, users across all sites were displayed. This issue has been resolved. Now, only the users linked with the site of the Change Project are displayed. | US483323 |
Maps
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when your APM system used an Oracle schema, and you updated the GIS Configuration, the new settings were not applied. This issue has been resolved. | DE159225 |
Maximo Adapters
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to use the Unified Asset Ingestion Data Loader to load Maximo assets or Functional Locations into the APM, the Predix Asset Model was incorrectly populated with the Unique ID instead of the Equipment ID or the Functional Location ID. This issue has been resolved. | US496687 |
Metrics and Scorecards
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| In the Scorecard Details page, the Scorecard view that you select is now saved as your user preference. | US484428 |
| In the tabular view of the History of a KPI, you can now view the date in either the User Timezone or in the UTC timezone. To facilitate this enhancement, a KPI Time Preference setting has been added in the Metrics and Scorecard Application Settings, where you can set the time preference as required. | US516741 |
| Description | Tracking ID |
|---|---|
| Previously, when you accessed the Drilldown feature in a Metric View, extraneous characters were displayed between the navigation links. This issue has been resolved. | DE167192 |
| Previously, a security user who was assigned to MI Metrics Viewer security group and another group with more privileges (for example, MI Metrics User security group), could not create a KPI. This issue has been resolved. | DE160309 |
| Previously, when accessing a metric view, if you switched between the graph view and the tabular view, the tabular view displayed the US Dollar ($) regardless of the culture or the language setting. This issue has been resolved. | DE158621 |
| Previously, when creating a KPI, if you used APM query in the Data Source Type field and selected values for the Worst Value, Critical Value, Target Value, Stretch Value, and Best Value fields from their respective drop-down list boxes, and then attempted to view KPI in the KPI viewer after refreshing the KPI, the values were not displayed on the chart. However, when you entered the field values manually and switched to the KPI viewer and refreshed the KPI, the values on the chart appeared correctly. This issue has been resolved. | DE158315 |
Mobile Proof Testing
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you closed the Proof Test workspace, values in some fields (for example, Step Sequence Number) were cleared. This issue has been resolved. | DE159507 |
Policy Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, the execution duration for each node is now displayed in a policy. When you select each node of a policy in Validation mode or in Execution History view mode, the Node Execution Details window displays the Execution duration. | US491145 |
| You can now copy a policy instance from an existing saved policy instance. To facilitate this enhancement, a Duplicate option has been added to the Instance workspace. | US491141 |
| To enhance usability, a new dashboard, Recent Policy Executions has been added to the General Dashboards. Using this dashboard, you can monitor the completion of policy executions and queue wait times. To facilitate this enhancement, the new dashboard and supporting queries have been added to the Catalog folder \\Public\Meridium\Modules\Policy Manager. |
US500241 US486832 |
| You can now view a graph showing the average and maximum Time in Queue (time taken from Trigger Sent Time to Execution Start Time) for policies executed in the last 4 hours on the Policy Designer Overview page. To facilitate this enhancement, new graphs and queries are added to the catalog. Note: If your APM system uses an Oracle schema, you must modify the Policy Overview dashboard to use the Oracle version of the graph. | US485566 |
To improve performance, the Email node has been enhanced. You can now:
|
|
| To improve the usability of the Execution History pane, the execution summary now displays links to the first five entities created by a Create Entity node. Note: You can access the links to all the created entities by selecting the Create Entity node in the execution history details displayed on the policy canvas. | US475170 |
| You can now confirm before saving the security setting updates that will limit your access to a policy. To facilitate this enhancement, when you select Save, the Confirm Security Settings window is displayed. | US474235 |
Performance, while you perform search on the policy instance has been significantly improved. To facilitate this enhancement, the following changes have been made:
| DE170376 |
| Description | Tracking ID |
|---|---|
| Previously, the default datasheet for Policy Recommendations displayed the Alert tab, even though email notifications were not supported for Policy Recommendations. This issue has been resolved. Now, the default datasheet does not display the Alert tab. Note: If you have previously modified the default datasheet configuration, this change will not be applied automatically. | US515201 |
Previously, if your APM system contained many policy execution history records, when you accessed the Policies tab on the Policy Designer Overview, the list of policies did not load. This issue has been resolved. To facilitate this update, the default query used by the Policies tab has been modified. The following columns are no longer displayed:
Note:
| US500043 |
| Previously, when you executed a policy that called a sub policy that contained a Create Entity node, if the entity was not created due to an error on another node, the execution details in the Create Entity node were incorrect. This issue has been resolved. | DE168085 |
| Previously, when you did not have an active license for Policy Designer in your APM system, and you configured the R Server Connection to use the Machine Learning Server, an error occurred when you subsequently attempted to access the R Server Connection page. This issue has been resolved. | DE164156 |
| Previously, if your APM system used the Machine Learning Server to execute R Scripts, and you executed or validated a policy where the R Script had an error, the R Script node did not show the error message and null output values were passed to any successor nodes in the policy. This issue has been resolved. Now, the R Script node shows an error message, the successor nodes are not executed, and the policy execution results in an error. | DE163897 |
| Previously, the Constant node icon size did not match with the other icons in the application. This issue has been resolved. The icon for the Constant node has been updated to . | DE163680 |
| Previously, in the Policy Instance Data Loader, when you attempted to assign a record in a family where the Family ID differed from the Physical Table Name to a Point Value node, the policy instance was not created correctly. This issue has been resolved. | DE160265 |
| Previously, if you executed a policy where a Close Event node followed an Or node, and a calculation or comparison node preceding the same Or node was not executed due to the policy logic, an error occurred, and the policy event was not closed. This issue has been resolved. | DE159541 |
| Previously, in an Oracle schema, when you searched for a user to assign to an Instance, an error occurred. This issue has been resolved. | DE157802 |
| Previously, in an Edit Entity node, if any of the specified entity keys were not found in the specified family, an incorrect error message appeared, and the policy execution resulted in an error. This issue has been resolved. Now, a correct warning message is displayed, and the policy execution is successful. | DE157112 |
| Previously, when you selected Policy Recommendation, Production Event or Health Indicator Value in the Family ID section of a Create Entity node, and then added a new Create Recommendation, Create Production Event or Add Value to Health Indicator node, respectively, the fields in the new node were not displayed as expected. This issue has been resolved. | DE144639 |
| Previously, when your APM system contained multiple instances of the Policy Trigger service, and you added a new reading to a measurement location which was the triggering input for a policy instance, multiple executions were triggered. This issue has been resolved. | DE141928 |
| Previously, when you mapped an input with Integer datatype to an input of a Math node or a Comparison node, and an input with undefined datatype, for example, a calculated query column, to the other input, an incorrect error message appeared in the notification bar and the policy could not be activated. This issue has been resolved. | DE132771 |
Production Loss Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| A new query, GetAllPLAPolicyInstances, has been added to the Catalog folder Public\Meridium\Modules\PLA\Queries. This query enables you to populate the instances of a PLA policy in a Production Profile record. | US485272 |
| To improve usability, you can expand and collapse the Production Summary chart in the PLA Production Summary page. | US513120 |
| Description | Tracking ID |
|---|---|
| Previously, in a Production Plan, if the number of products that caused the Production Plan ID to exceed 200 characters, an error occurred, and the plan was not created. This issue has been resolved. Now, the character limit for the Production Plan ID is 1000 characters, which allows more products to be included in a Production Plan. | US488980 |
| Previously, the Data Grid column headers on the Production Data page were not translated to the local language based on your profile culture setting. This issue has been resolved. | US485290 |
| Previously, when you navigated quickly between the tabs in the Production Loss Analysis module, an error occurred. This issue has been resolved. | US483938 |
| Previously, when you regenerated a Production Plan, the value of the Plan End Time field was always set to one month after the Plan Start Time, irrespective of the initial End Time field value in the plan. This issue has been resolved. | DE159089 |
| Previously, when you attempted to link nine or more work histories to a Production Event, you could not save them because the Cancel and OK buttons were unavailable. This issue has been resolved. | DE158233 |
| Previously, when you attempted to update a Production Event record, a blank screen appeared when you saved the changes. This issue has been resolved. | DE158231 |
| Previously, in a Production Plan, you could not access the Production Event workspace when you operated on a small screen device. This issue has been resolved. Now, you can access the Production Events workspace in all supported devices. | DE158228 |
| Previously, when you attempted to unlink Production Events from Production Losses, which were related to Production Plans upgraded from previous versions of the APM, an error occurred. This issue has been resolved | DE158226 |
| Description | Tracking ID |
|---|---|
| When you attempt to create or update a Production Profile using the PLA Data Loader, the upload fails if the Product Alias field value contains a comma. Note: Do not use commas in the Product Alias field. | US505557 |
|
In the Production Summary workspace of a Production Plan, the following field headers do not appear in the APM User's local language:
In the Existing Losses window accessed from the Production Data workspace, the following field headers do not appear in APM User's local language:
In the Production Losses workspace of a Production Plan, the following field headers do not appear in APM User's local language:
| US505557 |
Queries
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, in edit mode, you can now open the selected query in the query design page from the Edit Widget window of a Calendar widget. To facilitate this enhancement, a new button, Open in New Tab () has been added to the Edit Widget window. | US508133 |
| To enhance usability, you can now open a query in the Design workspace from the results-only view. To facilitate this enhancement, a new Open in Query Editor button () has been added to the results-only view. | US497980 |
To enhance usability, you can now export a query to a file from the results-only view. To facilitate this enhancement, a new Export to a File button ( ) has been added to the results-only view. | US470779 |
| To improve usability, in APM, when you execute an append query, the query now returns error messages specific to the error. Note: If there are more than one errors, the next error message appears only when you have resolved the error that is already displayed. | US186085 |
| Description | Tracking ID |
|---|---|
| Previously, when you exported a query to a dataset using the Export to a Dataset option, the Catalog Items folder was provided as the default location to save the query results. This issue has been resolved. Now, when you export a query to a dataset, the most recent folder location is retained and provided in the Save As window. | US186122 |
| Previously, in the Query Designer page, the new fields that were added to the family when you selected Spread to Sub Families, were not displayed in the query columns (family fields). This issue has been resolved. | DE171705 |
| Previously, in the Query Designer page, when you created a manual join between two families, and then selected the fields in the query from the second family, an error occurred. This issue has been resolved. | DE170804 |
| Previously, in the Results workspace, when you attempted to search for a date in the Date column with hyperlink, the search failed to filter the results. Similarly, in the Results workspace, when you attempted to sort the Date column with hyperlink, the results did not get sorted. This issue has been resolved. | DE169088 |
| Previously, when you executed a query that used a ROUND expression that referenced a stored query, an error occurred when you attempted to sort or filter the values in the query result. This issue has been resolved. | DE163524 |
| Previously, in APM, if you reopened a criterion for a Crosstab query, an error message appeared. This issue has been resolved. | DE163612 |
| Previously, when you changed a Crosstab query into a Select query, and then changed back to the Crosstab query and executed this query, an unknown error appeared. This issue has been resolved. | DE163421 |
| Previously, when you attempted to sort the column values in the Results workspace of a distinct or union query, an error occurred. This issue has been resolved. | DE163216 |
| Previously, if you added a hyperlink in a Query, and the query result used as a parameter by the hyperlink included a special character such as &, the hyperlink did not work as expected. This issue has been resolved. | DE149786 |
| Previously, when you updated a Predecessor Join field parameter and attempted to open the properties again, the Predecessor Join field parameter reverted to the original field parameter. This issue has been resolved. | DE167376 |
| Previously, when you attempted to use Page-Up or Page-Down keys within the SQL text area in the query designer, the header disappeared. This issue has been resolved. | DE167357 |
| Description | Tracking ID |
|---|---|
| When you select the Export to Dataset option for a Query, the Save As window displays the last selected Catalog folder, but the Save button is not available. If you select the Catalog folder that is shown as selected, the Save button appears. | DE167658 |
Record Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can now configure the email address from which the Conditional Alert emails are sent in the From field in the Email Settings page. | US501541 |
| To improve functionality, you can now add an email message (.msg) file as a reference document to a record, from the Add Reference Document window. | US499631 |
| To improve usability, you can now specify new or updated field values in the URL that is used to open an existing record for editing in Record Manager. Note: The new or updated field values specified in the URL are saved only when you select Save in the Record datasheet. | US489063 |
| Description | Tracking ID |
|---|---|
| Previously, when you accessed a record using a URL with the format #record-manager/entity_key?datasheetid=ID, the record was displayed using the default datasheet instead of the datasheet with the specified ID. This issue has been resolved. | DE167133 |
| Previously, when you imported an existing system code reference behaviour on an existing family, and attempted to save the data records, an error occurred. This issue has been resolved. | DE166838 |
| Previously, when you accessed records in the Bulk Datasheet view, you were able to edit fields that were disabled by a rule, for example, fields in approved Calibration Events. This issue has been resolved. | DE162849 |
| Previously, when you manually entered a date in the measurement date field in the two-digit format, (for example, 19 instead of 2019), and then saved the record, the date was updated to the current date and saved. This issue has been resolved. | DE159595 |
| Previously, when creating a new Conditional Alert record, if you selected an email recipient from the Fixed Distribution List drop-down menu and saved the record, Conditional Alert email was not sent to the recipient. This issue has been resolved. | DE158319 |
| Previously, when a conditional alert email was generated, the timestamp did not appear in the email. This issue has been resolved. | DE158318 |
Previously, when a conditional alert was executed, the alert message was blank in the following scenarios:
| DE158316 |
| Previously, if you used the recent browser versions to access the APM system, and then exported a datasheet or result grid to PDF, the PDF print was broken and resulted in a blank output. This issue has been resolved. | DE158106 |
| Previously, an error occurred if the input values entered in a JSTrigger form included special characters. This issue has been resolved. Now, the input values are encoded, enabling special character to be included in the text. | DE158105 |
| Previously, when you attempted to configure the Reference Document Server credentials, and if you assigned a large number of Sites, Groups, or Roles, or if the Shared Directory path was longer than 100 characters, an error occurred, and you could not save the record. This issue has been resolved. | DE157810 |
| Previously, the documentation of the URLs to create and open records in Record Manager was incorrect. This issue has been resolved. | DE156928 |
| Previously, in the Reference Documents list that was displayed in an analysis (for example, in a Root Cause Analysis), the Last Updated Date did not use the correct display format for the user's culture. This issue has been resolved. | DE156923 |
| Previously, in a datasheet, when the Turn On Help Text feature was enabled, the multi value fields did not display the help text correctly. This issue has been resolved. | DE153621 |
| Previously, when you displayed records in a Bulk Data Form and selected a Datasheet that used Column layout, the default column captions were displayed instead of the captions defined in the datasheet layout. This issue has been resolved. | DE150303 |
| Previously, if you deleted or inactivated a predefined value used in the drop-down list for a field, and you viewed an existing record using that value, a null value was displayed. This issue has been resolved. Now inactive is appended to the displayed value and you can no longer select the inactive value when editing the field. | DE137420 |
| Description | Tracking ID |
|---|---|
The following fields have been removed from the Conditional Alerts datasheet:
| US501541 |
Reliability Analytics
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you navigated quickly between the tabs in the Reliability Analytics module, an error occurred. This issue has been resolved. | US483938 |
| Previously, when you added content in the Reliability Spares Analysis, and then changed the application name, the content was lost. This issue has been resolved. | DE169546 |
| Previously, if event dates were not added for all the datapoints, the extrapolation method failed to estimate the number of measurements. This issue has been resolved. Now, only a minimum number of datapoints are required to execute extrapolation of failure dates. | DE165958 |
| Previously, in the Reliability Analysis charts, when you hovered over the extrapolated line, the tooltip did not provide the correct data. This issue has been resolved. | DE165880 |
Previously, in Automation Rules section, as an APM user restricted to view-only permissions for Reliability, you were able to select  . This issue has been resolved. | DE164770 |
| Previously, in Spares Analysis, an error appeared when you tried to navigate quickly between pages. This issue has been resolved. | DE163425 |
| Previously, when you executed a new Automation, the target reliability analyses were not updated with the most current data. This issue has been resolved. | DE162462 |
| Previously, you were unable to ignore the datapoints by clicking the datapoints on the chart. This issue has been resolved. | DE162409 |
| Previously, when you executed new Automation rules for existing reliability growth records, duplicate records were created instead of updating existing records. This issue has been now resolved. | DE162405 |
| Previously, when you created a Production Analysis from a query, if the data contained many records, the operation exceeded the timeout period and failed. This issue has been resolved. Now, to avoid the timeout issue, the query results have been restricted to 5000 records. If there are more than 5000 records, a warning message appears asking you to modify the query. | DE162231 |
| Previously, when you executed a rule in Reliability Analytics Automation Rule, and if the calculated value was very small, an error message appeared for Oracle database users, stating that the Distribution could not be saved. This issue has been resolved. | DE161495 |
| Previously, in System Reliability, when you added a Risk, Action, or Global Event and then selected the Save button multiple times in quick succession, multiple Risks, Actions, or Global Events were created with an error message. This issue has been resolved. Now, entities can only be saved once, irrespective of the number of times the Save button is selected. | DE160662 |
| Previously, in Spares Analysis section, if your culture setting had a culture other than English, when you generated a report, multiple fields were not translated to the language based on your culture setting. This issue has been resolved. Note:
| DE160212 |
| Previously, in Reliability Distribution, the icons displayed next to each of the entry in the Chart Legend, and the icons displayed in the actual chart did not match. This resulted in incorrect data interpretation. This issue has been resolved. | DE158351 |
| Previously, when you attempted to delete a Reliability Analysis without delete privileges, a generic error message appeared saying internal server error. This issue has been fixed. Now, if you attempt to delete an analysis without delete privileges, an error message appears saying, you do not have delete privileges for this application. | DE158185 |
| Previously, in System Reliability section, as an APM user restricted to view-only permissions for Reliability, you were unable to see the details in a Global Event. This issue has been resolved. | DE158174 |
| Previously, in a System Reliability Analysis, when you linked a planned resource to a scenario in the analysis, the resource was automatically unlinked from the planned resource list and you could not add the resource back. This issue has been resolved. | DE157864 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To enhance the usability of the baseline datasheet, the following fields have been removed:
| US485341 |
| The performance when adding assets to an analysis for assessment has been improved. To facilitate this enhancement, a new window, Add Assets, now appears when you attempt to add assets to an analysis. | US484611 |
| To improve performance, the Save as Template functionality has been converted to a background job. In case of an error, the corresponding details are available in the job status, which appears in a separate window on the same page. | US484123 |
| Description | Tracking ID |
|---|---|
| Previously, the Decision Logic Builder was not working as expected. This issue has been resolved. | DE170570 |
| Previously, you could consolidate recommendations linked to different assets in RCM. This issue has been resolved. | DE166051 |
Previously, when you uploaded the RCM Template,
FMEA Analysis Template, or FMEA Asset Template through the data loader, a warning message was displayed for the below fields:
| DE161367 |
| Previously, users with MI RCM User security group permission were unable to access RCM analysis. This issue has been resolved. | DE160674 |
| Previously, when you attempted to import data through dataloader, the operation timed out if the excel file had many Failure Effects and Recommendations. This issue has been resolved. | DE160108 |
| Previously, after applying a template to an RCM analysis at Function and Function Failures levels, the hierarchy took a long time to load. This issue has been resolved. | DE158902 |
| Previously, when loading data though dataloader, financial details were not updated as per the dataloader worksheet. This issue has been resolved. | DE158069 |
| Previously, in the RCM Analysis Details section, when you accessed the Risk card of the Failure Effect, Risk Category ID appeared instead of Description alias. This issue has been resolved. | DE154478 |
Reports
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, using the APM Report Designer, when you attempted to deploy a report that contained a large amount of data, an error message appeared. This issue has been resolved. | DE162311 |
Previously, you could not pass the date parameter values in SSRS report viewer hyperlinks formed using Query Designer tool with the following format: #ssrs/viewer/<QUERY-CATALOG-PATH>/P0={1}/P1={2}/P2={3}This issue has been resolved. Now, the support for report hyperlink has been added in the query string format, as follows: #ssrs/viewer/<QUERY-CATALOG-PATH>?P0={1}&P1={2}&P2={3} | DE160308 |
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 |
|---|---|
RBI Analysts can now carry out Risk Based Inspection on Functional Location and perform the following RBI analysis on Functional Location:
Additionally, the Functional Location supports the following functionalities:
| US483495 |
| Description | Tracking ID |
|---|---|
| Previously, in the Active page of RBI Evergreening workspace, when you generated the bulk recommendations for analyses of components linked to the same parent asset, the recommendations were not consolidated. This issue has been resolved. Now, when you generate the recommendations and select yes on the Generate Recommendations window, the Recommendations are consolidated based on Degradation Mechanism and Task Type. | DE168063 |
| Previously, in the Analysis workspace, when you added a Degradation Mechanism Evaluation in the Degradation Mechanisms section, the Controlling Corrosion Rate, Long Term Avg. Corr. Rate, and Short Term Avg. Corr.Rate fields were not populated. This issue has been resolved. Now, these fields are populated based on the source of Calculated Corrosion Rate field of the parent RBI Component. | DE166076 |
| Previously, when you accessed the Analysis workspace by navigating through the Process Unit workflow, the Inspection Plan hyperlink was not displayed. This issue has been resolved. | DE165417 |
| Previously, when you approved an Inspection Plan with a Consolidated or Superseded Master Recommended Action in the Not Required state, an action was erroneously created and linked to the Master Recommended Action. This issue has been resolved. Now, when you approve an Inspection Plan, no actions are created for Recommended Actions in the Not Required state. | DE165764 |
| Previously, when the RBI Components were linked to a Corrosion Loop through Risk Based Inspection (RBI) Corrosion Loop data loader, Potential Degradation Mechanisms linked to the Corrosion Loop were not added to the RBI Components. This issue has been resolved. | DE157768 |
| Previously, when creating a new RBI Component, in the Create New RBI Component window, the values in the Component Type drop-down list box appeared in English regardless of your culture settings. This issue has been resolved. Now, the Component Type drop-down list box is populated with the values from the MI RBI COMPONENT TYPES system code table and appear in the language based on your culture settings. | DE157760 |
| Previously, the RBI Corrosion Loop table in the Unit Summary workspace took a long time to load. Now, performance improvements have been made to reduce the time to load the table. | DE157692 |
| Description | Tracking ID |
|---|---|
| The Asset Counts for Units query is deprecated. The query is no longer used to show assets associated with a process unit in the Process Units section of the Risk Based Inspection Overview page. However, the Process Units section continues to show the count of the associated corrosion loops. | DE164828 |
RBI 580
| Description | Tracking ID |
|---|---|
You can now export RBI Criticality Analyses to an excel format from either of the following workspaces:
The exported file is in the Risk Based Inspection (RBI) 580 Data Loader template format. This provides the ability to modify the exported analysis data and re-import for easy bulk editing. To facilitate this enhancement, Export Analyses feature has been introduced. | US483624 |
| To enhance usability, when duplicating or evergreening an RBI Criticality Analysis, if the Source of Calculated Corrosion Rate field on the related RBI Component is set to Manual, then the Short Term Corrosion Rate and Long-Term Corrosion Rate field values are now copied to the new RBI Criticality Analysis. | US466736 |
| Description | Tracking ID |
|---|---|
| Previously, some fields in the RBI Criticality Analysis family displayed incomplete help content. This issue has been resolved. For more information on the list of fields updated for the help content, refer to KBA 000038624. | DE167992 |
| Previously, the import of data using Risk Based Inspection (RBI) 580 Data Loader failed if there were errors due to calculation validation. This issue has been resolved. Now, the RBI 580 Data Loader has been enhanced to issue warnings when calculation validation errors are present and allows the import of data to complete successfully. | US487232 |
Previously, in the Degradation Mechanisms section of an analysis, in the Other Damage Mechanism Evaluation datasheet, the Probability Category drop-down list box was not populated for the following Damage Mechanisms:
| DE157762 |
RBI 581
| Description | Tracking ID |
|---|---|
| To improve usability, in the Global Preferences workspace of the RBI Admin Preferences page, Enable Release type calculation as per RFI-8388 is added. When this preference is selected, the Release Type calculation for RBI 581 Consequence Evaluations does not require the release mass to be greater than 10000 for the Release Type to be Instantaneous. This preference is not selected by default. | US492953 |
You can now export RBI 581 Risk Analyses to an excel format from either of the following workspaces:
The exported file is in the Risk Based Inspection (RBI) 581 Data Loader template format. This provides the ability to modify the exported analysis data and re-import for easy bulk editing. To facilitate this enhancement, Export Analyses feature has been introduced. | US483624 |
| To enhance usability, when duplicating or evergreening an RBI 581 Risk Analysis, if the Source of Calculated Corrosion Rate field on the related RBI Component is set to Manual, then the Short Term Corrosion Rate and Long-Term Corrosion Rate field values are now copied to the new RBI 581 Risk Analysis. | US466736 |
| You can now calculate an RBI 581 Risk Analysis with the Representative Fluid field set as H2O (Water) on a Storage Tank Bottom component. To facilitate this enhancement, the H2O (Water) Representative Fluid record has been updated with a Dynamic Viscosity value. | US453124 |
| Description | Tracking ID |
|---|---|
| Previously, the import of data using Risk Based Inspection (RBI) 581 Data Loader failed if there were errors due to calculation validation. This issue has been resolved. Now, the RBI 581 Data Loader has been enhanced to issue warnings when calculation validation errors are present and allow the import of data to complete successfully. | US487232 |
| Previously, when you loaded the RBI 581 ISO Risk Matrix workspace with more than 1,000 assets for a process unit, the risk values of the assets were not plotted. This issue has been resolved. Now, the maximum limit of assets has been increased to 10,000. | DE169491 |
| Previously, if the value of Culture field in your user settings was not set to English and you added an RBI 581 Thinning Degradation mechanism to an active RBI 581 Risk Analysis, you could not see the Corrosion Rate in the Corrosion Analysis section of the RBI 581 Asset Risk Report. This issue has been resolved. | DE160127 |
| Previously, the value in the Base Damage Factor field in the RBI 581 Brittle Fracture Damage Evaluation datasheet related to an RBI 581 Risk Analysis was calculated incorrectly for certain combinations of CET-Tref and Furnished Base Material values. This issue has been resolved. | DE157767 |
| Previously, the Tmin Calculations in RBI 581 for Component Type Storage Tank were based on the Geometry Type selected. This issue has been resolved. The Tmin formula for Storage Tank components has been updated to match the API specification. For more information on how to identify the applicable assets that require a recalculation, refer to KBA 000037310. | DE157766 |
| Previously, the Fracture Appearance Transition Temperature (FATT) field in 581-Low Alloy Steel Embrittlement degradation mechanism contained an incorrect Unit of Measure (UOM). As a result, the calculated value of the Damage Factor for the degradation mechanism was incorrect for a non-imperial user. This issue has been resolved. The field caption for Fracture Appearance Transition Temperature (FATT) has been modified to Delta Fracture Appearance Transition Temperature (Delta FATT) to indicate the correct UOM. | DE157764 |
Previously, in the Picklist tab of RBI 581 data loader template, the following process fluids were not available:
This issue has been resolved. | DE157761 |
| Description | Tracking ID |
|---|---|
| The Fluid Viscosity table is deprecated and is no longer used to validate the representative fluid field on RBI 581 Risk Analyses for Storage Tank Bottom components. Now, the DynamicViscosity field in the Representative Fluids table is used for validation. | US499819 |
Root Cause Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in an RCA recommendation, when you enabled the State to Status mappings, and Completed the Recommendation from the Recommendation Panel, the Implementation Date and Status field values were not updated. This issue has been resolved. | DE167035 |
| Previously, when you navigated quickly between the tabs in the RCA module, an error occurred. This issue has been resolved. | US483938 |
| Previously, you could not save RCA Recommendations if the target completion date had passed. This issue has been resolved. | US419972 |
| Previously, when you copied a node in an RCA Event diagram and enabled the Show Event Dates option, the copied node displayed the timestamp for copying, with the event dates. This issue has been resolved. Now, the copied node correctly displays only the event dates associated with the node. | DE164773 |
| Previously, when you accessed a Verification added to a Hypothesis in an RCA Analysis created from a Template, an Unsaved Changes window appeared even when you did not make any changes. This issue has been resolved. | DE164725 |
| Previously, when you created a new RCA Analysis and navigated to a logic tree or an event diagram, the RCA Event displayed a global site key, irrespective of the site key of the parent analysis. This issue has been resolved. Now, for a new analysis, both RCA Analysis and RCA Event display the site key of your default site. | DE164699 |
| Previously, even when you enabled the Send Notification on Due Date? field in an RCA Verification, you did not receive the email alert on the due date set. This issue has been resolved. | DE164646 |
| Previously, when you generated the RCA SSRS Comprehensive Analysis Report, the report did not include the details from the RCA Verifications. This issue has been resolved. | DE164520 |
| Previously, when you created a copy of an RCA Analysis, the newly created Analysis could not copy the Assigned To details for the RCA Verifications. This issue has been resolved. | DE164343 |
| Previously, when you published an RCA analysis, the email notification to the designated addressee failed. This issue has been resolved. | DE162656 |
| Previously, in the grid below the Hypothesis Verification chart, the details in the Hypothesis and Team Members fields were not populated . This issue has been resolved. | DE162532 |
| Previously, when you generated RCA Comprehensive Analysis report, the report was generated without Logic Tree and Event diagrams. This issue has been resolved. | DE162401 |
| Previously, if you were a member of the team associated with a Root Cause Analysis (RCA), you could change the state of the RCA from In Progress to Pending Approval only if you were assigned with the Principal Analyst role. This issue has been resolved. Now, irrespective of the team member role, you can change the state of the RCA if you are assigned to a security group or a security role that has privileges to change the states. | DE162398 |
| Previously, in the RCA Recommendations, the fields did not appear in the language based on your language settings. This issue has been resolved. | DE162393 |
| Previously, when State Management was enabled in RCA analysis, you were unable to save the analysis as a template in any other state except for Not Started, and an error message appeared. This issue has been resolved. | DE162391 |
| Previously, in the Team Members tab of the RCA Analysis Summary section, as an MI RCA PROACT Admin you were unable to modify the Team Member permissions when you were not part of that Team on an RCA Analysis. This issue has been resolved. | DE162381 |
| Previously, you were unable to save RCA Recommendations if target completion date was in the past. This issue has been resolved. | DE162351 |
Previously, in the RCA Overview page, you could not publish RCA Template even though the RCI check box was selected and the Publish option was enabled. This issue has been resolved. Now, the Publish option for RCA Template is enabled only in the following scenarios:
| DE160244 |
| Previously, in the RCA Event Timeline, the labels along the time axis did not appear in the language set in the culture setting. This issue has been resolved. | DE159709 |
| Previously, in the RCA Administrator workspace, the Event Type List for Event Timeline did not appear in the language based on your culture setting. This issue has been resolved. | DE159707 |
| Previously, in the RCA Event Diagram, when you double-clicked a node in the diagram, an error message "Failed to load datasheet" may occur. This issue has been resolved. | DE159806 |
| Previously, when you accessed the RCA Event Diagram originating from the APM V3 in APM V4, the nodes did not appear as expected. This issue has been resolved. | DE158454 |
| Previously, if your Language setting was not English, and you accessed the Event Timeline diagram for an analysis, the event types were not translated to the language corresponding to your Language setting. This issue has been resolved. | DE158383 |
| Previously, in the RCA Event Timeline, irrespective of the event that you changed and saved, a message appeared that the secondary event was saved successfully. This issue has been resolved. Now, you receive a message indicating the specific event that you have changed. | DE158190 |
| Previously, when you selected an RCA Template, you could view the Publish and Unpublish buttons without Super User or Administrator privileges. This issue has been resolved. Now, you can view the Publish and Unpublish buttons only if you have the required privileges. | DE158187 |
| Previously, in the Preserve Records section for a Root Cause Analysis, some of the fields were not translated based on the Language setting for your user account. This issue has been resolved. | DE158186 |
| Previously, in the Team Members section for a Root Cause Analysis, some of the fields were not translated based on the Language setting for your user account. This issue has been resolved. | DE158182 |
| Previously, when you published an RCA Analysis and enabled the option to send an email to the linked EAM system, the email message was not received by the linked EAM system. This issue has been resolved. | DE158179 |
| Previously, any RCA User could delete an analysis. This issue has been resolved. Now, only Super Users, APM Administrators, and Principal Analyst for the specified analysis can delete an RCA Analysis. | DE158178 |
| Previously, in the RCA Team Members section of the Analysis Summary page, when you accessed the HR record, it opened the list of all available APM users. This issue has been resolved. Now, when you open the HR Record in Teams, it loads only the APM users with site permissions corresponding to the parent analysis. | DE158051 |
Rounds Data Collection
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, the GIS coordinates associated with data captured for a checkpoint were collected periodically. Now, you can capture the GIS data more frequently and consistently. To use the updated GIS coordinate process, in the Rounds Designer module, in the Rounds Default Device Settings workspace, set the Maximum length of time (seconds) that is allowed to retrieve GIS data to a value greater than zero. | DE166548 |
| Previously, when a recommendation was created in Rounds Data Collection, the label Created was not localized. This issue has been resolved. | DE161541 |
| Previously, the Recommendation Type value on the Recommendations tab was not localized. This issue has now been resolved. | DE157439 |
V4.6.10.0.0
This topic provides a list of product changes released for this module in this version.
Rounds Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you accessed a Route using the Route History datasheet, an error occurred intermittently. This issue has been resolved. | DE163001 |
| Previously, certain Measurement Locations and Lubrication Requirements were not available in the Add Existing ML/LR function. This issue has been resolved. Now, these checkpoints are available to add to Routes. | DE162960 |
Previously, in the Rounds Designer Overview workspace, when multiple changes were done to the users assigned to a route and you attempted to save the changes, the loading icon ( ) appeared indefinitely and the changes were not saved. This issue has been resolved. | DE161028 |
| Previously, when you added the first ML or the first LR to a route, an error message appeared. This issue has been resolved. | DE160896 |
| Previously, in the Compliance workspace of the Rounds Designer administration page, the schedule defined for a task to track compliance did not appear as expected. This issue has been resolved. | DE155906 |
Rounds Pro
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
|
When you schedule a route to end after a specific time, you are unable to save the route if you have set up the schedule with some occurrences in the past. You must set up the schedule so that all new scheduled occurrences are created in the future. | DE172400 |
| When you attempt to filter the Assigned To column data in the Open Instances, or the Instance History pages, an error occurs if you are a secure user. | DE172186 |
| Currently, you cannot use picklists that contain special characters in their name on steps and steps templates. To work around this issue, you must modify the picklist name to exclude the special character. | DE172183 |
| When you attempt to re-sequence steps within a route, the performance may degrade when you move steps when there are more than 200 steps under a given asset node on the route. Though the re-sequencing action does not fail, the action does not complete within optimal performance expectations. | DE172180 |
| When you delete a route master, the confirmation message that the delete was successful does not appear and the deleted route master still appears in the list of route masters. Close the Route Details page and refresh the list of route masters, to verify that the route master has been successfully deleted. | DE172179 |
| When you copy and rename a step with associated conditional steps, the mappings on the conditions records are not retained. | DE172127 |
| If you are not operating the mobile device on a reliably fast network, you may encounter delays and errors. In this case, move to a better network and use the mobile device. Code and network optimizations are continuing to be worked and will be delivered in future patches. | DE172059 |
| In the Rounds Designer page, if you add a nested Conditional Step to a Step that is already specified as a Conditional Step on a Primary Step, then the nested Conditional Step will not be available when the Primary Step is included on a Route. | DE171733 |
| In the Rounds Designer page, if you add a step that contains a hashtag (#) in the name, an error message appears indicating that the Asset Key is not passed in the request. Close the error message window and save the step. | DE171246 |
| Site functionality is not fully supported within Rounds Pro. Steps inherit the site for the Asset or FLOC that they are created under. If you do not have access to the assets due to a site access restriction, then any instances that you create from the web or from the mobile application will not contain those steps that exist under the specific assets. If you have a broader site access and create the instance, the steps will be part of the instance and all users will be able to see and update those steps in the Rounds Pro mobile app. | DE170565 |
| When you attempt to create a Health Indicator using the Generate Health Indicators section while creating a step, the health indicator creation may fail, and an error message appears indicating that the action has failed. In this case, you need to create a new step. | DE170265 |
When you modify a step template to use a new picklist and picklist values, the save button ( ) does not get enabled with the changes. A work around for this issue is to modify the step description also to enable the save button (). | DE168473 |
| You cannot add a primary step as a condition to itself in the first level. However, you can add the primary step as a condition at the second or later levels. | DE158339 |
SAP Adapters
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you set the parameter REJECT_EMPTY_PATH to ON in FILE configuration table FILECMCUST, the SAP Adapters fail with an error message. This issue has been resolved. | US499236 |
| Previously, when you performed Data Extraction using SAP adapters, if the extraction job contains fields with data type INT1 (Single byte data type), the extraction failed. This issue has been resolved. | US484893 |
Previously, in SAP Adapters help, the following tables were missing in the SAP Tables Required section of the APM Connect User Profile Requirement topic:
This issue has been resolved. | DE158554 |
| Previously, if a cell text in the ingestion Excel template, which was generated using an automated tool, contained double quotes ("), the data loader framework did not work as expected. This issue has been resolved. | DE158418 |
| Previously, in SAP interface of Work History, the MI_EVENT_STRT_DT field was not populated correctly for all the Work Order Objects. This issue has been resolved. | DE156753 |
Schedule Logs
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you scheduled jobs, some of the jobs were not executed successfully because the jobs went to BLOCKED state in the QRTZ table. This issue has been resolved. Now, to unblock these jobs, you can execute the SchedulerCleanupJob by selecting the Recover Jobs button. Note: The frequency at which the SchedulerCleanupJob is executed can also be configured in appsettings.json file at tenant level. | DE163382 |
Search
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance performance, in search, the search index will no longer include the related entities of an entity. | US512610 |
SIS Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to add a team member to an SIL Analysis, users across all sites were displayed. This issue has been resolved. Now, only the users linked with the site of the SIL Analysis are displayed. | US483318 |
| Previously, in SIL Analysis, when you defined a negative value for Trip Point in the Proof Test Template Details and performed a Proof Test task, the calculated result appeared as Fail in the Pass/Fail column. This issue has been resolved. | DE171455 |
| Previously, for a Protective Instrument Loop, when you set a Logic Solver device (for example, Triconex Tricon) for which one or more failure rates were not defined in the Analog Input, Analog Output, Digital Input, or Digital output modules, an error appeared. This issue has been resolved. | DE170898 |
| Previously, when you added a custom device with a linked equipment to the Final Element or a Sensor, and then attempted to update the related sensor group or final element group, an error occurred. This issue has been resolved. | DE168136 |
| Previously, in the Definition tab of the SIL Verification section, if IEC 61508 was selected from the drop-down list of the Test Architecture Constraints, SIL-Achieved value was not calculated correctly for a Protective Instrument Loop. This issue has been resolved. | DE165806 |
| Previously, for a Protective Instrument Loop that used the ExSILentia V4 Calculation Engine, the SIL-Achieved and Architectural Constraints fields were not displayed correctly. This issue has been resolved. | DE164599 |
| Previously, when you attempted to save a Protective Instrument Device, if any error occurred, an incorrect error message was displayed. This issue has been resolved. | DE164133 |
| Previously, when you created a new or updated an existing SIL Analysis, Instrumented Function, Safety Instrumented System, or Protective Instrument Loop Element, the Modified By and the Modified Date fields did not display correct values. This issue has been resolved. | DE164107 |
| Previously, when a user assigned to SIS Administrator or SIS Engineer security group attempted to create a Risk Assessment Recommendation, an error occurred. This issue has been resolved. | DE162163 |
| Previously, in the Risk Assessment Recommendation datasheet, the Interval and Interval Units fields appeared in the Alert tab instead of the General Information tab. This issue has been resolved. | DE161964 |
| Previously, after importing a Protected Instrument loop into the APM, when you attempted to modify the Protected Instrument loop record, an error occurred. This issue has been resolved. | DE160394 |
| Previously, when you updated the state of a Protective Instrument Loop to a state other than Design, the fields in the Protective Instrument Device datasheet were still available for editing. This issue has been resolved. | DE160302 |
| Previously, when you used the Import from Exida functionality in SIL Analysis, the performance of the APM was not as expected if there were many analyses present in APM. This issue has been resolved. | DE158244 |
| Previously, in the SIL Assessments, when you entered values for the Probability of Failure on Demand (PFD) and Risk Reduction Factor (RRF) fields, the associated SIL level value was not displayed correctly. This issue has been resolved. | DE157711 |
Previously, when you attempted to promote a recommendation to ASM, a blank message appeared in the following scenarios:
These issues have been resolved. | DE157630 |
| Previously, when you entered values for the Risk Reduction Factor (RRF) field for an External SIL assessment, an incorrect validation error occurred. This issue has been resolved. | DE157629 |
| Previously, Promote To ASM operation failed for Recommendations in which the Instrumented Function was linked to a LOPA Assessment or External Assessment. This issue has been resolved. | DE157627 |
| Previously, in SIL verification, when you selected a sensor, a final element, or a logic solver device for a protective instrument loop, an error may have occurred. This issue has been resolved. | DE157621 |
| Previously, when you used the Export to Exida functionality in SIL Analysis, the performance of the APM was not as expected, if there were many analyses present in APM. This issue has been resolved. | DE157620 |
Sites
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you accessed the Sites Page that had exactly 25 sites, the list of sites was repeated indefinitely when you scrolled down. This issue has been resolved. | DE163529 |
SSO
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To improve accessibility, users can now login without adding the proxy details (/?custom_sso=1) in the Server field when accessing the GE Digital APM mobile application. | DE161731 |
State Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you deleted a state or an operation and attempted to save, the Save button was disabled. This issue has been resolved. | DE169919 |
| Previously, in a State Configuration diagram, if multiple states were aligned horizontally and connected using a straight line, you could not select an Operation link if the link overlapped with the connecting lines. This issue has been resolved. Now, you can drag the states and connecting lines to a different position, and then select the Operation link. | DE167083 |
System Requirements
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Microsoft Internet Explorer 11 and Microsoft Edge Legacy browsers are no longer supported in APM. | US492702 |
Teams
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in the Team Members section of any analysis, when you filtered the email column, an error occurred. This issue has been resolved. | DE163636 |
Thickness Monitoring
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
The following enhancements have been made to the Minimum Thickness (T-min) calculator:
| US509814 |
You can now filter the Thickness Measurements based on a defined interval when calculating Short Term and Long Term Corrosion Rates. To support this functionality the following enhancements have been made:
| US509585 |
| To continue the device support for Olympus (Panametrics) 38DL Plus Ultrasonic Thickness Gage in APM, the Meridium Device Service has been updated to support the new driver update. To facilitate this update, when you install the latest version of the Meridium Device Service, you must install the latest version of the Olympus GageView software, which includes the specified drivers update. Similarly, if you have installed the latest version of the Olympus GageView software, you must install the latest Meridium Device Service. | US508989 |
In the Data Loaders page, when loading the data into the database using the following equipment, the performance has been improved.
| DE166555 |
| To align with the API specification more closely, the minimum thickness calculations for Thickness Measurement Locations of Welded Shell or Riveted Shell type tanks has been modified. It now considers the value of Height in the below formula as the distance from the bottom of the Course Number under consideration till the Maximum Operating Fill Height. Previously, the value of the Maximum Operating Fill Height was used when calculating minimum thickness for these types of Thickness Measurement Locations. Any Thickness Measurement Locations of these types of tanks where minimum thickness has previously been calculated and saved, must be recalculated. For more information on identifying applicable assets and steps for recalculating T-Min, refer to KBA 000037226. | US483111 |
| To align better with the API specification, the minimum thickness calculations for Thickness Measurement Locations of Piping have been modified. To facilitate this enhancement, PipingB31.3, FormulaD now considers the Inside Diameter when calculating the minimum thickness of a Piping. | US457149 |
| Description | Tracking ID | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Previously, deleting the TML Groups with large number of TMLs associated with an asset failed due to a time-out exception. This issue has been resolved. Now, the process of deleting a TML Group has been converted to a scheduled action. | US504092 | ||||||||||||||
| Previously, in APM, if you modified the Corrosion Inspection Type system code table to customize the list of available Inspection Types in Thickness Monitoring and had attempted to load data using the Thickness Monitoring data loader, the list of Inspection Types was being saved for all the users in APM. This resulted in an error when other users attempted to load the data using a different list of Inspection Types. The following error appeared in the dataloader log stating that, Inspection Type UT is not valid/available to create corrosion analysis settings for the linked Asset ' <Asset ID>', and hence skipping this row. This issue has been resolved. | DE171210 | ||||||||||||||
| Previously, for the Thickness Measurement Locations (TMLs) that are related to a Piping Band type TML Group on a Piping Asset in an Oracle database, if you attempted to send the TMLs to the datalogger device, it failed. This issue has been resolved. | DE170947 | ||||||||||||||
| Previously, in the Measurements section, when you created a Thickness Measurement record as a user with a non-imperial UOM conversion set, if there were additional required fields configured on the Thickness Measurement family, the value specified in the Readings field of the Add Measurement window was incorrectly copied to the datasheet. This issue has been resolved. | DE170639 | ||||||||||||||
| Previously, when you created settings for an asset in the Corrosion Analysis Settings workspace, if you had selected any Inspection Type other than UT, a duplicate analysis record was created. This issue has been resolved. | DE169662 | ||||||||||||||
| Previously, in the left navigation pane of Analysis Overview page, when you modified and saved a TML for an asset or a TML Group that had more than 25 directly linked TMLs, and then navigated back to the asset or TML Group, the TML list in the left navigation pane was incorrectly displayed. This issue has been resolved. | DE169354 | ||||||||||||||
| Previously, when you viewed the Details page of a TML Group and switched to other tabs in APM and then navigated back to the Details page tab of the TML Group, the corresponding TML Group did not appear as selected in the tree and the datasheet failed to appear. This issue has been resolved. | DE166078 | ||||||||||||||
| Previously, TM overview data was not displayed for a selected level in the Asset Hierarchy. This issue has been resolved. Now, TM Overview baseline queries are delivered again to consider the current level. Note: Baseline queries are not delivered if there are any changes in the overview queries. See the upgrade section for more details. | US491678 | ||||||||||||||
| Previously, when you created a TML Record using the Create TML window, you were able to create TMLs with duplicate IDs even though an error was expected. This issue has been resolved. | DE166165 | ||||||||||||||
| Previously, in the Datalogger page, you were able to select up to 10,000 TMLs to review while using an SQL database. However, an error appeared preventing you from sending the selected TMLs to the device. This issue has been resolved. Now, you can send up to 10,000 selected TMLs to the device directly. However, all the 10,000 TMLs do not appear in the grid, as the maximum number of TMLs displayed in the grid are limited to 5,000 for an SQL Database. For an Oracle database, the selection limit is 1,000 TMLs. |
| ||||||||||||||
| Previously, in the Analysis Overview page of an asset, when you attempted to view the TMLs section for an asset with more than 1,000 TMLs in an Oracle database, an error appeared. This issue has been resolved. | DE165692 | ||||||||||||||
| Previously, when you selected more than 10,000 TMLs in the Send To section of the Datalogger page, a message appeared indicating that there were too many TMLs to display, but you were able to send the data to any selected device. However, if you switched to other tabs in the APM and then accessed the tab of the Datalogger page again, the grid would attempt to load the selected TMLs, and a query execution error appeared. This issue has been resolved. Now, the grid does not attempt to load the selected TMLs, and no error message appears. | DE165382 | ||||||||||||||
| Previously, when the culture setting had numeric values formatted using comma as the radix, the numeric values in the TML Data in the Datalogger of the Send To page appeared incorrectly. This issue has been resolved. | DE164935 | ||||||||||||||
| Previously, for Analysis Output section, when you selected a link for the Thickness Measurement Location in the view all pop-up window, it navigated to an incorrect Thickness Measurement Location record. This issue has been resolved. | DE164357 | ||||||||||||||
| Previously, when you were updating corrosion analysis setting from Asset or TML Group to TML level, there was no indicator that the corrosion analysis settings data was loading, and you were able to finish the update before the corrosion analysis settings data completed loading. This issue has been resolved. | DE160728 | ||||||||||||||
| Previously, an attempt to delete a piping component failed, if there were Thickness Measurements associated with the Thickness Measurement Locations. This issue has been resolved. | DE160315 | ||||||||||||||
| Previously, as a metric user, when you modified the fields related to the calculation of Allowable Stress and when the Override Allowable Stress field was set to True, the Allowable Stress field was updated with an incorrect value. This issue has been resolved. | DE158560 | ||||||||||||||
Previously, when a Thickness Measurement Location had a Skipped Measurement record as its last active measurement and you updated the data for the other TML records in the asset, the Analysis Output section did not display updated data for the following fields if the Controlling Corrosion Rate of the asset became less than the TML’s Controlling Corrosion Rate:
This issue has been resolved. | DE157798 | ||||||||||||||
Previously, when attempting to populate the fields necessary to look up the Allowable Stress value on a Thickness Measurement Location record, the following fields were incorrectly marked as required if the Tank Type field was set to Annular Ring:
This issue has been resolved. Now, only the following fields are required to populate Allowable Stress when the Tank Type field is set to Annular Ring:
| DE157683 | ||||||||||||||
Previously, some queries incorrectly included direct joins to the Equipment family. This issue has been resolved. Now, Thickness Monitoring supports both Equipment and Functional Location families in the baseline product and these queries have been corrected. The following table provides a list of queries affected and their corresponding Thickness Monitoring Overview widget or tile by title.
| DE157675 | ||||||||||||||
| Previously, if a secured user was associated with the Metric UOM Conversion Set, when viewing the T-Min Calculator page for an Asset, the minimum thickness value that appeared in the Current column was incorrect. This issue has been resolved. | DE157671 | ||||||||||||||
| Previously, when you attempted to sort the Thickness Measurement grid by the Measurement Taken Date column, the Thickness Measurement grid was incorrectly sorted. This issue has been resolved. | DE157673 |
V4.6.10.0.0
This topic provides a list of product changes released for this module in this version.
Workflow Solutions
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| New families, fields, family policies, system tables and codes, permissions, security groups and roles, policies, and catalog content that enable tailored configurations to accelerate adoption of APM have been delivered in this release. Important: Workflow Solutions Content is designed to be used only after configuration by GE Vernova. If you attempt to use or modify the Content without assistance from GE Vernova, this may adversely affect other APM features and functions, and is not supported. |
US495736 US485570 US485569 |