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.

Currently, if SQL server authentication is disabled on the SQL server hosting the Wonderware Historian, the connector cannot authenticate and read from it because the connector is designed to authenticate explicitly using SQL credentials. To be able to authenticate using Windows authentication is essential for some customer to be able to implement the PI Connector for Wonderware Historian, as some organizations disable SQL server authentication for security purposes.

The code for the PI Data Collection Manager's web pages is currently not minified. Please minify it so that the pages load faster, especially on mobile devices, and so that the network traffic is reduced.

To be clear, to avoid the extra processing time of a separate minification step, the code should be minified to begin with. That is, the PI Data Collection Manager should be released with pre-minified code.

The highest version of TLS that the 1st-generation PI Connectors currently support is 1.2. Please add support for TLS 1.3 to make the administration pages of the 1st-generation PI Connectors load faster and more securely.

The highest version of TLS that the PI Data Collection Manager currently supports is 1.2. Please add support for TLS 1.3 to make the PI Data Collection Manager load faster and more securely.

The HTML code of the administration pages of these PI Connectors is over 3000 lines long and is very unoptimized. It also seems like most of the CSS and JavaScript code is inline and so is not taking full advantage of HTTP/2's multiplexing.

Please put the CSS and JavaScript code in separate files where it makes sense and minify all of the administration pages' code to make the pages load faster and to reduce network traffic. To avoid the extra processing time of minifying the code, the generated code should be minified to begin with.

The number of suggestions for the PI Data Collection Manager and the PI Connector Relay is building up, and they are currently all going under the "General" category. Please add new categories for these programs and reclassify existing suggestions accordingly.