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 Tell us more
Product AVEVA™ PI Server
Categories Data Archive
Created by Hobbe
Created on Aug 20, 2022

RELATED IDEAS

New attribute for a PI point type ID

To take full advantage of AF and substitution parameters it would be great to have a sort of type ID. Now i have to rename all tags to gain this possibility. It would be easy if i could use a portion of the tag name and a  type id. Then i could deploy AF templates with substitution parameters really fast.
  • ADMIN RESPONSE
    Aug 20, 2022
    Using a portion of a tag name and a type ID may not guarantee there is a unique tag. What would be your expectation in this scenario? Should we always take the first one?
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Need clarifications. Are you referring to PI Point types? or AF attribute value types?
  • Hobbe
    Reply
    |     Aug 20, 2022
    In response to Stephen Kwan, "Need clarifications.  Are you referring ..." Hi! Since it is nearly impossible to have a perfect naming convention for PI tags, i wanted the possibility to substitute another attribute from the PI configuration to get it into AF.   //Magnus     Skickat med BlackBerry Work (www.blackberry.com)
  • Hobbe
    Reply
    |     Aug 20, 2022
    Hi! We are still struggeling with this issue! We are implementing a PI point name convention that are object oriented! However we are loosing the unique name of the sensor that brings the data. Somehow we want to be able to retrieve the unique sensor name from a PI point attribute and be able to create a AF attribute using this name, This is needed for the operators to find the correct attribute in PI AF or PI Vision from the sensor name in the controlsystem