V5.0.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, when you select the job status component, job error details appear in a separate window on the same page. | US447214 |
To enhance usability, the catalog query has been redesigned for the Recommended Actions section. For more information on modifying the query, refer to KBA 000039672. | DE182275 |
Description | Tracking ID |
---|---|
Previously, in the Strategy Actions workspace of the Action Management page, when you modified an action and selected Apply Updates, the action took longer than expected to load. This issue has been resolved. | DE187468 |
Previously, when you filtered the Performance Recommendations for a state, such as Completed, Cancelled, or Rejected, you were unable to view the Manage State Assignments option. This issue has been resolved. | DE180732 |
Previously, while implementing actions as EAM Maintenance Plan, the export file was named as EAM Action Mapping. Now, the export file has been renamed to Strategy Export. | DE179764 |
Previously, in the Implement Actions section, you were unable to implement an EAM Maintenance Plan when you selected actions from more than one asset. This issue has been resolved. | DE178356 |
Previously, when you attempted to supersede a Policy Recommendation, an error occurred. This issue has been resolved. The relationship definition between Policy Recommendation (predecessor) and Policy Recommendation (successor) entity families is now added to the Has Superseded Recommendations relationship family. | DE175274 |
Previously, in the recommendation datasheet for a Recommended Action, the column names in the Select User window for the following fields were not translated based on the language setting configured for your user account:
| DE155765 |
Advanced Visualization
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Advanced Visualization module has been introduced in APM and provides you a powerful way to visualize and collaborate on the data that is available within APM Classic by connecting, aggregating, and analyzing data through business intelligence (BI) like capability. Important: APM requires the use of Webfocus software from TIBCO, which is provided as part of the installation of this product. TIBCO Webfocus is provided strictly for use within APM and is not licensed to you for any other use outside of this product. Any other use is prohibited without an additional license from TIBCO. | US561552 |
API Documentation
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To maintain backward compatibility, all APIs will now have a version as part of the base URL. For example, api/custdev/core/ will now be /v1/api/custdev/core/. | US562121 |
APM Connect
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The APM Connect EAM Jobs feature has been removed from the Admin>Operations Manager page. | US557778 |
APM Data Extraction
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, if several rules were configured for a family, when you attempted to extract data with an OData request, the rules were triggered and the data extraction process took longer than expected. This issue has been resolved. Now, the rule execution has been disabled, resulting in improved performance. | DE182079 |
APM Mobile Application
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, reference documents that were added to a checkpoint opened automatically on the GE Digital Mobile application for Windows. This issue has been resolved. Now, the GE Digital Mobile app prompts you to save the reference document on your device and then open it. | DE191615 |
Previously, a route that was marked done after you had cleared its values in the APM mobile application, entered into a locked state and a warning message appeared that all readings were not uploaded. This issue has been resolved now. | DE154583 |
Previously, when you entered readings for a route in the APM mobile application, and under certain conditions when you applied the Only Incomplete Checkpoints filter, the readings were not saved. This issue has been resolved. Now the APM mobile application retains the readings. | DE154392 |
Previously, when the APM mobile application was run on an iOS device and you used the drop-down data entry control to enter readings, the application would freeze sometimes. This issue has been resolved. | DE153730 |
Previously, in some cases, readings entered in the APM mobile application did not get saved to the APM database. This issue has been resolved. | DE146093 |
Previously, in Rounds Data Collection, the offline data forms did not display the default values. This issue has been resolved and the default values are now visible. | DE144483 |
Description | Tracking ID |
---|---|
Currently, Legacy APM Mobile app for Windows application does not support GeoLocation feature during data collection. This feature will be re-enabled in the future releases. | US561644 |
APM System Monitoring
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The APM System Monitoring and Performance Monitoring features have been deprecated. | US458612 |
APM Upgrade
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To use the APM Database Comparison Tool, you need to first copy all files from the Content Generation Utility (C:\Program Files\Meridium\upgrade\DBUpgrade\Utility) to the APM Database Comparison Tool (C:\Program Files\Meridium\upgrade\DBUpgrade\DatabaseReport). | DE193523 |
Asset Criticality Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve the usability, export of multiple Asset Criticality Analyses will use background job infrastructure from the Asset Criticality Analysis Overview page. | US532282 |
To improve usability, in an ACA Analysis, when you select the job status component, send to job error details appear in a separate window on the same page. | US447208 |
Description | Tracking ID |
---|---|
Previously, in an Asset Criticality Analysis, if an EAM configuration was used with multiple systems, sometimes an incorrect EAM system was targeted and a validation error occurred. This issue has been resolved. | DE152565 |
Previously, if you modified the criticality of an Analysis to a lower value, the modified value did not appear in the ACA Overview dashboard. This issue has been resolved. | DE150707 |
Previously, asset details and criticality distribution information did not respond properly to the asset filter. This issue has been resolved. | DE150118 |
Previously, when you accessed APM using a Chrome browser, there was a performance issue while saving records through the datasheet. This issue has been resolved. | DE149743 |
Previously, when using an EAM configuration with multiple systems, sometimes an incorrect EAM system was configured causing a validation error. This has been resolved. | DE146801 |
Previously, when using risk matrix in ACA, if a risk assessment was previously defined, when you attempted to set the risk assessment to Not Applicable in each risk category, the criticality of the asset did not change to Undefined or Not Applicable. Additionally, ACA retains the risk assessment value that was previously defined. This issue has been resolved. | DE145472 |
Previously, in an Asset Criticality Analysis you could add, link, unlink, edit, or delete the reference documents even in the Approved state. This issue has been resolved. | DE171592 |
Previously, when you changed a Risk Matrix that was associated with the site to a different Risk Matrix, you were still able to update the assessment using the old Risk Matrix. This issue has been resolved. | DE179424 |
Previously, when you created an Asset Criticality Analysis, you were able to access all the tabs. This issue has been resolved. Now, only the Analysis Definition tab is enabled until the new analysis is saved. | DE179929 |
Previously, when you attempted to add an asset, the Asset field in the Enter Parameter Values window displayed Home by default. This issue has been resolved. Now, it displays the asset hierarchy value. | DE184381 |
Asset Hierarchy
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The following columns are now required in the Query you use to define an Asset Group:
Note: The new required columns will be added automatically to the query when you access an existing query-based asset group. |
US521226 US510070 |
You can now see the asset type in the Asset Hierarchy page. | US510545 |
To improve usability, you can now view the options in the Asset Hierarchy Filter drop-down lists in alphabetical order. | US489034 |
You can now search the Asset Hierarchy with a search term containing at least two characters or alphanumeric values. | US476414 |
You can now set the number of assets to be displayed in asset hierarchy. To facilitate this enhancement, Page Size field has been added in the Asset Hierarchy Configuration workspace. | US472624 |
You can now define a priority between the parent-child relationship in the asset hierarchy configuration. This allows the hierarchy to be displayed when it includes assets related to more than one parent. To facilitate this enhancement, Parent Priority field has been included in the Asset Hierarchy Configuration workspace. | US444360 |
You can now view when the asset hierarchy was last built. To facilitate this enhancement, the Build Status of the last build and a refresh button has been added in the Asset Hierarchy Configuration workspace. | US328150 |
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. | US514053 |
Previously, you could only edit an Asset Group that you created. This issue has been resolved. Note: You can now edit any asset group if you are a super user or you are assigned to the MI Foundation Admin role. | DE154702 |
Previously, the scheduled Asset Hierarchy rebuild task failed and an error message appeared. This issue has been resolved. | DE145292 |
Asset Strategy Implementation
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve the usability, when you select the job status component in ASI, the job error details now appear in a separate window on the same page. | US447211 |
To enhance 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 |
Description | Tracking ID |
---|---|
Previously, when you updated an ASI package with changes to a 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 also required. | US501490 |
Previously, when you implemented an ASI Implementation Package, the associated WMIs were updated in SAP even if the corresponding WMIs were not modified in APM. This issue has been resolved. | US469281 |
Previously, in the child work management item hierarchy for an ASI Package, you could not see the full item description when it was long. This issue has been resolved. Now, a hover text is added to display the full description text. | US467480 |
Previously, when you sent the operation data from ASI to SAP, the long text value in SAP was not aligned properly. This issue has been resolved. | DE172198 |
Previously, when you accessed APM using a Chrome browser, there was a performance issue while saving records through the datasheet. This issue has been resolved. | DE149743 |
Previously, when updating the Interval for ASI maintenance packages directly in the package, for some of the intervals, it was not updated appropriately in SAP after implementing the package. This issue has been resolved. | DE149596 |
Previously, when you updated the intervals for the actions in ASM that were linked to the respective operations in an ASI package, and then activated the strategy, the updates were not visible in the maintenance package linked to the operations or in the Maintenance packages screen in the Tasklist level. This issue has been resolved. | DE140099 |
Previously, when you attempted to implement a package with Process Resource Tool (PRT) linked to the operations, an error occurred. This issue has been resolved. Now, you can only import the document type PRT from SAP. You cannot modify or push the PRT records to SAP. | DE174208 |
Previously, when you deleted an operation associated with an ASI maintenance package and the package was implemented, an error occurred. This issue has been resolved. | DE179078 |
Asset Strategy 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 perform a bulk edit on actions from the Manage workspace of the System Strategy page. | US559870 |
To improve usability, the Implement Action as EAM Work Request option is renamed to Implement as Recommendation and you can now select the Create EAM Work Request as an optional functionality. | US559429 |
To improve usability, you can now bulk edit the Risks and Actions of the ASM Strategy and ASM Template. To facilitate this enhancement, a new icon () , has been added to the Risks and Actions section. | US555736 |
To improve usability, when you apply the template as a master or as a copy, the Strategy Description and Note field values are now copied to the Controlled Asset Strategy record. | US526085 |
To improve usability, in an Asset Strategy, you can now optimize the ASM Template. | US525440 |
To improve usability, when you select the asset strategy and save it as a template, the selected ASM template appears in a new window with the Asset Strategy Template datasheet. | US523633 |
To improve the usability, export of multiple asset strategies will use background job infrastructure from the Asset Strategy Management Overview page. | US513337 |
To improve user experience, you can now directly access the promotional information and know more about purchasing Asset Strategy accelerator templates from the ASM Overview page. | US513028 |
To improve usability, in ASM, when you select the job status component, job error details appear in a separate window on the same page. | US447223 |
To improve usability, in an Asset Strategy or Template Activation and Apply Template, when you select the job status component, background error details appear in a separate window on the same page. | US447222 |
To improve usability, in the ASM Overview page, when you select the job status component, Import from EAM and Import from Rounds job error details appear in a separate window on the same page. | US447215 |
To enhance usability, you can now move controlled asset strategies from one template to another. | US414703 |
Description | Tracking ID |
---|---|
Previously, the size of the Implement as EAM Maintenance Plan window was smaller and therefore you could not view all columns in the window. This issue has been resolved. Now, the size of the Implement as EAM Maintenance Plan window has been increased and you can view all the columns without scrolling. | US539759 |
Previously, when an Asset Strategy was part of a large System Strategy, the APM application took longer than expected to save Actions. This issue has been resolved. | US452194 |
Previously, there were performance issues when deleting a strategy. The issue has been resolved. | US445909 |
Previously, in the Implement Actions workspace of the Asset Strategy page, when you modified an action and selected Apply Updates, the action took longer than expected to load. This issue has been resolved. | DE187468 |
Previously, when you promoted an RCM or FMEA template to ASM, it appeared in both the Templates and Asset Strategies sections of the Asset Strategy Overview page. This issue has been resolved. Now, the promoted template appears only in the Templates section. | DE186588 |
Previously, when you attempted to apply an ASM template as master to the asset, new action IDs were generated based on the strategy ID. This issue has been resolved. Now, when you apply an ASM template as a master to the asset, you can configure if you want to copy the action ID from the template or generate new action IDs. To facilitate this change, you must delete the Action ID from the Excluded Action Fields while applying Template As Master field from the ASM Preferences tab in the ASM Admin page. | DE182095 |
Previously, while implementing an action as an EAM Maintenance Plan, if the action record included special characters, the CSV file did not generate correctly. This issue has been resolved. | DE181834 |
Previously, while implementing actions as EAM Maintenance Plan, the export file was named as EAM Action Mapping. Now, the export file has been renamed to Strategy Export. | DE179764 |
Previously, in the Recommendation section, if your culture setting had a culture other than English, the State fields were not translated to the specific language selected in the culture setting. This issue has been resolved. | DE166047 |
Previously, when you accessed APM using a Chrome browser, there was a performance issue while saving records through the datasheet. This issue has been resolved. | DE149743 |
Previously, when you make a strategy Active after unconsolidating the consolidated actions, an error occurred. This issue has been resolved. | DE148009 |
Previously, if you deleted the Actions associated with a deleted risk, and then activated the strategy, the deleted risk appeared twice with the same ID. This issue has been resolved. | DE147606 |
Previously, if a Security Role was assigned to a state associated with the Asset Strategy family, when you attempted to create a System Strategy, an error occurred. This issue has been resolved. | DE145463 |
Previously, if the minimum threshold value for a risk matrix was not set to zero, the risk values in the risk card for a given strategy were not correct. This issue has been resolved. | DE141584 |
Previously, in the Implement Actions workspace, when an action was linked to an EAM plan with multiple maintenance items associated to the maintenance plan, an incorrect EAM work order was displayed. This issue has been resolved. | DE173400 |
Previously, in the Templates tab of an Asset Strategy Overview page, when you attempted to save the Risk Matrix values for a Risk with multiple mitigated actions linked to an asset template, an error occurred, and the Risk Matrix values were not saved. This issue has been resolved. | DE173755 |
Previously, when you attempted to make a copy of an Asset Strategy template with the custom fields or any baseline fields that were set as the Required Behavior, an error occurred. This issue has been resolved. | DE173627 |
Previously, when you attempted to query the Risk Rank table, a Risk value with a lengthy decimal was returned. This issue has been resolved. | DE171050 |
Previously, in a Controlled Strategy, when you created an action, the Action ID that was generated was not unique. This issue has been resolved. | DE174879 |
Previously, when the ITS URL in an EAM System record was not configured, the value in the ID field of the EAM Plan record was displayed incorrectly. | DE175483 |
Previously, when you attempted to export the ASM template from an ASM Overview page, it contained an incorrect field ID column in the Risks worksheet. This issue has been resolved. | DE175323 |
Previously, when you changed a Risk Matrix that was associated with the site to a different Risk Matrix, you were still able to update the assessment using the old Risk Matrix. This issue has been resolved. | DE179424 |
Previously, when the ITS URL in an EAM System record was not configured for the SAP system, the hyperlink to navigate to the EAM Plan or EAM Plan Details records from the Implement Actions section displayed incorrectly. This issue has been resolved. | DE180918 |
Previously, when you attempted to create a strategy, the Asset field in the Enter Parameter Values window displayed Home by default. This issue has been resolved. Now, it displays the asset hierarchy value. | DE184381 |
Description | Tracking ID |
---|---|
When the Asset Strategy is a part of a System Strategy, an activation of an Asset Strategy may take longer than the expected time. | DE194756 |
Asset Strategy Optimization
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, the simulation for optimizing an asset strategy did not get completed if custom rules were defined in the strategy. This issue has been resolved. | DE173565 |
Calibration Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now have more control on handling the unsaved results and unfinished tasks while performing Send to Calibrator using Fluke 74x- 75x or Fluke 729 FC Calibrators and also after performing Receive from Calibrator. To facilitate this enhancement:
| F62318 |
To improve efficiency in managing calibration data for a group of assets, the Instrumentation System functionality has been added in the Calibration Management module. Instrumentation Systems can be created for a high-level Functional Location such that you can add assets beneath that Functional Location. The Instrumentation System functionality helps you define, manage, and review the calibration schedule (tasks) and reporting (events) at a system or an instrumentation loop level. | US554245 |
The Work Management Interface functionality is now enabled to support notification creation in addition to work order generation when tasks are created in the application. Additionally, you can select EAM Object, User Status, and Type while creating tasks. | US523942 |
Description | Tracking ID |
---|---|
Previously, when you created a Calibration Profile record and selected the site as Global, you were unable to link assets from different sites. This issue has been resolved. Now, you can link assets based on user-assigned sites. | US555755 |
Previously, in a Functional Test Template datasheet, when you selected the Refresh Equipment Data check box and saved the datasheet, the Equipment or Functional Location values were not copied to the template. This issue has been resolved. | DE184459 |
Previously, in Has Reference Documents relationship family, when you attempted to add the relationship definition between safety related families and reference document, the Reference Document option was not available in the respective family datasheet. This issue has been resolved. | DE172444 |
Previously, when you created a Calibration Event record using a Calibration Template whose Detail records were in a random order, Calibration Result records were displayed in random order. This issue has been resolved. Now, irrespective of the order of the Detail records, the Calibration Result records appear in the correct order based on the test sequence numbers. | DE157282 |
Previously, when you ran Calibration Data Model Upgrade Utility as part of the database upgrade activity, when processing large number of records, the utility stopped responding. In addition, system ran out of memory space during the upgrade. This issue has been resolved. | DE155590 |
Previously, after you created a calibration event and selected a value in the Test Equipment ID box, you could not clear the value. This issue has been resolved. Now, the Clear button has been added to the Test Equipment ID box. | DE155551 |
Previously, in a multi-component Calibration Event record, when you selected a value for the Cylinder ID field and saved the record, only the cylinder expiry date was recorded, while the Laboratory Number field was not populated in the multi-component identification datasheet. This issue has been resolved. | DE154985 |
Previously, when you attempted to update Desired Interval, Min Interval and Max Interval values in the Calibration Task datasheet, an error occurred. This issue has been resolved. | DE121496 |
Description | Tracking ID |
---|---|
You can no longer customize the code to generate a work order because the work order generation for tasks created in APM has been moved into the product code. | |
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 functionality can be achieved using the normal Calibration workflow. So, the Associated Pages functionality has been removed for these families. | DE152310 |
Catalog
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve usability, you can now include leading and trailing spaces in a Catalog folder name. | US529221 |
Description | Tracking ID |
---|---|
Previously, when you selected your personal folder in the Catalog, the workspace displayed “Personal” instead of your name. This issue has been resolved. | DE170888 |
Compliance 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 view the Inspection Task datasheet in a Datasheet window instead of a new tab, when you select the Task ID hyperlink in the existing tasks section of the Inspection Plan page. | US547779 |
To improve usability, in the Compliance Configuration section of the Inspection Management Admin page, when linking assets to Compliance Strategy Templates using the Add Assets Via Finder option, the finder window has been updated to Asset Finder. Now to select an asset, you can select the checkbox next to the asset in the tree. | US521250 |
To improve usability, you can now view the Asset info summary in the Compliance inspection page. To facilitate this enhancement, a new button for Asset info summary has been added to the header of the Inspection Plan page. You can now get a high-level view of the health of an asset which consists of the following information:
If you have Risk Based Inspection licensed, you can configure all the fields and values displayed on the Asset info summary in the Asset Info Configuration workspace under the RBI Admin Preferences page. | US516051 |
Description | Tracking ID |
---|---|
Previously, in the Integrity section of the <Asset Name> workspace, the Compliance Management hyperlink displayed both the count of Assets without Inspection Plans and the count of Inspection Plans. Compliance Management supports both RBI Assets and Inspection Assets, and the count of Assets without Inspection Plans does not apply to RBI. This issue has been resolved. Now, the Compliance Management hyperlink has been updated to show only the count of Inspection Plans. | US547778 |
Previously, in the Assets without Inspection Plans section, when you created or updated an Inspection plan, if the selected asset is already part of another executing job, no error message was displayed. This issue has been resolved. | DE168448 |
Previously, when you approved a modified Inspection Plan that already had Compliance Recommendations in the Implemented state, and RBI Recommendations in the Proposed state, the Compliance Recommendations were reverted to the Approved state. This issue has been resolved. | DE153651 |
Previously, the Build Suggested Templates workflow in Compliance Management failed when you attempted to delete large datasets. This issue has been resolved. | DE149423 |
Previously, when creating an Inspection Plan, if an Asset did not meet the policy criteria of the assigned template, no error message was added to the log file, and the log file incorrectly indicated that the Inspection Plan was created successfully. This issue has been resolved. | DE145734 |
Previously, when creating Inspection Plans or updating Compliance Recommendations for Inspection Plans in bulk from the Compliance Management Overview page, if the job did not complete successfully for a certain Asset, subsequent Assets were not processed until the datasource was made offline and then online. This issue has been resolved. | DE145733 |
Content Change Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The Content Change Management module has been deprecated. | US533582 |
Data Loaders
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, when using the APM Family Data Loader to define the value of a long text field, if the text contained lines that end with a comma and a linefeed, the commas were being removed. This issue has been resolved. | DE179432 |
Previously, when you attempted to load analysis with large number of assets contained in a single Excel sheet, the ACA data loader timed out. This issue has been resolved. | DE142694 |
Description | Tracking ID |
---|---|
Currently, in the TOOLs section, Data Loaders appears as Data Loaders V2. This will be updated to Data Loaders in a future release. | US568652 |
When you attempt to create and update the relationships for a Health Indicator through the APM Family data loader, the data loader will appear to be stuck in the "Ingest" stage and data will not be inserted into APM. For additional information and workaround, review the https://digitalsupport.ge.com/communities/en_US/Article/Unable-to-Create-and-Update-Relationships-for-a-Health-Indicator-Record-through-APM-Family-Data-Loader | DE194409 |
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. | DE145579 |
eLog
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, when you refresh the eLog Overview page, the result grid for the Sign-in/Sign-out Logs section is now sorted according to the last modified date and time, instead of the sign-in date and time. | US545834 |
To enhance functionality, when you select the Create Notification field in an eLog Recommendation, the notification is now carried across to the eLog Record. As a result, notification alerts to linked EAM systems will now show populated Work Request field values for Equipment and Functional Location. | US516335 |
The following fields have been added to the eLog Recommendation family:
| US474385 |
You can now hide the Edit button from the Shift Log workspace in the Shift Summary page, so Shift Members cannot modify a log entry that is saved. | US462244 |
Description | Tracking ID |
---|---|
Previously, when you accessed the Shifts workspace of the eLog Administrator page, the functional locations hierarchy in the functional locations pane took longer than expected to load, and then the process timed out. This issue has been resolved. | DE157056 |
Previously, in the Shift Log workspace, if you selected Show History corresponding to a log entry, the history of the entry appeared in the workspace due to which you could not close the history after viewing it. This issue has been resolved. Now, the history of the entry appears in a separate window. | DE139459 |
Previously, in the STATUS OF ASSIGNMENTS chart, if you used the child families or the state management was enabled for the assignments, the chart did not capture all the data from the query. This issue has been resolved. Now, the chart displays Assignments by Priority. | US522314 |
Previously, if the Hide Edit Button in Shift Log Entries checkbox was not selected in the Settings of the eLog Administrator page, all signed-in users of an active shift log were able to edit the current log entries; to view the previous shift log entries, users were also able to see the Edit option but without the edit permissions. This issue has been resolved. Now, if the Hide Edit Button in Shift Log Entries checkbox is not selected, only originators can edit the log entries in an active shift; to view the previous shift log entries, you should select the View option. | US516201 |
Email Settings
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You will now receive email notifications from the email ID configured in the From field in the Email Settings page. Note: The subject of the email notification for Conditional Alert, KPI, and LDAP feature will now be prefixed by Predix APM. | US459672 |
Failure Modes and Effects Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve the usability, export of multiple Failure Mode and Effects Analyses will use background job infrastructure from the Failure Mode and Effects Analysis Overview page. | US513337 |
To improve user experience, you can now directly access the promotional information and know more about purchasing Asset Strategy accelerator templates from the FMEA Overview page. | US513028 |
To improve the usability, when you select the job status component in FMEA, the job error details now appear in a separate window on the same page. | US447209 |
Description | Tracking ID |
---|---|
Previously, if you added a recommendation to a failure effect in RCM or FMEA, duplicate recommendation IDs were created. This issue has been resolved. | DE185427 |
Previously, when loading an FMEA Analysis Template that has multiple virtual assets, the data did not load correctly. This issue has been resolved. | DE182684 |
Previously, the Asset ID of a consolidated recommendation was incorrect. This issue has been resolved. | DE181288 |
Previously, when you attempted to apply an FMEA asset template to a new FMEA analysis, only the global asset templates appeared in the list of templates. This issue has been resolved. | DE180243 |
Previously, when loading data though dataloader, financial details were not getting updated as per the dataloader worksheet. This issue has been resolved. | DE152522 |
Previously, when you accessed APM using a Chrome browser, there was a performance issue while saving records through the datasheet. This issue has been resolved. | DE149743 |
Previously, if your culture setting was set to a culture other than Invariant Language, when you attempted to export FMEA analyses from the FMEA Overview page, an error occurred. This issue has been resolved. | DE147986 |
Previously, when you reset the value of a mitigated risk to a value less than that of the unmitigated risk, unmitigated risk was not updated with the change in mitigated risk. This issue has been resolved. | DE143700 |
Previously, if you are not an administrator, when creating a failure effect, the risk assessment record was not copied from ACA. This issue has been resolved. | DE143493 |
Previously, as a non-English language user, you were unable to view the Template Type column in the FMEA Overview page. This issue has been resolved. | DE174354 |
Previously, when you changed a Risk Matrix that was associated with the site to a different Risk Matrix, you were still able to update the assessment using the old Risk Matrix. This issue has been resolved. | DE179424 |
Previously, when you attempted to link an asset to an analysis, the Asset field in the Enter Parameter Values window displayed Home by default. This issue has been resolved. Now, it displays the asset hierarchy value. | DE184381 |
Family Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance readability, you can enable rich text formatting for a field with the text data type (from the Fields section of the family). When you do so, a toolbar appears next to the field in a datasheet, which you can use to format the text in the field. | F64567 |
The usability of the Master/Detail Datasheet Builder has been enhanced. To facilitate this enhancement, you can now select the values required to define the datasheet using drop-down list boxes. Additionally, you can edit existing datasheet definitions. | US515838 |
To improve usability, while creating a new family field, you can now select from additional data types. To facilitate this enhancement, in the Information section of the new field workspace, the Data Type drop-down list box now displays four new options:
| US282205 |
Description | Tracking ID |
---|---|
Previously, an administrator was able to change the cardinality of an existing relationship definition, which could lead to data integrity being compromised. This issue has been resolved. Now, modifying the cardinality of relationship definitions is no longer supported. | US568224 |
Previously, when you used a Security Group Query as a condition for Field Behavior, an error occurred. This issue has been resolved. | DE182353 |
Previously, in the Picklist behavior, when you exported and then imported a query that contained prompts, the query was imported without the prompts. This issue has been resolved. | DE178521 |
Previously, when you attempted to modify a datasheet that has the Tabular layout, you could insert a new field only at the bottom of the datasheet. This issue has been resolved. Now, you can add a field anywhere in the datasheet. | DE176264 |
Previously, when you were connected to an Oracle Datasource, and if the Field ID or Physical Column name contained lowercase characters, the field values in the Physical Column were ignored. This issue has been resolved. Now, the Field IDs and the Physical Column names are auto corrected to uppercase characters. | DE166611 |
Family Policies
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
A new catalog query, Public\Meridium\Modules\Policy Manager\Queries\Family Policies with Upgrade Issues, is provided to identify any family policies that could not be successfully upgraded to V5.0.0.0.0. You should review the upgrade logs for any family policy that could not be successfully upgraded and modify the policy model as appropriate. Important: Failure to modify family policies that were not successfully upgraded may result in unexpected system behaviour when inserting, updating, or deleting records in the relevant families. For more information, refer to Upgrade or Update Policy Designer. Please contact GE Vernova Support in case of any difficulty with family policy modifications. | US533620 |
You can now review warnings and errors that occur during the post-upgrade processing of family policy records in the Family Policy UI. To facilitate this enhancement, you can now select the Upgrade Logs tab in the module navigation menu and view or delete the log information for a family policy that is upgraded from an earlier version. | US525819 |
You must now specify the family ID or family key(s) for relationships that you want to delete in a family policy. To facilitate this enhancement, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, and the Successor Family Key(s) sections are added in the Delete Relationship node properties window of Family Policies. Note: When your APM system is upgraded, family policies containing the Delete Relationship node will be upgraded only where the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. | US520092 |
To enhance usability, additional output system fields have been added to the Current Relationship node. Now, the node contains the following output system fields:
| US518099 |
To improve usability, the following output system fields have been added to the Current Entity node:
| US518098 |
You can now use a new Collection output from the Sub Policy node. To facilitate this enhancement, now, when you execute a family policy containing a sub policy node that is not operating on a collection, the values returned from the sub policy are accessible in a collection output containing two columns, (Name and Value) in addition to the single-value outputs. | US511936 |
To enhance functionality, the Family Key is now included in the outputs of the following entity and relationship family nodes:
| US481771 |
You must now specify the family ID or family keys for relationships that you want to create in a family policy. To facilitate this enhancements, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, and the Successor Family Key(s) sections are added in the Create Relationship node properties window in Family Policies. Note: When your APM system is upgraded, family policies containing the Create Relationship node will be upgraded only where the entity keys and the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. | US454314 |
You must now specify the family for entities that you want to delete in a family policy. To facilitate this enhancement, the Family Key(s) section is added in the Delete Entity node properties window of Family Policies. Note: When your APM system is upgraded, family policies containing the Delete Relationship node will be upgraded only where the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. |
|
You can now configure the catalog path input of the Query node to accept the output from a predecessor node. To facilitate this enhancement, select the switch to field input button () under query path to choose an input from another node. Note: When the query path is sourced from a predecessor node, the results collection output from the query node can be used only when you do not need to select a specific column in the collection. | US414721 |
You can now configure the maxSubPolicyDepth. This setting limits the number of levels of sub policy calls and ensures that recursive policy executions cannot occur. The default maximum sub policy depth is set to 10. | US374957 |
The Email node has been enhanced. You can now:
|
|
Description | Tracking ID |
---|---|
Previously, if you defined an R Script to use an input parameter of type Matrix of Values - Numeric, Matrix of Values - Boolean, or Matrix of Values - Character, the matrix of values passed to the R server was transposed. This may have resulted in unexpected results from the R Script node. This issue has been resolved. Note: If you have existing R Scripts using Matrix input parameters, the behavior of these scripts will change. Contact GE Vernova Support for assistance with identifying and correcting the impacted R Scripts. | US540206 |
Previously, if you configured a family policy for a relationship family that included a Cancel Transaction node, when the Cancel Transaction node was executed, the alert message was not displayed. This issue has been resolved. | DE188184 |
Previously, when you attempted to export family policies for custom relationship families from the Configuration Manager, an error occurred, and the export was not successful. This issue has been resolved. | DE183424 |
Previously, if your APM system used an Oracle schema, when you configured a Query node to run a query containing an Entity Key column, and mapped the Entity Key output from the Query node into the first input of a comparison node (for example, an Equal node), regardless of the type of value mapped to the second input of the comparison node, the error message, "Please specify fields with valid types for this condition" appeared in the notification bar and the policy could not be activated. This issue has been resolved. Now, the notification message appears only when the second input value mapped into the comparison node does not have a defined type. If you use a Constant node or Point Value node as the source for the second input value, you must configure the node as String, Numeric, or Decimal data type. | DE180113 |
Previously when you attempted to copy and paste a Case node, its predecessor node and the link between the nodes, the pasted Case node did not retain the configuration of the copied Case node. This issue has been resolved. | DE158704 |
Description | Tracking ID |
---|---|
If a Query node references a query with column aliases containing quotation marks, the policy model may not be upgraded correctly when your APM system is upgraded. You will need to modify and reactivate the policy. | DE195101 |
When you create a Policy Recommendation using the Create Entity node, the recommendation is not linked to the equipment record automatically, even though the Equipment ID is provided. | DE194635 |
When your APM system is upgraded, if the policy model contains multiple Sub Policy nodes that reference the same sub policy, the policy is not upgraded correctly and a warning appears in the Upgrade Log indicating that sub policy recursion was encountered. You will need to modify and reactivate the policy. | DE194299 |
When your APM system is upgraded, if an entity key in a Delete Entity, Create Relationship, or Delete Relationship node is defined in a Point Value node in an instance, you may need to modify and reactivate the policy instance and the policy. This is as-designed; however, the product documentation does not cover this upgrade step. | DE194296 |
Description | Tracking ID |
---|---|
The Content GUID output has been removed from all nodes in family policies. Note: When your APM system is upgraded, any existing family policies that use the Content GUID output from any nodes will be upgraded to use the Entity Key output, and the behavior of the family policy may change. For more information, refer to Upgrade or Update Policy Designer. |
|
Foundation
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve usability, the main navigation menu in the application has been enhanced. The new menu provides a clear hierarchical structure and it lists all the selectable modules within each category. In addition, with an improved visual styling, the screen width available for the application is also increased. You can access the new Applications Menu by selecting the button in the main navigation bar. You can now:
| F51334 |
General Dashboards
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, when you attempted to export Public\Workflows\Equipment Health Tracking Workflow\Dashboards\EHW Evaluate Health Baseline Dashboard, an error occurred. This issue has been resolved. | DE186518 |
Description | Tracking ID |
---|---|
The APM Foundation dashboard design has been modified. The Recommendations Created and Approved - 12 Months graph is no longer displayed. If you have previously modified this dashboard, this update will not be automatically applied. If your APM system uses an Oracle schema, an error may occur when you access the dashboard. Contact GE Vernova Support for assistance. | DE189442 |
Generation Availability Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
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. | US489817 |
To enhance usability in the GAA Unit page, the CEA reporting format has been improved when you enter a single digit for the Primary Unit Code instead of two digits. To facilitate this enhancement, the single digit entered in the Primary Unit Code is now prefixed with 0 and appears as two digits in the CEA Event Report. | US473682 |
Description | Tracking ID |
---|---|
Previously, if the time zone associated with your user account was different than the time zone of the plant, and you created an event, calculations in the performance record did not consider events in the following scenarios:
This issue has been resolved. Now, when you create an event, the event Start Date and End Date fields are automatically adjusted according to the time zone of the plant while creating a Performance record. | US474413 |
Previously, in the Breakdown of Period Hours section of the Unit Summary workspace, when you accessed the Planned Outage details for a GAA unit, the events associated with PE Event Type were not displayed even though the events were created for the GAA unit. This issue has been resolved. | DE143051 |
Description | Tracking ID |
---|---|
In the Unit Summary workspace, in the Performance & Reports workspace, the Performance for a Year button () is no longer available to generate Performance records for a year. However, you can generate Performance records using the Bulk Generation feature. | US453226 |
Generation Availability Analysis Wind
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve performance, the jobs in the Import Events Workspace and Report Generation Workspace are now automatically refreshed every 10 minutes. You can also manually refresh the data in these workspaces. To facilitate this enhancement, a new button, Refresh (), has been added to the workspace. You can either specify the interval at which the jobs must be refreshed automatically, or turn off the automatic refresh feature by selecting the appropriate option from the drop-down list box. | US546163 |
Hazards Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now retrieve the IPL Subtype values in the Hazards Analysis Safeguard record using the following catalog queries that are configurable:
| US555917 |
Description | Tracking ID |
---|---|
Previously, in Hazard Analysis, when you updated Cause and Consequence records, various fields in the linked LOPA were not updated. This issue has been resolved. Now, the LOPA record for the related fields syncs when you update a Cause or Consequence record. | US560135 |
Previously, when you attempted to update the CCPS Cause Type field in Hazard Analysis cause datasheet, the new value in the Linked LOPA was not updated in the related consequence. This issue has been resolved. | US553999 |
Previously, in the Hazard Analysis Datasheet, the Node IDs in the title and the left navigation panel appeared in an abbreviated form when the Node ID was longer than 24 characters. The title and left navigation panel did not display the complete ID when you mouse-over the abbreviated ID. This issue has been resolved. Now, the limit for abbreviating the Node ID in the title is increased from 24 to 90 characters. The Search issue is also fixed in the left navigation panel. | DE186962 |
Previously, while updating a Cause in a Hazards Analysis, if you cleared the value in the CCPS Cause Type field, an error occurred. This issue has been resolved. | DE186956 |
Previously, in Hazard Analysis team members section users you could only update one team member's role at a time. This issue has been resolved. | DE186955 |
Previously, when you copied nodes in the Hazards Analysis, custom fields were not copied. This issue has been resolved. | DE184532 |
Previously, if the datasheet for the Hazop Deviation/What-If, HazardsAnalysis Cause, Hazards Analysis Consequence, or Hazards Analysis Safeguard was open and you attempted to delete the record, the screen did not refresh and there was no message displayed after the operation. This issue has been resolved. | DE184026 |
Previously, in the Risk Assessment Recommendation datasheet, when you selected a functional location from the Asset Finder, the Functional Location ID field was not populated with the selected value. This issue has been resolved. | DE183773 |
Previously, in Has Reference Documents relationship family, when you attempted to add the relationship definition between safety related families and reference document, the Reference Document option was not available in the respective family datasheet. This issue has been resolved. | DE172444 |
Previously, when you logged in as a secured user and attempted to select an APM query from the catalog in the admin section, an error occurred. This issue has been resolved. | DE152664 |
Import and Export
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, when you exported the Family Rule Project for the Has Recommendations family rule, and then imported the same file, the import failed and an error message appeared. This issue has been resolved. | DE184891 |
Previously, as a German user, when you attempted to export a dataset containing decimal numbers, an error occurred. This issue has been resolved. | DE156429 |
Previously, if the status of a Security User account in APM was inactive, when you imported the user account details using an XML file that had the user account in active state, the status of the user account in APM was not changed. This issue has been resolved. | DE149054 |
Previously, when date functions were applied to date fields, the UTC time zone was applied by default instead of the user time zone. This issue has been resolved. Now, all date functions display the user time zone. | US533350 |
Description | Tracking ID |
---|---|
When you export a family from a previous version to V5, if any field in the family was changed to a Key field, the family is not imported and must be manually created in V5. Also, the State Management is not imported to V5. | US556701 |
When you attempt to create a Catalog folder with a leading or trailing space, and then import that folder, an error message appears indicating that the folder name cannot have leading or trailing spaces. To work around this issue, modify the folder path in the exported file and then import it:
| DE192736 |
Inspection Field Data Collection
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, in the Inspection Field Data Collection Overview page, when you attempted to delete a downloaded inspection that was already deleted on the server from a device, an error occurred, and the inspection was not deleted. This issue has been resolved. | DE173508 |
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, when you accessed an inspection for the family in the Inspection Field Data Collection page, the system code value did not appear in the drop-down list box. This issue has been resolved. | DE167899 |
Previously, when a field in an offline datasheet had a configured picklist behavior dependent on the value of another field, if an error occurred when syncing the offline inspection data, the list of valid values for that field no longer appeared in the datasheet. This issue has been resolved. | DE144870 |
Description | Tracking ID |
---|---|
You can no longer download an inspection for Inspection Field Data Collection from the Inspection Details page. You must use the My Inspection tab in the Inspection Field Data Collection Overview page. | US545003 |
Inspection Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve performance, the Inspection Management (IM) Assets and the Inspection Management (IM) Functional Location Data Loaders have been enhanced such that you can upload Inspection Recommendations even if there are a large number of users in the Author Name column. | US561867 |
To enhance usability, the MIExecutionService is now available in the APM server. It processes jobs in the Inspection Management, Integrity Mobile, Risk Based Inspection, and Thickness Monitoring module queues. The MIExecutionService uses a single shared ActiveMQ queue service across APM. | US554741 |
To improve usability, the following changes have been made in the Inspection Overview page:
| US546443 |
To improve usability, the MI Inspection Pre-Approver security role has been added that can be used to transition state for an Inspection if required. | US543837 |
To improve usability, the State Management functionality is now enabled for review and approval process for the Inspection families. This feature provides the following functionalities:
Note: To enable State Management for custom inspection families, refer to the KBA 000039742. | US543067 |
To enhance usability, the following queries have been modified to support State Management approval for Inspection events:
| US532505 |
To enhance the usability, the following Inspection Families Baseline datasheet have been redesigned:
| US528303 |
Work Management Interface functionality is enabled to support the notification creation in addition to the existing work order generation when the tasks are created in the application. Additionally, you can select EAM Object, User Status, and Type while creating the tasks. | US523941 |
To improve usability, the following changes have been made in the Inspection Management Overview Page:
| US523253 |
To improve usability, the following changes have been made in the Bulk Review Inspection page:
| US523245 |
To improve usability, you cannot delete an inspection task that appears in the Tasks Addressed drop-down list box of an Inspection record. | US438691 |
The Integrity Mobile app is now available for Android and iOS devices. You can download the app from Google Play Store or Apple App Store. Using this app, you can perform the following functionalities:
Note: The app is currently available only for Android tablets and iPad devices. A version that supports phone form-factors will be released soon.
In addition, the APM web client has been enhanced with the ability to revoke inspections that are downloaded from the app by a super-user or user with the Inspection Administrator Resource role. This can be done from the Inspection Management Overview within the Open Inspections section. | US551133 |
Description | Tracking ID |
---|---|
Previously, you could set null values in the Inspection Report Owner and Reviewers Name fields while creating inspection using dataloader. This issue has been resolved. The null values will not be set in both these fields while creating inspection using dataloader in the future releases. | US546458 |
Previously, when you attempted to search a task list from the Inspection or Calibration task, the functional location ID was not displayed correctly. This issue has been resolved. | DE184549 |
Previously, in the Inspection Management Overview dashboard, the records for an asset selected at the root level in the asset hierarchy were not displayed. This issue has been resolved. The following queries have been modified to resolve the issue:
| DE183947 |
Previously, you were able to update the Item ID field of the Inspection Profile family through the datasheet or data loader even when the Item ID field was auto populated by default with selected value for Item Category field. This issue has been resolved. Now, the Item ID field is disabled and removed from the baseline datasheet and data loader Excel template, so that you cannot update the field manually. | DE183234 |
Previously, if you had MI Inspection group privileges and attempted to delete an Inspection Task, an error occurred, indicating that you did not have the delete privilege on the Has Task Revision relationship family. This issue has been resolved. | DE181963 |
Previously, when you generated the Findings automatically from profiles during Inspection creation, if the length of the profile name exceeded 100 characters, an error occurred, and the Inspection was not created. This issue has been resolved. | DE181568 |
Previously, Inspection Profile Item field in General Finding Datasheet was not displayed in a formatted mode. This issue has been resolved. | DE181345 |
Previously, users with the MI Inspection group permissions added to their security roles were unable to create an Asset Technical Data. This issue has been resolved. | DE178133 |
Previously, when you accessed the Linked Tasks section under Inspection, the Inspection task hyperlink was not displayed. This issue has been resolved. | DE174597 |
Previously, when you deleted an inspection that had Inspection Health Evaluation records, the associated records were not deleted. This issue has been resolved. Now, all the records that include Inspection Health Evaluations and any Inspection Recommendations that are directly linked to those Inspection Health Evaluations are deleted. | DE166471 |
Previously, in the Inspection Overview workspace, when you attempted to create the Inspection Confidence Evaluation records and then switched to the Team Members section or created the Inspection Team Member records and switched to the Inspection Confidence Evaluation section without saving, the Unsaved Changes window appeared. When you attempted to save the changes, it failed, and the records were not displayed. This issue has been resolved. | DE163752 |
Previously, when viewing an Inspection Checklist, if you resized the split view of the checklist section to full-page, or from full-page to half-page, the columns within the data grids of the checklist categories were misaligned. This issue has been resolved. | DE153307 |
Previously, when you selected the Enable Inspection Grouping option in the RBI Admin Preferences page, the Inspection section in the Inspection Management Overview page, did not display the Inspection records associated with a Functional Location as an Asset. This issue has been resolved. | DE149644 |
Previously, when creating an Inspection Event record that has additional fields defined as required either through field behaviour or field level rules, and if the record is not new, an error occurred and the Inspection Event was not created. This issue has been resolved. | DE146250 |
Previously when you implemented Compliance Recommended Actions to existing Inspection Tasks in bulk, the data for the Recommended Inspection Task appeared only for the first Recommended Action. This issue has been resolved. Now, the Recommended Inspection Task data appears for each Recommended Action. | DE144641 |
Previously, in certain cases, when you modified a checklist inspection and checklist finding record, an error occurred when you attempted to save the record. This issue has been resolved. | DE144425 |
Description | Tracking ID | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
The Reports button () is no longer available in an Inspection. To print an NR13 Full Inspection Report, select the more options button () in the datasheet, and then select Print. Note: If you have not activated the NR13 license, we recommend that you remove the NR13 Full Inspection Report and the NR13 General Inspection Report from the Full Inspection and the General Inspection families respectively using Family Management. For instructions, refer to Remove the Reports Linked to a Family. | US528872 | |||||||||
You can no longer customize the code to generate a work order as the work order generation for the tasks created in APM moved into the product code. | US523941 | |||||||||
The following fields that were available in the General Finding family are no longer used in the application:
| US457583 | |||||||||
The following Inspection Management queries are no longer used in the application and have been removed: Folder: Public/Meridium/Modules/Inspection/Document Queries
Folder: Public/Meridium/Modules/Inspection/Work Pack Queries
Folder: Public/Meridium/Modules/Inspection/Task Queries
Folder: Public/Meridium/Modules/Inspection/Resources Queries
Folder: Public/Meridium/Modules/Inspection/Manage Report Queries
Folder: Public/Meridium/Modules/Inspection/Conditional Alert Queries
Folder: Public/Meridium/Modules/Inspection/Profile Queries
Folder: Public/Meridium/Modules/Inspection/Config Queries
| US445953 |
Integrity Mobile Application
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The Integrity Mobile app is now available for Android and iOS devices. You can download the app from Google Play Store or Apple App Store. Using this app, you can perform the following functionalities:
Note: The app is currently available only for Android tablets and iPad devices. A version that supports phone form-factors will be released soon. In addition, the GE Vernova web client has been enhanced with the ability to revoke inspections that are downloaded from the app by a super user or a user with the Inspection Administrator Resource role. This can be done from the Inspection Management Overview within the Open Inspections section. | US551133 |
Layers of Protection Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now link any protective instrumented loop in the Hazards Analysis Safeguard. To facilitate this enhancement, you can now select the protective instrumented loops from the linked instrumented function in the hazard analysis safeguard datasheet. | US555929 |
You can now copy a LOPA analysis. To facilitate this enhancement, the Copy icon () has been added in the Under Review and Approved tabs of the LOPA Overview page. This Copy option is also added in the LOPA summary page. | US523074 |
Description | Tracking ID |
---|---|
Previously, in Has Reference Documents relationship family, when you attempted to add the relationship definition between safety related families and reference document, the Reference Document option was not available in the respective family datasheet. This issue has been resolved. | DE172444 |
Previously, when you logged in as a secured user and attempted to select an APM query from the catalog in the admin section, an error occurred. This issue has been resolved. | DE152664 |
Previously, you could delete the Initiating Events in the LOPA Admin Preferences page in Application Settings, even though the Initiating Events were linked to a LOPA analysis. This issue has been resolved. Now, you can delete only those Initiating Events which are not linked to any LOPA analysis. | DE174777 |
Manage Translations
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve user experience, Translation Management module has been redesigned. The user interface has been updated to a grid view where you can:
| US552405 |
Description | Tracking ID |
---|---|
Previously, if your language setting was set to a language that had Cyrillic script, the system messages contained question marks instead of the actual text. This issue has been resolved. | DE145359 |
Management of Change
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, when you created a user in Security Manager with the MOC User role, and then attempted to access the Management of Change module as this new user, the MOC Overview page did not load. This issue has been resolved. | DE176302 |
Previously, in Has Reference Documents relationship family, when you attempted to add the relationship definition between safety related families and reference document, the Reference Document option was not available in the respective family datasheet. This issue has been resolved. | DE172444 |
Maps
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The Geographic Information System (GIS) Data Loader requirements have changed. Now, you must specify the Family ID of the record to which the GIS data must be linked, in addition to the Entity Key or Entity ID of the record. | US458351 |
Description | Tracking ID |
---|---|
Previously, when you navigated away from Maps page and then returned to the page, the map did not reload correctly. This issue has been resolved. Now, the Maps page refreshes automatically when you return to the page. You can select the Refresh button to retrieve data that has changed since the last reload. | DE173585 |
Metrics and Scorecards
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, in KPI details page, when you selected the Update Measures icon (), some of the measurements were duplicated and data values in the trend line chart displayed incorrectly. This issue has been resolved. | DE183137 |
Previously, in the Schedule, Alerts, and Privileges section, when you attempted to define alerts for KPIs and you selected the Add Recipients icon () the list of security users included both active and inactive users. This issue has been resolved. Now, only active users are displayed. | DE180188 |
Policy Designer
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
In order to simplify the module deployment, the existing query, Public\Meridium\Modules\Policy Manager\Queries\Time In Queue (SQL), has been modified to work on all database types and is renamed Public\Meridium\Modules\Policy Manager\Queries\Time In Queue. This query is used in the Time In Queue graph on the Policy Designer Overview and the Recent Policy Executions dashboard. As a result, the following items which are no longer required have been removed from the catalog:
Note: If you have previously modified any of the above mentioned catalog items, you have to copy the updated item from the baseline folders to the public folders and then, re-apply your changes. | US557648 |
The Policy Designer data model has been enhanced and the following queries have been modified:
If you previously modified any of these queries, you must copy the relevant query from the baseline folder to the public folder and reapply your modifications. | US551776 |
Policy Instance records are now linked to Policy records by the new Policy Has Policy Instance relationship family. To facilitate this change, the Policy Key field has been added in the Policy Instance family and the Policy GUID field has been removed. Note: Do not configure Family Policies or VB Rules to be triggered when the Policy Has Policy Instance records are deleted. | US551771 |
Policy Event records are now linked to Policy Instance records by the new Policy Instance Has Policy Event relationship family. To facilitate this change, the Policy Instance Key field has been added in the Policy Event family and the Policy Instance GUID field has been removed. Note: Do not configure Family Policies or VB Rules to be triggered when the Policy Has Policy Event records are deleted. | US551770 |
The Policies list on the Policy Designer Overview is updated to show any policies that have been inactivated during the upgrade. Note: Review the upgrade logs for any policy that has been inactivated and modify the policy as appropriate before re-activating it. For more information, refer to Upgrade or Update Policy Designer. Contact GE Vernova Support in case of any difficulty with policy modifications. | US542244 |
You can now view an updated Average and Max Wait Times graph in the Policy Overview page. To minimize configuration effort, the graph now displays queue times in seconds for all database types. | US528386 |
You must now specify the family ID or family key(s) for relationships that you want to delete in a policy. To facilitate this enhancement, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, and Successor Family Key(s) sections are added in the Delete Relationship node properties window of Policy Designer. Note: When your APM system is upgraded, policies containing the Delete Relationship node will be upgraded only where the entity keys and the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. | US520092 |
You can now review warnings and errors that occur during the post-upgrade processing of policy records in Policy Designer. To facilitate this enhancement, you can now select the Upgrade Logs tab in the module navigation menu and view or delete the log information for a policy that is upgraded from an earlier version. | US519063 |
You can now use a new Collection output from the Sub Policy node. To facilitate this enhancement, now, when you execute a policy containing a sub policy node that is not operating on a collection, the values returned from the sub policy are accessible in a collection output containing two columns, (Name and Value) in addition to the single-value outputs. | US511936 |
To enhance functionality, the Family Key is now included in the output of the following nodes:
| US481771 |
You must now specify the family ID or family Keys(s) for relationships that you want to create in a policy. To facilitate this enhancement, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, Successor Family Key(s) sections are added in the Create Relationship node properties window of Policy Designer. Note: When your APM system is upgraded, policies containing the Create Relationship node will be upgraded only where the entity keys and the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. | US454314 |
You must now specify the family for entities that you want to delete in a policy. To facilitate this enhancement, the Family Key(s) section is added in the Delete Entity node properties window of Policy Designer. Note: When your APM system is upgraded, policies containing the Delete Entity nodes will be upgraded only where the entity keys and the family of the entities to be deleted can be determined automatically. For more information, refer to Upgrade or Update Policy Designer. |
|
You can now configure the catalog path input of the Query node to accept the output from a predecessor node. To facilitate this enhancement, select the switch to field input button () under query path to choose an input from another node. Note: When the query path is sourced from a predecessor node, the results collection output from the query node can be used only when you do not need to select a specific column in the collection. | US414721 |
You can now set the time or number of occurrences by when a scheduled execution should end in a policy. To facilitate this enhancement, the End Repeat option is added to the Scheduled Execution section of the Details workspace in the Policy Designer page. | US402265 |
You can now configure the maxSubPolicyDepth. This setting limits the number of levels of sub policy calls and ensures that recursive policy executions cannot occur. The default maximum sub policy depth is set to 10. | US374957 |
Description | Tracking ID |
---|---|
Previously, if you defined an R Script to use an input parameter of type Matrix of Values - Numeric, Matrix of Values - Boolean, or Matrix of Values - Character, the matrix of values passed to the R server was transposed. This may have resulted in unexpected results from the R Script node. This issue has been resolved. Note: If you have existing R Scripts using Matrix input parameters, the behavior of these scripts will change. Contact GE Vernova Support for assistance with identifying and correcting the impacted R Scripts. | US540206 |
Previously, when you attempted to delete a policy instance with large number of execution history records, an error occurred. This issue has been resolved. | US459366 |
Previously, if your APM system used an Oracle schema, when you configured a Query node to run a query containing an Entity Key column, and mapped the Entity Key output from the Query node into the first input of a comparison node (for example, an Equal node), regardless of the type of value mapped to the second input of the comparison node, the error message, "Please specify fields with valid types for this condition" appeared in the notification bar and the policy could not be activated. This issue has been resolved. Now, the notification message appears only when the second input value mapped into the comparison node does not have a defined type. If you use a Constant node or Point Value node as the source for the second input value, you must configure the node as String, Numeric, or Decimal data type. | DE180113 |
Previously when you attempted to copy and paste a Case node, its predecessor node and the link between the nodes, the pasted Case node did not retain the configuration of the copied Case node. This issue has been resolved. | DE158704 |
Previously, when you executed a policy with two or more levels of sub-policies, and the second or lower level of sub-policies had an error, the execution status of the policy did not indicate that an error had occurred. This issue has been resolved. | DE143955 |
Description | Tracking ID |
---|---|
If a Query node references a query with column aliases containing quotation marks, the policy model may not be upgraded correctly when your APM system is upgraded. You will need to modify and reactivate the policy. | DE195101 |
If the policy execution service experiences a session time out, the policy execution is not retried. This may result in skipped policy executions. | DE194998 |
When you create a Policy Recommendation using the Create Entity node, the recommendation is not linked to the equipment record automatically, even though the Equipment ID is provided. | DE194635 |
When your APM system is upgraded, if the policy model contains multiple Sub Policy nodes that reference the same sub policy, the policy is not upgraded correctly and a warning appears in the Upgrade Log indicating that sub policy recursion was encountered. You will need to modify and reactivate the policy. | DE194299 |
When your APM system is upgraded, if an entity key in a Delete Entity, Create Relationship, or Delete Relationship node is defined in a Point Value node in an instance, you may need to modify and reactivate the policy instance and the policy. This is as-designed; however, the product documentation does not cover this upgrade step. | DE194296 |
If you set the culture and language of the policy execution service user to other than English (US), policy execution results and emails sent by the policy will appear in English (US) instead of the configured language and culture. | DE194065 |
Description | Tracking ID |
---|---|
The following catalog queries, which were used to determine the status of the scheduled policy trigger jobs, are no longer used and have been removed from the catalog:
The Public\Meridium\Modules\Policy Manager\Recent Policy Execution Results dashboard has been updated to remove widgets that reference the queries listed above. The Public\Meridium\Modules\Policy Manager\Recent Policy Execution Results (Oracle) dashboard has been removed. Note: If you have previously modified these queries or the dashboards, an error will occur when you access the content. You must copy the updated query,Baseline\Meridium\Modules\Policy Manager\Recent Policy Execution Results dashboard to the public folder and then reapply your modification. | US557590 |
The Modified From Baseline column is no longer displayed in the Module Workflow Policies section of the Policy Designer Overview page. Note: If you have previously modified the Public\Meridium\Modules\Policy Manager\Queries\Policy Overview - Module Workflow Policies Tile query, an error will occur when you access the Policy Designer Overview page. You must copy the updated query, Baseline\Meridium\Modules\Policy Manager\Queries\Policy Overview - Module Workflow Policies Tile, to the public folder and then reapply your modification. | US556297 |
The Content GUID output has been removed from all nodes in Policy Designer. Note: When your APM system is upgraded, any existing policies that use the Content GUID output from any nodes will be upgraded to use the Entity Key output, and the behavior of the policy may change. For more information, refer to Upgrade or Update Policy Designer. |
|
Production Loss Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now select multiple Production Events from the Module Overview Result Grid and delete the selected Events in bulk. To facilitate this enhancement, there are checkboxes added in the result grid. | US539439 |
To enhance usability, you can now delete multiple Production Plans and all associated Production and Loss data. To facilitate this enhancement, check boxes are added corresponding to the Production plans under the Production Plans section in the Production Loss Analysis page. | US539206 |
To enhance usability, the PLA Data Loader now supports custom fields for datasheets of all families except the Production Plan and Production Data families. | US532882 |
To improve usability, the PLA Data Loader now allows you to create custom fields in the three baseline data loader templates for the following families:
Note: Custom fields are not supported for Product and Production Plan families | US532870 |
To improve usability, if your culture setting has a culture other than English, the column headers in the Data Grid on the Production Data page are now translated to the language based on your culture setting. | US472217 |
You can now create copies of the existing Events in the Production Events workspace. | US311647 |
To improve usability, the definition and descriptions for the Event Codes that are provided in the baseline database for PLA are now included in the product documentation. | US530175 |
To enhance usability, you can now create Production Analyses based on any of the available production margins from a Production Profile for the associated production unit. To facilitate this enhancement, you can select a margin value from the Choose Margin drop-down list box in the Production Analysis Builder page. | US515583 |
Description | Tracking ID |
---|---|
Previously, when you attempted to update the Headline field value for a Production Event that contained a ~ (tilde) character, an error occurred, and the previous and updated Headline values were appended together. This issue has been resolved. | DE174230 |
Previously, when you accessed a Production Event Code, you were unable to select a child code in the production event code hierarchy. This issue has been resolved. | US543251 |
Previously, in the PLA Event Data Loader, you were required to use the baseline format of the ID Template for the Causing Asset field. This issue has been resolved. Now, the Entity ID field of the respective family is used. | US271623 |
Description | Tracking ID |
---|---|
When you enable the State Management functionality, the State ID column does not appear in the Production Event and Production Plan sections. | DE190908 |
Queries
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Since Oracle databases do not support date math by year ('yy') or month ('mm') with time stamps enabled, the DateAdd function for Oracle databases will now use 365.25 days for years and 30 days for months. | US563265 | ||||||||||||||||||||||
The following changes have been made to the Advanced section of the Expression Builder window:
| US457466 | ||||||||||||||||||||||
The following parameters are now supported for creating expression syntax for the MI DatePart and DATEPART functions:
| DE143708 |
Description | Tracking ID |
---|---|
Previously, when you deleted a query column that was included in the query clause, and then attempted to run and export the query results, an error occurred. This issue has been resolved. | DE184300 |
Previously, when you created a query with several parameters, which included single-value and multi-value parameters, the query sometimes did not return any data, and the graph using the query did not display any results. This issue has been resolved. | DE181800 |
Previously, when you used a hyperlink in a query to build links using multi-value parameters, the first two parameters were incorrectly encoded. Due to this, the parameter values were not passed as expected. This issue has been resolved. | DE180641 |
Previously, while creating a query, when you added a family, and selected the Fields filter button in the Design workspace, the filter options were always visible, even if you navigated back to the previous page. This issue has been resolved. | DE180619 |
Previously, when you attempted to select a query in the Asset Group page, if the query path contained any special characters, an error occurred. This issue has been resolved. | DE180782 |
Previously, if you attempted to run a crosstab query using a conditional alert, an error occurred. This issue has been resolved. | DE179635 |
Previously, if a column in your query result contained special characters, such as the equal sign (=), percent (%), or ampersand (&), and you ran the subquery associated with that column via a hyperlink, the subquery did not return any result. This issue has been resolved | DE177644 |
Previously, if you ran a query containing a union operator and a column having null values, and then applied a filter on the query results, an error occurred. This issue has been resolved. | DE154094 |
Previously, if the results of a crosstab query contained only one column, and you attempted to export the results, an error occurred. This issue has been resolved. | DE147190 |
Previously, when you attempted to run a query that contained a DATENAME function, an error occurred. This issue has been resolved. | DE145048 |
Previously, when you created a query that uses another query as its source, and if the source query had another query at the parent level, an error occurred in the following scenarios:
| DE108925 |
Previously, in the Results workspace, when you right clicked the column header and then selected the sort order to sort multiple columns in the query results, the sort order was not displayed. This issue has been resolved. | DE176433 |
Description | Tracking ID |
---|---|
When a value in your query result contains the ampersand (&) and equal (=) characters (for example, "A&B=C"), and you use that value as a parameter in a hyperlink, the hyperlink may not work as expected. | DE180641 |
Description | Tracking ID |
---|---|
In the Expression Builder window, the following redundant functions are no longer available to create query expressions:
| US457466 |
R Scripts
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
APM now supports Rserve (http://rforge.net/Rserve/), used with an open-source R Server distribution, for execution of R Scripts in Policy Designer and Family Policies, in addition to the previously supported R server options. | US529924 |
Record Manager
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The process for storing files associated with a Reference Document record in the APM database is changed. Reference Document files are now stored in the MI_REF_DOCUMENTS_BINARY system table. The MI_REF_DOCUMENTS_DOC_B field in the Reference Document family is no longer used. Now, to retrieve binary data in a query, you must join with the new system table. When your APM system is upgraded, existing document files will be moved to the new system table during the database upgrade. You must update any non-baseline queries that retrieve reference document binary data. For more information on how to query binary data, refer to the KBA 000040031. | DE543293 |
To enhance readability, you can now format the text in text fields. To facilitate this enhancement, a toolbar for formatting appears next to each text field for which rich text formatting is enabled. | F64567 |
To enhance performance and usability, you can now perform the following tasks in the Bulk Data Form, which displays related records in a Master/Detail datasheet:
|
F51961 US525665 |
To enhance the configurability of APM, when using the !datasheet-dialog URL, you can now specify the window title and hide the Edit button in the window. | US550781 |
You can now enter the localized values for a field group heading in a custom datasheet or the column headings in a tabular datasheet. To facilitate this enhancement, the <> icon has been included in the datasheet builder. | US515836 |
The following enhancements have been made to the Record Manager URLs and the Datasheet Dialog action route.
|
US456821 US540957 |
To enhance the usability of Record Manager, the width of the Record Explorer pane has been increased. To facilitate this enhancement, the width of the pane is now responsive to the width of the browser window. | US443206 |
You can now specify the datasheet to use in the URL to open records in the Bulk Data Form. | US437595 |
To improve usability, you can now add the following file formats as reference documents to a record from the Add Reference Document window:
| US526646 |
To improve security, you are no longer able to specify the APM Server in the UNC Path when configuring shared Reference Document folders. | DE178037 |
Description | Tracking ID |
---|---|
Previously, in the Document Path field, you could not specify the network path for a folder. This issue has been resolved. | US460298 |
Previously, if you selected a master detail datasheet for a record in a family using a state machine and attempted to change the state of the record, incorrect values were displayed in the datasheet and you could not save the record. This issue has been resolved. | DE192787 |
Previously, when you opened a record in Record Manager and hovered over the application tab, the tooltip displayed the record ID in truncated format. This issue has been resolved. | DE176906 |
Previously, when you attempted to link multiple reference documents to the same entity in a single transaction, relationships were not created for some of the selected documents. This issue has been resolved. | DE163821 |
Previously, when you attempted to update a record with an external hyperlink in the TEXT field or saved the record with an external hyperlink, an error occurred, and the datasheet did not load. This issue has been resolved. | DE155394 |
Previously, in a record containing a drop-down list box, if you selected a value in the drop-down list box, and then attempted to save the record, an error occurred. This issue has been resolved. | DE146300 |
Previously, when you tried to view the data copied from the datasheet through the result grid, the multiple spaces between the words were reduced to a single white space. This issue has been resolved. | DE144840 |
Previously, in a shared network, if you selected a hyperlink that was referenced to a document to be downloaded using Google Chrome or the Microsoft Edge browser, the file was downloaded with an invalid name and extension. This issue has been resolved. | DE141659 |
Previously, if the browser zoom level was set to less than 80%, the rows in the Bulk Data Form were misaligned. This issue has been resolved. | DE122725 |
Previously, the Email Subject Line field did not appear in the Conditional Alert datasheet layout. This issue has been resolved. | US528252 |
Description | Tracking ID |
---|---|
When you print the Bulk Data Form, only the columns that are visible on the screen are printed, instead of the entire form. | DE192562 |
Description | Tracking ID |
---|---|
The Send Query Link check box on the Conditional Alert datasheet is redundant and has been removed. Now, the Send Web Query Link check box is selected by default and can be cleared if required. | DE183846 |
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 link the analysis to one or more assets or functional locations for the Spares Analysis section. To facilitate this enhancement, the Linked Assets tab has been added in the Analysis Summary workspace. | US540477 |
Description | Tracking ID |
---|---|
Previously, in a System Reliability Analysis, when you specified values for a New TTF Distribution and saved them, the Beta and Eta values would default to zero and not reflect the values from the new distribution. This issue has been resolved. | DE186012 |
Previously, in a Reliability Distribution Analysis, when you adjusted the X-axis range, the setting was not retained between the plot tabs. This issue has been resolved. | DE183604 |
Previously, the Probability Distribution workflow in the documentation was incorrect. This issue has been resolved. | DE182309 |
Previously, in Automation Rules, when you attempted to merge two or more analyses, the values in the Number of Assets column were incorrectly displayed as the sum of number of assets and number of failures. This issue has been resolved. | DE176522 |
Previously, in System Reliability Analysis, when a planned resource was linked to a risk, if the same risk was then linked to an unplanned resource, the resource would be removed from the planned resource list and could not be added back. This issue has been resolved. Now, the planned resource is not removed from the correct resource list. | DE162457 |
Previously, in a Reliability Distribution for a Probability plot, the x and y coordinates continued to be displayed and were updated even for the Show data view of the chart component. This issue has been resolved. | DE153062 |
Previously, in System Reliability Analysis, the value on the Resource Time graph was incorrect if the resource time was being rounded to three decimal places. This issue has been resolved. | DE146552 |
Previously, if you did not have delete permission and when you attempted to delete a Reliability Analysis, an error occurred. This issue has been resolved. Now, in this scenario, a message appears indicating that you do not have delete permission. | DE138241 |
Previously, in System Reliability, the Monte Carlo Simulation included the detection of failures even when the PF interval value was set to zero which slowed down the performance. This issue has been resolved. | DE126740 |
Reliability Centered Maintenance
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve the usability, export of multiple Reliability Centered Maintenance Analyses will use background job infrastructure from the Reliability Centered Maintenance Overview page. | US513337 |
To improve the usability, when you select the job status component in RCM, the job error details now appear in a separate window on the same page. | US447209 |
Description | Tracking ID |
---|---|
Previously, when you exported an RCM analysis, the Asset information was not available in the Failure Effects, Recommendations, and Secondary Actions pages. This issue has been resolved. | US549693 |
Previously, if you added a recommendation to a failure effect in RCM or FMEA, duplicate recommendation IDs were created. This issue has been resolved. | DE185427 |
Previously, when you attempted to link an asset to an analysis, the Asset field in the Enter Parameter Values window displayed Home by default. This issue has been resolved. Now, it displays the asset hierarchy value. | DE184381 |
Previously, if you linked a failure mode to an asset and subsequently linked it to a different asset, when the RCM recommendations were promoted to ASM, the asset strategy was updated only for the first asset. This issue has been resolved. | DE182351 |
Previously, the Asset ID of a consolidated recommendation was incorrect. This issue has been resolved. | DE181288 |
Previously, when you changed a Risk Matrix that was associated with the site to a different Risk Matrix, you were still able to update the assessment using the old Risk Matrix. This issue has been resolved. | DE179424 |
Previously, as a non-English language user, you were unable to view the Template Type column in the RCM Overview page. This issue has been resolved. | DE174354 |
Previously, when loading data though dataloader, financial details were not getting updated as per the dataloader worksheet. This issue has been resolved. | DE152522 |
Previously, when you accessed APM using a Chrome browser, there was a performance issue while saving records through the datasheet. This issue has been resolved. | DE149743 |
Previously, if your culture setting was set to a culture other than Invariant Language, when you attempted to export RCM analyses from the RCM Overview page, an error occurred. This issue has been resolved. | DE147986 |
Previously, if you are not an administrator, when creating a failure effect, the risk assessment record was not copied from ACA. This issue has been resolved. | DE143493 |
Reports
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, if Bulk Reports were not configured in Report Configuration, the reports were not generated, and the SSRS report viewer returned an error. This issue has been resolved. | DE183908 |
Description | Tracking ID |
---|---|
The scheduled job for Bulk Reports (SSRS) is causing a deadlock when the job is triggered under high load conditions. This is leading to the JobExecution Service becoming non-responsive. ActiveMQ unsubscribes all non-responsive consumers and this causes all jobs handled by the JobExecution Service to stop processing. This results in all jobs handled by the JobExecution Service (SSRS bulk report, Export & Import, Strategy Macros, and KPI update jobs) being in queued state and not proccessed. To reset this state you can restart the JobExecution Service to clear the deadlock, and the queues will then continue to process. | DE195077 |
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 |
---|---|
To enhance usability, the MIExecutionService is now available in the APM server. It processes jobs in the Inspection Management, Integrity Mobile, Risk Based Inspection, and Thickness Monitoring module queues. The MIExecutionService uses a single shared ActiveMQ queue service across APM. | US554741 |
To improve usability, you can now view the Inspection Task datasheet in a Datasheet window instead of a new tab, when you select the Task ID hyperlink in the existing tasks section of the Inspection Plan page. | US547779 |
To enhance usability, the Suggest Potential Degradation Mechanisms (PDMs) feature has been introduced. This feature provides the following functionalities:
To facilitate this enhancement, select the Enable Suggestion of Potential Degradation Mechanism option in the RBI Admin Preferences workspace. For more information on modifying the policy, refer to KBA 000039240. | US519095 |
To improve usability, you can now view the Asset info summary in the RBI Asset View page. To facilitate this enhancement, a new button for Asset info summary has been added next to the Asset ID in the RBI Asset View page. You can now get a high-level view of the health of an asset which consist of the following information:
| US518766 |
Risk Based Inspection pages have been enhanced to improve usability:
|
|
When creating an RBI Component from the Asset Summary or Unit Summary workspace, the Component Types in the Component Type drop-down list are now populated based on the Component Family selected in the Create New RBI Component window. To facilitate this enhancement, a new system code table, MI RBI COMPONENT FAMILIES, has been added to the System Codes and Tables page. The system code table contains the Component Families and the supported Component Types associated with the MI RBI COMPONENT TYPES system code table. Note: For more information on the baseline Component Families and the Component Types that are supported for each Component Family, refer to the topic. | US446310 |
To improve usability, the following changes have been made to the Component:<name> workspace:
| US446303 |
To improve usability, the Potential Degradation Mechanisms tab has been removed from the Corrosion Loop: <name> workspace. You can now select the Corrosion Loop Details tab, and then expand the POTENTIAL DEGRADATION MECHANISMS sub-section to view the list of Potential Degradation Mechanisms (PDMs) that are linked to a Corrosion Loop. | US443994 |
To improve usability, the following changes have been made to the left pane tree navigation for RBI Asset and RBI Process Unit:
| US443991 |
To enhance usability, a new inspection planning methodology, Alternative Inspection Plan, has been introduced. Using this feature, you can perform the following functionalities:
To facilitate this enhancement, enable the Alternative Inspection Plan option from the application settings. Note: This is an optional functionality. The Alternative Inspection Plan does not support the following workflows:
| US528269 |
Description | Tracking ID | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Previously, the Desired Interval Basis field on Inspection Tasks implemented from Risk Based Inspection was set to RBI Recommendation or RBI 581 Recommendation. This issue has been resolved. Now, the Desired Interval Basis field on Inspection Tasks implemented from Risk Based Inspection is set to RBI 580 or RBI 581 respectively. The Desired Interval Basis field on Inspection Tasks implemented from manually created Inspection Plan Details is set as User Designed. | US537338 | ||||||||||||||||||||||||||||||
Previously, when searching for Potential Degradation Mechanisms from the Component Overview section or the Corrosion Loop Overview section, previously selected Potential Degradation Mechanisms were not retained. This issue has been resolved. | US439611 | ||||||||||||||||||||||||||||||
Previously, when you accessed an RBI Component, the analysis table in the Component Overview section sometimes failed to load, resulting in a blank screen. You had to refresh the browser to view the related analyses. This issue has been resolved. | DE189291 | ||||||||||||||||||||||||||||||
Previously, when you attempted to delete an RBI Analysis, there was no indication that the delete process had started, and you selected the Delete icon multiple times, resulting in an error. This issue has been resolved. Now, a busy cursor is displayed when you select Delete on an RBI Analysis. | DE183466 | ||||||||||||||||||||||||||||||
Previously, when you attempted to link the protected components to a Pressure Relief Device component on a Corrosion Loop, components which were not eligible to be linked were displayed in the list. This issue has been resolved. | DE154170 | ||||||||||||||||||||||||||||||
Previously, when the RBI Evergreening Preference was set to RBI 581, hyperlinks for the Asset ID, Component, and Analysis ID columns in the Pending Evergreening tab of the RBI Bulk Evergreening workspace were not displayed. This issue has been resolved. | DE152646 | ||||||||||||||||||||||||||||||
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. | DE141412 | ||||||||||||||||||||||||||||||
Previously, the field captions of the following family fields contained extra spaces, special characters, or spelling mistakes. This issue has been resolved. Now, the field captions have been corrected to the captions listed in the following table.
| DE101745 |
RBI 580
Description | Tracking ID | ||||
---|---|---|---|---|---|
You can now update What-If RBI Criticality Analyses using the RBI 580 Data Loader. To facilitate this enhancement, the RBI 580 Data Loader template is updated to include the Event Type column on the RBI Criticality Analysis worksheet and all Consequence Evaluation, Degradation Mechanism Evaluation, and Damage Mechanism worksheets. When the Event Type is set to W, the system updates the analysis with the matching Analysis Unique Identifier. Note: If the What-If Analysis does not exist, an error appears, indicating that the What-If Analysis cannot be created using data loaders. | US554368 | ||||
When calculating an RBI PRD Criticality Analysis and the leakage rate for minor and moderate leaks, the calculations are now based on API 581, third edition. | US513966 | ||||
You can now correctly reference the RBI Component and Equipment of an RBI Criticality Analysis and its related RBI Degradation Mechanisms that are related to from their respective datasheets after applying or copying the analysis. To facilitate this enhancement, the following fields have been updated to match the Component and Equipment you are applying or copying to.
| US453121 | ||||
You can now select and link a Protected RBI Component to a PRD component from the navigation pane in RBI Asset workspace. To facilitate this enhancement, the button has been added to the navigation pane in the RBI Asset workspace. | US453094 | ||||
You can now export RBI Criticality Analyses to an excel format from either of the below workspaces:
The exported file will be in the Risk Based Inspection (RBI) Data Loader template format. This will provide 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. | US450061 | ||||
You can now select the field displaying the Inspection Priority and Risk Category data in the page heading to view the Risk Matrix. To facilitate this enhancement, the Risk Matrix section has been removed from the Asset Summary workspace for RBI Criticality Analyses. |
US530725 US443989 |
Description | Tracking ID | ||||||||
---|---|---|---|---|---|---|---|---|---|
Previously, the following fields in the RBI Criticality Analysis family displayed the Unit of Measure (UOM) incorrectly as Pounds Force per Square Inch Absolute (PSIA):
This Issue has been resolved. Now, the UOM value is displayed as Pounds/Sq Inch Gage. Note: You must enter the value in the Analysis for Tube Press - Channel field with unit of measurement as PSIG. | DE179745 | ||||||||
Previously, if you cleared the Toxic Mixture Shell check box on the Criticality Consequence Evaluation of an RBI Criticality Analysis, the values in the Toxic Fluid Shell Side and Percent Toxic Shell boxes did not get cleared as expected. This issue has been resolved. Now, the existing values in the Toxic Fluid Shell Side and Percent Toxic Shell boxes get cleared and the boxes are also disabled. | DE175499 | ||||||||
Previously, when re-implementing an Inspection Group on a Process Unit, the previous Inspection Group’s recommendations were not archived if the related Inspection Plan was in the modified state. This issue has been resolved. Now, when re-implementing a new Inspection Group, the previous Inspection Group’s recommendations will be archived, and only the newly created Inspection Group Recommendations will be linked to the modified inspection plan. | DE156821 | ||||||||
Previously, in the RBI Criticality Analysis, the Allowable Stress field was populated based on the Material Specification and Material Grade fields in the Tank Stress table. This issue has been resolved. Now, the Design Code and Code Year fields are also considered for populating the Allowable Stress field. | DE156070 | ||||||||
Previously, when you attempted to execute the RBI 580 Dataloader, if the value provided in the fields on the Analysis, Consequence Evaluation, or Degradation Mechanism Evaluation sheets were null, the field value was updated as null. This issue has been resolved. Now, if the value provided for the fields are null, the field is skipped and the default value or any mapped value is displayed. | DE154518 | ||||||||
Previously, when duplicating an RBI PRD Criticality Analysis, when at least one related Degradation Mechanism was not selected, an error occurred, and the RBI RBI PRD Criticality Analysis was not copied. This issue has been resolved. | DE145892 | ||||||||
Previously, if the PV Stress or Piping Stress reference tables contained multiple records with the same combination of Design Code, Code Year, Material Specification, Material Grade and Metal Temperature, the Allowable stress field in RBI Criticality Analysis was populated arbitrarily with one of the records returned. This issue has been resolved. Now, the record with the lowest Allowable stress value from the records returned is used to populate the Allowable Stress field. | DE145435 | ||||||||
Previously when you implemented RBI 580 Recommended Actions to existing Inspection Tasks in bulk, the data for the Recommended Inspection Task appeared only for the first Recommended Action. This issue has been resolved. Now, the Recommended Inspection Task data appears for each Recommended Action. | DE144641 | ||||||||
Previously, when calculating an RBI Criticality Analysis, the toxic evaporation rate was calculated using an incorrect wind speed factor. This issue has been resolved. Now, the toxic evaporation rate is calculated correctly, and will be used in populating the Toxic Mixed Release Rate field and in the RBI Criticality Analysis calculation. | DE120477 | ||||||||
Previously, if the Design Temperature value was less than the minimum value of Metal Temperature in the Piping Stress or PV Stress table records, the Allowable Stress field in RBI Criticality Analysis was calculated incorrectly. This issue has been resolved. Now, if the Design Temperature value is less than the minimum value of Metal Temperature, then the Allowable Stress field is calculated based on the minimum value of Metal Temperature. | DE84703 |
Description | Tracking ID | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following catalog queries are no longer used and have been removed from APM.
| US461310 |
RBI 581
Description | Tracking ID | ||||||
---|---|---|---|---|---|---|---|
You can now update What-If RBI 581 Risk Analyses using the RBI 581 Data Loader. To facilitate this enhancement, the RBI 581 Data Loader template is updated to include the Event Type column on the RBI 581 Analysis worksheet and all Consequence Evaluation, Degradation Mechanism Evaluation, and Damage Mechanism worksheets. When the Event Type is set to W, the system updates the analysis with the matching Analysis Unique Identifier. Note: If the What-If Analysis does not exist, an error appears, indicating that the What-If Analysis cannot be created using data loaders. | US554368 | ||||||
To improve usability, the following changes have been made in the RBI 581 ISO Risk Plot page:
| US533000 | ||||||
You can now view the risk calculated on the Target Inspection Date. To facilitate this enhancement, the following changes have been made:
| US528300 | ||||||
To improve usability, RBI Analysts, can now manage Inventory Groups. To facilitate this enhancement, the Inventory Groups workspace has been moved from the RBI Admin Preferences page to the Risk Based Inspection workspace. It is accessible from the RBI Component workspace and also from the Risk Based Inspection Overview workspace. | US518223 | ||||||
You can now export RBI Criticality Analyses to an excel format from either of the below workspaces:
The exported file will be in the Risk Based Inspection (RBI) 580 Data Loader template format. This will provide 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. | US450061 | ||||||
The Final Damage Factor for RBI 581 External Cracking Damage Evaluations now adheres to API 581 3rd Edition, Addendum 1. The Final Damage Factor will now have a maximum value of 5000. | US470511 | ||||||
You can now correctly reference the RBI Component and Equipment of an RBI 581 Risk Analysis and its related RBI Degradation Mechanisms that are related to from their respective datasheets after applying or copying the analysis. To facilitate this enhancement, the following fields have been updated to match the Component and Equipment you are applying or copying to.
| US453121 | ||||||
You can now select the field displaying the Total SHE Risk – RBI Date, SHE Risk Category – RBI Date, and Total Financial Risk – RBI Date data in the page heading to view the RBI 581 ISO Risk Plot and the default Risk Matrix. To facilitate this enhancement, the Risk Matrix section has been removed from the Asset Summary workspace for RBI 581 Risk Analyses. |
US530725 US443989 | ||||||
The Final Damage Factor for RBI 581 Cracking Damage Evaluations now adheres to API 581 3rd Edition, Addendum 1. The Final Damage Factor will now have a maximum value of 5000. | US439316 | ||||||
The Coefficient Y Material field in the RBI 581 Risk Analysis is now localized. To facilitate this enhancement, the RBI 581 Coefficient Y Materials List system code table will be used to populate the values for the Coefficient Y Material field in the RBI 581 Risk Analysis. | US351000 |
Description | Tracking ID |
---|---|
Previously, the Deg Mech Comments field was disabled in Degradation Mechanism Details page when the RBI 581 Risk Analysis was set to Created state. Now, you are allowed to enter the comments in the Deg Mech Comments field until the RBI 581 Risk Analysis is set to Complete state. This issue has been resolved. | DE192230 |
Previously, when the Operating Temperature field of an RBI 581 External Damage Evaluation was greater than 90 degrees Fahrenheit, the Calculated Corrosion Rate field was not set to the most conservative value from Table 15.2 (Corrosion Rates for Calculation of the DF-External Corrosion) of the RBI 581 Specification. This issue has been resolved. | DE190649 |
Previously, when you attempted to calculate an RBI 581 Risk Analysis with a Representative Fluid that satisfied the following conditions, an error occurred:
| DE189199 |
Previously, the susceptibility calculations for the 581-Chloride Stress Corrosion Cracking degradation mechanism evaluation were not updated as per API 581 Specification, Third Edition. This issue has been resolved. To facilitate this fix, the RBI 581 Calculate Susceptibility - CISCC policy has been updated. For information, refer to KBA 000039983. | DE188760 |
Previously, when the Operating Temperature field of an RBI 581 Risk Analysis was set to a value 100, 200 or greater than 300 degrees Fahrenheit, the Cracking Susceptibility field was calculated incorrectly on the 581-Chloride Stress Corrosion Cracking degradation mechanism evaluations. This issue has been resolved. | DE188760 |
Previously, when calculating an RBI 581 Risk Analysis with a 581-Atmospheric Tank Bottom Corrosion degradation mechanism evaluation where the Highest Effective Inspection Level field is set to Highly Effective, the Recommended Inspection Effectiveness field on the related Damage Mechanism was not set. This resulted in no recommendations being generated. This issue has been resolved. Now, the system will attempt mitigation on 581-Atmospheric Tank Bottom Corrosion degradation mechanism evaluations regardless of the highest effective inspection level. | DE187364 |
Previously, when you created an RBI 581 Admin option from the RBI 581 Admin Options workspace and switched between tabs, the newly created option did not appear on the page. This issue has been resolved. | DE183593 |
Previously, when calculating a Thinning and Lining Damage Mechanism Evaluation where the Cladding field was set to true in the parent RBI 581 Risk Analysis, the Expected Metal Loss Fraction (Art) field was calculated using the incorrect cladding corrosion rate based on the Selected Base Material Corrosion Rate field. This issue has been resolved. Now, the Expected Metal Loss Fraction (Art) field is calculated using the cladding corrosion rate based on the Selected Cladding Material Corrosion Rate field. | DE181240 |
Previously, when you calculated an RBI 581 Risk Analysis with a related 581-Internal Component Lining Damage degradation mechanism, the damage factor was set to Zero if the age was less than 0.5. This issue has been resolved. Now, if the age is less than 0.5, the Damage Factor is populated based on the updated content in the following tables:
| DE179908 |
Previously, as a multiple site user, when you created an RBI 581 Inventory group, the site was set based on the user’s default site instead of the Process Units site. This issue has been resolved. Now, a newly created RBI 581 Inventory Groups site is set based on the Process Units site. | DE179048 |
Previously, in the RBI 581 Admin Options workspace under the RBI Admin Preferences page, the Character Field Value drop-down list was not populated for some of the Target Family and Target Field combinations. This issue has been resolved. | DE178900 |
Previously, when you navigated to the Inventory Groups workspace from the Unit Summary workspace, the Create New Group button () was not enabled for the Process Unit. This issue has been resolved. | DE176641 |
Previously, when you logged in with the MI RBI Viewer permissions, the Link () icon was displayed in the Linked Components section of the Inventory Group workspace. This issue has been resolved. | DE175357 |
Previously, when calculating an RBI 581 Risk Analysis with a toxic mixture, if one of the following values was selected in the Toxic Model field, the Weighted Toxic Consequence Area field on the related RBI 581 Consequence Evaluation was calculated incorrectly using release mass:
This issue has been resolved. Now, in this scenario, the Weighted Toxic Consequence Area field considers the release rate. For more information access the KBA 000037566. | DE155372 |
Previously, when you attempted to execute the RBI 581 Dataloader, if the value provided in the fields on the Analysis, Consequence Evaluation, or Degradation Mechanism Evaluation sheets were null, the field value was updated as null. This issue has been resolved. Now, if the value provided for the fields are null, the field is skipped and the default value or any mapped value is displayed. | DE154518 |
Previously, when calculating an RBI 581 Risk Analysis that had the Component Type set to Storage Tank and a related RBI 581 Thinning Degradation Mechanism Evaluation or RBI 581 External Degradation Mechanism Evaluation, the Strength Ratio field was calculated incorrectly. This issue has been resolved. | DE152192 |
Previously, if an RBI 581 Risk Analysis was linked to an RBI Component with the component type set to Air Cooled Exchanger Tubes, the recommendations were erroneously generated. This issue has been resolved. To facilitate this fix, the below two baseline queries are updated:
| DE152190 |
Previously, the Calculated T-min field on 581 Risk Analyses was calculated incorrectly when Geometry Type field value was Piping. This issue has been resolved. Now, the Calculated T-min field on 581 Risk Analyses is calculated using the formula from the reference, ASME B31.3, 2014 Edition. For more information about the formula, refer to KBA 000036403. | DE151334 |
Previously, when calculating an RBI 581 Risk Analysis, the Final Damage Factor field for the RBI 581 Thinning and Lining Evaluation family was incorrectly calculated in the following scenarios:
| DE150440 |
Previously, the Calculated T-min field on 581 Risk Analyses was calculated incorrectly when Geometry Type field value was Spherical Head or Hemispherical Head. This issue has been resolved. Now, the Calculated T-min field on 581 Risk Analyses is calculated using the updated formula. For more information about the formula, refer to KBA 000037009. | DE149068 |
Previously, when duplicating an RBI 581 Risk Analysis, when at least one related Degradation Mechanism was not selected, an error occurred, and the RBI 581 Risk Analysis was not copied. This issue has been resolved. | DE145892 |
Previously, if the PV Stress or Piping Stress reference tables contained multiple records with the same combination of Design Code, Code Year, Material Specification, Material Grade and Metal Temperature, the Allowable stress and Flow stress fields in 581 Risk Analysis were populated arbitrarily with one of the records returned for each field. This issue has been resolved. Now, the record with the lowest Allowable stress value from the records returned is used to populate the Allowable Stress and Flow stress fields. | DE145435 |
Previously, in the picklist tab of RBI 581 data loader template, the following process fluids were not available:
This issue has been resolved. | DE145420 |
Previously when you implemented RBI 581 Recommended Actions to existing Inspection Tasks in bulk, the data for the Recommended Inspection Task appeared only for the first Recommended Action. This issue has been resolved. Now, the Recommended Inspection Task data appears for each Recommended Action. | DE144641 |
Previously, if the Design Temperature value was less than the minimum value of Metal Temperature in the Piping Stress or PV Stress table records, the Allowable Stress and Flow Stress fields in 581 Risk Analysis were calculated incorrectly. This issue has been resolved. Now, if the Design Temperature value is less than the minimum value of Metal Temperature, then the Allowable Stress and Flow Stress fields are calculated based on the minimum value of Metal Temperature. | DE84703 |
Previously, when creating an RBI 581 Risk Analysis, the Measured External Corrosion Rate field in the RBI Component family was not mapped to the Base Material Measured Rate field in the related RBI 581 External Damage Evaluation family. This issue has been resolved. | DE83359 |
Previously, when you calculated an RBI 581 Risk Analysis with Component Type set to Storage Tank Bottom, the Base Damage Factor on RBI 581 Thinning and Lining Datasheet was not retrieving the most conservative value from Thinning Damage Factors of the AST Bottom table in the API 581 Specification. This issue has been resolved. For more information, refer to KBA 000038729. | DE83086 |
Risk Matrix
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, you can now change the label of the protection level slider in a Risk Matrix. To facilitate this enhancement, a new System Code Table named Protection Level Label has been added. | US514864 |
Description | Tracking ID |
---|---|
Previously, the Risk Rank was not displayed even when the Hide Numeric Risk Rank? checkbox in the Risk Matrix was not selected. This issue has been resolved. | DE183690 |
Root Cause Analysis
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, the text fields for 5 Whys Analysis are now expanded across the complete width of the page. | US552064 |
To increase usability, in the RCA Definition datasheet, the filed name Frequency is renamed Number of Related Failures. | US541077 |
To enhance usability, while creating an RCA Verification, you can now assign the verification to any team member, instead of only the Principal Analyst. | US501284 |
The Configure System Email section has been removed from the Email Settings workspace in the RCA Administrator page. You will now receive root cause analysis alert notifications from the email address that is configured in the Email Settings page in Operations Manager. | US459248 |
Description | Tracking ID |
---|---|
Previously, when you published an RCA Analysis and enabled the option to send an email, and if any of the email recipient was incorrect, then the publishing failed with an incorrect error message. This issue has been resolved. Now, in this scenario, a warning message appears indicating that you must validate the email recipients. | US536521 |
Previously, in the Preserve Records section, the fields appeared in English and not in the language based on your language settings. This issue has been resolved. | US463186 |
Previously, for all categories of Root Cause Analyses in the RCA Overview page, the Analysis Type column contained an incorrect spelling. This issue has been resolved. | DE189077 |
Previously, when you created an RCA using a template that was loaded through the RCA Data Loader, you were unable to edit the analysis. This issue has been resolved. | DE186407 |
Previously, when you attempted to access the Logic Tree in an RCA Analysis and while the page was still loading, you attempted to switch to the Event Timeline, an error occurred. This issue has been resolved. | DE181425 |
Previously, the RCA Analysis verification email did not contain any reference to the source analysis. This issue has been resolved. | DE175885 |
Previously, in the RCA Recommendations, when you attempted to assign a target completion date that was in the past, an incorrect message appeared. This issue has been resolved. Now, you receive a message indicating that the target date must be set as a future date. | DE170361 |
Previously, when you created a copy of an RCA Analysis, the copied analysis did not display the secondary events in the Event Timeline. This issue has been resolved. | DE164706 |
Previously, in the design canvas of the RCA Event Diagram, you were unable to drop icons from the Palette section to the top left corner of the start node. This issue has been resolved. Now, the available workspace to add nodes has been extended to include the far corners of the design canvas. | DE162460 |
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. | DE155403 |
Previously, in an RCA Event Timeline that has multiple events, when you modified a primary event and attempted to save it, an incorrect message was displayed. This issue has been resolved. | DE153555 |
Previously, if State Management was enabled for a Root Cause Analysis and the analysis was in any state except Not Started, when you attempted to save the analysis as a template, an error message appeared. This issue has been resolved. | DE145612 |
Previously, when you deleted an RCA Hypothesis from RCA Logic Tree, the child verifications were not deleted in the database record and appeared in Record Explorer when you did a global search. This issue has been resolved. | DE143298 |
Previously, when you added an event to the RCA Event Timeline, and then attempted to add another event, the datasheet for the event added previously was loaded instead of a blank Event Datasheet. This issue has been resolved. | DE143055 |
Previously, when you selected the notification checkbox for an RCA Verification Record, the notification was sent to the first Team Member instead of the current assigned user. This issue has been resolved. | DE131253 |
Rounds Data Collection
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, you were not able to log in or change user accounts within APM without clearing the application cache on a shared work surface. This issue has been resolved. | DE176004 |
Previously, when you selected the Reference Documents section and attempted to open the associated reference document, you were unable to download documents that were added from a UNC path. This issue has been resolved. | DE175078 |
Previously, in Rounds Data Collection and the GE Digital APM Mobile Application, the Additional Instructions section for the Measurement Location did not wrap text or allow scrolling to show all information, and you were not able to view text that exceeded the width of the screen. This issue has been resolved. | DE132407 |
Description | Tracking ID |
---|---|
When you load Readings data into APM through Rounds Readings Data Loader, you will encounter a DataValidationError if the MI_READING0_RELAT_ML_ENTIT_KEY_N is not supplied. For additional information and workaround, review the https://digitalsupport.ge.com/communities/CC_Login?startURL=%2Fcommunities%2Fen_US%2FArticle%2FLoading-the-Data-Through-Rounds-Readings-Data-Loader-Results-in-DataValidationError. | DE194630 |
Rounds Designer
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, in the Routes section, when you completed all the readings on the Measurement Locations, the subsequent conditional Measurement Locations were not triggered. This issue has been resolved. | DE181629 |
Previously, some queries that supported data loaders were not functioning as expected. This issue has been resolved. The specific queries have now been updated to improve performance for the supported data loaders. | DE157060 |
Product documentation is now updated to define more clearly when a route is due and when it is overdue. | DE153348 |
Previously, when you added a checkpoint using a checkpoint template, the Equipment Technical Number did not appear when you accessed the checkpoint record. This issue has been resolved. | DE149996 |
Previously, in the Recommendations section of the RDC Overview page, the Node Pin Board icon overlapped the Recommendations icon. This issue has been resolved. | DE136885 |
Previously, when you entered a long category name in the Allowable Values section, the application did not display a warning message and the name was also not added to the Allowable Values list. However, the application allowed you to create an allowable value with a blank category name. This issue has been resolved. Now, you can add a maximum of 50 characters in the category name and if you do not enter a category name, a notification message will be displayed when you attempt to save the table. | DE136915 |
Previously, when you attempted to create a Template Group and did not enter an ID in the ID text box, the application did not indicate that the ID is a required field, and you could create the Template Group. This issue has been resolved. | DE136916 |
Rounds Pro
- Rounds Pro is currently not available for APM V5.0.0.0.0. The module will be available in subsequent APM V5.x releases.
- The Rounds Pro mobile app currently does not support APM V5.0.0.0.0.
Rules
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
A new parameter for family key (fmly_key) is now added to the ExistingEntity(enty_key) function. Note: You must update the custom rules containing the ExistingEntity(enty_key) function with the new parameter ExistingEntity(enty_key, fmly_key). | US465532 |
The datatype for ENTY_KEY variable is now changed to string. Note: You must update the datatype of all the variables that refer to ENTY_KEY and are assigned the value of ENTY_KEY to the string datatype. | US465532 |
Description | Tracking ID |
---|---|
Previously, if the application server was not installed in the C: drive, and you attempted to open the Rules Library rule project, an error occurred, and you were unable to edit the rules. This issue has been resolved. | DE177742 |
Description | Tracking ID |
---|---|
When you upgrade APM from any older version to 45000, it takes notably longer since there are significant changes made to the database during the upgrade. | US465532 |
Description | Tracking ID |
---|---|
The MI_ENTITIES table is no longer available in the database. You can now access the system fields from the family table. Note: You must update all the queries and Visual Basic rules that refer to MI_ENTITIES to allow the system fields to be pulled from the family table. | US465532 |
SAP Adapters
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Previously, in the SAP Interface, when a Long Text and FLOC Label with a large count was extracted, if the ARC folder was not specified, some data was not processed into APM. This issue has been resolved. | DE184932 |
Previously, when using an alternate unit of measure for the numerical values in the Technical Characteristics section, the conversions to the base unit of measure was incorrect. This issue has been resolved. | DE147449 |
Previously, the SAP Deployment authorization chart was not complete for use for WMI interface. This issue has been resolved. | DE140397 |
Search
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, you can now update the search index for a specific family. To facilitate this enhancement, you can now select the Reindex Family button in the Search Configuration page. | US518022 |
You can now find a link to the advanced search in the global search window. From there you can search selected Family and the Linked To information through the advanced search. | US186116 |
Security Manager
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now configure State Management using the following newly introduced user roles:
| US541632 |
Security of cookies has been improved with advanced attributes in APM. | DE142479 |
Description | Tracking ID |
---|---|
Previously, a user associated with MI Foundation Admin role could not view or open Policy Designer. This issue has been resolved. | DE178355 |
Previously, if you removed multiple Security Users from a Microsoft Active Directory Group, and then ran the LDAP synchronization process, the Security Users were not dissociated from the corresponding Security Role in APM. This issue has been resolved. | DE143330 |
Previously, in the User Defaults page, when you attempted to assign a Russian site to Security Users, an error occurred. This issue has been resolved. | DE142239 |
SIS Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
The Work Management Interface functionality is now enabled to support notification creation in addition to work order generation when tasks are created in the application. Additionally, you can select EAM Object, User Status, and Type while creating tasks. | US523942 |
In an SIL Analysis, you can now copy a Risk Assessment Recommendation to multiple Instrumented Functions. To facilitate this enhancement, the Copy icon() has been added in the Recommendations pane of SIL Analysis. | US518255 |
You can now unlink one or more Proof Test Tasks from an Instrumented Function or a Logic Solver. To facilitate this enhancement, the Unlink the selected Tasks button () has been added to the Proof Test Tasks section of the Instrumented Function and Logic Solver workspaces. | DE153712 |
Description | Tracking ID |
---|---|
Previously, the SIS Management Overview page took a long time to load due to the complexity of the SIL_Analysis_Asset_Overview and SIL_Distribution_for_Graph queries. This issue has been resolved. | US564147 |
Previously, if a Protective Instrument Loop contained more than one device in an identical Sensor or Final Element Group, and if you updated a device, the Device ID was changed in the remaining devices in the group as well. This issue has been resolved. | DE191397 |
Previously, in the SIL Verification section, when you selected multiple Protective Instrument Loops and attempted to delete the loops, the application did not respond as expected. This issue has been resolved. | DE190830 |
Previously, when you navigated between multiple SIL Analyses, and attempted to create an Instrumented Function, the application stopped responding and you had to refresh the page to continue. This issue has been resolved. | DE189891 |
Previously, the Proof Test workflow did not function as expected when only the Functional Location was selected at the Instrumented Function level. This issue has been resolved. | DE188701 |
Previously, the Protective Instrument Loop Sensor System records were not included in the search results. This issue is now resolved. | DE186408 |
Previously, in SIL Analysis, the Team Members section did not load when you selected the Team Members tab after navigating from the Definition tab. This issue has been resolved. | DE178101 |
Previously, in the Proof Test Tasks section, when you selected Perform Proof Test for a task, the Task ID field was not populated automatically. This issue has been resolved. | DE177405 |
Previously, when you performed a proof test, if the Trip point was defined as negative value in the Proof Test Template Detail, the result was calculated as Fail. This issue has been resolved. | DE172467 |
Previously, in Has Reference Documents relationship family, when you attempted to add the relationship definition between safety related families and reference document, the Reference Document option was not available in the respective family datasheet. This issue has been resolved. | DE172444 |
Previously, when you tried to link a Sensor, Final Element, Sensor Group, Final Element Group, Sensor System, Final Element System, or a Logic Solver in a Protective Instrument Loop, an error occurred. Also, the success or failure message did not appear after the operation. This issue has been resolved. | DE154988 |
Previously, when you added an existing proof test task to a record, an error occurred and the task list in the Proof Test Tasks section was not refreshed. This issue has been resolved. | DE153707 |
Previously, when you selected a device or calculated a Protective Instrument Loop, if there was a device configuration error, no error message was displayed. This issue has been resolved. Note: A warning message now appears in the Loop Diagram and Calculation page or when you select an incompatible device. | DE153164 |
Previously, when you logged in as a secured user and attempted to select an APM query from the catalog in the admin section, an error occurred. This issue has been resolved. | DE152664 |
Previously, when importing an .exp file, if a custom device was present in the Protective Instrument Loop, an error occurred in the calculation of the loop. This issue has been resolved. | DE152634 |
Previously, when you created Revision Record for an SIL Analysis, the Revision Record was not created for few Instrumented Functions that were linked to the SIL Analysis. This issue has been resolved. | DE150911 |
Previously, if the Hazards Analysis license was not active in APM, when you attempted to add a team member to the team associated with a Safety Integrity Level (SIL) Analysis, an error occurred. This issue has been resolved. | DE145949 |
Previously, when same asset was linked to more than one predecessor record using the Safety Analysis has Equipment relationship, the template field was not populated while performing proof test. This issue has been resolved. | DE162253 |
Previously, in the Risk Assessment Recommendation datasheet, when you selected a functional location from the Asset Finder, the Functional Location ID field was not populated with the selected value. This issue has been resolved. | DE183773 |
Description | Tracking ID |
---|---|
When you attempt to import a recently created Exida project file with the .exp extension into APM, an error occurs and the import fails. | DE195336 |
When you attempt to copy a LOPA and Hazards Analysis license is not active, an error occurs and copy functionality fails. | DE192842 |
When you attempt to copy a LOPA, the original LOPA site doesn’t get copied to the copied LOPA. | DE192841 |
Description | Tracking ID |
---|---|
You can no longer customize the code to generate a work order because the work order generation for tasks created in APM has been moved into the product code. | US523942 |
APM no longer supports the exSILentia v3 calculation engine for calculating loop results for SIL analyses. You can only use the exSILentia v4 calculation engine for calculating loop results for SIL analyses. | US459479 |
Single Sign On
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now configure SSO without providing the host name. To facilitate this enhancement, the Host Names in Operations Manager page has been replaced by SSO Configuration. | US538282 |
Description | Tracking ID |
---|---|
SSO login fails on an iOS mobile app for an SSO-enabled on-prem application. Recent security enhancements made in iOS blocks cookies that are used for authentication, resulting in login failure. The LDAP user has the option to login to APM mobile app without SSO, by entering username and LDAP password on the login page and clicking the Sign-in button. After signing out of the app, the user will have to re-enter the credentials to sign-in again. | DE194611 |
State Management
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
You can now query the State fields at the level of the State Management configuration of the family as the State management fields are no longer spread down a family hierarchy. | US567083 |
Description | Tracking ID |
---|---|
Previously, if you modified the time zone settings, and then viewed the state history of a record in the History tab, the time stamp was not updated. This issue has been resolved. | DE139798 |
Description | Tracking ID |
---|---|
The State Management field, mi_sm_states.smst_stat_ind, in the MI_SM_STATES table is no longer used. Therefore, when you upgrade, ensure that you remove any references to the State Management field in queries. | US567083 |
Strategy Macros
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, when scheduling conditional alerts in the Strategy Macros page, you can now schedule multiple Active Alerts at a time. | US447592 |
Teams
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To improve usability, the following functionalities have been added in the Teams page:
| US528506 |
Thickness Monitoring
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
To enhance usability, the MIExecutionService is now available in the APM server. It processes jobs in the Inspection Management, Integrity Mobile, Risk Based Inspection, and Thickness Monitoring module queues. The MIExecutionService uses a single shared ActiveMQ queue service across APM. | US554741 |
To enhance usability and improve contextual awareness, Schematic View (2D Visualization) has been introduced within Thickness Monitoring. This capability will allow you to:
You will be able to render industrial drawing formats (.svg, .dwg, .jpeg, .pdf, and so on) to plot TMLs. An active Mechanical Integrity 2D Visualization license will be required to access this functionality. | US539882 |
To improve usability when sending TMLs to the Olympus 38DL Plus Ultrasonic Thickness Gage datalogger device, the following enhancements have been made:
| US526329 |
To enhance usability, the T-Min Calculator now works in accordance with the Override Minimum Thickness Type field on the Thickness Measurement Location. If the Override Minimum Thickness Type field is already set, the Minimum Thickness on the Thickness Measurement Location is not updated from the T-Min Calculator screen. A warning message lists the TMLs that are not updated. | US522002 |
To enhance usability, in the Measurement Data Entry workspace, the width of the TML ID column is now automatically adjusted based on the length of the TML ID. To facilitate this enhancement, the following changes have been made:
| US518505 |
To enhance usability, when inserting or updating Thickness Measurements, you can now have APM automatically correct the measurement based on growth. If the measurement value indicates a growth over a previous measurement, the system will automatically update its value with the value of the previous measurement. The originally entered value will be retained in the Uncorrected Measurement field. To support this functionality the following enhancements have been made:
| US514853 |
To enhance usability, Thickness Monitoring is configured to use the TML Group family as the only way to group thickness measurement locations. To facilitate this enhancement, the Family Preferences workspace in the TM Admin Preferences page has been redesigned. You can now select the TML Asset ID for each family using the drop-down list boxes under the TML Asset ID Field column. | US445607 |
Description | Tracking ID |
---|---|
Previously, the catalog queries that populated the Corrosion Rate Distribution and Remaining Life charts on the Thickness Monitoring Overview had poor performance in large databases. This issue has been resolved. Now, the Corrosion Rate Distribution query has criteria limiting to assets with corrosion rates greater than or equal to 10 Mils/Year and the remaining life query has criteria limiting to assets with remaining life of less than or equal to 5 Years. | US457578 |
Previously, in the T-Min Calculator workspace, when you modified the User Defined field, the T-Min Selected field was not updated. This issue has been resolved. | DE191127 |
Previously, users with MI Thickness Monitoring User security group permissions were unable to create a Piping Band. This issue has been resolved. | DE181965 |
Previously, when multiple Thickness Measurement Location (TML) records had a Measurement Not Taken (MNT) record as the last active measurement, and the TMLs Controlling Corrosion Rate was less than the assets Controlling Corrosion Rate, the following fields were populated and displayed as expected in the Analysis Output section:
Note: It is recommended that you use the TM Bulk Analysis feature to recalculate assets that have MNT records as the last measurement on any TMLs. For more information on how to identify these assets, refer to the KBA 000037654. | DE181172 |
Previously, in TM Dataloggers page, when you attempted to search for TMLs in the Select TMLs pane, that were already displayed, the search did not return the correct values. This issue has been resolved. | DE179521 |
Previously, when you attempted to view Thickness Monitoring Locations (TMLs) in the Datalogger page, or if you attempted to send TMLs to the Datalogger, the inactive TMLs were not excluded by APM. This issue has been resolved. | DE175250 |
Previously, in the Thickness Monitoring Datalogger page, when you sent the Thickness Measurement Locations to the 38DL+ device, the TML IDs were formatted incorrectly if:
Note: To resolve this issue, you must install the latest Meridium Devices Service. | DE174874 |
Previously, when you navigated to the T-Min Calculator workspace for an asset that had been enabled for Piping Rotation, an error message appeared when you attempted to load the TMLs. This issue has been resolved. | DE172811 |
Previously, if you were assigned the Metric UOM Conversion Set, when entering values in a Thickness Measurement Location record to determine Allowable Stress that had the Tank Type field set to Welded Shell, the Minimum Yield Strength and Minimum Tensile Strength fields were incorrectly populated with Imperial values. However, the value of the Allowable Stress field appeared correctly. This issue has been resolved. | DE156721 |
Previously, if the PV Stress or Piping Stress reference tables contained multiple records with the same combination of Design Code, Code Year, Material Specification, Material Grade, and Metal Temperature, the Allowable Stress field of the Thickness Measurement Location was populated arbitrarily with one of the records that was returned. This issue has been resolved. Now, the record with the lowest value of Allowable Stress will be used to populate the Allowable Stress field. | DE155129 |
Previously, when flipping or rotating a Piping Component, if a calculated measurement value created for a TML was negative, even if the operation of flipping or rotating the component failed, the operation was in progress in the APM database due to which APM stopped responding. This issue has been resolved. | DE153950 |
Previously, if you were assigned to the Thickness Monitoring Inspector security group and granted additional delete privileges, you could not delete a TML. This issue has been resolved. Note: If you do not have delete privileges, when you attempt to delete a TML, an error message will appear. | DE149731 |
Previously, when using Column Chooser from the Measurements section of the Analysis Overview workspace, you could add a field to the Display Fields section multiple times. Due to this, the data in the Measurement Table did not load. This issue has been resolved. | DE147750 |
Previously, when you logged in to APM as a metric user and accessed the TML Trends graph, the values for Alert Level 1 and Alert Level 2 were incorrectly plotted based on their imperial equivalents. This issue has been resolved. | DE146040 |
Previously, when you attempted to send data to the Olympus 38DL Plus Ultrasonic Thickness Gage datalogger device multiple times, an out of memory error message appeared, and the data was not sent to the device. This issue has been resolved. Note: To implement the update, you must install the latest version of the Meridium Device Service. | DE144901 |
Previously, for an Asset that contained multiple TML Groups linked to it, when the Corrosion Analysis Settings for the Asset were spread to the TML Group level, an error occurred when you attempted to modify the settings for the Asset. This issue has been resolved. | DE144873 |
Previously, a secured user who was not assigned to any of the Thickness Monitoring security groups - MI Thickness Monitoring Inspector, MI Thickness Monitoring User, or MI Thickness Monitoring Administrator was able to view the Create Settings button for an asset with no related Corrosion Analysis Setting. This issue has been resolved. | DE142333 |
Previously, in the Measurement Data Entry workspace, when you saved the data for Thickness Measurement, and attempted to navigate to the next page, the data was not saved successfully. This issue has been resolved. | DE172724 |
Previously, in the Bulk Edit TMLs window, if you selected a single TML, the Design Code column was too narrow to display the values completely. This issue has been resolved. | DE117841 |
Description | Tracking ID |
---|---|
The query, Measurements Near or Less than T-Min, is no longer used in APM. The query has been removed from the Catalog folder Public/Meridium/Modules/Thickness Monitoring/Queries. | US445954 |
Workflow Solutions
This topic provides a list of product changes released for this module in this version.
Description | Tracking ID |
---|---|
Workflow Solutions Content has been updated in the latest version of APM. | US562494 |