Ideas

Allow specifying primary attribute category in AF and allow to use following options in the "Group by -  Category" menu in PI System Explorer: - show attributes in all categories - show attributes in primary category only (hide duplicate attr...

Suppose the following scenario: a user has 2 AF databases (a development and a production one), both containing same version of a template. The user deletes a few attributes and analyses from one element template (development), exports the xml and...

This is really a bug/security risk; but the support team has requested that a "Customer Voice" be raised. Support passwords longer than 15 characters in the PI AF Table Connector.

This would also enable calculation of percentiles. Percentile calculation would also be possible if the user could use nested substitution parameters in array functions. For example: RecVals := RecordedValues('Attribute1', start, end) CountLowe...

If the same analysis is trying to be used for multiple templates, there will be times when some attributes are not available from a template - this will cause the analysis to fail. Even when the difference in attributes is known and attempted to b...

I have one specific complaint but when I’m creating/testing a new event frame it is the worst. When backfilling a single analysis, the start time and end time boxes will throw an error and not allow the you to start the backfill if at any time the...

A customer thinks it is unreasonable to require all customers to recreate the linkage of a new attribute to a Enumeration Set that is a copy of the Digital State Set for the attribute’s linked PI tag. There should really be an Attribute “Value Typ...

Use case: We want to give a user read access to a single element. All future elements created inherit the Database level Security, meaning the user will also have read access to all future created elements.

Implement a way to hide the contents of a PI point attribute, specifically the Instrumenttag attribute. With many PI interfaces, the InstrumentTag attribute will store the IP address of the source, and we (as well as many other utilities) have a r...

In many cases analytics should not be visible to everyone having right to view an AF-Database. Should be possible to direct whom should have view access to analytics. This is an extension to the obivious right to change analytics :)