Skip to Main Content
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.

Status In development
Product PI Connectors
Created by Guest
Created on Aug 20, 2022

Do not synchronize description from OPC UA server into PI Tag

There are situations when customer prefers to use “description” in PI Tag attribute that is independent from item “description” provided by OPC UA Server.   Currently, during each synchronization, the OPC UA Connector synchronizes descriptor from OPC UA to PI Tag and overwrites desired “Descriptor” attribute provided by customer.  Although the solution would be to have desired description already on the OPC UA Server, in some situations (OPC Server managed by 3rd party) it is not possible. It would be good to have configurable parameter in OPC UA Connector, which disables synchronization of item description from OPC UA Server to PI tag.
  • Attach files
  • sahilp
    Reply
    |
    May 7, 2024

    Hi,

    The item is now marked "In development". Can someone from AVEVA please provide an expected completion date?


    Thanks,

  • sahilp
    Reply
    |
    Nov 23, 2023

    The same idea needs to be implemented in the adapter, or at the time of migrating all the connector users will be back to square one.

    https://pisystem.feedback.aveva.com/ideas/PIADAPTERS-I-36

  • Guest
    Reply
    |
    Mar 28, 2023

    Please fix this. You can't expect SCADA descriptions to always be useful for the end users. I understand the power of the OPC UA server being able to hold all this meta data. But PI being a separate client that extracts the data should have the ability to choose whether or not it wants any of that information.

  • Julian Shearing
    Reply
    |
    Aug 20, 2022
    We have a slightly different use case. It's fine to synchronise but we need the ability to turn it off after the connector has built the initial setup. Our problem is when buying off the shelf equipment we have no control over how the vendors present the data. The built in OPC server to the equipment may not be configured in a way that is user friendly or even complete. We could of course resolve this by requesting customising of the source system but that leads to considerable increases in complexity and cost and some vendors are not prepared to entertain doing it! Therefore the ability to synchronise the initial build and then turn off the auto update and complete the build in PI would be really helpfull
  • Guest
    Reply
    |
    Aug 20, 2022
    Another use case is you connect to a Control System via OPC UA The description in the control system is too generic e.g. the Control System has a connection to anther system and just has all the tags with the same description. Therefore you would want to have different description in PI.
  • Guest
    Reply
    |
    Aug 20, 2022
    This is very critical functionality for many customers. OPC UA is the preferred way of connecting control system in coming days and industry 4.0 and other program like Open Process Automation have very high dependency with OPC UA . This is must to have idea where we need OSIsoft Support to enable functionality on choosing not to have auto update for Description and Eng-Unit.
  • Guest
    Reply
    |
    Aug 20, 2022
    This behaviour happens also with "step" attribute on the PI Adapter for OPC UA. In particulart this happens every time Adapter is restarted or history recovery is performed. The workaround is to have desired "description" already on the OPC UA server but in some situations (OPC UA server managed by 3rd party) this is not possible. It would be good to have configurable parameter in OPC UA Adapter and Connector, which disables synchronization of "description" and "step" attributes from OPC UA server to PI tag.