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

CONNECT to PI Agent

CONNECT to PI minimum system requirements

  • Last UpdatedJun 12, 2025
  • 2 minute read

The following table lists the system requirements of CONNECT to PI.

System component

Requirement

PI Server

  • AVEVA PI Server 2018 SP3 Patch 3 or later is recommended
    AVEVA PI Server 2023 or later is required if using OIDC authentication

PI Web API

  • PI Web API 2023 SP1 or later

Operating system

  • Windows 10, Windows 11, Windows Server 2019, or Windows Server 2022
    CORE editions of the Windows Server operating systems are supported only with silent installations.

  • Processor: 1 gigahertz (GHz) or faster compatible processor or System on a Chip (SoC)

  • RAM: 4GB

  • Hard drive space: 32GB or larger

Network

  • An Internet connection that allows locally-initiated connections to CONNECT data services port 443.

  • If the agent is installed on a computer other than the PI Web API, a network connection that allows locally-initiated connections into the PI Web API on its configured listener port (443 by default).

  • Internet connectivity of at least 10 Mbps.

Administrator privileges

Privileges

Requirement

Installation privileges

To install a CONNECT to PI Agent, you must be an administrator on the agent host computer.

Configuration privileges

To configure a CONNECT to PI Agent after the installation is complete, you must have the Tenant Administrator role in CONNECT data services.

Ensure write access to the PI Server

The CONNECT to PI Agent uses PI Web API to write data to the PI Server. The account used for PI Web API must have permissions to create AF elements, element templates, and PI points in the PI Server.

Open firewall port for communication to CONNECT to PI

Port 443 must be opened for https communication to the CONNECT to PI gateway. The URL used for https communication depends on the namespace to which the agent is communicating, as indicated in the following table.

Region

URL

West US

uswe.datahub.connect.aveva.com

Northern Europe

euno.datahub.connect.aveva.com

East Australia

auea.datahub.connect.aveva.com

Although each of the above URLs currently corresponds to a public static IP address, we recommend you use the URL rather than the IP address in firewall rules. If required, you can determine the IP address by pinging the URL.

In This Topic
TitleResults for “How to create a CRG?”Also Available in