abstractBIM
From IFC to IDA ICE in Minutes: The Crash-Free Import Workflow
Why the IFC You Received Will Not Import — and What to Do Instead
Published
Every building performance simulation project starts the same way: the architect sends an IFC, you drag it into IDA ICE, and the import either crashes, hangs, or produces a zone model full of leaking boundaries, overlapping volumes, and unassigned surfaces. The model was built for planning and visualization — not for the airtight, closed-volume logic a simulation engine demands.
The standard response is manual remodeling: retracing the building envelope zone by zone inside IDA ICE or an authoring tool. Depending on the project, that costs 2 to 5 days per model — repeated for every design iteration, because the architect's next revision resets your work to zero.
There is a faster path. It requires exactly one thing from the architect — IfcSpaces — and hands everything else to automated normalization.
Technical Step-by-Step: The IFC-to-IDA-ICE Normalization Protocol
This workflow works with IFC files from ArchiCAD, Revit, Vectorworks, SketchUp, or any other authoring tool. The only prerequisite is that the model contains IfcSpaces (room volumes).
- Request the Right Input (Phase 1): Ask the architect for an IFC that contains IfcSpaces, ideally modeled from top of finished floor to bottom of structural ceiling. Do not ask them to "clean up" or "fix" the model — that conversation costs weeks and rarely converges. Spaces, windows, and doors are enough; everything else is noise you can ignore.
- Verify the Spaces Exist (Phase 2): Open the file in any free IFC viewer (e.g. BIMcollab ZOOM or Open IFC Viewer) and confirm the room volumes are present. If they are, you are done with quality control. If they are not, send one sentence back: "Please export with IfcSpaces enabled." Every major authoring tool supports this out of the box.
- Upload to abstractBIM (Phase 3): Upload the IFC at abstractbim.com. The engine rebuilds the geometry from the IfcSpaces: it closes micro-gaps, resolves overlapping volumes, computes clean space boundaries, and establishes which wall sits between which two spaces. No settings, no mapping tables, no manual intervention.
- Download the IDA ICE Export (Phase 4): Download the result as gbXML or IFC. abstractBIM ships a dedicated, optimized export for IDA ICE — the geometry arrives as sealed, simulation-ready zones instead of raw architectural elements.
- Import into IDA ICE (Phase 5): Import the file into IDA ICE. Zones map instantly, boundaries are airtight, and the model is ready for zoning strategy, HVAC systems, and simulation runs — the actual engineering work you were hired for.
- Repeat on Every Design Iteration (Phase 6): When the architect sends revision 7, upload it again. Normalization takes minutes, so design iterations stop being a threat to your schedule and start being routine.
Comparison of Model Preparation Strategies
| Workflow Metrics | Strategy A: Manual Remodeling | Strategy B: Raw IFC Import | Strategy C: The abstractBIM Pipeline |
|---|---|---|---|
| Time Investment | 2 to 5 days of manual retracing per model — repeated for every revision. | Variable; hours lost to crash loops and boundary debugging. | Minutes from upload to a running IDA ICE model. |
| Data Integrity | Lost. The simulation model diverges from the architect's file with every manual edit. | Broken. Leaking boundaries, overlapping volumes, unassigned surfaces. | Preserved. Sealed zones with consistent space boundaries and semantics. |
| Design Iterations | Each revision restarts the remodeling clock. | Each revision restarts the debugging lottery. | Each revision is a re-upload. |
| Cost | Engineering hours billed to unproductive prep work. | Unpredictable. | Thermal simulation exports are free on abstractBIM. |