Product data and lifecycle values in the design model
Lifecycle values exist, model objects exist — but they never meet in the design model. And that is where specification is decided.
Typical challenges
EPD and model live apart
EPDs sit as PDFs in a download area or a register, the geometry on an object platform. The values never reach the model.
No influence on specification
Product choice happens in the design model. Whoever does not exist there as a usable data set gets substituted later.
Requirements are rising
CPR 2024/3110 requires digital product and environmental data from 2026, the EPBD introduces GWP limits, and in Switzerland MuKEn 2025 anchors embodied energy.
How IFCLint solves it
Values into the model
Lifecycle and product values are written per material into the IFC model, rule-based, from CSV or KBOB/EPD data.
Verifiable and comparable there
Designers see the values in the model and can compare variants without switching tools.
Under your name
Your products appear as your products, with a pointer to your advisory service.
- Validate, correct and enrich in one place.
- No code, for the whole team.
- Browser-native, GDPR-compliant in the EU.
The relevant features
- Product data with lifecycle values in the design model
- Verifiable, comparable values at the decision point
- Dated validation report as evidence
What IFCLint does not do
- No creation or certification of EPDs — that is the job of verifiers and programme operators. IFCLint uses existing, verified data.
- No geometry or clash checking.
- Automatic CO₂ evaluation is in preparation. Writing the data into the model is available.