Support for Alarms & Conditions.  This data type would be good candiate for storing into Event Frames.  Tell us more about your use case in the comments, which source system you have that support A&C, and how you would select which A&C to collect/not collect.  How would you like Event Frames built and named?

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.

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.

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.

As a customer, I need to ensure that the primary instance of the adapter fails over to a secondary instance to minimize data loss.

Create a PI Adapter that supports the MQTT messaging protocol and is capable of writing data to EDS, PI, and OCS.

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      XYZ

The following data should be archived:

(Timestamp) (Value)
11:00:00 ABC
11:00:00 XYZ

Before, one of the main attractions of the Enterprise Agreement (EA) was that you get unlimited access to all standard PI Interfaces and PI Connectors. However, now that PI Adapters are the successors to PI Interfaces and PI Connectors, and since PI Adapters aren't included in the EA, the EA becomes an expensive way to gain unlimited access to dying technologies, and it becomes more cost-effective for customers to instead pay for each (not-dying) product separately.

Please include PI Adapters in either the current version or a new version of the Enterprise Agreement.

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.

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 stamp

This 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

Create a PI Adapter for relational database management systems (RDBMS) to make data available in the PI Server, OCS, and EDS.

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.

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.

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.

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.

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.

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.

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.

Write a PI Adapter that supports the SNMP protocol and is capable of writing data to EDS, PI, and OCS.