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.

How can we improve PI Connectors?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Suppress the creation of "Status Flag" PI Points

    The end-user would like to suppress the creation of the "Status Flag" PI Points, as they wish to keep their point count to a minimum due to the license-enforced point limit.

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

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    3 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 →
  3. UFL Connector - Add elements and attributes to existing AF hierarchies

    Simply, it would be nice if the UFL Connector could add to existing elements and attributes already in place instead of creating a new hierarchy.

    Also, would like the ability to create sub-elements from the UFL connector that span multiple elements and are not restricted to a single instance of the UFL connector.

    Very similar to the "Connector (UFL) can read AF data structure" idea, just more succinct.

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  4. Enable child Event Frames for Alarms and Conditions from PI Connector for Siemens Simatic PCS 7

    Would like to see states of alarms captured as child Event Frames of the parent alarm Event Frame that is currently created. Today this data is only captured in tags.

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

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Point name Illegal character handling in PI Connectors

    Currently source points for PI Connectors that contain illegal characters are handled differently depending on the PI Connector. Some will replace the character while others will map an illegal character replacement when creating the PI Point. These illegal characters should be dealt with the same across all PI Connectors. Examples of illegal data source Characters: * ' ? ; { } [ ] | \ ` "

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We have started implementing a way to handle illegal characters in Wonderware and UFL Connector. If this behavior is desired for a connector besides Wonderware and UFL kindly leave a comment below.

  6. 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
    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 →
  7. Better support for IE

    Some field values are missing or inaccurate when viewed through IE as compared to Chrome.  This was seen in the DCM UI and PSC UI for Data Source configuration.  Some IT environments are locked down to the point that IE built into the OS is the only browser option so it needs to show accurate information.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Keep a consistent order of PI Data servers on the administration pages

    On the Overview page, the PI Data server list grows downwards from the top. On the Server List page, the PI Data server list grows upwards from the bottom.

    Please use a consistent order for the PI Data server list so then one list does not appear out of order compared to the other list.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    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 →
  10. Allow the AF root element name to be configurable

    The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. Simple, readable, user-friendly names for all downloadable files

    OSIsoft's downloadable files are inconsistently named; use hyphens (-), underscores (_), and concatenations instead of spaces; and sometimes contain unnecessary abbreviations.

    For users who keep their OSIsoft files in the same folder, this means either grouping files into subfolders that have readable names or renaming the individual files if they want to identify their files by readable names.

    Please consider using straightforward, intuitive names for OSIsoft's files.

    Some examples (top is the current name, bottom is the proposed name):

    OSIsoft.UFL_1.1.0.76_.exe
    PI Connector for UFL 1.1.0.76.exe

    RDBMSPIx64_3.23.3.7_.exe
    PI Interface for RDBMS (x64) 3.23.3.7.exe

    PIDataLink_2017_.exe
    PI DataLink 2017.exe

    PI-DataLink-2017-User-Guide-EN.pdf
    PI DataLink 2017…

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Warning when stopping a connector about potential consequences

    Some connectors perform some kind of rediscovery of the data source upon start - Such as meta data or current values, etc. When stopping a connector from the UI, a warning should pop-up indicating potential consequences of doing so and what to expect, such as "Restarting the connector will potentially require a long time in order to perform data source discovery."

    This will prevent users from unnecessarily restarting connectors as a basic troubleshooting mechanism.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow data sources and servers to be renamed

    Currently, if you want to rename a data source, PI Data server, or PI Asset server, you must delete the one with the old name and create a new one with the new name, and redo all of the configuration. This is especially a pain for data sources, since they have a lot of configuration.

    Please allow data sources and servers to be renamed to avoid this trouble.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Incoming TimeStamps Utc

    Please rename "Incoming TimeStamps" to "Incoming Timestamps".
    Please change "Utc" to "UTC".

    These small spelling issues come across as sloppy.

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

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  15. Rockwell CLX Connector

    I am interested in a Rockwell CLX Connector.

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

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  16. Read files from .zip folders

    Would like UFL connector to take a .zip folder and read the files within that folder

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow PItoPI APS connector to sync "Point Type" changes

    Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual).

    Please make this possible in a future release.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. Selectively send source data to PI based on network connectivity

    Example:
    - If on network A (which could be satellite or 3G) send Tags 1-10 and buffer Tags 11-50.
    - If on network B (Wifi, wired), flush buffer and send all Tags 1-50.

    Requested by OSIsoft Transportation Team, but very beneficial for all remote mobile asset tracking.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. Selectively send source data to PI based on triggering conditions

    Example 1: If Circuit Breaker trips, begin sending high frequency load, voltage data, etc. Under normal operations do not send this data.
    (condition must allow for definition of a moving window, i.e. Trip occurs, data just before the trip must be sent as well as data after the trip)
    Example 2: Continually collect 10 engine variables. If an engine DTC (Diagnostic Trouble Code) triggers, collect additional set of 5 variables for the time the DTC code is active.

    Requested by OSIsoft Transportation Team, but very beneficial for all remote mobile asset tracking.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. Synchronize behavior between PI Connector for Cygnet and Cygnet enumeration value representation

    The values stored in the “Table Entry” column in Cygnet TRS should match the “State” column in the PI Server Digital states table. This way end users are not confused why the trends in PI do not match the trends in Cygnet.

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

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED