EPD Tool Migration from ecoinvent 3.8 to 3.10 is planned for the last week of November 2024. This migration will help streamline the transition to new EPD tools and will include the following changes:
● Mapping of Existing Data: Existing designs, data lists, and private constructions will be mapped to the respective ecoinvent 3.10 data (where available) and migrated to a copy of these entities in the latest version of the EPD tool and user company accounts.
Example: An existing project in EPD Hub V2 tool using ecoinvent 3.8 datasets will have a duplicate project created in EPD Hub V3 tool and the designs within that project will be updated with ecoinvent 3.10 datasets.
- Project names will have "EI 3.10 -" prepended and "- tool name" appended
- Designs within a migrated project will retain their original name
- Private construction will retain their original name, however, the duplicated construction type will be updated as 3.10
- Data lists will have "EI 3.10 -" prepended
● Handling of Unmapped Data: A small percentage of data (<1%) may be left unmapped from ecoinvent 3.8 to 3.10, or may require attention due to lower probability of accurate mapping. A detailed list of these data points will be available in this Help Centre article once the migration is completed. In the newly created ecoinvent 3.10 entities, these datasets will be handled as follows:
1. Designs: The ecoinvent 3.8 dataset(s) will remain with a warning
2. Private Constructions: The ecoinvent 3.8 dataset(s) will remain without a warning
3. Datalists: Any unmapped datasets will be removed from the list
● Actions Required After Migration: We encourage users to begin using the new tools and import forms for all future projects, including the new datalist and construction types aligned with the ecoinvent 3.10 database. The new import forms can be found in our Help Centre here. The current ecoinvent 3.8 tools will transition to read-only mode in March 2025, and no further migration of projects or data will occur.
- Note that the newly created designs require a re-save in order to show the results.
- It is also recommended to review the list of unmapped datasets present in the excel file to see if it is needed to address any missing/inaccurate data in designs, data lists, or private constructions.
- If the duplication of datalists causes ecoinvent data limits to be exceeded, please contact us for assistance with increasing your limit or removing unnecessary data.
Should you have any other questions, please do not hesitate to reach out to our support team at [email protected].