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.
-
Real Time Snapshot Support
PI System Connector: Need real time snapshot data support for the PI System connector.
128 votesUpdate: PI System Connector 2.3.0.1 is not available at this time due to an issue identified with this version. We are working quickly to provide an updated version that resolves this issue.
Original Post: I’m really excited to announce that PI System Connector 2.3.0.1 is now available with snapshot support for PI Points that have compression disabled/off (on the source system). I cannot wait to hear your feedback on this latest version. Head over to https://my.osisoft.com/ to learn more about 2.3.0.1.
We will be keeping this feedback item alive as we continue to work on the next release of PI System Connector. The next release is expected in early 2021, and will expand upon the snapshot support introduced in 2.3.0.1 by adding configuration options and snapshot support for compressed PI Points.
-
PI System Connector with mode to synch AF Analysis and Notifications Templates
As an equipment specialist working centrally, I wish to deploy my AF Element Templates including Analysis and Notifications Templates to my remote sites so I have them managed from a central location. This also insures that remote sites are using the same calculations and KPIs.
32 votesWe are aware of the interest in this functionality, but at this time it is not in our short-term plans to implement.
We would like to learn more about the different scenarios in which you would be syncing your Analyses and Notifications.
Please continue to share your use cases here. -
Replicate AF Analyses with PI System Connector
I would like to have the option to replicate AF Analyses using PI System Connector with the option to mark the desired analyses for replication.
27 votesThere are several edge cases when it comes to replicating analyses. This item needs more deliberation.
-
Add the ability to select a subset of PI Points from a PI Data Archive
The PI System Connector allows to include PI Point replication directly from the PI Data Archive even if they are not reference in the PI AF hierarchy with the "Include all PI points from this PI Data Archive" option.
I would like to replicate only some PI Points that are not referenced, not all. This would remove the need to maintain both a PI to PI and a PI System Connector.
I could create a bogus AF Database referencing those points but I would prefer not to.
21 votesWe are currently researching expanded flexibility of data selection for PI System Connector.
If you haven’t already shared your use case in the comments, please do so or feel free to email me. Your comments are extremely valuable to us as we are selecting the best solution for this functionality.
-
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…
13 votes -
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…
12 votes -
Extend the history recovery max period for PI System Connector to longer than 30 days
Allow history recovery for PI System Connector to be longer than the current max of 30 days
12 votesWe are currently evaluating PI System Connector performance in order to provide you with both configuration guidance and a safe recommendation for the boundaries of history recovery.
Look to see something from us in early 2021!
-
Rollback Option for System Connector
We had an issue with the System Connector and had to reinstall every part of it, but then all tags in the destination system have been created again. The old tags have not been updated anymore. We think about an option to reverse every change the connector did on the destination system (delete AF Elements, Attributes, Event Frames, PI Tags) that have been created by the connector.
We thought of a workflow like this:
Delete the routing of the "not-correct-working" Connector via DCM
Delete the Connector via DCM UI (and de-registering it from DCM and Relay in that step)
Deleting…11 votes -
Add instrumentation to the PI System Connector
Need to add instrumentation to PI System Connector wheras exposing perfmon counters (so PI perfmon can store accordingly in PI tags) on AVG data flow in events/sec for a 120 seconds time period, status of the connector, etc
9 votes -
PI System Connector: Add flexibility on which objects to synchronize
As an architect, I have to model AF structures at a central location, and push them to distributed assets.
I would like the ability to design my AF structure centrally, then replicate it to my distributed assets (e.g ships). Example features that are needed:
- Ability to include Analyses, Notification Rules, and their templates in the synchronization
- Ability to not copy the data from source to destination9 votes -
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.
6 votes -
PI System Connector Destination AF Configuration String should not Contain Source PI Server Name if it is Unreachable
Currently, if the PI Server specified in the source PI AF server is unreadable from the PI System Connector node, the Connector will forward the listed source PI Server name in the configuration string to the destination AF Server. This causes confusion as the Destination AF server will likely not have access to the unreachable source PI Server. Instead, The connector should create a configuration string on the destination AF server stating that the source PI Server Host is unreachable.
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 -
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.
5 votes -
Handle deletions across systems
Ability to have deletions replicated across systems as well (might need to be a config option on how to handle).
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 -
write/send Data to source PI Systems (output tag)
To use the PI System Connector for enterprise applications like machine learning, mvda,... it should also be possible to configure "output tags". the result of analytics on enterprise level are needed also on local PI systems, so for some attributes/tags a two way communication is required.
4 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
3 votes -
support linked tables for system connector
some of our data reside outside the PI System (e.g. in a LIMS System). to commuicate this kind of data to a global PI System, also linked tables and it values need to be sent to the global PI System.
3 votes -
Support for more than one data source
Is it possible to get it soon? it's not an option to set up a host for each system connector. it might be needed to have different data sources to define independent data streams for different use cases (e.g. send Data of AF Branch "A" to global Destination AF Database "A" and Data of Branch "B" to global Destination AF Database "B").
3 votesWe would like to learn more about the different use cases for your independent data streams.
While PI System Connector can support the configuration of data collection from specific branches of a PI AF Database, it seems that there’s also a need expressed here to regarding the destination options which we would like to know more about.
- Don't see your idea?