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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. PI UFL Interface - create selected tags using EnablePointCreation parameter.

    Customer noticed that tags can be created automatically, but he does not want to create all of the tags autmatically, but select which tags will be created. He wants to be able to select which tags will be created and which won't.

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

    We’ll send you updates on this idea

    1 comment  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enhance OPC server failover capability

    Need to trigger failover when a watchdog tag is stale for a configurable duration.

    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 →
  17. When Citect Interface loses connection to a device, throttle errors relating to failed tag reads

    OSI PI Citect Interface

    The interface will log an entry to the message log for every tag that it can't source data for. This is fine for a small number of tags that have not been able to read data from Citect. However, when a Citect Unit (eg PLC) goes offline and there are thousands of tags assigned to that unit, every single tag that is scanned is logged with the same message generating thousands and at times hundreds of thousands of log entries in a short time frame, eg every second. This results in a very, very large log…

    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 →
  18. Clarification on InstrumentTag attribute

    If you use IntrumentTag for the query, it has to be a file containing the query, not the query itself.
    You can specify the actual query in Exdesc.

    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 →
  19. Provide the option of specifying an output file path for the processed files that is different than the input file path

    Allow the user to specify an output file path for the processed files that is different than the input file path, moving the files to this "output" path after they are processed.

    Note: This was previously Enhancement 100038.

    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 →
  20. Create a new function indicating if the string can be turned into a number

    Create a new function indicating if the string can be turned into a number. For example, IsNumber() function could return 1 if the string can be turned into a number 0 if not.

    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