The Replicator feature gives you an effortless way of to do LCAs at scale. With the replicate feature you can create hundreds of variations of your products in minutes and you can update them in batch with a CSV or XLSX file.
You can use this feature to upload data from any other source that can be converted into a spreadsheet table. You can even import data from your bill of materials (BOM).
To get started, all you need to do is to create a "template" cycle that you want to replicate with variations, in other words create copies with different values. Use hashtags to define the inputs with variations.
As an example we are going to use different coffee recipes.
1. Create a template cycle
Create a new or chose an existing cycle to serve as the template for your replicas.
Add a hashtag to the description of the input that you want to be able to update.
Example: Add the #espresso tag into the coffee process input
The hashtag can be added anywhere in the description field
Parameter identifiers are automatically classified as updatable field
2. Download the pre-filled upload file (Template)
Once your template cycle is ready you can download your pre-filled upload file as a .csv or .xlsx file. The file will include any hashtags and parameter identifiers present in your cycle.
Open the cycle you want to replicate
Open the cycle settings
Click the dropdown menu of "Replicate in bulk" button
Click on the file type you prefer to use int he replication process
This same file can be used to replicate in bulk to create new cycles and update in batch to update the values of your existing cycles.
3. Add data to your template file
Populate your template file with your own data or add the headers into an existing spreadsheet file (e.g. BOM, datasheet...).
Each row represents a cycle that will be created when replicating or updated if the matching cycle name already exist within the worksapce.
Add a row per each replica (a copy of the template cycle you want to create)
Use the first row for defining your columns
Add a column for each tag or parameter identifier (input value)
Mandatory column title:
nameOne of the columns must be titled
name: This contains the name of the cycles.The column order doesn't matter.
Columns with non-matching identifiers will be ignored
Add as many columns with the identifier hashtags and parameters as needed
Example of the upload file of the coffee recipes:
name | #espresso | #milk | #frothed_milk | @coffee_bean |
Espresso | 1 | 0 | 0 | arabica |
Steamed Milk | 0 | 0 | 100 |
|
Caffe Latte | 1 | 0 | 240 | robusta |
Macchiato | 1 | 0 | 30 | arabica |
Cappuccino | 1 | 60 | 60 | arabica |
Note: The system only updates the input values that has a matching hashtag in the description field or a matching parameter identifier within the cycle and ignores any other data.
When replicating a cycle:
The example table creates 5 new cycles and updates 4 inputs in each.
When updating in batch:
The example table updates the 4 inputs in any cycle that is matching the name in the workspace.
4. Replicate in bulk
Replicating a cycle will create new copies of the cycle based on the specifications in your upload file. The new cycles are independent of each other and their original template cycle.
Open the cycle you want to replicate
Open the cycle Settings
Click the Replicate in bulk button
Upload your .csv or .xlsx file by either dragging or searching your file.
The system gives you a notification "Your cycle has been replicated successfully." when the replication process is complete.
The replicated cycles are saved to the same workspace where the template is.
5. Update in batch (upload file)
You can update any cycle in a given workspace that has the matching name in the upload file with the correct hashtags.
Navigate to the workspace where you keep the cycles you wish to update
Click the dropdown menu of Create new cycle button
Click the Update in batch (upload file) button
Upload your .csv or .xlsx file by either dragging or searching your file.
The system will update all the cycles with a matching name and all the inputs with a matching hashtags in the process description fields or parameter identifier.
Note: The system ignores any data without a matching cycle name and hashtag or parameter identifier.