This feature is only available in the Corporate plan.
The generator feature gives you an effortless way to create and update product specific LCAs at scale with your existing bill-of-material (BOM) data. Map your BOM items to existing cycles and datasets to automatically generate LCA models.
This feature supports uploading data from any source that can be converted into a spreadsheet table (CSV or XLSX), enabling flexible and efficient LCA creation.
Create and manage product LCAs at scale
Each ERP system exports their own style of bill-of-material data and column names may vary. Earthster recognises the most common naming conventions to allow you to use your BOM almost as is.
For modelling more complex products with the generator you can use additional data columns. For example you can specify the functional unit and create a nested structure.
Example of a simple generator file
Cycle name | Component | Amount | Unit | Geography |
Basic Lego box | BLOCK - 1x1 - red | 10 | unit | Europe |
Basic Lego box | BLOCK - 1x1 - yellow | 15 | unit | Europe |
Basic Lego box | plastic film | 20 | g | Europe |
Recognised column headers
*Mandatory field
Column header | Recognised synonyms | Field description |
Cycle* | SKU | The name of the cycle that will be created or updated. |
Component* | Process | List of inputs for the cycle. |
Amount* | Value | Numeric value representing the amount of the specific input. |
Unit* | Units | Unit of the of the specific input. |
Geography* | Location | Needed for differentiating between different production locations. For example dataset geographies. |
Scale |
| Sets the functional unit of the cycle. Can include multiple units separated by commas. |
Depth | Tree | Creates a nested structure, commonly used in BOMS. Level 2 inputs will be included under level 1 in a consecutive order. |
Query |
| Allows you to specify a different search term then what appears in the component fields. |
Other header names |
| Any other columns will be added as a description of the input.
|
Mapping your BOM items to datasets and cycles
To be able to efficiently generate LCA models at scale you need to translate your BOM language into LCA language. You can do this by mapping any of your BOM items to existing cycles and datasets.
The system remembers the mapped items and are available for the whole organization, regardless of the workspace. So you only need to do it once.
Creating mappings
Export your BOM data and make sure it includes the mandatory headers.
Accepted formats:
CSV
XLSX (first sheet only)
Navigate the to the workspace where you want to create your new models.
From the workspace dropdown menu click "Generate cycles from file".
The system gives you an overview of the planned actions and shows a red warning if there are any items requires mapping.
Go to the Mappings section and check each suggested mapping for your BOM items:
Click the checkmark to accept a suggestion.
Click the sideways arrows to search for another dataset or own cycle.
You need to finalise any pending mapping included in your generator file to be able to generate new cycles with your file.
Editing and removing an existing mapping
Open the Mappings section
The section can be accessed in any workspace
Click on an row that you would like to edit or delete.
Click the sideways arrows to search for another dataset or own cycle.
Click the "x" icon to remove the item from you mapping list.
Click the checkmark to accept a suggestion.
Creating and updating cycles with the generator
Export your BOM data and make sure it includes the mandatory headers.
Accepted formats:
CSV
XLSX (first sheet only)
Navigate the to the workspace where you want to create your new cycles.
From the workspace dropdown menu click "Generate cycles from file".
The system gives you an overview of the planned actions. Follow the above instructions if you have pending mappings.
Click Execute plan button if you want to proceed.
Click the "x" on the top right corner if you do not want to proceed.
Once the plan is executed you will get a success message.
Note: You can navigate away from the screen while the system is executing the plan. It will not stop the process.