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.

How can we improve PI Interfaces?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Interface / Connector to the SILA Lab Equipment Standard

    Hi all,
     
    i got to know this standard:
    Standards – SiLA Rapid Integration
    This standard is a really good approach to connect various types of lab equipment. Over it it is possible to fetch for example the RPM of a mixing device, temperature of a heater etc.
    For my understanding, this screams loudly for a time series recorder with analytic options.
     
    Thanks for your support
    Thorsten

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

    We’ll send you updates on this idea

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

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

    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 →
  4. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support of the PI Annotations in the PI-to-PI Interface.

    Having the support of the PI Annotations in the PI-to-PI Interface.

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

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. PI Buffer subsystem - management tool + robustness improvement

    1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
    2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  7. PI to PI automatic recovery if time desynchronization between the machines.

    We see a data gap in one PI Data Archive after the machine hosting the PI-to-PI interface was one hour in the future. In this case, the buffer disconnected from the machine when the issue happened, The buffer did not work correctly and there was a data gap in the target server.

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

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. 1 vote
    Sign in Sign in with OSIsoft
    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 →
  9. Add Mod10 to Custom Data Type Manipulator for Modbus Interface

    Please add support for SquareD Mod10 custom datatype to the Modbus Interface.

    Schneider Electric uses a custom datatype that uses four 16 bit registers. Each register represents an integer. Each integer is then multiplied by a factor and all results are added together.
    Currently the only way I know how to read this is to create a PI modbus point for each register value, then create a calculated PI point to perform the math to add them together. All the values are in consecutive registers, so they could be read with one call to the device, if there were a…

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

    We’ll send you updates on this idea

    0 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. PI to PI interface should perform first scan so that future data can recovered

    /fd parameter is only used while performing real-time scan. If scan rate is set to a higher value such as a day, the user would need to wait for the first scan (after a day) to get future data. This should be done at interface startup. For use case see notes for Case # 895278.

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

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  12. PI Interface for OPC DA retry writing data when it receives a CONNECT_E_ADVISELIMIT error.

    I would like the ability for the PI Interface for OPC DA to retry writing data when it receives a CONNECT_E_ADVISELIMIT error. Certain OPC servers return a CONNECT_E_ADVISELIMIT error when write requests are received in quick succession, and having a setting to retry writing the data would be better than the current method of performing a restart of the service. The issue is exacerbated when the network is unstable.

    1 vote
    Sign in Sign in with OSIsoft
    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. Embed more videos inside of help topics

    Add the YouTube help videos that exist on the OSIsoft Learning channel to the "Help" section of ICU. For example, the UFL designer YouTube videos would appear alongside the corresponding documentation that should be accessible from ICU > Help > Interface Manual...

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

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 →
  15. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 →
  17. 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 →
  18. Allow PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    PI EMDVB interface stops because of time difference between SQL and PI servers:

    "Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

    That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

    I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

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

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  19. Read-only versions of the PI Interface for RDBMS

    Several PI Interfaces that previously only had read-write versions (e.g. OPC DA, SNMP) now have read-only versions to help protect the data source from unintended or malicious edits.

    We need the same for the PI Interface for RDBMS. Since the PI Interface for RDBMS already comes in 2 versions (32-bit and 64-bit), we will now have 4 versions. The documentation must be clarified so that the user knows exactly which install kit to download.

    1 vote
    Sign in Sign in with OSIsoft
    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. Improve error messages in PI ICU

    Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

    Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.

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

    We’ll send you updates on this idea

    0 comments  ·  PI ICU  ·  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
COMPLETED