V4.3.0.6.0 Release Notes

The following release notes are available for GE Digital APM V4.3.0.6.0. You can access release notes for previous versions at https://www.meridium.com/secure/documentation/WebHelp/ReleaseNotes.htm.

Help System

Release Date: September 21, 2018

Table 1. Enhancements and New Features
NoteTracking ID(s)
The APM Classic help system has been updated with a new look and feel. This updated help system offers a streamlined presentation of the content and provides the following features:
  • You can access the help content from the APM Classic Help home page that is organized in functional groups for each module and feature.
  • You can now access all content related to a module or feature (for example, end user help, deployment steps, configuration options, and so on) in one place.
  • When you access the help content for a module or feature, content is presented in a scrolling page view that allows you to view more content with fewer clicks.
  • A dynamic navigation menu, On this page, appears in the page if you prefer to navigate to a specific section of the page.
F24081
To enhance presentation and readability, now, when you select the Application Help button (), the help documentation appears in a new browser tab.US279764

Action Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 2. Enhancements and New Features
NoteTracking ID(s)
The Assigned To column in the Recommended Actions section of the Action Management page has been changed to the State Assignee column. Previously, the values in the Assigned To column were populated by the Assigned To Name field of the associated Recommendation record. The State Assignee column, however, is populated with the name of the Security User who is currently assigned to the state of the Recommendation record.US265464
To facilitate navigation from the Asset Hierarchy, a link to the Action Management module has been added to the Strategy section of the <Asset Name> page. In the Action Management row, there is a context-sensitive count of available and Recommended Actions for the selected asset. Selecting this link will navigate you to the section of the Action Management page.US265462
To enhance usability:
  • The implementation of Actions has been improved.
  • A visual indicator has been added to track the job progress.
  • The limit of the number of implementable Actions has been removed.
US265430
A new query, EAM Action Mapping, has been added to the Catalog folder \\Public\Meridium\Modules\Asset Strategy\Queries. This query returns a list of fields from the Action family that are used in the Implement as EAM Work Request and EAM Maintenance Plan features. Using this query, you can control the mappings between Action data and the EAM Notifications via the Implement as EAM Work Request and EAM Maintenance Plan features. Using Action Mappings, you can send Action information to your EAM system as a singular work request or a recurring maintenance plan.US265137
Table 3. Resolved Issues
NoteTracking ID(s)
Previously, in the Recommended Actions page, if you modified input parameters for the Recommended Action Filter query, an error occurred. This issue has been resolved. You can now modify input parameters as expected.DE80753
Previously, when transitioning a Recommendation record to a different state assignment from the Recommended Actions pane, if that Recommendation record did not have an assignee, an error occurred. This issue has been resolved.DE79683
Previously, when viewing Recommendation records in the expanded Recommended Actions pane, you were unable to sort those records in the columns by date value. This issue has been resolved. The sort function now works as expected.DE79682
Previously, if you unlinked a Recommendation record that contained child Recommendation records that were in the Superseded state, when those child records were unlinked, they reverted to the Proposed state. This issue occurred because Recommendation records that were previously in the Consolidated state were not properly excluded from the Recommended Actions section. This issue has been resolved.DE78126

APM Connect

This topic contains a list of product changes released for this module.

Release Date: Sept. 21, 2018

Table 4. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
APM Connect now supports connecting multiple source systems to GE Digital APM for Equipment, Functional Location, Notification Management, and Taxonomy adapters.TFS358792
APM Connect now supports Windows Server 2016.US271643
APM Connect now supports using a .zip file that contains .csv files as input to the data loaders.US264960
Table 5. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, the topic Import the Karaf File into the APM Connect Administration Center contained an incorrect file name. This issue has been resolved. The file name has been corrected to RunDataLoaderRoute.kar.TFS348507
Previously, when using the Work Management Adapter to create a Task record, the Last Date field was set to 1970-01-01 00:00:00. This issue has been resolved. Now, the date is correctly set to a null value for the first time the Task record is created.DE85222

APM Mobile Application

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 6. Enhancements and New Features
NoteTracking ID
The GE Digital APM mobile application now focuses on modules with offline workflows. To facilitate this enhancement, only the following modules are now available in the mobile application:
  • Inspection Field Data Collection and Inspection Management
  • Mobile Proof Testing
  • Rounds Data Collection
  • SIS Management

Additionally, now, if you attempt to access a module other than one of these four, a link appears, directing you to the selected module in a browser tab.

Note: Inspection Management is only available online.
US262477

Asset Criticality Analysis

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 7. Enhancements and New Features
NoteTracking ID(s)
To enhance usability, a new family, Criticality, has been added to Asset Criticality Analysis (ACA). Criticality records store assessment data to allow future expanded criticality options and assessment features.US274050
To aid in importing data via the Asset Criticality Analysis (ACA) Data Loader, sample data has been added to the Asset Criticality Analysis (ACA) data loader workbook.US265465
The Asset Criticality Analysis (ACA) Data Loader has been enhanced to improve the performance of error logging.US265351
Table 8. Resolved Issues
NoteTracking ID(s)
Previously, in the Asset Finder page, the maximum number of pieces of Equipment that you could access was 25. This issue has been resolved. Now, in the Asset Finder page, you can access all pieces of Equipment.DE85515
Previously, when using the Export to a File feature in ACA, the following issues occurred:
  • Risk Rank column exported
  • Risk Rank column IDs were inconsistent
  • Risk N/A field did not export as a logical field
These issues have been resolved. Now, the Export to a File feature mirrors the features of the ACA Data Loader.
DE83052
Previously, when viewing the Analyses section of the ACA Overview page, the ENTY_KEY column erroneously appeared. This issue has been resolved.DE82414
Previously, in the ACA Overview page, if you attempted to simultaneously delete multiple analyses, an error occurred. This issue has been resolved. Now, you can only delete one analysis at a time from the ACA Overview page.DE82413
Table 9. Obsolete Features
NoteTracking ID(s)
The following fields have been deprecated from the Asset Criticality Analysis and Asset Criticality Analysis System families:
  • Site ID
  • Unit ID
DE81006

Asset Health Manager

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 10. Resolved Issues
NoteTracking ID(s)
Previously, in the Asset Health Manager Overview page, if you pointed to the elements of a bar chart, the percentages displayed were not correct. This issue has been resolved.DE81533
Previously, the table in the Health Indicator Source Management workspace did not display all the rows. This issue has been resolved. To facilitate this fix, the pagination feature has been introduced in the workspace.DE79356

Asset Hierarchy

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 11. Enhancements and New Features
NoteTracking ID(s)
The appearance of the Asset Hierarchy has been modified to improve its presentation and performance. The organization and content of the Asset Hierarchy is unchanged.US278711
You can now delete Asset Groups. Before you can delete an Asset Group, you must unlink the Asset Group from all analyses to which it is linked. If you attempt to delete an Asset Group that is linked to one or more analyses, a message displaying the names of the linked analyses appears. US255539
Table 12. Deferred Features
NoteTracking ID(s)
Implement pagination in the interface for Asset Groups to resolve an issue where Assets Groups containing very large numbers of assets cause poor performance and can cause the interface to become unresponsive. US258544

Asset Strategy Implementation

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 13. Enhancements and New Features
NoteTracking ID(s)
To enable customization, in the Asset Strategy Implementation Admin page, in the Asset Strategy Implementation Preferences workspace, the following new preferences have been added to enable custom function modules in SAP:
  • Maintenance Plan Detail Function Module
  • Maintenance Item Detail Function Module
  • Task List Detail Function Module
  • Notification Detail Function Module
US281980
You can now import a General Task List from the root of the WMI tree in the ASI Package page. Previously, you could only import a General Task List from the context of an existing maintenance item.US272853
To enhance usability, in the Asset Strategy Builder window, you now can view all fields simultaneously.US272370
When using the Import Task List from SAP feature, ASI now employs the Task List Function Module defined in the Asset Strategy Implementation Preferences workspace. Additionally, when importing a Task List from custom SAP Function Modules, ASI now uses the Task List WMI Definition Configuration Mappings that are defined in the Work Management Item Definitions workspace of the Asset Strategy Implementation Admin page. US270035
>You can now link a single task list in SAP to multiple maintenance items from the ASI Package page by selecting the Add button (), and then selecting Task List from SAP.US270009
The following properties and methods in the Work Management Item Definitions section of the Asset Strategy Implementation Admin page have been restored to ASI:
  • AllowDelete

  • AllowModification
  • Delete

Now, when executing ASI code, GE Digital APM will consider these properties and methods.
US269408
To enhance usability, in the Action Revision family, the Required Packaging field has been deprecated. US267783
Table 14. Resolved Issues
NoteTracking ID(s)
Previously, in the Asset Strategy Implementation (ASI) page, when you initiated service requests via an Associated Page link, no progress bar appeared. This issue has been resolved.DE84753
Previously, updates to Maintenance Plan records in SAP failed because SAP incorrectly notified ASI of the successful creation of Maintenance Plan records. This issue has been resolved. Now, SAP correctly returns the status of the creation request.DE79688
Previously, when transitioning a pending Recommendation record to a different state assignment from the Recommended Actions pane, if that Recommendation record did not have an assignee, an error occurred. This issue has been resolved.DE79683
Previously, when using the Import from SAP feature, if your culture setting was defined as anything other than English, values in the Status and Info columns were not properly localized in the Import Status page or the Import Results page. These issues have been resolved.DE79661
Previously, if you added a new Maintenance Item to a Maintenance Plan in ASI, the Maintenance Item did not inherit the Plan Category value from the Maintenance Plan. Additionally, updating the Plan Category value for the Maintenance Plan did not spread the value to its child Maintenance Items. These issues have been resolved.DE78124

Asset Strategy Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 15. Enhancements and New Features
NoteTracking ID(s)
Two new queries, Calibration Task Link Existing Query and Inspection Task Link Existing Query, have been added to the Catalog folder \\Public\Meridium\Modules\Asset Strategy\Queries. The Calibration Task Link Existing Query is used by the ASM Implement Actions section to locate existing Calibration Tasks for implementation. The Inspection Task Link Existing Query is used by the ASM Implement Actions section to locate existing Inspection Tasks for implementation. US271774
To enhance usability, when viewing the Risk Analysis section of the Strategy Details page, when you make any proposed strategy changes that alter the mitigated risk or proposed cost in the Actions pane, a specified label and calculated value will appear in the Risk Profile chart and Cost Projection chart in the Risk Analysis page.US267536

