AVEVA recently released AVEVA PI OPC UA Server 1.0.0, the initial production-ready release of its OPC UA server for the PI System. The product gives compatible OPC UA clients a standardized method for accessing operational data stored in the PI Data Archive and contextualized asset information organized in Asset Framework.
The server is based on OPC Unified Architecture, the industrial interoperability standard defined by IEC 62541, and supports OPC UA specification version 1.04. Connected applications can browse PI System data, read and write current values, subscribe to value changes, and retrieve historical information through a standard OPC UA connection instead of relying on a PI-specific integration method.
Accessing PI System Data Through OPC UA
AVEVA PI OPC UA Server exposes data from both the PI Data Archive and PI Asset Framework. Compatible clients can browse PI points alongside AF databases, elements, and attributes, providing access to time-series measurements and contextualized asset information through the same OPC UA endpoint.
Clients can poll current values or establish subscriptions that receive value changes from the server. When read/write access is enabled, they can also write values to the PI System, subject to the permissions assigned to the PI OPC UA service account. These permissions determine which PI points and AF objects are available and whether connected clients can only read the exposed information or modify supported values.
Historical Data Access
In addition to current values and subscriptions, AVEVA PI OPC UA Server supports historical data retrieval over a client-specified time range. This capability allows an OPC UA client to retrieve archived operational values or request earlier records when historical information must be loaded into another application.
Clients can also request historical aggregates such as average, minimum, maximum, total, count, range, start, end, percent good, and percent bad. Applications that require summarized information can therefore obtain processed PI data through OPC UA without retrieving every archived value individually.
Security and Access Control
Access to PI System data is controlled through OPC UA certificates and the permissions assigned within the PI System. AVEVA PI OPC UA Server supports X.509 certificate authentication and mutual certificate trust between the server and each connected client, while encryption can be configured to protect information exchanged across the connection.
Anonymous authentication is available but disabled by default, and username-and-password authentication is not supported. Administrators can configure access as read-only or read/write, although the PI OPC UA service account must also have the required permissions for the PI Data Archive points and Asset Framework data being exposed.
Configuration and Deployment Considerations
AVEVA PI OPC UA Server can expose multiple PI Systems registered in the Known Servers Table, with administrators able to include every listed system or select only those required by OPC UA clients. AVEVA recommends selecting only the necessary PI Servers so that OPC UA access remains limited to the intended systems.
Version 1.0.0 supports AVEVA PI Server 2024 R2 and PI Server 2018 SP3 Patch 8 and can be installed on Windows Server 2016, 2019, 2022, or 2025. AVEVA recommends installing the OPC UA server separately from the PI Data Archive computer because competition for system resources could affect the performance of both products. The service account used by the server must also have the appropriate PI Data Archive and Asset Framework permissions for the required data.
Current Limitations and Product Considerations
AVEVA PI OPC UA Server 1.0.0 does not support OPC UA Methods, which enable client-triggered function execution on the server, or Alarms and Conditions, which provide event-based notifications and alarm management. AVEVA Technical Support has also confirmed that Event Frames are not available through the server and that the product does not include built-in failover, which should be considered when defining availability requirements.
Deployment testing should represent the intended PI System environment, including the number of PI points and AF attributes exposed, concurrent client demand, data volume, update frequency, subscription activity, and historical retrieval workload.
How MetaFactor Can Help
MetaFactor can support the planning and deployment of AVEVA PI OPC UA Server by reviewing system compatibility, installing and configuring the product, establishing certificate trust, assigning service-account permissions, defining read and write access, connecting OPC UA clients, and validating current, subscribed, and historical data access. Contact us to discuss how the new OPC UA server can be integrated with your PI System environment.