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. PI Connector for Wonderware Historian should be configurable to use 'FULL' mode query

    The connectors should have a standard behavior. We believe the Wonderware connector should be collecting data in the same way as the Cygnet connector by getting all the data stored in the source historian irrespective of the value change. Currently, PI Connector WWH uses 'DELTA' mode query where only the changes are retrieved. In some situations, the source value doesn't change much, but we still want to collect the data reliably on PI. To accomplish this, we would like to have the ability to configure the connector to use 'FULL' mode query. Without this Full query option, we have to…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  2. Windows Authentication on the Wonderware SQL databases

    Currently, if SQL server authentication is disabled on the SQL server hosting the Wonderware Historian, the connector cannot authenticate and read from it because the connector is designed to authenticate explicitly using SQL credentials. To be able to authenticate using Windows authentication is essential for some customer to be able to implement the PI Connector for Wonderware Historian, as some organizations disable SQL server authentication for security purposes.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DEVELOPMENT  ·  0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  3. Optionally not include Galaxy name

    Add capability to include Galaxy name or not and include specific areas or not. In the current system I am working with, the primary and backup WW Galaxies are named differently. This causes the Connector to build separate trees in AF.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  4. Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags

    Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags.

    Existing tags were reading from "FxBias interfaces" and in need to let them read from WW historian thru WW connector.

    WW connector is reading names from WW historian and force the names as per WW historian.

    can we rename WW connector created tags to be as per existing tags or not?

    also about compression and exception settings, can we keep existing settings or we must follow WW connector settings only?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Connector for Cygnet - Historical Data Recovery

    The PI Connector for Cygnet is normally used for real-time data acquisition. But, some times it becomes necessary to migrate large volumes of historical data between Cygnet and PI.

    There is a back filling application that can be used to do this, but it is currently unsupported by Osisoft. It would be best to integrate a historical data recovery functionality into the connector.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  6. Wonderware Historian Connector Should store description in an AF attribute

    Wonderware Historian Connector should store description in an AF attribute.

    It has the description in hand as it is written to the PI tag descriptor

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  7. Filter Quality tags PI Connector for Wonderware Historian

    There should be away to filter which quality tags are created. Currently we can only choose all or none.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DEVELOPMENT  ·  1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  8. Wonderware Historian Connector should store some metadata in PI tag attributes

    The Description, Maximum EU, Minimum EU, Engineering Units, etc. that are stored in the Wonderware historian should be stored in the PI tags' attributes as well as the Wonderware AF structure.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  9. Disable Meta data collection for the PI Connector for Wonderware Historian

    We would like to have a way to disable the PI Connector for Wonderware Historian's ability to  collect descriptions and engineering units in the historian.  These can be incorrect at times in the Wonderware Historian.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  10. Connector Failover

    Add failover capability so I can run a pair of connectors that will failover to the backup if the active is unavailable

    51 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  11. Validate credentials before running connector

    Need a way to easily confirm that the credentials are correct before I try and run the connector.  Would like to see any errors surfaced via the web page so I can troubleshoot.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  • 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED