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 Completed
Product AVEVA™ PI Vision™
Categories Manual Data Entry / PI Manual Logger
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Manually Enter Event (EF) Attributes (like a Reason Code)

I'd like to manually enter data into event (event frame) attributes from PI Coresight.  The most common example of this are attributes such as a Reason Code for an excursion or downtime event, but there are other examples as well.
  • ADMIN RESPONSE
    Aug 20, 2022
    The PI Vision development team has completed work to allow users to edit the value of Event Frame reason attributes (based on the new Reason attribute trait in PI AF 2017 R2) on the Event Table and Event Details page in PI Vision 2017 R2. Upgrade to PI Vision 2017 R2 to take advantage of this and other new features. You can read about what's new in PI Vision 2017 R2 in the release announcement: https://techsupport.osisoft.com/Troubleshooting/Releases/RL01278
  • Attach files
  • Brent Bregenzer
    Reply
    |     Aug 20, 2022
    I have worked with 3 different customers who asked about this functionality because they do not have a tag that can be used to automatically assign a reason code. In one case, the customer was investing quite a bit of development time into their own EF client tool that included this feature. it would be great to have it natively in Coresight.
  • jagdish.konathala
    Reply
    |     Aug 20, 2022
    This will be very helpful in establishing a cleaner workflow for reason code entry. Currently being done in Excel after EF are imported. Using Coresight to eliminate Excel out of the equation by providing text field entry via Coresight will be awesome!
  • Guest
    Reply
    |     Aug 20, 2022
    Same as Brent Bregenzer. Our customers look for the same thing.
  • Guest
    Reply
    |     Aug 20, 2022
    Would be a great possebillity. Please consider implementing a identification for the user entering the data (and if possible the Support for 21 CFR Part 11 Electronic Signatures)
  • Guest
    Reply
    |     Aug 20, 2022
    I am waiting for this feature too. It would eliminate a lot of customization. I think the "Manual Data Entry"property is part of the plan. Tick that, configure an inline editor, and make it happen. For Event Frames and Elements.
  • Guest
    Reply
    |     Aug 20, 2022
    I get this request at nearly every presentation
  • Guest
    Reply
    |     Aug 20, 2022
    Yes please, customers are asking for this regularly!
  • Guest
    Reply
    |     Aug 20, 2022
    During AF workshop, I also heard this multiple times. It will allow customer to have data ready for reporting directly without any customization. Especially for Downtime tracing is this essential.
  • Guest
    Reply
    |     Aug 20, 2022
    This is very similar to this request: https://feedback.osisoft.com/forums/320517-pi-coresight/suggestions/13658616-manually-enter-event-ef-attributes-like-a-reaso Is there any possibility to merge similar/same request and add their votes?
  • Guest
    Reply
    |     Aug 20, 2022
    Very important feature. Hopefully, it will be implemented soon in PI Vision
  • Guest
    Reply
    |     Aug 20, 2022
    This would allow users to select from a fixed list of codes when entering in comments on PI Event Frames; this would make eventual event comparison or Pareto analysis (in PI DataLink, for example) far easier, since there'd be no chance that users could misspell or mistype reason codes when entering in comments. Without this, a site needs to make sure to be perfectly consistent every single time that a user adds a reason code through PI Coresight Event Frame annotations. Being able to add digital state values, for example, or pick from a list of Event Frame categories, for example, would make this far, far easier, and would make adding annotations far more useful!
  • Nico Cha
    Reply
    |     Aug 20, 2022
    I have a customer who would also like the functionalities that Dan Lopez, having users be able to select a fixed set of list code. I believe this would be a useful functionality as well!
  • Guest
    Reply
    |     Aug 20, 2022
    The user should be able to designate which Attributes will appear in PI Vision EF Details screen for manual entry. The most common uses are a reason code (enumeration list) and a free form comment (string Attribute)
  • Guest
    Reply
    |     Aug 20, 2022
    Could be extended to the change of PI AF attributes values
  • Jason Gogal
    Reply
    |     Aug 20, 2022
    This is a tremendous idea; it would essentially enable Vision to function as a downtime / production loss platform. The reason code part is a crucial piece that has been missing and filled in with third party stuff for quite some time.