Consistency among tag search GUIs within client products (PI Builder, DataLink, SMT, ProcessBook, etc.)  The search in PI Builder has limited functionality and would be nice to have the same search GUI as used in SMT and ProcessBook.

Currently in PI System Explorer we can search for Event Frames based on Element Name. However, it would also be good to have the option to also search for Event Frames belonging to child Elements of that specified Element.

For example, if you have a Parent Element for each of your sites or sub-sections within a plant and you would like to see all Event Frames for all assets belonging to that site or sub-section then you can select the option to include child Elements in the Event Frame Search.

PI System Explorer should show the last time an analysis went into error on the Management tab.

We have some data analyzers in the DCS system that provide results to PI tags in a delayed fashion.

Sample use case:
(t+0s) valve closes,
(t+30s) measurement1 sent to the DCS tag m1
(t+60s) measurement2 sent to the DCS tag m2.

We need to trigger a analysis off of the valve closure, but we need  Sleep(30) command in the analytic, or the ability to set per-analytic delays, so that some are delayed by 30 or 60  seconds.

Or is this possible today by other means?

Include event frames root cause data into Notifications message. A customer ask about how to include event frames root cause data into notifications message because he has a notification message generated when an equipment fails but to diagnose the cause of fail he has setup a root cause event frame and he needs to see this root cause data into notifications message.

When retrieving all PI points, there should be an option to also include the Snapshot value. Currently, a user must use other means to retrieve all current values and then merge the two together.

I am unable to implement Audit Trail due to the performance implications associated with auditing my entire server. Being able to audit very specific attributes, elements, or trees would allow me to take advantage of the Audit Trail feature in a practical way.

I want the ability to audit attribute changes with the following details:
* old value
* new value
* timestamp
* user

There should be an easy way to change the default value of the shutdown flag for analysis output PI Points. Right now, the default value is True, which means my analysis will show a "Shutdown" value every time I restart my PI Data Archive. The easiest way to modify it right now is in the attribute configuration and we can't easily use PI Builder to modify this parameter.

An AF attribute with a data type of String Array and a data reference of table lookup retrieves multiple values from an imported table (number of rows always vary). Would like to get the content of the string array in the body of the Notification or provide a URL link to a PI Vision display with the content of the string array.

As a user of Asset Analytics I would like the UOMs to be consistent and meaningful throughout the calculations that might involve various complex operations so that the written output values are meaningful and with the correct units.

Currently, AFUpdatePlugInConfigurations.exe will update the Attribute configurations of an entire AF Database as specified in the /Root parameter.  When dealing with large AF Databases where there were only a few changes made, this is an expensive call.  Please modify the /Root parameter so we can specify which Element and whether Child Elements (/IncludeChildern) are included should be in scope of the update.
 
Example:
C:\Program Files\PIPC\AF\AFUpdatePluginConfigurations.exe "/Root:\AFServer\AFDatabase\ParentElement\ChildElement" /IncludeChildren /CreateConfig
 
Cheers!

If there are no zeroth state needed for this type of operation then I don't see the need for the triggering input to be tied to a Digital State Set.

I believe the rather complex process of migrating from the legacy version of PI Notifications to PI Notification Rules and the new paradigm of how they operate deserves an online course in how to migrate, set up, configure, test and improve your new PI Notification Rules.

There needs to be better ways to create and manage element templates for assets that are similar (but not exactly the same to one another).

For example, reactors might have 50% of attributes consistent across all reactors. 20% of the attributes might be specific to one type of reactor, and another type has other differences. But they are all reactors that are related from a search, analytics, and visualization perspective.

If you export an XML file for a migration you can not specifically designate what parent and child elements you want to migrate

There is a function in AF named TagEU(). This function returns the EU of the PI Tag, NOT the EU of the element. This presents problems in analysis if the Units in PI are not spelled the same as they are in AF or if the unit in AF different than the PI Tag.

Please add a function ElementEU() which returns the EU of the element. It should use the same EU from the element that Convert() uses.