How do you manage the PI Vision screens?

Hi Karthi,

As a Technical Adviser at OSIsoft i cannot provide a specific example but i can provide some thoughts on some ways to think about this issue.  If you've been around PI for a while, then you're familiar with the issue of a proliferation of  ProcesBook (PB) displays.  When we move from the old days of PI and PB to AF and PI Vision, we may want to consider thinking of some of this differently, than we did before.

We helped a customer through an evaluation of notifications and displays and migrating them from a competing product to PI.  It turns out, when we looked a little deeper, notifications often existed just so people would know how often something was happening, not to take any action.  These were good candidates for Event Frames and Watchlists in PI Vision or MS Excel with DataLink and reporting.  Many of the displays were built so that people could have quick access to tags and understand their context in the process or association to an asset.   PI AF today is really helpful in understanding the data in context of the process or asset.

With a well developed AF structure and some analytics, we can easily cut way down on the number of PI Notifications.  With a good AF structure and a little understanding of how easy and fast it is to get to the information in PI Vision (those 3 easy steps), the less we need pre-built displays.  I've seen some PI Vision systems with many, many very simple displays; these may not be used often and are easily dynamically created when needed.

Of course in recent PI Vision versions there are folders to help with display management.  Perhaps consider limiting the number of displays that are built and shared with everyone too (as opposed to keeping the display for one's self).

There are governance considerations here too to ensure that folders and the number of displays do not get out of hand.  When any hierarchy gets pretty involved, people tend to defer to search pretty quickly; so naming standards may help as well.

Best of luck.

Keith 

Hi Karthi,

As a Technical Adviser at OSIsoft i cannot provide a specific example but i can provide some thoughts on some ways to think about this issue.  If you've been around PI for a while, then you're familiar with the issue of a proliferation of  ProcesBook (PB) displays.  When we move from the old days of PI and PB to AF and PI Vision, we may want to consider thinking of some of this differently, than we did before.

We helped a customer through an evaluation of notifications and displays and migrating them from a competing product to PI.  It turns out, when we looked a little deeper, notifications often existed just so people would know how often something was happening, not to take any action.  These were good candidates for Event Frames and Watchlists in PI Vision or MS Excel with DataLink and reporting.  Many of the displays were built so that people could have quick access to tags and understand their context in the process or association to an asset.   PI AF today is really helpful in understanding the data in context of the process or asset.

With a well developed AF structure and some analytics, we can easily cut way down on the number of PI Notifications.  With a good AF structure and a little understanding of how easy and fast it is to get to the information in PI Vision (those 3 easy steps), the less we need pre-built displays.  I've seen some PI Vision systems with many, many very simple displays; these may not be used often and are easily dynamically created when needed.

Of course in recent PI Vision versions there are folders to help with display management.  Perhaps consider limiting the number of displays that are built and shared with everyone too (as opposed to keeping the display for one's self).

There are governance considerations here too to ensure that folders and the number of displays do not get out of hand.  When any hierarchy gets pretty involved, people tend to defer to search pretty quickly; so naming standards may help as well.

Best of luck.

Keith