Historian Agent

Historian Agent enables System Platform, Plant SCADA, InTouch, Edge HMI, and any other product that can supply data to AVEVA Historian via PCS, SuiteLink, DDE, and other generic data sources to transfer process data and assets from historized tags to CONNECT data services. It currently supports Historian 2020 R2 and newer, so these versions can transfer data to the scalable, secure, and connected data management ecosystem that CONNECT data services provide.

Historian Agent architecture

The diagram below shows the flow of data when using Historian Agent.

Historian Agent, subscribes to the tags of the on-premise Historian, then seamlessly publishes the data to CONNECT data services. The transfer takes place over an encrypted HTTPS channel.

Historian Agent sends health and diagnostics data to CONNECT data services, which is available as Sequential Data Store (SDS) stream data.

Historian Agent can support streaming up to 30,000 tags to CONNECT data services. It can sustain a continuously updated stream of up to 15,000 tags per second, and a burst of up to 30,000 tags per second for 2-3 seconds.

The agent must be on the same computer as the Historian Server, and needs internet access to CONNECT data services. The source of historized tags (such as the deployed galaxy, the Plant SCADA server, or other source) can be a separate computer.

Limitations of using CONNECT data services as a replication server

• Forward-slash is not supported in replicated destination tag names.

• The following set of characters are supported in replicated destination tag names, however they will be replaced by ASCII codes in CONNECT data services: * ? ; {{ }} [ ] | \\ ` ' \"

• When replicating to CONNECT data services, if multiple assets in Application Server have the same contained name, use different contained names for those assets. If the contained name is created in App Server before replication, the destination tag name should use the contained name instead of the object name.

• CONNECT data services supports Asset IDs (the combination of asset name, hierarchy position, and tag name) of up to 250 characters. Asset IDs of more than 250 characters may result in incorrect metadata.

• Existing tags in CONNECT data services, as well as the hierarchy in Visualization, can only be updated or deleted manually.

• If you update the tag type of a replicated tag, the tag must be re-added to the replication list.

Historian Agent best practices

• For heavy workloads, install Historian and Historian Agent on a host computer that is separate from the source of the historized tags.