Skip to main content

DIV – Product Carbon Footprint (PCF) Use Case

Last updated on by rameshvaranganti

Tracking the carbon footprint of a product across complex supply chains requires multiple companies to exchange emissions data — a process that demands both data integrity and verified identity. SAP Decentralized Identity Verification (DIV) enables this by providing a Self-Sovereign Identity (SSI) infrastructure where supply chain partners can prove their identity and their membership in a trust network using Verifiable Credentials (VCs), without relying on a central authority.

This reference architecture illustrates how a Gearbox Supplier and a Car Manufacturer use the Bring Your Own Wallet (BYOW) provisioning model to each operate their own DIV instance on SAP BTP, and then exchange Product Carbon Footprint (PCF) data securely. In the BYOW model, each company self-provisions their DIV wallet independently — the Operator (e.g., Cofinity-X) retains its role as the trusted issuer of the membership credential, but the wallet infrastructure is owned and operated by each member.

Architecture​

image of solution diagram
Copy to clipboard
Solution Diagram Resources
You can download the Solution Diagram as a .drawio file for offline use. Alternatively, you may view and edit the Solution Diagram directly on draw.io.
Please note that any changes made online will need to be saved locally if you wish to keep them.
DownloadEdit

The architecture involves three parties, each owning their own wallet infrastructure:

  • Operator — the dataspace operator (e.g., Cofinity-X) who verifies member identities and issues membership credentials to the members' own wallets.
  • Gearbox Supplier — a tier-1 supplier who has provisioned their own DIV wallet on SAP BTP. The wallet holds the membership VC issued by the Operator and a company DID anchored on the DID network.
  • Car Manufacturer — an OEM who has provisioned their own DIV wallet on SAP BTP. The wallet holds the membership VC issued by the Operator and a company DID anchored on the DID network.

DIV's Agent on each side communicates using the IATP (Interoperability and Trust Protocol) to exchange and verify membership credentials before PCF data is transferred via the Eclipse Dataspace Connector (EDC).

Implementing the Data Exchange with Data Space Integration​

Identity verification and data-transfer governance are separate responsibilities. When using SAP Integration Suite's Data Space Integration capability for the exchange:

  1. Check the service plan, enable the required capabilities, and complete connector onboarding for the selected data space.
  2. Assign provider and consumer roles and configure backend connectivity and security material.
  3. As a provider, define the asset and its access/usage policies, then bundle them into a contract definition.
  4. As a consumer, discover an offered asset, review the applicable policies, and establish the agreement before transfer.
  5. Monitor agreements and transfers, and test changes to credentials, policies, and connector configuration.

See Data Space Integration setup, provider design, and agreement monitoring. Validate the connector and identity requirements of the chosen data space; wallet verification alone does not grant access to every asset.

Services and Components​

Resources​