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?

As someone who needs to create displays and other 'artifacts' from context, I need to be able to use different names for Attributes depending on the language of the user SO THAT I don't need to build multiple displays for each language.

Be able to handle the storage, context, and retrieval / visualization of spectral data.

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

Provide integration between ESRI ArcGIS Online and OSIsoft Cloud Services.

We are a company providing connected services leveraging operational data to our customers.

Enable us to provision OCS Tenants on behalf of our customers, and manage things like data ingress, stream configuration, data mapping, context, and others for our customer managed accounts SO THAT our customers can just consume our service (and they paid for us to do these types of tasks).

We need a way to onboard our customers easily with their own OCS tenants SO THAT we can expand our business to all our potential customers, not just those that already have a relationship with OSIsoft.

As a data scientist, I need to be able to create calculations from data using R SO THAT I can create analytics using the language I'm familiar with and write the outputs of these analytics back to the data store.

As a Data Steward, I need the ability to share Event Frames with partners SO THAT they can use this context in understanding the data and/or problems.

Ability to create a real time display visual for an Asset or Asset Shape or Streams in OSIsoft Cloud Services (OCS).

Use this idea to tell us about your scenarios for OCS streams with multiple indices (besides just time).

What are your scenarios? How do you need to access the data? How would you like to visualize it? etc.

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

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

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

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.

In addition to building the transfer list via searching a data archive, it would also be good to allow the user to reference a file (e.g. CSV) that has a list of points to transfer.

OCS APIs need to provide better support for viewing data in different time zones / my local timezone. We should be able to encode UTC UTC+13 when making queries to the system.