BIM to LCA Workflow: Why Material Data Breaks Between IFC and LCA Tools (2026)

When a life-cycle assessment (LCA) is late, a common cause is the handoff: material data does not flow cleanly from the BIM model to the LCA tool. The fix is less a better tool than a different split of responsibilities between IFC, IDS and EPDs in an openBIM workflow.

What is the BIM-to-LCA workflow?

The BIM-to-LCA workflow is the pipeline that moves material, geometric and quantity data from a BIM model (typically Revit or ArchiCAD, exported as IFC) into a life-cycle assessment tool such as One Click LCA, Tally, EC3 or LCAbyg. The LCA tool computes environmental impact indicators, following EN 15978 where the scheme or regulation calls for it, and reports whole-life carbon for the building.

Regulation is turning that pipeline into compliance infrastructure. Directive (EU) 2024/1275 (EPBD) Article 7(2) requires life-cycle global warming potential (GWP) disclosure in the energy performance certificate from 1 January 2028 (buildings above 1,000 m²) and 1 January 2030 (all new buildings). Country limits and dates, such as Denmark’s BR18 limit and France’s RE2020, are in whole-life carbon rules by country. LEED v4 BD+C MR Building Life-Cycle Impact Reduction Option 4 awards 3 points for a whole-building LCA. For the EPBD detail, see EPBD 2028 architect requirements; for the calculation method, see EN 15978 explained.

Where does the BIM-to-LCA workflow break?

Three failure modes appear on projects that move data from IFC into an LCA tool.

First, material naming mismatch: a Revit family named “Concrete C30/37” must map to an EPD record in a database that uses a different naming convention, such as “Ready-mix concrete CEM II/A, 30 MPa”. No common identifier exists across the two systems by default.

Second, environmental data is not carried by the material in a default IFC export. The IfcMaterial entity in IFC4.3 carries Name, Description and Category (Description and Category were added in IFC4). The buildingSMART documentation describes Pset_EnvironmentalImpactValues as a property set capturing the environmental impact values of an element, not of a material, and default Revit IFC exports do not populate it; check your exporter settings. Environmental indicators (GWP, ODP, AP, EP) therefore sit in an external EPD database and the model carries only a reference. Check the property set’s applicable entities in the buildingSMART IFC4.3 documentation for your schema version before relying on it.

Third, one BIM model is asked to carry everything (facility data, product specifications, environmental declarations) when the data architecture says those should be separate.

Key facts at a glance

Why does the data live outside the model?

Product environmental data comes from EPDs published by programme operators such as IBU, INIES, Ökobaudat, EPD Norway and EPD International. ECO Platform federates national programme operators under shared verification rules, but federation does not remove the lookup-key problem when a Revit material name has to find its EPD.

buildingSMART use case 3343 (openBIM and Sustainability) recommends three distinct IDS files rather than one consolidated model, and states that “The information may be found in one, two or three separate models or resources.” A Declaration IDS for EPDs keeps environmental values out of the IFC file and ties them to materials by reference.

How is whole-life carbon regulated across European markets?

Whole-life carbon rules differ by country in scope, unit and legal status: Denmark, France, the Netherlands, Sweden, Finland, the EU and London each use a different mechanism. The values, dates and sources are in whole-life carbon rules by country.

What is the leading-practice fix?

The following is practice guidance, not a regulation. Only the three-IDS split below comes from buildingSMART.

1. Standardize firm-wide Revit material naming with EPD lookup keys (or a bSDD reference). Keep the material library at the firm level, not the project level.
2. Use IfcMaterial with reference identifiers (a bSDD reference or an external reference to an EPD ID) instead of embedded environmental data. The reference points to the EPD, which lives in its own programme database.
3. Connect to the LCA tool through its IFC import where it has one, instead of manual material entry, which is a transcription-error risk.
4. Test the mapping on a small model export before committing the workflow to a live project, so naming mismatches surface early.

What is the buildingSMART three-IDS pattern?

The buildingSMART three-IDS pattern splits sustainability information across three Information Delivery Specifications: a Facility IDS for building, infrastructure, systems, components and spaces; a Product IDS for types, materials and products; and a Declaration IDS for EPDs per ISO 21930. It is buildingSMART’s answer to where environmental data should live.

The use case itself states: “The information may be found in one, two or three separate models or resources.”

Separate files suit data that changes at different rates and has different owners. Facility data changes through the design, a product library changes when products change, and an EPD is valid for 5 years. One EPD record can also be referenced by many products across many buildings.

Common mistakes

1. Treating Revit or ArchiCAD as the system of record for environmental data. The EPD record in the programme database is the system of record. Revit carries the reference identifier; the EPD database carries the values.

2. Assuming a default IFC export carries GWP. IfcMaterial has no environmental indicator attributes, and Pset_EnvironmentalImpactValues describes element-level values that default Revit exports do not populate. Check what your export actually writes before promising environmental data in the model.

3. Building one lookup table per project instead of a firm-wide library. Per-project mapping work repeats on every project. A firm library is reused: each project builds on what the last one mapped.

4. Embedding EPD PDF links in IfcMaterial.Description instead of a stable identifier. PDF links go stale. Stable identifiers (a bSDD identifier, an EPD registration number, an Ökobaudat UUID) survive across publication cycles.

Frequently asked questions

Why doesn’t IFC carry environmental data natively?

IfcMaterial in IFC4.3 carries Name, Description and Category, not environmental indicators, and the buildingSMART property set for environmental impact values is defined at element level. buildingSMART use case 3343 recommends separate Facility, Product and Declaration IDS resources, because facility data, product data and declaration data have different owners and update rates.

Do I need bSDD identifiers or are EPD registration numbers enough?

Either works as long as the identifier is stable. bSDD references can point to classification systems across regions, which helps on projects that span several markets. An EPD registration number ties directly to one verified EPD record, which is simpler when working within a single programme.

Is the BIM-to-LCA workflow required by EU EPBD 2024/1275?

The directive does not require BIM; its Article 7(2) duty is in EPBD 2028 architect requirements. Producing the calculation from a model is a practical way to get the material quantities it needs.