Skip to Main Content
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.

Status No status
Product PI Interfaces
Categories Other Interfaces
Created by Guest
Created on Aug 17, 2022

Create a migration path for AMI Interfaces when PI Server is moved to a new machine/hostname

Currently, AMI Interfaces require a rebuild of the AMI cache files when the PI Server is migrated to a new machine/hostname (Although to clarify if the hostname does not change during the PI Server migration the cache does not need to be rebuilt). This is undesirable for large AMI implementations as rebuilding the cache files can be a time consuming process. It is requested that AMI Interfaces should be able to handle PI Server migrations with new hostnames without rebuilding the AMI cache files
  • Attach files