Operations Hub Release Notes

This topic provides a list of product changes in Operations Hub for this release.

Version: 2.0

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

Description Tracking IDs
This release of Operations Hub contains the following features:
  • Enabled OPC UA connectivity for Proficy iFIX, (read/write operations), Proficy CIMPLICITY (read/write operations), and IGS (read operations).
  • Introduced a common browser for the Model Editor, Trend Chart, Query Editor, and Page Designer to browse the Asset Model, Historian, and OPC UA data sources.
  • Implemented enhancements for the trend chart in the web application:
    • Allows to configure color, line style, and width of trend lines
    • Added Lab and Lab to Raw as additional sampling modes
    • Allows plotting of multiple sampling modes for the same Historian tag
    • Specify upper, lower, and target specification limits
    • Increased sample count-up to 8K
    • Re-fetch of data and tag statistics on zoom
  • Allows trending of OPC UA data directly from configured OPC UA servers, in addition to the data from the Asset Model and Historian.
  • Application and Page enhancements in terms of duplicating between applications, specifying a friendly name, etc.
  • Improved and simplified approach towards binding Asset Model, OPC UA and Historian data to widgets.
  • New Date Time picker available for date and time selection.
  • Exposed Breadcrumb context selection to all widgets.
  • Licensing enforcement - Trial version, Historian analysis tier and full version.
  • F49615
  • F49632
  • F49634
  • F49628
  • F51614
  • F49627
  • F53670
  • F49613
  • F54027
Table 2. Known Issues and Limitations

The following known issues and limitations exist.

Description Tracking ID
When you save a favorite in a trend chart, if you include a special character in the name, the error message that appears does not specify the issue. DE123967
In a trend chart, if you add a tag that is identical to the one that is already plotted but the case of the tag name does not match the case of the tag name in Historian, a straight line appears in the trend chart. To resolve this issue, modify the tag name to match the case of the tag name in Historian. DE123833
During Operations Hub installation, when you provide the tenant user ID, the following conditions apply:
  • If you are installing Operations Hub for the first time, do not provide StudioAdmin as the tenant user ID because it is used by Operations Hub.
  • If you want to use a shared UAA to work with Operations Hub, do not provide the user ID of an existing user of the UAA instance. If you do so, the installation fails.
  • If you are installing Operations Hub after uninstalling it without purge, do not provide a tenant user ID that matches any previously used user ID (including any previously used tenant ID). This is because after you uninstall Operations Hub without purge, previous Operations Hub users (along with tenant administrators, their groups, and privilege assignments) still exist in the database.
DE123770
Some widgets, such as a table, do not work as expected when used with a REST query. In particular, features which require additional queries to fetch more data (such as pagination), as well as features limiting data (such as row limits) may not work. DE118883
When you create a data source, you can provide a certificate only in the base-64-encoded format. A DER-encoded certificate is not supported. DE116706
Operations Hub uses Kafka, which generates a large number of logs in the following location: C:\tmp\kafka-logs\. To avoid consuming too much space for these logs, we recommend that you periodically delete the logs, especially if the system has low disk space. N/A
If you encounter intermittent responsiveness issues with the Operations Hub runtime environment when using the Safari browser on your mobile device, it is recommended that you use the Chrome browser instead. DE131011
When adding environment variables to Windows System Variables, be aware that environment variables are case-sensitive. If your environment variables in Operations Hub do not match the case of the ones used by the target Historian Server, the data source will fail when tested. Be sure that you use the same case when configuring data sources in Operations Hub. A data source target in Operations Hub should match the case in the environment variables, as the variables are case-sensitive.

DE130896

