As a PI System Administrator, I'd like to be able to trace values being received, and subsequently being sent by the Adapter, similar to PI Interfaces.

Having the ability to trace/log timestamps and values for specific streams would greatly help in troubleshooting data issues, without requiring a network trace or other troubleshooting tools.

As a PI System Administrator, I would like to be able to apply conversion factors to the data that is being gathered from our OPC UA server. This would allow us to get data in the format/units we'd like, without requiring extra tags and/or calculations.

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.

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.

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.

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.

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

As we are using an ISO based tag naming, we would like the PI Adapters to be able to write OPC UA Tag value into Specific tags in DA and not only in automaticaly created tags. Automated DA tag creation should be a possible choice, not the standard.

Provide an option to add the EdgeCmd directory to PATH during the installation process on Windows.

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 be able to recover history on the data streams so that data can be migrated from one system to another.

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

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

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.

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