PI Interfaces

Welcome to the PI Interfaces feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering 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. 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
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. OPC DA interface to read data for advise and polled tags at startup

    If digital tags are part of advise groups and the flag to write "Intf Shut" is enabled in the OPC DA interface, then digital tags can read "Intf Shut" for hours/days/weeks, if the value does not change after an interface restart (for example, 2 pumps on the same duty, and they are only swapped every 2-3weeks). The unused pump reads "intf Shut" until it is started.

    It would be better for the OPC interface to get new values for ALL tags after a restart, regardless of whether the value has stayed the same before and after the restart, and timestamp…

    1 vote
    Sign in
    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. OPC DA, A&E historical recovery

    We have seen that the primary OPC interface will be connected but we don't see data coming across since the OPC server itself seems to have a problem. Since the connection is still active we won't failover to the secondary. We have to leave Notifications to look for IORATES to drop so we know we have to go and manually fail over to the secondary but this isn't good enough as we now have a data gap for the duration it takes for us to log in and failover.
     
    What if the secondary interface actually buffered a configurable amount…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support dynamic OPC addresses

    My OPC server's items have the OPC server node name included in the itemID, for example: serverA.AB_1234.PV. I have redundant OPC servers and redundant interfaces (in failover) and would like the tags to refer to the correct OPC address including when the OPC servers fail over. Currently the workaround is to create two sets of tags, each pointing to one OPC server's itemIDs in their instrument tags and then merge the data with AF or a PE.

    3 votes
    Sign in
    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. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. DeltaV Smart Connector configurability

    Smart Connector foo DeltaV should let user configure some default attributes for tags created:
    - User should be able to define what the default point security should be
    - User should be able to decide if tags should be created as Poll or Advise

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. CA ISO Interface - Allow conversion of timestamp values (i.e. InstructionStart) from UTC to local time

    Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences.  Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives. 

    Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. PI Interface for IEEE C37.118 support for Analog data Signed and Unsigned 16-bit Integers

    The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. Suppress creation of an AF Element hierarchy

    As a PI Admin, I may have already created a AF Element Hierarchy corresponding to my BES or MES source data. Therefore I have no need for the interface to create a new AF Elements and I would like to suppress this completely.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Assure changes made to any configuration of an interface are audit trailed

    We noticed that changes to the configuration of newer interfaces / connectors like
    - PI EMDVBCS interface 4.0
    - PI inbatch interface
    - PI Connector Wonderware Historian
    are no longer recorded in the PI Audit trail. (see also TechSupport Case # 937205)
    This is a compliance issue for the regulated industries.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. PI BACnet interface: add support for BACnet Setpoint object

    Add support for BACnet Setpoint objects in the PI BACnet interface.

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add subscribeCOV support to BACnet Interface

    My device only supports SubscribeCOV, but the PI Interface for BACnet only supports SubscribeCOVProperty. I would like the PI Interface for BACnet to support SubscribeCOV like the PI Connector for BACnet already does.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Interface for GE HABConnect FLDTIME Support for COUNT Objects

    Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  20. 1 vote
    Sign in
    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 →
← Previous 1 3 4 5 6 7 8
  • 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