PI Connectors

Welcome to the PI Connectors feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering 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. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  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
    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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow the UFL Connector to performa a scan Immediately after startup

    On startup, the Connector currently waits for the configured scan frequency time to pass before doing its first scan. There are cases where a low scan frequency (e.g. once per day) is required. This results in an unnecessary delay before the Connector starts collecting data. Please all ow the option to perform a scan immediately after the Connector finishes its internal startup routine.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add scan time offset option to UFL Connector

    Use case: The UFL Connector needs to read a huge data set from a REST Server which is updated once a day. The only way to control when the data fetch occurs is by starting the connector at the desired time. The Connector however currently waits for the configured scan frequency time to pass before doing its first scan after starting. Furthermore, the Connector/hosting server may be restarted throughout the day for various reasons (e.g. application of Windows patches) throwing the timing off and further adding another 24 hour delay.

    Scanning, processing and sending to PI the same data more…

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support HTTP Token Authentication to a REST Endpoint

    The REST endpoint from which I want to pull data requires token authentication. I would like the UFL Connector to be able to obtain the token given the username and password I enter on the Admin page.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Replicate AF Analyses with PI System Connector

    I would like to have the option to replicate AF Analyses using PI System Connector with the option to mark the desired analyses for replication.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  15. Make the UFL Connector logic development/testing/debugging process less tedious

    Deploying a UFL Connector solution requires a LOT of edits of the INI file as part of the development/testing/debugging process. After each INI file change and file save, the required procedure is as follows:
    1. Click on the Data Source List link.
    2. Click on ‘See Configuration’.
    3. Click on the ‘Change’ button.
    4. Click on the ‘Browse…’ button.
    5. Double-click on the INI file.
    6. Scroll the page down until the ‘Save’ button is visible (I’m using a 1920 x 1080 monitor).
    7. Press the ‘Save’ button.
    8. Click on the ‘Overview’ link.
    9. Press the ‘Start connector’ button.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  17. Suppress the creation of "Status Flag" PI Points

    The end-user would like to suppress the creation of the "Status Flag" PI Points, as they wish to keep their point count to a minimum due to the license-enforced point limit.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  18. PI System Connector: Add flexibility on which objects to synchronize

    As an architect, I have to model AF structures at a central location, and push them to distributed assets.
    I would like the ability to design my AF structure centrally, then replicate it to my distributed assets (e.g ships). Example features that are needed:
    - Ability to include Analyses, Notification Rules, and their templates in the synchronization
    - Ability to not copy the data from source to destination

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  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