Ability to define a global library of asset templates and assets and then map site data structures into it SO THAT we can standardize easier across sites when the underlying systems and equipment structures are different (and focused more on automation design rather than the use of the data).

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.

The ability to plot the rolling or moving average of trended data SO THAT I can smooth out the data by filtering out the “noise” from raw data making it easier to see longer term trends.

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.

Ability to view OCS data in a spreadsheet like Microsoft Excel or Google Sheets.

Ability to filter on equipment / assets by various metadata (key/value pairs) SO THAT I can find the assets I'm interested in monitoring or performing analysis on.

The ability to configure a peer group of similar equipment based on properties of the equipment SO THAT equipment KPIs can be benchmarked across multiple customers (and data shared anonymously).

For example, a peer group might be all GE7FA gas turbines owned and operated by company xyz.

The ability to see how my units are comparing across the entire group (including assets from other anonymous companies). What's my rank? Am I a good performer or a bad performer?

As a Data Steward of my company's data, I need to be able to publish data to partners that's accessible via a REST interface SO THAT our partner that has good technical resources/capabilities can easily access and make use of the data.

As a Data Steward of my company's data, I need to be able to publish data to a .csv file when shared with our partners SO THAT it's easier for them to consume.

As a Community Lead, I need the ability to configure an expiration date on membership to a community SO THAT contractors automatically lose access after their contract / project is finished.

In these cases, their member account should be deactivated (not deleted). If they want to gain access again, there should be a way for them to contact the Community Leads to reactivate their account.

As a Data Steward, I would like to rename shared data / metadata that is shared with our partners/customers SO THAT the data is meaningful to them or SO THAT I can protect the source of the data.

As a company that shares data with Partners, I need to share (or get access to) to YEARS of historical PI System data with partners SO THAT they can run their analytics on the history and tell us how to improve our operations.

Sharing or getting access to weeks or a couple of month of historical data is not enough for our data sharing use case.

I would like the ability to display my moving assets on a map SO THAT I can see where they have been over historical time.

This idea is to collect customer feedback around Data Ownership Issues. Please let us know your Data Ownership scenarios and needs!

As a customer of OCS, I want the ability to have full control and ownership of my data SO THAT I can assert my rights and have control over data from my farm.

You can zoom in on a portion of the trace, but it doesn’t appear possible to zoom out and return to the starting point. Perhaps this feature will be implemented later? I expect to be able to zoom out again, in part, because this is the behavior I see in other applications. I also want to be able to get back to where I was before I zoomed.

Ability to support URL parameters for data, time, etc. in the OCS Trend page.

Have an OCS Licensing Model for Partners

Ability to add notes to a particular time/cursor on a trend SO THAT when another person is looking at the same data, they can see the comment.

Ability to view the comments other users have entered and view the data associated with them SO THAT the community of users can contribute to the organizations shared knowledge.

Support running OCS and PI Cloud Connect deployed into Azure.gov and ensure that foreign nationals don't have access to the data or cloud servers (from a support/maintenance perspective).

Some customers need to store (retain) some, but not all, data for extended periods of time. For example, there can be a need to store any data used in regulatory reports for 5-7 years. Going forward, could OCS be an option for collecting/aggregating/storing these data?