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

    3 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 →
  2. The connector creates too many tags

    Currently, the connector will create 124 or 248 tags per data source, regardless of how many meaningful data points are actually in the data set.
    This greatly limits the use of the connector to any customer that is not an EA.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    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 →
  4. Mass create data source list for PI Connector

    For the PI Connector for EtherNet IP you can have up to 100 data sources. Typing in all of them is tedious. It would be nice if we could copy/paste information from Excel OR have a structured import/export file to the data source list.

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

    We’ll send you updates on this idea

    1 comment  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. 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.

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

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    4 votes
    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 →
  9. Connector provides Timestamps

    The EtherNet/IP protocol does not specify timestamps when data is transmitted, the connector currently assigns the timestamps base on when the data is being processed.

    This leads to the following issue, if the network/computer/etc gets busy, we will have several values be processed at the same time. Thus, many values with the same timestamps.

    A possible work around is that the connector specifies time frequency, for example values come 10ms apart.
    If the connector read this frequency, the connector could possibly assign better timestamps for values that are processed at the same time.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    1 vote
    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 →
  11. Connectors should support a Send Rate parameter

    Connectors need adapt to many different types of networks, in both configuration and quality (latency, etc.) of the data transfer. One of the features that interfaces had, but connectors still lack, is the ability to batch the values sent to PI and spread out when they are sent. These are the Send Rate settings for the buffer subsystem, they are requested for connectors as well.

    2 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. Need to start/stop individual data sources

    When going in the PI Connector Admin page in the data sources page, we cannot start/stop individual data sources listed when there is more than one. To stop one you need to stop all the data sources listed.

    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 →
  13. Possibility to change Back registration on relay side

    All in all a wrong configuration should be undone easily and not result in a complete re-installation of the system. If this is possible by using powershell scripts (an example is installed for all connections - RemoveAllConnectionConfigurationsRelay.ps1 - maybe it might be a base for a script to remove single registrations).

    3 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 →
  14. 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…

    3 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 →
  15. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  16. Have PI System Connector support null system digital states

    Would like to have the connector support Null System digital states. Null system digital states can work locally on a PI Server. Would like the connector to support all the options found locally so that we could accurately sync systems.

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

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  17. Do not silently overwrite PIPointPrefix.config.json when a PI Connector is upgraded

    Currently, if you install a new version of a PI Connector, the PIPointPrefix.config.json file is silently overwritten and reverted back to the default. For users that do not use the default prefix, this means that data gets recorded in the wrong tags and not the intended tags, which, in turn, can mean that critical notifications are never sent out.

    In general, files that the user is intended to edit should not be silently overwritten, and files that the user is not intended to edit are safe to be silently overwritten.

    Please consider either making it clear which configuration files will…

    2 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. PI Connector for InfluxDB

    Develop a connector for Prometheus \ InfluxDB

    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 →
  19. PI Connector for Splunk

    Develop a connector for Splunk.

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

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