To aid in importing data via an Asset Strategy Management (ASM) Data Loader, sample data has been added to the following data loader workbooks:

  • Asset Strategy Management (ASM) Data Loader

  • Asset Strategy Management (ASM) Templates Data Loader

US265465
A new query, EAM Action Mapping, has been added to the Catalog folder \\Public\Meridium\Modules\Asset Strategy\Queries. This query returns a list of fields from the Action family that are used in the Implement as EAM Work Request and EAM Maintenance Plan features. Using this query, you can control the mappings between Action data and the EAM Notifications via the Implement as EAM Work Request and EAM Maintenance Plan features. Using Action Mappings, you can send Action information to your EAM system as a singular work request or a recurring maintenance plan.US265137
Table 16. Resolved Issues
NoteTracking ID(s)
Previously, if you accessed the Add Existing Strategies window via the Manage Strategy section of the Asset Details page, the Add button was enabled prior to selecting a record. This issue has been resolved. Now, the Add button is only enabled if you have selected a record.DE82601
Previously, in the Strategy Details page, when accessing an Active Strategy, if you modified a value and then saved the Active Strategy, the message that appeared indicated that a new record was successfully saved even though a new record was not created. This issue has been resolved. Now, when you modify a value, the message that appears correctly indicates that the existing record has been modified and saved successfully.DE82600
Previously, in the Strategy Details page, when you attempted to delete a System Strategy, the message in the Confirm Delete window referenced an Asset Strategy record instead of a System Strategy record. This issue has been resolved.DE82599

Previously, in the Review Strategy workspace of the Strategy Details page, if you transitioned an Asset Strategy to the Active state, the value in the Has Changes column was not properly updated. This issue has been resolved. To facilitate this fix, the following changes have been implemented:

  • The Has Changes relationship has been deprecated.
  • The State column has been added to the Review Strategies workspace.
  • The Unit Review will now display only the collection of underlying Asset Strategies, not System Strategies.

DE82598
Previously, in the Strategy Details page, after applying a template as either a copy or the master, if you copied a risk or action, the Template Application job status indicator disappeared from the heading of the page. This issue has been resolved. The Template Application job status will now remain visible as expected. DE82596
Previously, while using an Asset Strategy Data Loader, if a value in the Risk Category column contained a space, when the data was imported, an error occurred. This issue has been resolved. You can now import risk categories that have spaces in their names as expected. DE81127
Previously, if you created a new System or Unit Strategy, then navigated to the Review Strategy section of the Strategy Summary page, and then selected Assignment in the Review Strategy section, an error occurred. This issue has been resolved. DE79378
Previously, if you implemented an EAM Work request from the Implement Actions section of the Strategy Details page and then attempted to access the Recommended Actions pane, the EAM Work Request that you implemented did not appear in the Recommended Actions pane. Additionally, if you deleted a General Recommendation record from the Recommended Actions pane that was expanded from the Implement Actions section, the deleted record still appeared in the Implement Actions section. These issues have been resolved. Now, if you implement an EAM Work Request from the Implement Actions section or if you add or delete Recommended Actions, the Recommended Actions pane refreshes and displays your changes.DE79377
Previously, while implementing Actions as an EAM Maintenance Plan, if you included a comma in the Action data, the .csv file exported incorrectly to Microsoft Excel. This issue has been resolved. Now, if you include a comma in the Action data, the .csv file exports correctly to Microsoft Excel.US283131

Asset Strategy Optimization

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 17. Resolved Issues
NoteTracking ID(s)
Previously, in the Elements section of the Analysis Summary workspace, the labels of some column headings related to Risk Categories were truncated. This issue has been resolved. DE85363

Calibration Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 18. Enhancements and New Features
NoteTracking ID(s)
To enhance usability, you can now change the value in the Error Assessment field from Percent of Range to Engineering Units and vice-versa in the following calibration templates:
  • Calibration Template, Analog
  • Calibration Template, Discrete
To facilitate this enhancement, the following changes have been implemented:
  • The Error Assessment field has been added to the Calibration Template, Analog and Calibration Template, Discrete datasheets.
  • The Max Error Limit or Engineering Units Error Limit field is enabled based on the value selected in the Error Assessment field in the template.
  • When you access Calibration, Analog or Calibration, Discrete records, the Error Assessment field is disabled and populated from the template that is linked to the calibration.
  • The Calibration Error Limit or Engineering Units Error Limit field is enabled based on the value in the Error Assessment field in the Calibration record.
  • US273397
  • US273395
To enhance usability, you can now enter the exact value of the error limits in engineering units in the following calibrations:
  • Calibration Results, Analyzer record linked to a Calibration, Analyzer Single Component record
  • Calibration Results, Analog record in Weight Scale Calibration
To facilitate this enhancement, the following changes have been implemented:
  • When you access calibration templates, either the Max Error Limit or Engineering Units Error Limit field is enabled based on the option selected in the Error Assessment field.
  • When you access calibration results, the As Found and As Left values now appear in engineering units only if the value in the Error Assessment field in the Calibration record is Engineering Units.
  • New fields, Eng. Unit AF Error and Eng. Unit AL Error, have been added to the Calibration Results, Analyzer family.
  • A new field, Engineering Units Error Limit, has been added to the Calibration Template, Single Component Analyzer and Calibration Template, Weight Scale families.
  • The Error Assessment and Engineering Units Error Limit fields have been added to the Calibration Template, Single Component Analyzer and Calibration Template, Weight Scale datasheets.
  • US266110
  • US266102
The amplitude peak-to-peak voltage has been set to 5VDC for the frequency-sourced calibrations. This enables Fluke 74X and 75X to generate wave forms with 5VDC amplitude when you send data to the device. US266086
Table 19. Resolved Issues
NoteTracking ID(s)
Previously, every time you navigated away from the Calibration Queue section and then accessed it again, the dates in the Due Date Range box were erroneously updated, although they appeared correctly in the UI. As a result, additional records appeared if calibration tasks existed for the new date range. This issue has been resolved. DE87327
Previously, in the Download Calibration Checklists section of the Receive From Device window, after receiving data from the Fluke calibrator, in the Data subsection, the status of the records received was incorrectly displayed with the number of records sent to the calibrator instead of the number of records received. This issue existed when the calibration was not completed on the Fluke device. This issue has been resolved.DE82721
Previously, in the Identification section of a Calibration Event datasheet, you could add a value in the Cylinder ID drop-down list box even if it did not match the ID of a Standard Gas Cylinder. This issue has been resolved. Now, you must select an existing option in the Cylinder ID box, which contains only the Cylinder IDs of existing Standard Gas Cylinders.DE82499
Previously, when you switched from the Calibration Profile datasheet to another page, and then returned to the same Calibration Profile datasheet, the Link Asset(s) button () and the Search button () that previously appeared in the Linked Assets section no longer appeared. This issue has been resolved.DE81983

Connections

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 20. Enhancements and New Features
NoteTracking ID(s)
You can now access the SQL Server Reporting Services feature in the Connections page.US283296

General Dashboards

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 21. Resolved Issues
NoteTracking ID(s)
Previously, if a category for a Calendar widget contained a special character, the widget did not appear as expected. This issue has been resolved. DE83036

Data Loaders UDLP V2.5.0

This topic contains a list of product changes released for this adapter.

Release Date: Sept. 21, 2018

Table 22. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the Work History Data Loader, the WorkHistoryToWHDetails worksheet now contains a field that relates the Work History Detail record to the Work History record.DE81126
Table 23. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when loading data with a timestamp specified as a key field, the APM Family data loaders did not update records correctly; they created duplicate records. This issue has been resolved. Now, the data loaders update records correctly. US258019
Previously, using the Role data loader, when you attempted to assign an existing Security User or an existing Security Group to a role that had users or groups assigned to it, an error occurred. This issue has been resolved.DE82630
Previously, when running the Work History jobs, GE Digital APM created Success and Failure logs for Work History records that failed to relate Equipment or Functional Location records that did not have a Site record. This issue has been resolved. Now, only a Failure log is created when a Site record is missing.DE80426

eLog

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 24. Enhancements and New Features
NoteTracking ID(s)
The following fields have been added to the Shift family:
  • Description
  • End Date
  • End Time
  • Functional Location
  • Start Date
  • Start Time
  • Teams

Additionally, the Shift ID field is now named the Shift Name field.

US271668
You can now assign one or more teams to a Shift. To facilitate this enhancement, the Teams field has been added to the Shift family.US254814
Table 25. Deferred Features
NoteTracking ID(s)
In eLog, in the Shift Records topic, the following fields have not been included:
  • Description
  • End Date
  • End Time
  • Functional Location
  • Start Date
  • Start Time
  • Teams

Additionally, the Shift ID field has not been named the Shift Name field.

US271668

Failure Modes and Effects Analysis

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 26. Enhancements and New Features

The following enhancements and new features have been added.

NoteTracking ID(s)
To aid in importing data via a Failure Modes and Effects Analysis (FMEA) Data Loader, sample data has been added to the following data loader workbooks:
  • Failure Modes and Effects Analysis (FMEA) Data Loader
  • Failure Modes and Effects Analysis (FMEA) Asset Templates Data Loader

  • Failure Modes and Effects Analysis (FMEA) Analysis Templates Data Loader

US265465
Table 27. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

NoteTracking ID(s)
Previously, in the following pages, the following graphs did not load successfully:
  • The Asset Strategy Management Overview page
    • Asset Strategies by State
  • The Asset Strategy Implementation Overview page
    • Implementation Packages by State
  • The Failure Modes and Effects Analysis page
    • FMEA Analyses by State
    • FMEA Recommended Actions by State
  • The Reliability Centered Maintenance page
    • RCM Analyses by State
    • RCM Recommended Actions by State
