OSIsoft Cloud Services
Welcome to the OSIsoft Cloud Services feedback page!
We created this forum to hear your ideas, feature suggestions and feedback around our cloud offerings. For more information on OSIsoft Cloud Services, please refer to: https://cloud.osisoft.com/
Please note that your ideas and comments posted here are visible to all other users.
- For PI Cloud Connect, please enter your ideas here: https://feedback.osisoft.com/forums/598033-pi-cloud-connect
-
Segregate Data from Different Customers within a Namespace
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.
6 votes -
Spectral Data
Be able to handle the storage, context, and retrieval / visualization of spectral data.
6 votes -
Support different data retention via OCS
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?
3 votes -
Batch Tracking Data Storage & Visualization
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.
2 votes -
Easier Experience for Editing Stream Types
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.
1 vote -
Edit Unit of Measure (UOMs)
Within OCS, make it easier to edit the unit of measure (UOM) for streams.
1 vote -
create new units of measure
UoM of source data or required representation not supported.
1 vote -
GeoJSON
As a remote operations monitoring user, I would like to store locations and track movements of assets in a native GeoJSON data type / format for both querying as part of OCS and integration with peer cloud services that take advantage of geospatial positioning data.
1 vote -
Video Storage
The ability to store video files in OCS and relate the video to process data by timestamp.
1 vote -
Large data set of real data for testing - PMU Data from LBNL
As someone who collaborates on PMU Data or wants to do Wide Area Surveillance would it be possible to load and test data from LBNL PMU Data set. This will allow researchers to create sample solutions on top of OCS. In this area. More informtona and the data set can be found here: http://powerdata.lbl.gov/
1 vote -
Local Data Historian for embedding in Partner Applications
As a Partner that wants to focus on application logic instead of writing a database, I often receive manual data inputs, results of time-series calculations, and create predictive data sets that require persistence SO THAT our application can receive and publish data from OSIsoft and other sources without the overhead of managing a full stack of software.
Ideally this local historian would seamlessly integrate with our application without having to directly embed it (so upgrades are easy) - while also having a high affinity to Data Sharing behaviors in OSIsoft's Cloud Services (thus making it near zero configuration).
Some of…
1 vote -
Local Data Historian for Data Science
As a Data Scientist or Data Steward, I would like a local, zero configuration, in-memory ordered, columnar data storage instance that can take a subset of data from a Cloud Services Data Sharing Publication and persist it for local computing resource tasks SO THAT repetitive updates and changes to my data queries perform well, and also, give me a safe space to test several scenarios prior to publishing data back to Cloud Services.
1 vote
- Don't see your idea?