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. 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
    Sign in Sign in with OSIsoft
    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. 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.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    PI EMDVB interface stops because of time difference between SQL and PI servers:

    "Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

    That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

    I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make UserID and ReviewerID available from BatchQuestion table for PI Interface for Wonderware InBatch

    Currently UserID (DoneBy_User_ID) and ReviewerID (CheckBy_User_ID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. More external resources for high latency networks with PItoPI, specifically with satellite networks

    I have been working with a customer who works with oil rigs and satellite networks and they requested that more external resources be available for how to efficiently operate PItoPI in a high latency environment. Currently there is only one internal document that may be out of date.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. debug an arbitrary number of tags belonging to a PI OPC interface instance

    It is currently possible to debug one tag, or all tags. Logging timestamp and data for all tags is expensive and make logs harder to read, so one one would like to select an arbitrary number of tags.

    1 vote
    Sign in Sign in with OSIsoft
    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 →
  12. Accept the dd-mmm-yyyy format in the absolute time syntax for history recovery start and end times

    The PI Interface for RDBMS currently accepts the format dd-mmm-yy but not the format dd-mmm-yyyy for history recovery start and end times.

    The former format lacks the century, so the year is ambiguous. The latter format solves this problem and so should also be accepted as a valid time format.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  13. Modifying the functionality of Trend Advise feature for PI OPC interface

    As a PI OPC Interface user I would like to get step-like trends whenever that the Trend Advise parameter is enabled (even with having large exception and compression deviations that filter some of the events) so that I don't need to enable the step attribute for each PI tag.

    1 vote
    Sign in Sign in with OSIsoft
    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 →
  14. Option for PI Interface for UFL to purge read-only files

    Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Offset timestamps send by  PI Interface for  Environmental Systems Corp StackVision

    Please allow the option to offset data sent by the interface. This will enhance the ability to compare time stamps between data sources and the PI Server  in different timezones.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. DNP3: add functionality to allow outputs

    DNP3 - add functionality to allow outputs for binary and possibly other object groups/variations.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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)

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  18. Create a clearer, shorter INI file syntax

    Most of the problems appear in the FIELD, MSG, and message sections of the INI file. Note the difference in clarity, readability, and length between the current and proposed syntaxes below.

    Current syntax:

    [FIELD]
    FIELD(1).NAME="Tag"
    FIELD(1).TYPE="String"
    FIELD(2).NAME="Date"
    FIELD(2).TYPE="DateTime"
    FIELD(2).FORMAT="yyyy-MM-dd"

    [MSG]
    MSG(1).NAME="MessageSection1"
    MSG(2).NAME="MessageSection2"

    [MessageSection1]
    MessageSection1.FILTER = (MessageSection1 message filter)
    (MessageSection1 code)

    [MessageSection2]
    MessageSection2.FILTER = (MessageSection2 message filter)
    (MessageSection2 code)

    Proposed syntax:

    [Variables]
    Tag String
    Date DateTime("yyyy-MM-dd")

    [Messages]

    <(MessageSection1 message filter)>
    (MessageSection1 code)

    <(MessageSection2 message filter)>
    (MessageSection2 code)

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  19. Always use arc_append when archiving data using SIPowerTG interface

    This is the interface from the Siemens Power TG EMS system. The problem is with the saving of Alarm and Event text messages. There are instances when the data files are produced out of order. When data is sent out of order the interface seems to go into arc_noreplace mode and our data is lost.
    To store Alarm and Event messages, the duplicate record check is turned off so there is no way to overwrite data, therefore the arc_noreplace is a meaningless protection. Data will never be over written.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  20. UFLDesigner should aid with visualizing the flow of control through the INI file

    Currently, the UFLDesigner is focused on helping the user add content (variables, filters, actions, etc.) to the INI file. However, the UFLDesigner does nothing to help the user understand the interaction between these components.

    Rather than having the 5 tabs on the left pane, the UFLDesigner should be rearranged to show the flow of control through the INI file, perhaps as a programming loop. Then the user can add content to the skeleton loop.

    The loop arrangement would also help the user debug the INI file, since now the loop can be stepped through, line by line, showing the value…

    1 vote
    Sign in Sign in with OSIsoft
    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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED