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
- Codes do not mention IFC, but every rule depends on knowing what an element is: exit, stair, compartment wall, fire door, sprinkler, damper.
- Occupancy and use of each space decide occupant load, travel distance limits and exit width.
- Elements must sit on the right storey so vertical rules (stairs, shafts, compartmentation) work.
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
| Element | IFC entity | What a check reads |
|---|---|---|
| Rooms and corridors | IfcSpace | Space boundaries and the occupancy or use recorded as a property or classification |
| Doors | IfcDoor | Class, host wall relationship, fire rating property |
| Walls | IfcWall, IfcWallStandardCase | Class, fire rating, compartment property |
| Generic objects | IfcBuildingElementProxy | Flagged: the checker cannot tell what the object is |
| Storeys | IfcBuildingStorey | Which level every element belongs to |
| Classification codes | IfcClassificationReference | Codes from a classification system linked to the element, where your project uses one |
Why models fail this check
- Critical elements exported as IfcBuildingElementProxy because the authoring category was not mapped to an IFC class.
- Rooms with no usage or occupancy recorded, so occupant load cannot be calculated.
- Elements missing a storey assignment, or assigned to the wrong level.
- Inconsistent naming and classification between the architectural and MEP models.
- Custom property names used instead of the standard property sets, so tools cannot find the values.
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
- Map categories: in the export settings, map every authoring category that matters for fire (doors, walls, stairs, slabs, spaces) to its IFC class.
- Remove proxies: search the exported model for IfcBuildingElementProxy and fix the mapping for any element a rule needs.
- Record usage: give every room a usage or occupancy value so occupant load can be derived.
- Check storeys: confirm each element is assigned to the right IfcBuildingStorey.
- 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
- BIM fire compliance checking: the complete guide
- IFC model health check
- Fire door rating validation
- Service penetrations and fire-stopping
- How to check an IFC model for building code compliance