Asset Framework (AF)

Users would like to be able to pull in the instrumenttag of a PI point into an attribute that is referencing it.  This isn't currently possible because the AF server and any attribute aren’t aware of most properties of the PI point itself, so...

In SMT there is the PIPOINT security table. When any new points get created it uses the PIPOINT table for the default security configuration. I would like to have a separate table for any points created from AF, so that they inherit a different se...

XML Export/Import supports renaming of objects when the Preserve ID option is selected. It would be useful if this could be extended to support moving of objects when the Preserve ID option is selected, e.g. moving an Element from one location in ...

Avoid having to manually reconnect to the AF database in PSE whenever a client computer returns from standby after the network connection has returned. Other PI client tools such as SMT are able to automatically re-establish connection under these...

XML Export/Import supports modifying and renaming of objects (the latter when the Preserve ID option is selected). It would be useful if this could be extended to support deletion of objects, e.g. deleting an Element, Template, Analysis etc that e...

I would like to monitor and manage alerts & events gathered from PI Interface for OPC AE to create a report like Top 10 alarms, Floating Alarm, Operator Alarm, because by default PI System will collect AE as a string and stored it. Should we h...

The feature introduced in 2018 SP2 to manually synchronize digital state sets with AF enumeration sets has a limitation where state sets with duplicated names aren't imported correctly into AF. This is due to the current design of AF enumeration s...

When using string builder attributes to dynamically generate specific values, additional attributes need to be created whenever concatenation of multiple attribute values is part the the logic. For example when using a string builder to generate a...

Currently the user must unlink and link the table to check this setting

Dynamic endpoints with comma separated email addresses are the preferred method for addressing notification recipients. They allow all recipients to see which other recipients have received the notification. The downside is any syntax error (e.g. ...