The atma.io connected product cloud from Avery Dennison utilizes this policy to calculate scope 3 emissions during the RFID Inlay production processes. The policy is fully integrated into the atma.io platform and is designed for API-driven usage.
MRV data from the production process is received by the policy, which also tracks waiver batches. Once the Scope 2 emissions have been calculated, this subsequent policy should be triggered. The Scope 2 emissions that need to be passed on a UoA (Unit of Analysis) level to this policy can either be retrieved from a dedicated Scope 2 policy or calculated via a different process, depending on the use case.
Currently the following roles exist within the policy:
Organization: The organization that is tracking carbon emissions during the inlay production process is referred to as the Organization
Policy Setup
Information about the product and production process must be recorded within the policy before production data can be captured. This is similar to the Scope 2 policy, where production-related information is first added when setting up the scope 2 policies. The current iteration of the policy is limited to tracking the emissions of only one product. If multiple products need to be tracked, additional policy instances must be created.
The following information is required when setting up a policy:
Organization Information: Information about the organization and the company's governance structure, such as business entities.
Definition of GHG sources: Captures information about the GHG sources, such as Ground transport and Supplier PCF Data.
Product information: Information about the product and its production process, such as quantity information and used materials.
Policy Workflow and Usage
During the production process, MRV data is sent to the initialized policy on a 'per batch' level. Based on this provided information and emissions from scope 2 (on a per unit of analysis level), a partial scope 3 emission is calculated. Additionally, an emission token is minted, representing the carbon emissions on a per batch level.
The included Postman collection utilizes the Guardian REST API to set up the policy and initialize and populate it with example data. Before the policy can be used, the collection level variables for fields such as guardian instance URL and credentials must be set.
The referenced data in this section reflects industry standards and needs to be adopted by policy users to reflect real-world values or changed to matching industry standard values.
The actual out of our policy is the scope 3 emission - Cradle to Gate - for an individual item of the batch, listed in "gco2ePerUoaCradleToGate" and represents roughly 0.978 grams CO2-eq.
The output for the full batch of all produced inlays is available in"co2ePerCumulativeOutput" and represents roughly 3,910,698 grams CO2-eq.
Subsequently, we use the output of the carbon emission policy to store PACT Pathfinder 1 compliant records in our system, following the 2.0.1-20230314 specification 2.
One such sample is outlined below and includes the required data points from our policy output.
