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 No status
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by taterhead247
Created on Aug 19, 2022

RELATED IDEAS

Value Retrieval Method should read integer value of Digital tag, not string

If you try to do Value Retrieval Method (like Min) of a Digital type tag, you will get an error saying non-numeric data. AF should be smart enough to realize that the data is actually a set of integers and not try to read the string representation.
  • Attach files
  • Gregory Malek
    Reply
    |     Jan 13, 2023

    I support this idea. The numeric order of the states does not necessarily have to apply to any real-world scenario for this feature to be valuable. Things like averages and totals for binary 0/1 attributes would be extremely useful for things like downtime % and fault count.


    If there is an issue with the states' numeric order not reflecting any real-life sequence, then the end user can account for this in their analytics. Such a concern should not discourage development of this feature.

  • Rick_Davin_3.0
    Reply
    |     Aug 19, 2022
    I would vote against this idea. While it is possible to create a state set where the numeric order aligns with a notion of "min" and "max" for states in relation to each other, this is not a requirement of state sets. I have seen some state sets where a given state is not higher than or lower than another - it just happens to have a certain integer code that may be greater than or less than another. In the purest sense, digital state sets are simply a finite set of choices that happen to be stored by some integer. Just like with SQL table keys, that integer is not supposed to be meaningful data.