V4.3.0.1.0 Release Notes
V4.3.0.1.0
AMS Analytics
Description | Tracking ID |
---|---|
Previously, on the AMS Analytics Overview page, the Event ID column in both the Active Alerts and the Events workspaces displayed the related AMS Asset ID, and the associated links accessed the related AMS Asset record in Record Manager. This issue has been resolved. Now, the column displays the unique Event ID and the link accesses the corresponding AMS Asset Event record in Record Manager. | TFS323540 |
Previously, when viewing an AMS Trend Chart, on the Enter Parameters window, if you selected Year for the value in the Period box, the default dates were January to December, instead of one year from the date listed in the Date box. This issue has been resolved. | TFS316079 |
APM Connect
Description | Tracking ID |
---|---|
APM Connect now supports S/4 Hana (1511 and 1610) SAP environments for the following SAP Adapters:
| TFS326636 |
Asset Criticality Analysis (ACA)
Description | Tracking ID |
---|---|
Previously, when you used the ACA Data Loader to load analyses into the ACA module, not all relationships between Equipment and Risks were created as expected. This issue has been resolved. | TFS328179 |
Previously, a user without ACA permissions could access the Asset Criticality Analysis page using a hyperlink. This issue has been resolved. Now, if you do not have ACA permissions, you cannot access the Asset Criticality Analysis page. | TFS323181 |
Previously, when you added assets to Asset Groups, the record count on the ACA Analysis Summary Overview page did not update to match. This issue has been resolved. | TFS251070 |
Description | Tracking ID |
---|---|
Promoting analyses to and from ACA. | TFS160858 |
Asset Health Manager (AHM)
Description | Tracking ID |
---|---|
A new field, Do not automatically create health indicator, has been added to the Checkpoint and Checkpoint Template families. If the check box for this field is selected in one of these records, then health indicators will not be created automatically when those new checkpoints are linked to assets. The field appears as a new column in the Health Indicator Source Management workspace. |
|
Description | Tracking ID |
---|---|
Previously, the number of readings displayed in trend charts was limited based on the trend type. This issue has been resolved. Now, all trend charts can show up to 10,000 readings. If more than 10,000 readings exist, a message appears indicating that the data has been truncated, and asks whether or not you would like to see more data. If you do, the next 10,000 readings appear. This message recurs for all possible readings. | TFS274231 |
Previously, when you filtered contents in the Trend Chart workspace or the Events section, the To and From boxes in the Date Range section were incorrectly populated. This issue has been resolved. Now the To and From boxes are populated with the date and time from the user’s time zone. |
|
Previously, if you entered an invalid date range (i.e., if the end date was more recent than the start date) in the Events section of the Health Summary page, no error message appeared. This issue has been resolved. | TFS252681 |
Previously, when using the date range filter on the Trend Chart page, the chart returned 10 years of data regardless of the selection you made in the filter control. This issue has been resolved. Now, the data returned matches the time range that you specify in the filter. In addition, when you select Reset in the filter control, the time range is reset to 1 year. | TFS308678 |
Description | Tracking ID |
---|---|
Asset Hierarchy sorting and filtering based on health indicator status, filtering based on health indicator family field values, and filtering based on assets with or without health indicators. |
|
The display of health indicator statuses in Asset Hierarchy. | TFS86796 |
Asset Hierarchy
Description | Tracking ID |
---|---|
Previously, when you rebuilt the Asset Hierarchy, the operation may have exceeded the allowed timeout limit, causing the rebuild to fail. This issue has been resolved. | TFS328512 |
Previously, when you attempted to add more than 500 assets at one time to an asset group, the load failed. This issue has been resolved. | TFS324631 |
Previously, if you selected a tile before the Enter Parameter Values window had fully appeared, an error occurred. This issue has been resolved. Now, you cannot select any tiles until the Enter Parameter Values window has fully appeared. | TFS319144 |
Asset Strategy Implementation (ASI)
Description | Tracking ID |
---|---|
Previously, when you built an SAP plan using the Actions are Operations option, the Description field in the Task List family was updated based on the value in the Asset Name field of the Asset Strategy family although the Asset Name field was no longer used. This issue has been resolved. Now, the Description field in the Task List family is updated based on the Entity ID of the asset. | TFS326772 |
Description | Tracking ID |
---|---|
Creating implementation roles and filtering the WMI tree by each role. | TFS243573 |
Using a link to manage the object list records that are linked to maintenance item records represented by the selected node. | TFS238443 |
The option to exclude child items when copying Work Management Items. | TFS147790 |
Managing asset and action assignments when executing copy/paste operations. | TFS144110 |
Searching in SAP for the standard text value that you want to append to the value in the Long Text field of a Maintenance Item record. | TFS117765 |
Asset Strategy Management (ASM)
Description | Tracking ID |
---|---|
Migrating strategies between databases. |
Asset Strategy Optimization (ASO)
Description | Tracking ID |
---|---|
Optimizing Actions. | TFS112125 |
Bulk Data Form
Description | Tracking ID |
---|---|
Previously, when the Family Is Managed By Product Module property for a family was set to True, the horizontal scroll bar did not operate as expected in the Bulk Data form when you viewed the family and its related records. This issue has been resolved. | TFS323443 |
Previously, if you accessed a Bulk Data Form, then selected a cell in the Site column, and then attempted to save the record or navigate away, an error occurred. This issue has been resolved. | TFS319488 |
Calibration Management
Description | Tracking ID | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The Calibration Data Loader has been enhanced to support the device mapping feature. The following updates have been made to the Calibration Data Loader:
| TFS323696 |
Description | Tracking ID |
---|---|
Previously, when you installed third-party calibration management software, the software used the same GE Device Driver version as GE Digital APM. This issue has been resolved. Now, the Meridium Device Service uses GE Device Driver 1.6.0.0 to prevent third-party calibration management software from using the same GUID and DLL of the device driver used by GE Digital APM. | TFS324142 |
Previously, in V4.3.0.0.0, when you attempted to import data using the Calibration Data Loader, the data did not load. This issue has been resolved. Note: This issue existed only in V4.3.0.0.0. | TFS323696 |
Previously, when you created a Calibration Strategy for an automated calibration, you could not send data to the calibrator if you did not define the new strategy in the following System Code Tables:
This issue has been resolved. Now, when you create a Calibration Strategy for an automated calibration, you do not need to define it in the System Code Tables. | TFS322060 |
Previously, if you did not create a Calibration Strategy for Bemeax CMX calibration software by entering CMX in the Strategy Name field, and then defined the new Calibration Strategy in the System Code Table MI_CALIBRATION_STRATEGIES, you could not send and receive data from the Beamex CMX calibration software. This issue has been resolved. Now, you do not need to create a Calibration Strategy for Beamex CMX calibration software and define it in the System Code Table. | TFS322060 |
Description | Tracking ID |
---|---|
The Calibration Closed check box has been removed from the Calibration datasheet. Now, you can close a Calibration by changing the state from Pending Approval to Approved via the State Management feature. | TFS323102 |
The System Code Table MI_CALIBRATION_STRATEGIES has been deprecated. In the System Code Table MI_CALIBRATION_REFERENCES, the following system codes have been deprecated:
Now, you do not need to define a new Calibration Strategy for automated calibration and Beamex CMX calibration software in the System Code Tables. | TFS322060 |
Description | Tracking ID |
---|---|
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. |
|
Catalog
Description | Tracking ID |
---|---|
Previously, if you saved a Catalog item whose description was longer than 255 characters, an error message indicating that the description exceeded the maximum allowable length appeared; however, after selecting Cancel, the Description field for the Catalog item displayed the excess characters, suggesting that the excess characters had been saved when they had not. This issue has been resolved. Now, after selecting Cancel, the value in the Description field is refreshed to display a maximum of 255 characters. | TFS329182 |
Previously, when you renamed a Catalog item, such as a query, both the old name and the new name appeared in separate rows in the associated list of recently accessed Catalog items, such as the list of queries on the Query page. This issue has been resolved. Now, only the new name for a renamed Catalog item appears in the associated list of recently accessed Catalog items. | TFS321032 |
Previously, on the Save As window, you could not enter more than 100 characters in the Description box, despite the field having a character limit of 255. This issue has been resolved. Now, you can enter up to 255 characters in the Description box on the Save As window. | TFS319132 |
Previously, when saving a file, the default save location was not always the last save location selected, which forced users saving multiple files to modify the save location each time. This issue has been resolved. Now, the default save location is the last location where the user saved a file. If the user has not saved a file, the default location is the personal folder. | TFS318116 |
Configuration Manager
Description | Tracking ID |
---|---|
Previously, members of the MI APMNow Admin Security Group could not access the Site feature of Configuration Manager. This issue has been resolved. | TFS323517 |
Previously, when you selected the Move all button to export all the dashboard content, the dashboard content was not exported and the export log file contained an incorrect message. This issue has been resolved. | TFS323312 |
Previously, when using Internet Explorer to access offline forms, if you cleared the check box for a Boolean field, the corresponding field value was not properly set to false. Because of this, if you then enabled a Boolean check box, the corresponding field value was not set to true. This issue occurred because dependent field behaviors were not functioning properly. This issue has been resolved. | TFS300681 |
Description | Tracking ID |
---|---|
Global number and date format. | TFS160148 |
Global Preferences- Background Colors. | TFS65297 |
Datasets
Description | Tracking ID |
---|---|
Previously, when you exported a dataset to an Excel file, if the dataset included a Date field, the file was created, but the Date column was blank. Also, if the dataset included a Numeric field, the file could not be opened in Excel. These issues have been resolved. | TFS323004 |
Data Loaders
Description | Tracking ID |
---|---|
Previously, when you attempted to load data that contained braces ({}), an error occurred and the data did not load. This issue has been resolved. | TFS327231 |
Previously, when you used the Equipment and Functional Location Data Loader to load a large number of Functional Location records (e.g., 50,000), the process took an excessively long time to complete. This issue has been resolved. Performance when loading a large number of records using the Equipment and Functional Location Data Loader has been significantly improved. | TFS323905 |
Failure Modes and Effects Analysis (FMEA)
Description | Tracking ID |
---|---|
Promoting RCM and FMEA analyses directly to templates. | TFS160858 |
Family Management
Description | Tracking ID |
---|---|
You can now configure a numeric field as a multi-value field. | TFS318448 |
Family Policies and Policy Designer
Description | Tracking ID |
---|---|
When using the Auto-map field values? option in the Edit Entity node, you can now update each specified record with different values. Previously, the values in the last row of the collection containing the new values were used to update all specified records. The exact records that are modified is now determined as follows:
| TFS324981 |
In the Properties window for a Collection Filter node, the following comparison operators are now available:
You can use these operators to filter text data more easily when you are using a Collection Filter node. | TFS318820 |
Foundation
Description | Tracking ID |
---|---|
In a cluster environment, you can now dedicate a virtual machine to run scheduled jobs. | TFS320346 |
Generation Availability Analysis (GAA)
Description | Tracking ID | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following fields and related functionality from the GAA Plant and GAA Unit record:
| TFS229627 | ||||||||||||
The following fields and related functionality from the Performance record:
|
| ||||||||||||
The following families in GAA:
|
| ||||||||||||
The following Security Groups in GAA:
|
|
GE Analytics
Description | Tracking ID |
---|---|
KPIs for GE Analytics. | TFS162791 |
Graphs
Description | Tracking ID |
---|---|
Previously, when selecting a data source for a new Graph from the Catalog using a mobile device, after you selected a value on the Enter Parameters Window, multiple prompts appeared and the selected query did not appear in the Query Path box. This issue has been resolved. Now, the selected query appears as expected. | TFS323861 |
Previously, on the Graph Result page, in the Data Source workspace, if you modified a query or created a new query to populate a pie graph, the query data did not automatically display on that pie graph. To view the changes, you were required to select the Show Data button to see the new content. This issue has been resolved. Now, when you modify or add a query for a pie graph, the contents of that query are displayed on the pie graph as expected. | TFS326732 |
Description | Tracking ID |
---|---|
Exporting to a PDF and printing graphs. | TFS81015 |
Hazards Analysis
Description | Tracking ID |
---|---|
Previously, when you accessed a What-If analysis using the global search, in the Hazards worksheet section of the associated System/Nodes, the What-Ifs, Causes, Consequences, and Safeguards did not appear. This issue occurred because the URL for navigating to the module contained the path to access only a HAZOP Analysis. This issue has been resolved. Now, the URL for navigating to the module contains the path to Hazards Analysis (i.e., What-If or HAZOP) and the records associated with the System/Nodes in a What-If analysis appear in the Hazards worksheet section. | TFS324531 |
Previously, you could modify the values in the IPL Checklist section of a Safeguard although the associated Hazards Analysis was not in the Planning state. This issue has been resolved. | TFS324487 |
Previously, when you accessed System/Node, What-If, Deviation, Cause, Consequence, and Safeguard records using the Record Manager, you could modify the values in these records although the related Hazards Analysis was not in the Planning state. This issue has been resolved. Now, in the Record Manager, you can only view these records; you cannot modify them. | TFS324205 |
Previously, in a What-If Analysis, when you copied a System/Node, the associated What-Ifs, Causes, Consequences, Safeguards, and Risk Assessments were not copied. This issue has been resolved. Now, when you copy a System/Node in a What-If analysis, the associated records are also copied. | TFS322099 |
Inspection Management
Description | Tracking ID |
---|---|
Previously, the Inspection Management Overview page took a long time to load and appeared to stop responding in environments that had numerous records and utilized customized queries. This issue has been resolved. Now, a busy indicator is displayed while the page is loading. | TFS329156 |
Previously, in Inspection Management, if you created a new Security User whose first and last name were the same first and last name as another Security User in the GE Digital APM system, the users’ names were duplicated and you could not distinguish between the two. This issue has been resolved. Now, to provide consistency across drop-down name values, fields in the Inspection Management module that reference Security Users now use the following format: <Last Name>, <First Name> ~ <User Name> (e.g., Smith, Jane ~ jsmith). | TFS327991 |
Previously, when viewing Checklist Inspections in the Inspection Data section, if you selected the Reports button () to access a report, an error occurred. This issue has been resolved. Now, to access an Inspection Report, you can select the More button (), and then select Print on the menu. | TFS327118 |
Previously, if the Inspector, Inspection Supervisor, or Inspection Administrator team member roles were deleted, the Security Users whose roles were deleted were no longer displayed in:
This issue has been resolved. | TFS322928 |
Layers of Protection Analysis (LOPA)
Description | Tracking ID |
---|---|
Previously, when you accessed the records associated with a LOPA using the Record Manager, you could modify the values in these records although the related LOPA was not in the Planning state. This issue has been resolved. Now, in the Record Manager, you can only view these records; you cannot modify them. | TFS325098 |
Life Cycle Cost Analysis (LCC)
Description | Tracking ID |
---|---|
Previously, when you accessed the LCC Overview page, only the USD currency symbol ($) appeared in the charts. This issue has been resolved. Now, no currency symbols appear in the charts. | TFS325164 |
Management of Change (MOC)
Description | Tracking ID |
---|---|
Previously, in the Application Settings for MOC, when you unlinked a Question from a Checklist, the Question was deleted from the database. This issue has been resolved. Now, the Question that you unlink is not deleted from the database. | TFS324195 |
Maps
Description | Tracking ID |
---|---|
Previously, for users assigned to the Everyone Security Group, if you selected Browse on the Maps page and then selected a map, the map that you selected did not appear. This issue occurred because the proper permissions were not attributed to the Everyone User Security Group. This issue has been resolved. | TFS324011 |
Metrics and Scorecards
Description | Tracking ID |
---|---|
A new dimension, Site, has been added to Work History cube that allows the user to filter cube data. | TFS323636 |
Description | Tracking ID |
---|---|
Previously, in a Scorecard, when you filtered the KPIs based on their performance and then updated their measures by selecting the Update Scorecard KPIs button (), the KPIs disappeared. This issue has been resolved. | TFS322006 |
Previously, if the system running the Report Designer had a non-English user culture setting, you could not open a report from the Catalog. This issue has been resolved. | TFS323892 |
Description | Tracking ID |
---|---|
Export/Import of KPI Schedules. | TFS173886 |
Selecting columns to include in a Scorecard. | TFS170641 |
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 |
Policy Designer
Description | Tracking ID |
---|---|
Previously, if you mapped an output from an Entity node to a Comparison node, and Field was selected in the Display list on the Comparison node Properties window, the field caption did not appear on the node in the policy diagram. This issue has been resolved. Now, the field caption appears on the Comparison node. | TSF323821 |
Previously, when changes were made to a policy that contained, or previously contained, an OPC Tag node configured to trigger the policy’s execution, notifications to the PDI Service may not have been updated according to your changes, which may have resulted in the policy being executed unexpectedly, or not being executed when expected. This issue has been resolved. Now, when you make changes to a policy that contains an OPC Tag node, the notifications to the PDI service are updated accordingly, and the policy will be executed when expected. | TSF322998 |
Previously, if the Data Type list was set to Decimal on the Properties window of a Constant, Return, or a Point Value node, if you entered a value containing characters other than numbers or valid radix and decimal separators, the expected notification message did not always appear. This issue has been resolved. Now, if you enter an invalid decimal value, a notification appears indicating that the value needs to be modified. | TFS318909 |
Previously, if the Timestamp section in the Properties window of an Add Value to Health Indicator node contained no value, the AHI Service did not update the status of the Health Indicator when the policy was executed, and there was no indication that an error had occurred. This issue has been resolved. Now, if the Add Value to Health Indicator node does not contain a value in the Timestamp section, the policy execution fails and an error appears in the policy execution log. | TFS312991 |
Previously, for policies that contained an OPC Tag node configured to trigger the execution of the policy, restarting the PDI service caused duplicate policy executions. This issue has been resolved. Policies now execute as expected. Note: Policies containing OPC Tag nodes may also be triggered when the OPC Tag record is synchronized with the process historian and when readings are added or modified. | TFS324133 |
Previously, negative numbers in policy nodes and execution results appeared in scientific format. This issue has been resolved. | TFS321943 |
Previously, if you removed a column from a query that was used in a Collection Filter node, the corresponding field in the Collection Filter Properties window appeared blank. This is expected behavior. However, no errors appeared in this scenario, and the Collection Filter node did not work as expected because no query field was specified. This issue has been resolved. Now, in this scenario, the empty field is outlined in red, and a notification appears, indicating that necessary information is missing. | TFS258794 |
Previously, if you mapped a value of Boolean type to one input of an Add or Subtract node, the other input field was incorrectly set to a Boolean input, and the notification messages were not as expected. This issue has been resolved. Now, in this scenario, you are prompted to select valid inputs for the node type, the input field to which a Boolean value is mapped is highlighted with a red border to indicate that it is not valid, and notification messages appear as expected. | TFS321528 |
Previously, when you attempted to save a policy with name longer than 50 characters, the following generic error message appeared: Failed to save policy. This issue has been resolved. Now, when you attempt to save a policy with a name longer than 50 characters, a more specific error message appears. | TFS288600 |
Process Data Integration
Description | Tracking ID |
---|---|
Previously, the Process Data Integration Service placed messages in queues for modules whether or not they were licensed, which may have resulted in a significant performance impact to your GE Digital APM server. This issue has been resolved. Now, messages are placed only in queues that are used by licensed modules. | TFS320778 |
Production Loss Analysis
Description | Tracking ID |
---|---|
A warning message now appears when you enter a value greater than the planned production value in the Production Data workspace. | TFS317128 |
Description | Tracking ID |
---|---|
Previously, for a user with a European culture setting, after you entered the Plan Start Time and Plan End Time on the Time-based Plan screen for a time-based sequential plan or plan template, the End Time appeared as invalid in the lower grid. This issue has been resolved. | TFS330464 |
Previously, when you added a Production Unit record, the Timezone field incorrectly displayed Russian Standard time as (UTC+4:00). This issue has been resolved. Now, Russian standard time is correctly displayed as (UTC+3:00). | TFS328184 |
Previously, the Planned Production vs Losses chart on the PLA Overview page did not display month and year values when the Category of the Dimension Mapping for the chart was set to MonthWise. This issue has been resolved and the month and year are now displayed in the YYYY.MM format. | TFS327715 |
Previously, when you attempted to import costs from a Production Event with no start date, you could modify the default start date and the costs could not be imported. This issue has been resolved. | TFS327491 |
Previously, if you created a Production Plan from a Plan Template, when you selected Finish, an error occurred. This issue has been resolved. | TFS323925 |
Previously, when you accessed the Asset Hierarchy without the correct Production Loss Analysis Security Group assignments, an error message appeared, indicating that an internal server error occurred. This issue has been resolved. | TFS323916 |
Previously, when you added or deleted a Production Loss in the Production Data workspace, the Unaccounted Loss color indicator did not change. This issue has been resolved. | TFS323152 |
Previously, when you reconciled losses using the Internet Explorer browser, the Impact Code and Event Code boxes displayed the wrong end of the text string, making it difficult to see which option was selected. This issue has been resolved. | TFS321028 |
Queries
Description | Tracking ID |
---|---|
Previously, when you exported a query result set to a file, if the query contained a column whose Include check box was cleared, any columns whose Display check boxes were cleared were incorrectly included in the file. This issue has been resolved. | TFS326489 |
Previously, if you attempted to export a query result set to a file when the Numeric field or Date field contained a hyperlink, an error occurred. This issue has been resolved. | TFS325487 |
Previously, if you attempted to export a query result set to a dataset when the Numeric field contained a hyperlink, an error occurred. This issue has been resolved. | TFS304413 |
Previously, when you exported a query result set to a dataset, if the query was formatted and included a null date value or null numeric value, an error occurred and the dataset was not created. This issue has been resolved. |
|
Previously, if you selected the Formatted and Limit Results to Top check boxes in the Design workspace for a query, then entered a value in the Limit Results to Topbox, and then ran the query, a number of records greater than the entered value appeared in the Results workspace. This issue has been resolved. | TFS323195 |
Previously, when you exported a query result set to a file, if the query included the Top parameter to limit the result set to a subset of records, the file that was created contained all records. This issue has been resolved. |
|
Previously, if a user with a culture setting that formats dates as dd/mm/yyyy attempted to export to an Excel file a query result set containing a date with a day value less than 13, the file was created, but dates with day values less than 13 appeared in the incorrect mm/dd/yyyy format. This issue has been resolved. | TFS322419 |
Previously, if a user with a culture setting that formats dates as dd/mm/yyyy attempted to export to a dataset a query result set containing a date with a day value greater than 12, an error occurred and the dataset was not exported. This issue has been resolved. | TFS300290 |
Previously, if you selected a default value for a date prompt on the Expression Builder window, an error occurred. This issue has been resolved. | TFS312756 |
Previously, if the Query Privilege for a Security User was set to Restricted By Timeout Limit and you ran a query that exceeded the timeout limit, no error message appeared and the query could be saved. This issue has been resolved. Now, if you attempt to save a query that has exceeded the timeout limit, an error message appears, indicating that the query cannot be saved. | TFS305409 |
Previously, if you accessed GE Digital APM via the Internet Explorer browser and had an open page for an Append query, then selected the tab for a different page, and then reselected the tab for the Append query, the Append Query – Target Source window appeared, despite the target source having been selected previously. This issue has been resolved. | TFS301967 |
Previously, when exporting a query result set to a dataset, if you attempted to save the dataset in a way that would overwrite an existing dataset, an error occurred. This issue has been resolved. Now, you can overwrite an existing dataset when exporting a query result set to a dataset. | TFS300249 |
Previously, if you accessed GE Digital APM via the Internet Explorer browser, created a Crosstab query, and then ran the query, an error occurred and values in the Crosstab row were cleared. This issue has been resolved. | TFS294157 |
Recommendations
Description | Tracking ID |
---|---|
To provide consistency across name values, fields in the Recommendation Management module that reference Security Users now use the following format: <Last Name>, <First Name> ~ <User Name> (e.g., Smith, Jane ~ jsmith). | TFS328373 |
Description | Tracking ID |
---|---|
Previously, users with only View permissions for recommendations were able to delete recommendations. This issue has been resolved. Now, users with only View permissions for recommendations cannot delete recommendations. | TFS223878 |
Record Manager
Description | Tracking ID |
---|---|
Previously, if you deleted a large number of records (i.e., 1000 or more records), the system became unresponsive for several minutes. This issue has been resolved. | TFS324112 |
Reliability Analytics
Description | Tracking ID |
---|---|
In System Reliability, the Analysis Summary workspace now contains a Resources section in which you can create, update, and delete resources. | TFS323339 |
Description | Tracking ID |
---|---|
Previously, when you accessed the report for a Production Analysis without a Process Reliability Line, only the cover page appeared. This issue has been resolved. | TFS330649 |
Previously, in the Reliability Automation Rules Builder window, on the Choose an Asset Family screen, when you selected the Show Family Hierarchy icon, an error occurred. This issue has been resolved. | TFS328223 |
Previously, in the Reliability Growth section on the RA Overview page, the Analysis Start Date and Analysis End Date columns were blank for new analyses. This issue has been resolved. | TFS325326 |
Previously, when you modified the Distribution Type of a detail plot on the Probability Distribution page using the Distribution Options button (), you could not modify the data points in the data editor unless you first refreshed the browser tab. This issue has been resolved. | TFS325165 |
Previously, when you accessed the Asset Hierarchy without the correct Reliability Analytics Security Group assignments, an error message appeared, indicating that an internal server error occurred. This issue has been resolved. | TFS323913 |
Previously, when you extrapolated a Reliability Growth Analysis based on continuous operating time (COT) that contains event dates to any date beyond the last event date, an error occurred. This issue has been resolved. | TFS323464 |
Previously, in System Reliability, you could not modify or delete existing resources. This issue has been resolved. The Analysis Summary workspace now contains a Resources section in which you can create, update, and delete resources. | TFS323339 |
Description | Tracking ID |
---|---|
Action optimization in System Reliability Analysis. |
Reliability Centered Maintenance (RCM)
Description | Tracking ID |
---|---|
Promoting RCM and FMEA analyses directly to templates. | TFS160858 |
Reports
Description | Tracking ID |
---|---|
Previously, when you created reports using the Report Designer and then selected the Deploy button, the reports did not deploy. This issue has been resolved. | TFS321813 |
Previously, on mobile or tablet devices, when you downloaded the reports in any format using the Export drop down menu button, an error message appeared. This issue has been resolved. | TFS323935 |
Previously, when you selected a report in the Catalog search results, the report did not appear. This issue has been resolved. | TFS323140 |
Previously, on the Data Source page, if you had provided the application server name in the Data Source Host box, the Report Designer did not list the data source for that application server. This issue has been resolved. | TFS326625 |
Risk Based Inspection (RBI)
Description | Tracking ID |
---|---|
For each family field that is used to calculate an analysis, the user help text now indicates that a value is required to calculate the analysis. | TFS327808 |
Description | Tracking ID |
---|---|
Previously, if you accessed the Corrosion Loop Overview section, then selected an RBI Component whose Source of Calculated Corrosion Rate field was set to Component, and then selected the Manage TML Groups button, an error occurred. This issue has been resolved. | TFS324974 |
Previously, on the Risk Based Inspection Overview page, in the Assets section, if you selected the check box corresponding to an asset, navigated away from the page, and then accessed the page again, the Calculate and Change States buttons were still enabled although the check box was cleared, and you could calculate or change the state of the analyses in the previously selected asset. This issue has been resolved. Now, you must select the check box again to calculate or change the state of analyses in the asset. | TFS323970 |
Description | Tracking ID |
---|---|
Creating a bulk What-If analysis. | TFS73475 |
Description | Tracking ID |
---|---|
If you modify the value in the Source of Calculated Corrosion Rates field in an RBI Component, the values in the following fields in a Criticality Int. Corr. Deg. Mech. Eval. record are now updated automatically to match the corrosion rate of the selected source:
This happens only if the RBI Component is linked to a TML Group, and the associated RBI Criticality Analysis is in Created state. | TFS270992 |
Description | Tracking ID | ||||||
---|---|---|---|---|---|---|---|
Previously, in an RBI PRD Criticality Analysis, the values in the following fields were sometimes calculated incorrectly.
This issue has been resolved. | TFS326761 |
Description | Tracking ID |
---|---|
If you modify the value in the Source of Calculated Corrosion Rates field in an RBI Component, the values in the following fields in an RBI 581 Thinning and Lining Evaluation record are now updated automatically to match the corrosion rate of the selected source:
This happens only if the RBI Component is linked to a TML Group, and the associated RBI 581 Risk Analysis is in Created state. | TFS270992 |
Description | Tracking ID |
---|---|
Previously, the value in the Total POF With Plan field in an RBI Degradation Mechanisms record was used to plot the probability of failure on the default risk matrix. This issue has been resolved. Now, the value in the Total POF – RBI Date field is used to plot the probability of failure. To facilitate this fix, the baseline RBI Risk Matrix Mapping records have been updated. | TFS322997 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, when a user with view-only privileges accessed the Event Diagram workspace and paused the mouse pointer over a node connector, the option to delete the connector appeared. This issue has been resolved. | TFS329648 |
Previously, when you generated a Comprehensive Analysis Report from a Root Cause Analysis whose state was In Progress, the Date Published value generated was 01/01/1001. This issue has been resolved. Now, the Comprehensive Analysis Report Date Published value is blank when the Root Cause Analysis state is In Progress. | TFS325865 |
Previously, when you accessed the Asset Hierarchy without the correct Root Causes Analysis Security Group assignments, an error message appeared, indicating that an internal server error occurred. This issue has been resolved. | TFS323919 |
Previously, a Security User associated with the MI PROACT Administrator or MI PROACT Team Member Security Group who did not have Delete permissions to the RCA Analysis family could not unlink assets from an analysis. This issue has been resolved. | TFS287181 |
Description | Tracking ID |
---|---|
Emailing capability to notify and track changes in an Asset in an RCA. | TFS175610 |
Sending email notifications for alerts configured in RCA for Hypothesis Verifications. | TFS175610 |
Standard APM State Management functionality in RCA. | TFS63432 |
Rounds
Description | Tracking ID |
---|---|
Selecting multiple nodes in the Route 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 |
Rounds Data Collection
Description | Tracking ID |
---|---|
When you attach an image to an Operator Rounds Recommendation while using Rounds Data Collection, the Reference Document record for the image is now linked to the recommendation. This allows you to locate images associated with recommendations more easily. | TFS319957 |
When you select a Lubrication Requirement on a route, the following fields now appear in the Lubrication Requirement Summary section:
| TFS326789 |
Description | Tracking ID |
---|---|
Previously, when you accessed a Route with more than 2 Lubrication Requirements, you could not view checkpoints after the second Lubrication Requirement. This issue has been resolved. In addition, performance when loading a Route has been enhanced. | TFS327169 |
Previously, you could not open Reference Documents when using Rounds Data Collection on a mobile device. This issue has been resolved. | TFS324965 |
Previously, when you accessed a Route with three or more levels that contained an inactive conditional Measurement Location or Lubrication Requirement in the second level, the Route datasheet did not load. This issue has been resolved. | TFS324664 |
Previously, the State column was incorrectly labeled Status in the Recommendations section of the Rounds Data Collection Overview page. This issue has been resolved. | TFS329077 |
Previously, when you took readings on a Route with the Only Incomplete Checkpoints filter applied and closed the Route before marking it done, the readings were not saved. This issue has been resolved. | TFS329379 |
Previously, when you scanned a tag to unlock a measurement location using an Ecom i.roc handheld device with a low frequency reader, the device stopped responding. This issue has been resolved. | TFS323702 |
Previously, when you enabled state functionality and selected the Show States on Datasheets check box in the State Configuration section for the Operator Rounds Recommendation family, the state control menu did not appear on the Recommendation window (i.e., the window that appears when you select a Recommendation ID in the Recommendation section of the Rounds Data Collection Overview page). This issue has been resolved. | TFS313056 |
Rounds Designer
Description | Tracking ID |
---|---|
In the Route Pane, you can select to open a menu that now includes options to expand or collapse all checkpoints. | TFS326038 |
A new field, Do not automatically create health indicator, has been added to the Checkpoint and Checkpoint Template families. If the field is selected, then health indicators will not be created automatically when new checkpoints are created and linked to assets. |
|
You can now enter Route descriptions that are up to 125 characters long. Note: If you are using a Windows Mobile Device, GE Digital recommends that you do not enter Route descriptions longer than 40 characters. | TFS321664 |
When you modify an allowable value, existing Measurement Location and Measurement Location Template records can now be synchronized automatically to match the new allowable values. To facilitate this enhancement:
This feature is inactive by default and can be activated by an administrative user. |
|
A new field, Related Route History Entity Key, has been added to the Reading family. You can use this field to create a query to view a report that combines readings taken on the Route with the Route History record. | TFS327821 |
Description | Tracking ID |
---|---|
Previously, after you assigned users to a Route in Rounds Designer, the User Count column on the Rounds Designer Overview page did not update. This issue has been resolved. | TFS325383 |
Previously, when you added an ML Template Group to a checkpoint Template in a new Route, the contents of the Select Value field did not appear on the second and subsequent conditional nodes. This issue has been resolved. | TFS324809 |
Previously, when a value for the Related Asset ID field was provided in the Measurement Location worksheet, the Rounds Routes Data Loader did not link assets to checkpoints as expected. This issue has been resolved. | TFS324389 |
Previously, due to caching, it may have taken up to 30 minutes before newly created Categories and Allowable Values appeared in the relevant drop-down lists on the Measurement Location and Measurement Location Template datasheets. This issue has been resolved. Now, newly created values appear within 30 seconds. | TFS323717 |
Previously, when you uploaded records using the Rounds Data Loader, the number of records processed was calculated incorrectly. This issue has been resolved. | TFS312039 |
Previously, when you added a new Checkpoint Condition to a Route when a Checkpoint Condition was already selected, an error message appeared, warning you that unsaved changes would be lost. This issue has been resolved. An error message no longer appears in this scenario. | TFS287834 |
Previously, if you attempted to add a Template Group containing more than 100 Measurement Location Templates to a Route, the action timed out, and the Template Group was not added. This issue has been resolved. Now, performance is improved, and you can add a Template Group containing up to 150 Measurement Location Templates. | TFS295365 |
Same Sign-On
Description | Tracking ID |
---|---|
Previously, if a user logged in via SSO refreshed a page in GE Digital APM, the user was logged out. This issue has been resolved. | TFS327469 |
Previously, when using SSO to log in to GE Digital APM, two pages not needed for SSO log in would appear, and selecting an option on the first page would disrupt the log in process. This issue has been resolved. Now, the unneeded pages do not appear when using SSO to log in. | TFS323792 |
Security Manager
Description | Tracking ID |
---|---|
Previously, when you mapped an LDAP field to the MI_HR_BADGE_ID field, the LDAP synchronization process did not update the mapped id fields in Meridium Enterprise APM. This issue has been resolved. | TFS328185 |
SIS Management
Description | Tracking ID |
---|---|
Previously, when you accessed the records associated with an SIL Analysis using the Record Manager, you could modify the values in these records although the related SIL Analysis was not in the Planning state. This issue has been resolved. Now, in the Record Manager, you can only view these records; you cannot modify them. | TFS325097 |
Previously, when you attempted to import a project file from exSILentia and the data in the .exi file satisfied one or more of the following conditions, an error occurred and the data was not imported:
This issue has been resolved. To facilitate this fix, the following changes have been made:
| TFS325009 |
Strategy Macros
Description | Tracking ID |
---|---|
Previously, when you scheduled a strategy macro run, the strategy macro run failed. This issue has been resolved. | TFS329180 |
Systems and Tags
Description | Tracking ID |
---|---|
Previously, when you viewed the reading history for OPC Tag readings in the Systems and Tags page, the grid displayed the oldest reading first. This issue has been resolved. Now, the grid displays the most recent reading first. | TFS321893 |
Previously, when you pointed to the line plotted on the graph in the Trend Chart workspace accessed from the Systems and Tags page, datapoints appeared as undefined. This issue has been resolved. Now, when you point to the line plotted on the graph, datapoints appear with details of the reading. | TFS330075 |
Description | Tracking ID |
---|---|
Viewing trends for multiple OPC Tags simultaneously (i.e., the Process Data Viewer feature in V3). | TFS62299 |
Thickness Monitoring
Description | Tracking ID |
---|---|
The tabs on the top navigation bar when using the Thickness Monitoring module now display page-specific captions to aid in navigation. | TFS327807 |
A new page, TM Quick View, has been added, which you can access using the More () menu on the Analysis Overview page. The TM Quick View page displays a cumulative view of measurements by month and year for all TMLs associated with a specific asset or TML group and its subcomponents. By default, TML measurements within a 10 year range of the current date are shown. | TFS324661 |
Description | Tracking ID |
---|---|
Previously, when using the Bulk Analysis feature in Thickness Monitoring, if validation errors occurred, the process completed but the progress bar on the log never reached 100%. This issue has been resolved. Now, even if validation errors occur, the progress bar reaches 100% and the errors appear in the log. | TFS329533 |
Previously, for users whose culture setting was French, an error occurred when accessing the Thickness Monitoring Overview page, and the page did not load. This issue has been resolved. | TFS327588 |
Previously, when using a datalogger to send measurements to Thickness Monitoring, if your local time zone was behind UTC (e.g., Mexico City: UTC -6), measurements logged with your datalogger device could not be saved to the TML and an error occurred. This issue has been resolved. | TFS327021 |
Previously, when you created a Thickness Measurement Location (TML) under a TML Group rather than directly under the asset, the TML was not shown in the count of TMLs on the Assets page of the Asset Hierarchy. This issue has been resolved. | TFS326657 |
Description | Tracking ID |
---|---|
Corroded Area Measurements. | TFS101752 |
Dataset integration with dataloggers. | TFS83553 |
Color Coding Preferences. | TFS70840 |
Exporting data to Excel via the TM Dataloggers interface. |
Tools
Description | Tracking ID |
---|---|
A new column, Caption, has been added to the Maps, Dashboards, and Graphs pages. In addition to the value in the Name column, the value in the Caption column provides a title or explanation for the items in each row. Text values in the Caption column can be localized. | TFS322960 |