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.
58 votesThis item is under technical review. Currently, support for collecting Snapshot data can be achieved via PI to PI interface and should be considered for achieving this specific functionality.
-
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.
15 votesWe have considered including this functionality natively as part of the PI system as opposed to including this in the connector.
-
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.
13 votesAs suggested in the description of this item, PI System Connector uses AF database as the primary source and thus any filtering that is desired at the PI Tag level can be accomplished by referencing only those tags in the source AF database. If users would only like to replicate PI tags without an AF model, then PI-to-PI interface can serve as an alternate option.
-
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…9 votes -
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.
9 votesThere are several edge cases when it comes to replicating analyses. This item needs more deliberation.
-
Multiple AF Databases Support
Support for replicating data from multiple AF Databases.
7 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
3 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 destination3 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.
3 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).
3 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.
2 votes -
Support choosing which collective member is the data source
When configuring the PI System Connector, there is currently no option to constrain the communications for the data source of PI Tag data to a secondary or tertiary PI Collective member.
The ability to force the PI System Connector to use the secondary or tertiary PDA as the data source will allow customers worried about impacting their primary archive's performance to manually balance the load on their collective and eliminate impacting the performance of their existing solutions.
2 votes
- Don't see your idea?