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

PI System Connector 3

Set the destination

  • Last UpdatedMay 20, 2026
  • 4 minute read

When selecting PI System s the destination, the connector establishes a direct connection to the target AF Server and Data Archive, allowing replicated AF objects and PI point data to be written without using a broker. When configuring a direct destination, no broker services or AMQP connections are involved.

Use this option in environments where direct network connectivity is available between the source and destination PI Systems.

Note: Before leaving this page, select Apply Changes to save all changes.

PI System

PI Server

The PI Server field lets you specify the PI Data Archive that the connector will send data to. Enter the server name in your environment so the connector can connect and forward PI point updates without interruption.

  • Select a PI Server from the drop-down menu of available PI Servers.

  • Select to open a pop-up window where new PI Servers can be defined and managed.

  • Select Properties () to manage the properties of the selected PI Server.

Select Connect to create a connection between the connector and the PI Server.

AF Server

AF Server is a required field that indicates where the AF database is located.

  • Select an AF server from the drop-down menu of available AF servers.

  • Select to open a pop-up window where new AF Servers can be defined and managed.

  • Select Properties () to manage the properties of the selected AF Server.

  • Select Connect to create a connection between the PI System Connector and the AF Server. This populates other fields in the UI, such as the AF Database field.

    Note: Each connector supports one destination AF Server and one destination PI Server. To connect to multiple destination AF or PI Servers, a separate instance of AVEVA PI System Connector 3 (PSC3) must be installed on a different machine.

AF Database

This required parameter specifies the destination database where the source database will be replicated.

  • Select an AF database from the drop-down menu of available databases.

  • Select to open a pop-up window where new AF Databases can be defined and managed.

  • Select Properties () to manage the properties of the selected AF Database.

Root Element Path

This optional parameter sets a more precise destination within the selected destination AF database. If you did not configure the Root Element Path, then AF data is stored at the highest level of the AF hierarchy on the destination.

To add a root element path:

  • Select Add to display the Root Element Path pop-up box.

  • Enter the name of the connector and then select a Root Element Path. The Connector Name should match the Connector Name field on the Overview tab.

  • Select a root element path.

    To search for a specific elements, select .

    To browse through the AF hierarchy and select the preferred Root Element Path, select .

  • Select OK to save your root element path.

To edit or remove an existing root path:

Select Edit to modify the Connector Name or the Root Element Path saved in the table.

Select Remove to remove the selected Root Element Path from the table. Without a Root Element Path in the table, AF data will be sent to the highest level of the AF hierarchy of the destination.

Windows Authentication | Open ID Connect

Select between Windows Authentication type or Open ID Connect (OIDC) type authentication.

  • If you select OIDC, the system displays prompts to enter the Client ID and Client Secret. After saving, the Client ID and Client Secret in the PI Identity Model is replaced with the strings in these fields.

  • If no ID or Secret is submitted, the last submitted ID and secret is used for authentication.

  • If no ID or Secret has been submitted and there is no ID or secret stored in PI Identity Model, an error displays.

Global PI Point Prefix

A unique prefix for all PI System Connector 2 PI Points. This field is automatically populated when the user migrates from PI System Connector 2 to PI System Connector 3.