How to Add Custom Data to IFC Models for Construction Tracking

IFC files are powerful containers of building data — geometry, materials, spatial structure, property sets. But they capture design intent. Once construction begins, a whole new category of data emerges that was never part of the original model: installation progress, inspection results, material substitutions, punch list items, warranty information.

Traditionally, this construction-generated data lives in spreadsheets, paper forms, or disconnected field management apps. The 3D model sits on one screen while the data sits on another. The connection between "this specific wall" and "its installation status" exists only in someone's head.

Custom attributes solve this by letting you attach project-specific data directly to elements in the BIM model — without editing the IFC file itself.

What Are Custom Attributes in BIM?

IFC files come with built-in property sets (Pset_WallCommon, Qto_DoorBaseQuantities, etc.) that are defined at export time by the design software. These are read-only — you can't add new properties to an IFC file without re-exporting from the authoring tool.

Custom attributes are a layer of project-specific metadata that sits on top of the IFC data. You define the schema (what fields exist, what types they are), and then your team populates values for individual elements. Think of it as adding custom columns to a spreadsheet where each row is a building element.

Common attribute types include:

• String — free text (notes, RFI references, inspector names)
• Number — measurements, quantities, percentages
• Boolean — yes/no flags (installed, inspected, approved)
• Date — installation dates, inspection dates, warranty expiry
• Enum — predefined options (status: "Not started" / "In progress" / "Complete" / "On hold")

Common Use Cases

Progress Tracking

Define a "Status" enum attribute with values like "Not started", "In progress", "Complete", and "Inspected". Field engineers update the status for each element as work progresses. Project managers filter by status to see completion rates per floor or per system — all visualized in the 3D model.

Quality Inspections

A QA inspector walks a floor with a tablet, opens the model in the browser, clicks each element being inspected, and records results: pass/fail, date, inspector name, deficiency notes. Back in the office, the compliance lead exports the data as CSV for regulatory reporting.

Material Substitutions

When specified materials aren't available, the engineer records the substitution directly on the affected element: substitute material name, reason, approval reference number. This data travels with the element — no separate tracking spreadsheet needed.

Punch Lists

At project handover, define attributes for punch list tracking: issue description, priority, assigned subcontractor, resolution date. Each punch item is attached to the specific building element it affects, making it easy to locate issues in the 3D model.

Adding Custom Attributes Without Editing the IFC File

The key insight is that you don't need to modify the IFC file to enrich it with data. Instead, custom attributes are stored separately and linked to elements by their IFC GlobalId — the unique 22-character identifier that every IFC element carries.

In Bimvue, the workflow is straightforward:

1. Define your schema — create attribute definitions for your project (e.g., "Installation Status" as an enum, "Inspection Date" as a date)
2. Click any element in the 3D viewer to select it
3. Fill in values in the properties panel — the data is saved immediately
4. Search and filter elements by their custom attribute values
5. Export filtered data as CSV or JSON for reporting

All changes are audited — every edit records who changed what, when, and what the previous value was.

Why GlobalId-Based Linking Matters

Design models change throughout construction. When the architect issues a new revision, you upload a new model version. If custom attributes were linked to internal database IDs, all your data would be lost with each new version.

By linking to the IFC GlobalId instead, custom attributes automatically carry over when you upload a new model version. The GlobalId is stable across exports — the same wall has the same GlobalId in version 1 and version 15. Your installation status, inspection results, and punch list items persist without any manual re-entry.

This is the difference between a useful tool and a frustrating one. Construction data shouldn't be disposable every time the design team issues an update.