New Features in Historian 2023 R2

AVEVA Operations Control connected experience sign-on support

Historian supports the AVEVA Operations Control connected experience with AVEVA System Platform.

The server must be configured with an advanced license to retrieve data for expressions.

Note that the following still require Windows credentials:

• HTTP communication (HTTPS is required)

• Replication

• SDK connection using Classic Historian (WCF) Windows Communication Foundation.

• Managing Historian with System Management Server

Changes to default Historian communications protocol and ports

The Historian communications protocol has been updated. The port for the new protocol is 32565 by default. The previous port, 32568, is supported as a legacy port for connecting servers that are running older software that doesn’t support the new protocol.

Tier 1 Historians, AppEngines, and Platforms that support the new protocol and use the default 32568 port are updated automatically when the software is updated to the latest version. The local IDAS is also updated automatically. Existing connections that use legacy custom ports will need to be updated manually. External firewalls may need to be updated to allow connections on the new port.

• For a remote IDAS, change the port with the remote IDAS configurator.

• Update replication servers via the OCMC.

• Update application servers that use old ports in the engine definitions in the Galaxy.

Connecting servers that support the new protocol but are still using a custom legacy port will show as using the HCAL (Classic) protocol on the Data Acquisition page. (Note that connecting servers on older software will also use the HCAL (Classic) protocol. This is expected. Older software does not support the new protocol, and should still connect on the legacy port and use the classic protocol.)

If you have connecting servers that support the new protocol but still use the legacy port, the following warning appears once each hour in the Operations Control Logger:

The Historian Client Access Point running on XXX:XXX is an older version using a legacy protocol. Please update the port in the connection definition to point to the new Historian Client Access Point (port 32565 by default).

For more information, see the following sections in the Historian Administrator Guide:

• IDAS Security and Firewalls

• Configuring IDAS on a Remote Node

Tags support multiple languages in Historian Client Web, Historian Client Query, and Historian Client Trend

You can now configure multiple translations for the same tag in Historian Client Web, Historian Client Query, and Historian Client Trend.

The language for these applications will be set automatically based on the operating system or browser language.

HTTPS-based communications

Internal Historian network communication is more secure and easily integrated with HTTP proxies.

Live data via iData

You can view latest historical values as the “live” values on OMI displays.

Alarm grid filter and sort in Historian Client Web

Browser-based alarm history in Historian Client Web supports more filtering and sorting options.

Historian Client Web/Excel integration

Easily transition from Historian Client Web charts to detailed analysis in Excel.

New look for Historian Client Web

The Historian Client Web interface is updated to be more powerful and easier to use.

Export/import Historian Client Web content

Include saved charts in CSV configuration import/export.