Expand the tag based PI Vision Calculations introduced in PI Vision 2020 to support simple AF attribute based calculations (addition, subtraction, etc.).

In some situations, PI Vision administrators may wish to globally disable the Calculations feature, or selectively limit who may use it.

• Backwards compatibility with PI ProcessBook Data Sets is not needed
• Policy requires exclusive use of Asset Analytics
• Concerns of increased load on the PI Server due to lack of restrictions on Calculation creation
• Etc.

PI Vision should offer the ability to limit the use of Calculations throughout the system, or to only a select group of trusted users.

We need to track which PI Vision displays are using ad-hoc calculations so we can monitor how they are impacting the PI Data Archive.

Best would be to limit this usage (https://feedback.osisoft.com/forums/320517-pi-vision/suggestions/42635995-ability-to-disable-calculations-feature) but using the report feature could also be a viable solution and enable us to really go to the 2020 version and further releases.

Now we stay on 2019 versions just because we cannot control the ad-hoc calculation usage by end-users.

Allow users to use the rows list to select, move, or delete a row in the Asset Comparison table.

It would be very useful to be able to configure the trace type for each tag on a single trend. For example have one tag show only markers but a second one show only the line.

In nearly all installations in the last three years we have restrictions on the servers where we need to install the SSL certificates, that make it impossible to verify the validity (e.g. no access to revocation servers).
The certificate is accepted by clients as those have different authorisations.

I would like to optionally bypass the certificate checks in the PI Web API Configuration utility to allow using certificates that cannot be validated. This will save a lot of time to bypass the utility and manually remove and bind a certificate.

Multistate: Change text color
In multistate, we are able to change background color.
We would like to be able to change text (letters, words) colors for text and value symbols with multistate.

In multistate, we are able to change background color.
We would like to be able to change text (letters, words) colors for text and value symbols with multistate.
Thx

I need to be able to see a summary page with various trends, however some of them I would like to see at different trend durations. For example, I would like to see most trends at a one month interval. However, for another trend where the data is only taken monthly I need to see it on a yearly interval to see a trend. Or for another trend that I care about long term process creep I would like to see at 90 days.

Large displays can take 30 seconds or longer to load. Load times are particularly slow in Internet Explorer. Displays needs to load faster.

The PI Vision install kit currently includes the 32-bit and 64-bit versions of Microsoft Visual C++ Redistributable 2015, 2017, and 2019. There is a version available that combines these versions (https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads). Please include this version with the PI Vision install kit instead. This should make the PI Vision install kit a bit smaller and shrink the list of included programs.

Of course, if the dependence on the 2015 and/or the 2017 version is eliminated, then it would be better to not implement this suggestion.

Digital states used for multistates are currently stored with a display, so if they are modified PI Vision does not currently detect this change. PI Vision should provide a way to update multistates with the new modified digital states. This applies to enumeration sets in AF as well.

Just a question? What happened to the training videos? I just started using this PI Vision yesterday as I was looking forward to learning via the videos. I am alone in extreme remote solar. : (

I want to see if there is event frames for each attribute in a PI Vision collection. However as soon i am converting a single object to a collection it doesn't list any event frames.

I have been told this has been designed to work like that, but this functionality would be very useful for us.

The arc symbol is migrated with the PI ProcessBook to PI Vision Migration Utility, however PI Vision does not support the same configuration options as PI ProcessBook, so in many cases arcs are not migrated well (PI Vision only supports 90 degree arcs). Improvements should be made so that arcs from PI ProcessBook can be migrated properly.

Allow specifying plot titles for trend symbols, similar to how ProcessBook allows specifying a plot name.

Configure multi-state: enable color changes using result of a calculation comparing data with another PI tag or PI AF attribute value.

As we're going to use Chromium browser as enterprise standard, it would be great if Chromium was officially compatible with PI Vision (case number 00643921).

We should be able to add element's name and description to symbols, without the need to create another attribute for that. So we could easily have element relative titles and labels...

Ability to filter out data on trends when a condition is true.

For example: remote all data on a trend when the status is 'Not Running' or 'Capacity' is below 50%.

Data would be hidden on the trends (gaps), optional way to collapse the false time periods as well.