Attribute UOM Substitution Parameter
If you have a PI Point attribute with auto tag creation and you want the attribute UOM and PI Point engunits to match, you have to define it twice; once in the attribute UOM field and a second in the attribute configuration string, e.g. engunits=m3. If there was a substitution parameter for the attribute's UOM, you could use it in the attribute configuration string, e.g. engunits=%AttributeUOM%.

10 comments
-
Mdiakhite commented
Fully agree with all comment below, for those seeking a workaround until development of the functionality :
https://pisquare.osisoft.com/community/all-things-pi/af-library/blog/2016/04/08/create-pi-point-with-custom-uom-from-an-attribute-in-a-template?comment=14318 -
ngardy_APP commented
This function is really needed to improve PI AF...
-
rfesler commented
there are too many work around that are not stable. this would be a really really helpful feature.
-
DannyTaylor commented
yes - this is a function we need to have please.
-
Roger Palmen commented
I just ran into this again today using the Integrator for BA where i need to expose the UoM used for attributes...
-
Asle Frantzen commented
This is something we need. This is a pain today - we need to do it manually for all output points created from AF.
-
Roger Palmen commented
It should be easier to create PI Points from the AFmodel using the UoM set for the attribute. This will help a lot to simplify that.
When used for template attributes, the engunits could even be set by default to this, ensuring proper alignment -
Roger Palmen commented
That's a nice one! Or when enabling the point creation in the template, pre-fill the units with the UOM of the attribute.
-
Fabiano Batista commented
As I user, I want to create my analysis output tags with the eng units matching the defaut UOM set for the element attribute. That would require the implementation of a substituition parameter like %UOM%.
-
Sebastien Raposo commented
We use a custom data reference to store UOM information in an AF Attribute, which is then stored in PI using Tag Creation and substitution parameter. Currently there is no way to automate the UOM written in an AF attribute to the UOM field of the "target" attribute.
A possible way of doing this, from a user perspective, would be to allow substitution parameters to be used in UOM definition.