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. Link to user manual/ help file unavailable from UI

    The connector UI does not contain any link to the help documentation or the user manual. The files are also not found in the standard PIPC path and are available only with the installation extarction

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

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow specifying UOM for new AF attributes created by UFL or OMF

    I'd like the ability to specify UOM for new attributes that I create. Adding categories as well would be even better!

    7 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. 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 →
  4. 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…

    6 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 →
  5. PI Connector for Azure ML Web Service

    Develop a connector for Azure ML Web Service

    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 →
  6. PI Connector for iFIX SCADA

    Develop a connector for iFIX SCADA

    6 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 →
  7. Program objects (BACnet object type 16) also bought through by the connector

    The program object description is often very useful to understand what the various object instances relate to. At our site the description holds the Asset designation and that would allow correct assignment of the analogue and binary object instances to the correct asset.

    6 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 →
  8. Need the WITSML connector to connect to Petrolink

    As we know WITSML is a rather loose standard. A large integrated Oil and Gas Company would like for the WITSML connector to work with Petrolink https://www.petrolink.com/witsml/

    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 →
  9. Wonderware Connector - History Recovery

    Wonderware Connector has limited historical data recovery capabilities. It can cover a few days back in time but has not been designed to perform both realtime values and configurable history recovery period as both processes are synchronous.
    An old date is configurable but it would delay real time values capture which is counterproductive with the nature of the connector.
    It is not a reproach; that's just what it is.
    That's we figured out when implementig and assessing connector with an excellent support from OSISOFT engineers.

    Our connector implementation project came with the need of nearly a year of historical data…

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

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  10. Setting of parameters k and w for IEC 60870-5-104

    Parameters k (Maximum number of outstanding I format APDUs) and w, cannot be adjusted, while vendors recommend customers to set it to k=12 and w=8

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

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  11. UFL Connector - Add elements and attributes to existing AF hierarchies

    Simply, it would be nice if the UFL Connector could add to existing elements and attributes already in place instead of creating a new hierarchy.

    Also, would like the ability to create sub-elements from the UFL connector that span multiple elements and are not restricted to a single instance of the UFL connector.

    Very similar to the "Connector (UFL) can read AF data structure" idea, just more succinct.

    6 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 →
  12. Filter Quality tags PI Connector for Wonderware Historian

    There should be away to filter which quality tags are created. Currently we can only choose all or none.

    6 votes
    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 →

    We are currently evaluating this request. Any additional information would be incredibly helpful!

    How would you expect to select which quality tags to create?

    Would this be a one-time operation? Or repeated on a regular basis?

    What are some reasons why some quality information would need to be collected rather than all of it?

  13. Scan only when the data folder changes

    Specifying the scan time seems unnecessary. Instead, the PI Connector for UFL should only scan the data folder if a change to the data folder's contents is detected. Surely some sort of event listener can be set up to achieve this?

    6 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 →
  14. Allow the AF root element name to be configurable

    The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.

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

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow data sources and servers to be renamed

    Currently, if you want to rename a data source, PI Data server, or PI Asset server, you must delete the one with the old name and create a new one with the new name, and redo all of the configuration. This is especially a pain for data sources, since they have a lot of configuration.

    Please allow data sources and servers to be renamed to avoid this trouble.

    6 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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.

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

    5 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 →
  • 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