Test your model against the building code
Run your federated IFC model through an automated check against the Bbl. Every applicable rule is tested against the model's geometry and properties, and the result comes back as a clear pass, warning, or failure per article, each one traced to the element that triggered it. You see where the design already meets the building code and where it doesn't, long before anyone walks the site, and a failure turns straight into a finding your team can pick up.
Checking a model against the code by hand doesn't scale
Reading the Bbl article by article against a model is slow, and it's exactly the kind of work where a tired eye misses things. On a real project the model changes every week, so a check done once is stale by the next revision. The result is that code issues surface late, on site, where they are expensive to fix. And when a reviewer does flag something, the reasoning lives in their head or a side email instead of next to the element it concerns.
The code, checked against your model on demand
- Test the model against every applicable Bbl rule in one pass, instead of reading articles by hand.
- Get a clear pass, warning, or failure per article, with the count of what passed, what to watch, and what failed.
- Trace each result to the exact element that triggered it, so nobody hunts for what the rule is about.
- Turn a failure into a finding your team can assign and resolve, right where the issue is.
Key capabilities
Checked against your model
The check runs on your federated IFC model, testing the actual geometry and properties, not a checklist someone fills in by hand.
Pass, warning, or failure
Every applicable article comes back with a clear verdict and a running count, so you know at a glance where the model stands against the Bbl.
Traced to the element
Each result points at the element that triggered it, so a failure is never an abstract line in a report. You see exactly what to look at.
Straight into a finding
A failure becomes a finding your team can assign, photograph, and follow to verified, so the check feeds the same workflow as the rest of your snags.
Frequently asked questions
- What does the compliance check test?
- It runs your federated IFC model against the applicable Bbl rules, testing the model's geometry and properties. Each rule returns a pass, a warning, or a failure, tied to the article it comes from.
- How do I know which element caused a failure?
- Every result is traced back to the element that triggered it. You see the element and the article together, so there's no guessing what a failure is about or where to find it in the model.
- What happens to the issues it finds?
- A failure or warning turns straight into a finding, so it lands in the same board, calendar, and dossier as the rest of your work. Your team assigns it, fixes it, and follows it to verified.
A visual tour of the workflow.