The 30-day history recovery by the connector after restarts should get activated only after the initial history recovery is confirmed to have completed successfully.

In Data Collection Manager, it would be good to have a status on Currently Synchronized Elements, Events, Tags, structure. Be able to count the events and tags that failed to synchronize since some time. Missing values in tags between source and destination...

Today the diagnostics are poor, difficult to understand and disappear very quickly

Point changes on the source currently necessitate a restart of PI System Connector to rectify the streams. Allow the tau framework to handle these changes at runtime without restarting the connector.

Currently, if the point type changes are made during runtime, because of the persistence of streams, there is a flood of errors in the message logs which are not consequential to the nominal functionality of the connector. This leads to erroneous conclusions about the state of the connector.

This product is pushing production data... it should be redundant.

All in all a wrong configuration should be undone easily and not result in a complete re-installation of the system. If this is possible by using powershell scripts (an example is installed for all connections - RemoveAllConnectionConfigurationsRelay.ps1 - maybe it might be a base for a script to remove single registrations).

Please add support for future data / tag type to PI System Connector. Since it is currently unsupported we have to continue to rely on PI to PI interfaces or other to handle these tags.

The PI Data Collection Manager User Interface has the options to "Collect All Data from this Entire Database" and "Collect Data from a Specific Branch". What we want to do instead is to "Collect All Data from this Entire Database EXCEPT from a specific branch". This is because the users in the target (test) database do not have permissions to configure the branch (element) that we want to exclude from syncing. The current workaround is to install a PI System Connector for each branch of the database that we want to include.

When Digital States are editted or deleted on the Source Data Archive, these changes are not replicated on Destination with the PI System Connector

For each PI Point query (Data Archive Only), I would like to specify certain attributes: mainly security. Defaulting to PIPOINT security string is preventing us from using this product because we have special security strings for tags to 1) keep some data limited access and 2) not overload the PI OPC server.

Especially when requesting a large amount of historical data from PI System Connector, I would like the Connector to prioritize the current data from the data source while processing the historical data at a lower priority in the background.

PI System Connector should be able to replicate GUIDs if desired, as some third party products like Seeq index against GUIDs.

As a PI engineer, I would like to sort and search the tag lists in PI DCM so that I can verify that the tags I am interested in are created / available in the PI Data Archive.