As a company that needs to share data with external business partners, I want to have a way to provide secure access to our company's data through the Cloud SO THAT we can share data with partners that don't have a PI System, without making external copies of the data, and having a more standard way of sharing data with our external partners.

As a customer that has assets in locations that have few personnel that are capable of maintaining software on site, but need to create displays, reports, and troubleshoot operational issues using data from several different small automation systems. I need a low to zero footprint offering that is always up-to-date offered on a subscription basis so that I can enable visualization and analytical capabilities on my remote sites.

Ability to share a display of information (real-time & historical) with an external partner/company.

Must support ability to secure and share specific displays with specific partners.

It must be possible to share the display with an external partner that doesn't already have a PI System.

The ability to collect data directly into OCS (Cloud) but then route some data back to on premises PI Systems for merging with that data.

As a service provider, I need to ensure that our customers can NEVER see another customer's data or even meta-data (that they exist) SO THAT customers can't see any information about their competitors and who we work with.

As a industrial operating company that shares data with partners and service providers, I need to ensure that our data is only accessible to those that we share with SO THAT we can ensure our data and company's intellectual property (IP) is safe and secure.

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

I need to be able to have OSIsoft's cloud services solution be deployed into private clouds that the customer controls SO THAT the infrastructure and security for the application is managed by the customer (and their providers).

Ability to configure calculations based on OCS data and store the values back into OCS as new Streams.

Ability to display sites & assets on a map, show their current status, and then have a way to drill down into details for them.

Deploy OCS in Australia

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

Ability to click on an Asset and view the current values for data & metadata associated with the Asset.

Ability to define and constrain the scope of data shared. For example, limit the amount of data history shared with an external partner (ex: week of data, month of data, year of data, etc.). Or a specific time range. There should be no limits on when the time range can exist (i.e. able to share data from 5 years ago).

As a contract manufacturer (or partner of a CM), I need to only share data with my partner (customer) while I am manufacturing their product on my equipment SO THAT they don't get sent data from another customer.

The Contract Manufacturing equipment is used to produce products from multiple customers so data can only be shared with each partner when their product is being manufactured.

As an company that uses PI Systems across our enterprise, we need the ability to aggregate data across on premises PI Systems located at our sites.

Today, we often use another "Enterprise" level PI Server to perform this aggregation and 'corporate view'. but in the future, we would like to be able to aggregate this data in a cloud based Software as a Service (SaaS) offering hosted by OSIsoft.

This would enable customers to largely replace their central/corporate PI Servers with OSIsoft Cloud Services (OCS).

Ability to restrict user access to an Tenant's Users and namespaces within a Tenant so that certain users/roles don't know other users in the tenant.

Used for scenarios when a Tenant is storing multiple customer's access within the same Tenant prior to Community Data Sharing services being available.

If OCS is missing units of measure that you use and need for your data, please vote for this idea AND add a comment to this idea specifying what the missing UOMs are.

Enable a way for external organizations that are partners that are sharing data and displays to also communicate & collaborate with each other in the context of their sharing community SO THAT everyone in the community can leverage the expertise of the community members and work together to meet their collective business objectives.

Support a chat/message board to enable collaboration and sharing of ideas within a 'community space'.

Ability to segregate and view information (Data Ingress, Streams, Assets, etc.) from multiple customers/clients within a Namespace SO THAT it's very clear what data and system artifacts are related to each customer and SO THAT information doesn't accidentally get mixed up and exposed to the wrong customer.

Ability to manage security from ingress to egress via the same mechanism.