What's New in GENESIS Version 11 Update 2 (11.02)

This release includes the following new features and enhancements.

Licensing

Reference ID

Description

14504
14688
15689
17508

A license sidebar has been added to GraphWorX and Workbench so that you can easily monitor your license usage and status. To open or close the license sidebar, click the License button on the right side of the status bar. If there are license violations, a badge with the number of license categories that have been violated is displayed on the License button.

The license sidebar has three sections:

Info—Lists the server name and license tier.
Tags—Lists the number of tags that are in use.
Options—Consists of 7 sections that correspond to the license (or feature) categories.

The color of a category indicates its status. In GENESIS version 11, license violation severity changes depend on the time or on the number of violated tags.

The following table describes each status. For more information about a license status, open the License Monitor.

License Status	Status Color	Description
Not enabled	No border or background	The feature isn't being used.
Licensed and in use	Green border and background	The license is being actively used.
Warning	Yellow border and background	When a license has been violated, a warning is immediately displayed.* If you immediately stop using the feature, the warning goes away.
Error	Red border and background	If you continue using the feature for more than 2 days, the status changes to an error.* If you immediately stop using the feature, the error will become a warning after 1.5 days. The warning will return to normal after another day.
Severe error	Bright red background and white text	If you continue using the feature for more than 5 days, the status changes to a severe error.* If you immediately stop using the feature, the severe error will immediately become an error. The error will become a warning after 1.5 days. The warning will return to normal after another day.

* A message box also appears at the top of the license sidebar with more detail about the warning or error status.

Node Status

The following list describes node violations.

