Need a way to utilize the trigger time in analysis functions.

'*' refers to now or snapshot values

Using timestamp('triggered attribute','*') only works if there is only one triggered attribute configured.

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?

When trying to move multiple elements to a different location, right now we have to select only one element at one time, we would like to be able to select multiple elements in PSE at one time. For now, we could use PI Builder as alternative.

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!

The default is set to Natural (event driven), but best practices say that this is a very costly method. Creating thousands of analyses can lead to forgetting to change it to periodic.  My suggestion is that the default should be set to periodic and/or the user should be allowed to set what default analysis type they want in the configuration.

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 I would suggest to configure an event frame so that, depending on the reason code, severity automatically changes

Would be good to have one screen to manage the periodic scheduling for  all analyses in a given AF database.  This way, you can standardize where it makes sense to, and look for outliers (analyses that may have been scheduled incorrectly).

API Rest delivery channel has one format, it is configured for one template. Customer would like to implement it for all of the templates in bulk.

Two Notification Templates could be linked to two different Analysis Templates that can be linked to two different Event Frame templates. Therefore the options to populate the delivery end point could be different between notification template. SQL stores a GUID in the properties of the delivery format, applying in bulk would also mean copying over GUIDs which would result in the wrong configuration.

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.

If the "Show simplified configuration strings" option is selected in Settings, this removes GUIDS from the output in Excel.

However, this option also removes the linefeeds in any formatted Analyses. If reloaded then this can corrupt the analyses - especially if comments are used.

Please add an option to remove GUIDS but preserve formatting.

@OSIsoft: Refer to TechSupport case 929964 for information.

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.

A few customers would like the capability of storing vibration wave form data in PI. They often measure data in MHz and GHz frequencies, which are at a finer resolution that the PI Data Archive is capable of storing. The wave forms are captured over periods from 2 to 30 seconds and only saved if there is an interesting event.

Customers in data centers are also requesting power quality wave form storage in PI.