IFC classification checking, before the rules run.

IFC classification checking confirms every element in your model is the right IFC class with the right properties, so fire and code rules can find it. See what is checked and why models fail.

What is ifc classification checking?

IFC classification checking verifies that every element in your model is exported as the correct IFC class (a door as IfcDoor, a room as IfcSpace) and carries the properties a rule needs. A code checker can only apply a rule to an element it recognises. If a fire exit door is exported as a generic proxy, the exit-door rules never run, and the model can look "clean" while real problems go unchecked.

What the code asks for

The exact values (ratings, distances, widths, densities) come from the code edition your authority applies, so a check always reports which edition and clause it used.

How it shows up in an IFC model

ElementIFC entityWhat a check reads
Rooms and corridorsIfcSpaceSpace boundaries and the occupancy or use recorded as a property or classification
DoorsIfcDoorClass, host wall relationship, fire rating property
WallsIfcWall, IfcWallStandardCaseClass, fire rating, compartment property
Generic objectsIfcBuildingElementProxyFlagged: the checker cannot tell what the object is
StoreysIfcBuildingStoreyWhich level every element belongs to
Classification codesIfcClassificationReferenceCodes from a classification system linked to the element, where your project uses one

Why models fail this check

What a Verify AI finding looks like

Example finding: object cannot be classified

Severity: HIGH

Element: IfcBuildingElementProxy "Door_Stair_02_L1"

Location: Level 1, Staircase 2 access

Detected: exported as a generic proxy

Impact: exit-door and fire-door rules cannot run on this element

Action: map the family to IfcDoor in the IFC export settings and re-export

This is an illustrative example. Every finding is pinned to the plan, names the element, and cites the clause it was checked against. See a full sample report.

How to prepare your model

  1. Map categories: in the export settings, map every authoring category that matters for fire (doors, walls, stairs, slabs, spaces) to its IFC class.
  2. Remove proxies: search the exported model for IfcBuildingElementProxy and fix the mapping for any element a rule needs.
  3. Record usage: give every room a usage or occupancy value so occupant load can be derived.
  4. Check storeys: confirm each element is assigned to the right IfcBuildingStorey.
  5. Re-export and re-check: repeat until the classification check reports no unclassified critical elements.

Frequently asked questions

What is IFC classification checking?

It is a check that every element in an IFC model has the correct IFC class and the properties needed by rules. It runs before code rules so those rules can find the doors, walls, stairs and spaces they apply to.

Why does IfcBuildingElementProxy cause problems?

A proxy is a generic placeholder. A rule engine cannot tell whether it is a door, a damper or a piece of furniture, so rules written for those elements never apply to it.

Is this the same as an IDS check?

Related, not the same. buildingSMART's Information Delivery Specification (IDS) is a standard way to state what information a model must contain. Classification checking confirms the model meets that kind of requirement; code compliance then applies fire rules to the result.

Does Verify AI fix the model?

It reports what is wrong and where, with the suggested change. Your team makes the change in the authoring tool and re-exports.

Related

Sources

Try Verify AI · See a sample report · Talk to the founder