Carbon & energy readiness — one chain, one model
Every number on this dashboard traces back to the IFC file: a readiness gate first, then embodied carbon, then the cost case. Nothing here is a black box — the spec each check runs, and the assumptions each result carries, are one click away throughout.
IFC → Readiness → GWP → NPV
Where this project sits in the chain right now
What this actually is
For the person looking at this for the first time
| Stage | What happens | What you get |
|---|---|---|
| 01 IFC | You export your model — Revit, Archicad, anything that writes IFC4. | Nothing changes about how you model. |
| 02 Readiness | Your model is checked against a published IDS spec — material, quantities, classification. | A gap table + fix list, re-runnable after every revision. |
| 03 GWP | Embodied carbon computed from your actual quantities, staged per EN 15978. | Hotspots ranked by impact, not by guesswork. |
| 04 NPV | Carbon findings priced against real financial scenarios. | A decision, not just a number — with the flip called out if it happens. |
The IDS spec, in plain language
This is the actual spec your model gets checked against — not a summary of it. Each row below is one real requirement from v0-structure-readiness.ids or envelope-thermal-readiness.ids, why it exists, and how this project currently checks out.
Structure — material, quantities, classification
v0-structure-readiness.ids · checked against STUDIO-01's structural elements
Envelope & spaces — energy readiness
envelope-thermal-readiness.ids · a separate spec, on purpose — this serves the energy validation service line, not the carbon one
Why two separate spec files, not one
- Different service lines: structure/classification feeds the LCA (carbon) work; spaces/thermal feeds energy model validation.
- A client buying one service shouldn't be handed pass/fail results for a service they didn't ask for.
- Each spec is independently re-runnable after any model revision — you keep both files.
Assemblies & materials
Every element that passed the readiness gate, grouped the way an EPD database expects to see it — Uniformat classification, not just a Revit family name.
STUDIO-01 — element schedule
Pulled directly from IFC — material and classification as-modeled
| Element | Uniformat | Material | Net volume |
|---|---|---|---|
| Wall-01 (exterior) | B2010 | Concrete, Cast-in-Place | 4.50 m³ |
| Slab-01 (floor) | B1010 | Concrete, Cast-in-Place | 6.00 m³ |
Embodied carbon by stage & system
Global warming potential, staged per EN 15978. Illustrative figures below — the format a real result would ship in, once the calculation engine sits behind this readiness gate.
GWP by building system
42.3 tCO₂e total (A1-A3) · stacked by life-cycle stage
Hotspot ranking
Top contributors, A1-A3 only
Boundary & assumptions (ships with every real result)
- Stages: A1–A5, B4, C1–C4. Module D calculated, reported separately, never counted toward compliance.
- Database priority: Manufacturer EPD > Plant-specific EPD > regional/industry-average > generic. NA/Canada uses TRACI, not CML.
- Biogenic carbon: −1/+1, modeled explicitly by module — not a single netted number.
- Reinforcement not called out on drawings uses the LCA tool's own average reinforcement dataset, flagged as an assumption — never a silent guess.
Thermal performance
Feeds the energy validation service line — checked against envelope-thermal-readiness.ids, separate from the carbon chain above.
Envelope U-values
Pset_WallCommon.ThermalTransmittance, as modeled
Thermal bridging checklist
Reference points, per BC Hydro's BETBG — not yet run against this project
The decarbonization case
Illustrative figures — the shape a real GHG-LCCA result takes once carbon findings are priced against financial scenarios per the four-scenario framework.
Scenario comparison
40-year NPV, real discount rate 3.0% · CAD
STUDIO-01 · IFC4 · generated for demo purposes via templates/ids/generate_fixtures.py and generate_fixture_energy.py. Readiness results in this dashboard are real tool output; carbon and cost figures are illustrative pending the calculation engine.