VitruAI + IFC / openBIM
The VitruAI + IFC / openBIM integration reads and writes IFC 4 and IFC 4.3 natively through IfcOpenShell, preserving geometry, property sets, classifications, and IFC types for tool-agnostic compliance and authority submissions. It is currently shipping with 1–3 design partners on IFC-first workflows where authorities expect clean IFC handover.
- Native IFC 4 and IFC 4.3 read/write with geometry, property sets, classifications, and IFC types preserved end to end.
- Tool-agnostic workflows across IFC from Revit, ArchiCAD, Tekla, Bentley OpenBuildings, and any IFC-compliant authoring tool.
- Authority-submission ready for jurisdictions that accept or require IFC, including Singapore CORENET, Norway, and parts of EU public works.
What the IFC integration covers.
-
IFC 4 and IFC 4.3 read/write
VitruAI reads and writes IFC 4 and IFC 4.3 on the same code path through IfcOpenShell, so the same Code Compliance Agent or Sustainability Agent logic runs across both schemas. IFC 2×3 remains supported for read so legacy projects and archives stay in scope, but new exports write to IFC 4 family only in line with buildingSMART guidance. Mixed-schema portfolios can run side-by-side checks while you migrate standards per framework or jurisdiction.
-
Property-set aware
Agents working on IFC understand `Pset_*` property sets as first-class data, so rule checks and edits target the same parameters your standards team already maintains. Firm-specific property sets register as configurable extensions, which means an office standard like `Pset_Office_Fire` can drive the same checks as native schema sets. This is critical for workflows like IFC round-trip validation where authority feedback arrives as property changes rather than geometry edits.
-
Classification-system aware
The integration reads and writes Uniclass, OmniClass, MasterFormat, and firm-specific classification systems on a configurable map. That map normalises differences between authoring tools such as Revit and Archicad so IFC exports carry consistent classification codes regardless of source. Agents can flag missing or inconsistent classifications before you push the model into Solibri or a CDE, reducing rework when public clients require strict code lists on every element.
-
Geometry-validation pass
Before you submit an IFC to an authority or an external coordinator, VitruAI runs a geometry-validation pass that checks watertightness, solid validity, and IFC type assignment correctness. Typical edge cases include walls exported as generic proxies, openings lost on export, or malformed solids that crash downstream tools. This pass feeds both internal QA and external workflows, including IFC round-trip validation where you need confidence that the differences are design changes, not export artefacts.
-
Solibri-compatible rule shapes
For firms running Solibri Model Checker as their primary IFC validator, VitruAI aligns issue shapes with the same rule logic so results stay comparable. Agents preparing models for Solibri use the same classifications, property sets, and geometry assumptions that your Solibri rule sets expect, which reduces false positives when you move between VitruAI and Solibri. This makes it practical to let agents run pre-checks and keep Solibri focused on final coordination or client-facing reports.
-
OpenBIM federation alongside Speckle and Archicad
VitruAI treats IFC as one of several openBIM backbones alongside Speckle streams and native Archicad models, so cross-tool federation does not depend on a single vendor stack. Agents can coordinate an IFC from Tekla against an IFC from Revit and an Archicad IFC export in the same run, then hand the merged result to Solibri or a CDE. This is the practical answer to firms asking for vitruai for ifc openbim without rebuilding their entire pipeline.
IFC / openBIM integration FAQs
-
Does this work with IFC 2×3?
VitruAI reads IFC 2×3 for legacy compatibility so older projects and archives remain checkable, but new exports write to IFC 4 or IFC 4.3 only. This matches buildingSMART’s guidance that IFC 4 family is the recommended target schema for new work. In mixed portfolios, agents can compare an IFC 2×3 archive against a fresh IFC 4 export to highlight migration issues before you involve external reviewers or Solibri.
-
Can VitruAI work without ever touching the authoring tool?
Yes, for firms that treat IFC as the lingua franca, VitruAI agents run entirely on IFC files without a Revit, Archicad, or Tekla add-in in the loop. This suits openBIM-led practices and public works projects where the contractual deliverable is IFC plus BCF, not native files. You can run the Code Compliance Agent or Sustainability Agent directly on IFC exports and exchange results through your CDE or Speckle workspace.
-
Is this Singapore CORENET ready?
The IFC integration supports CORENET-compatible IFC 4 profiles so models align with Singapore BCA’s submission requirements. Each Beta deployment calibrates export and validation settings to the firm’s templates and the specific CORENET profile in use. The Singapore BCA regulation page documents how VitruAI maps its rule libraries to BCA checks, and Beta partners receive a per-project accuracy report calibrated to their pipeline.
-
How does it handle vendor IFC quirks from Revit, Archicad, and Tekla?
Each authoring tool has known IFC export quirks, such as Revit’s tendency to overuse IfcBuildingElementProxy or differences in how Archicad and Tekla encode openings and composite elements. The IFC integration normalises common cases on a configurable map so downstream checks see consistent types and properties regardless of source. This mapping is especially important when you run multi-tool coordination or IFC round-trip validation across Revit, Archicad, Tekla, and Solibri in the same workflow.
-
What does the Beta cohort look like?
The Beta cohort currently targets 1–3 design partners with openBIM-led workflows or jurisdictions where IFC submission is expected by the authority. Typical candidates include firms delivering Singapore CORENET submissions, Norwegian or EU public works where IFC is contractual, or practices standardising on IFC plus Speckle for cross-office coordination. Cohort partners help refine rule mappings, export profiles, and integration points with tools like Solibri and the Code Compliance Agent.