AdminLaurent Garrigues
(Sr. Strategic Product Manager, OSIsoft)
My feedback
-
27 votes
We have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
As part of the Community creation workflow, we are working on a way that Communities are formed without exposing other customer accounts/tenants in the process.
Additionally, Namespaces can now be used to segregate customer data (if you’re providing a service to those customers), or the data can be stored in their own OCS tenant/account and then shared via Community data sharing functionality (when it becomes available).
An error occurred while saving the comment -
3 votes
Thank you for the feedback. We are researching how best to achieve the goal of specifying a client id and secret manually during install rather than forcing the user to login to OCS to retrieve the client id and secret.
Please let me know if you have questions, or additional information you wish to share.
Warm regards,
Janelle Minich
Technical Product ManagerAdminLaurent Garrigues
(Sr. Strategic Product Manager, OSIsoft)
shared this idea
·
-
1 vote0 comments · OSIsoft Cloud Services » Development Tools & API · Flag idea as inappropriate… · Admin →AdminLaurent Garrigues
(Sr. Strategic Product Manager, OSIsoft)
shared this idea
·
-
11 votes
An error occurred while saving the comment As an OCS user, I'd like to populate an Excel like spreadsheet with data stored in OCS so that I can build reports and simple calculations.
AdminLaurent Garrigues
(Sr. Strategic Product Manager, OSIsoft)
supported this idea
·
-
2 votesAdminLaurent Garrigues
(Sr. Strategic Product Manager, OSIsoft)
shared this idea
·
Using different namespaces for different customers would provide the best isolation mechanism within a single account. It does limit the possibilities of analyzing data across multiple customers though.