Please consider creating a web application like PI Vision Admin, PI Web API Search, PI Manual Logger for Web, and the various integrators, but for PI System Explorer (PSE, PI AF). I would prefer this to the client-server design now. It would make version management, software dependency management, upgrading, firewall/network-services management, etc. easier. This would obviate the need to re-package the OSIsoft installers in whatever software package management software an organization uses. Another solution would be to use the Windows 10 application store. However, that wouldn't mesh well with using Cloud IaaS services. OSIsoft could even offer this new PSE Web as a PaaS: gear, Juju charm, Docker container, Amazon image, whatever.

When the PI Analysis service determines an Analysis should be Suspended, it should also set any output Attributes to be Excluded. As the Analysis is Suspended, it will not output any results and if it has always been Suspended, the output Tags will never get created. Excluding the output Attributes will keep the Element looking clean and also allow dependent Analyses to go into a Suspended state instead of throwing an error when they can't find the Tags. Similarly it will prevent other applications (OSIsoft and third parties) from querying the Attributes and also throwing errors, causing performance issues.

Automatically suspended Analyses when the inputs are excluded was an extremely useful feature and has made supporting and maintaining an AF database easier. Automatically excluding the output attributes is a natural progression of this feature and will make AF database even more easier to maintain.

When adding a Mapping to an Identity in the AF Server this will always generate a new mapping linked to a user/group account.

If this user/group account it's already mapped to an identity then, by default, it will add 1 to the mapping name.

If I have a user called PISCHOOL\u602 and I add it to an identity Engineers it will generate a mapping called PISCHOOL\U602. If I add this same user to another identity like Support then it will by default generate a mapping called PISCHOOL\U603.

This can be misleading since the PISCHOOL\U603 user might already exist and we could think that this user its already mapped to an identity.

I would like to suggest to use the same method use in the PI Data Archive where the mappings are unique and the identities are added to them.

Please see the images attached for a graphic example.

This is a followup to discussions with Roger Palmen and Rick Davin about their excellent writeups on the topic of EF Duration attributes; see Event Frame duration - easy way in AF2.6 or higher & Duration attribute on an Event Frame - Part 1 , respectively.
With the addition of the %Duration% substitution parameter and it's support in the Formula Data Reference, the following is suggested as a standard way to add a Duration attribute with values in a Time class UOM for newer versions of AF.
Create an EF attribute template with the following configuration:

Note 1: no parameters need to be defined; the substitution parameter is put directly into the Equation and can even be retrieved from the "helper" menus (red box and arrows).
Note 2: As mentioned in Rick's blog, the Formula DR supports unit conversions so we can change the result in seconds produced by %Duration% to any other time class UOM (from seconds to hours in the example above; blue boxes).
Note 3: A third method not shown here or the referenced articles, is use of EF Generation analysis outputs to add duration (see KB01884). Pro: this is a nice, all-in-one method if you also want to output the duration to a PI Pt attribute on the reference element. Cons: Because the output expressions are not evaluated until the EF closes, there are no intermediate Duration attribute values available for open EFs. This method seems more complex to configure.
For further details/discussion, please see the comments under Rick's blog.
Please vote/comment here to let everyone know what you think of this as a standard way to get EF duration into an EF attribute.
Thanks for your time!
Edit: It looks like some automated process to convert PI Square ideas to UserVoice entries removed the links & screenshots; added them back.

A few minor improvements to the search and filtering capabilities of the management tab could save time when doing backfills at scale - for example after transferring several elements from a development server.  If possible the following search capabilities could be very useful:
-Improve search by template: Currently when searching by template every analysis will be listed and in alphabetical order by analysis - not template name which makes it difficult to search. It could be helpful if it were possible to choose one template and every analysis associated with that template would be included.  At the very least, adjust the ordering of the drop-down so that it is in alphabetical order by template
-Improve Element search: Include or allow for search of child Elements as part of Element search