A reproducible openLCA workflow

• openLCA version
• active database
• product system
• functional basis or reference amount
• impact method
• important parameters or scenario settings

Do this before the first result, not after two runs disagree.

Use IDs returned by openLCA or the client library instead of relying only on display names. Names can be duplicated or change between databases.

Before scenario or uncertainty work, confirm that the baseline model calculates, inspect its result, check basic inventory and contribution behavior, and save the baseline assumptions.

When the interface provides a live result handle, use it for impacts, inventory, contribution analysis, trees, and exports. This reduces the chance that the model changes between analysis steps.

• what changed
• old value
• new value
• units
• why it changed

A label such as “high efficiency” is not enough to reproduce a scenario.

A model output is not plant performance or experimental data. Label modeled values clearly, especially in reports and comparisons.

• model or database identity
• impact method
• functional basis
• parameters
• package or source version
• exported result
• interpretation notes

Dispose or close live result objects when the analysis is finished. The saved study record should remain useful after the software session ends.