Skip to main content

Diverse Data Sharing

Overview​

This scenario addressed what it looks like when supply chain actors want to have different degrees of disclosure in their RBTP credentials. Participants reviewed how supply chain actors could share different levels of disclosure:

  • Public Digital Product Passport with limited disclosure
  • Digital Product Passport with selective sharing of additional information with recipients of an encryption key, but which still does not share linked digital credentials of the sender's upstream supply chain

Scenario Version:

  • Midstream supply chain actor willing to share limited information in public Digital Product Passport but willing to share more data with a direct customer

Scenario Value Chain Outline​

The value chain map below illustrates an example of how selective sharing of data works and be represented to different supply chain actors. The public-facing version of the Digital Product Passport can be accessed by clicking the "DPP:CAM" under the Universal Location PC. The QR code with a lock is the encrypted DPP as accessed by a user without the key while the QR code with an unlocked icon is the encrypted DPP as accessed by a user who has been given the key.

Credential List​

Credential TypeCredentials
DPP (Product Passport)Public - High-Nickel NMC 811 Cathode Active Material
Encrypted/Private - High-Nickel NMC 811 Cathode Active Material

Lessons Learned/Conclusions from Roundtable​

  • Validated core items for RBTP proof of concept:
    • Flexibility for different degrees of information disclosure
    • Organizations can successfully disclose different data/enable different levels of disclosure in data credentials for the same facility or product (e.g. a "public" version of a Digital Product Passport versus encrypted version with more data disclosed to intended recipient)
  • Use of RBTP itself as a way to store and send data does not require a specific level of disclosure, and downstream companies may still communicate preferences on what data they want suppliers to share while using the RBTP data format
    • Companies would need a supplement to the Protocol to communicate preferred data fields for sharing; the RBTP itself will not require a specific level of disclosure
  • When a supply chain actor does not share digital credentials for its upstream supply chain, pilot participants found that a combination of third-party attestation and technical proofs could be used to provide confidence in claims made to a customer without requiring the supplier to disclose its own suppliers in turn
  • Regardless of transparency protocol or solution used, it is important for customer/downstream data requests to be reasonable and made in view of operational realities for different supply chain operators