This issue has been resolved.
DE86642
Previously, in the Recommended Actions pane, when you selected multiple Recommendations with different states, the More Options button was incorrectly enabled. This issue has been resolved. Now, when you select multiple Recommendations with different states, the More Options button is disabled. DE85938
Previously, if you attempted to promote a large number of Recommendations across multiple assets, the process failed, and an error occurred. This issue has been resolved.DE85208
Previously, in the Recommendations page, the Asset Filter was based only on the first 25 loaded records. This issue has been resolved. Now, the Asset Filter will be based on all related assets.DE85018
Previously, in the Analysis Details page, if you modified the Decision Logic of a Failure Effect, the changes were not saved. This issue has been resolved.DE84022
Previously, when you executed the Failure Modes and Effects Analysis (FMEA) Data Loader, some records did not receive the site key, and after promoting the analysis to Asset Strategy Management (ASM), an error occurred. This issue has been resolved.DE82937
Previously, in iOS devices, in the Analysis Details page, the Apply Template Builder – Select Template window extended beyond the screen, and you were not able to view all the columns. This issue has been resolved. Now, a scroll bar has been implemented in the Apply Template Builder – Select Template window. DE82611
Previously, in the Analysis Details page, when you pasted a Failure Effect, no message appeared indicating that the operation was successful. This issue has been resolved.DE82606
Previously, when deleting an analysis from the Analysis Details workspace, if you selected the Delete button () in the page heading, the busy indicator did not appear. This issue has been resolved.DE79681
Previously, when viewing an existing FMEA template in the Template Details page, if you attempted to perform a search using the option in the heading of the pane, an error occurred. This issue has been resolved. DE79677
Previously, if a Security User did not have permissions to access RCM FMEA Recommendation records, when they selected an RCM FMEA Recommendation record returned by the Global Search feature, the record did not load. This issue has been resolved. Now, if a Security User does not have permissions to access RCM FMEA Recommendation records, the Access Denied page appears as expected.DE79666

Family Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 28. Enhancements and New Features
NoteTracking ID(s)
If you enable the state functionality for a subfamily without inheriting the state configuration of its root baseline family, the Reserved State check boxes for the states and the Is Reserved check boxes for the operations are cleared, thus allowing you to modify or remove the inherited states and operations.US270602

Family Policies

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 29. Enhancements and New Features
NoteTracking ID(s)
You can now configure the Sub Policy node to iterate the execution of a sub policy for evaluating a collection of input values.US259940
You can now configure a Sub Policy node to execute a specific instance associated with the sub policy.US255681
You can now add numeric values to and subtract numeric values from time stamp and time span values, where the numeric values represent time in seconds.US229153
To enhance usability when performing complex calculations involving multiple input values, a Math node can now perform operations on mathematical expressions where a single variable represents a collection of numeric values derived from the output of a predecessor node.US204329
You can now configure the time for which the execution history of Policies must be stored in the GE Digital APM database. To facilitate this enhancement, Policy Designer has been added to the Application Settings page.
  • US192152
  • US165727
Table 30. Resolved Issues
NoteTracking ID(s)
Previously, if you had used an Average node in a Policy to calculate the average value of a collection of very large numbers, the output of the node was intermittently incorrect. This issue has been resolved.US246552

Previously, when you attempted to access a Policy where the value in a calculated column of a Query was mapped to a node in the Policy model, the Policy did not load if you modified one of the following details in the Query:

  • Name
  • Catalog path
  • Column ID of the calculated column
  • Content of a column to a calculated value

This issue has been resolved. Now, in this scenario, the Policy loads as expected. Additionally, an error message appears in the notification bar if you access the Policy after modifying the name, catalog path, or column ID of the calculated column, in the Query.

DE87006
Previously, when you attempted to create a Family Policy for a Relationship family, the Baseline Rule node did not appear in the Calculations section of the toolbar in the Design workspace. This issue has been resolved.DE86916

Previously, when you attempted to configure a Sub Policy node to pass one of the following values to a Point Value node, which is configured to represent a Data Frame value in the sub policy, an error message indicating incorrect data type appeared in the notification bar and you could not activate the Policy:

  • The Readings collection output of a Health Indicator node.
  • The Readings collection output of a Measurement Location node.
  • The HDA Readings collection output of an OPC Tag node.

However, you could successfully validate the Policy. This issue has been resolved. Now, in this scenario, the error message does not appear in the notification bar and you can activate the Policy.

DE85420
Previously, if the Data Frame, Matrix, or Vector input configured for an R Script node contained a null value, validation and execution of the Policy failed. This issue has been resolved.DE80649
Previously, in a Policy model, if you did not specify the data type of the value represented by a Constant node and configured another node to use the output of the Constant node as an input, validation of the Policy failed. However, the validation was successful if you had previously validated the same Policy with a data type for the Constant node. This issue has been resolved. Now, irrespective of the previous validations, you can successfully validate the Policy without specifying any data type for the value represented by a Constant node.DE80646
Previously, if you specified a collection of date and time values expressed as strings to be the input of an Average node, and then validated or executed the Policy, a warning appeared in the notification bar and the string values for date and time were not included in calculating the average value. This issue has been resolved.DE80645
Previously, in the Properties window for a Constant node, if you did not specify any values in the Data Type and Value boxes, and then configured an Is Null node to use the output of the Constant node as the input, the validation and execution of the Policy failed. This issue has been resolved.DE80638
Previously, if you attempted to validate a Policy using an ad hoc test value with more than three digits for a Point Value node configured to represent integer data, the validation failed. This issue has been resolved.DE80633
Previously, if you copied and pasted all the nodes and connections of a Policy containing a Case node, in the pasted Policy model, the mappings between the predecessor nodes and the fields in the If Input and Else sections of the Case node were not retained. This issue has been resolved.DE80630
Previously, if you deleted a module workflow Policy or a baseline Policy associated with a family, the deleted Policy could not be restored. This issue has been resolved. Now, the Delete button () is disabled for the module workflow Policies and baseline Policies associated with families.DE51859
Previously, in the Properties window for a node, if you specified a fractional value of hours, minutes, or seconds as a timespan value, a notification indicating invalid data appeared in the notification bar and validation of the Policy failed. This issue has been resolved.DE51850

Foundation

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 31. Enhancements and New Features
NoteTracking ID(s)
In the module navigation menu, in interfaces where the Apps option appears, the position of the option has been moved such that it is now the final option in the menu.US275522
In the Edit Schedule window, while scheduling the recurring jobs in monthly or yearly intervals, you can now schedule the jobs for selected days in multiple weeks. For example, if you want to schedule a job on the first and second Saturdays of a month, you can select First and Second in the Days drop-down list box and Saturday in the adjacent drop-down list box. US260695

Generation Availability Analysis (GAA)

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 32. Resolved Issues
NoteTracking ID(s)
Previously, when you deleted a GAA Company, the Functional Location associated with it was also deleted. This issue has been resolved.DE80299
Previously, you could not create a Contributing Event for a Related Event. This issue has been resolved.DE61703

Generation Availability Analysis Wind (GAA Wind)

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 33. Enhancements and New Features
NoteTracking ID(s)
The Generation Availability Analysis Wind (GAA Wind) module has been introduced in V4.3.0.6.0. You can use this module to record generation and loss data for each wind plant in your fleet. US287419

Help Configuration

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 34. Obsolete Features
NoteTracking ID(s)
The Help Configuration feature is no longer available. When you upgrade to GE Digital APM V4.3.0.6.0, the GE Digital APM help content is installed in the default location on the GE Digital Application server. No additional setup steps are required, and the help content must remain in this location.US287438

Inspection Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 35. Enhancements and New Features
NoteTracking ID(s)
You can now use State Management for the approval work process of Inspection Recommendation. To facilitate this enhancement, the following changes have been made in the Application Configurations section in the Inspection Configuration page in Application Settings:
  • A new preference, Use State Management for Inspection Recommendations, has been added. You can now select Status or State Management to manage Inspection Recommendations.
  • A new utility, Configure Status to State Mapping, has been added to map each Status to a corresponding State. After mapping, you can update the existing Inspection Recommendation records to use the new states for the approval work process.
US284119
In the Queries section in the Overview Configuration page in Application Settings, the following queries have been added:
  • Open Recommendations for Asset (State Management)
  • Open Inspection Recommendations for Unit (State Management)
  • Overdue Inspection Recommendations for Unit (State Management)
These queries are used when the Use State Management for Inspection Recommendations check box in the Application Configurations section in the Inspection Configuration page in Application Settings is selected.
US280130

You can now use two new secured user roles when transitioning states for Inspection Recommendations:

  • MI Inspector
  • MI Inspection Supervisor
US278613
You can now change the state of Inspection Recommendations using the Recommended Actions pane.US276822
Table 36. Resolved Issues
NoteTracking ID(s)
Previously, in the Inspection Management module, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, the Asset Overview page appeared as if the functional location were an asset. This issue has been resolved. Now, the Inspection Management Overview page appears as expected.DE84510
Previously, in the Asset Hierarchy Configuration page, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, in the Integrity section, an incorrect hyperlink appeared, behaving as if the functional location were an asset. Also, the number of linked records in the Asset Hierarchy page was incorrect. This issue has been resolved.DE84510
Previously, when you attempted to save an inspection and the save failed, the busy indicator remained in the page until you refreshed the page. This issue has been resolved. DE83057

Life Cycle Costing

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 37. Resolved Issues
NoteTracking ID(s)
Previously, in the Cost Data grid, if you created a Blank Row in the grid and then populated the fields in that row with numbers, if you then attempted to delete that row, the row was not deleted. This issue has been resolved. Now, if you delete a newly created Blank Row with populated numerical values in the grid, the row deletes as expected.DE87667
Previously, in the Analysis Summary page, in the Summary section, if you selected either Capital Cost BreakDown or Operating Cost BreakDown from the drop-down list box, and then selected the Show Data button (), the scenario names appeared in the Sequence Name column instead of the Scenario Name column. This issue has been resolved. DE86857
Previously, you could not delete newly created Operating Cost Data from a Cost Data grid. This issue has been resolved. DE83606
Previously, you could not use a URL to access the LCC Summary page. This issue has been resolved.DE83153
Previously, in the Analysis Summary page for a new LCC Analysis, when viewing the Cost Data section of a Scenario, if you expanded the Calculated Values row, the Primary Element row was erroneously collapsed. Also, in the grid in the Cost Data section, the cells were misaligned. These issues have been resolved. DE83011

Manage Translations

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 38. Enhancements and New Features
NoteTracking ID(s)
Polish is now a supported language in GE Digital APM.US267465

Maximo UDLP V2.5.0

This topic contains a list of product changes released for this adapter.

Release Date: Sept. 21, 2018

Table 39. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when running a job to extract Service Request records with a site filter, the job failed. This issue has been resolved. Now, the Service Request records are extracted, and the job completes successfully.DE84357
Previously, when running a job to extract Functional Location records without using a Site filter, all data for the site was extracted. This issue has been resolved. Now, only the Functional Location records are extracted.DE82025

