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. Adjust GE e-terraHabitat Connector to support e-terraPipeline systems

    The Pi Connector for GE e-terraHabitat systems was apparently only written to support GE's Electrical SCADA systems (EMS/DMS) that are based on e-terraHabitat. They also have Oil & Gas Pipeline SCADA systems, also based on e-terraHabitat, known as "ETPL" (e-terraPipeline), which have a slightly different record structure for POINT and ANALOG records. Both expose their data via GE's SAMPLER technology, which at a basic level works the same for both types of SCADA systems, the difference is in the record structure related to POINTS and ANALOGS that is slightly different for each system.

    The existing Pi Connector would need a…

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

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

    We’ll send you updates on this idea

    PLANNED  ·  0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    2 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 →
  4. Allow PI System connector to actively rectify streams if point type changes are made during runtime

    Point changes on the source currently necessitate a restart of PI System Connector to rectify the streams. Allow the tau framework to handle these changes at runtime without restarting the connector.

    Currently, if the point type changes are made during runtime, because of the persistence of streams, there is a flood of errors in the message logs which are not consequential to the nominal functionality of the connector. This leads to erroneous conclusions about the state of the connector.

    1 vote
    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. Add one more option for the "Incoming Timestamps"

    Add one more option for the "Incoming Timestamps"
    Be able to use take the timestamp direkt from connector server/PC.

    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 →
  6. Add Digital Set in OPC UA

    Possibility to specify the digital set of a digital tag (CLOSE/OPEN)

    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 →
  7. Ability to monitor which OPC UA Connector is active in a failover pair

    As a PI administrator, I need to monitor which OPC UA Connector in a failover pair is currently active. When the primary OPC UA Connector goes down, I need an email notification, and vice versa when the secondary OPC UA Connector goes down.

    1 vote
    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. GE Proficy to PI / OCS w/o a VPN

    Ability for connectivity for GE Proficy system sent to an external PI System and/or OCS without the use of a VPN.

    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 →
  9. Honeywell PHD to PI / OCS w/o a VPN

    Ability for connectivity for Honeywell PHD system sent to an external PI System and/or OCS without the use of a VPN.

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

    We’ll send you updates on this idea

    1 comment  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  10. PI Connector for MQTT - support more generic JSON formats

    While the existing support for Sparkplug MQTT format is helpful, this connector would be more useful if it also supported a more generic JSON format.

    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 →
  11. Redfish - Allow port selection from the DCM UI

    When configuring the PI Connector for Redfish, it will default to port 443 for the target Redfish Server. Servers are commonly installed on custom ports. Currently, the port needs to be manually edited in in DataSource.config.json.

    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 →
  12. Distribute-Broadcast-To-Network broadcast for Discovery Tool and Connector

    When running the discovery tool from a subnet with no BBMD to query BACnet devices on a separate subnet, it seems like the auto discovery tool is seen as a ‘foreign device’, so the devices do not respond correctly.

    When analyzing a Wireshark trace, the discovery tool sends an ‘Original -Broadcast-NPDU’ Who-Is request to the BBMD on the other network, because it is seen as a foreign device, the request is not forwarded onto the sub-devices by the BBMD on this separate subnet. We can see that no I-am requests are sent back to the discovery tool.

    As the discovery…

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

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  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.

    9 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. Auto discovery on a separate subnet (as foreign device)

    When running the discovery tool from a subnet separate from the BBMD and BACnet devices, it seems like the auto discovery tool is seem as a ‘foreign device’, so the devices do not respond correctly. There is no BBMD on the subnet the connector is on.

    When analyzing a Wireshark trace, the discovery tool sends an ‘Original -Broadcast-NPDU’ Who-Is request to the BBMD on the other network, because it is seen as a foreign device, the request is not forwarded onto the sub-devices by the BBMD on this separate subnet. We can see that no I-am requests are sent back…

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

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  15. New function for Ethernet/IP (“scanner”)

    Add the function to able to act as (“scanner”).
    At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
    https://www.odva.org/Technology-Standards/EtherNet-IP/Overview

    7 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 →
  16. Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags

    Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags.

    Existing tags were reading from "FxBias interfaces" and in need to let them read from WW historian thru WW connector.

    WW connector is reading names from WW historian and force the names as per WW historian.

    can we rename WW connector created tags to be as per existing tags or not?

    also about compression and exception settings, can we keep existing settings or we must follow WW connector settings only?

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

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  17. OMF Support PI Connector Relay

    Keep the OMF support in PI Connector Relay, also add the new OMF Versions to it not just only OMF 1.0. Not just leave the OMF support to the PI WebAPI. In many customer scenarios, the PI Connector relay is a much more robust solution than PI WebAPI.

    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 →
  18. Develop PI Connector for AspenTech IP21 for the PI System and OCS

    We have customers who are using AspenTech IP 21 and would like to have data replicated in both PI DataArchive and OCS in the future. Since the PI Interface is a bit outdated, a new PI Connector would make perfect sense (since there is already a PI Connector for WonderWare and Honeywell PHD). The PI Connector shall support both PI and OCS.

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

    We’ll send you updates on this idea

    2 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  19. PI Connector for Beckhoff TwinCat

    Develop a connector for Beckhoff TwinCat

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

    We’ll send you updates on this idea

    1 comment  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI Connector for Jason/GBP - Ford Connected Car

    Develop a connector for Jason/GBP - Ford Connected Car

    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 →
← Previous 1 3 4 5 11 12
  • 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