PI Integrators

Welcome to the PI Integrators feedback page!

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

(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. Improve the UI to allow the starting/stopping of multiple views at once.

    There are a variety of reasons why being able to handle views in bulk would be nice. If I am cleaning up the UI it would be easier to delete multiple views at once. If I am doing maintenance on a target and I want to stop a subset of views, then I currently have to do them one at a time. Allowing the option to select multiple views would aid in these tasks.

    7 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 →
  2. Allow the choice of 24 hour and 1 day sampling intervals to handle DST transition periods

    Make the PI Integrator handle DST transitions better by allowing users to choose between a sampling interval of 1 day (can be 23 or 25 hours on DST days) or 24 hours. Currently, the PI Integrator will publish 24 hours when a sample frequency of 1 day is selected, causing timestamps to shift during DST transition days.

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add support for OAuth2 authenication for the Hadoop target

    It would be good to support more types of authentication. The current release of Hadoops add OAuth2 support to WebHDFS. This helps PI Integrator for BA to integrate with enterprise data lakes utilizing single-signon systems.

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

    We’ll send you updates on this idea

    1 comment  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  4. Include Annotations of Event Frames into Event Views

    Customer would like to do Batch reports in BI Tool and Annotations contain important information, like Operator comments, reasons for changed values etc.

    14 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. Increase 100k stream limit

    As an engineer looking to leverage hundreds of thousands of tags for BI, I would like to use a single integrator instance to publish all of the data rather than installing multiple instances on different nodes.

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

    We’ll send you updates on this idea

  6. Allow "PI View" target to be disabled

    I would like the option to remove or disable the "PI View" target on the Data Warehouse, Azure, and SAP Hana editions. 

    In these editions, the PIIntegratorDB is expected to remain small because the data is published out to a separate database.  The problem, however, is that users may accidentally publish very large views to the "PI View" target instead of, for example, Azure Data Lake.  This can fill up drive space on the SQL server and prevent the Integrator (or other services that rely on that SQL server) from running.

    For these editions, most users will not be publishing…

    10 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 →
  7. Add option to limit time period for 'Last Recorded Value' Data Context

    For data such as daily volumes produced, we need exact values from PI and Interpolated data just doesn't fit in this case. So we need to configure such columns with 'Last Recorded Value' Data Context. With this setting we certainly get the last archived data from PI, however we do not know if the data is stale.
    It would be great to have an option to limit time period for 'Last Recorded Value' data context.
    Example: Replace stale data with NULL if data is older than a month/year.

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

    We’ll send you updates on this idea

    1 comment  ·  PI Integrator for SAP HANA  ·  Flag idea as inappropriate…  ·  Admin →
  8. Filter based on tag attributes

    As a data scientist, I would like the output from the integrator to only include values for tags that are actively updating. When the PI administrator disables scanning on a tag, I would like the option to filter the row or at least send a NULL value instead of interpolating the stale value.

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for SAP HANA  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow users to "Add Columns" while "Modifying View" even if there is no time series values selected.

    Allow users to "Add Columns" while "Modifying View" even if there is no time series values selected.

    This will let us export things like 'path', 'description', 'category', 'name', etc. Which may be useful on their own, or when joined with another table.

    This has the additional benefit of making table joins easier, as time series tables are almost guaranteed not to have any columns with unique entries.

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

    We’ll send you updates on this idea

    2 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  10. Option to delete target database when view is deleted

    When a PI View is deleted from the Integrator User Interface, the Publication Metadata and target data tables are both deleted for that view. For a view with a non-PI View target such as a SQL target, however, only the Publication Metadata table is deleted. The Integrator will no longer consider that view name to be reserved after deleting the view, but using that name again for a new view with the same target requires us to manually delete the target table if there is a change to the shape or we do not want to append to the existing…

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

    We’ll send you updates on this idea

    7 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →

    Correction to earlier comment by Matt Ziegler: This idea was not fulfilled in PI Integrator for Business Analytics 2018 release. This idea is currently not planned for a future release. If you have a use case and desired behavior for a particular writer and want to discuss further, please comment below or email me. Thank you!

  11. Provide Bulk Column Configuration

    The current method for adding columns and changing their Data Content type (value, average, min, max, etc) is clunky and time consuming.  You can only change (or add) one column at a time, and you have to wait for the data view to refresh after each change.

    Ideally, I would like to have the ability to switch from the default UI (Column headers with real data) to a configuration UI that has a more tabular configuraiton layout or a layout similar to AF. 

    I want to be able to select multiple data items and change them all to be "Average"…

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

    We’ll send you updates on this idea

    6 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →

    Correction to earlier comment made by Matt Zieger: PI Integrator for Business Analytics 2018 does not support bulk column configuration. This idea is currently not planned. Feel free to contact me if you’d like to discuss more. Thank you!

  12. Cross-Column filtering on PI Integrator

    Have to be able in the filtering page of the PII4BA to 'include all columns where any/all of these conditions are true' and then select where a given attribute is greater, lower, etc. than... another attribute present in the preview table. Now I am able only to define constants (e.g. 100, 50).

    6 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. Allow to include open Event Frames

    The integrator only includes EventFrames that are closed (have end time). That is not included in the documentation, so a major issue for me now.
    The reasoning is that an open EF may not have all data or correct data. I would prefer to let the user decide on that and allow to include open eventframes. After all we can filter out the open ones using row filters.

    I planned to use the integrator to get rid of OLEDB Enterprise. Now it turns out i cannot reach all my data. Looking seriously into returning the license.

    The reasoning is

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  14. Display more than 100 records (or show the total number of matching records)

    Allow the user to display more than 100 records in Modify View screen or at least show the total number of rows as additional information.

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add ability to export stored Events for Event-based analysis, not only interpolated

    Currently we can export PI data using a given interval, returning evenly-spaced rows of data.

    However, for some uses i need to have the original events stored in PI, not interpolated.

    E.g. i need to create a report that contains every value that the operator has entered (e.g. a catalyst dosing volume) in the duration of an EventFrame.
    For that i would need Archived values like i have in OLEDB Enterprise.

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

    We’ll send you updates on this idea

    6 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  16. Automatically remove data from continuous views

    As an engineer using PI View or SQL writers for a report, I would like option to remove data older than a certain cutoff. For example, a continuous view is used to generate data for a report on the last 8 hours. Data older than that are no longer needed for the report and should be removed to avoid unnecessarily large tables.

    One workaround with Text and Hadoop writers is the Append Timestamp option, but there's no ability to remove data from other targets.

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

    We’ll send you updates on this idea

    4 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →

    For supporters of this idea, what is the downstream client tool that consumes the data prepared by the PI Integrator? Is the concern about disk space or how to only display data for a specified time range?

    For the former, this seems to be a different type of “rolling” reporting use case that we do not currently have a solution for. In the mean time, as Rory mentioned below, a stored procedure on SQL would work if this idea is intended for SQL writers.

    For the latter, is it possible to create “rolling timespans” for your graphs, reports, tables, etc.? For example, here’s a video on how to create calculated measures for a table based on last day or month of data: youtube.com/watch?v=NevFWL2JoMU

  17. Allow for sampling rate that is faster than one event per seconds

    High frequency data is increasingly common. With examples in manufacturing of events happening entirely within a few 100s of milliseconds.
    The request is to allow the export of interpolated data at a rate higher than the current limit of 1 event per second.

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

    We’ll send you updates on this idea

    1 comment  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  18. BI Integrator preserve Column Configuration on Filter Change

    When you copy a BI Integrator Job ans change some settings in the Filter all attributes are added to the column view.

    We remove Attributes that are not needed e.g. Level1 Attributes when we only Need the Level2 Child Attributes. On a change the Level1 Attributes are always added.

    We rename Attributed and change the export settings e.g. Aggregstion or UOM. On a filter change the original Attributes are added again.

    We would prefer an option/setting in PI BI that no column is added to the column view and you can select them by the Add Column function.

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  19. HA/Failover mechanism for the PI Integrator for ESRI

    As a user of the PI Integrator for ESRI, I would like a High Availability/failover mechanism for the integrator (data relay and application server components).

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Esri ArcGIS  ·  Flag idea as inappropriate…  ·  Admin →
  20. Keeping AF structure consistent with the Map layer

    There is a new map feature created, while adding a new element based on the same element template in AF.

    However, while deleting one of the existing AF elements does not delete the map feature.

    Customer is monitoring oil wells. They are rebuilding the AF structure (using custom AF SDK script) once a day. They want to display only the active oil wells. The newly added oil wells are displayed alongside the updated ones and the removed ones (features) from the AF structure. They want to remove the map features for the non-existent elements (inactive wells).

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

    We’ll send you updates on this idea

    0 comments  ·  PI Integrator for Esri ArcGIS  ·  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