Skip to Main Content
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.

Status No Status
Categories Event Frames (EF)
Created by Guest
Created on Aug 20, 2022

Store event frame start and end time as DateTime to allow sub-millisecond duration event frames

Because event frame start and end time are stored as a bigint datatype in PIFD.dbo.AFEventFrame, the precision only seems to be to the nearest millisecond. This is a problem for sub-millisecond event frames. Why aren't event frame start and end times stored as DateTime datatypes?
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi, can you provide some example use cases? What type of events are you trying to capture with event frames?
  • Asle Frantzen
    Reply
    |
    Aug 20, 2022
    Hi Steve. Ben created this feedback item for me. We're doing a project for a T&D company, and they have done a large IoT project together with some partners. The project aims to give extra insight in their switchgear operations with all the benefits of inexpensive, stand-alone sensor units, which can be retro-fitted to any circuit breaker, disconnector, earthing switch, etc. Their transmission system is relatively stabile, resulting in not many switchgear operations. If one operation occurs at a circuit breaker, it could easily be a year until the next operation (or they could occur back-to-back for a few repetitions). Once something happens, they record everything - and need to do it with precision. An operation may result in 10 000 values, and a whole motor current event may have a duration of 200 ms. This is my event frame! In the case I reported to techsupport, I'm missing 11 out of 12 values occuring within the last millisecond of the event. That is, between 2019-11-27 14:26:33.0340000 and 2019-11-27 14:26:33.0349167. The latter timestamp is the end time I'm trying to set, but both PI System Explorer and AF SDK simply truncates everything less than 1 ms. Had it actually rounded the number up to .035 all my time series data would have been included, so that's what I'll be doing programmatically now.
  • Guest
    Reply
    |
    Aug 20, 2022
    Thanks Asle, we'll look into this.