Understand destination options

AVEVA PI System Connector 3 (PSC3) supports two destination types for delivering replicated AF and PI Data Archive information: PI System and Broker. Your selection determines how data moves through the network and what infrastructure is required to support that flow.

Select the appropriate destination as the first step in planning your deployment. Each option is designed for a different set of network conditions, security requirements, and architectural goals.

PI System

A PI System destination allows PSC3 to send data directly to the destination AF Server and PI Data Archive without using intermediary components. This approach creates the most direct data path between the source and destination systems.

Direct delivery is typically used in environment where:

• The source and destination PI Systems reside on the same network or have unrestricted connectivity.

• The environment does not include demilitarized zone boundaries (DMZ) or routing layers.

  Note: A DMZ is a secure middle layer that lets data flow between different network areas, but keeps direct access to the internal PI System blocked.

• You want a simple deployment model.

Because the connector writes directly to the destination, this option offers the most streamlined data path and requires minimal additional configuration beyond identifying the PI System endpoints.

Note: When the connector writes directly to a destination PI Server, it acts as both connector and broker. This leads to reduced performance compared to a standard Connector → Broker → Destination PI System setup. AVEVA recommends to limit usage of this deployment option to small or medium PI Systems. Refer to the Topology 1 and Topology 2 sections of the AVEVA™ PI System Topologies for PI Server for additional details to help determine which topology is best suited for you.

Broker

A Broker destination introduces an intermediary routing point between PSC3 and the destination PI System. The broker receives replicated data from PSC3 and forwards it to a PI System or to another broker in the delivery chain

Broker destinations are designed for environments where:

• Data must pass through one or more DMZs or segmented network zones.

• Multi-hop routing is required across enterprise tiers.

• Additional isolation, flow-control behavior, or secure boundary enforcement is needed.

• Maximizing PI System Connector performance is a priority.

A Broker provides a controlled, structured handoff between network areas and enables deployments that span complex enterprise architectures.

PSC3 supports chaining up to three Brokers, allowing you to move data across multiple network layers while maintaining structured, reliable delivery.

Note: While PSC3 can connect more than three brokers in a chain, AVEVA recommends limiting broker chains to a maximum of three brokers to reduce the risk of latency and performance degradation.

Typical supported configurations include:

Connector → Broker → Destination PI System

Connector → Broker → Broker → Destination PI System

Connector → Broker → Broker → Broker → Destination PI System

A connector can publish directly to a Broker or route data through multiple Brokers before final delivery to the PI System.