Historian REST response time increases exponentially when there are over 30 users logged into Operations Hub accessing an End app that utilizes Historian REST queries. DE134904
When using Safari 13+ on iOS, trend card functionality like adding tags to the trend, favorites, and annotations perform inconsistently. The workaround is to use the Chrome browser on the iPad. DE136597, DE149433
If a Historian data point being trended transitions to a bad quality (such is the case when a collector goes down or loses communications), the trend card displays a flatline for the last known good value. If you experience one or more flatlines in your trends, and all the various requests from the same source, you should check the communication chain for an issue with Historian, a collector, or a SCADA driver, for instance. DE138128
There are currently some page printing issues. For instance, if you have iframe that spills over to a second page, that can cause an issue. DE146462
The uaa-provisioning.log file generates in a new folder if the location path provided during Operations Hub installation contains a space in it. For example, C:\Custom Logs. DE148827
An import of an older app containing the Trend widget will not have the Scroll Percentage property available. As a workaround, when upgrading from Operation Hub 1.7 to 2.0, delete the Trend card and then re-add it to your app. DE140521
When importing an application with plug-ins, if you choose to duplicate instead of replacing the application, some of the bindings may need to be recreated. See Import an Application. DE149914
If the OPC UA test connection fails with a Certificate Uri is Invalid error, it is possible that the URI specified in the UA SDK session call does not match with the URI in the certificate. To resolve this,
  • Modify the ServerConfig.xml file (found at C:\Program Files\GE\Operations hub\BrowseService if Operations Hub was installed with default location) to do the following:
    Replace
    <ServerUri>urn:[NodeName]:proficy:webhmi:dataservices</ServerUri>
    with
    <ServerUri>urn:<machine name in capital letters>:proficy:webhmi:dataservices</ServerUri>
    wherein, the node name must be replaced with the Operations Hub server machine name in capital letters (even if the machine name is in small case or camel case).
  • After modifying the XML file, restart GE Operations Hub UA Browse Service in your Services console.
DE149878, DE149879
If there are several OPC UA data sources in Operations Hub pointing to the same URN, and if one among them is configured incorrectly (for example, an incorrect user name or password), then the data does not flow to the end application. The workaround is to eliminate the data sources with the bad configuration to allow the data to flow. DE149674
When working with Operations hub, you can open a maximum of 5 browser tabs. N/A
Table 3. Fixed Defects

The following fixed defects have been addressed with this version of Operations Hub.

Description Tracking ID
Previously, errors occurred when duplicating a page several times from an application imported to the system. The error occurred sometimes on the fourth or fifth attempt to duplicate the page. This issue has been resolved. DE132571
Previously with queries relation database, 'invalid number' occurred on passing a negative integer value to a stored procedure input parameter. This issue has been resolved. DE141438
Error occurred when creating a new application page or modifying an existing one. To fix this issue, the default Tomcat POST max size has been updated. DE143197 / SF 00890752
Previously, the properties tab for configuring plugins was not functioning as expected. This issue has been resolved. DE141439 / SF 00878135
Previously for the input widget, there were issues with the properties display pane, which made it difficult to apply settings. This issue has been resolved. DE141443 / SF 00878583
During export, an unusual file name was generated for an application that had a name with Japanese characters. This issue is fixed to generate the export file as <AppName>_IQPPackage.zip. DE138649 / SF 00881458
The graph widget’s data download icon was not displaying in the end application at runtime. This has been fixed. DE141440 / SF 00880342
Previously, a live preview for Mobile and Tablet devices appeared at the bottom of the Model Editor when creating or deleting objects. This issue has been resolved. DE121922
Previously, import or export of an application bundle with images failed if the image names contained spaces or non-English characters. This issue has been resolved. DE105597
When not connected to the Internet, there are a couple of icons (the certificate lock icon and view password icon) in the UAA/LDAP tool which may not display. These icons require an Internet to display. N/A
Table 4. Compatibility Matrix

The following products are compatible with Operations Hub.

Product Required Version
Proficy Historian
  • Historian 7.0 with the latest SP
  • Historian 7.1 with the latest SP
  • Historian 7.2 with the latest SIM
  • Historian 8.0
  • Historian 8.1
Note:
  • Operations Hub 2.0 and Historian on the same box is not supported.
  • Historian REST APIs are required for REST integration between Operations Hub and Historian 8.x and above. Historian REST APIs are installed automatically when you install Historian web-based clients.
Proficy Plant Applications
  • Version 8.0, SIM3, for Integrated Process Apps
  • Version 8.1
User Authentication and Authorization (UAA) service Version 2.0
Proficy iFIX 6.0 (read operations), 6.1 (read operations)
Proficy CIMPLICITY 10 (read operations), 11 (read operations)
GE Common Licensing Version 19.2.1725.0