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
Categories Event Frames (EF)
Created by dgenet
Created on Sep 26, 2025

PI EF security trait/context

We are trying to standardize and mutualize all of our templates but we want to keep the security well defined : in general it work perfectly when things are in read only mode.

Where write access is needed everything looks good for Elements since the security is redefined for each tree node.

But when we are working with event frame it is a big mess because the security is derived from template :

  • We cannot use a single event frame template that have exactly the same logic for all the site but security context different.

  • We don't want to have user writing to elements, but just to a specific attribute in the event frames not all.

a good improvement would be to define the security settings for ef template but add one additional layer :

  • EF context security : we can define one per site: and for a specific element depending on the value of this security context the security of all the EF generated by analysis have this security layer applied.

This idea would be applicable to aknowledgment but also attribute edition, and all other rights

I know there is the possibility to create child template per site : but it is not like this that we would push end user to standardize and rationalize the number of templates.



  • Attach files
  • MAl
    Sep 29, 2025

    If I understand correct, the proposal is adding the possibility of making the event frame inheriting the security from the primary Element instead than from the template. Is it so (good idea)?

    Thanks