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. Allow Modification on PI Integrator published view

    Often, once a view is published, we would like to add a tag to it.

    Unfortunately, for this we need to copy the view and it'll create a copy of the target, forcing us to backfill again all the view.

    We would like this to change.

    Knowing that other companies would like to keep published view locked, this is our proposal:

    - when a copy of the view is made, on the publish panel, you can select a target and also choose to create a new table or select an existing table.
    -> This will allow us to publish to…

    9 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 →
  2. Allow publish to Azure data lake store gen. 2

    Allow PI intergrator for Business Analytics to publish to Azure data lake store gen. 2.

    28 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. Support connecting to a different DNS listener for each of the Integrator's backend SQL databases

    The Integrator currently supports only a single SQL server connection string to access all of its backend databases (PIIntegratorDB, PIIntegratorLogs, PIIntegratorStats). Our organization's SQL Server cluster provides high availability at the SQL database level, however, with a separate DNS listener for each database. When either of the other PI Integrator backend databases fails over to another SQL server, we see errors like the following:
    “SqlUtilities:GetBackendSqlConnection: Error: Unable to obtain open SqlConnection to database, ‘PIIntegratorLogs’,at SQL server path, '(Server)'".

    9 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. 9 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 →
  5. Add support for Group Managed Service Accounts (gMSA)

    Our organization uses gMSAs to run other PI services, so I would like to be able to run the PI Integrator services under a gMSA account.

    13 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 →
  6. Azure IoT Hub: allow Integrator to use device-level connection string

    As an Azure IoT Administrator, I would like to only give the Integrator minimum permissions to my IoT hub in order to minimize security concerns and reduce management overhead for shared access keys. Currently I can specify a device ID in the Integrator's Admin > Targets page, but this still requires a connection string for the IoT hub as opposed to the individual IoT device. I instead want to be able to use the device-level connection string.

    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 →
  7. Add support for multiple events with same timestamp in PI Integrator for BA

    The Integrator for BA appears to be a great fit for exporting event-based data such as Batch Interface Messages to external systems. Interpolation doesn’t apply in these cases so we can use a tag as the ‘Key’ in value mode selection.
    However, there are cases where a tag can have multiple entries at a given timestamp (e.g. EMDVB Recipe Parameter Downloads) and the current behavior is to only include the first value in the output view. This approach results in missing data and makes the integrator unusable in these cases.
    Ideally the view would return all records (as per PI…

    18 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 →
  8. Please have PI Integrator for Business Analytics supports high availability (HA)

    As a user of PI Integrator for Business Analytics, I'd like to have it support high availability (HA).

    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 →
  9. Expose PI Integrator view statuses

    Customers who plan to have a significant number of views need a better way to manage the status of their views other than periodically checking the PI Integrator UI.

    There should be a way to obtain view statuses through other programs (custom or PI), so that users can receive alerts if a view goes into an error status.

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

    We’ll send you updates on this idea

    3 comments  ·  PI Integrator for Business Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    2 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 →
  11. Please have the PI Integrator for Business Analytics support Windows Server Core

    As a user of PI Integrator for Business Analytics, I'd like to have it support Windows Server Core operating systems.

    2 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. Specify desired logging level

    As a PII4BA administrator I would like to specify a logging level so I can filter which logs I want to store and which ones I don't want to store in the database.

    18 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 →

    Is this an issue of limited SQL storage? We have a log retention policy that can be configured by the user in the CAST.UI.WindowsService.exe CONFIG file today. By default it only retains a maximum of 2 months of data AND no more than 100k rows AND no more than 1000MB of disk space. Similar retention policies can be created for the PIIntegratorStats database as well.

    Let me know if this would satisfy the requirement. Or provide more information on how specifying the logging level would help. If you could, which logging levels would you keep vs. throw away and why?

  13. Allow attribute annotations to be published with the Integrator

    I want to publish the attribute annotation for a time series event using the Integrator. For example, if a user enters data in PI Manual Logger, they enter comments as annotations to the tag event. I would like to publish those annotations along with the attribute event's timestamp and value.

    9 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. 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 →
  15. Ability to Create View Templates

    For a large implementation of the Integrator, the ability to create View Templates would be very helpful. While the ability to create a View based on an existing View and the ability to export/import Views are both steps in the right direction, I'd like a View template to be source agnostic with regard to the Asset Shape. For example, I want to configure a metadata view that will have PI Points, uoms, paths, categories, descriptions, etc. for each Attribute I'm publishing in another View. We're talking hundreds of columns as a result. If I try to import this View, then…

    11 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 →
  16. More control over view format (wide verse long tables)

    I would like to be able to have more control over the format of the views. For instance, right now it automatically populates every included attribute as a column. For my continuous data attributes I would like to be able to condense the 50+ individual attribute columns into 3 columns : attribute, value, timestamp. This would make the table a long format instead of wide.

    1 vote
    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 →
  17. Allow large queries to be split up into manageable pieces

    If I build a view in the Integrator that asks the Data Archive for a large amount of information my query can timeout. This will result in the Integrator writing NULL values to certain columns of my view. As a current workaround I just build a view that spans a shorter time frame to decrease the amount of data I ask for in my query to avoid NULL values. I then can use the Update Data functionality to additional time frames in manageable pieces. This is not ideal and I do not believe it was the intended use of the…

    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 →
  18. Allow PiView to be removed from Identities "Allowed Publish Target"

    This is very similar to the "Allow PI View Target to be disabled" suggestion below (I voted for that one as well). - I can understand if PiView needs to remain to simplify installation, but if I have a specific group of users that I want to just be able to publish to specific targets, I CAN"T currently remove "Pi View", and it always comes up 1st on the list of potential dropdowns.

    In this case, I don't want users publishing to PIView, rather I just one to give them a single choice, that is controlled at the Admin level.…

    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. Allow configurable column size (nvarchar) when publishing to a relational table

    The current default column size is 4000 characters. It would be nice to allow the user to have control over this parameter.

    8 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. Add value option to publish element version metadata

    As a PI Integrator user, I would like to be able to publish metadata about a given element's/attribute's AF version metadata (such as number like 0, 1, 2) so that I am aware when an element/attribute version has changed.

    1 vote
    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 →
← Previous 1 3 4 5 6
  • 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