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. UNIINT Interfaces and Connectors should be able to retry an output event if output write fails

    When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on.  User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.

    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 →
  2. Quindar interface should allow tracing of values from the data source for a specified PI point.

    The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

    1 vote

    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 →
  3. UFL Interface - Increase UFL designer sample data file size limit beyond 50 KB

    The UFL designer currently limits the sample data file size to 50 KB. This requires users to truncate their text files until it is below this limit.

    15 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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. PI-SNMPTrap interface request support for SNMPv3 trap

    PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.

    Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.

    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 →
  5. PI Interface for GE HABConnect support of SCTIME request

    Currently, the PI Interface for GE HABConnect supports FLDTIME requests, which provides the timestamp of the field device.  In the absence of this, the default is the timestamp of the Sampler when HAB API makes an unsolicited update to the interface. 

    If SCTIME was a request that was supported, the timestamp that the sampler received data from the field device could be returned instead.  This would be helpful for two reasons. 

    1.  As an alternative to FLDTIME: SCTIME would standardize the timestamps coming in when field devices are not on synced time clocks

    2.  As an alternative to the update…

    2 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 →
  6. History recovery from multiple tags with one output tag

    I have a scan-based output point writing multiple PI values to the relational database as described here:
    https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

    I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
    https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

    Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.

    1 vote

    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 →
  7. Source and destination tag mapping list

    Customer would like the ability to have PItoPI create a list of tags that includes the FULL name of the source tags, as well as the destination tags they are mapped to.  This will greatly assist in managing tags that are being sent to a remote customer.

    2 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 to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. PI PerfMon tags to support Timestamp DataType

    There are some performance counters that are Date and Time based.

    PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.

    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. SNMP Interface outputs a .txt file that includes the SNMP devices that are timed out

    For the SNMP Interface, the suggestion would be to have the interface output a .txt file that includes the SNMP devices that have lost connection with the interface. This could be useful when there is a high volume of SNMP devices that connect to the interface.

    1 vote

    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 →
  10. Consistent Naming Convention for the UniInt Health Points Across Versions for the SNMP Interface

    The health point names for the Read_Only 1.6.8.1 SNMP Interface have a different naming convention than the health points for Read-Write SNMP Interface 1.5.1.306. In order to keep monitoring consistent across version upgrades, the suggestion is to keep naming convention of the health points the same across versions.

    1 vote

    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 →
  11. Replace pipc.log and PI Message logs with the Event Viewer

    PI Connectors already use the Event Viewer to log messages. It is time for PI Interfaces to do the same.

    0 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Improve error messages in PI ICU

    Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

    Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.

    1 vote

    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 ICU  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. Allow Tag Template Triggers to trigger on blank placeholders

    Currently, Batch Interface Framework interfaces implement tag template triggers that can trigger whenever a placeholder has any value. These interfaces should also support triggering when a placeholder does not have a value. For example, our SISBatch data source has separate columns for Operation and Phase information. We would like to record the value of the [DESCRIPT] column in a tag only for non-phase batch events (i.e. trigger the tag template only when the [PHASE] placeholder is blank).

    5 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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. EFGEN - Allow for null/blank values to be Zeroth State for active point

    When my EFGen Active Point tags have a null value, the interface should be able to designate this as a Zeroth State.

    13 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

    TELL US MORE  ·  3 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. Suppress the message "exception attributes corrected through the SDK read"

    In the PI Interface of UFL we would like the option to suppress the message: "exception attributes corrected through the SDK read" for values of excmax larger then 9hrs.

    1 vote

    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 →
  17. Remote PI ICU

    Regardless of where interface info are stored (PI Module DB or AF), it would be useful to have a remote client tool allowing administrator users to configure interfaces  like they do with tags and AF objects. Today when you have to change configuration you need to connect remotely to the interface node and that often requires a demand for permissions through firewalls (or a travel in the worst case), determining a delay of days.
    I imagine a client tool connected to the PI server only, and a future release of the PI Interface (i.e. PI OPC) detecting configuration changes while…

    47 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  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  18. Name support in BACnet Network Discovery Tool

    Can you remove the restriction to use only an IP address in the BACnet Network Discovery Tool?  The interface will correctly load and poll tags to a network device referenced by name instead of IP, however the Discovery Tool has the limitation of being IP only.

    1 vote

    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 →
  19. Migrate the PI ICU settings away from the PI Module Database

    PI ICU settings are currently the main reason why the PI Module Database continues to live on even the most up-to-date PI systems. Please consider migrating the PI ICU settings from the PI Module Database to the PI Asset Framework or a separate file.

    This way, PI administrators have 1 less legacy PI feature to worry about eventually migrating and 1 less legacy PI feature that they need to keep visible in PI System Management Tools.

    39 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

    5 comments  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  20. Upgrade the PI Interface Configuration Utility to a responsive web-based user interface

    OSIsoft's migration from PI Interfaces to PI Connectors is very slow. Even after the migration is complete, many PI Interfaces will not be upgraded to PI Connectors, so users will continue to use the PI Interfaces and the PI ICU to configure them.

    Please consider upgrading the PI ICU to a responsive web-based user interface, much like the PI Connector administration pages. The PI ICU is currently very cramped, very grey, not resizable, and a bit hard to navigate.

    7 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 ICU  ·  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