Changing Units of Measure (UOM)
The ProcessBook feature of changing the units would be great in PI Vision. Example: instead of Watts, it would be better to see MW.
VERY IMPORTANT FOR US AS A GLOBAL COMPANY!!! Do be able do use Collections it is absolutely no solution to create seperate Attributes for each UOM!!!
Yes - please do something around allowing the user to select the UOM or UOM set they want in Vision. There are products out there that do this already. Should be possible to leverage the UOM groups in AF. This is quite important for global companies, where the displays will be consumed in many parts of the world.
There are many things Vision could do with Units of Measure. For example, convert all traces in a trend to a common UOM - we have process flows measured in bbl/h, kbbl/day, etc. It would be nice to be able to specify that in the trend they can all be converted to a common UOM for better comparison.
Jeremy Dyer commented
Very keen to see this implemented. It is a great AF feature and would be great to also have this functionality in Vision. Different users like to see different units such as L/s vs ML/d or mm vs m as examples.
It would be great to use the UoM group feature within PI Vision (with a dropdown)!!!
Convert units on display of attributes (under formatting options)
Naoto Yamabe (山部 直登) commented
I would like to strongly support this idea. Engineering Units of displayed data (attribute) on PI Vision should be changed by user.
Paul Booth commented
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.
Fabiano Batista commented
This feature is crucial for PI Vision. It will allow users to leverage the power of UOM. Because of the lack of this feature, some users had to create additional attributes to be able to expose values in different UOM (users end up going against AF development best practices).