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

Currently, only 1 AF server is configured to provide identities for vision display security. Displays can show data from multiple AF servers, which could have different security mappings. It would be nice to be able to pull identities from multiple AF servers for display security that matches the AF security that already exists.

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)

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

Not a fan of the Asset Framework tree structure in PI Vision. It needs to work as a tree structure just like PI System Explorer. The setup in Vision is too clunky and is hard to navigate.

Again, I would like to see the tree structure consistent in all products to mirror System Explorer.

Often work has been done on a PI Vision display (with a known/published URL) only to realise you were not the owner when hitting the "save" button. A prompt when editing starts, or keeping the save button in the "inactive" state if not the display owner would help prevent this re-work.

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.

Allow adding a table to event comparison displays so that different information for each event can be displayed (for example recipe, cell-clone, ...). This would allow this information to be available similar to how it is displayed in the search results in BatchView

It is very important in the case of downtime to see the changes in Manual Logger Web immediately to ensure the downtime and run-time events are accurately measured. Therefore having the data not update immediately in the tag trend display in the manual logger web view or the historical data view is detrimental because it is difficult to know if the event was accurately entered.

When the Assets on Display option is used for the Asset Name field in events search, events that match the search criteria are shown sorted by asset. In all other cases events are ordered by start time. Events should always be sorted by start time, even when the Assets on Display filter is used.

Option to export data to a PI DataLink sheet configured with connection info so that you can jump into further analysis in a spreadsheet.

Provide a way to configure which users have access to Acknowledge an EF within PI Vision.

Currently, the font size is directly related to symbol size. This is problematic when migrating button symbols from PI ProcessBook to PI Vision, since they will not retain their width. This leads to manual work being required to adjust the display layout after displays are migrated.

An alternative solution would be to add a button symbol to PI Vision that can be sized independently of the symbol's font size.

Add a navigation pane to the display (similar to Assets, Events, and Graphics Library) for Display Navigation, to allow users to easily navigate to a different display.

The PI Vision Display Utility allows modifying the PI or AF Server/Database when copying displays from on PI Vision server to another, but it does not support modifying PI tag names.

We are syncing tags between environments and using prefixes to denote the environment. The PI Vision Display Utility does not support this scenario currently, since both the point ID and the tag name are different in the other environment, the tags cannot be resolved after displays are copied.

Currently, a "dynamic" links on PI Vision displays are Asset Framework attributes using StringBuilder that are displayed using a value symbol. When the symbol is clicked, a new tab is opened.

Having the display redirect in the same tab would be more ideal.