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
-
Community Data Sharing: Share Data with External Partners
As a company that needs to share data with external business partners, I want to have a way to provide secure access to our company's data through the Cloud SO THAT we can share data with partners that don't have a PI System, without making external copies of the data, and having a more standard way of sharing data with our external partners.
78 votesWe have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
If you have an active use case where you are trying to share data with external business partners of yours and you interested in trying this out once we have reached a point in our development where this is possible, please let us know and we will add you to our list!
-
Ensure Data Segregation for Data Sharing - Multi-tenant System
As a service provider, I need to ensure that our customers can NEVER see another customer's data or even meta-data (that they exist) SO THAT customers can't see any information about their competitors and who we work with.
As a industrial operating company that shares data with partners and service providers, I need to ensure that our data is only accessible to those that we share with SO THAT we can ensure our data and company's intellectual property (IP) is safe and secure.
23 votesWe 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).
-
Conditional Sharing of Data - Contract Manufacturing
As a contract manufacturer (or partner of a CM), I need to only share data with my partner (customer) while I am manufacturing their product on my equipment SO THAT they don't get sent data from another customer.
The Contract Manufacturing equipment is used to produce products from multiple customers so data can only be shared with each partner when their product is being manufactured.
16 votes -
Data Constraints: Limit Amount of History in Data Sharing
Ability to define and constrain the scope of data shared. For example, limit the amount of data history shared with an external partner (ex: week of data, month of data, year of data, etc.). Or a specific time range. There should be no limits on when the time range can exist (i.e. able to share data from 5 years ago).
15 votes -
Share Data by Copying across PI Systems
As a company that shares data with partners, I need to be able to copy data from our PI System to our partner's PI System SO THAT they can leverage the PI System infrastructure they already have in place.
The PI Cloud Connect model that copies data from one PI Server to another PI Server securely through the cloud works great for us today.
Note: This idea is in contrast to Sharing Data by Providing Access: https://feedback.osisoft.com/forums/597811/suggestions/19140958
8 votes -
Share data from AF Hierarchy
As a company that shares our data with partners, I want to define what data to share with partners via our existing AF model SO THAT I can use this existing context to know what we're sharing with Partners.
8 votes -
Handle Unit of Measure (UOM) Conversion Across Companies
As a company that receives data from our partners or customers, I need to be able to convert/transform shared data from my partners into different Units of Measures (UOMs) that our company works with SO THAT we can work in the units we're comfortable with and our analytics and visualizations are built on top of.
7 votesWe have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
We are currently planning on supporting UOM conversions for shared data and in the OCS platform in relation to this work.
-
Ability to Share Event Frames (EF)
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.
6 votes -
Publish data via a REST interface
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
5 votesWe have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
This will include REST API access to data shared in a Community.
-
Publish data to .csv File
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.
5 votes -
Rename / Anonymize Data Shared with Partners
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.
5 votes -
Sharing Data after Batch Completion
Ability to share specific batch manufacturing production data after the batch has been completed (limiting real time data sharing while a batch is in progress).
4 votes -
Data Sharing Transparency Reporting & Auditing
Enable a way to easily identify what data we're sending (sharing) and receiving (consuming from external orgs) to understand where my data is going and who has access to it.
Have ways to audit who has access to our data.
3 votesWe are planning on having a way to easily tell what data you are sharing externally (and what data is being shared with you) in our Community Data Sharing initiative.
-
Share Assets in a Community
Enable Assets to be shared in a Community within OSIsoft Cloud Services (OCS)
3 votes -
Share Data Views with External Partners
Ability to share data view with an external business partner.
3 votes -
Cross Account/Tenant Data Writing Through Community
Ability to write data into another account via Communities (data sharing).
For example, one service provider reads data from their customer, uses models and machine learning to generate results that get written back into the customer's Account.
2 votes -
Public Data Sets Shared
Support public data sets that can be published by organizations and are accessible to all other tenants on the platform.
2 votes -
Transfer Data Ownership Across Tenants
Ability to carve out a data set in one Tenant and transfer ownership of data set to another Tenant.
Examples: plant investments and divestment, connected service customer starts within a namespace within connected service tenant and eventually moves to their own tenant.
2 votes -
cross-tenants data access via API Console
Could we use Client API keys with the API Console to access data from another account/tenant?
2 votes -
Share Asset / Element Relative Displays
Be able to share an asset / element relative display with a partner and have it work on the assets that are shared with them.
2 votes
- Don't see your idea?