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.

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?

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

Have a mechanism to subscribe to data change updates on the platform so applications don't need to constantly poll for changes.

Ability to store images as time bound data into OCS, and retrieve the images for viewing or modeling/analysis.

Example scenario: a thermal camera takes a picture of a furnace and the image is used to extract data and performance KPIs about the furnace (stored back into OCS).

The ability to define custom units of measure (UOMs) within OCS.

Within OCS, make it easier to edit the unit of measure (UOM) for streams.

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.

Previously added UOMs September 2021: https://feedback.osisoft.com/forums/597811/suggestions/40119379

Currently, the OCS portal only exposes Stream Names when creating Metadata Rules, but the API exposes the Stream ID as well. It would be beneficial to create a Metadata Rule based on the Stream ID from the portal.

Stream IDs are often more formulaic than names, and therefore can be better suited for parsing out data. PI to OCS streams are a common use case where the Stream ID contains useful metadata (data archive name, point ID) not found in the Stream Name.

Ability to define Units of Measure on a Field in an SDS Type using the OCS Portal UI. Currently, the field type, name, and description can be edited, and fields can be marked as indexed. It is not possible in the UI to add UOM to a Field.

Stream Types are not editable in OCS SDS by design but it's painful to have to recreate a new type and do your work all over again when you need to make a change or forgot something.

Please capture related scenarios you have around making changes to Stream Types here.

Ability to capture Batch Tracking data into OCS and visualize it.

The data could be coming from an existing PI System with using Event Frames.

Users have pumps that have statuses of ON and OFF. Currently, they map to Good and OFF to Warning. However, pumps being off isn't really a warning sign to them, but only a normal condition.

When on the Manage Data page for a stream I would like an on screen option to refresh the last value/first value/ range. This is because I want to be able to see if a new value came in for easy troubleshooting purposes. Currently you either need reload the whole page, or change the data call and apply it and then change it back and apply it again.

As an admin using SDS Explorer, I want to hide the columns like ID or type because I don't care about these and I want to see the entire stream name which is impossible even if I make other columns as small as possible.

The PI Data Archive allows for the setting of Display Digits so that clients such as System Management Tools only renders a certain number of decimal places, regardless of how many are actually stored in the archives. We would like to this functionality to be added to OCS streams, and for the portal to abide by it when rendering recorded values.

As a user I would like to be create and edit OCS streams in bulk. I would like something similar to AFBuilder but for OCS.

It would be beneficial to be able to export a list of streams in csv format (including columns such as stream name, stream id, type id) from the portal's SDS explorer, particularly after a search query has been executed so only a small subset of the streams would be included in the export. This csv file could then be used in other applications for easy stream name to stream id reference, or to simply document a list of streams to apply to certain search criteria.

I am creating a large type (10+ properties), but am not sure exactly how I want the type to look. I would like to be able to easily in the portal duplicate an existing type and then make edits to it and save it as a new type, rather than having to type in and reselect each property selection. This would allow me to test my data in different organizational patterns to see what is best for my needs.

I am creating a large type (10+ properties), but am not sure exactly how I want the type to look. I would like to be able to easily in the portal duplicate an existing type and then make edits to it and save it as a new type, rather than having to type in and reselect each property selection. This would allow me to test my data in different organizational patterns to see what is best for my needs.