Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No status
Created by Hobbe
Created on Aug 20, 2022

Function to retrieve Instrument tag

I want to have a function to retrieve a PI Tags Instrument tag in AF analytics
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Can you tell me what you would use this information for?
  • Hobbe
    Reply
    |
    Aug 20, 2022
    In response to Stephen Kwan, "Can you tell me what you would use this ..." Hi Stephen!   It is useful to bring information about which instrument tag is used in the opc source.   Therefore, if you see a faulty signal in  PI the operators can easily find the signal  inside the source.   As now you have to check that up in PI SMT and it takes some time.   Regards   Magnus
  • Guest
    Reply
    |
    Aug 20, 2022
    I would also like this functionality to be available. I want to extract the intrumenttag attribute from a Ping PiPoint, and set it´s value into a Write PiPoint so I can send it to our OPC server. It can be any other attribute, not just the instrument tag one.
  • Guest
    Reply
    |
    Aug 20, 2022
    Does the information in the InstrumentTag attribute change with time?
  • Hobbe
    Reply
    |
    Aug 20, 2022
    In response to Stephen Kwan, "Does the information in the InstrumentTa..." Hi Stephen!   Normally it should not change! But since we have not got an optimal naming convention we are constantly working to improve it.   Therefore it would be great to have this function.   Regards Magnus Holmbom   Från: Stephen Kwan Skickat: den 29 juli 2019 17:12 Till: Holmbom Magnus (GV-PP) Ämne: Re:  - Function to retrieve Instrument tag   PI Square   Function to retrieve Instrument tag new comment by Stephen Kwan View all comments on this idea
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi, I understand what you're trying to do. However, please keep in mind that AF/Analytics was designed to be a streaming calculation engine. We designed it assuming that users would use it as a way to perform calculations with a schedule, e.g. every time there is a new trigger event for the calculation or based on a clock schedule. What you're describing seems to be a manageability need that may not happen very often, i.e. not in a streaming fashion. Therefore, with the information that you have provided, this request would not be high priority for us.
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi Stephen, We would very much appreciate if this request gets prioritized. I have been in touch with OSIsoft account manager regarding this feature. We want to use Instrument tag information to cross reference other databases to pull metadata and safe operating limits etc. into AF. This is essential for optimal use of event frames. All other methods require lot of manual work or unnecessary extensive customization. Our scada tags change from time to time due to field works so maintaining them in AF manually is quite difficult. Given that some tag functions already exist, this seems like an easy Win!!. Regards, Manbir
  • MAMEDINA
    Reply
    |
    Aug 20, 2022
    I would like to see this as well. We have interfaces to other systems and sometimes we have system administrators from those systems that would like to check the underlying mapping(instrumenttag) for a PI Tag via the AF element using PI Vision - They may not have PI System Explorer and even if they did would need some training to show them how to perform the tag search. I would rather just make this information available as an attribute in the AF structure. There are already some related Point Attribute functions like TagExDesc and TagSource that provide similar information but recommending a TagInstrumentTag function to retrieve this information.