When you have thousands of tags in your Data Archive, you need to know wich tags are beign used and witch don't. It would be very usefull to have some diagnostic that shows wich tags are being cosumed more and from wich client.

Having more thorough and detailed messages for the Analysis service in the event logs, especially upon startup.

Environment details + Language settings that the Analysis service is using should be mentioned in the startup logs in order to better troubleshoot configuration issues without needing to go through a trial and error process.

It is possible to search for Templates, Elements and Attributes, however the only way to obtain Analyses is to perform a full Element search then filter out the Analyses columns.
I have an extensive AF structure with many 100,000 rows. It would be useful for such large AF structures to be able to search for Analyses in the same way that you can search for Elements or Attributes.

As other vendors do, offer customers the option to purchase extended support for PI ProcessBook for security updates only past 2022 for at least one year, and reevaluate annually based on number of customers interested.

This would only apply to security-related fixes, not enhancement or other functionality updates.

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.

I would like to be able to reference the parent of a element reference. As it currently stands, it is only possible to reference the original parent element of an element.

Transfer Saved searches: This option will allow transferring event frames "saved searches" from one computer to another. For customers who have many search criteria, it is time-consuming to rebuild again on another PC.

It is not possible to download just the PI Event Frames Interface Manager. Request to download PI Event Frames Interface Manager by itself similar to how PI ICU is treated. This would allow users to obtain bug fixes in the PI Event Frames Interface Manager without OSIsoft having to release a new version of every single batch-type interface.

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.

PI Interface for OPC DA has a plugin called "Time Array" to manage numerical arrays but string arrays are not supported.
It would be a good improvement to develop this feature for string arrays.

When mouseover on a output attribute analysis icon the analysis is displayed in the tooltip on a single line. The analysis will quickly become unreadable.

It would be nice if the analysis could be presented in a readable way.

It would be very intesting to access tuning parameters (that are present in PI SMT) via AFSDK.
This is interesting when you have to manage dozens of PI DA servers and you want to ensure they are all correctly configured (and no change are performed locally for example).
Thanks a lot!

Ability to allow extensions in PI AF Analysis template, in order to modify specific element analysis.

In an HA environment, if the primary Data Archive is unavailable it would be helpful if the Interface Configuration Utility could read the interface configurations from the MDB on the secondary. Additionally, could it be configured so that any changes made to the interface configuration could be cached until the Primary Collective member becomes available?

Our process is writing an array of strings into an AF attribute of the same type. This AF attribute may receive information of different size (index) in time.
We need to extract all the information contained in the string array (all the items) and store it in a PI tag of type string so it can be viewed in PI Vision or any other client.
Since there is no For-Loop function in ABA, we need a new array operation (for example GetStringContent()) to based on an event or periodically store this complete string in a PI tag.