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

RELATED IDEAS

Be able to add child attributes to attributes that use limit traits

Currently, if an attribute has a limit trait assigned to it, it cannot have child attributes. This seems somewhat arbitrary. Child attributes of attributes with limit traits would be useful for high/low warnings/alarms.
  • ADMIN RESPONSE
    Aug 19, 2022
    When AF attribute traits were designed, the guiding principle was that traits would be inherent "properties" of the attribute. Specifically the Limits traits were to facilitate easier visualization in our client product such as PI Vision. The use case would be: trend this measurement also the limits so that users wouldn't have to additionally find the limits. As such, traits have limitations by design as they are not treated the same as regular attributes. For example, there is no concept of attribute references (parent-child, composition, etc.) for traits. This request is to extend this concept to have either child attributes or (child) traits, for existing attribute traits. This request does not follow the original design principle for traits thus we have no plans to implement this request.
  • Attach files
  • Kenneth Barber
    Reply
    |     Aug 19, 2022
    For example, suppose that we measure tank level and temperature. Both level and temperature will have a Hi limit and a Lo limit. Each limit also has an associated alarm for when the limit was reached and an event (in the OPC A&E sense) for when the operator took action return the tank level to normal. We would probably want the tank to have its attributes arranged like this: Level ↳Hi _↳Hi Level Alarm _↳Hi Level Event ↳Lo _↳Lo Level Alarm _↳Lo Level Event Temperature ↳Hi _↳Hi Temperature Alarm _↳Hi Temperature Event ↳Lo _↳Lo Temperature Alarm _↳Lo Temperature Event Alarms ↳Hi Level Alarm ↳Lo Level Alarm ↳Hi Temperature Alarm ↳Lo Temperature Alarm Events ↳Hi Level Event ↳Lo Level Event ↳Hi Temperature Event ↳Lo Temperature Event However, this is currently impossible because attributes with limit traits cannot have child attributes and child attributes cannot belong to multiple parent attributes without duplicating the child attribute across all of the parent attributes.