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

Status Declined
Categories User Experience
Created by Guest
Created on Aug 18, 2022

Better handle incompatible data type event in PI Vision trend

Scenario: Your company has a PI tag set up as string that primarily gets float values. It is a string because it sometimes contains messages explaining why a result was not obtained. The tag is set up as a double attribute in AF and plotted in Vision. This works fine unless a non-numeric value is encountered within the Time Range you are looking at. If this happens, the trend is blank and No Data is displayed. While PI annotations would have been a good use in this situation, it is difficult to go back and change this when you have many different tags with lots of historical data. It would be better if an incompatible data type event was handled like a system digital state and create a data gap instead. Workaround: Create an Analysis that uses the Double() function to convert events to double. This creates a Calc Failed event when the event can't be converted to double.
  • ADMIN RESPONSE
    Aug 18, 2022
    While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work the product needs. Thank you for your feedback, and please continue sharing suggestions for how we can improve PI Vision for you!
  • Attach files
  • Matt Voll
    Reply
    |
    Aug 18, 2022
    to reiterate a point above . . . one bad data point (coercion failure) will cause the ENTIRE trace to fail, whether its 1h or 30d. Regardless of whether that one data point should be handled differently, its seem rather problematic that one bad data point can cause the entire trace to fail