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

The PI Server install kit includes many deprecated components, namely:
• PI Totalizer Subsystem
• PI Alarm Subsystem
• PI Performance Equation Scheduler
• PI Batch Subsystem
• PI Module Database Builder
• AF Collective Manager

Also, the PI AF Link Subsystem is not needed if the PI Module Database, which is deprecated, was never used.

Please label these components appropriately and ideally also state the replacement. Otherwise, a new PI administrator might install some of these components "just in case" or follow outdated advice on how to set up a PI system without knowing that it is outdated.

When the Step attribute of a PI Point is "on", PI assumes that a value is constant until the next event, which works well in most cases.

For PI Points that track rolling averages, rolling totals, real-time derivatives of totalizer tags with respect to time, etc., it would be more useful to assume that a value is constant up to the previous event. Please add this as an interpolation option for PI Points.

The current names of objects, columns, and column groups usually use some combination of camel case, abbreviations, and no spaces, which makes them difficult to read. Nobody writes like this outside of programming, and most users of PI Builder are administrators, not developers.

It's not like spaces are never used; they are just not used enough. For example, the UOMClass object has a column group called "UOM Mapping". The ElementTemplate object has a column group called "Attribute Columns".

Please make the names more user-friendly.

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).

PI AF Admin would like grant permissions for users that are not level server admins to create and edit non-impersonated linked tables. Currently this only allowed for AF server admins or using impersonated linked tables.

User guide:

https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v12/GUID-B6374C40-8922-40CC-8E76-45CC646DA03F

https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v12/GUID-D1BDFD1B-8720-4CAD-8A06-0FCE958664BC

Currently there are 7 standard limits available to be used as limit traits. However there are situations where more than 7 are required. Users would like an option to create additional limit traits rather than having to manually configuring additional intervals in PI Vision multi-state.

While it is possible to manually calculate Process Capability Statistics, such as Cpk and Ppk, using AF Asset Analytics, it would be much more convenient to have a built in function to calculate these values, specifically in relation to the SQC Western Electric rules analyses available in AF asset analytics already.

Allow free-form JSON construction. Maybe not replace the simple JSON guide that is the only entry form now, but free-form would allow the kind of flexibility that would empower the user.

This would allow a single template to be used, rather than the workaround to manually override the template for every individual sensor configured, resulting in hundreds of template copies in which only the "Path" field is edited

For Notifications which send on Event Start and Event End, it would be useful to have the ability to have multiple Message Formats for the same Notification (one to send out at start, one to send out at end).

Advantages:
-Can include "End Time" in only the Notification sent at end (rather than showing an erroneous 1/1/1970 00:00:00 included in the Notification sent at start)
-Can include "Duration" in only the Notification sent at end
-Can fully customize different messages for start and end of the Event Frame

Allow for additional authentication types to be added for web service delivery endpoints. Currently, the only available options are Windows, Anonymous, and Basic.

When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to allow escaping it with a backslash or even better (IMHO) to use the JSONPath way to solve this: being able to specify arbitrary property names putting them between brackets and single quotes: ['prop.erty'].

The error message thrown when attempting to use a timestamp input with ValueType other than DateTime in an Asset Analytics calculation refers to "AF Time," which is unclear for many users.

An example of when the error would be thrown is when creating an expression that uses TagVal('attr1', 'time1'), where 'time1' is a String-valued attribute.

A better error message would read something like:

"<Attribute>: Cannot convert <time> to ValueType DateTime"

When calculating the disk space requirements on a recent upgrade the drive was expected to have only 138 MB installed. But the install failed due to not enough disk space on the drive because the minimal backup needed a certain amount of disk space. This need should be included in the Required Disk Space panel when upgrading.

As a PI Recalculator Subsystem end user, I need the PI Recalculator Subsystem to support recalculation of PI Performance Equation tags with point sources other than 'C'. This feature would be especially useful because of the PE Scheduler service startup performance issues associated with not assigning a unique point source to each PE Scheduler instance as described in KB00296 - Best Practice: Assigning a unique point source for each instance of an interface.

Data can be flagged as questionable, which should mean the value may or may not be valid. Asset Analytics seems to be rejecting the value as Bad. The function instead should evaluate the result, but flagging the result as questionable as well.