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.

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

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

    8 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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

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

    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 →
  10. PI Connectors buffering (Tau) - provide configuration options

    As a PI Administrator, I would like to be able to DISABLE or configure Tau buffering SO THAT after a network outage the flood of data doesnt overload my network switch and PI DA. My current use case doesn't require the data that may be lost during a network outage.

    I would like to be able to throttle the number of events that are sent ot the PI DA via Tau buffering so that the PI DA can ingest the data without building event queues.

    Specific connector: PI Connector for EtherNet IP which is used for high speed data collection.

    10 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 →
  11. New MELSEC interface

    Develop new connectivity to replace legacy PI Interface for Mitsubishi Electric MELSEC.

    6 votes
    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 →
  12. PI System connector creates additional data on start up

    When PI System connector is stopped and started (as a service or in UI), duplicate event is received and archived by the target PI Data Archive. The write mode for the PI Connector Relay is append, in this case history recovery will include/send the previous snapshot value. This is critical for many customers, especially pharmaceutical companies.

    4 votes
    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 →
  13. OPC UA: Set PI Tag Zero and Span Based on OPC UA Range

    For OPC UA Analog Items, the OPC UA standard mandates an EURange property and an optional InstrumentRange property. These Range properties contain a Low and High field.The PI Connector for OPC UA should have an option to use either of these Ranges to set the Zero and Span of the PI tags it creates and the Maximum and Minimum AF Attribute Traits.

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

    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 →
  15. Extend the history recovery max period for PI System Connector to longer than 30 days

    Allow history recovery for PI System Connector to be longer than the current max of 30 days

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

    We’ll send you updates on this idea

    PLANNED  ·  1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  16. UFL Connector NoReplace fuction ( Store Mode)

    What we would like is a third option with UPDATE and INSERT, which prevents a new value for the same timestamp from being processed. Such as a NO REPLACE mode.

    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 →
  17. Switch for using Name of AF Attributes from Browsable Name or Display Name

    Add a Switch to the OPC UA Connector that we can choose if we want the AF Attributes to be created using "Browsable Name" or "Display Name". Using the Display Name would make it much easier for us to locate the Attribute and refer to its OPC Tag as we can see the same "Display Name" in both PI System Explorer and OPC Tools.

    4 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 →
  18. The UFL Connector should have a run once mode

    Many rest APIs allow access to historical APIs. This is data that should be collected only once when, for example, a new piece of equipment is being added for data collection. This one time data collection is currently tricky in the UFL connector as it involves the following:
    1. Create and configure a data source
    2. Wait several minutes for the data to be collected
    3. Delete the data source

    And this process has to be repeated each time a new equipment is done.

    3 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 →
  19. Configure PI Smart Connector for Emerson DeltaV 3.x Health Tags

    PI Smart Connector for Emerson DeltaV 3.x creates the following two health tags on the PI Data Archive:
    DeltaVACtrAssetSyncHealthTag
    DeltaV
    ACtrPointSyncHealthTag

    The names of these tags are hardcoded, so if I install another instance of the Smart Connector and configure it to create tags on the same PI Data Archive, it will write to these same health tags when reporting the status of a sync. I would like to configure the names of these health tags so my two Smart Connector instances write to two different sets of health tags.

    2 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 →
  20. PI Connector for Apache Kafka / Confluent

    Dear Connector Experts,

    for our Enterprise data integration project we have the need to use Apache Kafka / Confluent as the "data highway".

    This requires to send data to PI DA/AF from Kafka and also to read from PI DA/AF back into Kafka.
    I know that there are Integrators to actually read, but I also need the write-into-PI-option.

    Any comment on this if you have any plans on this would be great.
    The following data types are in focus for us for this:
    - Process Data (time series data) of Sensors / Actuators
    - Batch Data (Event Frames)
    - AF…

    7 votes
    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 →
← Previous 1 3 4 5 13 14
  • 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