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.
I agree. I would find it helpful if the PI Vision local calculations included functionality which returned the start time, duration and end time of the PI Vision display. I think this would provide PI Vision displays similarly effective calculation potentials as the EventFrame([xxx]) function.
DisplayTime("StartTime") => Start time of display
DisplayTime("Duration") => Duration of display
DisplayTime("EndTime") => End time of display
(While I reference this using a format based upon the EventFrame([xxx]) function within EventFrame Analyses, I am happy for any format.)
My Use Case:
Within PI ProcessBook we had custom code which allowed the user to enter start and end times and the VBA Code would update every trend and data set to reflect those times. These VBA-created data sets were embedded with timestamps implementing similar functionality to what is now in the EventFrame([xxx]) function within analyses. We used this for event reviews to easily find the extrema values and times for a large set of tags for any random event. Since moving to PI Vision, we have made a proxy of this functionality forcing all reviews to be a static duration of one hour. This adds a lot of noise to our reviews.
Another, more general use case would be to use PI Vision for EventFrame Analysis design and simulation.