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.

Currently the MQTT Connector only supports username/password authentication. This is great for local brokers/servers, but very unpractical when connecting to cloud brokers like AWS IoT Core. Adding support for Client SSL authentication will make it significantly more useful in a cloud based infrastructure.

PI Connector for UFL allows for configuring point prefix, but does not allow for modifying point source. Some users prefer browsing tags by point source, and may want separate point sources for different UFL connectors.

It would be helpful to be able to re-order (e.g. sort) data sources being used by the PI Connector for UFL.

As the number of data sources grow it can be difficult to find a particular data source, especially if those data sources have similar names (changing one or two characters)

With Automatic UDC recognition enabled, PI Connector for Cygnet defaults to placing all UDC's in the CVS column by default, or in the VHS column if "Prefer VHS for Automatic UDC recognition" is checked.

This behavior should be a preference, not an all-or-nothing selection - users would like Automatic UDC recognition to default to CVS or VHS, but also have the option to specify UDCs that do not follow the default behavior.

Actually, if an error occurs during data processing, datasource stops immediately execution and skips the remaining rows.
Try catch or similar could increase stability of data acquisition.

Often third party web API needs input parameters so static URL is not enough.
Sometimes parameters are simple, e.g. current data, or can be derived from PI tags; these could be set with placeholder in configuration.

Actually the UFL Connector sends data to all of the listed PI Data Archives and AF Servers in the server list configured in administration page, so it's not possible to send different data to different PI DA or AF databases with a single UFL Connector.
It would be better to bring these configuration at datasource level.

The latest supported operating system for PI Interface for Citect is Windows Server 2016, with a requirement to upgrade our machines to Windows Server 2019, this interface is the only thing holding us back, the ICU is supported although the interface is unsupported.

We need to be able to handle Alarms and Conditions into the PI system. We are moving away from OPC classic into OPC UA.

Currently, only the Generation 1 version of the PI Connector For OPC UA appears in the Data Collection List (https://techsupport.osisoft.com/Products/PI-Interfaces-and-PI-Connectors), and it is the only PI Connector whose platform is "Windows" instead of "X64".

Please add the Generation 2 version of the PI Connector For OPC UA to the list. Please also change the platform of the PI Connector For OPC UA to "X64" unless there is some special reason for having it as "Windows".

• In my OPC UA server, each node is historized for 7days of time in order to avoid the data loss in case of internet issue/communication issue in field devices.
• When the PI connector is stopped and restarted for some time interval, data missed during that period has been recovered successfully.
• While PI connector is running, I want to read and store this historical data of each node in PI server. It would be great if any options available in PI connector (version 1.3) to view and store this historical data?. Thank you

The connector should allow sending the data to a custom tag name. The combination of ASDU and IOA are not useful to end users without the signal list.

There should also be an option to automatically combine the quality flags with the value e.g. if the quality is not valid, then write the quality code to the value

I have come across customer requirements asking for the possibility of calling a REST endpoint using POST, from a PI UFL connector running as a "REST Client".

So far, the workaround has been to develop an intermediary custom script which would call the REST endpoint using the POST method, store the results in flat files, and then have the connector pick them up from there.

During setup of a new data source we always face a long list of several thousand tags where we only need a couple of hundred. We have also a list with tagnames available as .xlsx or similar. The idea is to have an import function for that list to automatically select / create the selection rules for that given set of tags.

The PI OPC UA connector can manage historical data recovery when connection is lost between the OPC UA server and the connector, but if the connection problem is between the OPC UA server and the data source on field, when connection is recovered and pending data is available in the OPC UA server there's no way to recover it using the connector.

The PI Asset Connector for Emerson DeltaV 3.X sets PI Point Attributes either based on the values in the enterprise historian configuration file (EntHist.xml) or based on default values.

It would be useful to have the option to adapt the PI Point Attributes set by the DeltaV Asset Connector before a PI Point is created. These are: PtClassName, PointSource, PtOwner, PtGroup, DataOwner, DataGroup, PtAccess, DataAccess, DisplayDigits, ExcDev, Location1, Location2, Location3, Location5, Shutdown.

So far, it is only possible to adapt them after the PI Point creation (for example by using PI Builder or SMT > Point Builder).

The AF Hierarchy that is created by the connector does not take into consideration any of the tagnames within the PLC array, it just creates attributes for them as slot.n where “n” is a number corresponding to the array position. Not only is this is not human friendly, but it will require renaming all assets and PI tags in order to understand what the data is.