AVEVA™ PI System™ Feedback Portal

Welcome to our new 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™ PI Server
Categories System Management
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Add ability to honor archive list file locations when adding new server to PI HA Collective

When adding a new server to a PI HA Collective, all archive files selected to be included in the initialization are copied and registered with the new server in one defined location in collective manager.  This can create more manual work for organizations who wish to have all servers have similar file structures.  If the primary server has archive files registered across multiple locations, these locations should be honored and attempt to move files to these locations first, then if a drive is not available fall back to the default location.
  • Attach files
  • jerome.boudon
    Reply
    |     Aug 19, 2022
    This feature would be very helpful and would facilitate the synchro process of a secondary server in a collective. Actually, we need to synchro the file in the main archive location, then unregister all the others, move them manually to their final destination on secondary, register all on primary and secondary