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 Data Steward of my company's data, I need to be able to mask the names of data such as attribute names, descriptions, UOMs, etc. before sharing with my partners SO THAT it's not easy for someone else to understand and reverse engineer our process through the data. We want to protect our IP.

Our partner just needs to get the raw values and they need to know the typical range for the attribute but they don't need to know what it means.

The ability to extract data from a bulk set of streams/tags (potentially hundreds) into spreadsheet tools like Excel.

Interpolated data (configurable) over the specified time window.

Drive data sharing from a shared on premises PI Vision display.

For example, selecting to share a display (or set of displays) externally would automatically copy all supporting data to OSIsoft Cloud Services. The display definition and data are automatically moved.

Goal: Replayce the "fax me that display" or "screen shot that display for me".

Ability to share a display with an external person on an ad-hoc basis (display not previously shared).

The access to the display might be temporary (hours, days, week).

As a Systems Integrator, I want to have a way to offer a competitively priced historian as a service to customers we bid projects on SO THAT we have a competitive offering in the marketplace built on OSIsoft technology. Target is for low end of the market (under 5K tags).

As an OSIsoft Partner and Systems Integrator, I want to have a way to build connectors (interfaces) that can write data to Cloud Services for customers that have custom equipment SO THAT we can have more opportunities in the market.

Leverage OSIsoft Message Format (OMF).

I need to be able to be notified when something important happens in the process/assets we are working with SO THAT I can take action on the issue.

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 Community Lead, I need the ability to deactivate and reactivate Community member access into a community SO THAT I can restrict access to only those members that are using the data frequently.

As a service provider, I need to incorporate data into our multi-tenant customer portal (custom) SO THAT we can share data and other information with our customers.

As a company that shares data with our partners, my partners would like the ability to create their own displays from data we share with them SO THAT they can build what they need in a self-service model (and we don't have to build everything for them).

We need to ensure that when our company's data is stored in the cloud, it is stored within Asia (APAC) SO THAT we can comply with local regulations and stay in compliance.

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

As a company that shares data or displays with our partners or customers, I need to be able to convert/transform/project our shared data into different Units of Measures (UOMs) that our partners/customers want to work with SO THAT they can view the data in the units they are comfortable with.

Ability to carve out a data set in one Account and transfer ownership of data set to another Account. For example, during plant investments and divestment.

Have a way to synchronize displays between on premises PI Vision systems and OCS because we don't want to manage two completely different sets of displays.

Provide a way to easily access operational data securely from the cloud without having to jump through lots of login hoops like VPN, Citrix, etc.

Enable white labeling of OCS Visualization so that Connected Services companies can brand the solution to their customers as their own.

As an OCS user, I'd like to populate an Excel like spreadsheet with data stored in OCS so that I can build reports and simple calculations.

Have a namespace concept so that Pi can service multiple tenants without the risk of breaching data security between tenants. Also allowing data from tags associated with a nanesyto be archived and the tags reassigned to another namespace.