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

    2 votes

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

    We are declining this item as we don’t feel it’s the right fit with our overall product strategy for the EMDVB Interface. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  2. Make UserID and ReviewerID available from BatchQuestion table for PI Interface for Wonderware InBatch

    Currently UserID (DoneByUserID) and ReviewerID (CheckByUserID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

    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 →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  3. PI Interface for CAISO Exclude Certain Batch Types

    We would like the PI CAISO interface to parse through the .XML files and exclude XMLs that contain certain specified <Batch Types>. Only certain batch types contain valid data for consumption.

    3 votes

    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 →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  4. More external resources for high latency networks with PItoPI, specifically with satellite networks

    I have been working with a customer who works with oil rigs and satellite networks and they requested that more external resources be available for how to efficiently operate PItoPI in a high latency environment. Currently there is only one internal document that may be out of date.

    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  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI BES Interface (i.e. PI EMDVB): aliasing of Unit Names

    Currently the interface creates PI UnitBatches or Event Frames associated to Units (PI Units or AF Elements) determined by some placeholders specified at the "Unit Procedure" level; the default is "[AREA][PROCESSCELL][UNIT]".
    Moreover the interface properly created a PI MDB or AF structure under an alternate module path, specified in "Batch Setup" section (/SMP parameter).

    It would be useful to have a way to specify different Units instead of the one determined by the [UNIT] placeholder (at least).
    As an example, suppose we want to register unit batches for a PI Unit called Reactor1" when the [UNIT] placeholder values "U6-K54100", and…

    3 votes

    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 →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  6. DNP3: Add slave functionality

    DNP3 - add slave functionality. Currently, interface can only act as master station.

    0 votes

    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 →
  7. Delete mode in Wonderware InBatch interface

    When run in delete mode for WWInBatch interface, it uses the data source as the system of record--any open batch in SQL will be deleted. However, as abandoned or done  batches are open in WonderWare but closed in PI, the interface may delete batches in PI that are still open in the source. It would be helpful if the interface gave the option of using PI as the system of record regarding batch end times.

    5 votes

    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 →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  8. debug an arbitrary number of tags belonging to a PI OPC interface instance

    It is currently possible to debug one tag, or all tags. Logging timestamp and data for all tags is expensive and make logs harder to read, so one one would like to select an arbitrary number of tags.

    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 →

    We have reviewed this idea, and it’s not something we plan to implement. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  9. PI EMDVB Interface - Rename Parsed Files

    PI EMDVB Interface - Rename Parsed Files.  Files that get renamed to .999 is no longer available with PI EMDVB.  This file renaming feature was very useful from a system maintenance perspective.  We would easily remove .999 from the active EVT folder and move to an offline directory.  Currently with PI EMDVB, there is no obvious visual indication that the EVT file was parsed completely.

    7 votes

    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 →

    We are declining this item as we don’t feel it’s the right fit with our overall product strategy for the EMDVB interface. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  10. Enhance element creation to use user defined element templates

    The interface can automatically create an element at each level of event frames, but the elements do not derive from a template and there is no way to specify any attributes on the element. The enhancement request is to create elements that are based off of different templates for different Event Frame levels it would allow categories, default attributes, etc. to be assigned to the elements associated with the Event Frames.

    7 votes

    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 →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  11. Unregister interfaces in bulk on ICU

    In scenarios where we have to move interface instances to a new machine, we will have to perform some cleanup after of un-registering the interfaces in ICU. This includes removing the bat files and services. It would be nice to perform this task in bulk.

    0 votes

    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

    DECLINED  ·  1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  12. UniInt should include a test mode for all interfaces that collects data but does not send it to PI.

    This functionality would allow users to test the connection to the data source and inspect the data that is retrieved without sending it to PI. That data might be written to a text file, for example.

    This would allow users to verify settings and data integrity without needing to delete archived values, for example. Potentially, this functionality would also have some type of PI point selection so that user would be able to select which tags the interface should use for this test mode, rather than using all tags (The interface would essentially assume that all other tags have scan…

    3 votes

    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 →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  13. DNP3: add functionality to allow outputs

    DNP3 - add functionality to allow outputs for binary and possibly other object groups/variations.

    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  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support redundancy with OPC event tags

    Currently, with OPC event tags, if the connection between the interface and PI Data Archive is broken and signups lost, the event tags will stop polling the OPC server for data. I would like to see a level of redundancy added whereby if the OPC-PI Server connection is broken, the event tags will default over to a predefined scan class, or alternatively be advise tags.

    0 votes

    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

    DECLINED  ·  0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  15. Create a clearer, shorter INI file syntax

    Most of the problems appear in the FIELD, MSG, and message sections of the INI file. Note the difference in clarity, readability, and length between the current and proposed syntaxes below.

    Current syntax:

    [FIELD]
    FIELD(1).NAME="Tag"
    FIELD(1).TYPE="String"
    FIELD(2).NAME="Date"
    FIELD(2).TYPE="DateTime"
    FIELD(2).FORMAT="yyyy-MM-dd"

    [MSG]
    MSG(1).NAME="MessageSection1"
    MSG(2).NAME="MessageSection2"

    [MessageSection1]
    MessageSection1.FILTER = (MessageSection1 message filter)
    (MessageSection1 code)

    [MessageSection2]
    MessageSection2.FILTER = (MessageSection2 message filter)
    (MessageSection2 code)

    Proposed syntax:

    [Variables]
    Tag String
    Date DateTime("yyyy-MM-dd")

    [Messages]

    <(MessageSection1 message filter)>
    (MessageSection1 code)

    <(MessageSection2 message filter)>
    (MessageSection2 code)

    2 votes

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

    Thank you for your input. We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files. We encourage you to go to the PI Adapters forum to share your use cases.

  16. Batch Framework Interfaces - Allow creation of only the Event Frame levels that exist on data source

    The BES/MES sometimes contains recipes with no Procedure, or even Unit Procedure. The Batch Framework Interfaces should allow the creation of only the Event Frame levels that exist on the data source. This would need to be enabled with an interface configuration parameter so the default behavior is not changed on upgrades to existing systems. This enhancement would not be possible when writing to the PI Batch Database.

    2 votes

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

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  17. Modify the Modbus Interface to accept 32-bit Unsigned Ints from the PLC

    provide a data type to accept a 4 byte unsigned integer from the PLC.  At this point, it would be stored in a 64-bit float in PI DA.

    21 votes

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

    Thank you for your feedback. We do not plan to add native support for 32-bit Unsigned Integers to PI Interface for Modbus Ethernet PLC. Please check out the workaround provided in the comments below.

  18. Reference a local .csv file with mappings (TagName-InstrumentTag) to shorten start-up times.

    The .csv file with TagName-InstrumentTag mappings will allow start the interface without specifying the PointSource, which will potentially shorten the start-up times against systems with larg point count. Once the interface is running it will update this file with corresponding points, which have been created/updated/deleted while the interface has been running.

    Note: This was previously Enhancement 125215.

    0 votes

    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

    DECLINED  ·  0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support for mathematical operations to be performed on timestamps that are stored as SECONDS_GMT

    Time manipulations (adding and subracting) can only be performed on standard datetime formats and not on SECONDS_GMT 

    Note: This was previously Enhancement 118924.

    0 votes

    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

    DECLINED  ·  0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  20. DNP3: DNP3 XML file, make defaults explicit

    Upon initial configuration, the XML config file does not include the default interface settings.  This can cause confusion for the user.  Explicitly add the elements for the default values to the XML config file.

    Note: This was previously Enhancement 123207.

    2 votes

    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 →

    Thank you for your input. We are continuing to support PI Interface for DNP3 with stability and security releases.

    That being said, PI Adapter for DNP3 is now available and we will continue to focus on the PI Adapter for enhancements to DNP3 connectivity. Please check out the release notes and user guide for a comprehensive list of capabilities.

  • 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