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.

How can we improve PI Connectors?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add a Boolean data type

    Boolean variables are useful for reusing Boolean (sub)expressions, concise debugging of the value of a Boolean expression, and extraction and storage of Boolean values before writing to Int32 PI status tags (e.g. on/off status, open/closed status).

    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 →
  2. Transformations and scaling

    Add the ability to configure PI points so that the PI Connector for OPC UA performs transformations and scaling on the values before being archived.

    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 →
  3. DeltaV Smart Connector Update to OPC UA

    The newest release of DeltaV has the capabilities of enabling an OPC UA server that could be used to transmit realtime date from DeltaV to the PI database. Right now, the interface between the two systems uses OPC DA. With DeltaV's plan to migrate to only using OPC UA, Is there a roadmap to update the smart connector such that it uses OPC UA for realtime data transmission? This could allow the OPC UA connector to be placed on the PI data server directly since it is much easier to setup OPC UA connections across physically separate machines (as opposed…

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. OPC UA Connector Trend Advise Option

    OPC UA Connector Trend Advise Option, such as in the UniInt interfaces

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

    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. Be able to modify the PI Point prefix from the PI Connector for UFL administration page

    It does not make sense that edits to some of the PI Connector for UFL's JSON files can be done through the administration page, but not all. The administration page should be a 1-stop configuration shop.

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

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  7. Put a REST endpoint on all connectors

    It would be very useful to see the data flowing through a connector at the edge, or even the data buffered in a connector. Every connector could have a rest endpoint with the same methods as PI Web API. Possible uses:

    -Diagnose connection/configuration issues
    -Attach a dashboard directly to the connector on the node (for example a display on a monitor in a mining truck)
    -Attach third party software for local analysis or alarming of equipment status (for example, alerting the driver of a truck of important events)

    I'm sure there are many others...

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support user-defined data types in the PI Connector for EtherNet/IP

    As an advanced user, I would like to be able to specify a user-defined data type for the array sent to the PI Connector for EtherNet/IP.  For example, if I have a 32-bit array composed of one INT and two SINTs, I would like to be able to configure the connector to parse this array correctly. Currently the data type specification of the array is limited to one data type (DINT, INT, FLOAT, or SINT).

    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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. 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.

    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 →
  15. 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 →
  16. Wonderware Historian Connector should store some metadata in PI tag attributes

    The Description, Maximum EU, Minimum EU, Engineering Units, etc. that are stored in the Wonderware historian should be stored in the PI tags' attributes as well as the Wonderware AF structure.

    4 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 →
  17. Log device information when the Connector receives errors from a device

    Currently the Connector logs when it receives errors, but does not print information that can be used to determine which device is reporting the errors.

    We currently need to perform a wireshark trace to look at the individual packets to determine which devices are sending errors.

    4 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 →
  18. UFL Connector HTTP compression

    Large data sets need to be pulled from a REST server on the internet which supports HTTP compression. Since this feature is not supported by the UFL Connector, the data will need to be retrieved in an uncompressed format. For the current project, this means several Gigabytes daily.

    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. Add ‘No Replace’ mode to UFL Connector

    Currently the only PI Data Archive ‘Store Mode’ options are ‘Insert’ and ‘Update’. I’m currently working on a project where a large quantity of data needs to be downloaded daily from the internet using the REST client node. To reduce chances of data loss (e.g. due to download failure), the Connector will be configured to retrieve the same data set several times throughout the day. The best option at the moment is the “Update” mode. This however will place unnecessary load on the PI Data Server as large quantity of archive records are re-written with the same data throughout the…

    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 →
  20. Add instrumentation to the PI System Connector

    Need to add instrumentation to PI System Connector wheras exposing perfmon counters (so PI perfmon can store accordingly in PI tags) on AVG data flow in events/sec for a 120 seconds time period, status of the connector, etc

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