Absolutely dreadful retrograde move. A cynic might think OSISoft is deliberately setting out to make life hard for firms who support multiple customers so as to get the support work itself.
Again, we are left with a sub-standard visualization tool. Whatever were you thinking when you didn't bother to include UOM selection? These basic things, things ProcessBook can do with ease, should have been put in as a matter of course - we shouldn't have to be begging for basics. Instead we have, as commented, a requirement to duplicate attributes just to do basic unit adjustments, breaking our naming conventions and trouncing your own AF development best practices.
81 votesRESEARCHING / EVALUATING · 22 comments · PI Server » Asset Framework (AF) · Flag idea as inappropriate… · Admin →
We are currently researching this item and evaluating it for a future release.
If you have a moment, please let us know if you have a preference for how data item descriptions should be displayed in trends. For example, would you prefer to be able to configure the trend legend to show the item’s description, that the descriptions be shown under the plot area of the trend, or would you like them to be displayed in another way?
Let us know what your preference is by adding a comment below.
Again, it's difficult to understand why OSISoft present their flagship product with such deficient standard items. It should have been policy to, at very least, provide an item that was at least as good as the ProcessBook symbol it replaced. ProcessBook allows inclusion of any combination of value, units, name, descriptor: this should have been the starting point, not something that needs to be asked for......
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
This is a must.
Tried using the Collection, but some idiot programmed it to display fixed format text when there were no items: whoever decided that really knows how to take a potentially useful thing and mess it up. Sure, allow it to do it if someone wanted it to, but please think about these things. Also I believe that its root search element doesn't change with the screen context: quite an omission that. Perhaps more experienced designers should have been used for a flagship product?.
This is a requirement that I, and a number of other users, have identified as being very useful.
This need to be a complete solution - i.e. both read and write access to the message logs, just as the PI-SDK allows now.