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. PI PerfMon interface to support ArcReplace

    Right now PerfMon only supports ArcNoReplace. PerfMon has a history of failing over if a server is unreachable. And since PerfMon only supports Hot failover, every time it fails over the new interface tries to write values that the old one already wrote. I would like to be able to specify ArcNoReplace so I don't get an error flood every time the interface fails over.

    2 votes
    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 →
  2. Improve DNP3 Output performance

    Currently DNP3 outputs are done one event at a time. We could improve performance by either supporting multiple DNP messages per TCP packet or multiple analog output commands per DNP message.

    2 votes
    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. Support string tags in PI Interface for CSI UCOS

    The newest version of UCOS now supports string tags.  Currently the CSIUCOS interface (1.0.0.22 as of writing) does not support these types of tags.

    2 votes
    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. PI Interface for GE HABConnect support of SCTIME request

    Currently, the PI Interface for GE HABConnect supports FLDTIME requests, which provides the timestamp of the field device.  In the absence of this, the default is the timestamp of the Sampler when HAB API makes an unsolicited update to the interface. 

    If SCTIME was a request that was supported, the timestamp that the sampler received data from the field device could be returned instead.  This would be helpful for two reasons. 

    1.  As an alternative to FLDTIME: SCTIME would standardize the timestamps coming in when field devices are not on synced time clocks

    2.  As an alternative to the update…

    2 votes
    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. Cal ISO: allow instruction level data to use batch level start time

    allow instruction level data to use batch level start time. Add an option to allow this. use case: the instruction level start time is the time when the DOT should be ramped up or down.  The batch start time is a few minutes before that timestamp.  To get the turbines adjusted in time, they need to use the batch start time.  This gives the operator enough time to adjust the set point and have the new target met by the instruction start time.

    2 votes
    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. 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
    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 →
  7. CSI UCOS Enhancement: Implement Bumpless Download

    The new CSI UCOS API now supports a "bumpless download".

    "CSI has recently added what they call a “bumpless download” feature to their UBrowser application that the interface uses to communicate with the database. What this does is allows the database to be updated without stopping the service. "

    Please implement this feature.

    Note: This was previously Enhancement 121741.

    2 votes
    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 →
  8. DNP3: DNP3 XML file, make defaults explicit

    Upon initial configuration, the XML config file does not include the default interface settings.  This can cause confusion for the user.  Explicitly add the elements for the default values to the XML config file.

    Note: This was previously Enhancement 123207.

    2 votes
    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 →
  9. Enhancement for OPC HDA to add switch  '/outputsnaptime'

    OPC HDA Interface would be enhanced to use  switch '/outputsnaptime'.  For output tags, the interface would use the timestamp from the original event that triggered the output to timestamp the data.

    Note: This was previously Enhancement 124754.

    2 votes
    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 →
  10. Export double-byte characters with HDATagBuilder

    PI Interface for OPC HDA, as well as OPC HDA COM Connector, offer a tool called HDATagBuilder to collect all tags on an OPC HDA Server and export them to a CSV-file that can be used with PI Builder.

    This tool, however, is currently not able to correctly handle double-byte characters well. If it finds one inside item ID's or descriptions, the property value (whether it's the tag name, the description or the instrument tag) simply becomes a blank.

    Please fix this, as more and more DCS's are capable of using them, and even PI DA can handle tag names…

    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. GE HabConnect interface support for both IGNORExTH and IGNOREFLDMSEC

    PI ICU rejects options IGNORE5TH and IGNOREFLDMSEC at the same time. When modeling teams change MEAS fields often, IGNORE5TH is extremely useful to keep data history contiguous. When using field time that is stamped by the EMS, milliseconds are not useful.

    Please remove the constraint on having both options.

    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 →
  12. Add OMF health to Citect interface

    Add OMF health function to Citect 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 →
  13. Enhance the PI Perfmon interface to accept if the first character after the first bracket is #

    Enhance the PI Perfmon interface to accept if the first character after the first bracket is #

    The counter path of NVidia's GPU temperature is \computername\NVIDIA GPU(#0 Quadro M4000 (id=1, NVAPI ID=1280))\Temperature C.

    Enhance the PI Perfmon interface to accept the counter path if the first character after the first bracket is a "#".

    Replied from Techsupport :
    The PI Points cannot be configured because their counter path does not follow the standard counter path "\Computer\PerfObject(ParentInstance/ObjectInstance#InstanceIndex)\Counter".

    The problematic tag is in the format of \VW-AS\NVIDIA GPU(#0 Quadro M4000 (id=1, NVAPI ID=1280))\Temperature C
    Thus, when the interface checked the path and…

    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. Support capture of instrumentation values, such as "voltage" in the EEAMAS interface.

    We are using this interface to capture meter attributes and measurements. However, the voltage comes in the XML files as an "instrumentation value", which is not currently supported. We would like to bring the voltage into a tag for the meter to use in PI analytics.

    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 →
  15. Allow modification of "head_end" in piscc.ini to modify naming convention for elements and tags.

    When our EEAMAS Interface was originally implemented, the HeadEnd parameter was set to "Elster", the vendor name for our meters. So all of our meters from that interface are named Elsterxxx. Elster was purchased by Honeywell, so the name no longer makes sense. We would like to change our prefix for the elements to something more generic like "MTR", since the element name is something that is exposed regularly to end users.

    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 →
  16. OPC Alarms&Events interface should allow to change fields pipe delimiter for PI points

    When using a single PI tag, the fields are delimited by the pipe (|) symbol by default.
    It would be useful to change it to another delimiter or a combination of others. There could be messages containing this pipe (|) symbol, which would make it difficult to split the fields afterwards.

    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. Quindar interface should allow tracing of values from the data source for a specified PI point.

    The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

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

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. 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 →
  20. 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 →
  • 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