Policy Designer

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 40. Enhancements and New Features
NoteTracking ID(s)
You can now specify a null value as the test value to validate a Policy. US274590
You can now identify the Policy instances that are not imported due to duplicate IDs. To facilitate this enhancement, the data loader log has been modified to display a warning message indicating the instances that are skipped. US264577
You can now configure a hyperlink to execute specific active instances or all the active instances associated with an active policy.US260150
You can now export the instances associated with a Policy to a Microsoft Excel file. To facilitate this enhancement, the Export Instances button has been added to the Instances section in the Design workspace of Policy Designer.US260122
You can now access all active and inactive Policies from a single section in the Policy Designer Overview page. To facilitate this enhancement, the Active Policies, Inactive Policies, and Recent Policies tabs are combined into a single tab labeled Policies.US260114
You can now configure the Sub Policy node to iterate the execution of a sub policy for evaluating a collection of input values.US259940
You can now configure a Sub Policy node to execute a specific instance associated with the sub policy.US255681
You can now use an entity ID in the Policy Instance Data Loader workbook to map a record to an Input node of a Policy. US255678

You can now specify Policy and Instance names with up to 255 characters. To facilitate this enhancement, the character limit of the following fields has been increased from 50 to 255:

  • Name box in the Details workspace
  • Instance box in the Instances pane
  • US255677
  • US255676
You can now add numeric values to and subtract numeric values from time stamp and time span values, where the numeric values represent time in seconds.US229153
To enhance usability when performing complex calculations involving multiple input values, a Math node can now perform operations on mathematical expressions where a single variable represents a collection of numeric values derived from the output of a predecessor node.US204329
You can now configure the time for which the execution history of Policies must be stored in the GE Digital APM database. To facilitate this enhancement, Policy Designer has been added to the Application Settings page.
  • US192152
  • US165727
A new Security Group, MI Policy Administrator, has been added and assigned to the MI Health Admin role, with exclusive rights to configure the execution history retention settings for the Policy Designer module.US192151
Table 41. Resolved Issues
NoteTracking ID(s)
Previously, if you had used an Average node in a Policy to calculate the average value of a collection of very large numbers, the output of the node was intermittently incorrect. This issue has been resolved.US246552
Previously, when you started the Policy Trigger Service or Policy Execution Service, the service did not connect to data sources after it failed to check the Policy Designer license for a data source. This issue has been resolved.DE87835

Previously, when you attempted to access a Policy where the value in a calculated column of a Query was mapped to a node in the Policy model, the Policy did not load if you modified one of the following details in the Query:

  • Name
  • Catalog path
  • Column ID of the calculated column
  • Content of a column to a calculated value

This issue has been resolved. Now, in this scenario, the Policy loads as expected. Additionally, an error message appears in the notification bar if you access the Policy after modifying the name, catalog path, or column ID of the calculated column, in the Query.

DE87006

Previously, when you attempted to configure a Sub Policy node to pass one of the following values to a Point Value node, which is configured to represent a Data Frame value in the sub policy, an error message indicating incorrect data type appeared in the notification bar and you could not activate the Policy:

  • The Readings collection output of a Health Indicator node.
  • The Readings collection output of a Measurement Location node.
  • The HDA Readings collection output of an OPC Tag node.

However, you could successfully validate the Policy. This issue has been resolved. Now, in this scenario, the error message does not appear in the notification bar and you can activate the Policy.

DE85420
Previously, in the Analysis Details page, if you modified the Decision Logic of a Failure Effect, the changes were not saved. This issue has been resolved.DE84022
Previously, if the Data Frame, Matrix, or Vector input configured for an R Script node contained a null value, validation and execution of the Policy failed. This issue has been resolved.DE80649
Previously, when you upgraded GE Digital APMfrom v3.5 or v3.6 to a later version, and then accessed a Policy to view the execution details of a Create Recommendation node that was executed before the upgrade, you could not access the associated Policy Recommendation record using the hyperlink in the Execution Details window. This issue has been resolved. DE80648
Previously, in a Policy model, if you did not specify the data type of the value represented by a Constant node and configured another node to use the output of the Constant node as an input, validation of the Policy failed. However, the validation was successful if you had previously validated the same Policy with a data type for the Constant node. This issue has been resolved. Now, irrespective of the previous validations, you can successfully validate the Policy without specifying any data type for the value represented by a Constant node.DE80646
Previously, if you specified a collection of date and time values expressed as strings to be the input of an Average node, and then validated or executed the Policy, a warning appeared in the notification bar and the string values for date and time were not included in calculating the average value. This issue has been resolved.DE80645
Previously, in the Properties window for a Constant node, if you did not specify any values in the Data Type and Value boxes, and then configured an Is Null node to use the output of the Constant node as the input, the validation and execution of the Policy failed. This issue has been resolved.DE80638
Previously, when you attempted to copy an existing Policy with the associated instances, in the Save Policy With Instances As window, after you selected OK, there was no indication that the operation of saving the new Policy was in progress. This issue has been resolved. Now, a loading spinner appears while the new Policy is being saved.DE80637
Previously, if you attempted to validate a Policy using an ad hoc test value with more than three digits for a Point Value node configured to represent integer data, the validation failed. This issue has been resolved.DE80633
Previously, if you copied and pasted all the nodes and connections of a Policy containing a Case node, in the pasted Policy model, the mappings between the predecessor nodes and the fields in the If Input and Else sections of the Case node were not retained. This issue has been resolved.DE80630

Previously, if the Policy Trigger Service failed to start due to one of the following reasons, an error message did not appear in the Policy Trigger Service log:

  • An invalid Data Source.
  • An offline Data Source.
  • Inactive Policy Designer license.

This issue has been resolved. Now, in this scenario, an error message appears in the Policy Trigger Service log, providing the reason for the failure of the Policy Trigger Service.

DE76472
Previously, if you deleted a module workflow Policy or a baseline Policy associated with a family, the deleted Policy could not be restored. This issue has been resolved. Now, the Delete button () is disabled for the module workflow Policies and baseline Policies associated with families.DE51859
Previously, in the Properties window for a node, if you specified a fractional value of hours, minutes, or seconds as a timespan value, a notification indicating invalid data appeared in the notification bar and validation of the Policy failed. This issue has been resolved.DE51850

Previously, while validating a Policy using ad hoc test values, the unspecified test values were considered as follows:

  • An empty string, if no values were specified.
  • A null value, if an existing test value for the Input node was deleted.

These issues have been resolved. Now, if you validate the Policy without specifying a test value for an Input node, the unspecified value represents an empty string, and it represents a null value only when you specify the test value as null.

DE51823

Production Loss Analysis (PLA)

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 42. Enhancements and New Features
NoteTracking ID(s)

To improve usability, you can no longer perform the following tasks:

  • Modify the value in the Code field of an Impact Code that is associated with a Production Loss record.
  • Modify the value in the OEE Code field of an OEE Code that is associated with a Production Loss record.
  • Modify the value in the Code field of a Production Event Code that is associated with a Production Event record or a Production Unit record.
  • Delete an Impact Code that is associated with a Production Loss record.
  • Delete an OEE Code that is associated with a Production Loss record.
  • Delete an OEE Code whose child OEE Code is associated with a Production Loss record.
  • Delete multiple OEE Codes at once if at least one of them is associated with a Production Loss record.
  • Delete an OEE Code that is mapped to an Impact Code.

  • Delete a Production Event Code that is associated with a Production Event record or a Production Unit record.
  • Delete a Production Event Code whose child Production Event Code is associated with a Production Event record or a Production Unit record.
  • Delete multiple Production Event Codes at once if at least one of them is associated with a Production Event record or a Production Unit record.
  • US284833
  • US254820

To improve performance, the following changes have been made:

  • In the Production Event family, the Source Production Unit field now stores the key of the Production Unit.
  • In the Production Loss family, the Production Event field now stores the key of the Production Event.
US267512

You can now create a mapping between Impact Codes and OEE Codes. To facilitate this enhancement, in the PLA Administrator page, the Codes workspace has been modified to display the following sections:

  • Impact Codes: Contains the following subsections:

    • Details

    • Map OEE Codes
  • OEE Codes

  • Event Codes

To create a mapping, the Map OEE Codes subsection for an Impact Code contains check boxes for each OEE Code. These check boxes are automatically selected for existing OEE Codes. You can, however, clear the check boxes to remove the mapping.

Additionally, when you now create a Production Loss, in the Select OEE Code window, only the OEE Codes that are mapped to the Impact Code in the Impact Code box appear.

US254843

You can now specify a tolerance limit for the planned production of a Production Data record. To facilitate this enhancement, the Tolerance Limit (%) box has been added to the Settings window.

The tolerance limit of the planned production determines whether a Loss Amount of a Production Loss for the Production Data record will be adjusted.

Note: The Tolerance Limit (%) box is automatically populated with the value 0. You can, however, modify the value in the box.
US254838
You can now indicate whether a Production Event needs a Root Cause Analysis (RCA). To facilitate this enhancement, a new field, RCA Needed, has been added to the Production Event family and the Production Event worksheet in the Production Loss Analysis (PLA) 2-Event Data Loader.US254835
The Equivalent Downtime Hours field in Production Loss records is now disabled. DE82991
Table 43. Resolved Issues
NoteTracking ID(s)
Previously, for users whose Culture setting required the comma to be used as the decimal separator (for example, German), the following issues occurred:
  • In a Production Data record, you could not enter a comma in the Actual and Short Range Plan fields.

  • In the Production Data workspace, the value that appeared in the MSHR column was incorrect if the value in the Maximum Sustained Hourly Rate field in the corresponding Production Profile record was a decimal fraction.

  • In a Production Data record, the value in the Short Range field was incorrect if the corresponding planned production amount in the Plan Details workspace was a decimal fraction.

These issues have been resolved.
DE88453
Previously, when adding or modifying a Production Loss, when selecting the OEE Code, selecting a subordinate option in the hierarchy did not clear the predecessor option selection as expected. This issue has been resolved.DE81538
Previously, if you created a Production Plan from a Plan Template when the Review Plan Before Creating check box was cleared, the Plan Details and Production Data records were created per day regardless of the Data Entry Frequency specified in the Plan Template. This issue has been resolved.DE80557
Previously, when creating a Plan Template, if you selected the Finish button more than once, multiple Plan Templates with the same name were created. This issue has been resolved.DE62305

