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 Batch Interfaces
Created by Guest
Created on Aug 17, 2022

RELATED IDEAS

Batch Framework Interfaces - [TIME] placeholder should consider whether TS=LCL is configured

Batch Framework Interfaces - [TIME] and [TIMESTAMP] placeholders should consider whether TS=LCL is configured (meaning the interface is processing incoming events as Local Time). Currently, values of these placeholders always show up as GMT timestamps.
  • Attach files
  • lafound
    Reply
    |     Mar 18, 2024

    As part of the resolution to making the placeholders [TIME] or [TIMESTAMP] consider TS=LCL, could it also be allowed for the interface to optionally create an Event Frame Attribute for them as a ‘Date/Time’ datatype instead of a string? I think that could be most preferred, if possible, as client applications (like PSE) would then be able to display the timestamp stored as a value in local time when reading the data, much like the event frame timestamps.

  • lafound
    Reply
    |     Dec 6, 2023

    Please fix this feature as it severely limits the use cases for those placeholders.

  • Tim Proeber
    Reply
    |     Oct 12, 2023

    I was surprised that the command line /ts did not work. PLEASE fix this.

  • Navanita
    Reply
    |     Aug 17, 2022
    In destination data, Child event attributes shows Date and timestamp field with UTC timestamp instead of Local timestamp.