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. Define more explicit system requirements for PI Interfaces

    Define more explicit system requirements for PI Interfaces. According to a customer, despite the Buffer and Bandwidth Calculation Spreadsheet, currently available information does not allow for accurate hardware sizing.

    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  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    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 →
  3. Improved handling of PIBUFSS initialization

    We have encountered a situation where we were unable to write out-of-order data to PI through the buffer subsystem from an interface, apparently because the buffer subsystem was not yet fully initialized when the interface connected to it. Please implement an appropriate wait cycle at interface startup, to ensure that the buffer subsystem (on which the interface is dependent) is fully initialized and available before permitting the interface to complete its connection and initialization.

    Note the case in question arose when the interface service was configured with a dependency on the PI Buffer Subsystem service.

    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 RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clamp Value at Limit

    Ability to clamp or ignore values outside a threshold.
    Example would be to clamp the low value to 'zero' attribute and/or a high value at 'span' - many xmtrs read erratically when at limit (e.g., an empty flow transmitter often reads negative)

    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 →
  5. Allow the Event Frame Templates to be fully customizable in the PI Interface for EMDVB

    Allow the Event Frame Templates to be fully customizable. This will give the flexibility to remove attributes like Product from the PIBatch and Procedure, as it is represented in the lower levels of Event Frames.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. Pi Event Frames Interface Manager, "Remove Interface" needs an 'Are you sure?' pop up box to prevent accidental deletion

    In PI Event Frames Interface Manager, there needs to be a 'Are you sure?' pop up after clicking "Remove Interface" button to prevent accidental deletion of interfaces.

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

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

    Add OMF health function to Citect interface.

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

    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 →
  10. WonderWare InBatch - change phase state logic when a phase end event occurs at the same time as phase start event

    When a phase end event is received at the same time as a phase start event, the WWInBatch interface currently creates batches/event frames of zero duration despite there being phase state events under the phase event.
    It would be helpful if the interface logic is updated so that either:
    the phase end time is updated to the timestamp of the most current phase end event
    or ignore phase end events that happen at the same time as phase start events.

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

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

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

    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 →
  14. PItoPI: Disabling Time adjustment

    the ability to disable the timezone adjustment.

    currently we are calculating daily kpis on our global pi server. with PItoPI we are sharing it to the site pi-servers.
    so the daily kpi for e.g. 1st januar 2019 00:00AM sould alwas have that timestamp. Because if the forward it to e.g. britain, it has the timestamp 31st decemper 2019 11:00PM (adjusted -1h to austrian time)

    plz make it possible to disable it via Location2.

    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 to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  15. RDBMS Interface - Full Sync and Annotations

    The PI SDK writes required for setting annotation values with the exdesc and RDBMS interface are not compatible with Full Synchronization.

    Make this compatible.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  16. Managing loss of connectivity - local data

    For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. RDBMS time stamp precision

    Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp).
    Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair source time stamp to the pi time stamp (precision and rounding issue in SQL).
    I request to add support for sql datetime2 into the ODBC connection, or an option to read the time from the snapshot in seconds since 1.1.1970

    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 RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    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 →
  19. History recovery from multiple tags with one output tag

    I have a scan-based output point writing multiple PI values to the relational database as described here:
    https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

    I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
    https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

    Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.

    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 RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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

    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