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. Connector-level Failover - OPC UA 2.x

    Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.

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

    We’ll send you updates on this idea

    4 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Connector for IEC 60870-5-104 writes 'No Data' or another SYSTEM digital state when connection to the Data Source is lost.

    This connector is specially used to monitor the connection of the machines, but if there is a general network crash, and the connector losses the connection to the Datasource, it will stop sending data instead of sending something to alert of the situation.
    Not being aware of that situation can cause big impact in the companies.
    Receiving a Sytem digital state when the connection to the data source is lost would help to create an alarm and let the people in charge know.

    26 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 →
  3. Do not synchronize description from OPC UA server into PI Tag

    There are situations when customer prefers to use “description” in PI Tag attribute that is independent from item “description” provided by OPC UA Server.  
    Currently, during each synchronization, the OPC UA Connector synchronizes descriptor from OPC UA to PI Tag and overwrites desired “Descriptor” attribute provided by customer. 
    Although the solution would be to have desired description already on the OPC UA Server, in some situations (OPC Server managed by 3rd party) it is not possible. It would be good to have configurable parameter in OPC UA Connector, which disables synchronization of item description from OPC UA Server to PI tag.

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Prevent OPC UA Connector 2.x from doing Data Discovery in Tags-Only mode

    Use case: If we are frequently adding OPC UA tags and OPC UA server has a large variable count, then each discovery will increase the amount of time for it to complete. This increases the amount of time needed to discover the data source + configure new tags, and can also exhaust machine resources during the discovery.

    In version 1.3 of the connector, tags-only mode did not do a discovery.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Connector for IEC 60870-5-104: to filter IOAs

    Considering the following scenario encountered by the customer:

    In IEC-104 data source, there might be 500 signals of single point (type=1, MSPNA1) and 1000 measurements of normalized value (type=9, MMENA1); however the customer would not like to transfer all those signals and measurements into PI system with PI Connector for IEC 60870-5-104.

    How to configure the connector to filter them (such as filter them by IOA of signals and measurements)? Just like what can be done with filter file in PI OPC UA Connector?

    5 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 →
  6. IEC61850 - Ability to connect to a non-default port

    The connector is currently unable to connect and collect data from MMS Servers using a port other than the default 102.Port selection should be part of the data source configuration

    3 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 →
  7. View more detailed buffer queue statistics for PI Connector for OPC UA

    I would like to get a more detailed view of the buffer queue for the PI Connector for OPC UA. In particular, I would like to be able to see the number of PI Events in the queue (not just the number of Tau Messages) and the amount of space filled in the buffer queue file.

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. Enable Relay/DCM to allow control over the data streams and destination PI Systems

    Currently the Relay will send all data streams to all routed destination. This does not allow customers to have control over what data streams go to a specific destination. The only workaround is to have independent Connector/Relay pairs with specific configurations, which does not scale up if there are several Connectors since only one specific Connector/Relay can exist on a single node.

    For example: Let's say there are two Connectors (A and B), routed to a Relay with two destinations (1 and 2). The current implementation of the Relay will send both Connector A and B data to both Destinations…

    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 →
  9. Support filtering by element template or attribute

    Currently we can "filter" what is replicated by including a specific branch. But if using a composite model, say a site with all it's composite assets, and only want to replicate the "foo" assets from all sites, this option does not work.

    It is possible to build a weak referenced homogeneous asset model elsewhere under a separate branch and include only this branch. But this can be tremendous amounts of work / automation with all the burden on the client.

    An improved mechanism might be like the ESRI integrator -- selection by template type(s). And even more flexible, allow filtering…

    4 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 →
  10. Can we have a version of the UFL Connector that is compatible with the Data Collection Manager and the Relay?

    Can we have a version of the UFL Connector that is compatible with the Data Collection Manager and the Relay?

    Use case would be to allow the DCM to be the one-stop shop for all connectors and would make things easier to configure and manage the UFL connector if it were there

    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 →
  11. OPC UA 2.x - Health information and connector statistics

    In the PI Connector for OPC UA 1.3.x, some very useful statistics are available - Events in DA queue, Data rate, Variables Numbe - but 2.0.x these items are not available anymore. Those items should be available for data selection to be monitored and stored in PI.The same should be true for the PI Connector Relay Statistics

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  12. Payload configuration

    I want to be able to define a POST or PUT payload in the connector.
    Also the option to import the payload through a file. Add a testing capability so you can see the respons from the POST or PUT command.

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  13. Remove AF Requirement for PI Connector for OPC UA

    Remove the AF requirement for PI Connector for OPC UA.

    Users who may only be looking to send data from PI Connector for
    OPC UA to Data Archive are currently forced to configure connections/security for AF as well during initial setup.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enable setting tag attributes in MQTT Connector

    The MQTT Connector should have ways to set tag attributes. There should be way to set the default compression and exception settings and also other tag attributes like point and data security.

    5 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 →
  15. Connector should create point in PI server irrespective of the source tag value field, whether blank or null

    Connector should create point in PI server irrespective of it's value status in OPC UA server side, whether the source tag value field is blank or null, in either case, PI tag should be created for PI Connector for OPC UA 2.0.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  16. An import-export feature for PI Connector for OPC UA similar to the one used to configure OPC DA points

    Having to select the OPC UA server points to import from a list with thousands of points where a naming rule is not followed is a never-ending task using the OPC UA Connector web interface. My suggestion is to create an interface similar to the one on the OPC DA interface where it is possible to export the complete server’s point list to a csv file, remove the undesired ones, and import back the csv file.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  17. PI System Connector should be able to delete values on the destination server if they are deleted on the source server

    Sometimes when performing analysis recalculations, values are dropped from when they were initially recalculated. For example, when an analysis runs initially, it may calculate 15 values, which are then written to the source and transferred over to the destination as expected. However, if I perform a recalculation where I choose to permanently delete existing values and recalculate due to some of the analysis inputs having changed, and only 10 values are now written to the source server, these values are written to the destination, but the existing values that are now "incorrect" are still present. I would like for the…

    8 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 →
  18. Support for Chromium-based version of Microsoft Edge

    Currently OSI has not tested web-based PI tools with Chromium-based version of Microsoft Edge.
    It will be helpful to know if there are plans for it to become officially supported by a certain time, since eventually Chromium-based Edge will get pushed to all of end users

    4 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 →
  19. "Discover Available Endpoints” option is not available for backup server on DCM page

    "Discover Available Endpoints” option is not available for backup server on DCM page like it is available for primary server which lists down all the available endpoints depending on the security configuration settings in source OPC UA server side (None/128/256 Sign&Encrypt). As a result, user wont be able to select the desired security endpoint URL for the backup server explicitly. Please refer the point no.5 in the attached mail communication with reply from OSIsoft tech support for more details on this.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  20. Enable health tag creation even when "Create Data Source Asset in AF" is unselected

    Unselecting the Transformation Rule parameter "Create Data Source Asset in AF" for OPC UA 2.x causes the default health tags to not be created.

    Users who want this parameter unselected for control of the top-most asset in AF may still want the health tags created to monitor the status of the Connector.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 15 16
  • 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/PREVIEW
COMPLETED