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

RELATED IDEAS

Allow Access to Analysis Variable Values in Notification Rules

I tried to look but didn't see this requested. It would be very useful if the values of the variable(s) created in an Analysis could be accessed from the Manage Formats page of a Notification Rule. I know you can create output attribute and map the output of an Analysis to an attribute, then reference that from the Manage Formats page. However it would be much better if any variable created in the Analysis that is tied to the Notification Rule could be accessed when creating the email format. This would provide an easy way to for example create a variable for 1 hour average of a tag and then be able to include the value of this variable in the email. If for example the Content section of the Manage Format page would have a section called "Referenced Analysis Variables" that once expanded would include the variable names of all variables created in the referenced Analysis. Then could drag and drop the variable value(s) and/or timestamp(s) into the email message the same way you can the other referenced properties of the items.
  • Attach files
  • jmjackson
    Reply
    |     Aug 20, 2022
    Posting a comment in hopes that someone will see this. I feel like having the functionality above would save me a ton of trouble and make things so much easier to setup.
  • Guest
    Reply
    |     Aug 20, 2022
    Hi, rest assured that the product team at OSIsoft sees every single comment/updates that flow through this feedback website. While we're on this particular topic, I want to make sure I understand what you're asking. Notification rules are typically tied to an event frames analysis. When you say "variable", are you referring to variables that you create as part of the event frame analysis? Please confirm.
  • jmjackson
    Reply
    |     Aug 20, 2022
    Thanks for the reply. Yes, I am referring to the Variables that you add to an Analysis from the Add... hyperlink then select Variable from the drop down window. An example of what i am referring to is if you add a variable and for example calculate the average of a tag over an hour (TagAvg('TAG', '*-1h', '*'). You can use this variable in the StartTrigger1 which is great. But it would be nice to reference the value of this variable from the Manage Format page in the Notification Rule. If could do this then could put the value of this variable with the TagAvg function in the email body. This way could include the average that was used in the StartTrigger1 that initiated the message. I guess the way to do something similar currently is to create an Analysis of type Expression, or add an Output Expression to the current Analysis, and map the result to an Attribute, then can use the attribute value in the Manage Format page when setting up the email. I just think the variable option would work better and wouldn't have to create a ton of extra attributes on the element to store the calculated values that want to add to the email.
  • Guest
    Reply
    |     Aug 20, 2022
    The benefit of using an Output Attribute is that you can historize these values, but I can see how your suggest may be useful. As a matter of curiosity, if you had to create output attributes, how many would you need to create?