Tags created by a PI Connector can be renamed, but these renamed points can be "forgotten" if the Connector's point cache is lost. Updating the Tag Mapping configuration file can avoid this cache loss, but I would like to be able to rename Connector tags without updating this configuration file.

Support for health tags (similar to UniInt health tags), Windows performance counters, or any other way to bring Connector status and health information into PI tags to put them side-by-side with Interface health monitoring.

RWE Power AG

“But one really important feature we need, is the ability to write back from PI into the SCADA system
Until now, we couldn’t find anything about this (important) functionality.
So our question is if we can use this connector bi-directional?
And if not, is this already in the roadmap for this connector?”

Sometimes we need to send data back to our sources. Connectors should support output tags

Add the ability for PI Connectors to create future data point. This is especially useful for the PI Connector for UFL. The current workaround is to manually create the point as a StoredValues=FutureData.

Example 1 - OPC
If a new connection needs to be made to one OPC Server, restarting the connector forces all data sources (and potentially connections to multiple OPC Servers) to be restarted.

Example 2 - UFL
If my web service is down and I do not want to connector to keep trying to access to REST Server, I cannot stop/disable only one data source

Allow for connectors to create templates without the fixed prefix. E.g. The option to name an AF template "templatename" and not "UFL.templatename"

Although, the PI Connector Relay going down / not being available does not cause data loss since the connector data is buffered, if the source connector supports Failover, the relay becomes the only single point of failure in the data flow.

Having an HA option for the PI Relay would allow for a more robust architecture.

Right now, for one instance of the connector, all configured data sources will send data to all configured PI Data Archives and PI AF Servers. It is all or nothing. Due to the fact that you cannot have multiple instances of the same connector on any given node at a time, if you want this kind of granular control you would need an entirely new node and another connector. In the past, it was trivial to have multiple interfaces instances on the same node to send different data to different PI Data Archives; connectors should allow this capability.

It would be very useful to see the data flowing through a connector at the edge, or even the data buffered in a connector. Every connector could have a rest endpoint with the same methods as PI Web API. Possible uses:

-Diagnose connection/configuration issues
-Attach a dashboard directly to the connector on the node (for example a display on a monitor in a mining truck)
-Attach third party software for local analysis or alarming of equipment status (for example, alerting the driver of a truck of important events)

I'm sure there are many others...

In the configuration page of any data source, there is a "Save" button and a "Cancel" link. This is unnecessarily inconsistent. Please make "Cancel" a button.

Currently source points for PI Connectors that contain illegal characters are handled differently depending on the PI Connector. Some will replace the character while others will map an illegal character replacement when creating the PI Point. These illegal characters should be dealt with the same across all PI Connectors. Examples of illegal data source Characters: * ' ? ; { } [ ] | \ ` "

Some field values are missing or inaccurate when viewed through IE as compared to Chrome.  This was seen in the DCM UI and PSC UI for Data Source configuration.  Some IT environments are locked down to the point that IE built into the OS is the only browser option so it needs to show accurate information.

On the Overview page, the PI Data server list grows downwards from the top. On the Server List page, the PI Data server list grows upwards from the bottom.

Please use a consistent order for the PI Data server list so then one list does not appear out of order compared to the other list.

The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.

Some connectors perform some kind of rediscovery of the data source upon start - Such as meta data or current values, etc. When stopping a connector from the UI, a warning should pop-up indicating potential consequences of doing so and what to expect, such as "Restarting the connector will potentially require a long time in order to perform data source discovery."

This will prevent users from unnecessarily restarting connectors as a basic troubleshooting mechanism.

Currently, if you want to rename a data source, PI Data server, or PI Asset server, you must delete the one with the old name and create a new one with the new name, and redo all of the configuration. This is especially a pain for data sources, since they have a lot of configuration.

Please allow data sources and servers to be renamed to avoid this trouble.