We make use of strong naming convention for all our tags, using sets of prefixes/sufixes to properly position our PI tags in AF hierarchies.

We are making use of the PI Adapter against the PI WebAPI endpoint. Now with the PI Adapter health & diagnostic PI tags that are auto-created when 'EnableDiagnostics' is set to "True" in the auto-created AF DB for this purpose, the auto-naming of these PI tags does not permit a configuration of the naming using a set of prefixes that would help us locate better in our data landscape the position of the PI Adapter.

What we need is to be able to in further PI System Monitoring AF models to be able to re-use these PI Adapter health & diagnostic tags efficiently using substitution params in order to easily create analytics and visualization against AF Elem templates to monitor the whole PI Adapter fleet (potentially hundreds).

Without this prefix we have to map each PI tags manually to the correct AF attribute for our PSM purposes, which is absolutely against our good PI practice in terms of creation and maintenance.