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.
-
Support SAP HANA multitenant database
We would like the Integrator to support connecting to SAP HANA multitenant databases. The SAP ODBC writer used for PI Integrator for SAP HANA assumes that <port> takes the form 3<instance number>15 as stated in the HANA v2.0 SPS00 documentation. Since this is not true for multitenant databases, PI Integrator for SAP HANA does not currently support multitenant databases.
10 votes
AdminJoy Wang
(Product Manager, OSIsoft)
responded
PI Integrator for SAP HANA 2019 is currently on hold. We will update this idea when more information is available.
-
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 -
Add ability to select a subset of assets for backfill/Update in a view.
The current 'Update' feature backfills all assets matching the asset shape defined in the view.
However, when there is a need to back-fill only a small set of assets in a view there is no option to select such assets.
Adding a select option would prevent updating all assets in the view and user could select only those assets which require a back-fill.4 votesThank you for your feedback! We would need more discussion with supporters to understand the problem.
How does the lack of this functionality impact your work? How often does this happen? How many assets are typically in your view? And how many assets are typically affected?
Does the new automatic updates through persistent signups (introduced in 2018) mitigate this problem at all?
Please feel free to email me or post a comment to help us understand the pain point.
-
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 -
Option to split date and time into separate columns
SAP recommends using compression on column store databases to conserve RAM and disk space resources (https://blogs.sap.com/2016/08/12/how-and-why-to-do-compression-of-column-store-tables-in-sap-hana/). Since date+time values are typically unique and compression in SAP HANA is column-based, compression of timeseries data like the data published by the Integrator is more effective if date and time are in separate columns as opposed to a single time column containing both date and time.
2 votes
- Don't see your idea?