Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Plant SCADA

TABLE OF CONTENTS

Welcome to AVEVA Historian Plant SCADA Connector

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedMar 10, 2025
  • 3 minute read

AVEVA Historian Plant SCADA Connector is a conduit between AVEVA Plant SCADA and the destination you choose -- on-premises AVEVA Historian or cloud-based AVEVA Insight.

AVEVA Historian Plant SCADA Connector forwards alarm events, trend data, and string data from AVEVA Plant SCADA to the destination.

Note: If you've already installed an earlier version of Connector, you'll need to uninstall that version before setting up this version.

The AVEVA Historian Plant SCADA Connector installation requires administrative privileges. To launch the install, right-click PlantSCADAConnector.exe and select Run as administrator.

The Connector's relationship to the other Historian parts

To transfer data from AVEVA Plant SCADA to AVEVA Historian or AVEVA Insight, Connector does the following:

  1. Reads trend, string and digital variables, and alarm tag information from AVEVA Plant SCADA.

  2. Creates corresponding tags in AVEVA Historian or AVEVA Insight, converted to Historian or Insight data types as required.

  3. Reads process value data (analog, discrete, string) and events from AVEVA Plant SCADA.

  4. Writes real-time process value data (analog, discrete, string) and events to AVEVA Historian or AVEVA Insight.

When Connector is active, it forwards current data and any available historical data. This gives you access to relevant data for the current production without having to wait for long term historical data to be forwarded. At initial startup, Connector acquires the latest available sample for every trend tag and alarm event from the last day. After subsequent restart, Connector will forward current data, historical data, and alarm events simultaneously.

Example Topologies

  • AVEVA Historian destination

    This example topology can be installed on a AVEVA Plant SCADA or standalone computer. However it is recommended that Connector is installed on a separate computer than AVEVA Historian. Connector can be installed on a AVEVA Plant SCADA node or on a standalone computer.

    Sample Historian topology showing the connector

    In this example, the system has a redundant pair of AVEVA Plant SCADA servers and two client operator stations.

    When the AVEVA Historian is added to the system, AVEVA Historian Plant SCADA Connector is installed onto a AVEVA Plant SCADA client computer. This allows the connector to leverage the built in trend, string variable, and alarm event redundancy of AVEVA Plant SCADA; as it will forward data from the active trend, IO server, and alarm server.

    If the AVEVA Plant SCADA client with the connector is shutdown, the data forwarding to AVEVA Historian stops and it will automatically resume when the AVEVA Plant SCADA client restarts.

  • AVEVA Insight destination

    In this example, AVEVA Plant SCADA and AVEVA Historian Plant SCADA Connector can be on separate computers connected by a network. Both computers are also connected via internet with AVEVA Insight, and data is copied to AVEVA Insight from AVEVA Plant SCADA.

    Data movement to Insight

  • AVEVA Insight destination via AVEVA Historian

    In this case, AVEVA Plant SCADA copies data to AVEVA Historian. Because AVEVA Insight has been connected to AVEVA Historian as a tier-2 server in this example, the AVEVA Plant SCADA data is also copied to AVEVA Insight.

    Data moving to Insight through Historian