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

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.

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.

Connectors currently assign point sources; this is not user configurable.  In addition, all connector of like kind get the same point source.  This makes it difficult to determine which tags "belong" to which connector node.  Users would like to be able to monitor\count\filter searches based on connector node.

While writing data to PI through the connector relay there seems to be no option to control the write mode . E.g."[-109] Value at This Time Already Exists" is shown in the logs if the archive already contains an event with the same timestamp. The default update option can be "Replace" instead of NoReplace. Other write options can be made configurable.

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

There are use cases where data is sent over networks with latency (satellite link, for example) so being able to filter out noise at the connector is important.  This is also important when a connector sends data to a local PI Server in the field (low latency), but then PItoPI is used to send snapshot updates to a central PI Server over a high latency link.

Sometimes, when dealing with APS, a new TAG is generated for an existing point. Data stops going to the old point. It would be nice if there was an easy way, within the gui (not manually dumping and importing) that we could take the values from one tag, and place it into the new tag.

There are other times when we may want to copy all historical values from a tag, and place it into a new tag.

As a PI Administrator, I would like to be able to DISABLE or configure Tau buffering SO THAT after a network outage the flood of data doesnt overload my network switch and PI DA. My current use case doesn't require the data that may be lost during a network outage.

I would like to be able to throttle the number of events that are sent ot the PI DA via Tau buffering so that the PI DA can ingest the data without building event queues.

Specific connector: PI Connector for EtherNet IP which is used for high speed data collection.

While the existing support for Sparkplug MQTT format is helpful, this connector would be more useful if it also supported a more generic JSON format.

The current default log size in the event viewer is 1MB. Although it can easily be increased, a larger default (100MB+) would allow to catch errors the first time they occur and allow for further troubleshooting then having to change it and have to replicate the error one more time.

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...

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

PI connectors such as OPC UA, Wonderware and Cygnet send BAD values from the data source. We would like the option to filter these values out at the connector level such that they do not make the PI Data Archive.

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.

Currently OSI has not tested web-based PI tools with Chromium-based version of Microsoft Edge.
It will be helpful to know if there are plans for it to become officially supported by a certain time, since eventually Chromium-based Edge will get pushed to all of end users

Currently, all of the attribute templates of the element templates that PI Connectors create have their unit stated in their description but do not have a Default UOM assigned to them. Please assign Default UOMs to the attribute templates to save the user from doing this manually.

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.