PI Adapters
Welcome to the PI Adapters feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Adapters. 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.
-
Support Alarms and Conditions
Please provide additional information on how we can support Alarms and Conditions (Alarms and Events). In order to get a better understanding of what is needed on our side, we need plenty of information to help build a comprehensive and informative use case. Please comment with the following of information:
o What is your primary use case for collecting A&C data?
o How do you collect A&C data today?
o How is their A&C data stored in PI?
o What sort of alarm data do you have? I.e. instantaneous alarms, acknowledgements, alarms with a start and stop time?
o What…82 votesThis feedback item has been moved from the PI Connectors forum to the PI Adapters forum.
We are continuing to support the PI Connector for OPC UA with stability and security releases. However, for feature enhancements, we are considering them for the PI Adapter for OPC UA. We would like to hear more about your use cases for this functionality, so please share with us in the comments.
-
PI Adapter for AspenTech IP21
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 Adapter would make perfect sense (since there is already a PI Connector for WonderWare and Honeywell PHD). The PI Adapter shall support both PI and OCS.
19 votes -
PI Adapter for OPC UA should be able to write outputs to the OPC UA Server
The PI Adapter should be able to create a data pipe listener on certain streams (unsolicited reads) that would trigger the writes back to the OPC UA Server.
This is useful when providing set points to the equipment without the need of establishing a second (DA to UA) data flow in parallel.
16 votes -
History Recovery for PI Adapter for OPC UA
As a customer, I need to be able to recover history on the data streams so that data can be migrated from one system to another.
15 votesWe are currently considering the future development of this functionality. Please share your use cases here.
-
PI Adapter for MQTT
Create a PI Adapter that supports the MQTT messaging protocol and is capable of writing data to EDS, PI, and OCS.
14 votesWe have started developing a PI Adapter for MQTT. Look for more updates on our progress in Q1 2021.
-
PI Adapter for Structured Data Files
Create a PI Adapter that supports parsing data from simple file formats (CSV, XML, JSON, plain text) and is capable of writing data to EDS, PI, and OCS.
13 votesWe have started developing a PI Adapter for Structured Data Files. Look for more updates on our progress in Q1 2021.
-
Support Failover for PI Adapters
As a customer, I need to ensure that the primary instance of the adapter fails over to a secondary instance to minimize data loss.
13 votesWe are currently considering the future development of this functionality. Please share your use cases here.
-
PI Adapter for RDBMS
Create a PI Adapter for relational database management systems (RDBMS) to make data available in the PI Server, OCS, and EDS.
9 votesWe have started developing a PI Adapter for RDBMS. Look for more updates on our progress in Q1 2021.
-
9 votes
-
PI Adapters should accept a StreamID longer than 100 characters when writing to PI WebAPI OMF endpoint
Currently a StreamId cannot have more than 100 characters because of a limitation in PI Cloud for this type of object. Nevertheless for PI Cores and PI Data Archive, the PI tag limit of characters is 1024.
PI Adapters when writing to a PI WebAPI OMF endpoint should accept StreamID with more than 100 characters length to take into account a future migration path for customers currently using PI Connectors and working with existing PI tags with long tag names.
8 votes -
PI Adapter for OPC UA should be able to poll data from the OPC UA Server
Currently the PI Adapter for OPC UA only collects unsolicited advised data that is different from the previous value. We would need to see a polling feature to be able to:
- Refresh slow moving streams with updates with the same value but different timestamp
- Get the information in the OPC UA Server at a defined time stampThis polling feature could pave the way to more features like setup the equivalent of "Trigger event tags" offered by the old PI OPC DA Interface technology
8 votes -
Add another Archive Mode option for the PI Interface for UFL
There should be a way to configure the PI UFL interface to both discard duplicate events (same value at the same timestamp) and record multiple unique values for the same timestamp when these events come from multiple data files.
For example, if multiple data files contain the following entries:
(Timestamp) (Value)
11:00:00 ABC
11:00:00 ABC
11:00:00 XYZThe following data should be archived:
(Timestamp) (Value)
11:00:00 ABC
11:00:00 XYZ8 votesThis feedback item has been moved from the PI Interfaces forum to the PI Adapters forum.
We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files. We would like to hear more about your use cases for this functionality, so please share with us in the comments.
-
PI Adapters to support installation on Windows Server 2016 and above
To support the migration path of existing PI Interfaces / PI Connectors to PI Adapters, the installation packages available and SW requirements only has been certified for Windows 10 and Windows 10 IoT. We would require the ability to re-use existing HW in place for collecting data instead of having to deploy new HW with compatible OS that are not server class OS.
7 votes -
View PI Adapter log files via REST calls
We would like to be able to see the adapter log files via REST calls. Going to the machine itself to view is problematic because of remoting into the router and then going into the container to view. I think in a lot of containerized situations a REST call access would be better.
7 votes -
PI Adapter for SNMP
Write a PI Adapter that supports the SNMP protocol and is capable of writing data to EDS, PI, and OCS.
6 votesWe have started developing a PI Adapter for SNMP. Look for more updates on our progress in Q1 2021.
-
PI Adapter for MQTT should include MQTT broker
Having to deal with a MQTT broker between the data source and the PI Adapter adds a single point of failure to the data handling and weakens the data flow end-to-end.
From the data source we can guarantee that the data will reach the MQTT broker, but we cannot guarantee that the PI Adapter will in turn reach the broker.
Goal is to secure the MQTT data collection end-to-end (equipment to PI Data Archive) with reliable SW built, maintained and supported by OSIsoft.5 votes -
PI Adapter for OPC UA should poll a series of items based on a trigger events
Same as the PI Interface for OPC DA feature with "Trigger Tags", the idea is to poll for updates on a series of item streams (tags) only when a certain item stream updates.
The benefit of this is to create timestamp alignments between a series of data points, when a cycle begins or ends for instance. This is very useful for analysis and visualzation of production cycle efficiencies.
5 votes -
PI Interface DNP3 - unsolicited data listen only mode of operation requested
Is there an option in DNP3 driver (In fact at TCP level) to make it listen on a certain (usually 20000 for DNP3)? In era of IoT devices, most devices are sleeping devices, they wake up usually once a day and push data to DNP3 Master (PI), however DNP3 PI collector doesn't support this model. As an enduser I would like to utilize this mode of operation at our plant. FYI, there are other products e.g. Citect SCADA and ClearSCADA use two separate ports for Inbound and outbound DNP3 traffic to use the both modes simultaneously.
4 votesThis item has been moved from the PI Interfaces forum to the PI Adapters forum as we will be focusing on the PI Adapter for DNP3 for future feature enhancements.
We would like to learn more about the different scenarios in which this specific retrieval of unsolicited data is needed. Please continue to share your comments below.
-
PI Adapter for OPC UA Array Support
As a PI System Administrator, I would like for the PI Adapter for OPC UA to support array data types from the OPC UA Server. A large amount of our data may be contained within arrays on our OPC UA Server, so we would not currently be able to collect that data.
3 votes -
PI Adapter for (generic) MQTT to enable auto-discovery of key value pairs using wildcards
When reading from a generic MQTT broker, we currently need to specify explicitly each key value pairs we want to collect inside the data selection json configuration file. This prevents us from really being agile at the time of the initial setup and for each new information we want to collect, as we need to explicitly define the information manually into the Adapter.
We would like the PI Adapter for (generic) MQTT to be able to capture automatically exposed key value pairs in the MQTT broker following a wildcard pattern. For instance take this example payload:
{
"EquipABC.Location": "0020121047111948",
"EquipABC.Status":…2 votesWe are currently considering the future development of this functionality. Please continue to share additional use cases with us.
- Don't see your idea?