All ideas

Currently, when creating an Attribute in PI AF using "String Builder" or "None" Data References, the system does not update the timestamp associated with the attribute's value upon value change. When the end-user looks at the timestamp they see a ...

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

Pulling compressed data into an analysis is extremely helpful...but would be even more valuable if we could filter the compressed values, similar to the capability in PI Datalink.

if one element is deleted, the related tags which is created by attribute template can be deleted automatically

Currently unable to search for excluded attributes in PSE's attribute search. Enable/allow this.

If I have two AF databases, I would like to pull the value of an attribute from one database to another. The string builder path for the other database's attribute requires a value substitution from a non PI point DR from in the target AF DB (whic...

We have many calculations following this basic pattern - take recorded values of one attribute, apply a filter (using FilterData), then retrieve values of a second attribute at the filtered timestamps of the first attribute. Currently, we cannot r...

For unitless values you can assign a unit of measure by using the Convert() function. To further convert this to another UoM in the same class you need to nest another Convert() function. For example, Convert(Convert(3600, "s"), "h")) It would sim...

Pi Notifications should have smarts to exclude or N/A message body content for excluded attributes created from templates. Currently if we have say 4 attributes in an element template, and some instance elements have a couple of those "excluded", ...

We often write outputs at close to event frame attributes that reference a PI Point attribute on the referenced element. The analysis will not write to an EF attribute if it points to a referenced element attribute at the child level. In the examp...