Allow PI Points to use the UOM database in PI AF
The Engineering Unit attribute of PI Points does not offer the same robustness as UOMs, which are only available in PI AF. Also, the user must set both the PI Point Engineering Unit and the element attribute UOM manually and separately, which is redundant.
Please implement a way for PI Points to use the UOM database. This way, the user only needs to set the PI Point's UOM attribute once. Then element attributes in PI AF can automatically inherit the PI Point's UOM.
This would also mean that the UOM database would have to be "detachable" from the rest of PI AF, since the user's organization will not necessarily use PI AF and would probably not want to install it just to have access to the UOM database.
I would like to offer another idea on a solution. In trying to make a global AF library I have found that it is difficult as some of our sites are in different countries so we use different units, i.e. psi vs. bar. The AF template forces you to use one UOM so can't accommodate for different countries.
My suggestion is when you map the PI points for the value what you can choose to bring in other attributes like UOM from the PI point. You would choose the UOM in PI when setting up the tags and they would be site based. This way a global template can account for site variation by inheriting these attributes. Now it may be smart to make the PI tag use a UOM database instead of free text as suggested above.
Kenneth Barber commented
I meant "reference" instead of "automatically inherit".