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 writing SYSTEM digital states when a bad status is received by PI Adapter for OPC UA

    Currently if PI Adapter for OPC UA received a status other than "Good" for an event, it will not write the data to its endpoint. PI Adapter for OPC UA should be able to write a SYSTEM digital state that indicates the status it received.

    28 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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. History Recovery for PI Adapter for OPC UA

    As a customer, I need to be able to recover history on the data streams so that data can be migrated from one system to another.

    23 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 →
  3. PI Adapter for MQTT

    Create a PI Adapter that supports the MQTT messaging protocol and is capable of writing data to EDS, PI, and OCS.

    20 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. PI Adapter for Structured Data Files

    Create a PI Adapter that supports parsing data from simple file formats (CSV, XML, JSON, plain text) and is capable of writing data to EDS, PI, and OCS.

    18 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

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    PI Adapter for Structured Data Files 1.0.0.138 is now available. Please reach out to your Account Manager or Customer Success Manager with any licensing inquiries.

  5. PI Adapter for RDBMS

    Create a PI Adapter for relational database management systems (RDBMS) to make data available in the PI Server, OCS, and EDS.

    10 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 →
  6. PI Adapter for (generic) MQTT to enable auto-discovery of key value pairs using wildcards

    When reading from a generic MQTT broker, we currently need to specify explicitly each key value pairs we want to collect inside the data selection json configuration file. This prevents us from really being agile at the time of the initial setup and for each new information we want to collect, as we need to explicitly define the information manually into the Adapter.

    We would like the PI Adapter for (generic) MQTT to be able to capture automatically exposed key value pairs in the MQTT broker following a wildcard pattern. For instance take this example payload:
    {
    "EquipABC.Location": "0020121047111948",
    "EquipABC.Status":…

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. PI Adapter for Azure Event Hubs

    Write a PI Adapter that supports the Azure Event Hubs protocol and is capable of writing data to EDS, PI, and OCS.

    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 →
  8. PI Adapter for MQTT's Sparkplug B component should allow for data messages to be sent without metric names

    According to the Sparkplug™ MQTT Topic & Payload Specification Rev 2.2 on page 43 (https://www.eclipse.org/tahu/spec/Sparkplug%20Topic%20Namespace%20and%20State%20ManagementV2.2-with%20appendix%20B%20format%20-%20Eclipse.pdf), metric names should only be included in birth messages and for data messages, the metric alias should be used. The way the Sparkplug B component currently works is it looks at the metric name rather than the alias, which will mean that any client that sends data following the Sparkplug spec will not have its data messages read by the adapter.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Logical Compression for Sending Edge data to Site or Cloud

    The ability to define rules such as if a value is within it's limit, then don't send data up to PI or Cloud systems SO THAT we can reduce the data flow for our slow satellite links used for remote assets.

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