Process Data Integration (PDI)

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 44. Resolved Issues
DetailsTracking ID(s)
Previously, the PDI service only processed the first 10,000 XI tags in the GE Digital APM database. This issue has been resolved. Now, the PDI service processes all XI tags.DE86061
Previously, PDI failed and issued COM errors when starting. This issue has been resolved. Now, the COM error is logged as an informational message and PDI processing runs normally.DE86032
Previously, when you attempted to start the PDI service on the PDI server, an error occurred. This issue has been resolved.DE85373

Queries

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 45. Enhancements and New Features
NoteTracking ID(s)
You can now configure a hyperlink in a Query to execute an active instance or all the active instances associated with an active policy. To facilitate this enhancement, the Execute all instances of the Policy and Execute single instance of the Policy options have been added to the Select URL Type section of the URL Builder window.US260153
Table 46. Resolved Issues
NoteTracking ID(s)
Previously, in query results, calculated results that should have displayed a value of Blank or Null incorrectly displayed a value of 0 (zero). This issue has been resolved.DE74645

Reliability Analytics

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 47. Enhancements and New Features
NoteTracking ID(s)

To enhance usability, while viewing a graph, you can now set the Distribution Parameters for the following plots:

  • CDF Plot
  • Failure Rate Plot
  • PDF Plot
  • Probability Plot

With the Distribution Parameters option selected, you can now change the values for Beta, Eta, and Gamma.

US280608

The following distribution types have been added to the Reliability Distribution and Probability Distribution graphs:

  • Generalized Extreme Value Distribution
  • Gumbel Distribution
  • Triangular Distribution
  • US259200
  • US259199
  • US259198
In the Reliability Distribution Comparison Plot, you can now select the plot line to access the Reliability Distribution Analysis page corresponding to the line.US256603
In the Reliability Growth Comparison Plot, you can now select the plot line to access the Reliability Growth Analysis page corresponding to the line.US256600
To enhance usability, when creating an analysis, in the Reliability Growth Data Editor window or the Reliability Distribution Data Editor window, you can now select multiple assets to delete from the new analysis at one time.US256503
In Reliability Distribution, when viewing a plot, you can now adjust the x-axis to vary the display range.US254521
Table 48. Resolved Issues
NoteTracking ID(s)
Previously, in the Cumulative Failures Plot section of the Analysis Summary page for a Reliability Growth analysis, if you were logged in to the GE Digital APM Unified environment as a Super User that was not part of either the MI Reliability User Security Group or the Mi Reliability Administrator Security Group, the Growth Options and the Analysis Tasks menus did not appear. This issue has been resolved. DE88466
Previously, when creating a Reliability Growth analysis from a query, if the created analysis was assigned to a specific site, the site assignment did not properly restrict the source data to that site. As a result, all queried data was included in the Reliability Growth analysis, regardless of the site assignment. This issue has been resolved.DE86856
Previously, when creating a new Reliability Distribution analysis, if you placed your cursor in the Analysis Name field and then pressed Tab to navigate to a different field, an error occurred. This issue has been resolved.DE84432
Previously, when creating a Recommended Action, in the Target Completion Date field, if you selected a Target Completion Date that was prior to the current date, the Recommendation record was erroneously saved, and no error occurred. This issue has been resolved. Now, if you attempt to select a date in the Target Completion Date field that is prior to the current date, an error occurs as expected.DE83123
Previously, when you accessed the report for a Reliability Growth Analysis based on costs, the fields in the Analysis Summary section were incorrectly labeled as failures. This issue has been resolved.DE80604
Previously, when accessing an Asset Strategy Optimization Analysis from either Asset Strategy Management or from a System Reliability Analysis, in the Definitions section, if you modified the value in the Scenario Name field and then navigated away from the section, there was no indication that your changes were not saved. This issue has been resolved. Now, if you modify the value in the Scenario Name field and then navigate away from the Definitions section, a message appears, indicating that your changes have not yet been saved.DE78114

Reliability Centered Maintenance

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 49. Enhancements and New Features

The following enhancements and new features have been added.

NoteTracking ID(s)
To enhance usability, error messages related to RCA records have been updated to be more informative. US271722
To aid in importing data via the Reliability Centered Maintenance (RCM) Data Loader, sample data has been added to the Reliability Centered Maintenance (RCM) data loader workbook.US265465
Table 50. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

NoteTracking ID(s)
Previously, in the Recommended Actions pane, when you selected multiple Recommendations with different states, the More Options button was incorrectly enabled. This issue has been resolved. Now, when you select multiple Recommendations with different states, the More Options button is disabled. DE85938
Previously, if you attempted to promote a large number of Recommendations across multiple assets, the process failed, and an error occurred. This issue has been resolved.DE85208
Previously, in Reliability Centered Maintenance, in the Recommendations page, the Asset Filter was based only on the first 25 loaded records. This issue has been resolved. Now, the Asset Filter will be based on all related assets.DE85018
Previously, in the Analysis Details page, if you modified the Decision Logic of a Failure Effect, the changes were not saved. This issue has been resolved.DE84022
Previously, when you executed the Reliability Centered Maintenance (RCM) Data Loader, some records did not receive the site key, and after promoting the analysis to Asset Strategy Management (ASM), an error occurred. This issue has been resolved. DE82937
Previously, in iOS devices, in the Analysis Details page, the Apply Template Builder – Select Template window extended beyond the screen, and you were not able to view all the columns. This issue has been resolved. Now, a scroll bar has been implemented in the Apply Template Builder – Select Template window.DE82611
Previously, in the RCM Overview page, in Risks section, the Failure Mode column was not sorted in ascending order. This issue has been resolved.DE82608
Previously, in the Analysis Details page, when you pasted a Failure Effect, no message appeared indicating that the operation was successful. This issue has been resolved.DE82606
Previously, when deleting an analysis from the Analysis Details workspace, if you selected the Delete button () in the page heading, the busy indicator did not appear. This issue has been resolved.DE79681
Previously, when viewing an existing RCM template in the Template Details page, if you attempted to perform a search using the option in the heading of the pane, an error occurred. This issue has been resolved. DE79677
Previously, if a Security User did not have permissions to access RCM FMEA Recommendation records, when they selected an RCM FMEA Recommendation record returned by the Global Search feature, the record did not load. This issue has been resolved. Now, if a Security User does not have permissions to access RCM FMEA Recommendation records, the Access Denied page appears as expected.DE79666

Report Configuration

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 51. Enhancements and New Features
NoteTracking ID(s)
You can now customize the SQL Server Reporting Services (SSRS) reports with a logo that is specific to your organization. To facilitate this functionality, a new feature, Report Configuration, has been added in the Operations Manager page, with which you can either select the default GE Digital logo or configure a new logo that you want in the SSRS reports.
Note: For a logo, the size of the image must be less than or equal to 1 MB, and the image must be in one of the following formats:
  • .jpeg
  • .jpg
  • .bmp
  • .png
  • US281234
  • US271434

Risk Based Inspection (RBI) 580

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 52. Enhancements and New Features
NoteTracking ID(s)
The performance of the Risk Based Inspection (RBI) 580 Data Loader has been improved to load 65 RBI Components per Asset with three Degradation Mechanism Evaluation records for each RBI Component.
Note: The maximum number of RBI Components that you can load may vary based on the system configuration, load on the server, and other performance factors.
US284402
You can now link RBI Components to TML Groups using a data loader. To facilitate this enhancement, a new data loader, RBI Components To TML Groups Relationship, has been added.US274082
You can now link multiple RBI Components to a TML Group. To facilitate this enhancement, the TML Group to RBI Component cardinality has been modified to Many to Many in the Mapped to RBI Component relationship family.US274081
You can now generate recommendations from the Active section of the RBI Bulk Evergreening workspace.US274079
The No Recommendations section in the Risk Based Inspection Overview page now displays assets that have at least one component with a Risk Completed analysis with no recommendations. Also, recommendations are now generated for components that have no recommendations. US273998
When you automatically consolidate recommendations, pre-existing recommendations are now consolidated with the new recommendations that are being generated.US273998
When an inspection is linked to the Degradation Mechanism Evaluation (DME), the Inspection Date field in Criticality Degradation Mech Evaluation records is now populated by the date in the Completion Date field. If more than one inspection is linked to the DME, the Inspection Date field uses the latest Completion Date of all the linked inspections. If all inspections are unlinked from the DME, the Inspection Date field is blank. US273157
To enhance usability, in the Unit Summary page, when viewing an RBI Component that is linked to a Corrosion Loop, you can now use the More button () to access the RBI component in the Asset Summary page. Additionally, if you are viewing the RBI Component from the Asset Summary page, you can use the More button () to access the RBI Component in the Unit Summary page if the RBI Component is linked to a Corrosion Loop.US269097
RBI Criticality Analysis has been enhanced to use linear interpolation to look up the Allowable Stress value based on the value in the Design Temperature field. To facilitate this enhancement, the Use Interpolation for Stress Reference Tables check box has been added in the Global Preferences page to enable or disable the linear interpolation for piping and pressure vessel components. US266658
Table 53. Resolved Issues
NoteTracking ID(s)
Previously, in the Risk Based Inspection module, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, the Asset Summary page appeared as if the functional location were an asset. This issue has been resolved. Now, the Risk Based Inspection Overview page appears as expected.DE84510
Previously, in the Asset Hierarchy Configuration page, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, in the Integrity section, an incorrect hyperlink appeared, behaving as if the functional location were an asset. Also, the number of linked records in the Asset Hierarchy page was incorrect. This issue has been resolved.DE84510
Previously, the value in the Recommended Inspection Interval field was incorrect in the LC71 and LC72 Inspection Strategies. This issue has been resolved. Now, the value has been correctly updated to 180 months.DE84263
Previously, the values in the Inspection Confidence, Inspection Extent, and Recommended Inspection Scope fields were incorrect in the following Inspection Strategies:
  • LC49
  • LC491
  • LC50
  • LC501
  • LC51
  • LC511
  • LC54
  • LC541
  • LC55
  • LC551
  • LC56
  • LC561
