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 UFL
Created by Kenneth Barber
Created on Aug 18, 2022

RELATED IDEAS

Incoming TimeStamps Utc

Please rename "Incoming TimeStamps" to "Incoming Timestamps". Please change "Utc" to "UTC". These small spelling issues come across as sloppy.
  • ADMIN RESPONSE
    Aug 18, 2022
    Thank you for your feedback. Unfortunately, we were not able to include this request in a released version of the product and currently do not have plans to include it in a future release.
  • Attach files
  • Guest
    Reply
    |     Aug 18, 2022
    I am neutral on the idea but would like to dispel the notion that these are necessarily spelling mistakes or from sloppiness.  There is a justification/history behind each spelling.  For instance, TimeStamp was the spelling used for PIValue.  And Utc is frequently spelled as-is throughout Microsoft's .NET Framework such as with UtcNow, UtcOffset, UtcTicks, etc.  My comment is not to diminish your submitted idea.  The vote should be based on preference going forward, but do understand that either spellings are acceptable within given contexts.
  • Kenneth Barber
    Reply
    |     Aug 18, 2022
    The context that you are talking about appears to be programming. The context that I am talking about is UI. To me, it doesn't make sense to use programming spelling in a UI, especially since most PI administrators aren't programmers. For UTC, it is programming convention to only capitalize the 1st letter of acronyms if you are using camel case, which produces the Utc spelling. Outside of camel case function and variable names, no one uses Utc.