As a user using AF to create analysis, I would like to be able to convert time durations in a decimal format (ex: 3.5 hours) to an actual time format (ex: 3:30)
-Instead of seeing 3.5, we should have the ability to see it as 3:30
-Additionally, i...
When a PI Point is the output of an analysis add the attribute path to the description of the PI Point
It can be a challenge to find the analysis that writes to the PI Points in large AF hierarchies with many contributors. It would be convenient to have the PI Point Data Reference attribute path written to the PI Point configuration (description or...
Expression function to retrieve default attribute value
I am migrating part of an old ACE application over to AF Analyses, and need to replicate the functionality to fall back to default values in case any of the input attributes are bad.
I have taken the time to set the default value in each attribut...
PSE Analysis Preview Results to indicate the origin of the event times
In PI System Explorer, when using the Preview Results function for analyses, I want the dialog to indicate which of the input attributes the current timestamp originates from.
Example: Two inputs with update frequency 1 min, Input1 without offset...
The ability to utilize three columns as input for interpolation from an AF Lookup Table to determine the result for a fourth column could be beneficial for predictions and analysis.
Currently, only linear and bilinear interpolation is possible fr...
We would like to be able to extract the data reference type (PI Point, None, Formula, Table Lookup, etc.) for an attribute using PI Analysis, similar to the TagType function for PI points.
The TagNum function seems to be the only function that requires a double quote as opposed to single quotes.
Many other TagXXX functions call for single quotes for its attribute or PI Point arguments.
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 ...
Allow Analysis timestamp override feature to output milliseconds
When using an analysis variable as the output timestamp, it appears that the actual output timestamp is floored to the nearest second, shaving off any millisecond count. This is not a huge priority on our end, but I wanted to ask in case it was a ...
Remove tag need for Exit() and NoOutput() in analysis
Allow analysis outputting to Analysis Data Reference attributes to make use of the functions Exit() and NoOutput(), instead of requiring only PI Point Data Reference attributes.