PI Connectors

Welcome to the PI Connectors feedback page!  

We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Update PI Interface for Citect Supported Operating System to Windows Server 2019

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support for Alarms and Conditions

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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  3. Revise the PI Connector For OPC UA on the Data Collection List page

    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".

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Read the historical data of a variable from OPCUA server when PI connector (version 1.3) is running


    • 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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow rename of tags for IEC-60870-104 connector

    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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow the PI Connector for UFL to call a REST endpoint using the POST method

    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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  7. Import function for data selection in PI Data Data Collection Manager

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. PI Connector for Wonderware Historian should be configurable to use 'FULL' mode query

    The connectors should have a standard behavior. We believe the Wonderware connector should be collecting data in the same way as the Cygnet connector by getting all the data stored in the source historian irrespective of the value change. Currently, PI Connector WWH uses 'DELTA' mode query where only the changes are retrieved. In some situations, the source value doesn't change much, but we still want to collect the data reliably on PI. To accomplish this, we would like to have the ability to configure the connector to use 'FULL' mode query. Without this Full query option, we have to…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  9. OPC UA Historical data recovery

    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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow specification of PI Point Attributes set by the PI Asset Connector for Emerson DeltaV 3.X

    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).

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  11. PI Connector for Ethernet IP should retrieve tagnames from the PLC array

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  12. implement the option to choose between append or replace in the configuration

    It would be nice to be able to choose between append or replace when configuring a new source in a PI system connector, to be able to choose how to copy the data in real time. Since right now by default it is like replace. In the RDBMS interfaces of the source we have several data with the same timestamp, and when copying that data the connector to the destination system only copies the last value, that is, it replaces it. We would like it to be possible to choose between append or replace data copy and that the data…

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  13. Windows Authentication on the Wonderware SQL databases

    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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DEVELOPMENT  ·  0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  14. Remove or disable the PI Connector UFL function which puts "Excluded" into attributes

    If the user has two different UFL flows working on same elements and attributes, one flow puts "Excluded" into the attributes created within the second one and vice versa.

    Giving the possibility to the user to disable this function would be a smart solution.

    (To give an example: if one UFL flow creates elements and its attributes and another flow creates only EventFrams referenced to those created elements, there are 2 ways:
    1) having EventFrames referenced to elements (using "StoreElement" funcion tin the INI file) and all attributes created with the first flow in "Excluded"
    2) having EventFrames not referenced…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  15. Drop support for TLS 1.0 & TLS 1.1 for the 1st-generation PI Connectors

    For the administration pages of the 1st-generation PI Connectors, please drop support for TLS 1.0 & TLS 1.1. These have been known to be insecure protocols for a while now, are not supported by modern browsers, and have been superseded by TLS 1.2 & TLS 1.3.

    "Compatibility with older browsers" is not a good reason to keep them around, since even Internet Explorer supports TLS 1.2 & TLS 1.3. Anyone using an older browser should upgrade for their own good. Since PI Connectors are a newer technology, I'm surprised that OSIsoft even bothered adding support for TLS 1.0 & TLS…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. Minify the PI Data Collection Manager's (PI DCM's) HTML, CSS, and JavaScript code

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add support for TLS 1.3 to the 1st-generation PI Connectors

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add support for TLS 1.3 to the PI Data Collection Manager (PI DCM)

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. Minify the HTML, CSS, and JavaScript code of the 1st-generation PI Connectors

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add 2 new PI Connector categories on UserVoice: "PI Data Collection Manager" & "PI Connector Relay"

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 14 15
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED