How can we improve PI Vision?

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.

52 votes
Sign in
Signed in as (Sign out)

We’ll send you updates on this idea

AdminTodd Brown (Product Manager, OSIsoft) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
COMPLETED  ·  AdminAlicia Coppock (Admin, OSIsoft) responded  · 

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

15 comments

Sign in
Signed in as (Sign out)
Submitting...
  • jasongogal commented  ·   ·  Flag as inappropriate

    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.

  • Ales Soudek commented  ·   ·  Flag as inappropriate

    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)

  • Nico Cha commented  ·   ·  Flag as inappropriate

    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!

  • bazb commented  ·   ·  Flag as inappropriate

    Very important feature. Hopefully, it will be implemented soon in PI Vision

  • Elena Rakovska commented  ·   ·  Flag as inappropriate

    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.

  • JHvanderVen commented  ·   ·  Flag as inappropriate

    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.

  • flost commented  ·   ·  Flag as inappropriate

    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)

  • jagdish.konathala commented  ·   ·  Flag as inappropriate

    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!

  • Dan Lopez commented  ·   ·  Flag as inappropriate

    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!

  • Brent Bregenzer commented  ·   ·  Flag as inappropriate

    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.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED