AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ Adapters
Categories AVEVA Adapter Configuration Utility
Created by Álvaro Flor Catalán
Created on Sep 10, 2026

RELATED IDEAS

Support for Multi-Host and Remote Adapter Management within AVEVA Adapter Configuration Utility

We would request the ability to register, monitor, and configure remote AVEVA Adapters (installed on different physical or virtual machines) from a single, centralized instance of the AVEVA Adapter Configuration Utility in local on-premises OT environments.

Our organization currently manages a large-scale architecture consisting of 20+ AVEVA PI Adapters deployed across multiple remote production plants (OT networks). Due to strict corporate cybersecurity policies and compliance regulations, these industrial networks are completely isolated from the internet, making cloud-based orchestration tools like CONNECT or AVEVA Edge Management a non-viable option for our infrastructure.Current Pain Points:

  1. No Native On-Premises Centralization: The current AVEVA Adapter Configuration Utility strictly limits discovery and management to the local host (localhost), forcing us to either install the utility individually on 20+ servers or build custom automated workarounds.

  2. Operational Overhead: Managing configuration files (Datasource, Dataselection, Schedules) distributed across multiple servers without a central local UI introduces significant maintenance overhead and increases the risk of human error during manual deployments.

  3. Reliance on Third-Party Tools: To manage our deployment efficiently from a centralized jump server, we have been forced to build and rely on custom REST API collections (e.g., Postman) to push configuration payloads to individual adapter IP addresses.

Requested Functionality / Solution Blueprint:
We request a feature update to the AVEVA Adapter Configuration Utility that allows users to:

  • Add Remote Targets: Manually register remote AVEVA Adapters by specifying their Hostname/IP address and API port (e.g., 5590) within the utility's settings.

  • Central Navigation Tree: Implement an organized navigation pane inside the UI where administrators can view all registered remote hosts and switch between them smoothly.

  • Bulk Configuration Templates: A mechanism to push standard configuration baselines (such as common Logging settings or Schedules) to multiple selected adapters simultaneously.

Expected Value / Benefit:
Implementing this feature will dramatically enhance the value of the Adapter Configuration Utility for large enterprise customers with isolated, on-premises OT infrastructures. It will standardize adapter lifecycle management, reduce engineering configuration hours, and eliminate the need for custom administrative scripts.

  • Attach files