When a node isn't connected to the base node, a warning is immediately displayed.
- The warning will change to an error after 4 days (it's slower with a lost connection).
- The error will change to a severe error after 10 days (it's slower with a lost connection).
- The error will return to normal once the node is connected to the base node.
When two or more nodes that have the same product registration number (P Number) are connected to the base node, a warning is immediately displayed.
- The warning will change to an error after 2 days.
- The error will change to a severe error after 5 days.
- When the duplicated node is disconnected from the base node, the error will return to normal after approximately 2 hours.

17246

The title bar color changes to red when any portion of a GENESIS license has reached the Critical Error stage due to repeated license violations. The title bar caption also displays a "License Exceeded" message.

16964

The feature, FrameWorX - Reverse Proxy, has been renamed FrameWorX - Reverse Communication in the License Monitor.

17565

The feature, Data Historian - SPC, is enabled in the License Monitor when GENESIS is licensed with the Analysis option.

Common and Platform Services

Reference ID	Description
13131	The order of the columns for simulated data sets, which are the data set tags that start with srvsim:, has been changed from Index, Value, Timestamp, StatusCode to Timestamp, Value, Index, StatusCode. The new implementation matches the default order expected by Trend Viewer.

Compatibility Analyzer and Upgrade Utility

Reference ID	Description
13123	The Compatibility Analyzer now checks whether a custom database is used in one of the following configurations—Bridging, Reports, Alerts, Alarm Historian, Databases, and Alert and Notifications. When a custom database is identified, you are notified that NETWORK SERVICE access will be granted by the Upgrade Utility.
14237	The Upgrade Utility now checks custom databases configured in the system and makes sure that the NETWORK SERVICE can access them.
14283	The Import and PubDisplay system folders that are specified in Workbench > Project ribbon > File Configuration are now migrated from C:\Program Files\ICONICS\GENESIS64 folder to the C:\ProgramData\ICONICS\11 folder when you upgrade from GENESIS64 version 10 to GENESIS version 11.
15723	The assembly name and the class name for the network point manager have been changed in FwxServer.PointManagers.config. The Upgrade Utility will migrate the configuration from previous versions.

FrameWorX

Reference ID	Description
15276	The Enable OPC UA Interface option has been removed from Platform Services Configuration because it is now redundant. If needed, you can disable the OPC UA interface in the configuration file. Edit C:\ProgramData\ICONICS\11\FwxServer.Network.config. Set OpcUaInterface to false: <!-- Enables/disables OPC UA interface --> <OpcUaInterface>false</OpcUaInterface> Restart the FrameWorX server.
15697 15973	Added support for OPC UA reverse connections with third-party OPC UA servers, including communication via secure endpoints.
15885	Added support for OPC UA reverse connections with third-party OPC UA clients.
16915	The OPC UA Point Manager configuration is now automatically updated when C:\ProgramData\ICONICS\11\FwxServer.OpcUa.config is modified.
17841	The FwxServer.Network.config settings have been modified to exclude Alert Notifications method traces in GenEvent. The change is automatically migrated by the Upgrade Utility.

Installation

Reference ID	Description
13943	In the Configure System utility, you can disable the HTTP protocol for remote connections and only enable the HTTPS protocol.
14131	The Cancel button has been added to the Configure System utility to enable canceling the system configuration tasks in case they are taking too much time.
15725	The ExcludeComponents parameter has been added to the command line options for running the installation in silent mode. It allows you to remove components from the selected workload (type of installation). For example, the following command line results in the Server workload being installed without SQL Server Express: GENESIS_Setup.exe /s Workloads=Server ExcludeComponents=SQLEXPRESS
15753	The installation now detects unsupported Windows operation systems such as the Home and Core editions.
16261	The Autosol Communication Manager (ACM) Importer was added to the installation. It is unselected by default. To install the component, select ACM Importer on the Advanced tab of the installer. If installing in silent mode from the command line, mke sure to list it in the Components parameter. For example: GENESIS_Setup.exe /s Components=Component1,Component2,ACMImporter
17213	The Data Broker workload has been redesigned, and it is now mutually exclusive with the rest of GENESIS. This workload installs only the Data Broker component. If you select another workload or component, the Data Broker workload and component are unselected. The Data Broker is also a replacement for GenBroker in version 10 (but it is part of GENESIS).
17413	In the Configure System utility, you can now configure HTTPS for remote communication with other GENESIS version 11 systems.

Redundancy

Reference ID	Description
14373	Added a new checkbox, Synchronize online status with the parent cluster, to the SubCluster Settings dialog, which is set to false by default.
14508	The configuration panel is now hidden when nothing is selected in My Project > Servers and Redundancy > Unified Redundancy Editor dialog.
14671	You can now resize the left panel in Workbench > My Project > Servers and Redundancy > Unified Redundancy.
17205	In Workbench > My Project > Servers and Redundancy > Unified Redundancy, you can now specify the connection to the base node of the system in a network.

Schedules

Reference ID	Description
16509 16874	The Value Set configuration no longer allows duplicate Value Set Values or Value Set Tags. If a value is duplicated, the following error message is displayed: Detected the same value specified for one or more values of the value set. Duplicate values are not allowed. Please delete or change the duplicate values. Click here to highlight the duplicated value.

Reference ID

Description

16509
16874

The Value Set configuration no longer allows duplicate Value Set Values or Value Set Tags. If a value is duplicated, the following error message is displayed:

Detected the same value specified for one or more values of the value set. Duplicate values are not allowed. Please delete or change the duplicate values. Click here to highlight the duplicated value.

Unified Data Manager

Reference ID	Description
15972 16874	The Value Set configuration no longer allows duplicate Value Set Values or Value Set Tags. If a value is duplicated, the following error message is displayed: Detected the same value specified for one or more values of the value set. Duplicate values are not allowed. Please delete or change the duplicate values. Click here to highlight the duplicated value.

Reference ID

Description

15972
16874

The Value Set configuration no longer allows duplicate Value Set Values or Value Set Tags. If a value is duplicated, the following error message is displayed:

Alarms and Notifications

Connected Field Service

Reference ID	Description
13258	In Connected Field Service templates, {{cfscoreVariable:ListCompletionCount}}now increments if the WorkerAccess block returns no workers. Previously, it reset to 0.
15986 17242	An audit log message for email, voice, SMS, and WhatsApp notifications has been removed. If this information is required in the audit log, you should consider configuring an Audit Log activity with the contact details of the user who was notified, and the alarm details.

Analytics

Bridging

When Bridging and WebAPI request historical data from Data Historian, a Bad - License Disabled status code is displayed if the requested tags aren't configured in Data Historian by selecting an External Data Access checkbox. This is an intentional change and is working as designed.

There are several External Data Access options in Data Historian.
- External Data Access—Enables access to external historical values. It's located on the General tab on the Tag, Calculated Tag, and Merge Tag screens.
- Allow/Deny External Data Access for all tags—Allows or denies data access for all the tags in the selected folder or subfolder. To access this option, go to My Project > Historical Data > Data Historian >Logged Data, and right-click a folder.
- Allow/Deny External Data Access— Allows or denies data access for the selected tag. To access this option, go to My Project > Historical Data > Data Historian >Logged Data and right-click a tag.
To resolve this issue, select the appropriate External Data Access option for your situation.

Fault Detection

Reference ID	Description
14763	You can now enable logging to an external database. This feature allows you to establish a dedicated SQL Server database, distinct from the Fault Detection/Assets configuration database, for logging fault incidents. To set up a custom logging database connection: Use Microsoft SQL Server Management Studio to create a new database and grant the necessary login and access rights to the NT AUTHORITY/NETWORK SERVICE account. Open Workbench and in Project Explorer, expand Analytics > Fault Detection, and double-click Server Options. The Server Options pane is displayed. On the Fault Incidents Logging tab, select Use a custom database for logging. Double-click Configure connection to open the Connection Settings dialog, select the desired database connection, click Next, and then click Apply to save your changes. For the new settings to take effect, you must restart the Fault Detection run-time service.

Reference ID

Description

14763

You can now enable logging to an external database. This feature allows you to establish a dedicated SQL Server database, distinct from the Fault Detection/Assets configuration database, for logging fault incidents. To set up a custom logging database connection:

Use Microsoft SQL Server Management Studio to create a new database and grant the necessary login and access rights to the NT AUTHORITY/NETWORK SERVICE account.
Open Workbench and in Project Explorer, expand Analytics > Fault Detection, and double-click Server Options. The Server Options pane is displayed.
On the Fault Incidents Logging tab, select Use a custom database for logging.
Double-click Configure connection to open the Connection Settings dialog, select the desired database connection, click Next, and then click Apply to save your changes.
For the new settings to take effect, you must restart the Fault Detection run-time service.

Controls

Map Control

Reference ID	Description
12036	When adding a new Web Map Service (WMS) connection to the Map Control, the provided URL address is now automatically trimmed to remove any URL parameters with a preceding question mark.

Sankey Diagram

Reference ID	Description
14161	The following enhancements have been made in the desktop and HTML versions of the Sankey Diagram control, Node minimum height The node size in a Sankey Diagram might be sub-pixel, resulting in a non-visible node. To address this behavior, Sankey Diagram now exposes a new property, NodeMinimumHeight. It is available as Minimum Height on the NODES tab of the Sankey Diagram configuration. By default, this property is set to 0, which means no minimum size is required (for backward compatibility). Setting this property to an integer value greater than zero (0) results in the node's minimum size being set to this value. The Gain and Loss nodes' minimum size is also affected by the property. The minimum height might be changed by the diagram in case the chart runs out of available space. Node order Sankey Diagram now orders nodes in respective groups where child nodes move up and down to be as close to their parents as possible. The resulting diagram layout should have fewer node-to-node link overlaps. The order of links outputting from a node is not changed by the algorithm.

Reference ID

Description

14161

The following enhancements have been made in the desktop and HTML versions of the Sankey Diagram control,

Node minimum height

The node size in a Sankey Diagram might be sub-pixel, resulting in a non-visible node. To address this behavior, Sankey Diagram now exposes a new property, NodeMinimumHeight. It is available as Minimum Height on the NODES tab of the Sankey Diagram configuration.

By default, this property is set to 0, which means no minimum size is required (for backward compatibility). Setting this property to an integer value greater than zero (0) results in the node's minimum size being set to this value. The Gain and Loss nodes' minimum size is also affected by the property. The minimum height might be changed by the diagram in case the chart runs out of available space.
Node order

Sankey Diagram now orders nodes in respective groups where child nodes move up and down to be as close to their parents as possible. The resulting diagram layout should have fewer node-to-node link overlaps. The order of links outputting from a node is not changed by the algorithm.

Schedule Control

Reference ID	Description
13161	Added the option UseListViewJsonFormat. which is set to false by default. If true, the raw BACnet JSON strings are displayed in the schedule exception list view and calendar list view. You do not see the specially formatted strings that include locale-specific dates. It can be enabled on the Advanced tab of the BACnet Schedule or Calendar view properties.

Table

Reference ID	Description
13649	In the Table control configuration, you can now align the sampling interval to local time using the Align property on the General tab in the Time Range section. This is mostly useful when the data sampling interval is more than 1 hour and needs to be aligned with local time. For example, for a 24-hour sampling interval, the samples are likely aligned to midnight in the local time zone. With the UTC option, which was the original behavior, the sampling interval is aligned to UTC time zone, causing offsets and incorrect calculation of aggregates.

Reference ID

Description

13649

In the Table control configuration, you can now align the sampling interval to local time using the Align property on the General tab in the Time Range section. This is mostly useful when the data sampling interval is more than 1 hour and needs to be aligned with local time. For example, for a 24-hour sampling interval, the samples are likely aligned to midnight in the local time zone. With the UTC option, which was the original behavior, the sampling interval is aligned to UTC time zone, causing offsets and incorrect calculation of aggregates.

Trend Viewer

Reference ID	Description
5875	The Minimum bar size and Sample size mode settings that allow specifying the minimum bar size for a bar plot were added to the Trend Viewer configuration. To access these settings, open the configuration dialog by double-clicking anywhere in the Trend Viewer control, and then click Chart in the tree structure, and go to the Pens tab in the right pane.
13649	In the Trend Viewer configuration, you can now align the sampling interval to local time using the Time Range Alignment property in the Chart settings on the Data tab. This is mostly useful when the data sampling interval is more than 1 hour and needs to be aligned with local time. For example, for a 24-hour sampling interval, the samples are likely aligned to midnight in the local time zone. With the UTC option, which was the original behavior, the sampling interval is aligned to UTC time zone, causing offsets and incorrect calculation of aggregates.
16842	(HTML5) Flick gestures have been removed.

Data Connectivity

BACnet

Reference ID	Description
16354	The Poll Before Subscribing option in the BACnet channel settings has been changed to a checkbox. The setting is available in Workbench in Data Connectivity > BACnet > Channels on the Communication tab of the channel configuration dialog.
16705	The displayValue property is now writable.
17077	Added an option to hide all beta features (Secured Connect and BBMD) in the IcoSetup64.ini file under [BACNETSC\Configuration]. To hide the beta features, change of the option HideBetaFeatures to 1 (true).

OPC UA

Reference ID	Description
13048	The OPC UA Point Manager now retrieves historical aggregates from the OPC UA server and exposes them to the clients. In GraphWorX, you can add a Trend Viewer control and configure the aggregates when subscribing to an OPC UA historical tag.
15984	Improved the performance of the OPC UA point manager when creating a large number of connections. When approximately 10,000 OPC UA connections are created, the CPU usage now drops from 100% to 40%.
16735	The OPC UA Connection setting, Disable Reading Metadata, has been renamed to Fetch Complex Type Information, and the default has been changed from true to false.

Data Historian

Reference ID	Description
11832	There is a new History Reader tab on the Data Historian tag screen that allows you to view the history of any valid Data Historian point.
12956	Statistical Process Control (SPC) functionality has been added as a part of the extension module. When the extension module is enabled via the appropriate dialog (the default value is disabled), the SPC rules subtree appears in the Data Historian tree, and the configuration of SPC tags is allowed.

GraphWorX

Reference ID	Description
9722	Updated the scroll bar style of the Asset Navigator, Trend Viewer, and Table controls,
11138	Removed the Display Button feature from GraphWorX.
11795	You can now enable or disable telemetry in GraphWorX. To do so, select File > Tools > Telemetry Settings.
12451	Added a new option, AccountRateLimiter, in ico.anyglass.parsing.config. When the limit is set to a non-zero value (for example, 3), the per client limiter is used for the login and change password endpoint. We recommend setting this option when database-baked security is in use and the application is accessible to the public.
13364	The Run Script commands, scripting templates, and other features that rely on scripting are now hidden if scripting is disabled.
13567	The Help button at the top right of the GraphWorX screen was removed. The Help is now accessible from the Help tab in the ribbon.
15358	The Add, Absorb, and Remove Transform operations now affect all the selected 2D objects (if applicable).
16383	Improved application mode accent color consistency in the GraphWorX user interface.
17456	(GraphWorX 3D) Optimizations have been made to make the IFC import significantly faster for some types of input models.

HTML5 3D

Reference ID	Description
12522	Improved the color dynamics configuration for objects in the Lights category. The default and the only available preset value for TargetPropertyName of Color Dynamic placed on light objects in 3D Viewport has been changed to Color. The selectable values for other 3D objects remain Material or Back Material.
14645	When hovering over a 3D object that has a pick action on it, the cursor will change to a hand. Note that this change, as well as the change from the hand cursor back to the default one, is not immediate.

Internet of Things

Reference ID	Description
14517	A new decoder for the Mitsubishi FX5-ENET JSON format is available in the IoT Subscriber for the Azure IoT Hub, Azure Event Hub, and MQTT connectors.
15432	New settings for handling memory consumption have been added to the IoT Subscriber service. You can now set limits for the receive and process queues. If the limits are low, the processing may take longer. Other changes to improve processing time have also been made. The following settings have been added to the JSON configuration file. RealTimeMessageCountLoopLimit: A global setting that determines how many real-time messages can be processed in one loop. It's set to 1,000 by default. Higher values may delay other processing, while lower values may slow down message processing. HdaMessageCountLoopLimit: A global setting that determines how many HDA messages can be processed in one loop. It's set to 1,000 by default. The following options for the Azure IoT Hub and Azure Event Hub subscriber connection types are now available in Workbench. In Project Explorer, expand Data Connectivity > Internet of Things > Subscriber Connections. The new settings are located in the new Memory and Performance Settings section. Receive Queue Size Limit —The default setting is 1,024 KB. Process Queue Size Limit —The default setting is 10,240 KB. Enable Advanced Memory Optimization—Less memory is consumed when selected, but processing takes longer than when the setting is disabled. The setting is enabled by default.

Reference ID

Description

14517

A new decoder for the Mitsubishi FX5-ENET JSON format is available in the IoT Subscriber for the Azure IoT Hub, Azure Event Hub, and MQTT connectors.

15432

New settings for handling memory consumption have been added to the IoT Subscriber service. You can now set limits for the receive and process queues. If the limits are low, the processing may take longer. Other changes to improve processing time have also been made.

The following settings have been added to the JSON configuration file.

RealTimeMessageCountLoopLimit: A global setting that determines how many real-time messages can be processed in one loop. It's set to 1,000 by default. Higher values may delay other processing, while lower values may slow down message processing.
HdaMessageCountLoopLimit: A global setting that determines how many HDA messages can be processed in one loop. It's set to 1,000 by default.

The following options for the Azure IoT Hub and Azure Event Hub subscriber connection types are now available in Workbench. In Project Explorer, expand Data Connectivity > Internet of Things > Subscriber Connections. The new settings are located in the new Memory and Performance Settings section.

Receive Queue Size Limit —The default setting is 1,024 KB.
Process Queue Size Limit —The default setting is 10,240 KB.
Enable Advanced Memory Optimization—Less memory is consumed when selected, but processing takes longer than when the setting is disabled. The setting is enabled by default.

Report Editor

Reference ID	Description
2360	The Report Editor is a stand-alone application that you can use to configure reports for GENESIS version 11 using Microsoft Excel, and it is installed separately from GENESIS. Excel 2019 or higher must be installed on the machine before installing the Report Editor. After installing the Report Editor, you can open Excel and collect data coming from GENESIS version 11. You can then import the Excel file into Workbench and use it as a template for scheduled reports.

Reference ID

Description

2360

The Report Editor is a stand-alone application that you can use to configure reports for GENESIS version 11 using Microsoft Excel, and it is installed separately from GENESIS. Excel 2019 or higher must be installed on the machine before installing the Report Editor.

After installing the Report Editor, you can open Excel and collect data coming from GENESIS version 11. You can then import the Excel file into Workbench and use it as a template for scheduled reports.

Workbench

Reference ID	Description
17206	The Workbench Point Manager service IcoConfigService has been renamed to IcoWorkbenchService.