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 Declined
Product PI Connectors
Categories PI Connector for OPC UA
Created by Clint Ramsey
Created on Aug 20, 2022

RELATED IDEAS

OPC UA: allow historical data access

allow historical data access with custom time ranges, like OPC HDA
  • ADMIN RESPONSE
    Aug 20, 2022
    Thank you for your input. We are continuing to support PI Connector for OPC UA with stability and security releases. However, for feature enhancements, we are focusing our efforts on developing PI Adapter for OPC UA. While our current version of PI Adapter for OPC UA does not support history recovery, we are evaluating this functionality for a future release. If you have additional enhancement requests, please head to the PI Adapters forum and share with us there.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    How is that different that how it currently works?  It seems like tags that don't have current data for whatever reason (eg. power outage), start collecting data again without issue when new data is available.
  • Guest
    Reply
    |     Aug 20, 2022
    How is that different that how it currently works?  It seems like tags that don't have current data for whatever reason (eg. power outage), start collecting data again without issue when new data is available.
  • Clint Ramsey
    Reply
    |     Aug 20, 2022
    Hey Chris, the OPC HDA interface allows back-filling by entering a custom time range, ie start and end time.  The OPC UA Connector with historical access does not allow this; it starts back-filling at the last time it lost connection to the UA server, back-fills and then begins its realtime historical retrieval.  The customers would like the ability to back-fill using a custom timerange, like the OPC HDA interface.
  • Clint Ramsey
    Reply
    |     Aug 20, 2022
    Hey Chris, the OPC HDA interface allows back-filling by entering a custom time range, ie start and end time.  The OPC UA Connector with historical access does not allow this; it starts back-filling at the last time it lost connection to the UA server, back-fills and then begins its realtime historical retrieval.  The customers would like the ability to back-fill using a custom timerange, like the OPC HDA interface.
  • Guest
    Reply
    |     Aug 20, 2022
    How is that different that how it currently works?  It seems like tags that don't have current data for whatever reason (eg. power outage), start collecting data again without issue when new data is available.
  • Clint Ramsey
    Reply
    |     Aug 20, 2022
    Hey Chris, the OPC HDA interface allows back-filling by entering a custom time range, ie start and end time.  The OPC UA Connector with historical access does not allow this; it starts back-filling at the last time it lost connection to the UA server, back-fills and then begins its realtime historical retrieval.  The customers would like the ability to back-fill using a custom timerange, like the OPC HDA interface.
  • Guest
    Reply
    |     Aug 20, 2022
    How is that different that how it currently works?  It seems like tags that don't have current data for whatever reason (eg. power outage), start collecting data again without issue when new data is available.
  • Clint Ramsey
    Reply
    |     Aug 20, 2022
    Hey Chris, the OPC HDA interface allows back-filling by entering a custom time range, ie start and end time.  The OPC UA Connector with historical access does not allow this; it starts back-filling at the last time it lost connection to the UA server, back-fills and then begins its realtime historical retrieval.  The customers would like the ability to back-fill using a custom timerange, like the OPC HDA interface.
  • AM(CSL)
    Reply
    |     Aug 20, 2022
    Agree with Clint Ramsey. The feature to allow history recovery with custom time-range will help in recovering history that the connector is not able to cover, for example: time-sync issue between the connector and source that may cause the connector to miss the actual period where data was missing. The connector uses its own machine clock to recover history and the process could fail if the timestamp from source is leading or lagging. Can it be made that the connector uses the last timestamp from source? Please consider the improvement for the PI Connector for Siemens PCS7 as well.
  • FranzK
    Reply
    |     Aug 20, 2022
    Is there an update on this topic? As classic OPC is making more and more problems (insecure, not stable due to patches), an OPC UA based solution is urgently needed! It would already be OK, to define for example based on a filter file, which tags only have to use HDA communication. How about the adapter? As far as i understood, it still doesn't support pure HDA mode (e.g. based on a trigger tag like the OPC HDA Interface).
  • Gabriel Verreault
    Reply
    |     Aug 20, 2022
    @FranzK For the OPC UA Adapter, you can perform history recovery for a specific time period and/or configure it to perform automatic HR on startup. You cannot perform it based on a trigger tag like OPCHDA, since the adapter does not read data from the destination PI/OCS/Omf Endpoint and therefore would not be able to detect a change in the trigger tag. You can see the following for details: https://docs.osisoft.com/bundle/pi-adapter-opc-ua/page/main/shared-content/configuration/history-recovery.html https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000032182