PI Connectors
Welcome to the
PI Connectors feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. 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.
-
PI System Connector should be able to delete values on the destination server if they are deleted on the source server
Sometimes when performing analysis recalculations, values are dropped from when they were initially recalculated. For example, when an analysis runs initially, it may calculate 15 values, which are then written to the source and transferred over to the destination as expected. However, if I perform a recalculation where I choose to permanently delete existing values and recalculate due to some of the analysis inputs having changed, and only 10 values are now written to the source server, these values are written to the destination, but the existing values that are now "incorrect" are still present. I would like for the…
31 votesPlanning is underway to enhance PI System Connector to support global configuration enabling the propagation of deleted values from source to destination PI System.
-
implement the option to choose between append or replace in the configuration
It would be nice to be able to choose between append or replace when configuring a new source in a PI system connector, to be able to choose how to copy the data in real time. Since right now by default it is like replace. In the RDBMS interfaces of the source we have several data with the same timestamp, and when copying that data the connector to the destination system only copies the last value, that is, it replaces it. We would like it to be possible to choose between append or replace data copy and that the data…
19 votesPlanning is underway to enhance PI System Connector to support global configuration for an append write behavior.
-
Improve the structure of the history recovery after connector restarts to ensure that initial period of history recovery is complete
The 30-day history recovery by the connector after restarts should get activated only after the initial history recovery is confirmed to have completed successfully.
8 votes -
Have more KPIs/diagnostics for PI System Connector
In Data Collection Manager, it would be good to have a status on Currently Synchronized Elements, Events, Tags, structure. Be able to count the events and tags that failed to synchronize since some time. Missing values in tags between source and destination...
Today the diagnostics are poor, difficult to understand and disappear very quickly
6 votes -
Allow PI System connector to actively rectify streams if point type changes are made during runtime
Point changes on the source currently necessitate a restart of PI System Connector to rectify the streams. Allow the tau framework to handle these changes at runtime without restarting the connector.
Currently, if the point type changes are made during runtime, because of the persistence of streams, there is a flood of errors in the message logs which are not consequential to the nominal functionality of the connector. This leads to erroneous conclusions about the state of the connector.
6 votes -
Possibility to change Back registration on relay side
All in all a wrong configuration should be undone easily and not result in a complete re-installation of the system. If this is possible by using powershell scripts (an example is installed for all connections - RemoveAllConnectionConfigurationsRelay.ps1 - maybe it might be a base for a script to remove single registrations).
5 votes -
Support filtering by element template or attribute
Currently we can "filter" what is replicated by including a specific branch. But if using a composite model, say a site with all it's composite assets, and only want to replicate the "foo" assets from all sites, this option does not work.
It is possible to build a weak referenced homogeneous asset model elsewhere under a separate branch and include only this branch. But this can be tremendous amounts of work / automation with all the burden on the client.
An improved mechanism might be like the ESRI integrator -- selection by template type(s). And even more flexible, allow filtering…
4 votes -
Ability to exclude specific branches from syncing through PI Data Collection Manager
The PI Data Collection Manager User Interface has the options to "Collect All Data from this Entire Database" and "Collect Data from a Specific Branch". What we want to do instead is to "Collect All Data from this Entire Database EXCEPT from a specific branch". This is because the users in the target (test) database do not have permissions to configure the branch (element) that we want to exclude from syncing. The current workaround is to install a PI System Connector for each branch of the database that we want to include.
3 votes -
Allow PI system Connector to be Redundant
This product is pushing production data... it should be redundant.
1 vote -
Override PI Point Attributes in PI System Connector
For each PI Point query (Data Archive Only), I would like to specify certain attributes: mainly security. Defaulting to PIPOINT security string is preventing us from using this product because we have special security strings for tags to 1) keep some data limited access and 2) not overload the PI OPC server.
1 vote -
Sort / Search tag-list in PI Data Collection Manager
As a PI engineer, I would like to sort and search the tag lists in PI DCM so that I can verify that the tags I am interested in are created / available in the PI Data Archive.
1 vote
- Don't see your idea?