IFC Classification Checking: Why Models Fail Rule Checks

· 4 min read · By Verify AI

A model fails a rule check when the checker cannot recognise the elements the rule applies to. The most common cause is classification: an exit door exported as a generic object, a room with no usage, an element on the wrong storey. The code rule is fine. The model never gave it anything to test.

This guide covers five classification problems that block fire compliance rules, what each looks like in IFC, and how to fix it at the source. For the checking workflow, see BIM fire compliance checking.

What "classification" means here

Two layers matter:

  1. The IFC class of each element: IfcDoor, IfcWall, IfcStair, IfcSpace, IfcSlab, and so on.
  2. Optional classification codes linked to elements through IfcClassificationReference, if your project uses a classification system. buildingSMART's data dictionary, bSDD, hosts classifications that models can reference.

A rule engine finds elements by class and property. If the class is generic or wrong, the rule does not apply.

Problem 1: critical elements exported as proxies

IfcBuildingElementProxy is a generic placeholder. A fire exit door, a damper or a fire-rated wall exported as a proxy cannot be recognised by exit-door, damper or compartmentation rules. It happens when an authoring category is not mapped to an IFC class in the export settings.

Fix: map the category to the right class in the export configuration and re-export. Search the output for proxies on anything that matters for fire.

Problem 2: rooms with no usage

Occupant load, travel-distance limits and exit width all depend on what a space is used for. IfcSpace objects with no usage or occupancy cannot be assessed.

Fix: record usage or occupancy for every room, in the property or classification your project uses.

Problem 3: wrong or missing storey assignment

Vertical rules (stairs, shafts, compartmentation) need every element on the correct IfcBuildingStorey. MEP elements often arrive with no storey.

Fix: confirm assignment in the authoring tool, and check it again in the exported file.

Problem 4: different naming and coding between models

Architectural and MEP models that call the same stair or space by different names cannot be matched across disciplines. Cross-model checks, such as a stair against its pressurisation fan, fail quietly.

Fix: agree identifiers and naming up front, in the BIM execution plan.

Problem 5: custom properties instead of the standard ones

Fire ratings stored in a custom parameter are invisible to tools that read the standard property sets. The standard locations are Pset_DoorCommon.FireRating on doors and Pset_WallCommon.FireRating on walls, and buildingSMART guidance notes that you should use the existing property sets rather than invent your own.

Fix: map your authoring parameter to the standard property set in the export settings.

A quick self-check before you run a compliance check

Check Pass condition
Proxies None on doors, walls, stairs, slabs, dampers
Spaces Every room has a usage and a closed boundary
Storeys Every element assigned to the right level
Properties Fire ratings in the standard property sets, in one format
Naming Same identifiers across architecture and MEP

See the IFC model health check and IFC classification check pages for what each reports, and the IFC validation matrix as a one-page PDF.

Frequently asked questions

What is IFC classification checking?

A check that every element in an IFC model has the right IFC class and the properties rules need, so fire and code rules can find the elements they apply to.

Why do I have so many IfcBuildingElementProxy objects?

Usually because authoring categories were not mapped to IFC classes in the export settings. Fix the mapping and re-export.

Is an IDS file the same thing?

Related. An Information Delivery Specification (IDS) is a buildingSMART standard way to state what information a model must contain. Classification checking confirms the model meets requirements like those before code rules are applied.

Does the check change my model?

No. It reports what is wrong and where. You fix it in the authoring tool.

Find out what your model is missing

Verify AI reads IFC2x3 and IFC4 and reports unclassified or mis-classified elements before it runs fire rules. Talk to the founder about checking your model.

Sources

Property and class names follow the buildingSMART IFC documentation. Confirm details for the IFC version you export.

← All articles · Try Verify AI