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. 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 →
  2. 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 →
  3. PI Connector for OPC UA - Client must use a bitmasking .dll

    Request for Bitmasking

    As per Case Number: 00763382
    Case Link: https://customers.osisoft.com/s/casedetail?listViewType=Home&id=5001I00000WubpK

    There is no current support for bitmask using PI Connector for OPC UA the way that PI Interface for OPC DA supports it, and there are no current plans to implement it. However, a post on our feedback site for an enhancement request to provide this functionality would be appreciated. I see that the OPC UA Server may have an option to support the bitmask. You may look into using the OptionSetType variable, but I don't believe the PI Connector currently has support for this variable.

    Despite this, there…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  4. IEC 60870-5-104: Interrogation Type

    Currently, the Interrogation Type selection options are:
    - General interrogation
    - General and groups interrogation
    - General, groups and counters interrogation

    There should be an option for General and counters interrogation

    1 vote
    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. 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 →
  6. Support delayed startup of queries for GE HabConnect Connector

    In some EMS configuration it is possible that to connect and query sampler before habitat database has initialized. This can cascade throughout PI -- analytics set to watch for minimum values, applications looking for status changes, etc. It is almost impossible to repair since the source system reported it -- the only way I understand to fix it would be to backfill from eTerra Archive on every failover or startup.

    The current interface supports a delayed startup option, which combined with PERMANENT supports some ability to avoid this condition. However a more flexible solution would be an option, by query…

    1 vote
    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. Enable GE Habconnect default attributes by query

    Newest version of the GE HabConnect Connector supports default point attributes to be added at the field level. However, many attributes are set at the query level -- security for example.

    In addition, some installations potentially require dozens of queries. Having to set defaults at the field level grows the size of the configuration dramatically, and obscures the important configuration settings.

    Please support setting default attributes at the query instead of, or in addition to the field level.

    1 vote
    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 →
  8. Give the ability upload different Tag Naming files in DCM / OPC UA Connector

    When uploading a "Tag Naming" file in DCM, this file completly replace the existing Tag naming. It mean that a Tag naming file must be done for all datasources within one connector.
    It would be a lot more easy when dealing with a large number of tags to be able to import a list of new or modified tags. DCM will then compare the imported file with the existing list and make the required modification or creation.
    An option to delete some datas using a filter will then be usefull.

    1 vote
    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 →
  9. Elapsed time of last discovery, being a good feature to add into Connector display under Data tab in DCM

    Elapsed time of last discovery is a good piece of information and being a good feature to add into Connector display under Data tab in DCM page.

    1 vote
    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 →
  10. 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 →
  11. 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 →
  12. Add a checkbox disabling Tag and Element creation

    Case1:
    OPC UA Connector configured in a way that if the automation system will offer new tags, they will be created on PI system automatically. However, this makes running out of tags on the PI Server. Is there a possibility to start the OPC UA Connector, although new tags cannot be created.
    Case2:
    In a “validated environment”  in pharmaceutical companies, no one (including Connectors) is supposed to make changes in the system configuration without extended paperwork.

    1 vote
    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 →
  13. "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 →
  14. 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 →
  15. PI Connector for HART-IP: Remove UoM from being added to PI point "descriptor" attribute

    Currently, the connector applies the UoM to the PI point "descriptor" attribute. If I want to write in a custom descriptor, every time I restart the connector, I then need to re-edit all of the points.

    1 vote
    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 →
  16. Support response and additional handling of POST requests

    Have the PI Connector for UFL running in REST Server mode respond to the first PUT/POST request with additional information, which then allows the RESTful endpoint to generate a second PUT/POST request with the data we want to parse and store in PI Data Archive.

    1 vote
    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 →
  17. 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 →
  18. 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 →
  19. Allow connectors to write to a buffered PI Point

    The customer stores shelving and alarming event data in the same PI point, as they are two parts of a full picture. They receive alarm data through the interface for OPCAE, however shelving events are not exposed through this data path, and they have to export the shelving events on a scheduled basis as CSV files, then consume them using the interface/connector for UFL. Sending the data to two separate points and then combining with analysis would add to the complexity of an already complex process, so it's not desirable to use this method.

    1 vote
    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 →
  20. PI Data Collection Manager (DCM) High Availability (HA)

    I would like to have failover or high availability for the the PI Data Collection Manager (DCM)

    1 vote
    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 →
← 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