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. Handle deletions across systems

    Ability to have deletions replicated across systems as well (might need to be a config option on how to handle).

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

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

    We’ll send you updates on this idea

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Make "Cancel" a button, not a link

    In the configuration page of any data source, there is a "Save" button and a "Cancel" link. This is unnecessarily inconsistent. Please make "Cancel" a button.

    5 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 →
  4. Write an error message to logs when no destination PI Data Archive is specified

    Ran into this problem when configuring a new UFL connector. After install, I went straight to configuring my .ini--forgetting to add the PI Data Archive (in fact, the connector was actually installed on the DA node).

    I had the text files coming in and being processed by the connector without any errors, but saw nothing being created in my data archive. Eventually, I realized I had forgotten to add my destination server. This is an error you would typically never run into with interfaces since they require you to specify a destination when configuring a new instance. There should at…

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

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

    Develop a connector for Azure ML Web Service

    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 →
  10. Discrimnate meta data changes of source items picked by PI Connector for IEC 60870-5-104

    We would like to discrimnate when the meta data around the data item changes on the source. The digital states related to it, the description, etc. If these change, the connector will change them on our PI server.

    Currently PI Data Archive.does not discriminate it just blows away the current configuration and reloads everything from the source overwritting our custom changes.

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

    4 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 →
  12. write/send Data to source PI Systems (output tag)

    To use the PI System Connector for enterprise applications like machine learning, mvda,... it should also be possible to configure "output tags". the result of analytics on enterprise level are needed also on local PI systems, so for some attributes/tags a two way communication is required.

    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 →
  13. Support string data types for PI Connector for EtherNet/IP

    String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.

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

    4 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 →
  15. Configurable OSIsoft\PI Connectors\UFL.ConnectorHost\ location defined during installation

    Currently, the folder is created by default in %ProgramData%, which means that the output folder, storing the processed file, is created in %ProgramData%\OSIsoft\PI Connectors\UFL.ConnectorHost\Output{DSName}.
    Since %ProgramData% is generally on the OS drive (C:), processing a large number of files can cause serious damage to the machine.

    The path can be configured in Global configuration - parameter "Output Path" using the provided PS script that comes with the connector, but this parameter should be configurable during the installation.

    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 →
  16. Enable child Event Frames for Alarms and Conditions from PI Connector for Siemens Simatic PCS 7

    Would like to see states of alarms captured as child Event Frames of the parent alarm Event Frame that is currently created. Today this data is only captured in tags.

    4 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 →
  17. Add Time Offset Option to OPC UA Connector

    Please add a time offset option to the OPC UA Connector, similar to the old OPC DA interface (see attached screenshot).

    In come cases the OPC UA server may not actually be sending timestamps that are in UTC (ex. in local time) so an offset is needed to change the timestamps into UTC.

    4 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 →
  18. PI System Connector Destination AF Configuration String should not Contain Source PI Server Name if it is Unreachable

    Currently, if the PI Server specified in the source PI AF server is unreadable from the PI System Connector node, the Connector will forward the listed source PI Server name in the configuration string to the destination AF Server. This causes confusion as the Destination AF server will likely not have access to the unreachable source PI Server. Instead, The connector should create a configuration string on the destination AF server stating that the source PI Server Host is unreachable.

    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 →
  19. Better error handling in DCM UI

    For some cases where disallowed or poor configuration causes unexpected behavior, the UI should give a visual indicator and explanation.  Two examples:
    1. No write access for Relay to AF DB when using the PSC.  Result: replication of AF objects fails with many error messages.  Digging through log, found a message that indicated permissions issue on target AF DB.  In DCM, all was green. Would have been good to have an error or warning symbol on the Relay object with message about missing write permissions on Destination.
    2. Added a second destination AF DB with reference to same Data Archive. …

    4 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 →
  20. Allow UFL Connector to show status when HTTP request fails

    This enhancement would allow the UFL Connector to be able to write a status to it's tags when a HTTP request fails, such as 401 or 503. 

    Currently, a bad HTTP request will fail before attempting to parse with the .ini, so  there is no way to control this behavior via the .ini.

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