Skip to Main Content
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.

Status Declined
Created by Asle Frantzen
Created on Aug 19, 2022

New attribute trait: PI Tag Name

Since using the child attribute "PI Tag Name" to hold the actual tag name is considered best practice in AF, why not encourage it even more by making it an attribute trait? Another option would be the ability to expose the actual tag name as a property of the PI Point DR attribute. A vital part of increasing the usage of AF out there is to remember that (many) people have a strong relationship with their tags, and if you completely remove this information by "hiding" it into the attribute config. these people will never make any effort moving over to asset centric way of thinking.
  • ADMIN RESPONSE
    Aug 19, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    I fully agree with the PI Tag Name part. Hoping it ill be implemented in next version to help us have a consistent usage of that best practice within our AF.