PI Connectors

Welcome to the PI Connectors feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering 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. UFL / Generic file & web based interfaces interoperable with EDS & OCS

    Connectivity to “universal devices”; used for general purpose connectivity to many industrial devices and systems; capabilities include accessing REST Web services and parsing generic MQTT based messages.

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

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Connector for Siemens SIMATIC PCS7 relay support

    Allows customers to leverage the PI Connector relay for improved security, ease of deployment and maintenance when PI Connector for Siemens SIMATIC PCS7 is implemented in a process network with DMZ communication to the corporate network.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  4. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI Connector Relay - Add ability to retrieve cached OMF meta data like Types and Containers

    As an OMF application developer it will be very useful to have the ability to retrieve and have a look at the already created and cached OMF meta data like Types and Containers.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support string data types for PI Connector for EtherNet/IP

    String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  7. IEC61850 encryption

    Implement TLS encryption between the IEC61850 Connector and the target IED(s) as per TS 62351.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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".

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add support to the PI Connector Relay to support OMF Delete and Update actions

    The OMF specification outlines that delete and update messages are included within the specification, but those capabilities are not yet included in the PI Connector Relay. It'd be great to be able to delete or update previously created AF Elements or Types--for example, in the case where an edge device is upgraded to include a new sensor feed, which now needs to be appended to the existing AF Element Template created for that edge device.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide documentation and examples of how to interact with the PI Data Collection Manager API.

    - Enable Programmatic configuration for OMF applications to automate onboarding process
    - Swagger specification

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  11. PI Connector for FANUC Focus should give a warning to users when they change the machine IP address for an existing data source.

    In the PI Connector for FANUC Focus, each data source has the IP address of the related machine specified. The "Device ID" is also part of the configuraiton. If a Device ID is not specified, the IP address is used as part of the Device ID and ends up becoming part of the AF hierarchy as well as the PI point names.

    If a user goes to change the IP address for an existing data source, and the default Device ID is being used, they will inadvertently create a second set of PI points (Duplicates, orphaning the original PI points…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →

    Any configuration changes made to the device id or IP address after initial configuration, will be met by a warning message which the user will have to accept before proceeding with the changes.

  12. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  15. Increase the default log size

    The current default log size in the event viewer is 1MB. Although it can easily be increased, a larger default (100MB+) would allow to catch errors the first time they occur and allow for further troubleshooting then having to change it and have to replicate the error one more time.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. "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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  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