Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on Separating Emissions in Scope 3.1 Accounting Using PyMRIO #153

Open
jbnsn opened this issue Nov 26, 2024 · 0 comments
Open

Question on Separating Emissions in Scope 3.1 Accounting Using PyMRIO #153

jbnsn opened this issue Nov 26, 2024 · 0 comments

Comments

@jbnsn
Copy link

jbnsn commented Nov 26, 2024

Hello Konstantin & everyone,

I have a question about greenhouse gas emission accounting following the Greenhouse Gas Protocol.

It’s common for companies to estimate Scope 3.1/3.2 emissions (Purchased Goods and Services) using average emissions per monetary value of goods which can be done with EE-MRIO databases and PyMRIO. However, according to the Section on Scope 3.1 emissions of the Technical Guidance of the Greenhouse Gas Protocol (p.20):

Emissions from the transportation of purchased products from a tier one (direct) supplier to the reporting company (in vehicles not owned or controlled by the reporting company) are accounted for in category 4 (Upstream transportation and distribution).

My question is: How can I separate these emissions when using PyMRIO? Does PyMRIO have a feature or method to allocate transportation emissions separately, or is there a workaround to achieve this?

In fact, my current understanding is that if the cost of transporting a product from a tier one supplier to the reporting company is included in the invoice for the product, rather than in a separate invoice for the transport service, then these emissions simply cannot be reported separately using the spend-based approach with input-output data.

I hope it's appropriate to ask this question here. Any help is much appreciated.

Best regards,
Jonas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant