This request comes back time and time again from our user base.

I will add my vote to the list. Integrating PI manual logger into PI vision would be a great opportunity to improve and streamline your products! Thanks OSI and hope you can make it happen some day.

Installed the extensibility object for this and it worked great for me, yay . . . but doesn't work for other users, and we can't figure out why - Support is already alluding to, "well, this isn't a supported object". 9 values, that's it, and the display is built and works for one. Really don't want to mess with Excel or Man Logger. Other's are saying we should use GE's Plant Applications - lol, using the competition's app to put data in PI - I don't want to go there either.

Manual data entry is required from our customer at the moment but PI Manual Logger cannot add or modify Asset Framework attributes.

Question to OSIsoft/AVEVA - how much voices do need in order to satisfy clients your system ?

Also very high on my companies request list.

Having the manual entry features of PI Manual Logger integrated into PI Vision seems like such a natural fit and selling point.

I can't understand that Manual Logger has not been updated from 2017 and already integrated with PI Vision

This really is an essential feature and has been on nearly every user's wish list for years. Time to get it into the roadmap!!

Our Production departments upload well over 1,500 values a day (that cannot be easily or cheaply automated) to PI DB via DataLink/Custom VBA in Excel. Our IT department is moving everyone to web based O-365 (no DataLink support) and banning all VBA code. We are also migrating from Process Book to Vision. Having the ability to upload manual data directly from Vision would be a great benefit to us. This function was previously available in WebParts. And yes, we have looked at Manual Logger, it is not well suited for our needs.

410 votes so far - this is a highly requested item from our clients.

I'm aware that writing tags and attributes need specific roles for the accounts enabled, but the possibility to change the setting of alarms is essential for an effective use of PI Vision display for O&M staff

This is still an important topic. The number of votes and comments shows how hard this feature is needed. To make it a whole solution, it would be great to include electronic signature functionality (make it configureable, so the customer is able to enable or disable the ESIG funcionality for each symbol)

Need this feature. I read some of the comments below and I agree that PI Data Logger as a separate application is not a good visual solution. I'm not asking for "full scale" data entry where a user can easily populate attribute after attribute, create a spreadsheet, etc. I'm looking for a feature where a user can view the PIVision screen and affect the value of an attribute that may be temperature setpoint, or toggle a boolean value similar to a pushbutton.

We also need a method to allow users to edit values in internal AF tables. The only method that I am aware of is to edit those tables using PI System Explorer.

I've been trying to promote PI Vision as a tool for operator dashboard. But the feedback I got over and over again is if operators cannot input data it can't be a practical tool. We always end up using something else.

This can be done with PI Vision extensibility but that requires programming. PI Vision upgrade also tend to break it.

This can also be done with PI Manual Logger web but it's a separated web page. PIML Web is also designed for handheld and the visual is not that pleasing.

It's a fundamental issue. For comparison purposes, a good idea is to insert a value, like an attribute goal or setpoint, and visualize the difeerence to other available attributes.

@mitchesj could you elaborate how you writing manual entry data via PI Vision?

In bp we have PI Vision manual entry displays that write to PI Tags.

Ryan - I thought it was on the roadmap to be able to do data entry via PI-Vision as a merge of PI-ML into PI Vision. Is this off the table?

this is a gap that needs to be filled !

This should be definitely implemented. It would be very useful in a lot of cases and would make the edition of values of attributes much easier.