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. PI Connector for RDBMS

    The PI Interface for RDBMS is one of the most used PI Interfaces. Unfortunately, the fact that it is a PI Interface makes it unnecessarily difficult to use, and turning it into a PI Connector can help alleviate this. No more Location codes, squishy PI ICU, distributor tags, SQL file in the InstrumentTag, strange notations in the ExDesc, etc.

    52 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →

    From this item description it looks like the major pain point with existing RDBMS interface is providing configuration information (to the tags and interface). I would like to understand more if the request behind the connector is to solely minimize providing configuration information to the existing interface and tags?

  2. OPC UA: allow historical data access

    allow historical data access with custom time ranges, like OPC HDA

    35 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →

    We have a feature in the upcoming 1.2 release of the connector that will allow you to collect data from OPC UA tags that do not have current values but do have history. We would poll these every 60 seconds (default) to find new data.

    Was that part of this request in any way? Can you describe in more detail what you would like as a feature that prompted you to vote for this time?

  3. PI System Connector with mode to synch AF Analysis and Notifications Templates

    As an equipment specialist working centrally, I wish to deploy my AF Element Templates including Analysis and Notifications Templates to my remote sites so I have them managed from a central location. This also insures that remote sites are using the same calculations and KPIs.

    23 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    We have considered including this functionality natively as part of the PI system as opposed to including this in the connector.

  4. Apply the Connector Relay to IEC 60870-5-104 Connector

    Adding the Relay and the DCM framework to the "legacy"IEC 104 Connector in order to improve the architecture management and security

    22 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  5. Feature to turn off auto creation of PI Tags in PI Connector for UFL

    Ability to turn off auto creation of PI tags - When data is sent via REST to a PI Connector for UFL service ,currently it looks for a PI Tag in the PI Server and if the PI Tag does not exist it creates a new PI Tag. It would be good if we could turn off the feature if not required as in our case we have a naming convention for PI Tags and we create the tag names in advance so would not like to allow for the auto creation of PI Tags.

    20 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →

    I’m not sure why this would be needed. In the UFL connector you need to specify the name of the tag that you write to. And if that tag already exists, it will write to it. If that tag does not exist, then the connector would create that tag with your desired tag name. Why would you want the connector not to create that tag?

  6. PI Connector for IEC 60870-5-104 bi-directional between SCADA and PI

    RWE Power AG

    “But one really important feature we need, is the ability to write back from PI into the SCADA system
    Until now, we couldn’t find anything about this (important) functionality.
    So our question is if we can use this connector bi-directional?
    And if not, is this already in the roadmap for this connector?”

    20 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Can you share with us any info about your use case for sending data back to the SCADA system? For example, what is the purpose of that data? How many tags and how often will you send?

  7. Add the ability to select a subset of PI Points from a PI Data Archive

    The PI System Connector allows to include PI Point replication directly from the PI Data Archive even if they are not reference in the PI AF hierarchy with the "Include all PI points from this PI Data Archive" option.

    I would like to replicate only some PI Points that are not referenced, not all. This would remove the need to maintain both a PI to PI and a PI System Connector.

    I could create a bogus AF Database referencing those points but I would prefer not to.

    15 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    As suggested in the description of this item, PI System Connector uses AF database as the primary source and thus any filtering that is desired at the PI Tag level can be accomplished by referencing only those tags in the source AF database. If users would only like to replicate PI tags without an AF model, then PI-to-PI interface can serve as an alternate option.

  8. Windows Authentication to the Rest Endpoint should be supported with PI UFL Connector. Currently only Basic is supported

    I tried connecting to a REST endpoint using PI UFL Connector. However, it seems the Connector only supports Basic Authentication. The REST point only supports Windows Integrated Security. We can use Web Browser to read data from the REST endpoint. We get the following error in the connector log: HTTP status code: Unauthorized

    8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for reaching out. We can extend the connector to support the NTLM authentication, which falls under Windows Authentication. Would it meet your needs?

  • 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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED