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

Add the option to select or add custom triggers on Rollup

Currently Rollup triggers can only be "All attributes" or periodic. But sometimes, especially when you are dealing with lots of attributes been rolled up together, you may want to specify one (or a couple) attributes to the be triggers of your Rollup, while the other attributes wouldn't need to me monitored. Giving our case as an example, currently we have an asset with 100+ attributes with mixed online and manual data. The online data will come each 15 minutes while the manual data comes once in a week. And all online data comes basically together. So, ideally for us instead of having all attributes as triggers, we would want to have just some online attributes as triggers. That way we would reduce the log time of analysis and also the amount of memory used by it.
  • Attach files
  • Georg Krichel
    Reply
    |     Aug 20, 2022
    In our system about 40 values per asset comes via slow GPRS connections in random order. Most of these values are inputs to Formula data references with their outputs are inputs to rollups. Exactly one value is guaranteed to be the last one in a transmission series, so we want the attribute of this value to be the only trigger attribute to rollups.