One Click LCA Platform - Incident Report - 6th January 2025 - Default values are not generated correctly for certain material types

Scenarios based on LCA parameters are not populating and calculating for certain material types.
6th of January 2025

Incident Summary:

• On the 6th of January, it was noticed that certain materials did not get default values correctly generated for most columns in the queries of the Building tools. New inputs of those materials would not get default values generated for almost all columns in the queries during the incident. Pre-existing inputs of those materials would get some of their default values reset. This occurred because of an error in the scenario generation and the issue is now fixed. 

Which designs are affected:

• All the designs that were edited and saved between 3 January 18:45 UTC and 8 January 10:30 UTC. Not all edited designs and all data in those designs are necessarily affected. Users using exclusively the newer query interface were not affected by this.

Recommendations to ensure calculation quality:

• Users should resave all affected designs. This will ensure that transportation, site waste and operational impacts are calculated for all resources.
• Users who added new resources and saved them during the incident are recommended to re-add those resources or add any missing information for them in the different columns manually. 
• End of Life (C1-C4) Impact: Users using building tools that calculate waste treatment impacts, and use any of the “user-adjustable” End-of-Life methods in LCA parameters (default setting for projects), shall ensure the End-of-Life scenarios are correct for all data. This can be done in two ways: 1. Users that can see the End-of-Life column in the Materials query, can review the answers and edit them for all rows or more easily 2. Users can go to the LCA parameters for the project, switch the method to the “Material-locked” option, save LCA parameters, switch back to the original method, and resave LCA parameters. This will reset all End-of-Life settings to the default suggestions and recalculate the designs.
• Localisation: Users shall review the content of the “Localisation” column. This is not relevant for tools that don’t have manufacturing localization method enabled. The content of this column was reset to “Not applied” for all relevant materials. If this is not desired, users can reset the localization target for all rows by adjusting the column for each row manually. Users can also reset this for all resources at once, except in some cases One Click LCA generic data, by temporarily selecting to disable the manufacturing localization method in LCA parameters, save LCA parameters, switch back to the original method (v2.1 is the default), and resave LCA parameters to update and recalculate all the designs in the project. For One Click LCA generic data, the affected rows that are not updated by the aforementioned edit, have a yellow warning next to the material name, and users need to edit the content of the column manually or readd the resource and remove the old one.

  • Users using the below tools do not need to check localisation as these tools are not affected by manufacturing localisation method:

    • RE2020 and Energie Carbon
    • Klimatdeklaration, Miljöbyggnad 4.0
    • TEK 17
    • BR18
    • Rakennuksen vähähiilisyyden arviointityökalu (2021 versio)
    • DGNB tools
    • CalGreen
    • BREEAM UK IMPACT-compliant
    • QNG
     
• Business license users and others who can’t see the content of manufacturing localization and End-of-Life columns can reach out to the Customer Success team for additional support.

•  

Status: Issue has been resolved.

Event Timeline:

• 18:45 UTC 03/01: First instance of the issue in the logs.
• ~16:00 UTC 06/01/2025: Issue noticed and raised for investigation
• 10:30 UTC, 07/01/2025: Cause found and a solution is being worked on
• 10:30 - 14:00 UTC, 07/01/2025: Between this time period fixes were rolled out gradually for the vast majority of data
  
• 10:30 UTC, 08/01/2025: Fixes for all known cases were completed.

Incident Cause:

• The incident was caused due to an error during the database integration process.

Security Impact:

• The issue did not expose any users to security risks.