AVEVA / AVEVA OPC Server

Source: AVEVA Official Website
(https://www.aveva.com/)

The AVEVA OPC server you need depends on where your data resides. System Platform provides an OPC UA service for accessing Application Server data. AVEVA PI OPC UA Server provides OPC UA access to PI Server data. For projects in India, start by identifying which system holds the data your external application needs.

The sections below compare these two options and cover configuration and purchasing. If you need to collect data directly from PLCs, identify the equipment communication components separately from the service that exposes existing AVEVA data.

What to Check Before Choosing a Server

• Match the server to the source system: Application Server or PI Server.
• Separate equipment data collection from access to data already held in an AVEVA application.
• Check that your installed release supports the client operations you need.
• Discuss evaluation arrangements, implementation in India, and ongoing support before purchasing.

Which AVEVA OPC UA server do you need?

Identify the data source and destination first. Reading data from an AVEVA system and collecting data into it require different components, even when both connections use OPC UA.

For equipment data collection, give the implementation team the controller model, firmware, available protocol, and destination application. They will need these details to check compatibility. An OPC UA endpoint that publishes application data does not, by itself, confirm support for specific PLC models.

How external applications can access AVEVA data

Source: AVEVA Official Website
(https://www.aveva.com/en/products/aveva-pi-server/)

Access Application Server data
from an external application

The System Platform OPC UA service gives OPC UA clients access to Application Server data without a Galaxy Browser, gateway, or additional protocol translation mechanism for that connection. A third-party client can browse the available namespace and access runtime attributes within its configured permissions.

If your plant already runs Application Server, use this connection to share application data with another OPC UA-capable system. Select the attributes the receiving client needs, then test its access. This connection does not require a separate translation layer.

Use existing PI data
in OPC UA applications

AVEVA PI Server stores operational data and organizes it with asset context. AVEVA PI OPC UA Server gives external OPC UA applications access to that existing PI data.

An external application may, for example, need measurements already managed in PI. Accessing those measurements avoids collecting the same signals again from plant equipment. Specify the information and update behaviour the application needs before choosing the interface, then check the supported access functions listed below.

Which sites should consider
AVEVA OPC UA connectivity?

Plants already running System Platform

Consider the System Platform OPC UA service if the information you need is already available as Application Server objects and attributes. System Platform uses reusable asset models and templates. Identify the application attributes the receiving system needs as well as the underlying equipment signals.

Record your installed release, runtime nodes, and destination client before planning the connection so the implementation team can assess it against your existing architecture.

Companies already using PI Server

Consider PI OPC UA Server if an external OPC UA application needs information already managed in PI. Test it with representative assets and measurements from your installation. Set acceptance criteria around what the receiving application must do.

For an Indian project spanning several facilities, identify the site that owns the source data and the team that will operate the connection. Choose the starting point based on your existing software and required data path; location alone does not establish product suitability.

If you need to connect equipment from several vendors, compare OPC server products against your controllers and integration requirements. The vendor overview below links to other products you can evaluate.

Specifications
of AVEVA OPC UA server options

Supported devices
and connection targets

Each server exposes data from its source application. For Application Server, check that the required objects are deployed and that the client can access their attributes. According to the cited documentation, an undeployed Galaxy allows object browsing but not attribute browsing.

Check the upstream communication components separately for equipment connectivity. Access to application attributes does not confirm direct driver support for a particular PLC.

Implementation requirements
and pricing

Ask for a quotation that specifies the OPC UA component, compatible host products, and required deployment environment. Give the supplier your proposed client count and data volume, along with update requirements and support responsibilities.

AVEVA's PI Server product page describes subscription purchasing through PI Data Infrastructure and AVEVA Flex credits. Confirm the separate entitlement requirements for PI OPC UA Server; the PI Server purchasing information does not establish whether that component is included.

How do you configure the System Platform
OPC UA service?

Configure and deploy the service in the System Platform IDE, then test the connection from your intended client. The steps below follow the cited Application Server documentation. Check menu names and requirements against your installed release.

1. Configure the service: Open Galaxy > Configure > System > Services and check out the OPC UA service instance.
2. Set the endpoint port: The documented default is 48031. Additional instances require unique ports.
3. Set encryption and access rules: Configure the client to match the server's communication settings.
4. Assign and deploy: Select the runtime node, check in the service, and deploy it.
5. Configure network access and certificates: Complete the runtime-node firewall and client/server certificate configuration.
6. Test the required operations: Connect with the intended account, browse the namespace, and verify the required attribute access.

Control production access
and attribute changes

AVEVA recommends encrypted communication and disabling anonymous client connections in production. Write access requires both the appropriate service setting and permission in the user's Galaxy security role. Enabling the write option alone does not let every authenticated user change every attribute.

Application certificates and user authentication have different purposes. The cited runtime-access documentation states that this Application Server release does not support OPC UA login by certificate. Check the System Platform service's authentication requirements separately from those for PI OPC UA Server.

Is an AVEVA OPC server
trial or demo available?

In an official administrator response dated March 31, 2026, AVEVA confirmed that PI OPC UA Server had been released and was available for download through the Support Portal. Ask AVEVA about download access and the evaluation entitlement your project requires.

For the System Platform OPC UA service, request a demonstration or evaluation using the relevant System Platform installation. The reviewed public sources do not confirm a standard free trial period for either option.

Test the receiving application with representative data at the required update rates. Verify each operation your project needs. For procurement in India, agree who will handle installation and acceptance testing, and who will provide support after deployment.

Manufacturer information
and India contacts

AVEVA develops industrial software, including System Platform and PI Server, and is part of the Schneider Electric group. Its official locations page lists offices in Bengaluru, Hyderabad, and Mumbai. Ask AVEVA which team handles your chosen product and project.