As a user, I want to be able to search for specific PI Points used by PI AF attributes, so that I can easily find where the PI Points are being used.

As a user, I would like TableLookup Data Reference to be able to use substitution parameters to specify the column name(s) and table name for the SELECT and FROM fields respectively. This would allow for the use of attribute values like those from String Builder attributes to be used to identify the desired column(s) or table and facilitate the use of table lookup within Element Templates.

I would like to use some more advanced string functions such as Split, Len (string length), and even regex filtering to allow more fine grained control of how some input strings (such as attribute values or substitution parameters) are manipulated to create a new string output.

As a user, I want to be able to use substitution parameters in attribute template descriptions, so that when elements are created from template, the attribute template description can be substituted with pertinent information.

Note: This was previously Enhancement 116200.

Looking for a tool that would compare two databases (that originated from the same parent) then gives user option to keep or discard changes from each and eventually merge them to form a working production database.

We use a custom data reference to store UOM information in an AF Attribute, which is then stored in PI using Tag Creation and substitution parameter. Currently there is no way to automate the UOM written in an AF attribute to the UOM field of the "target" attribute.

A possible way of doing this, from a user perspective, would be to allow substitution parameters to be used in UOM definition.

If you have a PI Point attribute with auto tag creation and you want the attribute UOM and PI Point engunits to match, you have to define it twice; once in the attribute UOM field and a second in the attribute configuration string, e.g. engunits=m3. If there was a substitution parameter for the attribute's UOM, you could use it in the attribute configuration string, e.g. engunits=%AttributeUOM%.

As an user I want to be able to create a template hierarchy (parent-child) all at once, so that I can easily create a hierarchy representing related assets. For example, create a motor, gearbox, compressor train with a single template that actually consists of (in this case) 3 templates.

As an user, I want to be able to have a localized element and attribute name in addition to the base language, so that my users do not have to learn a different language.

We have seen several instances where we would like to have the order of element displayed in AF/Vision be sorted by process order, not alphabetically.  Suggest adding a "sort" field and an option to have element arranged by that rather than alphabetically.

PI System Explorer should visually highlight attributes of template based elements that have changes to the template.

Customer would like to be able to use AF Data References to reference AF Elements that reside in different AF Databases. This would allow him to not have to replicate elements and attributes across multiple databases.

As a AF Administrator, I would like to be able to define a list of synonym names for attributes associated with an element template SO THAT different sites leveraging the template can have their attributes shown based on their "local" terminology.

For example, one site might call an attribute 'Speed' and another site might call it "RPM".

It's a challenge to get sites to agree on what to call things in a standard template which can result in little progress of building out AF.

Allow the use of filter expressions, similarly PI DataLink Compressed Data, so that you can visualize or perform calculations on filtered data (e.g., excluding bad values, certain digital states, etc.).

Currently, in PSE there is no way to display attribute values greater than or equal to 1000 with commas for the thousands separators. Ex: 1,234,456 instead of 123456. This option exists in other PI Clients (i.e. PI Vision) and should be available in all PI Clients.

A feature to review the changes that will be made when importing AF templates that have been exported from a lower environment.

Example.
Make changes to element/attribute/archive templates in dev.  Export library to XML.  Compare export to QA templates and provide a report on what all will change to be reviewed before importing.  If it has only the changes you intend to promote, then you can go ahead and import.