V5.1.0.0.0
360 View
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| A new module, 360 View, has been introduced. This module provides a new visualization capability for Asset Hierarchy. Depending on your role and the type and site of the selected asset or asset group, you can configure dashboards and other visualizations to be displayed. You can further personalize your 360 View pages, including saving your favorite assets and choosing your default view for a given asset type. For more information, refer to the 360 View documentation. | F70741 |
| In 360 View, you can designate an Asset Group that you create as a personal group by using the Is Personal Group Boolean field, which has been added to the Asset Group family. You can also filter the view to show only personal groups. | US597200 |
To facilitate the introduction of the 360 View module, the following baseline Roles have been added:
Note: By default, these Roles do not include any Security Groups. The Roles are used for permissions synchronization in Cloud APM. | US590234 |
Action Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in the Implement Actions in Rounds Classic window, in the Create New from Template section, even after you applied a filter, the filter applied text did not appear. This issue has been resolved. | DE201858 |
| Previously, if there were states with the same caption from different Performance Recommendations, duplicate entries appeared in the Recommended Filters window in the Recommended Actions page. This issue has been resolved. | DE197751 |
APM Upgrade
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance the APM database upgrade experience, a new tool named Migrator has been introduced. As a result, all the post upgrade utilities used in previous releases have been removed, and the upgrade time has been reduced significantly. | US600714 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in Asset Criticality Analysis, the RBI Asset View option Sent To was disabled for a Functional Location. This issue has been resolved. Now, the RBI Asset View option is available for both, Equipment Location and Functional Location. | DE200674 |
Asset Hierarchy
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
|
Previously, in the Asset Hierarchy, the asset IDs were formatted incorrectly, resulting in unreadable display of the assets when you navigated to assets at level 6 and lower. This issue has been resolved. | DE205471 |
| Previously, when you applied a taxonomy filter, and then searched for an asset in the hierarchy, no results were returned. This issue has been resolved. | DE203520 |
| Previously, if you were not a super user, when you attempted to copy a query-based Asset Group as a static group, an error occurred due to insufficient permissions. This issue has been resolved. The Everyone Security Group now has the permission to view, insert, update, and delete Asset Group Job records. | DE201200 |
Asset Strategy Implementation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You can validate data on-demand before implementation to help reduce mistakes, ensure data quality, and enforce adherence to customer-specific master data standards. | F71934 |
| You can leverage on-demand implementation, which allows you to send data requests as needed at various levels of the implementation package, thus improving performance and quicker completion of tasks. | F71933 |
| You can configure custom import and export workflows without rules customization. | F71933, F71757 |
| You can leverage out-of-the-box flexibility and control of field mappings without rules customization. | F70958 |
| You can leverage out-of-the-box flexibility and control of field lookup parameters without rules customization. | F70963 |
| Description | Tracking ID |
|---|---|
| Previously, the implementation status icon did not appear for custom Work Management Items (WMIs). This issue has been resolved. Now, the icon appears for each custom WMI within the navigation tree. | DE204829 |
| Description | Tracking ID |
|---|---|
| To support Asset Strategy Implementation (ASI) on cloud, rule-based customizations will no longer be valid (except the customizations for Package Builder, PRT Report Builder, and Object List Items Import). If you created rule-based customization in a previous version of APM, you must reconfigure them using the Asset Strategy Implementation Admin page. | US597117 |
Asset Strategy Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, in the Bulk Risks and Actions workspace, you can now see the Status field icon displayed within a column, if it has been added to the datasheet for the Risk and Action families. You can also set the Status field icon to display as the first column using the Table Settings. | US591403 |
| To enhance usability, you can now configure the mapping between Action to General recommendation for Implementation of Action, as General Recommendation or EAM Maintenance Plan. To facilitate this enhancement, in the Action Mapping workspace, you can now view and select the options for General Recommendation and EAM Maintenance Plan from the Action Mapping column. | US581700 |
| While searching for Asset Strategies to add to a System Strategy, you can now add fields and criteria that will help you group and filter the search results as needed. To facilitate this enhancement, a new Catalog query named Adding Asset Strategies to System Strategy has been created, which is located at Public\Meridium\Modules\Asset StrategyManagement\Management\Queries. | US575862 |
| You can now access a Criticality Assessment or Risk Matrix of an asset directly using the following URL: rte=aca/<entity key of the analysis>/assessment/<entity key of the asset>. | US577242 |
| Description | Tracking ID |
|---|---|
| Previously, a Recommendation generated while implementing an Action as an EAM maintenance plan contained an incorrect URL in the description. This issue has been resolved. | DE206193 |
| Previously, if using a PostgreSQL database, while updating an Action linked to an EAM Plan or a Plant Detail, an error occurred. This issue has been resolved. | DE206114 |
| Previously, in the Summary tab of a System Strategy, the Risk Profile graph was incorrectly displaying the Proposed values for each Asset Strategy. This issue has been resolved. Now, the Risk Profile graph displays the Proposed values correctly. | DE205233 |
| Previously, when you attempted to view the Risk card on the Risks and Actions page, the Strategy Mitigated Financial Risk values inaccurately displayed the Unmitigated Financial Risk values. This issue has been resolved. Now, the Risk card displays the Strategy Mitigated Financial Risk values correctly. | DE205232 |
| Previously, in the Strategy Summary tab, the Financial Risk graph was incorrectly displaying the Active and Unmitigated values as the same. This issue has been resolved. Now, the Financial Risk graph correctly displays the Active and Unmitigated values. | DE205231 |
| Previously, in the Risk Analysis tab, the Financial Risk graph incorrectly displayed a reduction in Risk without any modifications being made to the Asset Strategy. This issue has been resolved. Now, the Financial Risk graph on the Risk Analysis tab will only show an increase or decrease in Risk if changes are made to the Asset Strategy. | DE205230 |
| Previously, you could create a ASM Data Loader and a Secondary Actions with the same ID, this resulted in duplicate records. This issue has been resolved. | DE205114 |
| Previously, the Condition Monitoring Type field was not present on the RCM FMEA Recommendation Family and therefore could not be promoted to the corresponding field on the ASM Action. This resulted in an undesirable amount of manual rework to successfully run an ASO Analysis on an Asset Strategy. This issue has been resolved. Now, the Condition-Monitoring Type field has been added to the RCM FMEA Recommendation family. | DE203803 |
| Previously, when a non-super user attempted to apply a template as a master, the Apply Template window appeared displaying assets from only one site, though the user had access to assets from multiple sites. This issue has been resolved. Now, the Apply Template window displays assets from all the sites to which the non-super user has access. | DE204575 |
| Previously, if the ACA Analysis Checklist was created for a user configured with an English culture setting, the checklist displayed the wrong probability values for users with a Spanish culture setting. This issue has been resolved. Now, the probability values appear properly regardless of the user culture setting. | DE202862 |
| Previously, in the Implement Actions in Rounds Classic window, in the Create New from Template section, even after you applied a filter, the Filter Applied text did not appear. This issue has been resolved. | DE201858 |
Previously, Asset Strategies that were controlled by a master template displayed the Proposed Action and Risk data instead of the Active Action and Risk data. This issue has been resolved. Now, Asset Strategies that are controlled by a master template display the following data:
| DE200669 |
| Previously, if the risk threshold values configured in the Risk Matrix were very low with small differences between them, the risk bar displayed on the Risks and Actions screen did not appear correctly. This issue has been resolved. | DE200527 |
| Previously, when going back and forth using the Previous and Next buttons in the Apply Template window, the Next button was disabled and the Apply Method page was not refreshed. This issue has been resolved. | DE198863 |
| Previously, if you attempted to import a General Task List from SAP that did not have a value in the ‘Changed Date’ field, an error occurred. This issue has been resolved. Now, you can import General Task Lists from SAP even if the ‘Changed Date’ field is blank. | DE197786 |
| Previously, even if an Asset Strategy was in the Pending state, you could modify it using the datasheet. This issue has been resolved. Now, you cannot modify an Asset Strategy in the Pending state using either the datasheet or the Asset Strategy Management (ASM) Data Loader. | DE197287 |
| Previously, the criticality value for the asset did not appear in a strategy record sometimes. This issue has been resolved. | DE195771 |
| Previously, while implementing an action as a Calibration Task, if the same task ID existed in the system, an error occurred. This issue has been resolved. Now, in this scenario, a unique task ID is generated. | DE194120 |
| Previously, a Strategy ID containing commas did not align with the heading in .CSV files while implementing an action as EAM maintenance plan. This issue has been resolved. | DE193700 |
| Previously, if you attempted to modify an approved Recommendation, an error occurred. This issue has been resolved. | DE190840 |
Asset Strategy Optimization
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to delete an Asset Strategy Optimization record, you were unable to delete the record and a timeout error occurred. This issue has been resolved. | US590076 |
| Previously, when you attempted to delete an Asset Strategy Optimization scenario, you were unable to delete the scenario and a timeout error occurred. This issue has been resolved. Now, there is no timeout error and the record is deleted as expected. | DE204539 |
| Previously, when you attempted to delete a copied Asset Strategy Optimization scenario, you were unable to delete the copied scenario and a timeout error occurred. This issue has been resolved. Now, there is no timeout error and the record is deleted as expected. | DE204537 |
| Previously, when assigning a Risk to an Action, no option appeared to replace TTF distribution or Failure Consequence. This issue has been resolved | DE136780 |
Calibration Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, in the Calibration Queue and Calibration Events sections, you can now create a Calibration Event without using a Calibration Template. | F71660 |
| To enhance usability, you can now link multiple Calibration Tasks to the same Calibration Template, even though the Template is already linked to an existing Calibration Task. Note: The earlier Replace Task functionality has been removed. To replace the existing task with a new task, you must first unlink the existing task from the Calibration Template using Unlink Task. | US557646 |
| Description | Tracking ID |
|---|---|
| Previously, when you created a Test Equipment record, the Certification Field was not populated if you had Insert and Update privileges. This issue has been resolved. | DE206016 |
| Previously, if a user who was assigned the MI Calibration Viewer security group logged in to APM, and attempted to view the Calibration records under Calibration Queue and Calibration Tools tile, an error occurred. This issue has been resolved. | DE205447 |
| Previously, when you tried to create Calibration, Analyzer Multi-Component record using a Calibration Template, Multi-Component Analyzer with template detail records, an error occurred. This issue has been resolved. | DE199798 |
| Previously, Calibration Recommendations linked to a Functional Location were not displayed on Calibration Management Overview graph. This issue has been resolved | DE192710 |
| Description | Tracking ID |
|---|---|
| When you perform Manual Calibration from Calibration Queue, then intermittently, the Asset field, or the Template field, or the Task field in the Calibration Event datasheet does not get populated. Workaround: Close the tab and create the Manual Calibration from the Calibration Queue section again. | DE205425 |
Compliance Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to access the Compliance Management Overview page, if there were a large number of Assets in the Assets without Templates section, sometimes, the page failed to load. This issue has been resolved. | DE196828 |
Datasets
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, manual creation of datasets displayed unsupported data types in the Data Type drop-down list of the Dataset column. This issue has been resolved. | DE205263 |
| Previously, if you imported a file that had column names as a number and used it as column header, the column names were jumbled in the preview and the imported dataset. This issue has been resolved. Now, during import of excel for datasets, if a column name is numeric, an underscore (_) is appended to the column name such that it is converted to text. | DE204645 |
| Previously, when creating a Dataset using a Microsoft Excel spreadsheet, date fields were displayed in the UTC format. This issue has been resolved. The date fields are now displayed in the format specified in the spreadsheet. | DE204272 |
| Previously, if your culture settings were set to Spanish, and you attempted to create a dataset by importing an Excel file that contained a date, an error occurred. This issue has been resolved. | DE200836 |
Data Loaders
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| A new API has been provided to ingest small number of records into APM. Based on the configuration provided, data can be processed into any of the APM families. The first step is to get the Meridium token with the Data Loader role. Then, the data along with the configuration is sent within the payload in JSON format with the received token. For more information, refer to the Simple Ingestion API documentation. | US603395 |
| Description | Tracking ID |
|---|---|
| Previously, if you attempted to load records using the Policy Instances Data Loader, and the policy name specified in the data loader file did not exist in the APM database, the status of the data bundle was reported as Completed. This issue has been resolved. Now, the status is reported as Completed with Warnings and you can view the error details by selecting the data bundle in the grid. | DE203047 |
Failure Modes and Effects Analysis (FMEA)
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
While promoting RCM/FMEA Analysis or an Analysis Template, you can now configure the following field mappings that occurs during promotion to ASM using a policy:
| US581702 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to apply an Asset Template to an Analysis Template, you were prompted to select an Asset. This issue has been resolved. | DE204010 |
| Previously, when you accessed the RCM Template, or FMEA Asset Template, the failure effects were not displayed properly. This issue has been resolved. | DE203768 |
| Previously, when you attempted to access an RCM or FMEA record using global search, an error occurred. This issue has been resolved. | DE203258 |
| Previously, when you attempted to access the virtual assets of an FMEA Analysis by clicking on the virtual asset list in the Assets section, an error occurred. This issue has been resolved. | DE197772 |
| Previously, when you accessed an FMEA Analysis or an FMEA Template, the search functionality did not work as expected. This issue has been resolved. | DE197026 |
Family Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you added behavior for a field, and if this behavior used fields that were not part of the child families, then the behavior inherited by the fields had an invalid configuration. This issue has been resolved. Now, if the field is available, the correct behavior is inherited. Additionally, if the field is not available in the child family, then the behavior is not spread. | DE202182 |
| Description | Tracking ID |
|---|---|
| The datasheet-level privilege, Allow for Linking, which had no effect on the options available to users in the Master Detail form, has been removed from the datasheet builder. | US590021 |
Family Policies
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, a new node named State Transition has been introduced. The new node allows you to modify the state of one or more records in a policy. | US598769 |
| A new input node, State Information, which is available in Before State Commit entity family policies, allows you to access information about the current state transition transaction. | US596296 |
| To enhance usability, when you view policy execution results in the design canvas, the node ID is now displayed in the node execution details window. | US595444 |
| A new calculation node, JSON Parser, allows you to define an output collection to be created from an input JSON object, using JSON Path query expressions. The JSON Parser node can be used to transform the output from an API node into a format that can be used in successor policy nodes. | US587684 |
| To ensure that the content protection and revert to baseline features work as expected, you can no longer modify the Family ID or the Trigger field in a baseline Family Policy record. | US581682 |
| To enhance usability, the policy model can now be started from a Query node, thus the Query node is now consistent with the other Input nodes. | US495730 |
| To enhance usability, the Convert Type node can now be configured to convert a column of values in a collection (for example, a query result), to a different data type. | US476079 |
| To enhance usability, a new baseline policy, String Replace Sub-policy and an associated R Script have been delivered. You can use this policy to facilitate replacing a string with a different string in a single text value or a collection of text values. | US293831 |
| To enhance the configurability of APM, for families where State Management is enabled, you can now define Family Policies to be triggered before and after the state of a record is saved. To facilitate this enhancement, the Before State Commit and After State Commit triggers have been added to the list of available family policy triggers. | US280338 |
| To enhance usability, a new node named Query Entity has been introduced, which enables you to retrieve all fields of a record by providing the entity key and family ID of the record. This removes the requirement to create a catalog query to retrieve a record that is not the Current Entity. | US255674 |
| To provide additional configuration capability, you can now configure a family policy to be executed when a new relationship is instantiated. | US236052 |
| Description | Tracking ID |
|---|---|
| Previously, when you executed a Create Entity or Edit Entity node in policy, if the family rules were configured to create a relationship based on the values written to fields on the new or updated entity, for example, a related record ID or entity key, the relationship was not created. This issue has been resolved. | DE194635 |
| Description | Tracking ID |
|---|---|
| When your APM database is upgraded to V5.x, the upgrade logs for certain policy models that contain Create Relationship nodes indicate that the node was upgraded successfully; however, the upgrade fails. Workaround: Correct the policy configuration. For instructions, refer to KBA 000069050. | DE206553 |
Foundation
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Oracle only: To enhance usability, in the Result grid columns, you can now enable case-sensitivity for the search term. To facilitate this enhancement, a new setting Filter Result Grid Case Insensitive has been added in the Query Settings page. By default, the text you enter for search and filter terms is case-sensitive. | US592116 |
| Description | Tracking ID |
|---|---|
| Previously, when you modified the filter settings on a module overview or other application page using a page-level filter, the filter icon was disabled, and you were unable to further modify the filter settings. This issue has been resolved. | DE206629 |
General Dashboards
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, in a Query widget, you can now specify whether to display text wrapped or on a single line. To facilitate this enhancement, the Wrap Text option has been added in the Edit Widget window for the Query widget and is selected by default. | US597201 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to open a query from the Query widget, if the percent (%) wildcard was used in a query parameter, the parameter was incorrectly encoded, and the query results did not appear as expected. This issue has been resolved. | DE192480 |
Generation Availability Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To enhance usability, as per the NERC standards, when creating an event for GAA, only the following amplification codes are available for U1 event types:
| US598359 |
To enhance usability, to move the state from New to InProgress for Performance Fuel in Performance Records, you must now populate the new mandatory fields. To facilitate this enhancement, it is now mandatory to populate the following :
| US587221 |
| To enhance usability, on the Bulk Event creation page, you can now add more input when you create new events. To facilitate this enhancement, you can now view all the columns that are available to add input, instead of a limited number of columns. You can also show or hide the columns as needed. | US584575 |
| For derate event types, D1, D2, and D3, the amplification code field is now an optional field. | US584572 |
To enhance usability, while creating an event for GAA, on the New Primary Event page, it is now mandatory to populate the following fields for NERC customers:
For CEA customers, the following fields are now mandatory to populate:
| US584563 |
| To enhance usability, when you select Show Unit Summary from the GAA Overview page, any newly added unit is now displayed in alphabetical order. Previously, any new unit added to the Units page was added to the bottom of the list. | US582116 |
| To enhance usability, the State Management tab is now added to the Bulk Event Creation page. The State Management column has been added to the Bulk datasheet. | US552543 |
| Description | Tracking ID |
|---|---|
| Previously, the Gross Available Capacity and Net Available Capacity for Contributing Events were not getting calculated correctly and did not match up to the Primary Events. This issue has been resolved. | DE203606 |
| Previously, you were able to change the Unit ID while creating a Related Event. This issue has been resolved. | DE197396 |
Inspection Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Performance has been enhanced when deleting records from the Inspections, Tasks, or Work Packs sections of the Inspection Management Overview page. | US600736 |
To enhance usability, the Next Date for Inspection Task can now be populated optionally based on the TM Remaining Life from Thickness Monitoring module. To facilitate this enhancement, the following fields have been added to the Inspection task datasheet:
Note:
After you enable the Consider TM Remaining Life check box and save the record, the Next Date field will be populated based on the most conservative value between Desired Interval and the calculated TM Remaining Life. If Next Date is calculated using TM Remaining Life, then Next Date Basis will be populated as Overridden By TM Remaining Life. However, if Next Date is calculated using Desired Interval, then Next Date Basis will be populated as Desired Interval. | US588914 |
| To enhance usability, you can now upload an Inspection Scope Visualization Document for an individual Inspection. To facilitate this enhancement, a new section, Inspection Scope Visualization, has been added and can be accessed by selecting the Scope tab of an Inspection within the Inspection Management module. | US582350 |
| To enhance usability, you can now determine Susceptibility Type of a Component from Inspection History. To facilitate this enhancement, a new field, Cracking Detected?, has been added to the Inspection Confidence Evaluation family. You can access this field from the Inspection Confidence section of an Inspection. When Inspections are linked to RBI 581 Cracking Damage Evaluation or RBI 581 External Cracking Damage Evaluation, if Cracking Detected?, is selected for any of the linked Inspections, the Susceptibility Type will be set to Detected. | US569500 |
| To enhance usability, you can now auto generate Inspection Confidence Evaluation records for RBI Components on an Inspection. To facilitate this enhancement, a new button Generate has been added and can be accessed by selecting the Inspection Confidence tab in the Inspection workspace. | US577958 |
To enhance usability, you can now load a Checklist Finding using the following Data Loaders:
| US570072 |
| To enhance usability, only effective Inspections will now be considered for RBI 581 Degradation Mechanism Evaluations. To facilitate this enhancement, Inspections with Ineffective confidence will not be considered when setting the Last Known Inspection Date field for RBI 581 Degradation Mechanism Evaluations. | US569635 |
| To enhance usability, you can now determine Thinning Type of the Component from Inspection History. To facilitate this enhancement, a new field Thinning Type has been added to Inspection Confidence Evaluation family and can be accessed from Inspection Confidence Evaluation tab in the Inspection. Note: When the Inspections are linked to an RBI 581 Thinning and Lining, RBI 581 External Damage Evaluation or Int. Corr. Deg. Mech. Eval. DME, Thinning Type from the latest Inspection is mapped to the DME. | US569497 |
To enhance usability, PRD Pop Test Checklist now supports multiple Degradation Mechanisms. To facilitate this enhancement, Inspection Confidence Evaluations has been enabled for PRD Pop Test Checklist and can be accessed from Inspection Confidence tab in the Inspection workspace. PRD Pop Test Checklist datasheet has been updated and the following fields have been removed from the datasheet:
|
|
| Description | Tracking ID |
|---|---|
| Previously, in the Inspection Profile record, when you entered values with single quote for the RBI Component field, the validation failed, and the record was not updated. This issue has been resolved. | DE205320 |
| Previously, if you had included a Boolean field in an Offline Form, after you downloaded an Inspection in Inspection Field Data Collection, you could not select or clear the check box corresponding to the Boolean field. This issue has been resolved. | DE203654 |
| Previously, if you updated the state of an Inspection when there were unsaved changes, the state was updated, but the unsaved data was lost. This issue has been resolved. Now, in this scenario, a message appears indicating that there are unsaved changes, and you can update the data and change the state. | DE200656 |
| Previously, if the Asset ID was long, Inspection Group hyperlink was not displayed correctly within an Inspection. This issue has been resolved. | DE198484 |
| Previously, in the Event Configurations section of the Inspection Management application settings, while reviewing the Related Families for the Checklist Inspection Template family, the Offline option was selected for each of the three configured related families. However, the Offline option for these families was not intended to be enabled, and in the Integrity Mobile app, this prevented Checklist Findings from displaying. This issue has been resolved. | DE198088 |
| Previously, when a Risk Analyst reviewed the Inspection Confidence record in the Inspection Confidence section, the Risk Analyst name displayed was overlapping. This issue has been resolved. | DE196413 |
| Previously, when loading new Inspection Confidence Evaluation records using the Inspection Data Loader, if a value was specified in the RBI Component field, the field was not set properly. This issue has been resolved. | DE166452 |
Integrity Mobile Application
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, after capturing a picture, the image preview screen, which prompted the user to either Annotate or Use Picture has been removed. Instead, now, you will be directly navigated to the image gallery view and you can now annotate the selected image by clicking on the Edit icon. | US597171 |
| You can now take photos directly against a recommendation. When you view a photo for a recommendation, you will see both, photos taken for any related finding as well as photos taken for the specific recommendation. Upon upload, the photos taken for a recommendation are linked only to that record. Note: This feature is only available when using V5.1.x.x or above of GE Digital APM Server. | US597147 |
To enhance usability on a tablet device, the following UI enhancements have been added:
| US596726 |
| The Integrity Mobile app now supports Korean language. | US595428 |
| To enhance usability, you can now view and annotate Inspection Scope Visualization Documents within Integrity Mobile. To facilitate this enhancement, a new section, Inspection Scope, has been added and can be accessed from the Inspection Details tab within the Inspection Workspace. This feature is only available for GE Digital APM V5.1.0.0.0 or above. | US579600 |
| To enhance usability, Remove from Device option is added in the My Inspections overview page. Using this option, you can now delete an inspection from a device that has already been deleted from server. | US547886 |
| To enhance data security, if you enter an incorrect PIN five times in offline mode, the Integrity Mobile application will prevent your login attempts for a duration of 60 seconds. | DE198615 |
| Description | Tracking ID |
|---|---|
| Previously, the Photos tab was available even for records of families that do not have the Has Reference Documents relationship. This issue has been resolved. | DE202996 |
| Previously, the Asset ID column in the My Inspection grid showed a blank value for Inspections directly related to a Functional Location. This issue has been resolved. Now, the Asset ID column displays a coalesce of the Asset ID and Functional Location ID fields for GE Digital APM databases upgraded to V5.1.0.0.0 | DE197864 |
Job Monitoring Dashboard
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in the Edit Schedule window, you could not modify a schedule from weekly, monthly, or yearly to minutes, hours, or daily. This issue has been resolved. | DE206825 |
Life Cycle Cost Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, in an LCC Recommendation, when the Target Completion Date was in the past, an incorrect error message appeared. This issue has been resolved. | DE205692 |
Management of Change
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance functionality and usability, you can now select multiple checklists while linking the checklists to a MOC Change Project. | US576169 |
| Description | Tracking ID |
|---|---|
| Previously, if you tried to add Changed Elements in MOC, the APM Family list was not displayed in APM Japanese language environment. Also, if you added more than five families in the Change project has element relationship for an MOC change project, the changed elements page did not load successfully. This issue has been resolved. | DE199130 |
Manage Translations
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| When upgrading from APM V4.6.X.X.X to V5.0.0.0.0, if there are any custom translations, you must export or download the custom translation from V4.6.X.X.X and upload to V5.0.0.0.0. For more information, see the Manage Translations Upgrade section in APM Upgrade guide. | US602636 |
| To enhance usability, you can add new languages to the Manage Translations application.To facilitate this enhancement, a plus icon next to the language drop-down menu on the Manage Translations page has been added. The plus icon enables you to access the Add New Language window where you can select the desired new language and save the selection. | US581533 |
| Description | Tracking ID |
|---|---|
| Previously, there were incorrect translation strings in German. This issue has been resolved. Now, the translation strings have been updated. | US597820 |
Previously, in the Manage Translations page, the following options were available for English language even though they were not applicable:
| US602044 |
Metrics and Scorecards
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you were using an Oracle database, the SQL Server Analysis Services (SSAS) cube dimensions were not getting processed. This issue has been resolved. To facilitate this fix, while deploying Work History Cube, Oracle users must use the Oracle specific Work History Oracle folder instead of Work History folder. | DE202987 |
| Previously, if you created a Key Performance Indicator (KPI) for an Analysis Services cube, sub-indicator KPIs were not automatically created for the underlying levels and members. This issue has been resolved. | DE197280 |
| Previously, calculated measure of metric view PM Effectiveness % by Equipment Taxonomy was not formatted in the Tabular view. This issue has been resolved. | DE186530 |
Policy Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance the configurability of APM, a new node named API has been introduced. The new node allows advanced policy users to configure policies to execute calls to the application programming interfaces (APIs) in APM. Note: To use this node, you must first configure the API Node Credentials in the Policy Admin page. | F39654 |
| You can now add, update and delete API Node Credential Records. To facilitate this enhancement, a new section, Manage API Node Credentials, has been added in the Policy Admin page. | US599062 |
| To enhance usability, a new node named State Transition has been introduced. The new node allows you to modify the state of one or more records in a policy. | US598769 |
| To enhance usability, you can now send an email notification to all the users in a security group. To facilitate this enhancement, a new baseline policy Concatenate Text Email Example with associated R Script and Query have been delivered to the baseline APM database. | US596437 |
| To enhance usability, when you view policy execution results in the design canvas, the node ID is now displayed in the node execution details window. | US595444 |
| A new calculation node, JSON Parser, allows you to define an output collection to be created from an input JSON object, using JSON Path query expressions. The JSON Parser node can be used to transform the output from an API node into a format that can be used in successor policy nodes. | US587684 |
| To enhance usability, the policy model can now be started from a Query node. Hence, the Query node is now consistent with the other Input nodes. | US495730 |
| To enhance usability, the Convert Type node can now be configured to convert a column of values in a collection (for example, a query result), to a different data type. | US476079 |
| To enhance usability, a new node named Query Entity has been introduced, which enables you to retrieve all fields of a record by providing the entity key and family ID of the record. This removes the requirement to create a catalog query to retrieve a record that is not specified in the Policy Instance. | US255674 |
| To enhance usability, a new baseline policy, String Replace Sub-policy and an associated R Script have been delivered. You can use this policy to facilitate replacing a string with a different string in a single text value or a collection of text values. | US293831 |
| Description | Tracking ID |
|---|---|
| Previously, if your APM system used an Oracle database, when you attempted to save, validate, or execute a policy containing an OT Connect input node, an error occurred. Also, if the policy was configured for Automatic Execution triggered by an OT Connect node, the policy did not execute when new data was received. These issues have been resolved. | DE206278 |
| Previously, if you were assigned to the Policy Viewer security group, you were unable to view Policy Events. This issue has been resolved. | DE204293 |
| Previously, if you scheduled a policy with a large number of instances, not all instances were executed every time. This issue has been resolved. | DE203646 |
| Previously, when you closed the Policy Admin page, even if you did not make any changes to the settings, a message appeared, stating that your changes would be unsaved. This issue has been resolved. | DE197820 |
| Previously, when you executed a Create Entity or Edit Entity node in policy, if the family rules were configured to create a relationship based on the values written to fields on the new or updated entity, for example, a related record ID or entity key, the relationship was not created. This issue has been resolved. | DE194635 |
| Description | Tracking ID |
|---|---|
| When your APM database is upgraded to V5.x, the upgrade logs for certain policy models that contain Create Relationship nodes indicate that the node was upgraded successfully; however, the upgrade fails. Workaround: Correct the policy configuration. For instructions, refer to KBA 000069050. | DE206553 |
Production Loss Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance functionality, State Management is now a baseline functionality for Product Loss Analysis. | US599981 |
| To enhance usability, the losses datasheet in the Production Losses section now has a column for Production Events to associate with the loss amount for a planned production. | US585318 |
| To enhance usability, you can now view the asset hierarchy in the Asset Finder window, when selecting the Causing Asset field in a Production Event datasheet or the Associated Unit field in a Production Unit datasheet. | DE184531 |
| Description | Tracking ID |
|---|---|
| Previously, in the PLA Administrator, if there were a large number of Event Code records, a timeout error occurred. This issue has been resolved. Now, pagination is available such that you can access only 10 records per page, which eliminates the timeout error. | DE204068 |
| Previously, the PLA Overview Count for Production Data, Production Plan(s), Production Events, and Production Analyses took more than the expected time to load. This issue has been resolved. The tiles in the PLA Overview page now load quickly. | DE201497 |
Queries
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if a query contained the date parameter, and if you attempted to open the query from the View Query column in the Query page, an error occurred. This issue has been resolved. | DE206744 |
Previously, the following issues existed in the Query Designer page:
These issues have been resolved. | DE206322 |
| Previously, under certain scenarios, when you attempted to run a query that contained a right join query, incorrect results were returned. This issue has been resolved. Now the query returns the same results as APM V4.6.0.0.0. | DE205146 |
| Previously, if you attempted to run a Show totals query that contained Meridium datetime function, an error occurred, and the export failed. This issue has been resolved. | DE204315 |
| Previously, when you accessed the query details page, and navigated to a different tab in APM, and then accessed the query details page again, the advanced filters were not available. This issue has been resolved. | DE203932 |
R Scripts
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| R Server 8.0.0 and Machine Learning Server are out of support by Microsoft and, as a result, will no longer be supported for use with APM. Now, the only supported option for R Script is RServe. | US566967 |
Record Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, you can now control the page layout when printing from a Bulk Data Form. To facilitate this enhancement, the Formatted Print button and the Print Options item in the More Options menu have been added in the Bulk Data Form. | US597088 |
| To enhance usability, you can now upload reference documents to be stored in APM in bulk. To facilitate this enhancement, a new option, Reference Document Bulk Upload, has been added in the Operations Manager page under Admin. | US584339 |
| To enhance usability, performance has been significantly improved when you open a record with a large number of related records. | US581478 |
| To enhance usability, you can now modify the state of records in bulk. To facilitate this enhancement, when you use the Bulk Data Form to access records of a family for which state management is enabled, the state management control appears when you select multiple records that are in the same state. | US571654 |
When you use the Table Settings window to modify the settings for a Bulk Data Form or Master Detail datasheet, the following column settings are retained as a user preference for that form:
Note: If, however, you change the order of columns using the drag-and-drop method, the changes are not saved as a user preference. | US543512 |
| Description | Tracking ID |
|---|---|
| Previously, if the record contained cascading picklist behaviors, then the record had to be saved for the dependent picklist to be populated. This issue has been resolved. | US531507 |
|
Previously, if the entity ID of a record was too long to display in the Record Explorer window, the displayed entity ID was excessively truncated. This issue has been resolved. Now, the truncated display format of the entity ID shows more characters and is allowed to wrap at lower display resolutions. | DE205445 |
| Previously, if you added a custom family as the child of another family, and included both families in the Asset Hierarchy configuration, the records in the child family did not appear in the Asset Hierarchy search results unless you were a super user. This issue has been resolved. The child family now appears in the Asset Hierarchy search results for all users with view permission for the custom family. | DE204693 |
| Previously, in Bulk Data Form, when you selected a field with a drop-down list, the cursor was placed at the end of the entry. This issue has been resolved. Now, the entire content is selected, which allows you to select a different option from the drop-down list by typing the first few letters of the desired value. | DE203001 |
| Previously, you could not select multiple Alert IDs in a Strategy Macro Schedule option, even though all alerts associated with the schedule were executed successfully. This issue has been resolved. | DE202964 |
| Previously, if you attempted to open a record in Record Manager using a hyperlink where the Family ID was entered in lowercase letters, an error occurred. This issue has been resolved. | DE166954 |
Reliability Analytics
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance usability, you can now use an Analysis Name more than 48 characters when Automation Rules are applied, without the name getting truncated in the display. To facilitate this enhancement, the Analysis Name for Automation Rules in Reliability Analytics has increased to 255 characters. | US539755 |
| To improve usability, you can now export and print the System Model or Subsystem diagram as an image. To facilitate this enhancement, a new button, Export, has been added to the System Reliability Scenario Diagram page. | US429616 |
| To improve usability, you can now query all simulation results in Reliability Analytics. However, this enhancement does not work for Existing Simulation. Existing Simulation should be run again for you to query the result. | US328449 |
| Description | Tracking ID |
|---|---|
| Previously, in an RA Recommendation, when the Target Completion Date was in the past, an incorrect error message appeared. This issue has been resolved. | DE205692 |
| Previously, if you created a recommendation that is linked to a distribution family, and then you opened that recommendation in Record Explorer, the related family details were not populated. This issue has been resolved. | DE205654 |
| Previously, you could not wrap text for the Name field in an Automation rule of a Reliability Analysis. This issue has been resolved. | DE204564 |
| Previously, when you tried to create a new Reliability Distribution analysis, the action failed, and an error message appeared. This issue has been resolved. | DE203193 |
| Previously, when creating a Probability Analysis by using the total time to repair as the production data and then drawing a demonstrated line and nameplate line, the regions under the reliability loss and efficiency or utilization loss regions did not have color. This issue has been resolved. | DE191582 |
| Previously, while creating a Production Analysis, the response time was high. This issue has been resolved. Now, it takes considerably less time. To facilitate this fix, while selecting the query to create a Reliability Distribution Analysis, ensure that the query contains the Entity Key, Family Key, and the Site Key for all the families used in the select clause. | DE172271 |
| Previously, while creating a Reliability Growth Analysis or a Reliability Distribution Analysis, the response time was high. This issue has been resolved. Now, it takes considerably less time. To facilitate this fix, while selecting the query to create the analysis, ensure that the query contains the Entity Key, Family Key, and the Site Key for all the families used in the select clause. |
|
| Previously, when adding a new analysis, if you moved the cursor to description, but tried to save without entering any value, an error message appeared, indicating that unsupported text was found. This issue has been resolved. | DE137619 |
| Previously, in a Reliability Distribution, the Probability Plot did not have confidence boundaries for the time to repair data. This issue has been resolved. | DE136769 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
While promoting RCM Analysis, an FMEA Analysis, or an Analysis Template, you can now configure the following field mappings that occur during promotion to ASM using a policy:
| US581702 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to apply an Asset Template to an Analysis Template, you were prompted to select an Asset. This issue has been resolved. | DE204010 |
| Previously, when you accessed the RCM Template or an FMEA Asset Template, the failure effects were not displayed properly. This issue has been resolved. | DE203768 |
| Previously, when you attempted to access an RCM or FMEA record using global search, an error occurred. This issue has been resolved. | DE203258 |
| Previously, when you accessed an RCM Analysis or an RCM Template, the search functionality did not work as expected. This issue has been resolved. | DE197026 |
Risk Based Inspection
This topic provides a list of product changes released for this module in this version.
RBI 580 and RBI 581
| Description | Tracking ID |
|---|---|
| To enhance usability of the RBI Components to TML Groups Relationship Data Loader, the Data Loader now prevents the creation of relationships if the Asset Corrosion Analysis has not been calculated. After the Asset Corrosion Analysis has been calculated in Thickness Monitoring, you can retry creating relationships using the Data Loader. | US593766 |
You can now create What-If analyses in bulk. To facilitate this enhancement, a new workspace, Bulk Create What-If Analyses, has been added and can be accessed from the Actions menu of the Risk Based Inspection Overview page. In addition, the following datasheets have been added to allow you to copy field values to the newly created what-if analyses:
|
|
| To enhance usability, you can now automatically generate Inspection Confidence Evaluation records for RBI Components on an Inspection. To facilitate this enhancement, a new button Generate has been added and can be accessed by selecting the Inspection Confidence tab of the Inspection. | US577958 |
| You can now identify if the re-calculation of an analysis is not successful. To facilitate this enhancement, the Date Criticality Calculated field of the analysis is reset during the calculation. | US571458 |
| To enhance usability, you can now determine Thinning Type of a Component from Inspection History. To facilitate this enhancement, a new field named Thinning Type has been added to Inspection Confidence Evaluation family and can be accessed from the Inspection Confidence Evaluation tab of the Inspection. Note: When the Inspections are linked to an RBI 581 Thinning and Lining, RBI 581 External Damage Evaluation, or Int. Corr. Deg. Mech. Eval. DME, Thinning Type from the latest Inspection is mapped to the DME. | US569497 |
To enhance usability, you can now save result grid column preferences. To facilitate this enhancement, advanced settings are enabled for result grids in the following workspaces and sections:
| US549058 |
| Description | Tracking ID |
|---|---|
| Previously, even if the unit key was provided in the URL, the records in the Risk Based Inspection Overview page were filtered based on the Asset Hierarchy context. This issue has been resolved. Now, the records are filtered based on the unit key you provide in the URL. | US376471 |
| Previously, when you enabled history for a field in a Degradation Mechanism Evaluation family, the history option was not displayed for the family in the datasheet. This issue has been resolved. | DE206343 |
| Previously, an RBI Administrator user was unable to modify RBI Inspection Auto-Selection Criteria records in the RBI Admin Preferences for Inspection Auto-Selection. This issue has been resolved. RBI Administrators can now modify RBI Inspection Auto-Selection Criteria. | DE206124 |
| Previously, you could only update the first what-if analysis in a Created state linked to a RBI Component through the RBI Data Loader. This issue has been resolved. You can now update multiple what-if analyses on the same RBI Component by utilizing the Sub ID column, which has been added to the dataloader template. | DE203367 |
| Previously, if the Entity ID Template of the Potential Degradation Mechanism family was modified, Potential Degradation Mechanisms could not be linked to an RBI Component. This issue has been resolved. Now, Entity ID will not be considered while linking a Potential Degradation Mechanism. | DE202443 |
Previously, while selecting Create Inspection Plan, an error occurred if the following conditions were satisfied:
| DE200604 |
Previously, RBI Components with Component Status field set to NULL were not considered as active components in the following fields:
| DE199691 |
RBI 581
| Description | Tracking ID | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| To adhere to API 581 Third Edition, Addendum 2, the 581- Atmospheric Tank Bottom Corrosion Damage Mechanism Age will now be adjusted if a Liner is Present. To facilitate this enhancement, a new table, Tank Bottom Internal Liner Types, has been added. Additionally, the Liner Condition, Liner Type, and Immersion Grade Coating Quality fields are now required when the Liner is Present field is set to Yes, and have been added in the DME_AST sheet in RBI_581_Data_Loader template. Note: The calculation of liner adjustment age, as per formula 5.1 under section 4.2.1 for Storage Tanks in API 581 3rd edition, 2nd addendum is incorrect as it does not give credit for online monitoring. APM has updated this formula to ensure credit is given for online monitoring while calculating liner adjustment age for tank bottom component. | US599965 | ||||||||||||||
To enhance usability and ensure data accuracy, the RBI 581 Risk Analysis is marked for recalculation if you update the following fields, which are used for Inventory Component Mass calculation:
| US599904 | ||||||||||||||
To enhance usability and ensure data accuracy, if an RBI Component is inactivated, the RBI 581 Risk Analyses linked to all the RBI Components in the Inventory Group are marked for recalculation. To facilitate this enhancement, a new field named Calculation Required has been added to the RBI 581 Risk Analysis family. When an analysis needs recalculation, the Calculate button ( ) appears in orange colour. | US599903 | ||||||||||||||
| To enhance usability, you can now capture the date on which the Risk or Damage Factor will exceed the threshold up to 30 years past the Plan Date on the RBI 581 Risk Analysis. To facilitate this enhancement, a new field named Risk Threshold Date has been added to store the resulting date. The number of years past Plan Date to calculate can be updated by setting the new field, Maximum Years for Risk Projection. | US594964 | ||||||||||||||
| To adhere to API 581 Third Edition, Addendum 2, if coating fails at the time of inspection, the Coating Adjustment will be set to 0. To facilitate this enhancement, a new field named Coating Failure? has been added to the RBI 581 External Cracking Damage Evaluation and the RBI 581 External Damage Evaluation families. |
| ||||||||||||||
| The Release Type calculation for RBI 581 Consequence Evaluations now adheres to API 581 Third Edition, Addendum2. To facilitate this enhancement, the Enable Release type calculation as per RFI-8388 preference has been removed from the RBI Admin Preferences; The Release Type field will now be calculated as per RFI-8388 automatically. | US591986 | ||||||||||||||
| The Strength Ratio calculation for RBI 581 Thinning and Lining Evaluations and RBI 581 External Damage Evaluations now adheres to API 581 Third Edition, Addendum 2. To facilitate this enhancement, the Strength Ratio will only use equation 2.14/2.40/2.54, the formula including minimum thickness, when the Override Minimum Required Thickness is set to true. | US591983 | ||||||||||||||
| The Age calculation on RBI 581 Cracking Damage Evaluations and RBI 581 External Cracking Damage Evaluations only considers the effective inspections now. To facilitate this enhancement, if the Highest Effective Inspection Level is Poorly Effective or Ineffective(None), the Date in Service is used instead of the Target Inspection Date in the Age and the Time Since Last Inspection calculations. | US579049 | ||||||||||||||
The display value of the Atmospheric Condition field on RBI 581 Cracking Damage Mechanism Evaluations and RBI 581 External Cracking Damage Mechanism Evaluations now adheres to the RBI 581 Specification. To facilitate this enhancement, the following system codes have been updated in the Atmospheric Conditions System Code Table:
| US571823 | ||||||||||||||
| The formula for calculating Age in RBI 581 External Cracking Degradation Mechanism Evaluations and RBI 581 External Degradation Mechanism Evaluations now adheres to API 581 Third Edition, Addendum 2. To facilitate this enhancement, the Coating Adjustment can now be overwritten using two new fields, Override Coating Adjustment and User Coating Adjustment. | US571822 | ||||||||||||||
To adhere to API 581 3rd Edition, Addendum 2, two new geometry types are now supported. To facilitate this enhancement, the following values have been added to the MI_581_Component_Geometry_Types System Code Table and will appear in the Geometry Type field picklist on RBI Component and RBI 581 Risk Analysis records
| US571821 | ||||||||||||||
To adhere to API 581 Third Edition, Addendum 2, the calculation for the RBI 581 Consequence Evaluation now supports several new materials. To facilitate this enhancement, the following Material Cost lookup fields have been added:
| US571820 | ||||||||||||||
| The formula for calculating susceptibility on 581-Alkaline Carbonate Stress Corrosion Cracking Degradation Mechanism Evaluations now adheres to API 581 Third Edition, Addendum 2. To facilitate this enhancement, the RBI 581 Calculate Susceptibility - Alkaline policy is deprecated and has been marked inactive. | US571819 | ||||||||||||||
The formula for calculating corrosion rate of carbon steel for 581-Hydrofluoric Acid Corrosion Degradation Mechanism Evaluation now adheres to API 581 3rd Edition, Addendum 2. To facilitate this enhancement, the following items have been modified:
| US571818 | ||||||||||||||
The formula for calculating susceptibility on 581-Chloride Stress Corrosion Cracking Degradation Mechanism Evaluations now adheres to API 581 Third Edition, Addendum 2. To facilitate this enhancement:
| US571816 | ||||||||||||||
| The formula for calculating Component Damage Cost on RBI 581 Consequence Evaluations now adheres to API 581 Third Edition, Addendum 2. To facilitate this enhancement, a new field, Cost Escalation Factor, has been added to the RBI 581 Consequence Evaluation family with a default value of 1. | US571815 | ||||||||||||||
You can now generate RBI 581 Recommendations for Heat Exchanger-Channel components. To facilitate this enhancement, the following queries have been modified:
| US571467 | ||||||||||||||
| Only effective Inspections will now be considered for RBI 581 Degradation Mechanism Evaluations. To facilitate this enhancement, Inspections with Ineffective confidence will not be considered when setting the Last Known Inspection Date field for RBI 581 Degradation Mechanism Evaluations. | US569635 | ||||||||||||||
| To enhance usability, you can now determine Susceptibility Type of a Component from Inspection History. To facilitate this enhancement, a new field, Cracking Detected?, has been added to the Inspection Confidence Evaluation family. You can access this field from the Inspection Confidence section of an Inspection. When Inspections are linked to RBI 581 Cracking Damage Evaluation or RBI 581 External Cracking Damage Evaluation, if Cracking Detected?, is selected for any of the linked Inspections, the Susceptibility Type will be set to Detected. | US569500 | ||||||||||||||
| To enhance usability, you can now inactivate an RBI Component linked to an Inventory Group, which will in turn be removed from the Inventory Group. | DE204733 | ||||||||||||||
| To ensure that updated calculation inputs are considered, if the Use Calculated Inventory field is true on RBI 581 Consequence Evaluations, then the Inventory Group Mass and Inventory Component Mass fields will be populated when calculating the related RBI 581 Risk Analysis. To facilitate this enhancement, now, Inventory Group Mass and Inventory Component Mass fields will not get updated before calculating the analysis. | DE156510 |
| Description | Tracking ID |
|---|---|
The Risk Based Inspection 581 Calculation Engine no longer uses the following policies. These policies have been removed from APM:
| US600950 |
RBI 580
| Description | Tracking ID |
|---|---|
| You can now export RBI Criticality Analyses with Degradation Mechanism Evaluations and Consequence Evaluations configured through the RBI Application Settings, Flexible Calculation Configurations. To facilitate this enhancement, the DME_Custom sheet will now be included in the export. | US593817 |
To enhance usability, PRD Pop Test Checklist now supports multiple Degradation Mechanisms. To facilitate this enhancement, Inspection Confidence Evaluations has been enabled for PRD Pop Test Checklist and can be accessed from the Inspection Confidence section of the Inspection. In addition, the PRD Pop Test Checklist datasheet has been updated and the following fields have been removed from the datasheet:
|
|
| You can now configure the Criticality Consequence Evaluation calculation to use a Leak Size based on the related Degradation Mechanism Evaluations instead of the Equipment type. To facilitate this enhancement, a new RBI Global Preference, Enable Leak Size Based on Degradation Mechanism, has been added. If you select this check box, you must add the Degradation Mechanism Leak Size records for each Degradation Mechanism in their system. Otherwise, by default, the minimum value of the diameter and 16 inches is considered. | US578984 |
| Description | Tracking ID |
|---|---|
| Previously, if you activated the Risk Based Inspection license (which is used for RBI 580) without activating the RBI 581 license, you could not create or modify an alternative Inspection Plan for an RBI Asset. This issue has been resolved. | DE204541 |
| Previously, when you archived an Inspection Group, the related recommendations, which were in the Archived state, still appeared in the Inspection Plan workspace of the Asset. This issue has been resolved. | DE156817 |
Previously, in an Inspection Group, the Current Percentage Selection was incorrectly displayed as 100 percent if both the following conditions were satisfied:
| DE146359 |
Root Cause Analysis
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| The Analysis Type field is now set based on a system code table even for a non-English language user. | US587086 |
| You can now assign a team as the team members to an RCA. | US585145 |
| To enhance functionality, users with the ProAct Admin and Superuser roles can now change and update the Principal Analyst role for visible analyses. Superuser can also change the Principal Analyst for restricted analyses as well. | US585078 |
| To enhance usability, the associated Analysis of the failure nodes imported from RCM, FMEA, RCA, or Hypotheses from RCA are now displayed. | US549169 |
| The Zoom settings on the Logic Tree and the Event Diagram remain unchanged now even when you navigate to a different page. | US541410 |
| To enhance usability, the Event Timeline tab now appears above the Logic Tree tab in the left pane. | US390864 |
| Description | Tracking ID |
|---|---|
| Previously, in print preview of the Preserve record report, the date overlapped the Parts description. This issue has been resolved. | DE206584 |
| Previously, in an RCA Recommendation, when the Target Completion Date was in the past, an incorrect error message appeared. This issue has been resolved. | DE205692 |
| Previously, when a user configured with a non-English culture setting tried to modify the team members list in an analysis, the Roles were not translated in the edit view. However, in display view, they were translated as expected. This issue has been resolved. | DE205033 |
| Previously, when navigating away from the Communicate Findings tab in a Root Cause Analysis, the Send button was still visible in other tabs. This issue has been resolved. | DE200447 |
| Previously, the query, Get Image Reference Documents Query, failed in an Oracle database. This issue has been resolved. | DE200370 |
| Previously, when adding images to reference documents attached in an RCA analysis, the formatting was incorrect. This issue has been resolved. | DE195967 |
Rounds Data Collection
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, while taking Readings for a Route from the browser with the filter option selected to show the Incomplete checkpoints only, the readings were not saved. This issue has been resolved. Now, irrespective of the filter option selected, all readings are saved. | DE206740 |
Rounds Designer
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you tried to Schedule a route or a Measurement Location on particular days of a month, an error message appeared, indicating that you could not convert a string to an integer. This issue has been resolved. Now, you can schedule a route or a Measurement Location on any day. | DE206885 |
| Previously, while taking Readings for a Route from the browser with the filter option selected to show the Incomplete checkpoints only, the readings were not saved. This issue has been resolved. Now, irrespective of the filter option selected, all readings are saved. | DE206740 |
Rounds Pro
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To provide an enhanced data collection experience, barcode scanning is now available in Rounds Pro. | US579271 |
| Description | Tracking ID |
|---|---|
Previously, the following fields were erroneously displayed:
| US574787 |
| Previously, while generating Health Indicators, the following message appeared, stating that Reading were tracked as history-only Health Indicators. This issue has been resolved. The message no longer appears. | US561507 |
| Previously, when you assigned users to an existing Route, all the users were not populated. This issue has been resolved. | DE201326 |
Rounds Pro Mobile
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| You cannot delete a Recommendation that is checked in (indicated by a headline in the Recommendation). The Delete button is disabled in such scenarios. | US582763 |
To improve usability, Round Pro mobile app now supports the following User Culture settings:
| US579662 |
| To prevent accidental deletion of Recommendations, now, a deletion confirmation message appears when you select the Delete Recommendation button for both Standalone and Normal Recommendations. Only after you select Yes, the recommendation is deleted. | US577382 |
| Description | Tracking ID |
|---|---|
| Previously, the last reading value for conditional steps was not displayed in the Rounds Pro mobile app after the route has been checked in. This issue has been resolved. | DE204047 |
| Previously, after checking out a Route, if you went offline and then online, your login instance was not retained, and the Route was indicated as checked out by a different user. This issue has been resolved. | DE203543 |
| Previously, after checking in and opening a route, if you attempted to add text in the Search box to filter a step, the search text was not visible. This issue has been resolved. | DE201590 |
Rules
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to compile rules in Visual Studio, a large number of warning messages were displayed that were not applicable. This issue has been resolved. Now, the number of warning messaged have now been reduced. The remaining warnings messages are due to Visual Studio adding references that are not used by GE Digital APM. | DE199368 |
Search
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if you closed an advanced search tab, an error occurred. This issue has been resolved. | DE204288 |
Security Manager
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, when you specified the Max Password Age LDAP attribute in the Active Directory as 0, and then changed your AD password and executed LDAP sync, you could not login to APM. This issue has been resolved. | US592798 |
Single Sign-On
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| To enhance security, if SSO is enabled and Single Logout is configured, when you log out of the APM mobile application, you are logged out of the third-party identity provider (IDP) application as well. Therefore, when you attempt to access the APM mobile application the next time, you are first redirected to the IDP login page where you must enter your SSO credentials again to log in. | US573509 |
| Description | Tracking ID |
|---|---|
| If you attempt to log in to the APM mobile application using SSO on a Windows device, an error occurs. As an LDAP user, you can login to the APM mobile application without using SSO. To do so, enter your LDAP username and password in the login page, and then select Login. To log in again, you must re-enter the credentials. | US604143 |
SIS Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To support the latest updates on Exida Libraries, APM now implements the following libraries and calculation engine:
| F70314 |
The validation function has been enhanced to include all fields suffixed with an asterisk (*) in the following datasheets, even if any of the field receives a default value for calculation:
| US599913 |
| When you copy an Instrumented Function, the associated Instrumented Data of all the selected records are also copied. To facilitate this enhancement, a new window Select the record(s) to Copy now appears, enabling you to select from the related families and records that you want to copy. | US591608 |
| To enhance usability, you can now identify and search devices marked as Proven In Use in the sensor, logic server, and final elements. To facilitate this enhancement, the search pop-ups have been converted to standard result grids. A new column, Proven In Use has been added to the result grid to filter out the devices that you have marked as Proven In Use. | US585384 |
| To enhance usability, you can now import Protective Instrument Loops with a maximum of 10 groups from Exida. | US582865 |
| To enhance usability, you can now view the Risk Reduction Factor and SIL required in the Loop Diagram and Calculation page and Datasheet. To facilitate this enhancement, the Required Risk Reduction Factor field is added in the Protective Instrument Loop datasheet. Also, the SIL-Required and Required Risk Reduction Factor fields are added to the Loop Diagram and Calculation page. | US577194 |
| To enhance usability, you can now upgrade Protective Instrument Loops in bulk from exSILentia V3 to V4. The Protective Instrument Loops will then use the exSILentia V4 calculation engine. To facilitate this enhancement, a button named Upgrade All to V4 is now available in the SIS Admin Preferences page. | US476806 |
| Description | Tracking ID |
|---|---|
| Previously, in the Protective Instrument Loop datasheet, the drop-down picklist of the Test Architecture Constraints field, had duplicate values. This issue is now resolved. | DE205310 |
| Previously, in a Protective Instrument Loop Sensor Group or a Protective Instrument Loop Final Element Group with multiple Sensors or Final Elements respectively, if you removed the Sensors or Final Elements such that only one of them remained, the calculation of the Protective Instrument Loop failed. This issue occurred only if you selected the Diverse check box. This issue has been resolved. | DE204116 |
| Previously, when you imported an ExSILentia V3 (.exi) file, Unit ID value for the Safety Instrumented Function was not populated. This issue has been resolved. | DE204029 |
| Previously, in a Protective Instrument Loop Sensor, the Analog Trip field contained 0 as one of the options. This issue has been resolved. Now, the value appears as None. | DE203996 |
| Previously, in a Protective Instrument Loop report, the Proof Test Interval (PTI) value for a Sensor System and Final Element System appeared as N/A. This issue has been resolved. | DE203437 |
| Previously, if a custom device was added to the Protective Instrument Loop Sensor, the Analog Trip field was not editable in the Protective Instrument Loop Sensor datasheet. This issue has been resolved. | DE203085 |
| Previously, when you attempted to access a Protective Instrument Loop Final Element record using global search, an error occurred. This issue has been resolved. | DE200353 |
| Previously, if the Calculated SIL Level for a LOPA was 0, and if you used the LOPA to create a SIL Assessment, the Risk Reduction Factor, Probability of Failure, and Availability Target fields contained incorrect values. This issue has been resolved. | DE199411 |
| Previously, the Proof Test Tasks that were linked to a Functional Location did not appear in the SIS Management Overview page. This issue has been resolved. | DE196005 |
State Management
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, the state assignment history displayed dates in the Coordinated Universal Time (UTC). This issue has been resolved. Now, the state assignment history displays dates in the time zone specified for your APM user account. | DE206032 |
Teams
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
| Previously, if your APM system used an Oracle database, when you searched for a user to add to a team, the search results did not contain all the matching users. This issue has been resolved. | DE205912 |
| Previously, when you modified a Team, the description of the Team Role of the team members is stored in the database instead of storing the system codes. As a result, if the language set in APM was other than English, the Team Role was not translated. This issue has been resolved. Note: When your APM database is upgraded to the latest version, the existing Teams data is modified to store the Team Role system codes. | DE205861 |
Thickness Monitoring
This topic provides a list of product changes released for this module in this version.
| Description | Tracking ID |
|---|---|
To enhance the usability of the TM Quick View page, the following enhancements have been made in the TM Quick View table:
|
|
| To enhance usability, the Last Measurement Date and Last Measurement Value fields in the Thickness Measurement Location’s Corrosion Analysis record will now be populated upon calculation even if there is only one measurement against a Thickness Measurement Location. Previously, the fields were not populated until there were at least two measurements associated. | US586832 |
| You can now load both Equipment and Functional Location data in a single Excel file using the Thickness Monitoring (TM) Equipment or Thickness Monitoring (TM) Piping Equipment data loader. To facilitate this functionality, the ASSET_FAMILY_ID column can be added to the Assets worksheet. This column should have the Family ID of the Equipment or Functional Location. If the column is not added or contains null values, APM will consider the data loader as Equipment. | US579346 |
To enhance the usability of the Measurement Data Entry page, the following changes have been made in the Measurement Data Entry table:
|
|
You can now export Thickness Measurement Data into an Excel spreadsheet from either of the following pages:
When exporting, you get an option whether to export Measurements or not. If you select not to export Measurements, the Measurement workbook will contain all the look up fields without the Measurement data. | US576946 |
| You can now delete Asset Corrosion Analysis and the Corrosion Analysis Settings records. Note: Delete option will be enabled only if the Asset does not have any associated TML groups or TMLs. | US571125 |
| To improve usability, the TM Analysis Output page now displays the first three available TML IDs in the Based On column for Controlling Corrosion Rate, Scheduled Next Inspection, and Projected T-Min Date. The View All option will still be available when there are more than three TMLs associated with the value. | US569835 |
To enhance the usability of the Thickness Measurement Location table in Non-piping Asset workflow, the following changes have been made in the Thickness Measurement Location table:
| US569829 |
To enhance usability of the Olympus 38DL Plus Ultrasonic Thickness Gage datalogger device, support for importing measurements into Thickness Monitoring taken on a device with thru coat mode enabled has been added. The following changes have been incorporated to support the different file modes:
Note: When attempting to capture measurements on the device with thru coat mode enabled, the datalogger file must first be sent from APM with the File Mode Options set to Thru-Coat. | US560327 |
| Description | Tracking ID |
|---|---|
| Previously, you were unable to relocate a Thickness Measurement Location to an Asset if the Asset had child TML Groups. This issue has been resolved. | US590957 |
| Previously, when calculating the Statistical Corrosion Rate, the corrosion rates for TMLs with negative corrosion rates were used for the calculation. This issue has been resolved. Now, for TMLs with negative corrosion rates, the values are substituted with zero for the purpose of calculation. | US569838 |
| Previously, if you modified the Corrosion Analysis Settings of an Asset, some of the settings were not cascaded to the TMLs that were directly linked to the Asset. This issue has been resolved. | DE206155 |
| Previously, if you tried to spread the Corrosion Analysis settings from an Asset to a TML Group or a TML, the default Inspection Interval was not updated in the Corrosion Analysis settings. This issue occurred only if the TML Group on the Asset did not contain TMLs. This issue has been resolved. | DE206151 |
| Previously, if you modified any settings under the Asset Corrosion Rate section of the Corrosion Analysis Settings page for an asset and chose not to spread those changes to any related TML Groups or TMLs, then the subsequent value was not updated correctly for the Controlling Corrosion Rate on the asset’s Corrosion Analysis. This issue has been resolved. | DE205158 |
| Previously, for a Thickness Measurement marked as Nominal with the same Measurement Taken Date as the first actual measurement, when the second actual measurement was added, the nominal measurement was not inactivated. This issue has been resolved. | DE205109 |
| Previously, in the Global Preferences workspace, when the Correct Measurements Based on Growth check box is enabled, the Nominal Measurement was considered for correcting measurement based on growth. | DE205107 |
| Previously, when you configured Use Minimum Measurement Interval for corrosion Rates, the field values for Near Measurement date and Near Measurement were not updated correctly. This issue has been resolved. | DE204918 |
| Previously, when you accessed the Bulk Edit TMLs window, your datasheet preference for the Thickness Monitoring Location family was overwritten to use the TML Bulk Edit datasheet. This issue has been resolved. Now, your datasheet preference for the Thickness Monitoring Location family is changed only when you select a different datasheet in the TML Details section in Thickness Monitoring, or in Record Manager. | DE204529 |
| Previously, Undo Last Movement in Piping Rotations did not pick up the latest pipe movement if more than one movement was done on the same day. This issue has been resolved. | DE203231 |
| Previously, when viewing the TMLs tab of an asset in Thickness Monitoring, the column Remaining Life was displayed. The name of the column created a confusion, as the value displayed in this column showed the amount of remaining life as calculated from today rather than the value stored in the Remaining Life field, as the name of the column indicated. To remove the confusion, this column has been renamed Remaining Life From Today. | DE200905 |
| Previously, if all Thickness Measurement Locations on an asset were inactive, the Next Date field in the Thickness Monitoring Task family was not set to null. This issue has been resolved. | DE198004 |
| Previously, calculation of large number of assets in Thickness Monitoring failed. This issue has been resolved. Performance improvements have been incorporated for bulk calculations. | DE194891 |
| Previously, in the Analysis Overview page, when you navigated back using the Back button in the left navigation pane, the data in the center pane was not updated. This issue has been resolved. | DE157422 |