1. Knowledge Base
  2. FAQ
  3. ecoinvent and LCA Software Tools

ecoinvent and LCA Software Tools

Sep 27th, 2023

Which Software Tools Integrate the ecoinvent Data?

The ecoinvent database is integrated in all leading LCA software tools as well as many simplified ecodesign tools. 

What is the Difference Between SimaPro or GaBi, Umberto, openLCA, etc. and the ecoinvent Database?

The ecoinvent database is a Life Cycle Inventory (LCI) database. SimaPro, Gabi, Umberto and openLCA are LCA software tools provided by different software providers. The ecoinvent database is implemented in all of the leading software tools. When the whole ecoinvent database is incorporated into a particular software tool, the provider acts as a reseller of the ecoinvent database. Users can acquire licenses and updates of the ecoinvent database through these resellers. These LCA software may also include other databases.

Why is the LCIA Score of a Certain Product not the Same in the ecoinvent Database and in my Software Tool? 

Changes the Characterisation Factors

Impact assessment methods are regularly updated to reflect the newest scientific advances, the inclusion of new mechanisms of cause-and-effect, newer data, etc. ecoinvent uses the results published by method developers to calculate the impacts of the calculated life cycle inventories (LCI). 

The implementation of impact assessment methods is not always straightforward and unambiguous. The method developers often calculate characterisation factors (CFs) with assumptions that are not compatible with the results of LCIs. 

For example, some methods require precise knowledge of the geographical location of an emission factor to select the appropriate CF. 

Other methods ask for information about some properties of the emissions, like water quality. Some methods characterise for example dissipative use of water or materials when this information is not directly present in the LCI. 

Method developers often use different naming conventions than ecoinvent for chemicals, land use, and material extraction elementary exchanges. In most cases, a CAS number can help, but these are not always present, or for some substances like pesticides, commercial names are ambiguous, contain a mix of active substances, and therefore report more than one CAS number. 

Some methods do not carry CFs for a substance in all the sub-compartments present in ecoinvent. For example, should a chemical emission to groundwater receive the same CF as the same emission to surface water, if the groundwater CF is not explicitly mentioned in the method? 

Different actors (method developers, database managers, software developers) might have different opinions about how to resolve ambiguities. 

Finally, plain old human mistakes are bound to happen when managing and aggregating a large quantity of information coming from disparate sources. 

Different Scores in ecoinvent and the LCA Software 

For all these reasons, CFs used by ecoinvent sometimes differ from what is found in software. Ecoinvent is not in a position to impose its implementation choices on the other actors in LCA. The actors in the LCA community are mostly divided by their specialisation: inventory and impact assessment. The implementation of impact assessment methods on the inventory sits uncomfortably at the interface of these two specialisations. There is no regulatory body acting as an authority for this particular task. 

Transparent Implementation

ecoinvent has started taken the following steps in the direction of greater transparency: 

  • Better LCIA implementation documentation. The file section of ecoQuery contains a detailed implementation report, showing the source of the CFs and how they were mapped to the ecoinvent elementary exchanges. These reports are reviewed by independent experts or by the method developer. 
  • Documentation of implementation differences with software. Ecoinvent has started to engage with software developers to minimise those differences. Prior to a release, the implementation is shared to the software and differences are identified. The source of these differences is discussed, and a spreadsheet is available in the file section of ecoQuery for users with a licence.

Where to Find the LCIA Results and Supporting Documents 

All the documentation and supporting files are available in the files section in the ecoQuery accessible to the users of the database who hold a valid ecoinvent license. 

Why are System Models Named Differently in my Software? 

The terminology used by software providers does not always match the one used in the ecoinvent database. 

For example, before the release of version 8.5, SimaPro used different names from ecoinvent. “Allocation cut-off by classification” was named “Allocation, recycled content” (Alloc Rec). “Allocation, default” was renamed “Allocation at the point of substitution” (APOS) in ecoinvent version 3.2., while, SimaPro, until version 8.5, used the old naming abbreviated as Alloc Def. “Substitution, Consequential, Long-Term” is simply called “Consequential” (Conseq). 

In SimaPro version 8.5, the names have been harmonised with ecoinvent.