As a company that shares data with external partners, I would prefer to provide secure access to our data through the Cloud SO THAT we can share our data without making a bunch of copies of it all over the place and have a more standard way of sharing data to external partners.

NOTE: This idea is in contrast to Sharing Data by Copying across PI Systems: https://feedback.osisoft.com/forums/597811/suggestions/19110427

Provide a way for partners, vendors, or customers that don’t have a PI System to securely access a subset of our operations data SO THAT we have a more standard and secure way of data exchange than today (VPN, Email, FTP, Citrix, PI to PI, PI CC, etc.).

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.

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

Ability to define 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).

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.

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.

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.

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.

As a company that shares data with Partners, I need to share (or get access to) to YEARS of historical PI System data with partners SO THAT they can run their analytics on the history and tell us how to improve our operations.

Sharing or getting access to weeks or a couple of month of historical data is not enough for our data sharing use case.

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.

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.

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.

As a Data Steward of my company's data, I need to be able to publish data to a table when shared with our partners SO THAT it's easier for them to consume.

As a Data Steward of my company's data, I need to be able to mask the names of data such as attribute names, descriptions, UOMs, etc. before sharing with my partners SO THAT it's not easy for someone else to understand and reverse engineer our process through the data. We want to protect our IP.

Our partner just needs to get the raw values and they need to know the typical range for the attribute but they don't need to know what it means.

As a company that shares data with partners, we need to share data temporarily (has an expiration) SO THAT my partner can see the data they need right now when they need it but they don't have access to it for ever.

As a company that shares data or displays with our partners or customers, I need to be able to convert/transform/project our shared data into different Units of Measures (UOMs) that our partners/customers want to work with SO THAT they can view the data in the units they are comfortable with.

Instead of having to setup an API on a server in our SCADA environment, get the data offered in OCS from PJM or MISO and then get it into our PI System for analytics and analysis.

Ability to have support for the ASTM E3077 standard for exchanging raw material eData for Pharma & BioPharma manufacturers.

https://www.astm.org/Standards/E3077.htm

As a company that shares data with partners, we need to share data for specified time periods only SO THAT my partner can see the data they require but not more.