PI Interfaces

Welcome to the PI Interfaces 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 Interfaces?

(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. Support Automatic Failover for PI UFL

    Currently UFL only supports two independent instances for redundancy purposes.

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Uni-Int to write to scan-class health tags on startup

    We've noticed this particularly with the RDBMS-PI interface when configured for failover: Health tags that are only written to when the interface becomes primary or has completed its first scan (eg Point Count, Scan Class I/O Rate etc.) say 'Intf Shut' when the instance is actually in 'Backup' mode. Even when changing to Primary status, many of these tags don't get a value till after the first scan, which could be quite a long wait.

    I would like UnitInt interfaces, on startup, to post an 'Initialising' or 'Awaiting 1st Scan' or some such digital state to all health tags that…

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. 6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. Enhance element creation to use user defined element templates

    The interface can automatically create an element at each level of event frames, but the elements do not derive from a template and there is no way to specify any attributes on the element. The enhancement request is to create elements that are based off of different templates for different Event Frame levels it would allow categories, default attributes, etc. to be assigned to the elements associated with the Event Frames.

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add functionality to the interface to adjust timestamps by a configurable amount

    This enhancement would add the ability to adjust timestamps to the PI to PI Interface (Beyond the included options for clock drift and subseconds). Potentially, a setting could be supplied to change the timestamps on all data transferred by a specified number of UTC seconds. This setting should be accompanied by a warning message in ICU and the message logs so that the implications of the setting are understood.

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. change the default behavior of the OPC DA interface to use /DC

    per the OPC DA 2.x spec, the OPC server will call us back for all points that have a changes; even those points where we are polling.

    We have a switch to disable the callbacks for points that are not set to advise: /DC

    Can we make that the default?!

    6 votes
    Sign in
    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 →
  7. Enhance pitopi.ini sections to include point source to make them unique

    The pitopi.ini file is used by the pitopi interface for collecting data from multiple sources and to save other miscellaneous settings such as 'histonly' flags. The configuration ini file uses sections to separate settings between instances with and the format is [PItoPI-<ID>] and this is not unique enough to distinguish settings between different instances that use the same instance ID but with a different point source. So when there are two instances with the same ID (regardless of the Point Source), any changes made to one instance will affect the other instance too.

    Note: This was previously Enhancement 121629.

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. Delete mode in Wonderware InBatch interface

    When run in delete mode for WWInBatch interface, it uses the data source as the system of record--any open batch in SQL will be deleted. However, as abandoned or done  batches are open in WonderWare but closed in PI, the interface may delete batches in PI that are still open in the source. It would be helpful if the interface gave the option of using PI as the system of record regarding batch end times.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. 5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. EFGEN - Allow Zeroth State strings to be used with Digital-type Active Points

    When my EFGen Active Point tags have a type of digital, the interface should allow certain digital states to be designated as a Zeroth State.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Log bad timestamps for the PI RDBMS Interface

    When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the actual bad timestamp received from the RDB should be logged as part of the error message.

    This would coincide with the following error:

    "pitm_settime() error - 15002. Using current time."

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow OPC DA  Output Tags to capture OOO events

    Currently there is no way to send corrected values to the OPC DA Server since they are triggered by snapshot. It would be useful if there was a way to alter the values that get sent in case there are substituted/replaced values.

    5 votes
    Sign in
    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 →
  13. Allow the UFL interface to delete PI tag data or provide some other supported automated method of deleting PI data from a collective.

    There is no way to easily delete data in a time range if you want the changes to occur on both the primary and secondary data archive. It seems the UFL interface would be good to use to do this. You could provide it a tag name and time range and then buffer the delete to both collectives, so the data does not exist on either.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add a watchdog counter to API shared memory

    Add a watchdog counter or something similar into the shared memory header. If the counter fails to update, initiate UFO.

    If PIBufSS crashes, data loss can occur.  implement something that allows UniInt to know that the Buffer Subsystem is not responding and initiate failover if available.

    This was previously enhancement 119481.

    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 →
  15. For PItoPI interface having a source PI-HA server, allow failover on source without using PI interface status utility.

    For PItoPI interface having a source PI-HA server, allow failover on source without using PI interface status utility. This should allow failover based on connectivity and/or a watchdog (like failover if a specific tag stay stale for a configurable duration).

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  16. SNMP: Throttle scan specific informational messages as the interface may fill up logs every scan frequency

    This is for SNMP version 1.6.3.0, the following message is printed every scan frequency:

    "Scan class <scan class number> for device <IP address> will be skipped due to previous pending requests"

    And this needs to be throttled as the logs may be get filled up quickly with this type of messages.

    Note: This was previously Enhancement 124938.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enhancement for Advise tags to poll  OPC server when Excmax expires

    Currently, when an advise tag does not get a value in an ExcMax period,  the interface will send the same value to PI over again without going to the OPC server (assuming that the OPC interface has not disconnected from the OPC server during that interval). This can cause the OPC interface to continuously send the wrong value to PI over and over again. ( last known good value) with current timestamp

    This enhancement would allow the interface to behave in the following way:
    When advise tags are configured and ExcMax expires, the interface would poll the OPC server for…

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  18. Enhance the OPC Interface to specify which groups are not receiving data

    When a polled group does not receive data for more than 2 scan cycles, the interface updates the device status health point to 5 | Error | One or more groups not getting data. It will be useful to also specify which scan classes did not receive data (Example, if scan classes 2,4 and 5 are not receiving data: 5 | Error | One or more groups (2,4,5) not getting data or 5 | Error | One or more groups not getting data - 2,4,5)

    Note: This was previously Enhancement 123110.

    5 votes
    Sign in
    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 →
  19. Support multiple Modbus devices on the same machine

    Add support for multiple Modbus devices (using the same IP address but different port numbers) on the same machine. For example, the interface could allow the user to configure something like this:

    /dn= xxx.xx.xxx.xx:43120,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43122,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43124,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
     
    Note: This was previously Enhancement 121980.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  20. DeltaV Smart Connector Enhancement

    I think it would be a good idea to allow exception settings to be created. The DeltaV history collection settings only allow for compression. Since many/most users use 1/2 compression for their exception value then perhaps we could have a check box on install of the smart connector to turn a general exception rule on. The point of the smart connector is so that a user shouldn't have to modify tags after they are created from DeltaV.

    The other enhancement that would be great is if we didn't have hard-coded security groups (DeltaV and Deltavadmin user) but could put in…

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