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
Created by Guest
Created on Aug 20, 2022

Mapping of event frame analysis variables to element attributes

It should be possible to map variables in event frame analysis to element attributes.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Holger, need some more details please. Not sure what you're asking. Can you provide an example?
  • Guest
    Reply
    |
    Aug 20, 2022
    In an expression analysis I can map a variable to an output attribute. In an event frame analysis (in AF version 2017 R2) I can define an output expression that can be mapped to an output attribute in the event frame. But I cannot map normal variables of event frame analyses to an output attribute (in the element). Currently I have to create two analyses to do this. First one is an expression analysis with the output attribute mapping and second one is the event frame analysis using the attribute.
  • Guest
    Reply
    |
    Aug 20, 2022
    Regarding this comment: "But I cannot map normal variables of event frame analyses to an output attribute (in the element)." Would you want this to be executed when the event frame triggers (creation time)?
  • Guest
    Reply
    |
    Aug 20, 2022
    Interesting question: I think it should be executed every time the event frame analysis is triggered and not only when the event frame is triggered.But that could be an interesting option.
  • Guest
    Reply
    |
    Aug 20, 2022
    This is especially useful in event frame generation for notifications. This way you could show intermediate variables used in the trigger conditions in the notification.
  • Guest
    Reply
    |
    Aug 20, 2022
    An additional idea for notifications: add an output expression "at start" to event frame analyses to have the possibility to show trigger relevant info in the notification.
  • Guest
    Reply
    |
    Aug 20, 2022
    Holger, might be better to separate out your suggestions into multiple ones as it's impossible to keep track of multiple requests in the same post. Regarding your latest request. When you configure the EF generation analysis, the Advanced option gives you a way to write the the start trigger name and/or start trigger expression to an EF attribute. The thinking here is that if you know the start trigger name and/or start trigger expression, it's likely that you can figure out what triggered the EF creation. Hope this helps.