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.

Support an Audit Trail within OCS to ensure data integrity for regulatory compliance (such as pharma 21 CFR Part 11).

As a documentation user I would like to see a last modified timestamp on each documentation topic. This would be helpful to keep track of when changes/ updates were made to individual topics.

A list of tenant aliases that is publicly available would allow publishers of data to more easily add subscribers.

As a PI System Administrator managing our OCS implementation I need to be notified when there is an important change in my PI to OCS software or the connection to OCS that will require me to intervene. I need a notification to tell me about any problems that are occurring. I also need to be able to configure the type of message I get alerts on. I need an alert when data stops transferring, or something critical needs my attention.

Please add support for HTTP/2 so that OSIsoft Cloud Services loads faster.

HTTP/2 check:
https://http2.pro/check?url=https%3A//cloud.osisoft.com/

I think the OMF endpoint should be easier to find. I struggled with this for over half an hour trying to find the URL for my OMF endpoint.

Also, I might be wrong on this, but shouldn't the URL include the https:// as a prefix?

I used the OMF endpoint from OCS by using the "copy to clipboard" button, and pasted in my json configuration file for OSIsoft's Edge Data Store (EDS). The Result: I received an "error: Invalid Endpoint". The solution was to add the https:// in front of the url that I copy from OCS.

When debugging an issue (user related or otherwise) via OCS Portal Log viewer, to aid debugging:
1. new log messages should be viewable as soon as possible (or an indication of the delay) because this speeds up the debugging process,
2. option to automatically refresh view and set/view refresh interval, to see new log entries,
3. retain any log filters entered between refresh,
4. ability to save a 'log view' - including log filters - as default.

Inputs into the portal for start time/ end time should be able to be things like wild card (*) and other common relative time format (maybe PI relative time?)

In order to confidently develop applications on top of OCS, we require different, independent environments to meet the needs of dev / testing / QA, staging, and production.

These environments should typically be isolated as far as configuration, users, security, and data.

There are also needs to promote objects in one environment to the other environments as they progress in the development & testing cycles.

Ability to search and view information from data across namespaces and communities.

I would like to be able to generate meta data for my streams that have extra, unused delimiters in the name

As a user, our company IT has a strategy to move all on-premise application to a PaaS or SaaS application. Therefore,OCS should be compatible to the PI Server and allow the migration of data and feature easily.

Be able to scale to handle use cases such as AMI that have 20 million smart meters x 10 streams (200 million tag equivalent) with 15 min readings.

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 OCS user, I would like to see the notifications sent to include a timestamp so that I can see when the notifications were generated

When a user clicks a shared link to launch OCS, they may get prompted for the tenant ID. Although the information is embedded in the links, it's not obvious to many users. It will be a much friendlier user experience if the tenant ID can be populated automatically.

With the goal of OCS to reach new users, this should include supporting the browser on the increasingly platform of choice for users like Data Scientist.