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. Better error handling in DCM UI

    For some cases where disallowed or poor configuration causes unexpected behavior, the UI should give a visual indicator and explanation.  Two examples:
    1. No write access for Relay to AF DB when using the PSC.  Result: replication of AF objects fails with many error messages.  Digging through log, found a message that indicated permissions issue on target AF DB.  In DCM, all was green. Would have been good to have an error or warning symbol on the Relay object with message about missing write permissions on Destination.
    2. Added a second destination AF DB with reference to same Data Archive. …

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

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

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow UFL Connector to show status when HTTP request fails

    This enhancement would allow the UFL Connector to be able to write a status to it's tags when a HTTP request fails, such as 401 or 503. 

    Currently, a bad HTTP request will fail before attempting to parse with the .ini, so  there is no way to control this behavior via the .ini.

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

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

    We’ll send you updates on this idea

    1 comment  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

    4 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 →
  6. 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.

    4 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 →
  7. Log device information when the Connector receives errors from a device

    Currently the Connector logs when it receives errors, but does not print information that can be used to determine which device is reporting the errors.

    We currently need to perform a wireshark trace to look at the individual packets to determine which devices are sending errors.

    4 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 →
  8. PI Connector for OPC UA Ignore First Value

    Some OPC UA servers send an initial subscription value of BAD or Bad_WaitingForInitialData when a subscription is first made. This data does not reflect integrity or the health of the data stream, and as such is not desirable to archive this value in some situations.

    This request is for the connector to have a configurable flag to no longer store the initial value sent by the UA Server data source.

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    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. Program objects (BACnet object type 16) also bought through by the connector

    The program object description is often very useful to understand what the various object instances relate to. At our site the description holds the Asset designation and that would allow correct assignment of the analogue and binary object instances to the correct asset.

    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 →
  11. Uninstall only the installed files & folders

    It is standard for uninstallations to follow a procedure similar to this: Remove all files that were added during the installation. Then remove all folders that were added during the installation if they are currently empty.

    The PI Connector for UFL does not follow this procedure. My folder of INI files was in the PI Connector for UFL installation folder. Then I uninstalled the PI Connector for UFL and lost my INI file folder. Luckily, I was able to recover it.

    Please change the PI Connector for UFL install kit and any other install kits that behave this way to…

    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 →
  12. UFL Connector HTTP compression

    Large data sets need to be pulled from a REST server on the internet which supports HTTP compression. Since this feature is not supported by the UFL Connector, the data will need to be retrieved in an uncompressed format. For the current project, this means several Gigabytes daily.

    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 →
  13. Add ‘No Replace’ mode to UFL Connector

    Currently the only PI Data Archive ‘Store Mode’ options are ‘Insert’ and ‘Update’. I’m currently working on a project where a large quantity of data needs to be downloaded daily from the internet using the REST client node. To reduce chances of data loss (e.g. due to download failure), the Connector will be configured to retrieve the same data set several times throughout the day. The best option at the moment is the “Update” mode. This however will place unnecessary load on the PI Data Server as large quantity of archive records are re-written with the same data throughout the…

    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 →
  14. 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.

    3 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 →
  15. 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
    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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. Cygnet - Check for prerequisites during the installation process instead of in the logs on startup

    Currently, if some Cygnet prerequisites are missing, the following error is logged:
    Although the errors are clear, this verification step should also occur during the initial installation process.

    Please review the "Installation requirements for PI Connector for CygNet" in the User Guide.
    And subsections "Install the ODBC drivers" and "Verify connectivity with ARS".

    3 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 →
  20. 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 →
  • 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