VitruAI + Solibri
VitruAI for Solibri reads Solibri rule sets (.cset) and ITO outputs to extend existing IFC checks with agent-driven rules that do not fit neatly into static trees, such as classification reasoning and room-program inference. It supports Solibri Office 9.13+ on Windows and macOS and is available as a Labs engagement under MSA + Appendix.
- Reads existing Solibri rule sets (.cset) and ITO outputs so agents complement, rather than duplicate, the firm’s current Solibri checks.
- Closes gaps that Solibri’s static rule tree does not cover, including classification reasoning, room-program inference, and jurisdiction-specific advisory rules.
- Ships as a Labs engagement under MSA + Appendix, scoped against one live project and the firm’s current Solibri rule pack.
Install, requirements, and what runs through the integration.
-
Solibri Office 9.13+ on Windows and macOS
The integration connects to Solibri Office 9.13+ on Windows and macOS, using the rule-set and ITO APIs that are not exposed in Solibri Anywhere. Firms keep their existing Solibri workspaces, role files, and discipline-specific rule packs. For IFC model movement between tools, many customers pair this with the IFC + openBIM integration and the IFC round-trip validation workflow.
-
Solibri rule-set (.cset) read
VitruAI reads existing Solibri .cset rule sets so agents understand which checks already run and avoid duplicating them. The Code Compliance Agent and Studio QA/QC Agent then target the gaps that are hard to encode as static rules, such as advisory interpretations, cross-model program checks, or jurisdiction-specific narrative clauses. This keeps Solibri as the primary rule-tree engine while agents handle judgement-heavy logic.
-
ITO (Information Takeoff) and classification-aware reasoning
The integration consumes ITO exports and Solibri classifications to drive higher-order reasoning about counts, areas, and program compliance. Agents can infer room programs from space names, classifications, and ITO quantity sets, then compare them against external briefs or jurisdictional tables. This is particularly useful where Solibri’s numeric checks pass but higher-level intent, such as adjacency patterns or departmental zoning, still needs review.
-
BCF round-trip into Solibri
Findings from VitruAI agents are written as BCF 2.1 or 3.0 issues, including viewpoint, component references, and a structured description. These BCF files open directly in Solibri’s issue viewer alongside the firm’s native Solibri clashes and rule hits. The same BCF payload can also feed downstream coordination tools or IFC viewers connected through the IFC + openBIM integration, keeping one issue stream across authoring platforms.
-
Available now as a Labs engagement
VitruAI runs this as a Labs engagement under MSA + Appendix, co-designing the agent rule pack around the firm’s current Solibri Office environment. The first deployment typically focuses on one project and one jurisdiction, then folds into a broader Roadmap cohort once patterns stabilise. Many Labs scopes pair Solibri-based checks with the Code Compliance Agent or Studio QA/QC Agent to cover both IFC and native-model workflows.
Solibri integration FAQ
-
Does this replace Solibri?
No, this integration keeps Solibri Model Checker as the primary rule-tree engine and adds agents around it. Solibri still runs its existing .cset libraries for clashes, clearances, and model-structure checks, while VitruAI focuses on rules that do not fit neatly into static trees, such as advisory interpretations or cross-discipline narratives. Many firms treat this as an extension of their current Solibri-based QA stack rather than a replacement.
-
Does it work with Solibri Anywhere (free)?
No, the integration requires Solibri Office because the rule-set and ITO APIs are not available in Solibri Anywhere. Anywhere remains useful for viewing IFCs and BCF issues that VitruAI produces, but it cannot host the rule-set integration itself. For teams that rely heavily on viewers and other tools, the IFC + openBIM integration keeps those workflows aligned with the Solibri-based checks.
-
How are results delivered?
Results are delivered as BCF 2.1 or 3.0 issues that open directly in Solibri’s issue viewer alongside the firm’s native Solibri output. Each issue carries viewpoints, component references, and a description that names the agent, the check, and the suggested remediation. The same BCF stream can participate in an IFC round-trip validation workflow so authoring tools and Solibri stay in sync on issue status.
-
Is this an IFC-only integration?
Yes, the VitruAI + Solibri integration sits on the IFC layer and uses Solibri’s IFC-based model representation. Native Revit, Archicad, or Rhino models enter this flow once they are exported to IFC and passed through Solibri Office. For firms that want consistency between native and IFC checks, pairing this integration with the IFC + openBIM integration and agents like the Studio QA/QC Agent keeps rule intent aligned across both worlds.