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. Support Regex engine in the message filters

    It would be nice to have regex matching and replace in PI UFL ini files.
    Also, would be nice to have anything other than ASCII encoding support (ex UTF-8..with/without BOM, etc)

    Use cases: ex. we need to parse timestamps where year has either 2 or 4 digits. PI UFL cannot do that.. so if we could have a regex match statement to match the 2digit year and pad it to 4 digit (or vice-versa, cut the first two digits).

    Regex is a totally different beast, lot more powerful than the current simple search patterns allowed.

    15 votes
    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 →
  2. 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.

    13 votes
    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 →
  3. 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.

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. and operator

    Add a function that can be used in the UFL Configuration File to perform bitwise operations. For example, a function similar to the AND operator in Performance Equations and Asset Analytics.

    8 votes
    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 →
  5. Support Automatic Failover for PI UFL

    Currently UFL only supports two independent instances for redundancy purposes.

    8 votes
    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 →
  6. 8 votes
    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 →
  7. Add another Archive Mode option for the PI Interface for UFL

    There should be a way to configure the PI UFL interface to both discard duplicate events (same value at the same timestamp) and record multiple unique values for the same timestamp when these events come from multiple data files.

    For example, if multiple data files contain the following entries:

    (Timestamp)  (Value)
    11:00:00      ABC
    11:00:00      ABC
    11:00:00      XYZ

    The following data should be archived:

    (Timestamp) (Value)
    11:00:00 ABC
    11:00:00 XYZ

    5 votes
    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 →
  8. UFL Designer should include a test mode to verify INI behavior with a data file.

    One can do this, to some extent, piecemeal with functionality the UFL Designer already has. However, it's a very manual process and does not actually have a way to show what data would be sent to PI for a particular file. An explicit test mode or test function, where the Designer outputs what the results might be for a supplied data file (Values of each variable, what would have been sent to PI, et.c) would be very helpful in building and verifying INI files.

    5 votes
    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. 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
    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. 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.

    3 votes
    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 →
  11. PI UFL MULTIPLE Language Support

    PI UFL currently supports only english.
    I would like PI UFL to read multiple language, for my case japanese character.

    PI UFL does not support to extract data from line with japanese character contained. For example, when Message Type-> Message Filter has Japanese character, Data Extraction does not display target line.

    2 votes
    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. PI UFL: Support String Interpolation for Print() Function

    Allow Print() function to evaluate runtime variables before outputting text to the log.

    For example: I have created a Counter variable that increments for each event that is successfully sent to PI. I would like to output the final tally to the logs but printing the raw number [Print(Counter)] is not valuable without context. Instead, I would like to combine literal string text with the dynamic value of this Counter variable:

    Print("Events sent to PI: {Counter}")

    2 votes
    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 →
  13. UFL Interface - Option for PRINT statement to not write to PI SDK log

    I use PRINT statements in my UFL ini files to help identify points that need to be created or edited in our PI System. The ini file has useful parameters to help me manage the size of UFL logs on the disk. Unfortunately all the PRINT messages also get written to the PI SDK log. All these messages cause the log files to grow to very large sizes (a few hundred MB daily). It also makes the logs difficult to read if we need to find another issue.

    Could we have the option to have PRINT write only to the…

    2 votes
    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 →
  14. 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)

    2 votes
    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. Please allow to use a hex value as a delimiter, which will allow to specify a Carriage Return (0x0D) as a delimiter

    While PI Connector for UFL supports FOREACH (CsvGetItem(__Message, char(13))) to allow using a Carriage Return as a delimiter, it does not support Serial input.
    This leaves PI Interface for UFL the only option to work with Serial input. Please allow to use a hex value as a delimiter, which will allow to specify a Carriage Return (0x0D) as a delimiter.

    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 →
  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
    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 →
  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. 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 →
  19. 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 →
  20. 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 →
← Previous 1
  • 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/PREVIEW
COMPLETED