As a Data Steward of my company's data, I need to be able to publish data to a table 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.

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.

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 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 company that shares data with partners, we need to share data temporarily (has an expiration) SO THAT my partner can see the data they need right now when they need it but they don't have access to it for ever.

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

As a process engineer, I need the ability to view data in unit of measure's that I'm used to SO THAT the values make sense to me when I'm viewing and analyzing displays.

As a service provider, I need the ability to view data in the time zone of where the asset/customer are located or the time zone I'm located in SO THAT we can work in the right time context and collaborate easier with our customers.

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 embed / integrate the OCS trend into our own visualization app so that we can leverage OSIsoft's trend without having to build and maintain our own.

PI to OCS creates an OCS stream type for PI digital tags with a property called DigitalStateName. This property includes both the "real" value of the tag's digital state set, but also the System Digital State (No Data, Error, Comm Fail, etc) when the Value property is null. It's difficult to distinguish what strings correspond to values and what strings correspond to errors.

Ability to write data into another account via Communities (data sharing).

For example, one service provider reads data from their customer, uses models and machine learning to generate results that get written back into the customer's Account.

Support for Active Directory (AD) Groups when adding users to a Community.

Support for Active Directory (AD) Groups when managing users within OCS.

Integration between OCS and Snowflake (a common cloud SaaS data lake solution).

Authentication support for Okta

https://www.okta.com/

Ability to share specific batch manufacturing production data after the batch has been completed (limiting real time data sharing while a batch is in progress).