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 Asset Framework (AF)
Created by Christoph Rose
Created on Aug 19, 2022

RELATED IDEAS

Change UoM, Display Digits of attribute independently of element template

Currently, if an attribute is created with a Unit of Measurement in an element template, it is not possible to change the Unit of Measurement in the element created from that template. If no UoM is given in the template, then the UoM of the underlying PI Point is assigned. It would be very useful if the UoM could be changed. The same goes for Display Digits. This allows for some relatively generic element templates (for example for assigning values, limits, texts, etc for use in a Collection in PI Vision).
  • Attach files
  • Guest
    Reply
    |     Jun 5, 2024

    I agree and would add Default Value and Value Type to the list.

    I most care about Value Type as my points are mostly 0=Normal and 1=Alarm but occasionally inverted. Currently I am using 2 pi tags for this, the base tag fed from my EMSand then a second tag with an equation to invert it. It would be much simpler if I could go to the attribute and change the enumeration set.

  • Guest
    Reply
    |     Aug 19, 2022
    I agree with this but would suggest a small amendment to the UOM portion...I think that changing UOM *class* should require a template update, but changing UOM within the template-defined class should be allowed. It seems to me that templates are a way to define rules for groups of elements and the current UOM 'rule' is overly restrictive.