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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Real Time Snapshot Support

    PI System Connector:  Need real time snapshot data support for the PI System connector.

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

    We’ll send you updates on this idea

    23 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    This 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.

  2. 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.

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    We 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.

  3. 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.

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

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

    We’ll send you updates on this idea

    3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    As 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.

  5. 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…

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  6. Have PI System Connector support null system digital states

    Would like to have the connector support Null System digital states. Null system digital states can work locally on a PI Server. Would like the connector to support all the options found locally so that we could accurately sync systems.

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

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

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

    We’ll send you updates on this idea

    PLANNED  ·  1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 destination

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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).

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  19. Possibility to confiure AF Prefix - PI System conector

    For the PI System Connector it is possible to configure a prefix for PI Tags. We also need the possibility to configure a prefix for AF related items like Event Frame Attributes or tables.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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").

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    We 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.

← Previous 1
  • 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/PREVIEW
COMPLETED