Ability to scale event frames to support hundreds of millions of EFs per year.

When force shifting an archive, the following message is displayed:

"Warning: This shift will clear data from the target archive. Are you sure you want to force an archive shift on <serverName> to a new archive?"

When Auto Archive Creation is enabled (having a value in Archive_AutoArchiveFileRoot), this is very misleading. A new archive will be generated and no data will be wiped.

This warning should only display if auto archive creation is not enabled and the archive will shift into the oldest shiftable archive.

Add the triggers to SQC rules to reset or hold the SQC rule. When monitoring a periodic or batch based process, a user needs to be able to hold the SQC rule or put that rule in a hold state until the process resumes. Without this feature, virtually all violations to the SQC rules are caused by the downtime periods - not the steady state process users are really intending to monitor

Currently, if an event frame generation analysis is renamed, all notifications rules that use it will display an error message, saying that the event frame generation analysis might have been renamed or deleted.

This message is fine for deletions, but it would be much more user-friendly if the notification rules were to automatically update to reflect the rename of the event frame generation analysis.

While no customers have asked for this directly, I have seen many customers ask how to check a tag for being stale. The solution to date assumes all tags have the same staleness timeout, which really is not the case most of the time.

This new "StaleTimeout" point attribute would be a duration (time span) customizable for each tag. There could also be a new PIPoint property called "IsStale" which could bounce the current value's timestamp off the "StaleTimeout".

As a PI Administrator with a test PI Server, I need to be able to easily promote configurations from our test environment to our production environment. Currently this is extremely difficult and a very manual process.

It would be helpful if you could search by Element Category or Element Description when searching for Analyses in PSE. My setup is 5 templates (CHW, Water, HW, Electric, Steam), each of which have accounts that can come from 5 different sources (selectable by element category). I can't filter by both commodity type AND source, I can only do Commodity type using the "Template" criteria option, as the "Category" and "Description" search criteria options relate to Analyses, not to elements. This severely limits the functionality of the search feature for me.

It would be nice to have the ability to drag and drop the value at end time of  an attribute in the message format of a Notification. We can do this with the value at start time and the value at send time, but not the value at end time. There are some ways to workaround this, but it would be nice to have it as a drag and drop option.

I would like the option to configure a Notification to continue to be escalated until it has been acknowledged, even after the trigger condition has become false and the Notification is no longer active.

As an AF user, I would like to be able to store a tag’s instrument tag value in an attribute so that it can be used in the content of a Notification. For example, notifying someone on data from a PING interface where the instrumenttag property holds the IP Address.

I am able to create an AF analysis to store a tag’s description in an attribute using the TagDesc PE function, but there is no similar PE function to pull in a tag’s instrument tag.

As a PI Administrator of a PI System with complex security requirements, I need to set up different default permissions for various users so they can create tags that automatically have the proper security instead of having to rely on a process/procedure to correct security after the tags are built.

A web service endpoint, for instance ServiceNow, may response with useful information to a notificate, like a ticket number. There should be a way to associate that information with the event frame that triggered the notification.

The Non-Repetition Interval in Notification Rules is currently only applied to Notifications sent at Event Start. I would like the Non-Repetition Interval to also be applied to Notifications sent at Event End.

Currently, there is no button in PI Builder which allows users to bring in Global Notifications Formats. The button would allow users to read in current Formats and then users would be able to Publish edited formats or newly created formats. This would give users another tool to manage Formats other than using PSE.

We should be able to export and import Event Frame SEARCHES to work with them in further projects.

It would be useful to trigger event-triggered rollup analyses upon adding new children. Currently rollup analyses are only triggered when rollup attributes are updated (and not triggered when rollup attributes are added). This would be particularly useful in cases where the rollup analysis is dependent upon the number of children such as an average. The current implementation results in misleading values when child elements are added or removed.

Currently, when you remove a template from an Element in PI System Explorer, you'll remove all existing attributes from the Element.

There should be a functionality in PI System Explorer to remove the template without making changes to the attributes for the element.

Currently, the only workaround is to use PI Builder to remove the template without removing the Attributes associated with said Element.

Feature of Notifications 2012 that was not carried forward - big mistake.

Need the ability to customize the sender email on notifications.  Makes it easier for users to configure email rules to take actions such as file in certain folders, forward, etc.  Also - with iPhone VIP setting, can set up phone to alert differently for critical notifications.

Huge swing and miss...