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 Siemens SIMATIC PCS7 Alarm and Conditions backfilling support

    In case of an interruption, the PI Connector has the current capability of backfilling any tag data from the source OpenPCS 7 system.

    Condition data leading to PI Event Frame creation from the connector should also support similar backfilling capability to avoid data loss.

    3 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  2. The MQTT Connector should be able to connect to MQTT Brokers that requires Client SSL Certificate.

    Currently the MQTT Connector only supports username/password authentication. This is great for local brokers/servers, but very unpractical when connecting to cloud brokers like AWS IoT Core. Adding support for Client SSL authentication will make it significantly more useful in a cloud based infrastructure.

    2 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  3. IEC 60870-5-104: Interrogation Type

    Currently, the Interrogation Type selection options are:
    - General interrogation
    - General and groups interrogation
    - General, groups and counters interrogation

    There should be an option for General and counters interrogation

    2 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  4. 2 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  5. Build native connectivity to Roche Diagnostics QC systems

    Roche Diagnostics has built a suit of quality control devices (CEDEX Analyzers) for process control in bio-processing. It would be very important for the business to create in collaboration with Roche Diagnostics a native PI Connector.

    2 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  6. PI Connector for MQTT Sparkplug - Allow users to configure clean session flag

    I would like to be able to configure the 'clean session' flag when configuring data sources on the connector, to allow for messages to be buffered on the broker in the event that the connector is unavailable.

    Currently the connector sets the clean session flag to true, and this is not configurable.

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

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

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

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

    2 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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow filtering of source points

    In the HabConnect Connector the only filtering of source composite ID's for inclusion into PI is through use of wildcards. As a user I want to filter not at the query level to sampler, rather filter out tags in the result set (preferably using regex) that are to be included to PI.

    The current mechanism can be tremendously wasteful in configuration time, tending towards error, and impact system resources. For example, using a record type, say DEVICE, you want only specific substations, you have to create multiple queries for each specific substation. If you need to monitor a dozen substations,…

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support delayed startup of queries for GE HabConnect Connector

    In some EMS configuration it is possible that to connect and query sampler before habitat database has initialized. This can cascade throughout PI -- analytics set to watch for minimum values, applications looking for status changes, etc. It is almost impossible to repair since the source system reported it -- the only way I understand to fix it would be to backfill from eTerra Archive on every failover or startup.

    The current interface supports a delayed startup option, which combined with PERMANENT supports some ability to avoid this condition. However a more flexible solution would be an option, by query…

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  12. Enable GE Habconnect default attributes by query

    Newest version of the GE HabConnect Connector supports default point attributes to be added at the field level. However, many attributes are set at the query level -- security for example.

    In addition, some installations potentially require dozens of queries. Having to set defaults at the field level grows the size of the configuration dramatically, and obscures the important configuration settings.

    Please support setting default attributes at the query instead of, or in addition to the field level.

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  13. IEC61850 - Support connection to servers requiring custom COTP parameters (network addressing)

    The connector should be able to define all the COTP parameters to connect to IEC61850 servers.

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  14. Use DESCRIP_POINT, ANALOG for e-terraPipeline description strings

    The PI Connector for e-terraHabitat HabConnect SAMPLER pulls tag descriptions from the PNTNAM and ALGNAM records. For Oil & Gas e-terraPipeline (a.k.a. ETPL or "LMS") customers, the DESCRIP field on those records are usually left blank, or they have a very generic value. The description for new Pi Tags created by this connector should come from the individual POINT or ANALOG records instead. This information was confirmed by a GE employee as being applicable to all current ETPL/LMS customers.

    For my company, here are a couple of examples:

    DESCRIPALGNAM = "# - Interface Level - #"
    DESCRIP
    ANALOG =…

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  15. WITSML - XML in debug logs instead

    To troubleshoot data collection issues in the PI Connector for WITSML, it is often required to trace the request made by the connector and responses (XML) returned by the WITSML Server. This is currently only available when running the connector interactively. It should be logged in the Event Viewer of dedicated log files for post-mortem analysis and ease of use.

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  16. Redfish - Allow port selection from the DCM UI

    When configuring the PI Connector for Redfish, it will default to port 443 for the target Redfish Server. Servers are commonly installed on custom ports. Currently, the port needs to be manually edited in in DataSource.config.json.

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

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • 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