As a GE eTerraHabitat user, I would like to have a nice way to choose which tags I want to create on the PI System, without having to force them through the Approved Changes folder on the installation directory of the Connector. It would be better to have a GUI that has some functionality to browse through the GE eTerraHabitat, and also, that helps to define each RecordType and FieldValue combination, PI Point naming convention and PI Point tag creation.

For the PI Connector OPC UA configuration, the Root NodeIds field can only accept a maximum of 255 characters currently. This is seriously limiting if we need to gather a lot of data from many pieces of equipment

Allow for out-of-the-box monitoring options for all connectors similar to the functionality of interface performance monitoring (i.e. provide the option to monitor IO rate, connector status, etc.).

In OMF unfortunately more complex use cases are not possible
Integration of Script functionally for generated elements from OMF are needed. Please insert an possibility or allow an other development method to use all AF functionality in case of generated OMF Elements.

The Wonderware/AVEVA Historian has some different illegal characters than PI tags and there are also cases where a single tag prefix isn't sufficient (e.g. when storing data from multiple buildings in the WW Historian). The Connector should have the capability to link a WW tag to custom PI tag name similar to the OPC UA connector.

When the point count maximum defined in the license file has been exceeded, this interrupts real-time data flow for all PI Connectors until the error is cleared. This affects an reports or time-sensitive operations relying on production data. Data flow should not stop for point s that were already created within the license limit.

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.

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

OSIsoft OPC UA Connector should support the BaseDataType. Points/nodes that are BaseDataType should not throw errors or warnings when the OPC UA Connector is loading the nodes/points from an OPC UA server.
These points do not need to be actively collected in subscriptions, but they should be created as PiPoints.
All currently supported datatypes (ie, Boolean, String) are sub-types of the BaseDataType.
Our vendor's OPC UA Server often has templates and items with data-holders that are yet to be fully defined. These data-points are defined as BaseDataType.

Currently, it is not possible to update the AF Server name in the DCM without recreating the Destination. This process is prone to errors since the configuration for the AF and PI Data Archive servers needs to be recreated.

Having the ability to update the AF Server would be useful when migrating the AF Server to new nodes.

Currently, the PI Connector for IEC 60870-5-104's Interrogation Period (for each data source) can only go as low as 1 hour.

As a PI System Administrator, I'd like to be able to set this value lower (on the order of seconds) so that all PI Points are updated frequently, even if the data source isn't sending unsolicited updates.

As a PI System Admin, I would like the PI Connector for Wonderware Historian to automatically delete PI Tags that no longer exist in the Wonderware Historian to ensure that the two systems are in sync.

As a PI System Admin, I would like to specify whether PI Tags created by the PI Connector for Wonderware Historian should have Compression enabled/disabled before being created by connector in order to reduce configuration time. Currently, tags need to either be modified after being created or the PI Data Archive's system-wide defaults values for the compression attributes have to be set before configuring the connector.

As a PI System Admin, I would like the PI Connector for Wonderware Historian to automatically populate the point attributes Zero and Span when creating PI Tags so that these attributes do not have to be manually edited after the tags are created.

Currently the connector creates all discrete Wonderware tags with a Point Type of Int32. As a PI System Administrator, I would like the connector to have the option to create these tags as digitals and automatically create their respective Digital State sets. This would decrease configuration time and would ensure that all tags are correctly configured in PI even if the tags are modified in Wonderware.

In the reverse connect methodology - The server opens the socket and calls the client with a Reverse "Hello" message. After that, the client will use the already open channel (which initially fails with establishing the handshake) and call the normal opc.tcp "Hello" message. After that, it works like normal opc.tcp.

This is not currently supported in the connector.

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.

I'd like a one button click to send WW System Platform data to OSI PI. An example would be to add another check box during configuration where you could collect the data in the Historian, OSI PI, or Both.