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.
-
Asset Comparison Display
Be able to easily create an asset comparison display where the same attribute on an asset is compared against other similar assets (for example, based on template) over a time range.
For example, compare the MW produced on all Wind Turbines over the last day, which on a trend the traces would be the name of each asset.
Note: This was previously Enhancement 93111.
15 votesIn the PI Vision 2017 release, we introduced Collections and an Asset Comparison Table, both of which allow you to quickly and easily compare attributes across similar assets.
We are looking for feedback on whether or not these features satisfy this request for an Asset Comparison Display.
-
Ability to allow Vision users to set and save their time zone
We are a large company that is across the US. We need to allow users to set and save their time zone within PI Vision.
7 votesIf you have a chance, we’d like to learn more about the use case behind this request.
By default, PI Vision will automatically pick up and use the time zone of the client machine a user is running their browser on, so all times should be displayed in a user’s local time zone.
If this isn’t the behavior you are seeing, or if you have a use case where users need more control over the time zone being used to display data please let us know.
-
Match Trace Colors Between the Display and Ad Hoc
In the PI Vision ad hoc workspace, the colors of the traces in the ad hoc trends should match the colors that they were in the display they came from, instead of being randomly assigned a new color when they are added.
1 voteIn PI Vision 2019, if a trend symbol is added to an empty ad hoc workspace, the trace colors used in the workspace will be the same colors that were defined in the trend. If there are already data items in the workspace, the colors will be assigned in a specific order so that there are no duplicates.
When data from any other symbol is added to the workspace, the data items will always get assigned a color in a specific order.
Please let us know if this is the behavior you are looking for or if you are looking for colors to be preserved in other cases.
- Don't see your idea?