PI Interfaces

Welcome to the PI Interfaces feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. 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. Alert user when the interface discards values

    Example:  When using a distribution tag, the number of tags returned and number of values sent to PI can be mismatched, due to missing aliases or data that does not need to be collected.

    It would be helpful to identify what values are dropped or were not updated in PI.  While there is the @rows_dropped variable, it can only be used for distribution tags and may have limitations when used with stored procedures.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  2. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please add a DAYOFWEEK function to the UFL interface

    Can you please add a DAYOFWEEK function to the available functions in the UFL interface.

    This will greatly assist with the handling of daylight savings transitions (e.g. first sunday in April) as there is currently no easy way of determining the current day of week.

    Function should take a DateTime and return an integer (i.e. Monday=1, Tues=2 etc)

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allowing output point with source tag to keep working even after switching to secondary server

    When primary server is down, secondary server is accessed instead of primary server, which is good. However, in the case of output point with source tag, it stops working, then restarting the interface instance of interest is needed. Of course, if we set up UniInt Failover that backup instance keeps its session with secondary server, this issue can be prevented. But, it will be better if source tag is also switched to secondary server.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix MAXSTOPTIME parameter for batch interfaces

    The MAXSTOPTIME parameter for batch interfaces does not kill the interface process when the limit is exceeded, however the parameter does work for UniInt based interfaces. Please fix the batch interfaces so that the interface process is killed once the MAXSTOPTIME has elapsed.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enhance how batch interfaces write to the message logs

    Batch interfaces should write their messages to the message logs using the Source1 and Source2 fields just like UniInt based interfaces. Currently, batch interfaces leave these 2 fields blank. Source1 should contain the process name or similar and Source2 should contain a string in the format of "<PointSource> | <Location1/ID> | <FailoverID>". Having this will greatly help PI administrators filter the logs based on point source, especially when there are 20+ interfaces running on a server.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow diagnostic tags per failover node for batch interfaces

    Batch interfaces should allow for diagnostic tags per failover node, just like UniInt based interfaces. Currently, there is no differentiation between the diagnostic tags for the primary failover node versus the backup failover node. The Location3 field is used to hold the failover ID of UniInt based interfaces so that there is a unique set of tags per failover node, however for some bizarre reason the Location3 field for batch interfaces stores the diagnostic tag index even though the diagnostic tag pointer exists in the ExDesc field. While not all diagnostics tags may be of interest for the backup node,…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. Interface TCP\IP para Data-Logger Davis (WeatherlinkIP)

    Se recomienda agregar funcionalidad para adquiquirir datos de un DataLogger WeatherlinkIP, ya que actualmente solo se soporta conexiones seriales con este data Logger:

    Davis Vantage Pro / Pro Plus Weather Station (NTI)
    Davis Weather Station (NTI)

    Tener en cuenta que actualmente todas tecnología se basa en conexiones TCP\IP.

    https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. Device Status UniInt health tag should update during runtime without needing a status update

    Currently, the device status is updated on startup, on change, on shutdown, and on each performance summary interval.

    However, for a device status tag created while the interface is running in a good state, the device status tag will remain at 'Pt Created' and not update until the interface status changes or the interface is restarted.

    A newly created device status tag should display the current state of the interface without needing a status change. This is especially helpful in cases where the interface cannot be restarted for the tag to pick up a status update.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. PI Interface for ABB Web Imaging System via ABB CNI

    CNI interface should support message 25. Currently, we do not support any message beyond 22.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Preferring a primary interface failover member

    hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

    https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  12. Buffering Manager - add metrics for each buffered interface

    When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  13. Monthly scans

    Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. 64-bit version of CatGH5 interface

    There needs to be a 64-bit version of the CatGH5 interface that is capable of parallel processing in order to efficiently process an quantity of data/files (that the 32-bit version is not up to the task of handling well).

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Ability to wait successful connection to PI Data Archive and download PI point information during startup

    (Posted on behalf of our customer)

    It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Interface for GE HABConnect FLDTIME Support for COUNT Objects

    Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. PI Buffer subsystem - management tool + robustness improvement


    1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.

    2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add Mod10 to Custom Data Type Manipulator for Modbus Interface

    Please add support for SquareD Mod10 custom datatype to the Modbus Interface.

    Schneider Electric uses a custom datatype that uses four 16 bit registers. Each register represents an integer. Each integer is then multiplied by a factor and all results are added together.
    Currently the only way I know how to read this is to create a PI modbus point for each register value, then create a calculated PI point to perform the math to add them together. All the values are in consecutive registers, so they could be read with one call to the device, if there were a…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  19. Parameter for restarting the interface if no connection to the OPC server can be established after a defined period of time

    We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI UFL Interface can read input files from non-UNC paths such as Azure File share

    I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED