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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Display data for entire time range progressively in map client data table

    As a PI Integrator user, I would like the data table in an Esri map for a PI Integrator for Esri ArcGIS time-enabled layer to progressively display data for the entire time range on the map. This is related to the enhancement request: As Time Passes setting on Integrator Time-enabled Layer

    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 →
  2. Expose additional Kafka target configuration options

    To accommodate high frequency messages to Apache Kafka brokers, additional tuning of Kafka producers can be necessary to prevent high CPU and Disk I/O load. The PI Integrator should expose these parameters to allow users the ability to adjust their system as necessary. The following are common parameters that would allow for this:

    - Batch Size (batch.size)
    
    - Linger time (linger.msg)
    - Buffer memory (buffer.memory)
    - LZ4 compression

    Additionally, many projects may require that acknowledgements be sent back to the producer to confirm that they were properly received. The PI Integrator should provide the option as for whether or not…

    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 →
  3. After manually updating data, the next scheduled publish should ensure it does not publish duplicates

    As a PI Integrator user, if I use the manual "Update Data" option to correct a time period that includes data that will be published on the next scheduled publication run I do not want this next scheduled run to publish duplicate rows. For example, if I have an Event View that publishes on the hour every hour and the last run was at 1:00 PM, if I run update data at 1:25 PM specifying start time 1:00 PM to end time *, the next scheduled publish will look at the 1:00 PM to 2:00 PM time range and therefore…

    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 →
  4. Allow change of target configuration after publish

    Once a View has been published, you cannot change the Target--the dropdown is greyed out on the 'Publish' screen in the designer. You have to re-create the View to publish to a new target, which is a lot more work and opens up the potential for issues or misconfigurations. Use case: if I was publishing to a sandbox environment and now want to publish the View to production, I could change the existing View's target in the drop-down instead of re-creating it.

    Note: This is different from another, completed idea (https://feedback.osisoft.com/forums/555136-pi-integrators/suggestions/35776837-allow-target-configuration-changes-to-be-pushed-ou) as I don't want the configuration of…

    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 →
  5. Push archived values for multiple attributes within one view

    Right now, you can essentially choose one column/attribute to get the archived values and use that as a key. So the timestamp for every column in the view would be the timestamps associated with one column's archived values.
    I would like to push just the archived values for every attribute within in my view and not be limited by one key.

    This would probably go well with this request: https://feedback.osisoft.com/forums/555136-pi-integrators/suggestions/38777014-more-control-over-view-format-wide-verse-long-tab

    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 →
  6. Support attribute renames

    When an attribute(s) name changes, I would like the Integrator to propagate that change to existing views that contain the attribute. The Integrator does support element renames but not attribute name changes. Currently, we have to republish the affected views in order to continue publishing data for the renamed attributes.

    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 →
  7. PI Integrator for BA support for Amazon RDS database

    It would be useful if the Integrator could use Amazon's RDS in addition to SQL Server as a backend for publishing views.

    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 Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  8. Disable automatic matches in Modify View screen

    As a PI View creator with an AF Database with several thousands of elements, I need to disable automatic matches so the GUI would run faster, and when I have finished shaping my data I should be able to enable matches again.

    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 →
  9. Throttle Data Archive reads

    As an Integrator user, I do not want to overwhelm the PI Data Archive when the Integrator reads data, either for an initial view backfilling operation or when I have multiple views running in real-time. I would like the Integrator to throttle Data Archive reads so as to not overwhelm the Data Archive or give me insight when I am making an expensive Data Archive call with the Integrator.

    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 →
  10. Integrator should have a status page

    The Integrator application server should have a status page ("OK" or "Running") so that clients or load balancers can easily determine whether the site is up or not.  This should be implemented when the Integrator eventually supports high availability.

    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 →
  11. Publish event view even if there are no matches

    I have a need to create event views before a process starts and the event frames are created. Right now, I have to create a dummy event frame in order to publish the view since you cannot publish a view with no matches.

    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 →
  12. Create Start Menu shortcut for Integrator

    It would be nice if the PI Integrator installation created a Start Menu shortcut to the Integrator User Interface, similar to how a PI Connector installation creates a Start Menu shortcut linked to the PI Connector Administration page.

    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. Option to disable Integrator REST Services Directory

    Allow Integrator administrators to disable the Integrator's REST API Services Directory as recommended by Esri for production systems. See https://enterprise.arcgis.com/en/server/latest/administer/linux/disabling-the-services-directory.htm

    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 →
  14. Overlapping Time Ranges for Continuous View updates (Rolling Publications)

    I wish that the start time of a continuous view update cycle could precede the end time of the last cycle.

    For example every day query the last 30 days of data and replace rows that have already been written to the target table with the most recent data. This would be a straightforward way to ensure that data in PI and the integrator View are the same for the last 30 days. Manual corrections up to 30 days old could then be captured automatically.

    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 →
  15. Allow English PI Time to be used regardless of integrator language settings

    Other products (such as DataLink) will allow for English PI Time to be utilized regardless of the language settings. For instance, both "-8h" and "-8horas" will work in DataLink if Spanish is the selected language. However, only "*-8horas" will work if Spanish is the selected language for the integrator in the UI.

    The request is to bring the integrator more inline with how other OSIsoft products handle PI Time in different languages.

    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 →
  16. 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 →
  17. 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 →
  18. Improve source AF migration/rename procedure for PI Integrator for Business Analytics

    current procedure <What are the steps to point the PI Integrator to a new AF server for the element and attribute data that it publishes in views?> requires exporting/importing and republishing every single view, which is tremendous amount of work. On top of this, all existing data tables are dropped and re-created. Please provide a utility or an easy way to accomplish it.

    3 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. Allow Configuration of S3 Target Endpoint to Enable S3-Compatible Storage Solutions

    Currently PI hardcodes the AWS S3 endpoint. We would like to target open source S3-compatible storage solutions but are inhibited by the lack of configuration available when setting up the S3 target

    3 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 →
  20. Don't recreate SQL View tables for minor changes

    As a Developer, it would be useful if the SQL tables outputted by the PI Integrator for Business Analytics were not deleted and recreated when minor changes are made to the Integrator View, such as the schedule. This would stop connections/queries being made to these tables from being broken.

    3 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 →
  • 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