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™ PI Server
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Provide options to connect PI Analysis service either to Primary or Any collective members

As a PI server Administrator I would like to have a way to decide the PI DA collective member Analysis server should connect. This will allow us to manage better the load on PI DA
  • ADMIN RESPONSE
    Aug 20, 2022
    Changing status. Addition clarifications on use case - user wants to be able to designate a specific PI Collective member for retrieving the inputs for analyses, but write back the results using BufSS to fan the results to all collective members. This is currently not possible.
  • Attach files
  • GaryYegiazaryan
    Apr 20, 2026

    The PI analysis service is hardcoded to only connect to the primary collective member regardless of if you configure the AFSDK to prefer the primary. The reason being is that the analysis service needs to be able to create PI points. This means that if your primary collective member is not available, then your calculations will fail. We have a userbase that uses the output of analytic calculations for real-time monitoring. They are effectively blind when we perform any patching or if there is a network interruption between the analysis service and the primary collective member.

    The analysis service should be able to read data from a secondary and create points on the primary as two separate processes. While the primary is not available, then the analysis service should queue those points for creation.

    https://softwaresupportsp.aveva.com/en-US/knowledge/details/000092545?lang=en_US

    Reply
  • Guest
    Aug 20, 2022
    PI Analysis Service connects directly to the Data Archive via the AF SDK residing on the same machine as PI Analysis Service. As with all clients connecting to a PI Collective, the connection behavior is governed by the collective connection priority and preference. On your machine with PI Analysis Service, you can use PI System Explorer -> Connections -> Right click on the PI Collective and select the member that you want to connect to, or simply start up the application "About PI SDK" and make the configuration there. Since this is existing behavior, I'm going to close this suggestion. If you need further instructions, please contact tech support and they would be able to help you.
    Reply
  • peheuvel
    Aug 20, 2022
    Within Shell we have that many calculations which results that load balancing is required to avoid too many skips or delayed calculations. Please share with us an approach how this can be managed with PI-AF Analytics.
    Reply