Ideas

I want to separate the security roles between 1) the ability to run an Auditviewer report and (potentially) associate a change control record to a configuration change and 2) the PI Admin Role in order to minimize security risk.

Currently, there are 2 windows to configure PI AF security, and it is a pain to switch between them: File → Database → Edit Security, which is used to assign permissions to identities File → Server Properties → Identities tab and Mappings tab, whi...

As an user, I want to be able to query web services using a fully support attribute data reference so that I can get the information I need from web services without having to write my own custom data reference.

As a user, I want to be able to view AF element connectivities using a graph view rather than a tree, so that I can see more relationships between elements than just parent-child as in a tree.

As AF Admin, it would be helpful to be able to archive and track the Database Property Count as a PI Point/Attribute to track the progress of AF deployment

Security setting for an identity must be sen in the PI server and AF should get that. Why create additional identities in AF as well. Duplication creates risk for errors and requires additional maintenance.

A frequent  PI Square problem regards using StringBuilder DR on event frames and the user wants to see the referenced element's attribute at the StartTime of the event frame.  Something like a TimeRangeMethod or  UseStartTime flag w...

PI AF shows who created and last edited an element, but does so by showing the user's ID in format "Domain\UserID" which is not always readable. It would be better to display the AD user's display name in these places to make it clear who performe...

With multi-user AF Servers, it is not unusual for a UOM to end up in the wrong class.  Currently, fixing this issue is not trivial.  If you try to delete the UOM from its current class so it can be recreated in the correct class, you get...

It's possible to inadvertently change the tag attributes for production tags if they are used with an attribute that has tag creation set. It would be safer if there was a lock that allowed new tags to be created, but blocked tag attribute changes...