AVEVA™ PI System™ Feedback Portal

Welcome to our 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 AVEVA™ PI System Access (PSA)
Categories PI AF SDK
Created by Guest
Created on Aug 23, 2022

RELATED IDEAS

Allow decimal representations of days, months, and years in time strings

PI Time offsets only allow for integer numbers of days, months, and years. For example, *-1d is allowed, but *-1.5d is not. Hours, minutes, and seconds allow decimals. There are a number of client tool situations where the customer would like to offset by a decimal number of days; in these cases, they will need to convert to hours before proceeding.
  • ADMIN RESPONSE
    Aug 23, 2022
    We cannot use fractions in many cases due to variability. For example, DST, leap year, # of days in a month, etc. From our documentation for AFTimeSpan.Add: “Intervals year, month, and day do not allow fractions because they are variable length. For example, adding a fraction of a month would require choosing between a month containing 28, 29, 30, or 31 days.”
  • Attach files
  • Guest
    Reply
    |     Aug 23, 2022
    Reluctantly voted up. Looking at the original PI Square post, i am wondering what the implications should be for computing 0.5 month or 0.5 day. As consistency across applications is KEY (it is already not consistent, leading to frequent mishaps), we have to make sure the rules are simple and consistent across all applications.
  • Guest
    Reply
    |     Aug 23, 2022
    Reluctantly voted up. Looking at the original PI Square post, i am wondering what the implications should be for computing 0.5 month or 0.5 day. As consistency across applications is KEY (it is already not consistent, leading to frequent mishaps), we have to make sure the rules are simple and consistent across all applications.