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

RELATED IDEAS

Improve the AFDatabase security model

Please remove the database level write access requirement to modify objects below the database level. This will: 1. Prevent users who should only have subobject write access from modifying the database. 2. Make the security model more intuitive for our users. If you want to edit ElementA, you need write access to just ElementA. Although the current model provides a quick mechanism to shut off write access, I can already achieve this by reassigning user identities.
  • ADMIN RESPONSE
    Aug 19, 2022
    This is in PI Server 2017 R2, available now on https://techsupport.osisoft.com/
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    It seems to me that there is still a bug. We have an AF structure Elements/Calculations/TagCheck (with several sub nodes). I want to give an identity the right to modify elements of TagCheck. Now it is not sufficient to give the identity write access to TagCheck. I also have to give the identity write access to the top "Elements" node.
  • Guest
    Reply
    |     Aug 19, 2022
    There was a problem in PI System Explorer where it was not checking security correctly which has been fixed in the upcoming 2018 release.