Case 1.
There are some EFs that should be acknowledged and commented by equipment owners. In Pharma World, these comments qualify as GxP and shall not be deleted. Whereas Event Frames generated by analysis can sometimes due to data coming late or analysis errors be faulty. If by recalculation the EF attributes are corrected with data, the user will not be notified of the change, and the comment would be faulty. And if the error is in the trigger tags, and they will be changed afterwards, while recalculating the event would be completely different, and the comments are therefor not valid for the new one. So would be helpful to have the old comment grayed out that in case any decision is made based on the old Event Frame, it can be traceable and comment validity can be understood.
Case 2.
In case additional information are needed for certain Event Frame types, they can easily be added to the EF template and than a long period backfill can be started to retrospectively fill in the data. In case those events are previously commented, they will just be overwritten and comments would be lost.
While might trace those things in different audit trails, from an end user point of view (Engineer using Pi-Vision Displays), there are not traceable.
So only keep (grayed out) events where a person worked on.

Maximum security by default would help encourage security best practices by:
• Making the best decision for customers that do not know or care about security
• "Rewarding" security-conscious customers with not having to expend effort to maximize security
• "Punishing" customers that practice suboptimal security by requiring extra effort to make their PI system less secure
• Sending the message that "secure" is the new normal and "insecure" is the odd one out

Please make the following changes to the PI Data Archive and PI System Management Tools:

• All built-in PI Users should have the "User is disabled", "User cannot be used in a Mapping", "User cannot be used in a Trust", and "User cannot be used for an explicit login" check boxes checked by default on new installations. These should also be the default for new PI Users.

• All built-in PI Groups should have the "Group is disabled", "Group cannot be used in a Mapping", and "Group cannot be used in a Trust" check boxes checked by default on new installations. These should also be the default for new PI Groups.

• All built-in PI Identities should have the "Identity cannot be used in a Trust" check box checked by default on new installations. This should also be the default for new PI Identities.

• The default value of the AutoTrustConfig tuning parameter should be 0. When upgrading an existing PI system, if AutoTrustConfig uses its old default value, this value should be preserved after the upgrade as a custom, non-default value.

• Max out the Security Setting slider by default (i.e. the default value of the ServerAuthenticationPolicy tuning parameter should be 51). When upgrading an existing PI system, if ServerAuthenticationPolicy uses its old default value, this value should be preserved after the upgrade as a custom, non-default value.

There is an audience of users that (based on recommendations from OSIsoft staff) overrides analysis templates - creates an analytic in a derived template with the same name as an analytic in the base. They can change the input attributes or even the equations in the overriding analytic. This results in multiple analytics showing in derived templates. This seems to be an 'unpublished' feature. If an element is selected, multiple analytics of the same name may appear but only one is enabled to be selected/used.

The issue - if a user has selected the derived element template and wishes to do a preview of an overridden analytic, they must select an example element. In these cases, when they click on the select Example Element link, the list includes all elements using the base template, instead of just those using that particular derived element template. This is very misleading - especially when overridden analytics are in multiple levels of derived templates. See case 00760876.

The Analysis server uses the PI Buffer subsystem in order to apply Exception and Compression testing on the results of Analysis. However, when deleting data (either through Recalculation or deleting data via Powershell or PI SMT, or whatever) the PI Buffer subsystem on the Analysis server never resets the stored snapshot value/timestamp.

The consequence of this is that if the same Analysis is recalculated multiple times (for example after corrections, optimization, etc), compression is only ever applied the very first time an Analysis is recalculated. After that, compression is never applied up to the timestamp that the recalculation was run up to, as the PI Buffer subsystem never resets the actual current snapshot value/time.

In the referenced thread, the only workaround is to completely stop the PI Buffering Subsystem on the Analysis Server, delete the cache, release ownership of the PI Points on the Data Archive, restart the Buffering Subsystem, and then hope that everything works.

It would be way easier to be able to tell the Buffering Subsystem to get the current Snapshot from the Data Archive.

Reference in this thread on PI Square:
https://pisquare.osisoft.com/thread/43696-analysis-recalculation-ignores-pi-point-compression-settings#comment-146126

So there is absolutely nothing in the PSE user guide about how analysis templates are handled in derived templates. And while it appears that it is possible to override an analysis in the base template by creating one with the same name, there is little to no content about it - PI Square, Live Library. The User Guide should discuss how analytics are handled in derived templates. I guess you could punt the discussion of overriding analytic templates to a link to content on the portal - IF you would create that content (not just a PI Square post)- and maybe if you make the portal actually perform...

Given the still questionable performance of the new portal, I depend on the documentation that I can download because I know it will open every time I make an attempt.