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.

How can we improve PI Connectors?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow sending data to the OPC UA Server

    Currently the Interface is supporting read only.
    Sending data is also required

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

    We’ll send you updates on this idea

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

    Currently, there are no plans to incorporate bi-directional data flow within PI Connector for OPC UA. This request will be reviewed again at a later date but for now, there are no immediate plans to incorporate this functionality.

  2. Failover for PI Connector Relay

    Although, the PI Connector Relay going down / not being available does not cause data loss since the connector data is buffered, if the source connector supports Failover, the relay becomes the only single point of failure in the data flow.

    Having an HA option for the PI Relay would allow for a more robust architecture.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Option to replicate PI Point security attribute with PI System Connector

    The current version of PI System Connector does not support replicating the PI Point security attributes:
    •Point Security
    •Data Security
    •Data Access
    •Data Group
    •Data Owner
    •Point Access

    A further option would be to automatically create any PI Identities contained the PI Point security attributes if the destination PI System is missing them.

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

    We’ll send you updates on this idea

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

    PI Point security might vary depending on where the point is getting accessed from. The points residing on a PI Server in a control/process network might allow different security on their points vs the points residing on a PI Server in a Corporate network.

  4. Support Failover at the data source level

    For PI Connector (1.x) that support failover like OPC UA, failover will only occur when all data sources get into a bad state. Failover should not have to be configure at the PI Connector node level, but for each data source.

    Use case 1:
    If 3 connectors are installed:
    -ConnectorA can connect to OPC1 and OPC2
    -ConnectorB can connect to OPC1 and OPC3
    -ConnectorC can connect to OPC2 and OPC3
    Impossible to configure failover with the current implementation

    Use case 2:
    -ConnectorA has 5 data sources and is primary
    -ConnectorB has 5 data sources and is backup
    If 4/5 data…

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

    We’ll send you updates on this idea

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

    At the current time, we are not planning this functionality. If you have a need for this, kindly upvote this item which will allow us to gauge wider interest and applicability.

  5. Be able to point the PI Connector for UFL to INI files

    Please allow INI files to be pointed to by saving their full path, just like the PI Interface for UFL, rather than saving a copy of an uploaded INI file. This makes editing, testing, debugging, etc. much easier.

    2 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 →
    DECLINED  ·  Chris Coen responded

    The proposed solution in this request is not advisable for security reasons. The current process ensures that the change to the parsing file is accomplished with credentials that allow administration of the connector.

    The question I have is what is the underlying problem that fostered this solution? If it is something like it is hard to deploy updates to the parsing script (.ini file) and maybe this is especially challenging during development, then that idea would be worth capturing for sure.

  6. Remove conflict between TAU framework and PIBufSS

    We should be able to use buffering on one tag that is fed by the connector, in case there are moments when data has to be primed into it using AFSDK.

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  • 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