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 No Status
Product PI Interfaces
Categories PI to PI Interface
Created by Guest
Created on Aug 17, 2022

RELATED IDEAS

Add functionality to the interface to adjust timestamps by a configurable amount

This enhancement would add the ability to adjust timestamps to the PI to PI Interface (Beyond the included options for clock drift and subseconds). Potentially, a setting could be supplied to change the timestamps on all data transferred by a specified number of UTC seconds. This setting should be accompanied by a warning message in ICU and the message logs so that the implications of the setting are understood.
  • Attach files
  • Laine
    Reply
    |     Aug 17, 2022
    We have a third party application that processes our individual plant locations’ environmental data and it requires a 00:00 timestamp. Each local location’s PI server sends data to the corporate PI server which is Central Time and the third party application then consumes the data. The 00:00 timestamp does not pose an issue for the local PI servers that are also Central Time, however in this particular case the local PI Server is Mountain Time an hour behind Central. Being the tags are from AF analyses I do have the option to adjust the timestamp relative to trigger time for some of the tags but this may not always be the case; plus the local locations also use the data and desire a 00:00 timestamp as well. I will eventually have issues with Eastern sites which are an hour ahead of Central. Are there any other options (interface/ tag configuration) other than adjusting the AF timestamp relative to trigger time to force the timestamp to be 00:00 central time which would be 22:00 for the previous day which would not work for local usage