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. 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
    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 →
  2. Preferring a primary interface failover member

    hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

    https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

    2 votes
    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 →
  3. 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
    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 →
  4. Buffering Manager - add metrics for each buffered interface

    When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.

    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. Store Tagdata in Batch Eventframe

    Our customer want to have the ability to build Batch Reports centrally in AF so that several Applications can access the same data.
    We are already transmitting batch data as Event Frames from our DCS batch package like Simatic Batch and others to AF. We also included other reported values from DCS batchpackage like Educts. But some information like actual product amount or other is not available in DCS batch but as classical PI Tag.
    We would like to have the possibility to add these information to the procedure of the Batch Event Frames. Either by an extension of the…

    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 →
  6. 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 →
  7. 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 →
  8. Allow Buffer to communicate with other buffer

    Currently the PI Buffer Subsystem only has the capability to speak directly with the Data Archive. This setup can have a negative impact on your Cyber Security setup as you are not able to leverage the DMZ between the IT/OT networks as it is designed.

    This request is to allow the PI Buffer Subsystem to communicate with another buffer subsystem to act as a relay to the data archive and would allow all cyber security requirements to be met.

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

    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. 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
    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 →
  12. 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
    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. Allow the same RTU Address to be used across different IP nodes

    The current implementation of the PI Interface for DNP3 does not allow the same RTU address to be used across different IP nodes. The PI Point Location3 attribute is used to specify the RTU address only. If a customer has multiple RTUs with the same address but on different IP nodes, they either have to reconfigure all of the RTUs to have different addresses, or create a new DNP3 interface instance for every IP node.

    Case example:

    Customer has 800 SEL-735 meters, each with a different IP address, and each with a DNP Address (RTU address) of 1. He has…

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  14. Batch Framework Interfaces - Support of two byte languages

    Batch Framework Interfaces currently do not support two byte languages. Please add support of two byte languages to batch interfaces.

    9 votes
    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 →
  15. EMERSON PK based DCS - EMDVB Interface support

    Emerson has a new PK Controller based DCS available (in lieu of full blown DeltaV). This new device is contained with OPC-UA and Batch Exec/Historian. We want support for the existing EMDVB interface to supply S88 based batches into PI Event Frames and/or PI Batch. Additionally, we will want to run the PI OPC-UA interface to get the live module data into PI tags. Do you have support for this today?

    3 votes
    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 →
  16. Automatic restart of the OPC interface whenever OPC server is restarted

    whenever the OPC server undergoes any restarts or configuration changes, the OPC interface will delete all old connections, groups, etc. and it will establish a new connection to the OPC server, loading all ItemID's etc (as if it is an automatic restart of the interface).

    The reason for this enhancement request:
    if OPC server is restarted or undergone configuration changes, all the handles and subscriptions for advise tags are not valid anymore. The interface would get the advise values in an inconsistent manor (values betwen the OPC server and the interface would show a mismatch)

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  17. OPC AE: add history recovery feature

    There is a stronger market demand to have more alarm data in PI so that the alarms can be analysed together with the process data. Existing (as of Oct 2019) PI OPC AE Interface does not support history recovery. Without the history recovery feature (automatic or manual), the interface is less reliable in terms of data loss possibility, especially in highly regulated industries such as Pharmaceuticals. On the control system side, OPC Historical Alarm and Events data access (OPC H A&E) is already available, for example for Siemens PCS7 with their product OpenPCS7. Requesting OSIsoft to look into adding this…

    3 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 →
  18. Encrypt trafic between interfaces/connectors and the Data Archive

    Add an option to encrypt trafic between interfaces/connectors and the PI Data Archive

    5 votes
    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 →
  19. 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 →
  20. 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 →
← Previous 1 3 4 5 9 10
  • 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