As a PI Administrator/Super User, I want to control which users can start or stop analyses. This would allow users to create analyses and preview their results, and for administrators to review them before they are put into production.

Customer would like to be able to use AF Data References to reference AF Elements that reside in different AF Databases. This would allow him to not have to replicate elements and attributes across multiple databases.

In order to calculate the current shift operating at a plant, I need to calculate where in the 28-day cycle the current week is. Knowing which week of the year it is allows me to do that. Note that current PI weekday functions always count Sunday as Day 1, while some Excel functions count Monday as Day 1. It might be important to have an option to specify which day of the week is Day 1.

As a user configuring Analyses, I would the the Performance Equation (PE) Editor's auto-complete to suggest any child attributes as well as regular attributes.  Note: This was previously Enhancement 109589.

As a AF Administrator, I would like to be able to define a list of synonym names for attributes associated with an element template SO THAT different sites leveraging the template can have their attributes shown based on their "local" terminology.

For example, one site might call an attribute 'Speed' and another site might call it "RPM".

It's a challenge to get sites to agree on what to call things in a standard template which can result in little progress of building out AF.

I want the ability to determine what PI System Configuration Changes (AF & PI Data Archive) are legitimate and approved, with the criteria of being able to focus on changes that occurred during a user defined time range. I want to minimize the time it takes to confirm that changes were appropriate with the ability to focus on certain tags/af attributes and/or time for the change.

I want the ability to associate a change control record to PI System Configuration Changes.

As a notification user I want to receive a report on daily or weekly basis but I don’t want to store any associated data about it like the event frame information or the notification history since I use event frames for other purposes and I don’t want to clutter my PI system

On a highly loaded system with thousands of analysis i have one analysis that is misbehaving, missing executions but no skipped count, etc. Currently tracing enables tracing for ALL analysis creating an ocean of logging to plough through for that one event every few days.

As an AF administrator i would like to turn on Tracing for one or more individual analysis to investigate rare issues that happen over time, without logging ALL analysis evaluations as 99.9999% runs fine.

Consistency among tag search GUIs within client products (PI Builder, DataLink, SMT, ProcessBook, etc.)  The search in PI Builder has limited functionality and would be nice to have the same search GUI as used in SMT and ProcessBook.

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

As a PI Administrator, I want to know which tags are being used at which PI Analysis so I can know exactly if there is already another Analysis writing to a tag and avoid duplicated or wrong data.

Allow the use of filter expressions, similarly PI DataLink Compressed Data, so that you can visualize or perform calculations on filtered data (e.g., excluding bad values, certain digital states, etc.).

I would like to be able to configure outputs in an analysis to write at multiple time points (which are defined by the result of an array function).

My use case is to:

1. Configure an attribute as a Time Series Table Lookup
2. Create an analysis that retrieves the values of this attribute as an array, e.g. using RecordedValues
3. Transform the data using MapData
4. Write the result back to another attribute that is configured as a PI Point

For recursive Analyses such as below :
PrevVal(tagA,'*') + 'TagB' → output : tagA

When the PI Analysis Service is down (or the node needs to be restarted), the current calculation needs to be halted until the Backfilling reaches up to the start up time. Or else the value will not be as expected.

Our company is progressively superseding the deployment of hosts with SQL Server installed, while moving towards the usage of SQL Server instances provided by AWS' Relational Database Service as the DB backend. Although currently OSISoft does not officially support the usage of RDS instances as backends for AF and PI Vision, we performed some internal tests with both AF and Vision and they seem to be promising. We would like OSISoft to study this kind of solution and, if there are no major obstructions, provide official support for such scenarios.

When i create a derived Element Template, i would like to be able to override an inherited analysis. Now i am severly limited in the re-use of templates due to this limitation. I cannot extend nor exclude functionality in a derived template if this is used in an analysis, because i cannot adapt the inherited analysis.

This is similar to https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17865355-exclude-analysis-function
but the two would complement each other quite well