PI Vision
Welcome to the PI Vision (formerly PI Coresight) feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Vision. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Support Cross Domain authentication for PI Processbook to PI Vision 2019 Migration Utility
On an architecture with Utility on a computer located on a different domain of the PI Vision server, the authentication fail.
Could it be possible to prompt a login window (as for AF)
6 votesCurrently the migration utility will attempt to access PI Vision as the user who is currently logged into the machine. Could you please share more information about your use case and how would a login prompt be useful in this case? Does the user need to enter login credentials so that they can authenticate as a different user (a user other than the user currently logged into the machine)?
-
Apply PI Vision folder security to Destination folders when migrating ProcessBook displays
Currently any user in the PI Vision Utility Users group running the PI ProcessBook to PI Vision migration utility can select any folder as the destination folder, regardless of whether they are allowed to write to the folder in PI Vision (i.e. their AF Identity has write permissions on the PI Vision folder).
Additionally, only certain users (e.g. PI Vision admins or specific identities) should be able to specify a user other than themselves as the owner of a display.
The ProcessBook to Vision migration utility should observe PI Vision folder security.
4 votes -
Distinguish between types of OLE objects during the migration analysis
Currently if a .PDI file contains an OLE object, which could be something as simple as an image embedded in the file using Insert > Object in ProcessBook, the OLE object can't be migrated. The Analysis Results return a warning that the "File contains OLE object" but nothing more. It would be useful if more details could be generated about the OLE object, such as whether it's embedded, how many OLE objects there are (if more than 1), and/or the object type.
2 votes -
Trend with digital state, show only digital state for scale, it should allow number like before in Processbook
In Processbook, when we draw a trend with multiple digital tag, we can set multiple scale with the number of the state. This permit to see multiple tag with the same scale on different place in the trend. When we define the trend we see only the digital state, we do not have the choice for entering a number
2 votes -
Preserve display links across different batches of migrated displays
Currently display links are only preserved when linked PI ProcessBook displays are migrated together. Navigation links should be preserved across different batches of displays that are migrated.
2 votes -
Batch Group / Gantt Chart from PI Batch Data
In PI Process Book it is possible to create Gantt Charts, and corresponding tag trend overlays from PI Batch data. There is no need to create event frames in PI AF to use this feature. This was my most used feature in PI Process Book, and the lack of this feature has prevented me from fully migrating all of my PI process books into PI vision.
1 vote -
I created a number of PI ProcessBook displays that utilize VBA code.
VBA coding or some form of coding should be supported in PI Vision. One use of VBA coding was necessary in PI ProcessBook because multiple PI AF contexts are not able to be selected for similar groupings of symbols on the same display. An example is a table where each row has a pull-down menu to set each column of the row to the proper PI tags.
1 vote
- Don't see your idea?