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. DNP3: handle invalid timestamps from the RTU

    If the RTU provides a timestamp of 0 when using RTU provided timestamps, which does not conform to the DNP3 spec, allow the option to timestamp the event with PI time or drop the event altogether.

    Note: This was previously Enhancement 123208.

    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  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Migrate the PI Universal Interface (UniInt) Framework to use PI AF SDK

    Most PI Interfaces are based on the PI Universal Interface (UniInt) Framework and rely on PI API and its successor, PI SDK. PI SDK has, in turn, been superseded by PI AF SDK. PI SDK also relies on the deprecated and insecure ActiveX technology, which PI AF SDK does not use. I don't know or want to think about how insecure PI API is, even when the Windows Integrated Security version is used.

    For many data sources, the only OSIsoft-supported option to get data from the data source to PI is a PI Interface, partly because an equivalent PI Connector…

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. PI EMDVB Interface - Allow to retrieve "description" column content from SQL DB

    The interface can retrieves Report events [Event,value="Report"].
    Within these events, [Descript] - parameter returning "category" from SQL database.
    We could not retrieve "description" column contents from the SQL DB [BReportEvent] table.
    See case 00902899.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. PI Point Sync for Siemens Spectrum

    Have the functionality to change the Point Type from the PSSS, because it cannot edit Point Type for existing PI Points.

    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 →
  5. Data Verification for the PI Interface for Emerson DeltaV Batch

    Add a feature that performs a verification check of the data in PI against data in the DeltaV Historian and provide a report of any missing or mismatched data.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. Meter Type support for REXU-EA

    PI Interface for EnergyAxis to support REXU-EA meter types.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide ability to disable purge behavior of UFL interface

    The PI Interface for UFL includes a PURGETIME setting to purge successfully processed files (_OK) after some period of time. We have a case where we do not want to purge processed files. We want the data to be in PI but want to preserve the original files in case there are issues. There are cases where the interface can successfully process files and send the data to the PI Data Archive. But the PI Data Archive has an error storing the data and so the data is effectively lost. Keeping the processed files around would give the ability to…

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. Request for customizing the order of the interface instances in PI ICU interface list.

    The interface instancesnames contain the plantsnames and I want to put the interfaces with the same plant name together in the list.

    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  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow scan class 0 to be monitored via Performance Counters

    As a PI System Administrator, I would like to monitor the point count and other parameters for scan class 0 via Performance Counters. Currently, this is only exposed via the UniInt Health Tags.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Create a migration path for AMI Interfaces when PI Server is moved to a new machine/hostname

    Currently, AMI Interfaces require a rebuild of the AMI cache files when the PI Server is migrated to a new machine/hostname (Although to clarify if the hostname does not change during the PI Server migration the cache does not need to be rebuilt). This is undesirable for large AMI implementations as rebuilding the cache files can be a time consuming process.

    It is requested that AMI Interfaces should be able to handle PI Server migrations with new hostnames without rebuilding the AMI cache files

    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 →
  11. Add a configuration option to UniInt so that the user can adjust the minimum wait time for checking for new events from the Update Manager

    This affects the delay in Event\Trigger tags. KCS: Delay in Event Points.

    The largest and most variable delay seems to come from the time the event is written to the PI Server and the time the interface (UniInt) picks, which is between 0ms-1,000ms from my testing. This seems to be due to a built-in, hard-coded, delay in how often UniInt checks for events from the PI Server update manager. The serviceeventsx function that is part of the main UniInt loop only checks for new events once a second; this means that sometimes there is no delay if the…

    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  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add a configuration option to the OPC DA Interface so that the user can adjust the maximum advise tag exception delay for Event/Trigger tags

    This affect to delay in Event\Trigger points. KCS: Delay in Event Points.

    When using Event Points, we purposefully do have a delay (if excMax is > 2 s then 2 s else 0.9*excMax) for advise tags (Trigger Point) before they're sent to the PI Server if the event value has not changed since the last scan.

    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  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  13. Improve the recovery process for long EFGEN batches

    Currently if EFGEN is configured to evaluate PI Points at the event end, long batches require recovery start time to be set before the start of the batch. This leads to a long recovery process as many completed batches will be evaluated again.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. Upgrade the most commonly used PI Interfaces to use only the Microsoft Visual C++ 2015-2019 Redistributable

    Please upgrade the most commonly used PI Interfaces so that the only Microsoft Visual C++ Redistributable version that they require is the 2015-2019 version. This will reduce the size of the install kit, make it faster to download, make it faster to install, reduce the wear on the customer's disk, and reduce the clutter in the list of installed programs.

    Here are the versions of the Microsoft Visual C++ Redistributables that some of the most commonly used PI Interfaces currently use:
    OPC DA & OPC HDA: 2008, 2010, 2012, 2017
    PI To PI: 2008, 2012, 2017
    UFL: 2008, 2012, 2013,…

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Manage interface names with service ID

    As a PI system administrator, I would like to use the service ID to define the interface name so that I can organize and manage my interfaces more efficiently. I am currently able to do this with PItoPI but not UFL x64.

    Ideally, I would like to define my service ID with a descriptor (e.g. <pointsource>-<instance ID>) so that my interface is named with this descriptor in PI ICU, PI SMT, Windows Services, and the PIHOME Interfaces directory. With this naming parameter:
    – The interface would be listed in PI ICU & PI SMT as PI
    UFL<pointsource>-<instance ID>

    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

    1 comment  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. Upgrade the PI Interface Configuration Utility to use only the Microsoft Visual C++ 2015-2019 Redistributable

    The PI Interface Configuration Utility install kit currently includes both the 2012 and the 2019 Microsoft Visual C++ Redistributables. Please upgrade the PI Interface Configuration Utility so that it requires only the Microsoft Visual C++ 2015-2019 Redistributable. This will reduce the size of the install kit and make it faster to download and install.

    Even though PI Interfaces are slowly being phased out in favour of PI Connectors, OSIsoft is still releasing new PI Interfaces, and so the PI Interface Configuration Utility will still be around for a long time and it will still be worthwhile to optimize it.

    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

    1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    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 →
  18. Use /opcstopstat when both interfaces in failover pair are shut down

    We would like to have some sort of digital state such as "Intf Shut" written to all OPC tags when both interfaces in a failover pair are shut down.

    Currently, the /opcstopstat and /stopstat parameters (which write a specified state to all tags when the interface is shut down) are ignored if the interface is in failover. We'd like for some sort of status to be written to tags when no data is being collected by either interface.

    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  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  19. Streamlined management of PI Interface for SNMP .pwd file

    When using the interface to gather data for hundreds of SNMP devices, managing the .pwd file becomes very burdensome due to an inability to format the file. Comments are helpful in sorting devices, but they are removed upon encryption. It would be nice to see a tool that helps with the management of passwords.

    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

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI Buffer Subsystem doesn't use the user who is logged in

    PI Buffer Subsystem must have a option to set up the user account is logged instead of using Windows Domain or Local account that is running the windows service. This is a huge security issue when using Buffer on client computer to send manual data because you will need to create a Mapping or Trust and give permission in so many pi points when the user logged on computer should have access to write in few pi points.

    Please prioritize this one!

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