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

PI AF Security - More Granularity Needed

It would be helpful if AF's security model was more granular. For example (and please correct me if I am wrong), the same settings that allow someone to add/modify UOMs in AF is the same setting that allow someone to change the AF Sever name. This particular case recently caused us some issues with a client as we needed access for UOMs and then later, someone unintentionally changed the AF server name, causing PI Vision to not be usable for a short time. This is a specific example, but in general, more granularity in the functionality of the PI system is desired.
  • ADMIN RESPONSE
    Aug 20, 2022
    You already have the ability to set security on the Unit-of-Measure Database independent of the PI AF Server security settings. In PI System Explorer, click on the 'Unit of Measure' tab so that the UOM Classes are showing in the tree. Then select the 'File/Edit Security' menu entry to edit the security settings for the 'Unit-of-Measure Database'.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Be aware that UoM's are defined server-wide, and not per AF Database. Therefore a change in UoM might also impact AF databases that the user is not authorized for. Although i agree there might be some more detailing that can be done, users with this level of access can do system-wide damage anyway.