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

RELATED IDEAS

Override analysis of template based element

Currently you can override an analysis of a base template in a derived template by creating an analysis with the same name. Unfortunately it is not possible to do the same in an element that is based on a template. I do not want to create a derived template for rare cases where the analysis of the template has to be tweaked for a special elements.
  • ADMIN RESPONSE
    Aug 20, 2022
    In your element instance, simply disable the analysis from the template and create an additional analysis. This behavior was designed to support your described need. We want to avoid overriding templates as much as possible because over time, it becomes much more difficult to manage the system since individual instances would behave differently.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Unfortunately your proposal does not work: - Simply stopping the template based analysis is confusing as nobody knows if the analysis is stopped by accident or intentionally. You can set the description, but that is bad. - The overrriden analysis must have a different name (ok we could live with that) - Mapping an output attribute is possible by design, but does not work. Error message: '...Attribute' is mapped as output for more than one analysis (AnalysisName)