As a company that provides services for remote assets at our customers sites, we need to collect data from our customer sites without having to deploy a full PI System SO THAT we can start providing our service weeks to months faster and save on deployment and infrastructure costs.  

Ideally, we could deploy some PI Connectors to remote sites and store the data in a Cloud Data Store.

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.

Allow users more flexibility and options when finding and selecting PI tags to transfer to OCS. Current implementation only allows a single PI tag name search criteria, and limits one transfer between each PI Data Archive and OCS namespace.

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.

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".

There seems to be a dependency on IE, when installing the PI to OCS agent. This wasn't there in earlier versions. I kept getting Flash error during DUO authentication. I had FF and Chrome installed, and Flash was disabled. I ended up having to install IE, then disable Flash in IE, before I could get past the DUO error

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.