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 Declined
Product PI Connectors
Created by Guest
Created on Aug 20, 2022

Retrieve data even it's not changed on OPC server

Currently Connector configured to rertieve event on change and not based on a scan class like interfaces.The Connector suscribes to the changes, and when a change comes in to the server, the data will be sent to PI connector. We need option to retrieve the data every certain minutes even data is the same and is not changed on OPC server. Saken TCO
  • Attach files
  • Admin
    Alan Izar
    Reply
    |
    Jul 16, 2024

    Declined - At the time we will not be implementing this idea since it does not align with our current data collection strategy. This feature is now available for Adapters.

    1 reply
  • JacobRoth
    Reply
    |
    Jul 11, 2023

    Agreed with the comment: "At least at Startup the connector should poll all the data one time."

  • asanzacedo
    Reply
    |
    Nov 10, 2022

    It would be really good if the connector retrieves and updates current data on startup

    Otherwise we face issues when a value changes its qualiy but not the value itself or the timestamp and we stick with an incorrrect value en PI as long as that signal does not change on OPC UA server

  • Guest
    Reply
    |
    Aug 20, 2022
    Since it also has to do with unchanged data updates, allow "exception reporting" capabilities where a tag can mimic trend-like behaviors, which are useful for things such as Set Points.
  • Guest
    Reply
    |
    Aug 20, 2022
    This functionality is necessary for Industry, we had it using one concurrent product, I hope you will implement it asap.
  • Gabriel Verreault
    Reply
    |
    Aug 20, 2022
    This functionality is available in the PI Connector for OPC UA version 1.3.x - available on the Tech Support website. Look for DataChangeTrigger in the User Guide. It explains how to set a subset of tags to update everytime the timestamp updates. In conjunction with SamplingInterval, you can define the data retrieval rate, and when is the data going to be sent to PI.
  • suyp
    Reply
    |
    Aug 20, 2022
    If I understand this correctly, the solution provided by PI Connector for OPC UA version 1.3.x requires you to maintain a csv file with all your opc server tags. That is impossible when your opc server have over +100K tags.
  • Guest
    Reply
    |
    Aug 20, 2022
    We have same issue with that. Most times it makes sense to ASK OPC Server to get actual values for some specific tags just to check, if connnection is alive or broken. It is not unusual that something is going wrong on the connection and we can't see if values are reliable or not.
  • Guest
    Reply
    |
    Aug 20, 2022
    We have a requirement to Test existing PI Tags getting data from OPC UA Server through PI Connectors (1.3.0.130). Since the OPC UA Server is also in Testing phase so no new data can be generated on it. What would be the best way to test my connection if the Status, Timestamp and Value of OPC UA Variables doesn't changes? Even getting one event from OPC UA Server to the corresponding PI Tag will result in successful connection.
  • Guest
    Reply
    |
    Aug 20, 2022
    At least at Startup the connector should poll all the data one time.
  • MartinRiemer
    Reply
    |
    Aug 20, 2022
    This feature is very important to us as missing one event in case of a Setpoint which gets only changed infrequently, would lead to have wrong information in PI until the Setpoint is changed again (might be weeks or month). As we use the PI System for GMP BatchReporting where setpoints play an important role, wrong data would invalidate our documentation. So we would like to introduce a "Scan every x seconds" on a Tag basis. Maybe in the TagNamingWorkSheet used in TagsOnly Mode. By specifying the scan rate per Tag the additional load / traffic could be limited to where needed.
  • Guest
    Reply
    |
    Aug 20, 2022
    Remaining BAD value after resolving issues.