Sometimes, the PI2OCS agent seems to have some interruption in replicating data from a PI Data Archive into OCS. It would be beneficial to have some more monitoring options (in addition to what is available through the OCS portal) either by supporting performance counters in the Agent software or having some statistics available through the REST API. Either receiving a notification when data is not current anymore would be a great accomplishment. Connection stability is crucial for using OCS within a production environment.

As a PI System Administrator, I would like a way to deploy PItoOCS in a secure and manageable way so that it is easy to maintain, and I can trust it is secure.

Currently, OSIsoft recommends PItoOCS be installed on a separate computer from the Data Archive to which it connects. PItoOCS only supports a single connection to a single Data Archive in the current version.

OSIsoft Product Management would like to better understand customer requirements about deployment of PItoOCS in their environment.

As a PI to OCS Administrator, I would like to be able to modify a PI to OCS Transfer after it is created. I may need to add data to the transfer - because we added new data sources, or because I may have missed some data that needs to be included. This is important so I don't have to delete the existing transfer and then rebuild it with the modified list of PI Points.

PI to OCS creates an OCS stream type for PI digital tags with a property called DigitalStateName. This property includes both the "real" value of the tag's digital state set, but also the System Digital State (No Data, Error, Comm Fail, etc) when the Value property is null. It's difficult to distinguish what strings correspond to values and what strings correspond to errors.

Enable a more seamless upgrade experience for the PI to OCS Agent, the on-premises component required to transfer data to OCS.

Send soft sensor and IOT device data straight to the cloud bypassing traditional automation and plant floor networks.

Provide built in dashboarding for the data in the cloud.

Ability to see how stale data is. Do I expect to see data but it hasn't been updated in a long while?

I have a customer that I would like to collect data from. I would like to allow them to run PI to OCS to send their on-prem data to my OCS tenant. They are not part of our user database, and I do not want to grant that customer "Admin" level access to my entire tenant. Rather, I want to be able to allow this particular PI to OCS Agent write access to my tenant.

The ability for data generating devices in the field to be redeployed to new assets and have the data in OCS reflect this reality.

Scenarios:
* Device 123 is capturing data from Asset A and redeployed to Asset B at this timestamp.

* Device 456 is capturing data from Asset A and is replaced with Device 789 at this timestamp for Asset A.

When looking at data for Asset A, it should reflect the history of all the data from the various devices.

As a OMF developer, I would like a way to easily check if my OMF message succeeded and the message was processed and there were no errors. I would like to do this from my sending application. One possible way would be to send in the returned operation-id of a call to get its status(using same auth header).

Provide a way to upload spreadsheet data to OCS. This is manually entered information, compiled manually from multiple sources.

I think the "Add Connection" button should prompt the user if they want to create a "OMF Type" or a "PI System" type connection.

This was confusing for me, since I didn't realize that the "Add Connection" button functionality is DIFFERENT based on weather I have the TYPE set to "OMF" vs "PI SYSTEM".

Ability to integrate data from eWON Cloud IoT platform into OCS

As an admin, I need to install and configure a Connector or application that collects, buffers, and transmits data to OSIsoft Cloud Services so that I can start making displays that help me monitor my process.