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 System Access (PSA)
Categories PI SQL Client
Created by Derek Wong
Created on Aug 23, 2022

RELATED IDEAS

Allow the SDK connection priority for the RTQP Engine to be configurable

The RTQP Engine is currently only able to connect to the Primary Data Archive to retrieve data, regardless of the SDK Priority settings. The “PreferPrimary” connection priority is hardcoded into the RTQP engine and cannot be modified. For users who depend heavily on RTQP queries, this can place a very high burden on the primary PI Data Archive, limiting their ability to spread the load across their PI Collective. Unlike the PI Analysis Service, the RTQP engine currently cannot write back to the PI Data Archive or create tags, thus it seems unnecessary to force the “PreferPrimary” setting on the RTQP engine. Ideally, the RTQP Engine can be configured to take the AF SDK Priority preferences so users can decide which PI Data Archive has priority, giving the users more flexibility on how to load balance their PI Data Archive collective. The workaround of setting the Primary’s priority to “-1” is not always feasible, especially for those users who are limited to two member collectives as this would leave them with just one Data Archive member to serve data to the RTQP engine.
  • Attach files
  • MarkGoepel
    Reply
    |     Aug 23, 2022
    Thank you very much for raising this Derek. We currently run three AF/RTQP servers, behind a NLB to service a very large (> 100 high frequency queries - as well as heavy ad-hoc queries) and growing number of RTQP Queries. We do not have any plans to write back PI Tag configuration via this method - even after that functionality becomes available. Our automated Tag Configuration processes use AF-SDK & PIwebAPI. Derek also mentioned it above, and it would be my preference to also enable AF Analysis Service to honour the SDK Priority Preferences, as we also do not have analysis engine creating/modifying tag configuration. Hard coding config backs us into a corner. By all means put warnings and comments in the app.config files, but please allow us the flexibility to balance the load across our PI Platform.
  • Guest
    Reply
    |     Aug 23, 2022
    This is essential as we have customers that already have high data loads on the Primary DA, and this ability to manually set the Priority allows for some form of load balancing in a system that doesn't have any built-in LB capability.