PI Adapters

Welcome to the PI Adapters feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Adapters. 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.

  1. Support Alarms and Conditions

    Please provide additional information on how we can support Alarms and Conditions (Alarms and Events). In order to get a better understanding of what is needed on our side, we need plenty of information to help build a comprehensive and informative use case. Please comment with the following of information:
    o What is your primary use case for collecting A&C data?
    o How do you collect A&C data today?
    o How is their A&C data stored in PI?
    o What sort of alarm data do you have? I.e. instantaneous alarms, acknowledgements, alarms with a start and stop time?
    o What…

    90 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

    15 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This feedback item has been moved from the PI Connectors forum to the PI Adapters forum.

    We are continuing to support the PI Connector for OPC UA with stability and security releases. However, for feature enhancements, we are considering them for the PI Adapter for OPC UA. We would like to hear more about your use cases for this functionality, so please share with us in the comments.

  2. Add another Archive Mode option for the PI Interface for UFL

    There should be a way to configure the PI UFL interface to both discard duplicate events (same value at the same timestamp) and record multiple unique values for the same timestamp when these events come from multiple data files.

    For example, if multiple data files contain the following entries:

    (Timestamp)  (Value)
    11:00:00      ABC
    11:00:00      ABC
    11:00:00      XYZ

    The following data should be archived:

    (Timestamp) (Value)
    11:00:00 ABC
    11:00:00 XYZ

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

    This feedback item has been moved from the PI Interfaces forum to the PI Adapters forum.

    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 would like to hear more about your use cases for this functionality, so please share with us in the comments.

  3. Allow PI Adapter for MQTT (Generic) to process non-json payloads

    Some MQTT devices do not send json payloads; for example, some devices send a single value as the payload for a specific topic.

    It would be beneficial for the adapter to be able to handle this rather than to convert these payloads into json before they get to the adapter.

    6 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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Enable Auto Discovery for PI Adapter for MQTT SparkplugB to always listen for Birth and Death messages

    When utilizing the SparkplugB protocol for MQTT, it would be beneficial for the adapter to be always listening for birth and death messages from specific Edge of Network nodes.

    This way, the device can send a birth message to have itself added to the data selection array, then a death message to have itself removed. This would enforce a data selection array that's always reflecting the current state of devices connected to the broker, doesn't miss any data messages, and doesn't bloat over time.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Interface DNP3 - unsolicited data listen only mode of operation requested

    Is there an option in DNP3 driver (In fact at TCP level) to make it listen on a certain (usually 20000 for DNP3)? In era of IoT devices, most devices are sleeping devices, they wake up usually once a day and push data to DNP3 Master (PI), however DNP3 PI collector doesn't support this model. As an enduser I would like to utilize this mode of operation at our plant. FYI, there are other products e.g. Citect SCADA and ClearSCADA use two separate ports for Inbound and outbound DNP3 traffic to use the both modes simultaneously.

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

    This item has been moved from the PI Interfaces forum to the PI Adapters forum as we will be focusing on the PI Adapter for DNP3 for future feature enhancements.

    We would like to learn more about the different scenarios in which this specific retrieval of unsolicited data is needed. Please continue to share your comments below.

  • Don't see your idea?

PI Adapters

Categories

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