The connector is currently unable to connect and collect data from MMS Servers using a port other than the default 102.Port selection should be part of the data source configuration

Can we have a version of the UFL Connector that is compatible with the Data Collection Manager and the Relay?

Use case would be to allow the DCM to be the one-stop shop for all connectors and would make things easier to configure and manage the UFL connector if it were there

Currently, the Interrogation Type selection options are:
- General interrogation
- General and groups interrogation
- General, groups and counters interrogation

There should be an option for General and counters interrogation

I would like to get a more detailed view of the buffer queue for the PI Connector for OPC UA. In particular, I would like to be able to see the number of PI Events in the queue (not just the number of Tau Messages) and the amount of space filled in the buffer queue file.

Newest version of the GE HabConnect Connector supports default point attributes to be added at the field level. However, many attributes are set at the query level -- security for example.

In addition, some installations potentially require dozens of queries. Having to set defaults at the field level grows the size of the configuration dramatically, and obscures the important configuration settings.

Please support setting default attributes at the query instead of, or in addition to the field level.

When uploading a "Tag Naming" file in DCM, this file completly replace the existing Tag naming. It mean that a Tag naming file must be done for all datasources within one connector.
It would be a lot more easy when dealing with a large number of tags to be able to import a list of new or modified tags. DCM will then compare the imported file with the existing list and make the required modification or creation.
An option to delete some datas using a filter will then be usefull.

Elapsed time of last discovery is a good piece of information and being a good feature to add into Connector display under Data tab in DCM page.

Connector should create point in PI server irrespective of it's value status in OPC UA server side, whether the source tag value field is blank or null, in either case, PI tag should be created for PI Connector for OPC UA 2.0.

Case1:
OPC UA Connector configured in a way that if the automation system will offer new tags, they will be created on PI system automatically. However, this makes running out of tags on the PI Server. Is there a possibility to start the OPC UA Connector, although new tags cannot be created.
Case2:
In a “validated environment”  in pharmaceutical companies, no one (including Connectors) is supposed to make changes in the system configuration without extended paperwork.

"Discover Available Endpoints” option is not available for backup server on DCM page like it is available for primary server which lists down all the available endpoints depending on the security configuration settings in source OPC UA server side (None/128/256 Sign&Encrypt). As a result, user wont be able to select the desired security endpoint URL for the backup server explicitly. Please refer the point no.5 in the attached mail communication with reply from OSIsoft tech support for more details on this.

Considering the following scenario encountered by the customer:

In IEC-104 data source, there might be 500 signals of single point (type=1, MSPNA1) and 1000 measurements of normalized value (type=9, MMENA1); however the customer would not like to transfer all those signals and measurements into PI system with PI Connector for IEC 60870-5-104.

How to configure the connector to filter them (such as filter them by IOA of signals and measurements)? Just like what can be done with filter file in PI OPC UA Connector?

Currently, the connector applies the UoM to the PI point "descriptor" attribute. If I want to write in a custom descriptor, every time I restart the connector, I then need to re-edit all of the points.

Have the PI Connector for UFL running in REST Server mode respond to the first PUT/POST request with additional information, which then allows the RESTful endpoint to generate a second PUT/POST request with the data we want to parse and store in PI Data Archive.

In the PI Connector for OPC UA 1.3.x, some very useful statistics are available - Events in DA queue, Data rate, Variables Numbe - but 2.0.x these items are not available anymore. Those items should be available for data selection to be monitored and stored in PI.The same should be true for the PI Connector Relay Statistics

Unselecting the Transformation Rule parameter "Create Data Source Asset in AF" for OPC UA 2.x causes the default health tags to not be created.

Users who want this parameter unselected for control of the top-most asset in AF may still want the health tags created to monitor the status of the Connector.

The customer stores shelving and alarming event data in the same PI point, as they are two parts of a full picture. They receive alarm data through the interface for OPCAE, however shelving events are not exposed through this data path, and they have to export the shelving events on a scheduled basis as CSV files, then consume them using the interface/connector for UFL. Sending the data to two separate points and then combining with analysis would add to the complexity of an already complex process, so it's not desirable to use this method.

I would like to have failover or high availability for the the PI Data Collection Manager (DCM)