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

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

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 if PI Adapter for OPC UA received a status other than "Good" for an event, it will not write the data to its endpoint. PI Adapter for OPC UA should be able to write a SYSTEM digital state that indicates the status it received.

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.

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.

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.

In our environment, we plan to deploy PI Adapters on Windows Server class OS. We are in a strict minimum privileges environment hence we only make use of gMSA on all PI services.

We do not want to make use of a domain service account where the password is known (by a few) and can be impersonated. PI Adapters should be enabled to make use of such gMSA type of account to run the service in a secure manner.

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.

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

Adapters are currently only listening on localhost (127.0.0.1) causing them to be only accessible locally. For docker containers, they can only be accessed from within the container or directly on the host (with the --network host switch which results in not containerizing the container's networking) but they cannot be accessed for elsewhere (not able to bind them to 0.0.0.0)
This makes adapter management very difficult in distributed environment.

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.

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.

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.

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