OSI should get together and devise a proper data synching mechanism that should guarantee synching archives for all backfilled events and so on.

The current automated Archive reprocessing creates a backup of the original archive in the archive directory. This can lead to a situation where the archive drive runs out of space.

It would be useful to be able to configure the backup location for the reprocessed archives. This should be a tuning parameter.

As an analysis user, I would like to be able to specify the path for an AF attribute and use it for my calculation logic at all places that expect an attribute input.

When trying to move multiple elements to a different location, right now we have to select only one element at one time, we would like to be able to select multiple elements in PSE at one time. For now, we could use PI Builder as alternative.

Need a way to utilize the trigger time in analysis functions.

'*' refers to now or snapshot values

Using timestamp('triggered attribute','*') only works if there is only one triggered attribute configured.

Would be good to have one screen to manage the periodic scheduling for  all analyses in a given AF database.  This way, you can standardize where it makes sense to, and look for outliers (analyses that may have been scheduled incorrectly).

API Rest delivery channel has one format, it is configured for one template. Customer would like to implement it for all of the templates in bulk.

Two Notification Templates could be linked to two different Analysis Templates that can be linked to two different Event Frame templates. Therefore the options to populate the delivery end point could be different between notification template. SQL stores a GUID in the properties of the delivery format, applying in bulk would also mean copying over GUIDs which would result in the wrong configuration.

If the "Show simplified configuration strings" option is selected in Settings, this removes GUIDS from the output in Excel.

However, this option also removes the linefeeds in any formatted Analyses. If reloaded then this can corrupt the analyses - especially if comments are used.

Please add an option to remove GUIDS but preserve formatting.

@OSIsoft: Refer to TechSupport case 929964 for information.

If a user has PI points that are calculated with average, maximum, and standard deviation time range method, it would be great if those points can be referenced as attributes in an event frame template. Right now the time context needed to calculate  a minimum, maximum, or standard deviation is not exposed within an event frame. It would be helpful if the time context can be exposed in event frame templates.

As a PSE user, I would like to be able to configure an expression which allos to automatically set or reset the exclude property on an attribute

There many posts with similar content. to get a better overview (for people who want to vote as well for osisoft). the feedback webpage should be managed and similar postings should be merged/grouped. one example is manual data entry for PI vision, but i think there more.

Currently the analysis function "EventFrame" supports parameters "StartTime", "EndTime" and "Duration".

I would like to see additional parameters "StartTriggerName" and maybe also "StartTriggerExpression".

That could be useful for creating different "Outputs at close" for different start triggers.

customer wants to change the font settings for a dynamic content values in the Notification E-mail message format. Only fixed text are only allowed to change. Once the Content value is selected, the Designer icons grey out.

The ability to define and rollout compression standards on tags across the enterprise / sites. 

When this information is captured bottom up from sites, bad settings make it difficult to maintain a standard which inhibits cross site data comparisons.

As a PI Admin, I need assistance configuring and testing Kerberos delegation, so that I can access the full functionality of the products without exposing my system.

As a user of Asset Analytics I would like to reference parent element attributes, name, and other context information in Expression and Event Frame Generation analyses, even when it is not known during configuration time what the parent element will be so that I can write better conditionals such as : If ParentElement = “Foo” then ‘..\Foo|attributeFoo’ ELSE ‘..\Bar|attributeBar’

The default is set to Natural (event driven), but best practices say that this is a very costly method. Creating thousands of analyses can lead to forgetting to change it to periodic.  My suggestion is that the default should be set to periodic and/or the user should be allowed to set what default analysis type they want in the configuration.

I I would suggest to configure an event frame so that, depending on the reason code, severity automatically changes