0 votes

This is a similar question to the one posed as "Why do I get negative results in all impact categories?", however it deals with the LCA Commons database from USDA.

Are you aware of issues using the "Auto-link processes" function with NREL data? 

As an example, I created a simple product system with 1 input (1MJ of Electricity, anthracite coal, at power plant - RNA). If I auto-link the processes when generating the product system, many impact assessment categories have negative values. 

Any tips would be great. Thanks!

in openLCA by (140 points)
by (140 points)
edited by
In digging deeper into the auto-linking, the issues seems to be with the Process: "Crude oil, extracted - RNA"; once its supply chain is removed, the emissions are positive.

When the supply chain for the process is manually added, the issue occurs with the process: Residual Fuel Oil, combusted in industrial boiler - RNA

2 Answers

0 votes
by (1.6k points)
Make sure you are using the latest version of the US LCI. I believe this issue has been resolved.

by (140 points)
I’m using the most recent version provided by GreenDelta (paid for this).
0 votes
by (170 points)

@byoung is correct; this issue was resolved with the corrections released as of the USLCI 2020 (Summer Quarter) version. 

The Nexus paid-for version does not reflect this correction. If you use the latest version of USLCI from the Federal LCA Commons, you will also need methods adapted to the Federal Elementary Flow List (FEDEFL), to which the USLCI converted in 2019. The FEDEFL and the FEDEFL-adapted methods are available on the Federal LCA Commons for download and import, e.g., into your openLCA desktop application. Please see the USLCI GitHub Support Content (https://github.com/uslci-admin/uslci-content/wiki) and/or the NREL USLCI Quick Help YouTube video series (https://www.youtube.com/playlist?list=PLmIn8Hncs7bFUOyXZNGXwG4LtdoTfLz6Q) for details on USLCI Database versioning, using FEDEFL-adapted methods, and running calculations on USLCI in openLCA.

Alternatively, you can manually implement relevant corrections from the USLCI Change Log into the Nexus paid-for verison: https://github.com/uslci-admin/uslci-content/blob/dev/docs/release_info/change-log.md.

by (64.1k points)
Thank you Rebe - it is a bit embarassing for us of course and we should try to get the versions faster on Nexus!