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

    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  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Convert incoming string data to float and provide division all in the same tag instead of a PE

    OPC server is outputting data with the currency data type (VT_CY) and it needs to be stored in the float type.  As per the OPCtoCSV document, the OPCtoCSV tool/OPC interface invokes VariantChangeType in order to convert this currency value to it's string representation before PI receives it.

    "Some OPC servers have property values that are type VTCY. The VTCY type is intended to represent monetary values. A VTCY value is a fixed-point number with four digits after an implied decimal point that is scaled and stored as a 64-bit integer. When VariantChangeType converts a VTCY value…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Batch Framework Interfaces - Officially support fanning tag data to a PI Collective

    Unlike other PI interfaces, the Batch Framework Interfaces do not use buffering. If the interface loses connection to the PI Data Archive, the interface continues collecting data and stores it in its local cache. The PI Batch Database is primary-only so it did not make sense to fan data to other PI Collective members. However, this is no longer a consideration if Event Frames are being written. There should be an officially tested and supported way to fan tag data to a PI Collective.

    33 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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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)

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    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 Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

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

    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

    3 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Batch Framework Interfaces - [TIME] placeholder should consider whether TS=LCL is configured

    Batch Framework Interfaces - [TIME] and [TIMESTAMP] placeholders should consider whether TS=LCL is configured (meaning the interface is processing incoming events as Local Time). Currently, values of these placeholders always show up as GMT timestamps.

    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

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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?!

    8 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 Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  11. ICU startup on high latency networks

    On high latency networks, it can take ICU many minutes to start because every interface on the PI Data Archive is checked. Minimize startup time by caching a node's registered interfaces.

    53 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 →
  12. 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 arcnoreplace 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

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

    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 →
  14. 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

    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 →
  15. AutoPointSync for OPC DA should work on 64bit servers.

    AutoPointSync for OPC DA does not install or run correctly on 64bit servers. As most new servers are 64bit this would seem to be an essential capability.

    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  ·  PI Interface for OPC DA  ·  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

    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 OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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).

    8 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 →
  18. 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…

    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 →
  19. PItoPI should switch from COLD to WARM failover instead of exiting

    As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, older versions supported COLD failover. In the case of upgrading the interfaces, the old configuration with COLD failover would cause them to refuse to start thus causing data loss or data delay.

    The interface could instead log a warning that COLD failover is no longer supported and switch to WARM failover.

    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  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI ICU should not allow PItoPI COLD failover configuration

    As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, the PI Interface configuration utility still allows COLD failover to be selected. This leads to an invalid configuration and the interface refuses to start.

    PI ICU should not allow the selection of COLD failover as it does not allow HOT failover, both of which are not supported by the interface.

    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  ·  PI to PI Interface  ·  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