This issue has been resolved. Now, the values in the Inspection Confidence and Inspection Extent fields have been correctly updated as follows:
Inspection Strategy IDsInspection ConfidenceInspection Extent
LC49, LC491, LC50, LC501MediumUT shear wave 50% of all potential locations
LC51, LC511MediumMT or PT 25% of all potential locations
LC54, LC541, LC55, LC551LowUT shear wave 25% of all potential locations
LC56, LC561LowMT or PT 10% of all potential locations
The Recommended Inspection Scope for all these Inspection Strategies has been updated according to the updated Inspection Confidence and Inspection Extent values.
DE84166
Previously, when you created an analysis where the value in the Design Temperature field was zero and the Stress Lookup Table was Piping or Pressure Vessel, the Allowable Stress field was blank, although the other stress input fields contained valid values. This issue has been resolved.DE84129
Previously, the values in the Recommended Inspection Interval, Inspection Confidence, and Inspection Extent fields were incorrect in the LC59 Inspection Strategy record. This issue has been resolved. Now, the values have been correctly updated as follows:
  • Recommended Inspection Interval: 180 months
  • Inspection Confidence: Low
  • Inspection Extent: UT shear wave 25% of all potential locations
DE83854
Previously, the value in the Recommended Inspection Interval field was incorrect in the LC42 Inspection Strategy. This issue has been resolved. Now, the value has been correctly updated to 240 months.DE83615
Previously, in the RBI Asset Summary and RBI Unit Summary pages, when you tried to delete an RBI component that had related records linked to it, the Delete button () was disabled. This issue has been resolved. Now, the Delete button () is enabled, and, if you try to delete a component with related records, an error message appears, stating that you cannot.DE82415
Previously, when you copied an RBI Analysis that had a linked Criticality Other Damage Mechanism (Qualitative DM), the DF field was incorrectly set to null. This issue has been resolved. Now, the Probability Category field will be validated for Criticality Other Damage Mechanisms.DE82369
Previously, when you accessed the No Recommendations section in the Risk Based Inspection Overview page, an error occurred in the following scenarios:
  • You had an active RBI 580 license but not an RBI 581 license.
  • You had an active RBI 581 license but not an RBI 580 license.
This issue has been resolved.
DE82358
Previously, when calculating an RBI 581 analysis that has a Ferritic Component Atmospheric Corrosion Degradation Mechanism, if the value in the Selected Corrosion Rate field was set to Estimated and the value in the Base Material Estimated Rate field was blank, an invalid error message appeared, stating that the Field Base Material Calculated Corrosion Rate was required. This issue has been resolved. The field caption for the MI_RBDEMEEV_BM_EST_RT_N field is now Estimated Rate.DE82230
Previously, when viewing the Inspection History for a DM that was related to an RBI Analysis, if you tried to unlink a locked Inspection from the DM, an error occurred. This issue has been resolved.DE82226
Previously, you could not promote an asset to ASM although you were a member of the MI Mechanical Integrity Power role. This issue has been resolved. To facilitate this fix, the MI ASM Analyst security group has been added to the MI Mechanical Integrity Power role.DE81525
Previously, you could calculate an analysis only if the Design Temperature of the component was greater than or equal to the Operating Temperature. The behavior was the same for both positive and negative values in the temperature fields. This issue has been resolved. Now, if the value in Design Temperature field is less than zero, you can calculate the analysis with any value in the Operating Temperature field. Similarly, you could calculate an analysis only if the Design Pressure of the component was greater than or equal to the Operating Pressure. The behavior was the same for both positive and negative values in the pressure fields. This issue has been resolved. Now, if the value in the Design Pressure field is less than zero, you can calculate the analysis with any value in the Operating Pressure field. DE81272
Previously, if you were using an Oracle database, the values in the following fields were sometimes set incorrectly:
  • DF field for Internal Corrosion DME
  • Corrosion Factor field for External Corrosion DME
This issue has been resolved.
DE80441

Risk Based Inspection (RBI) 581

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 54. Enhancements and New Features
NoteTracking ID(s)
You can now link RBI Components to TML Groups using a data loader. To facilitate this enhancement, a new data loader, RBI Components To TML Groups Relationship, has been added.US274082
You can now link multiple RBI Components to a TML Group. To facilitate this enhancement, the TML Group to RBI Component cardinality has been modified to Many to Many in the Mapped to RBI Component relationship family.US274081
You can now generate recommendations from the Active section of the RBI Bulk Evergreening workspace.US274079
The No Recommendations section in the Risk Based Inspection Overview page now displays assets that have at least one component with a Risk Completed analysis with no recommendations. Also, recommendations are now generated for components that have no recommendations. US273998
When you automatically consolidate recommendations, pre-existing recommendations are now consolidated with the new recommendations that are being generated.US273998
The Total Damage Factor calculation has been enhanced to adhere to Addendum 1 of the API RBI 581 specification. The Total Damage Factor calculation now takes the sum of the external damage factor and internal damage factor for the following scenarios:
  • External Damage is localized and Internal Damage is general.
  • Internal Damage is localized and External Damage is general.
Previously, the Total Damage Factor calculation only considered the maximum of the external and internal damage factor.
US273472
The following fields in the RBI 581 Consequence Evaluation family are now populated upon calculation with the values from API RBI 3rd Edition Addendum 1 when the component type is not Storage Tank or Tank Bottom:
  • Release Hole Diameter (Large)
  • Release Hole Diameter (Medium)
  • Release Hole Diameter (Rupture)
  • Release Hole Diameter (Small)
US273472
The Leak Duration Max calculation now adheres to API RBI 3rd Edition Addendum 1. As a result, the values in the following fields may change upon calculation:
  • Release Mass (Large)
  • Release Mass (Medium)
  • Release Mass (Rupture)
  • Release Mass (Small)
US273472
When an inspection is linked to the Degradation Mechanism Evaluation (DME), the Last Known Inspection Date field in RBI 581 Damage Mechanism Evaluation records is now populated by the date in the Completion Date. If more than one inspection is linked to the DME, the Last Known Inspection Date field uses the latest Completion Date of all linked inspections. If all inspections are unlinked from the DME, the Last Known Inspection Date field is blank. Also, if the Inspection Auto-Selection preference is enabled, the date uses the most recent date from all inspections linked during analysis creation.US273157
To enhance usability, in the Unit Summary page, when viewing an RBI Component that is linked to a Corrosion Loop, you can now use the More button () to access the RBI component in the Asset Summary page. Additionally, if you are viewing the RBI Component from the Asset Summary page, you can use the More button () to access the RBI Component in the Unit Summary page if the RBI Component is linked to a Corrosion Loop.US269097
RBI Analysis has been enhanced to use linear interpolation to look up the values in the following fields:
  • Allowable Stress based on the value in the Design Temperature field.
  • Flow Stress based on the value in the Yield Strength and Tensile Strength fields.
To facilitate this enhancement, the Use Interpolation for Stress Reference Tables check box has been added in the Global Preferences page to enable or disable the linear interpolation for piping and pressure vessel components.
US266658
Table 55. Resolved Issues
NoteTracking ID(s)
Previously, when calculating an analysis on a Storage Tank Bottom component with a 581 Thinning Damage Mechanism while using metric units, the value in the Expected Metal Loss Fraction (Art) field was incorrect. This value also affected the values in the Base Damage Factor and Final Damage Factor fields. This issue has been resolved.DE87817
Previously, if you had the RBI 581 license but not the Risk Based Inspection license, you could not access the Risk Based Inspection (RBI) Corrosion Loop data loader. This issue has been resolved.DE86846
Previously, in the Risk Based Inspection module, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, the Asset Summary page appeared as if the functional location were an asset. This issue has been resolved. Now, the Risk Based Inspection Overview page appears as expected.DE84510
Previously, in the Asset Hierarchy Configuration page, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, in the Integrity section, an incorrect hyperlink appeared, behaving as if the functional location were an asset. Also, the number of linked records in the Asset Hierarchy page was incorrect. This issue has been resolved.DE84510
Previously, when you created an analysis where the value in the Design Temperature field was zero and the Stress Lookup Table was Piping or Pressure Vessel, the Allowable Stress field was blank, although the other stress input fields contained valid values. This issue has been resolved.DE84129
Previously, in the RBI Asset Summary and RBI Unit Summary pages, when you tried to delete an RBI component that had related records linked to it, the Delete button () was disabled. This issue has been resolved. Now, the Delete button () is enabled, and, if you try to delete a component with related records, an error message appears, stating that you cannot.DE82415
Previously, when you accessed the No Recommendations section in the Risk Based Inspection Overview page, an error occurred in the following scenarios:
  • You had an active RBI 580 license but not an RBI 581 license.
  • You had an active RBI 581 license but not an RBI 580 license.
This issue has been resolved.
DE82358
Previously, when calculating an RBI 581 analysis that has a Ferritic Component Atmospheric Corrosion degradation mechanism, if the value in the Selected Corrosion Rate field was set to Estimated and the value in the Base Material Estimated Rate field was blank, an invalid error message appeared, stating that the Field Base Material Calculated Corrosion Rate was required. This issue has been resolved. The field caption for the MI_RBDEMEEV_BM_EST_RT_N field is now Estimated Rate.DE82230
Previously, when viewing the Inspection History for a DM that was related to an RBI Analysis, if you tried to unlink a locked Inspection from the DM, an error occurred. This issue has been resolved.DE82226
Previously, you could not promote an asset to ASM although you were a member of the MI Mechanical Integrity Power role. This issue has been resolved. To facilitate this fix, the MI ASM Analyst security group has been added to the MI Mechanical Integrity Power role.DE81525
Previously, you could calculate an analysis only if the Design Temperature of the component was greater than or equal to the Operating Temperature. The behavior was the same for both positive and negative values in the temperature fields. This issue has been resolved. Now, if the value in Design Temperature field is less than zero, you can calculate the analysis with any value in the Operating Temperature field. Similarly, you could calculate an analysis only if the Design Pressure was greater than or equal to the Operating Pressure and Operating Pressure was greater than or equal to zero. However, an appropriate message was not displayed if the validation failed. This issue has been resolved. Now, you cannot calculate the analysis with a negative value either in the Design Pressure or in the Operating Pressure field, and an appropriate message is displayed if the validation fails.DE81272

Risk Matrix

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 56. Resolved Issues
NoteTracking ID(s)
Previously, you could not select the Not Applicable check box if your Risk Matrix was configured to show aliases. This issue has been resolved.DE85123

Root Cause Analysis

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 57. Enhancements and New Features
NoteTracking ID(s)
To enhance usability, you can now publish or unpublish an RCA Template from the Template section. To facilitate this enhancement, the Status column and the Is RCI Template column have been added to grid in the Is RCI Template section.US264029
To enhance usability, when viewing a Logic Tree Diagram, if you select a Hypothesis node, Verification records linked to the selected node now appear within the Verifications pane.US254555
Table 58. Resolved Issues
NoteTracking ID(s)
Previously, if you created a custom error message for RCA Analysis Relationship in the relationship definition for the RCA Analysis family, and if you attempted to create a relationship between an RCA Analysis record and record in another RCA family, the custom error message did not appear. This issue has been resolved.DE87687

