The PI Interface for RDBMS is one of the most used PI Interfaces. Unfortunately, the fact that it is a PI Interface makes it unnecessarily difficult to use, and turning it into a PI Connector can help alleviate this. No more Location codes, squishy PI ICU, distributor tags, SQL file in the InstrumentTag, strange notations in the ExDesc, etc.

Implementation a connector that supports the ICCP TASE 2 protocol

We have customers who are using AspenTech IP 21 and would like to have data replicated in both PI DataArchive and OCS in the future. Since the PI Interface is a bit outdated, a new PI Adaptor would make perfect sense (since there is already a PI Connector for WonderWare and Honeywell PHD). The PI Adaptor shall support both PI and OCS.

Develop a PI Connector for Modbus TCP. 

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

Having a connector available for GE HABConnect rather than the interface would be useful to customers that are dealing with large amounts of data and make frequent changes to points on the GE side.  A connector that is capable of automatically updating point additions/deletions/modifications so that this doesn't have to be done manually on the PI side would be very helpful.

Develop new connectivity to replace legacy PI Interface for Mitsubishi Electric MELSEC.

Develop a connector for Azure ML Web Service

Develop a connector for iFIX SCADA

As we know WITSML is a rather loose standard. A large integrated Oil and Gas Company would like for the WITSML connector to work with Petrolink https://www.petrolink.com/witsml/

Develop a connector for Beckhoff TwinCat

Develop a connector for Mitsubishi Electric MELSEC

It would be very helpful if PI integrated the PI Connector with the Project Haystack tag standard. See www.project-haystack.org for more information.

Project Haystack is an open source initiative to streamline working with data from the Internet of Things. We standardize semantic data models and web services with the goal of making it easier to unlock value from the vast quantity of data being generated by the smart devices that permeate our homes, buildings, factories, and cities. Applications include automation, control, energy, HVAC, lighting, and other environmental systems.

To accomplish a dataflow in a cross domain architecture including a DMZ, and the abbility to avoid the use of a Credential Manager it would be usefull to setup connection between two PI Connector Relays (DZM domain and PIDA domain) based on AMQPS.

When PI System connector is stopped and started (as a service or in UI), duplicate event is received and archived by the target PI Data Archive. The write mode for the PI Connector Relay is append, in this case history recovery will include/send the previous snapshot value. This is critical for many customers, especially pharmaceutical companies.

Develop a connector for AMQP

Develop a connector for Meridium

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

I am interested in a Rockwell CLX Connector.

Develop a connector for OSII EMS