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

RELATED IDEAS

Better visual distinction between reference types in the element hierarchy in PI System Explorer

Currently, you cannot visually distinguish between a composition relationship and a primary parent-child relationship, or between a secondary parent-child relationship and a weak reference in the element hierarchy in PI System Explorer. Please allow all of the built-in reference types to be visually distinguishable from each other from the element hierarchy. Perhaps the dotted line that connects the parent to the child could be formatted (solid versus dotted?) in addition to modifying the child element's symbol.
  • ADMIN RESPONSE
    Aug 19, 2022
    Can you provide specific use cases? For example, what would you do differently if such distinctions are available visually? Composition and parent-child references primarily affect what happens when objects are deleted. It really doesn't affect visualization. Any details you can provide would be helpful.
  • Attach files
  • Kenneth Barber
    Reply
    |     Aug 19, 2022
    The strongest use case is to make sure that the correct relationships are used. This can always be checked in bulk with PI Builder as well, but PI Builder is not as visual as PI System Explorer. It's easy for people to just use the default relationship for everything, even if another one would have been more appropriate, so it would be nice to be able to detect and then correct this easily. My suggestion is obviously not critical. It just helps with getting an understanding of the relationships between assets at a glance.