AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Add a new idea Subscribe
Status Completed
Product AVEVA™ Adapters
Categories General
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

Enable adding prefix to health & diagnostic PI tags

We make use of strong naming convention for all our tags, using sets of prefixes/sufixes to properly position our PI tags in AF hierarchies. We are making use of the PI Adapter against the PI WebAPI endpoint. Now with the PI Adapter health & diagnostic PI tags that are auto-created when 'EnableDiagnostics' is set to "True" in the auto-created AF DB for this purpose, the auto-naming of these PI tags does not permit a configuration of the naming using a set of prefixes that would help us locate better in our data landscape the position of the PI Adapter. What we need is to be able to in further PI System Monitoring AF models to be able to re-use these PI Adapter health & diagnostic tags efficiently using substitution params in order to easily create analytics and visualization against AF Elem templates to monitor the whole PI Adapter fleet (potentially hundreds). Without this prefix we have to map each PI tags manually to the correct AF attribute for our PSM purposes, which is absolutely against our good PI practice in terms of creation and maintenance.
  • Attach files
  • Admin
    Jiyeon Hwang
    Reply
    |     Jan 12, 2023

    With recent releases of Adapter for OPC UA (v1.2 and onward), users have the option of specifying an optional HealthPrefix to be applied to health and diagnostics streams and asset IDs. You can find this information in our product documentation, under the "Configuration > Diagnostics and metadata" section: https://docs.osisoft.com/bundle/pi-adapter-opc-ua/page/main/shared-content/configuration/diagnostics-and-metadata.html. If this does not fulfill your needs, please share your use case in more detail with us.

  • Guest
    Reply
    |     Aug 16, 2022
    We make use of strong naming convention for all our tags, using sets of prefixes/sufixes to properly position our PI tags in AF hierarchies. We are making use of the PI Adapter against the PI WebAPI endpoint. Now with the PI Adapter health & diagnostic PI tags that are auto-created when 'EnableDiagnostics' is set to "True" in the auto-created AF DB for this purpose, the auto-naming of these PI tags does not permit a configuration of the naming using a set of prefixes that would help us locate better in our data landscape the position of the PI Adapter. What we need is to be able to in further PI System Monitoring AF models to be able to re-use these PI Adapter health & diagnostic tags efficiently using substitution params in order to easily create analytics and visualization against AF Elem templates to monitor the whole PI Adapter fleet (potentially hundreds). Without this prefix we have to map each PI tags manually to the correct AF attribute for our PSM purposes, which is absolutely against our good PI practice in terms of creation and maintenance.