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. Make Data Persistence Settings Configurable

    Currently, .zip folders containing processed files can reach up to 256MB in size. Browsing the contents these folders can be difficult due to the number of files within.

    Being able to specify either a file count of folder size parameter would help simplify this process by breaking the zipped folders into more digestible, user configurable sizes.

    1 vote
    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 →
  2. Identify the updated or changed nodes on the Type Definitions Export

    Be able to identify the changed (new, updated, removed) nodes that are exported in the Available Type Definitions file through the connector interface.   For systems that are in flux, there's not another way to identify those PI AF elements / attributes that are changed without saving different versions of the Export file and using a file comparison tool to see what has changed.  If the export file contained a date on each item on when it was created/updated (if that's available) that would help identify the new or changed items.

    When there are nodes and attributes that were removed from…

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    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 →
  4. Be able to browse for PI Asset Database and Root PI Asset Path

    On the Server List page, under "PI Asset servers", after the "Hostname or IP address" of a new PI Asset server has been specified, the user should be able to browse for the PI Asset Database and then the Root PI Asset Path. That is, the user should not have be forced to type these in, which can be error-prone.

    1 vote
    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 →
  5. Create a connector for Profinet

    Profinet is an industrial protocol which communicates over Ethernet. It offers a number of desirable features and functionalities which many of our customers find, or will find as the protocol becomes more widespread, very useful for collecting data from their industrial devices.

    http://us.profinet.com/technology/profinet/

    1 vote
    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 →
  6. Consistent version naming of PI programs

    PI Interfaces, PI Connectors, and other PI programs that are infrequently updated (e.g. PI Interface Configuration Utility, PI Diagnostics, Machine Signature File Generator) currently use the #.#.#.# version naming convention, while the other PI programs are named after the year, release number, and service pack number (e.g. 2017 R2 SP1).

    My suggestion is to reserve the #.#.#.# format for internal use and only expose the customer to the "year R# SP#" format, which is easier to read, recite, and remember compared to the #.#.#.# format.

    1 vote
    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. Share PI server configuration information across all PI Connectors by default

    In most cases, the same PI Data server and the same PI Asset server will be used for all PI Connectors that a customer is using, so it makes sense to propagate the most recently inputted PI server configuration information to all PI Connectors by default. This avoids repetitive configuration. Then the user only needs to configure PI server information if it differs from the default.

    1 vote
    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 →
  8. "Connected" to invalid PI Data servers

    If I add an invalid PI Data server in the Server List page, the PI Connector will say that it is connected to this data source. The status only becomes "Error" when the PI Connector tries to save data to this server. Please change this so that invalid servers produce an error immediately.

    Imagine this scenario. You configure all of the PI servers for the PI Connector. It says that everything is OK. You move on to configuring, say, the INI file for the PI Connector for UFL. When communication fails, you will likely try to troubleshoot the INI file…

    1 vote
    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. Use a consistent language-region separator for Locale

    Currently, the language-region separator in the Locale choices can be any of "-" (hyphen-minus), "–" (en dash), or ":" (colon). For consistency, please use only 1 separator.

    1 vote
    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 →
  10. Use the most recently used Locale as the default

    The default Locale is currently "English - United States" for all new data sources. Please consider using "English - United States" as the default Locale only for the 1st data source, and using the most recently used Locale as the default for all subsequent data sources. This saves the user from repetitive Locale configuration.

    1 vote
    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 →
  11. Make CONCAT take an arbitrary number of arguments

    Currently, CONCAT only takes 2 arguments, so you need to nest multiple CONCAT (or just use the & operator) if you want to concatenate multiple strings. This can be avoided if CONCAT could take any number of strings as arguments.

    In general, users expect associative functions to take an arbitrary number of arguments.

    1 vote
    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 →
  12. Branson Welders

    I am interested in a Branson Welders Connector.

    1 vote
    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 →
  13. PI Connector for HART-IP interoperable with EDS & OCS

    Update PI Connector for HART-IP to be interoperable with Edge Data Store (EDS) and OSIsoft Cloud Services (OCS).

    0 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 →
  14. PI Connector for Modbus Serial

    Develop a PI Connector for Modbus Serial. 

    Connectivity to Modbus slave devices; used for general purpose connectivity to many legacy industrial devices.

    Interoperable with Edge Data Store (EDS) and OSIsoft Cloud Services (OCS).

    0 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 →
  15. Update PI Connector for OPC UA to be interoperble with OCS & EDS

    Update PI Connector for OPC UA to be interoperable with Edge Data Store (EDS) and OSIsoft Cloud Services (OCS).

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Connector for DNP3

    Connectivity to DNP3 based data sources, popular legacy standard protocol in Utilities industry.

    0 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 →
  17. PI Connector for J1939/CAN

    Connectivity to J1939/CAN based data sources; used for connectivity to operational and diagnostics data from commercial vehicles and heavy construction equipment.

    0 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 →
  18. Make a PI Signal Generator Connector (Ramp Soak + Random)

    Please consider combining the PI Ramp Soak Simulator Interface and the PI Random Simulator Interface into a single PI Connector. The upgrade of these PI Interfaces is important because they come bundled with the PI Data Archive—nearly every PI system uses them. It is also the perfect opportunity to show off PI Connectors to students and new customers without burdening them with the step of connecting to a data source, since Ramp Soak and Random generate their own data.

    0 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 →
  19. Connectivity to Pro-Face-SP5000 series

    Pro-Face- SP5000 series HMI/PLC's are being used to replace an existing Allen Bradley solution and a connectivity option to Pro-Face HMI/PLC is needed.

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

    We’ll send you updates on this idea

    1 comment  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow PI Connector for NOV WITSML to use proxy server

    Some organisations enforce connection to the external network to be made through a proxy server.

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

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI 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