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.
All our comments are already explained in the existing comments. Nothing more to add
Enabling a rollback to a previous version would be very useful. There have been many of times a change to a graphic and the idea ends up being too cumbersome and being able to start from scratch would be helpful. Also, keeping a few versions would be great to enable check and balance from old to new version.
With a web-based design there is a much higher chance of production changes that can be made in error that can't be recovered or that with it being possible to have multiple users overwrite each others changes. Before with a file based system it was no problem to restore working versions from backups so the last of versioning or an automated backup system in Vision is a step backwards.
To help you, this is our vision :
Specific problem :
when users are saving a Display by mistake or with an error that cannot be easily modified once saved
identified who made a modification when several users can work on the display
How
Same as for O365 document where it is possible to view all modificatons carried out, when and by whom,
With the possibility to view the old version, restore the old version or remove the old version
Possibility to define how long each version can be stored and/or how many (to be configured by PI Vision Admin)
Who will benefit :
Users (less stress regarding modification)
PI Vision Administrators to help users
Quick and easy backup and restore is so essential to a system like this that we developed our own solution in house. If we hadn't we'd probably have to purchase the system that Werusys is developing to accomplish the same thing.
agree with Versioning, Major/Minor and the possibility to define specific users groups that can access both the published and newly versioned version.
every change should be trackable in terms of a little changelog.
not sure if an internal tool for finding the differences will do the expected job..
"performances" data should be collected separately for each version in order to optimize the new changes.
Agree with all below. Having ability to publish a Major Version (V1.0) of a display while also having the ability to edit a minor version (V1.1) in the background. Once V1.1 is tested and approved then the new screen would be published at a new major version V2.0 for example.
In a GMP environment we make software changes under a Quality Management System (QMS) or a change management process. Each version should be attributable to a change.
For example:
V2.0 Updated to include 2 x Temperature elements under QMS-123456
Agree 100%, comments below describe my vision of this functionnality just right.
I believe there is a display version number already. I wrote a PI-Vision display backup based on a OSIsoft example script. Part of the metadata had a count that changed every time the display was updated. I used this to keep the previous versions. Not perfect, because it's just a point-in-time backup of saved displays.