Provide integration between ESRI ArcGIS Online and OSIsoft Cloud Services.

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 is up.

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

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

Have an OCS Licensing Model for Partners

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.

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

Ability to perform hourly, daily, weekly monthly, quarterly aggregation summary calculations on data.

Often useful for utility consumption KPIs / metrics.

Integration with Power BI

Support the ability to handle connectivity models that map out relationships between assets/elements and associate different assets together based on their relationships.

The ability to push Machine Learning models trained from data in the cloud environment back down to remote assets / Edge systems.

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 to stop sharing data with a partner/vendor/service provider that is providing services to me but we decide to terminate the relationship (perhaps choose a different service provider).

In this situation, we would like to still retain access to the history of the community because you might need to determine what the vendor was doing with your equipment back in history.

NOTE: Please use the comments section for this idea to help document your requirements and use cases when a sharing relationship or contract is terminated.

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.

Deploy OCS in Asia Pacific (APAC).

We need to make sure the servers that our data resides on is located within Asia.

As a company that receives data from our partners or customers, I need to be able to convert/transform shared data from my partners into different Units of Measures (UOMs) that our company works with SO THAT we can work in the units we're comfortable with and our analytics and visualizations are built on top of.

Deploy OCS in Norway

We need to make sure the servers that our data resides on is located within Norway.

Ability to visualize recent faults for an Asset.

Ability to search for Assets by their metadata (key/value pairs). For example, search for "Philadelphia Pumps"