Rounds Data Collection

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 59. Enhancements and New Features
NoteTracking ID
To improve usability, in the Due Items and Overdue Items sections of the Rounds Data Collection Overview page, the number of assets and the number of checkpoints for each Route no longer appear.US271310
Table 60. Resolved Issues
NoteTracking ID(s)
Previously, when you accessed Rounds Data Collection offline, sometimes, when you selected a Route that was due, no checkpoints appeared in the workspace for the selected Route. This issue has been resolved. To facilitate this fix, the Status column has been removed from the table on the Assigned Routes section of the Rounds Data Collection Overview page. DE88624
Previously, after the reading for a predecessor checkpoint was modified in a way that should have caused the successor checkpoints not to appear in the Route Map pane, successor checkpoints nevertheless continued to appear. This issue has been resolved.DE86320
Previously, when you attempted to access Rounds Data Collection, an error occurred intermittently. This issue has been resolved.
  • DE84834
  • DE84833
Previously, if synchronizing readings to the GE Digital APM database failed, you could not recover the data. This issue has been resolved. You can now recover the data using the Rounds Readings Data Loader. For more information, refer to KBA 6331.DE83877
Previously, in a Measurement Location, when you selected a numeric value in the Reading box, closed the Route, and accessed it again, the value did not appear. The value, however, was saved in the database and appeared in the left pane. This issue has been resolved. DE83774
Previously, when you synchronized Routes, data for Routes that were not modified was also loaded. Due to this, synchronization of data took longer than expected. This issue has been resolved. Now, only the Routes that are modified are loaded. DE83772
Previously, in the Recommendations section of the Rounds Data Collection Overview page, the Assigned To column was blank or displayed an incorrect value. This issue has been resolved. DE82813
Previously, in the Rounds Data Collection Overview page, no Due On or After value appeared in the Due Items section. This issue has been resolved.DE82812
Previously, in the Due Items section of the Rounds Data Collection Overview page, the value in the Next Date field did not appear. This issue has been resolved.DE82812
Previously, you could not scan RFID tags using the Ecom Smart-Ex 01 Android device. This issue has been resolved. DE82354
Previously, if a Route contained many conditional Measurement Locations, it took a long time to update the Route when the Measurement Locations were included in the Route. This issue has been resolved.DE81752
Previously, on a small screen device, the scan button () and the recommendation button () overlapped. This issue has been resolved.DE81501
Previously, when conditional checkpoints were added to a Route, the sequence and count of the assets associated with checkpoints in the left pane were incorrect. As a result, you could not navigate through the assets. This issue has been resolved.DE81270
Previously, when you collected data on a mobile device, if a checkpoint had an image associated with it, the elements in the workspace did not appear as expected. This issue has been resolved. DE79753
Previously, if more than 25 users were assigned to a Route, in the Assign to Team Members window, multiple entries for the users appeared. This issue has been resolved.DE79671
Previously, if you created a Recommendation for a Route in offline mode and then accessed the Route in online mode, the following issues existed for the Route
  • Duplicate entries appeared in the Recommended Actions pane.
  • When you accessed the Mark Done window, the value that appeared in the Recommendations Raised box was incorrect.
  • After you marked the Route as done, the count of Recommendations that appeared in the Route History section was incorrect.

These issues have been resolved.

DE77389
Previously, when you enabled offline access for a large number of Routes, there was a leakage of database connections. This issue has been resolved. Now, in this scenario, the database connections are correctly reused. DE74111

Rounds Designer

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 61. Enhancements and New Features
NoteTracking ID(s)
You can now assign Routes to teams of users in addition to individual users.US274370
Table 62. Resolved Issues
NoteTracking ID(s)
Previously, in the left pane of the workspace for a Route, when you dragged a successor checkpoint above its preceding condition, an error occurred, and you were unable to further modify the Route sequence. This issue has been resolved. DE87173
Previously, when you modified the site for an ML Template in an ML Template Group to a site that conflicted with the site of the ML Template Group, an erroneous error message appeared. This issue has been resolved. Now, in this scenario, the following message appears: Template is currently being used in a Template Group for a different Site. Before changing its Site, you must remove the Template from the Template Group. DE82538
Previously, users with view privileges were unable to access the Rounds Designer Overview page. This issue has been resolved.DE82118
Previously, when you added or modified a condition on a Route, if you selected the node for the same condition in the left pane before saving your changes, a window appeared, notifying you that you had unsaved changes; when you closed the window, an error occurred, and you were unable to save your changes. This issue has been resolved. DE81253
Previously, if you created a Recommendation for a Route in offline mode, and then accessed the Route in online mode, the following issues existed for the Route:
  • Duplicate entries appeared in the Recommended Actions pane.
  • When you accessed the Mark Done window, the value that appeared in the Recommendations Raised box was incorrect.
  • After you marked the Route as done, the count of Recommendations that appeared in the Route History section was incorrect.

These issues have been resolved.

DE77389

SAP and SAP PI ULDP V2.5.0

This topic contains a list of product changes released for this adapter.

SAP - Release Date: Sept. 21, 2018

Table 63. Enhancements

The following enhancements and new features have been added.

DescriptionTracking ID
Asset Criticality Analysis for SAP Adapter is now supported.US264423
The SAP Class Number and Item Number fields have been added to the Technical Characteristics mappings.US257987
Table 64. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when running the Work Management Adapter job for a new Maintenance Plan that was importing a Task List into GE Digital APM for the first time, the system created a revision that was marked as Discontinued. This issue has been resolved. Now, the revision is not created.DE85219
Previously, when a job attempted to load data that exceeded the limit set in the threshold parameters in the context file, the job failed even when OVERRIDE_GUARDRAILS was set to Y. This issue has been resolved. Now, APM Connect correctly indicates that the job failed because you did not configure an SMTP server for email notifications and that the threshold has been exceeded.DE83177
Previously, if you ran the Functional Location Adapter that defines a Functional Location record (for example, FL02) that references a nonexistent Superior Functional Location record (for example, FL03), GE Digital APM created a record for the Superior Functional Location. If you again ran the Functional Location Adapter that defined the previously created Superior Functional Location, GE Digital APM created a duplicate Functional Location (FL03) record. This issue has been resolved. Now, the second run of the Functional Location Adapter updates the previously created Functional Location record.DE82574
Previously, in a cloud environment, Failure records for the First Extract and Load jobs were left on the client side after the Failure records were correctly processed. This issue has been resolved. Now, after the Failure records are correctly processed, they are removed from the client side.DE80528
Previously, when you deleted the last Task List from an SAP Maintenance Plan and ran the Work Management Adapter job, GE Digital APM did not synchronize the tasks. This issue has been resolved. Now, the tasks are removed correctly.DE80440
Previously, in a Multi-EAM environment, GE Digital APM used the Default EAM System ID when attempting to link a Task List or Work Order to an Inspection Task record. This issue has been resolved. Now, the EAM System defined by the related asset is used when retrieving Task List data.DE80014
Previously, if you removed all the Classes and Characteristics from an Equipment or Functional Location in SAP, the APM Technical Characteristics was not synchronized. This issue has been resolved. Now, APM Connect sends any Technical Characteristics data from SAP that needs synchronization.DE80009
Previously, if a Work History record was created from a Notification, values were not populated in the class description fields. This issue has been resolved. Now, the system correctly updates the class description fields.DE76486

SAP PI - Release Date: Sept. 21, 2018

Table 65. Enhancements

The following enhancements and new features have been added.

DescriptionTracking ID
This release provides a combination ABAP Service Pack, which allows you to run SAP-PI Adapters supported by GE Digital APM V3.6.x and GE Digital APM V4.3.x. Information on how to use the package is available from GE Support Services.TFS361381
SAP PI now supports configuring all Work Management Filter parameters in the context file.US280687
Table 66. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when using SAP PI to process Work Management records, the Work Order Numbers were not added in GE Digital APM. This issue has been resolved. Now, the Work Order Numbers are correctly added.DE85195
Previously, the Work Order Long Description field in SAP sent from the SAP PI Adapter only contained the Task Description. This issue has been resolved. Now, the Work Order Long Description in SAP contains the value of the Task Description concatenated with the value of the Task Details.DE83087

Search

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 67. Enhancements and New Features
Search Configuration
NoteTracking ID(s)
The Search feature has been enhanced to allow users to configure the search index to provide more precise results based on customer data. To facilitate this enhancement, in the Search Configuration page, a new button, Settings, has been added. After selecting this button, in the Edit Settings window, an Administrator can now adjust the values in the Minimum Index Size and the Maximum Index Size drop-down list boxes. These fields determine how the Search indices are created. US280404
Table 68. Resolved Issues
Advanced Search
NoteTracking ID(s)
Previously, if you entered values in the Search In, Linked To, and Through boxes and added one or more field conditions to an advanced search, an error occurred when you selected a hyperlink in the Linked To column in the search results. This issue has been resolved.DE82374
Search Configuration
NoteTracking ID(s)
Previously, even if you had deleted a scheduled job, the job was displayed in the Successful section of the Schedule Logs page. This issue has been resolved.DE63687

Security Manager

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 69. Enhancements and New Features
NoteTracking ID(s)
You can now synchronize user information from multiple Microsoft Active Directory domains using the LDAP synchronization process. To facilitate this functionality, a new feature, Cross Domain Configuration, has been added in Operations Manager where you can:
  • Configure more than one cross domain.
  • Define credentials for each cross domain to authenticate the domains while retrieving user information during LDAP synchronization.
US267760
Table 70. Resolved Issues
Lightweight Directory Access Protocol (LDAP)
NoteTracking ID(s)
Previously, during an LDAP synchronization, if the letter case of the user ID of a Security User stored in the GE Digital APM database did not match the letter case of the user ID of the corresponding user record in Microsoft Active Directory, an error occurred. This issue has been resolved.DE83521
Previously, during LDAP synchronization, some Security Users were not assigned to a Security Role even though the role existed in GE Digital APM. This issue has been resolved.DE79483
Users
NoteTracking ID(s)
Previously, for users whose Culture setting was Russian, when the user attempted to change a password in the Users page, if the password did not meet the criteria for the password policy, an incorrect error message appeared. This issue has been resolved. Now, the correct error message appears.DE83049

