AVEVA Product Feedback


Add a new idea Subscribe
138 VOTE
Status No Status
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

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%.
  • Attach files
  • Guest
    Reply
    |     Feb 13, 2023

    This feature is long overdue. This was identified as a critical piece of missing functionalities back with AF 2.1 in ~2010. I don't think this will be added/implemented in our lifetime. I surely hope it will.

  • Guest
    Reply
    |     Oct 11, 2022

    Hello, it would be nice to have the option to use substitution parameters for the UOM in the configuration string of attribute: like:
    \\%server%\%@.|tagname%;UOM=%@.|sourceUOM%

    we have Templates applied to difference Motors from different vendors, the UOM can change from one to another , these source UOM are saved in attributes ( using Tablelookup).

    this is really very important as now we need to do that in a custom script all the time.


  • Roger Palmen
    Reply
    |     Aug 19, 2022
    That's a nice one! Or when enabling the point creation in the template, pre-fill the units with the UOM of the attribute.
  • Guest
    Reply
    |     Aug 19, 2022
    In response to Roger Palmen, "That's a nice one! Or when enabling the ..." Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Guest
    Reply
    |     Aug 19, 2022
    Hi Roger, I suggested the use of a substitution parameter for this because this is how AF pass the dynamic information during the tag creation process. So the idea was just to keep consistent with the existing mechanism. Thanks for your vote!
  • Roger Palmen
    Reply
    |     Aug 19, 2022
    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
  • Asle Frantzen
    Reply
    |     Aug 19, 2022
    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
    Reply
    |     Aug 19, 2022
    I just ran into this again today using the Integrator for BA where i need to expose the UoM used for attributes...
  • Guest
    Reply
    |     Aug 19, 2022
    yes - this is a function we need to have please.
  • Guest
    Reply
    |     Aug 19, 2022
    there are too many work around that are not stable. this would be a really really helpful feature.
  • Guest
    Reply
    |     Aug 19, 2022
    This function is really needed to improve PI AF...
  • Guest
    Reply
    |     Aug 19, 2022
    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
  • Guest
    Reply
    |     Aug 19, 2022
    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%.
  • Guest
    Reply
    |     Aug 19, 2022
    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.
  • +38