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 Declined
Product AVEVA™ PI Vision™
Categories AF Integration
Created by Willy Seah Wei Liat
Created on Aug 19, 2022

RELATED IDEAS

Support of more than 1 reason code

As a user, I would like to enter more than 1 reason code per event frame. For example, a downtime event frame is created for the whole production line, and I would like to have a reason code for the cause and the other for the equipment. Currently, AF only supports 1 reason trait attribute per event frame. This also allows PI Vision to enter 1 reason per event frame.
  • ADMIN RESPONSE
    Aug 19, 2022
    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    totally agree here.  we need to be very flexible here because many events are caused by a combination of triggers.
  • Guest
    Reply
    |     Aug 19, 2022
    We need at least two reason codes for proper downtime tracking and pareto analysis. The comments box is useful for additional explanation but the reason codes must be selected from individual lists to ensure they are consistent for analysis.
  • ehoffman
    Reply
    |     Aug 19, 2022
    Multiple reason codes would really help us add additional context to our event frames. Our goal is to tie equipment ids to our event frames to help with failure reporting while still having the failure reason code data. Can this item be reopened and considered?
  • Guest
    Reply
    |     Aug 19, 2022
    Also want to to comment that this is absolutely necessary. We need the capability of multiple reason codes so that the downtime events can be efficiently and accurately coded by the operator. I can give them 10,000 choices in a single reason code, or 100 in code 1 and 100 in code 2. Which one do you think they are more likely to get right?
  • J.M. Rodríguez
    Reply
    |     Aug 19, 2022
    This is absolutely necessary. I find a lot of cases where it is necessary to classify, as it has been said, in case of a downtime, at least the equipment which caused it and the concrete reason. This split is needed for later analyses. It is not enaugh with having a codes tree. I think that this enhancement should be considered.