SIS Management

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 71. Resolved Issues
NoteTracking ID(s)
Previously, while upgrading to V4.3.0.5.0 or any previous versions of V4, when the 9721_ProtectiveLoopUtility was run for upgrading the Oracle database, an error occurred. This issue has been resolved.DE87251

Strategy Macros

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 72. Resolved Issues
NoteTracking ID(s)
Previously, the Strategy Macros option was available in the Operations Manager page only if the Developers license was activated. This issue has been resolved. Now, even if the Developers license is inactive, the Strategy Macros option is available in the Operations Manager page and you can schedule an existing macro. However, you cannot add or delete a macro unless the Developers license is active.DE84831

System Codes and Tables

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 73. Enhancements and New Features
NoteTracking ID(s)
The following baseline system codes have been added to the UOME (Unit of Measure) system code table:
  • MW (MegaWatt)
  • mH (MilliHenry)
  • mWatt (MilliWatt)
  • mOHM (MilliOhm)
  • ms (MilliSecond)
  • mm2/s (Viscosity)
  • V.s (Volt Second)
US270712

Teams

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 74. Enhancements and New Features
NoteTracking ID(s)
You can now create teams and assign the teams to individual modules rather than selecting users individually to assign a task. To facilitate this functionality, a new feature, Teams, has been added in the Tools navigation menu.US261049

Thickness Monitoring

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: September 21, 2018

Table 75. Enhancements and New Features
NoteTracking ID(s)
The B31.8 T-min calculation formula has been modified to use Yield Strength instead of Allowable Stress. Yield Strength is a reference value from the Piping Stress table and is based on the following fields:
  • Design Code
  • Code Year (Allowable Stress Lookup)
  • Material Specification
  • Material Grade
US273898
When calculating a single asset, you can now view and download the log in the Schedule Logs page. US273147
Table 76. Resolved Issues
NoteTracking ID(s)
Previously, when you ran a bulk analysis and viewed the Schedule Logs page, the page heading incorrectly implied that you were generating an inspection document. This issue has been resolved.DE85451
Previously, in the Thickness Monitoring module, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, the Analysis Overview page appeared as if the functional location were an asset. This issue has been resolved. Now, the Thickness Monitoring Overview page appears as expected.DE84510
Previously, in the Asset Hierarchy Configuration page, if you used a family (parent or child) other than the baseline Functional Location family to denote a functional location, in the Integrity section, an incorrect hyperlink appeared, behaving as if the functional location were an asset. Also, the number of linked records in the Asset Hierarchy page was incorrect. This issue has been resolved.DE84510
Previously, when you created a TML for a Piping or a Pressure Vessel component where the value in the Design Temperature field was zero, the Allowable Stress field was blank, although the other stress input fields contained valid values. This issue has been resolved.DE84129
Previously, in a corrosion analysis, if there were many TMLs based on which the values in the Controlling Corrosion Rate (Maximum), Schedule Next Inspection, and Projected T-Min Date fields were calculated, you could not view the complete list of TMLs. This issue has been resolved.DE83061
Previously, when you created or modified a TML Group and modified the Corrosion Group field, the TML Group ID did not update in the page until you navigated away from the page. This issue has been resolved.DE82433
Previously, when you ran a calculation from the TML Group level, other TML Groups associated with the parent asset were not calculated. This issue has been resolved. Now, when you calculate from the TML Group level, the asset and all associated TML Groups are calculated.DE82393
Previously, when you performed a bulk analysis that failed validation, the Schedule Log erroneously listed the analysis in the Successful section. This issue has been resolved.DE82364
Previously, in the Thickness Monitoring Overview page, the Asset View button () was enabled even when you set the asset hierarchy level to Home, and an error message appeared when you selected the Asset View button (). This issue has been resolved. Now, when you set the asset hierarchy level to Home in the Thickness Monitoring Overview page, the Asset View button () is disabled.DE81522
Previously, when you set the UOM Conversion Set as Metric, and then tried to calculate the Asset Corrosion Analysis, the calculation failed as there was no conversion defined from MM/YR to IN/YR(TM). This issue has been resolved.DE81444
Previously, if the Remaining Life field in an Asset Corrosion Analysis stored in an Oracle database contained a value less than 0 with more than six decimal places, the TM calculation failed. This issue has been resolved. To facilitate this fix, the Remaining Life Less than 180 Months query has been modified.DE80578
Previously, if you modified the unit of measure for a Security User and then accessed a Corrosion Rate Distribution graph, the values for the y-axis were not modified per the selected unit of measure. This issue has been resolved. Now, the values for the y-axes of these graphs are modified per the selected unit of measure.DE79752
Previously, the Thickness Monitoring (TM) Equipment and Thickness Monitoring (TM) Functional Location data loaders were performing duplicate validations when a Thickness Measurement record was loaded. This issue has been resolved. A new field, Measurement Imported by Data Loader, has been added to the Thickness Measurement Family. This field indicates if a record is loaded through data loaders to prevent duplicate validations. US272812

APM Classic Deferred Features

This topic provides a list of features that were available in APM Classic V3.X but that are not yet available in the current version.

Release Date: September 21, 2018

Table 77. Asset Health Manager
NoteTracking ID(s)
Asset Hierarchy sorting and filtering based on health indicator status.TFS86430
Table 78. Calibration Management
NoteTracking ID(s)
Automated Calibration using Beamex and Meriam documenting process calibrators.
Note: Automated calibration using Beamex documenting process calibrators, Beamex MC5 and Beamex MC6, is supported using Beamex Business Bridge (B3) Version 1 (1.2.0) software for Beamex CMX Calibration software.
  • TFS61334
  • TFS61319
Table 79. Configuration Manager
NoteTracking ID(s)
Global number and date format.TFS160148
Global Preferences- Background Colors.TFS65297
Table 80. Generation Availability Analysis
NoteTracking ID(s)
The following fields and related functionality form the Performance record:
TabFields
Unit Identification
  • Capacity History Statistics Type
  • Zone
  • Refresh Incident Rollup
Unit Generation Performance
  • Demonstrated Max Capacity (G)
  • Demonstrated Max Capacity (N)
  • Override Reserve Shutdown Hours
  • Sum of fuel BTUs
  • Heat Rate
Unit Starting Characteristics
  • YTD attempted unit starts
  • YTD actual unit starts
  • YTD start reliability
Unit Primary Fuel Information
  • EIA Fuel Reporting
  • Primary Quantity Burned Unit of Measure
  • Primary Fuel BTUs - Contract
  • Primary Fuel BTUs - Electrical Generation
  • Primary Fuel BTUs - Plant Heating and Cooling
  • Primary Fuel BTUs - Process Steam
  • Primary Fuel BTUs - Total
Unit Secondary Fuel Information
  • EIA Fuel Reporting
  • Secondary Quantity Burned Unit of Measure
  • Secondary Fuel BTUs - Contract
  • Secondary Fuel BTUs - Electrical Generation
  • Secondary Fuel BTUs - Plant Heating and Cooling
  • Secondary Fuel BTUs - Process Steam
  • Secondary Fuel BTUs - Total
  • TFS234410
  • TFS234310
The following fields and related functionality from the GAA Plant and GAA Unit record:
DatasheetFields
GAA Plant
  • Date/Time Alternate Format
  • GADS Region
  • GADS Subregion
GAA Unit
  • Demonstrated Maximum Gross Capacity
  • Demonstrated Maximum Net Capacity
  • Summer Net Capacity
  • Winter Net Capacity
TFS229627
The following families in GAA:
  • Generation Forecast
  • Generation Fuel Annual Report
  • Generation Fuel Monthly Report
  • Generation Fuel Report
  • Generation Nameplate
  • Generation Nameplate Combined Cycle
  • Generation Nameplate Diesel
  • Generation Nameplate Fluidized Bed
  • Generation Nameplate Fossil Steam
  • Generation Nameplate Gas Turbine
  • Generation Nameplate Hydro
  • Generation Nameplate Miscellaneous
  • Generation Nameplate Nuclear
  • Generation Role
  • Generation Role Assignment
  • Generation Role Definition
  • Generation Role Field Configuration
  • Generation Unit Loading Profile
  • Generation Unit Starting Profile
  • TFS184663
  • TFS184661
  • TFS184660
  • TFS184659
  • TFS184657
  • TFS184656
  • TFS184655
  • TFS184653
  • TFS184652
  • TFS184646
The following Security Groups in GAA:
  • MI Generation Management Forecast
  • MI Generation Management Nameplate
  • MI Generation Management Security
  • TFS184663
  • TFS184661
  • TFS184660
  • TFS184659
  • TFS184657
  • TFS184656
  • TFS184653
  • TFS184652
  • TFS184646
Table 81. GE Analytics
NoteTracking ID(s)
KPIs for GE Analytics.TFS162791
Table 82. Graphs
NoteTracking ID(s)
Exporting to a PDF and printing graphs.TFS81015
Table 83. Metrics and Scorecards
NoteTracking ID(s)
Export/Import of KPI SchedulesTFS173886
GM (Generation Management) cube is deferred from V4.0.0.0. Any previously deployed GM (Generation Management) cube, which worked in V3.6 and earlier releases, will continue to work in V4.0.0.0 after upgrading the product. You will be able to use the existing GM cube and the support will continue. TFS160446
Selecting columns to include in a Scorecard.TFS70641
Table 84. Reliability Analytics
NoteTracking ID(s)
Action optimization in System Reliability Analysis.N/A
Table 85. Risk Based Inspection
NoteTracking ID(s)
Creating a bulk What-If analysis.TFS73475
Table 86. Rounds
NoteTracking ID(s)
Selecting multiple nodes in the left pane in Route Management.TFS173671
Ad hoc inspection of a single asset.TFS160740
Offline access to the five most recent Recommendations in Rounds.TFS153853
Support for Bluetooth-connected barcode scanners.TFS124935
Unlinking a Measurement Location from a Measurement Location Template.TFS61751
Accessing a list of recent Routes. TFS61638
Table 87. Systems and Tags
NoteTracking ID(s)
Viewing trends for multiple OPC Tags simultaneously (i.e., the Process Data Viewer feature in V3).TFS62299
Table 88. Thickness Monitoring
NoteTracking ID(s)
Corroded Area Measurements.TFS101752
Dataset integration with dataloggers.TFS83553
Exporting data to Excel via the TM Dataloggers interface.N/A