List all PI Points in error from PI AF Attributes in PI System Explorer.

wish to have the "Analysis Service Statistics" to have a button in the management tab in PSE. Instead of right clicking and click on "view analysis service statistics".

With the introduction of the property "Delta UOM", there is no way to control this in PSE. We need this to properly configure or modify UOM classes

Refer to 2017SP2 release notes:

121485

A new property, DeltaUOM, has been added to the UOM object to allow applications to determine the appropriate unit for measuring the differences between two values.  For example, temperature units typically have a different unit to represent deltas because of the offset present in the conversion factors.

There needs to be better ways to create and manage element templates for assets that are similar (but not exactly the same to one another).

For example, reactors might have 50% of attributes consistent across all reactors. 20% of the attributes might be specific to one type of reactor, and another type has other differences. But they are all reactors that are related from a search, analytics, and visualization perspective.

As a user, I want to be able to perform clipboard "cut" operations in PI System Explorer, so that I can remove an object and store it in the clipboard for later use.

Use geolocation to find assets around the location of another asset.

For example, find all wells within 2 miles of well 1043.

As a PI AF administrator or power user, I would like to be allowed to continue loading content from a server library into a database, even if a UOM conflict is detected.

Upon finding a UOM conflict, the library import feature does not allow me to ignore the error and continue loading the content (screenshot1.png), in contrast with the file import feature (screenshot2.png).

Tech Support case #00957957 concluded that this was not a bug.

Automatically display UOMs in the PI AF client in the language of your choice i.e. not a conversion of units. For example, to change the display of UOMs to Russian instead of English, kg becomes кг, V becomes B.

Changing from Expression to Rollup by mistake will erase the Expression configuration in PI System Explorer. Add a warning message regarding this.

When writing an expression analysis with many variables, if there is a missing ")" or an extra ")" then the whole analysis will not evaluate with error "Equation not set." This error does not help the user identify where the issue is. If PSE would back-light highlight the variable row in question or include the variable name within the error these would be much easier to identify and would save a lot of headache.

In the attached screenshot is an example of "equation not set" where the issue is visible in the screenshot, but difficult to identify.

Users must use an SQL JOIN clause while configuring linked table to join Link Tables belonging to the same data source .
For table Lookups, joining internally existing Link Tables in AF within the AF Server is not possible as Table Lookup Data Reference does not support SQL JOIN clauses

Nobody knows what PIFD means. We've had customer personell create PIDF2, PIFD3, etc. when tasked to create new AF databases, and also requests to remove PIFD because ICT personell don't know what it is.

I suggest renaming the SQL Server database for AF to something more understandable. Following the naming structure used f.ex. by the PI Integrators, the name could be PIAssetFrameworkDb, or simply PIAFDB

As AF Table Lookup Data Reference is configured with a time column in order to support cashing, edits of the following types to the table data will not be picked up by AF Clients: 

1- Update the value of an Existing record/Event

2- Add a new record/event with Timestamp prior to the end of stream (the last retrieved event)

Enhancement required is for PI AF Clients is to pick up the mentioned types of changes.

Enhancement Request for PSE tables "Cache Interval" to allow a date/timestamp/offset to be entered for the cache interval.

Currently, the PI Point Array data reference allows the Source Units field to be set, but this setting applies to all points in the array. It would be better if the Source Units field could be set individually for each point in the array for conversion to the Default UOM.
Use case: we have multiple PI Points we want to put into an array, but some have source units of lb/h while others have source units of klb/h. We would like to enter the source units individually so all values in the array are converted to the same UOM (klb/h).

Would like ability to use the value of an attribute array values when doing name substitution like %@attribute1[0]%

When a parent attribute template is excluded, but included at the element level, all child attributes are also included. It makes sense if a parent attribute is set to excluded all child attributes should also be set to excluded. However, if a parent attribute is set to "included", some child attributes may or may not be excluded. Instead of "including" them all, maybe they could remain excluded and the user can choose which to include.