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. Allow PI APS to rename PI Points

    PI APS is now not able to rename a PI Point name. If the item name is changed on the Datasource side we wish that APS rename the Pi Point.

    5 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 →
  2. Log bad timestamps for the PI RDBMS Interface

    When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the actual bad timestamp received from the RDB should be logged as part of the error message.

    This would coincide with the following error:

    "pitm_settime() error - 15002. Using current time."

    5 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 RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow OPC DA  Output Tags to capture OOO events

    Currently there is no way to send corrected values to the OPC DA Server since they are triggered by snapshot. It would be useful if there was a way to alter the values that get sent in case there are substituted/replaced values.

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

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add a watchdog counter to API shared memory

    Add a watchdog counter or something similar into the shared memory header. If the counter fails to update, initiate UFO.

    If PIBufSS crashes, data loss can occur.  implement something that allows UniInt to know that the Buffer Subsystem is not responding and initiate failover if available.

    This was previously enhancement 119481.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. SNMP: Throttle scan specific informational messages as the interface may fill up logs every scan frequency

    This is for SNMP version 1.6.3.0, the following message is printed every scan frequency:

    "Scan class <scan class number> for device <IP address> will be skipped due to previous pending requests"

    And this needs to be throttled as the logs may be get filled up quickly with this type of messages.

    Note: This was previously Enhancement 124938.

    5 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. Enhancement for Advise tags to poll  OPC server when Excmax expires

    Currently, when an advise tag does not get a value in an ExcMax period,  the interface will send the same value to PI over again without going to the OPC server (assuming that the OPC interface has not disconnected from the OPC server during that interval). This can cause the OPC interface to continuously send the wrong value to PI over and over again. ( last known good value) with current timestamp

    This enhancement would allow the interface to behave in the following way:
    When advise tags are configured and ExcMax expires, the interface would poll the OPC server for…

    5 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 →
  7. Enhance the OPC Interface to specify which groups are not receiving data

    When a polled group does not receive data for more than 2 scan cycles, the interface updates the device status health point to 5 | Error | One or more groups not getting data. It will be useful to also specify which scan classes did not receive data (Example, if scan classes 2,4 and 5 are not receiving data: 5 | Error | One or more groups (2,4,5) not getting data or 5 | Error | One or more groups not getting data - 2,4,5)

    Note: This was previously Enhancement 123110.

    5 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 →
  8. PI OPCtoCSV Tool: Filter by OPC ItemID

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. It is possible to filter the items by subbranch like the PI APS Connector for OPC DA interface, but unlike the APS Connector, it is not possible to filter by OPC ItemID using the PI OPCtoCSV tool.
    We have an OPC server with around 20k items that we read into PI, however, using the OPCtoCSV tool it takes 12 hours to extract about 2k of these PI tags and 200k other OPC items that we are not interested (mostly just metadata). Filtering…

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

    4 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 →
  10. Alert user when the interface discards values

    Example:  When using a distribution tag, the number of tags returned and number of values sent to PI can be mismatched, due to missing aliases or data that does not need to be collected.

    It would be helpful to identify what values are dropped or were not updated in PI.  While there is the @rows_dropped variable, it can only be used for distribution tags and may have limitations when used with stored procedures.

    4 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 RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  11. DeltaV Smart Connector Enhancement

    I think it would be a good idea to allow exception settings to be created. The DeltaV history collection settings only allow for compression. Since many/most users use 1/2 compression for their exception value then perhaps we could have a check box on install of the smart connector to turn a general exception rule on. The point of the smart connector is so that a user shouldn't have to modify tags after they are created from DeltaV.

    The other enhancement that would be great is if we didn't have hard-coded security groups (DeltaV and Deltavadmin user) but could put in…

    4 votes
    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 →
  12. SNMP Interface to support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.

    SNMP Interface should support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.

    4 votes
    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 →
  13. PI Event Frames Generator - Fix 'merge consecutive' in PIBAGEN mode.

    To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running  in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.

    119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
    124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
    119363 - Consecutive subbatches can get merged incorrectly

    Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.

    4 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 →
  14. AutoPointSync for OPC DA should work on 64bit servers.

    AutoPointSync for OPC DA does not install or run correctly on 64bit servers. As most new servers are 64bit this would seem to be an essential capability.

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

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  15. PItoPI should switch from COLD to WARM failover instead of exiting

    As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, older versions supported COLD failover. In the case of upgrading the interfaces, the old configuration with COLD failover would cause them to refuse to start thus causing data loss or data delay.

    The interface could instead log a warning that COLD failover is no longer supported and switch to WARM failover.

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

    We’ll send you updates on this idea

    1 comment  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  16. DNP3: store data as "bad"

    Add functionality to treat the data as "bad" and send a digital state instead, when status flags are sent with the event and status bits are set to TRUE. Right now, the data is sent to PI and marked as "questionable".

    Note: This was previously Enhancement 125605.

    4 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 →
  17. Enhance connection logic to source PI server during Interface startup

    When PitoPi Interface starts up, it prints a message saying that it secured a connection with the Target or Host PI server as follows:  PIAPI Successfully connected to <Target_PI_Server>:5450. Then it begins to load target PI points and it starts looking for the source PI point even if it doesn't have a connection to the source PI server. This will result in pipt_findpoint for source tag returned [-5] Tag Not Found

    So this enhancement request is to handle situations when it doesn't have a connection to the source PI server at startup. If there are X number of points on…

    4 votes
    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 →
  18. Support data collection across data diodes or similar technology

    Regulatory and/or security requirement to separate data collection from data storage using a one-way data flow. Could apply to Interfaces or Connectors, for example PI Interface for Emerson Ovation.
    PI Interface/Connector -> one-way data flow -> PI Server/EDS/OCS

    3 votes
    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 →
  19. 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…

    3 votes
    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 →
  20. 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 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 →
  • 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