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 Vision™
Categories AF Integration
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Hide data when attributes don't exist for dissimilar assets

Assets and machines are never quite the same. Be able to swap the asset/element context (may be different template) and if the selected asset doesn't have certain data available on the display or if it is marked as excluded, don't show it on the display rather than an error message. This should apply to collections in addition to individual symbols.
  • Attach files
  • Zubin Najmi
    Reply
    |     Dec 28, 2022

    AF correctly hides excluded attributes when viewed in the left pane of Pi Vision -- but Trends, Tables, Values need some work/fixes to work correctly (for excluded/hidden attributes). PiVision and AF are not "in-synch". Aveva team, please address as we heavily rely on using templates.

  • Guest
    Reply
    |     Aug 19, 2022
    The customer would like the ability to hide template-based attributes with non-existent PI point data references in existing PI Vision displays. They have site's (i.e., ~100k tags) which are not yet monitored - meaning their tags are not created yet. In AF, the template already associates these attributes (PI point data reference) to their respective tags. Currently, the excluded property hides the template-based attributes in the PI Vision navigation tree, but does not remove it from existing displays. Instead, it displays excluded attributes with a value of either "No Data" or "N/A".
  • karthi44
    Reply
    |     Aug 19, 2022
    My scenario explained below: Element A - Has 10 Attributes Element B - Has 8 Attributes Element C - Has 10 Attributes All from a same template - where Element B has 2 excluded attribute. Now, In PI Vision - If i add all the 10 Attribute from Element A and convert to collection... I will see N/A for the missing/ excluded attribute in Element B ... ( This is annoying as we cannot hide it easily.) So IF we have the ability - Hide excluded in pi vision or hidden option for the excluded attribute it will be awesome. And, If we have Multi-State on the Font color of "Value" It will be easy to hide the N/A values.... Some "intuitive functionality"
  • Guest
    Reply
    |     Aug 19, 2022
    It would also help on the usage of collection, excluded attributes not being considered for the collection would be a good usage.
  • Guest
    Reply
    |     Aug 19, 2022
    And if you'd like to extend, also if an rectangle/object has a multi state linked to an excluded it could be "excluded" too from pi vision display.
  • RyanCarpenterAd
    Reply
    |     Aug 19, 2022
    +1 for hiding excluded assets in PiVision. I find it easier to just have a big "Strawman" template that is common to everything instead of manage 10 different derived templates of various layers. The one gap with this approach is that users see quite a bit of data in the attribute area that doesn't exist.
  • Guest
    Reply
    |     Aug 19, 2022
    In addition to adding this functionality please make multistate configuration available when implementing this solution as well. An excluded attribute currently lists "No Data" as a value and multistate is not applicable. When switching to an asset that may have that data point/attribute multistate would apply yet cannot be configured.