When creating PI points through AF Templates, there should be an option to "Write Default Value after Point Creation", or some other way to initialize the value of an automatically created PI tag.

Right now, there is no way to replace the Pt Created value with a default value upon creation, and the "Default Value" in the AF Template serves no real purpose for PI Point Data References.

Use category of an attribute for the name substitution parameter of the PI point data reference

substitution parameters

Currently managing attribute templates which can create tags is very laborious. It is an issue particularly when dealing with different security settings for tags. Improvements suggested would include

• have the ability to create and maintain multiple 'profiles' or templates for tag creation - which for example might be used where different tag security settings are needed
• enable the ability edit an attribute template's PI Point creation settings in PI Builder

AF Templates should show creation and modification dates and creators and changers. Currently AF Elements show creators and modifiers, but AF Templates do not show this information in PI System Explorer. This would make it more obvious when changes happened, without having to dig through the audit logs.

Adding an identity to an established large system can cause a flood of change records, leading to performance issues.

The AFDiag /AddIdentity feature will bypass this issue, but it would be more convenient to have this functionality included in PSE.

The feature introduced in 2018 SP2 to manually synchronize digital state sets with AF enumeration sets has a limitation where state sets with duplicated names aren't imported correctly into AF. This is due to the current design of AF enumeration sets that don't allow duplicated names for enumeration values. It would be nice if AF enumeration sets supported multiple values with the same name as it is supported in digital state sets in the Data Archive.

Effective Access tab in PI System Explorer supports checking for users in another trusted domain.

Currently there are 7 standard limits available to be used as limit traits. However there are situations where more than 7 are required. Users would like an option to create additional limit traits rather than having to manually configuring additional intervals in PI Vision multi-state.

Currently to view the Audit Trails of any object on an AF Server, Server level Administrator privileges are needed.

There should be the ability for a user that does not have server level administrator to view the Audit Trails of a specific object or Database they have Administrator privileges over.

This is really a bug/security risk; but the support team has requested that a "Customer Voice" be raised.

Support passwords longer than 15 characters in the PI AF Table Connector.

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 would be helpful.  Perhaps even detect the DR is used on an event frame and default UseStartTime to True.

As a PI AF administrator or power user, I would like to be allowed to continue loading content from a server library into a database, even if a UOM conflict is detected.

Upon finding a UOM conflict, the library import feature does not allow me to ignore the error and continue loading the content (screenshot1.png), in contrast with the file import feature (screenshot2.png).

Tech Support case #00957957 concluded that this was not a bug.

Currently when viewing Time Series Data for a numeric attribute value type (e.g Double, Single) in PI System Explorer, sorting the value column will sort the results alphabetically (e.g. 1, 10, 2, 20, 3...) and not by size (e.g. 1, 2, 3, 10, 20). PI System Explorer should be able to sort Time Series Data for a numeric attribute by the size of the value in addition to or instead of the alphabetical order of the values as strings.

It would be nice if the UOM field of an AF Attribute would accept substitution parameters. This way if an attribute is a reference to another, the UOMs could also be linked. If the UOM is updated on the source, it would also get updated in the reference.

It would be nice to have a substitution parameter to fetch the name of a base template. There is a substitution parameter to retrieve the name of a template: %Template%, but none to retrieve a parent/base template.

When looking at element attributes or event frame attributes in PI System Explorer I would like to see [string1, string2, string 3] for the value field of an array attribute, instead of "String Array" as we see today.

When you quickly check out the current values of an EF or element, it much easier to recognize the values you're looking for if you see (a preview of) it directly in the Values field for the attribute.

"Hiding" it under the "String Array" key word makes it more difficult to spot!