What's New in Historian 2023

Description Tracking ID
Configuration Hub Enhancements

Configuration Hub provides a better user experience using an IDE model to manage systems, bringing in consistency across the portfolio to manage the configuration and administration of multiple products.

All of the administrative features are now available in Configuration Hub, which is more user-friendly. You can now perform the following tasks as well:
  • Configure Historian systems and servers, collectors, tags, data stores, and archives.
  • Perform calculations.
  • Achieve high availability of systems (data replication or failover of disaster recovery sites)
  • Achieve high availability of collectors.
  • Configure offline collectors to specify the list of tags, tag properties, collector interface properties, and so on (without the need to manually update the XML configuration file).
  • Manage alarms and events data, along with creating an alarm.
  • Access activity logs.
  • Visualize data by unleashing the data extraction capabilities of Historian and using the various sample modes, query modifiers, and filter conditions.
  • Configure the advanced options of systems, collectors, and data stores.
  • Access Configuration Hub in Chinese.
For more information, refer to Configuration Hub.
 F64161

MQTT Collector Enhancements

  • Enhanced Security: To enhance security while connecting an MQTT broker and an MQTT collector, you can now use authentication based on any of the following options:
    • Username and password
    • Certificate
    You must first set these parameters in the MQTT broker, and then provide the same values while creating an MQTT collector.
  • MQTT 5 Support: In addition to MQTT 3.1.1, Historian is now supported on MQTT 5, which provides additional features such as session/message expiry interval and reason code.
  • Sparkplug B V1.0 Support: In addition to the KairosDB format, you can now collect data in the Sparkplug B v1.0 format.
  • Quality of Service (QoS) Levels: You can choose among the QoS levels 0, 1, and 2 that you want to use while collecting data from an MQTT broker.
  • Data Loss Prevention: When an MQTT broker and an MQTT collector are reconnected, you can specify whether you want to use the old session instead of creating a new one. This will ensure that there is no loss of data.
  • Session Expiry Timeout: You can specify the timeout interval for connection between an MQTT broker and an MQTT collector. When you do so, data collected before reconnecting is stored by the MQTT broker. If the MQTT broker and the collector are reconnected before the session timeout, the data is collected; otherwise, it is discarded.

For instructions on setting these parameters, refer to Add and Configure an MQTT Collector.

F65029

HAB Collector Enhancements

Using Configuration Hub, in addition to adding a HAB collector instance, you can now perform the following tasks using the UI (without the need to manually edit the xml files):
  • Configure the tags and alarms.
  • Approve tag changes.
For instructions, refer to Add and Configure a HAB Collector.
Also, the HAB collector can now collect data from GENMOM and NETMOM databases, which are databases supported by Habitat. To facilitate this enhancement, the following changes have been made:
  • You can now set multiple values in the TagTemplate parameter.
  • The timestamp and quality values are now optional. This is to accommodate Habitat databases that do not use these fields.
  • You can now provide the MRID, composite key, and tag description values when configuring tags. If, however, you do not have the MRID, you can use the composite key.
In addition to alarms, you can now set a tag prefix for tags as well. In both the cases, you can now set the tag prefix at the collection definition level instead of at the collector level. This helps you identify tags based on the collection definition.

For alarms, previously, tags from only the CIRCLG record type were supported. Now, you can specify tags from all the record types.

For information on configuring these parameters, refer to Configure the HAB Collector for Tags and Configure the HAB Collector for Alarms.

 F63932
Data Replication or Failover of Disaster Recovery Sites

You can set up a mirror of the Historian server in a network different from that of your organization. When you do so, any tag/data update requests to the Historian server can be routed to the public/IT network instead of your organization's network.

For more information, refer to Set Up a Mirror of Mirror .

 F65763
Extended Quality in Data Attributes

SCADA applications such as Habitat support data samples with several quality types. To support such SCADA applications, Historian is now enhanced to store up to 128-bit quality types, which are stored in data attributes. These attributes are extended qualities that you can store more than the regular qualities and sub qualities such as good and bad.

In addition to regular qualities, the HAB collector collects extended qualities such as replaced, suspect, garbage, old, and so on. You can use these attributes using REST APIs as well as Configuration Hub.

 F65699

eDNA Data Extraction

Using the Historian Extract, Transform, and Load (ETL) tools, you can now extract data from an eDNA server as well.

Advantages:
  • You can transfer data using a periodic file-transfer mechanism where a steady network connection is not possible or cost-effective.
  • You can collect both historical and current data.
  • You can create the tag file automatically.
  • You can use a custom data type for tags.
  • You can map the sub-quality values stored in a SCADA system with those in Historian.

For more information, refer to About Extracting Data from an eDNA Server.

 F65818
REST API Calls for Alarms and Events Data
You can now use REST APIs to perform the following tasks:
  • Fetch a list of alarms and events
  • Create alarms
  • Backup and restore alarms
  • Delete alarms
 F60770
Delta Calculation Modes in Excel Add-in
You can now use the following calculation modes in Excel Add-in for Historian to return the delta of values over a time interval:
F65827

Support for Mutual TLS (MTLS) Protocol for Enhanced Security

In Historian 2023, certificate-based security was implemented to strengthen the authentication mechanism and build trusted connections among the core Historian services. The Mutual Transport Layer Security (MTLS) protocol is used to build trusted connections among the core Historian services.

Core Historian services include the Data Archiver, the Client Manager, the Configuration Manager, and the Diagnostic Manager. The MTLS feature is enabled by default.

Important: When you install Historian, you are presented with three install types: Historian Single Server, Historian Mirror Primary Server, and Historian Distributed/Mirror Node. The MTLS protocol and certificate-based security is enabled by default for all install types. If you are installing a Historian Single Server or the Historian Mirror Primary Server, the security settings for the certificates will be automatically configured for you by the installer. If you are installing a Historian Distributed/Mirror Node, you must configure the security settings manually after installation.
CreateRootCertificate.exe and MTLSCertificatesInstall.exe are the two binaries used for manually generating the certificates from the command-line.

For more details, refer to the Post Installation Steps for Configuring Certificate-based Security section in the Getting Started guide, or in the MTLS Security Enabling Guide.pdf document found in your Historian product install folder: <Install drive>:\Program Files\Proficy\Proficy Historian\MTLS.

 N/A
Deprecation of the UAA Config Tool

The UAA Config tool (file name: uaa_config_tool) is no longer available. You can now set up authentication using Proficy Authentication.

 N/A