IFC 2x3 & IFC4 · buildingSMART IDS 1.0 · BIM quality assurance

Specification clauses, checked against the BIM model you are delivering.

Upload a native IFC file or an IDS specification, run deterministic validation, ask the Evidence Assistant what the results mean, review findings with your team, control regressions against a baseline, and export a checksummed audit package.

Working product · Demo includes passes, failures, an unknown finding, a waiver and two revisions

Model formats
IFC2x3 · IFC4 · model JSON
Specifications
buildingSMART IDS 1.0 · JSON · CSV · XLSX · DOCX · PDF
Parser
Server-side web-ifc — no plugin, no desktop install

Demo project

Riverside Office

Baseline set

Requirements

6

Pass / fail

mix

Unknown

1

req-office-min-areaOffice min areaFail
req-stockroom-door-widthStockroom door widthWaived
req-fire-rating-unknownEI 90 compartment wallsUnknown
req-room-has-doorRoom has connected doorFail
Two revisions seed regression; audit ZIP uses SHA-256 checksums — not a digital signature.

Workflow

What the product actually does

These steps are live in the workspace today — not a roadmap. Nothing here promises digital signatures, SSO or features that are not shipped.

  1. 01

    Import documentation

    Bring in native IFC2x3 / IFC4 or model JSON, plus a specification from buildingSMART IDS 1.0, JSON, CSV, or a reviewed XLSX, DOCX or PDF package.

  2. 02

    Deterministic validation

    The server re-runs structured rules against the BIM model. Results are never accepted from the client.

  3. 03

    Source traceability

    Every finding links back to a requirement, clause and — when available — document provenance.

  4. 04

    Evidence Assistant

    Ask questions in plain language. The assistant explains server-verified evidence; it can never invent or override a pass or fail.

  5. 05

    Human review

    Acknowledge, resolve or waive findings with a named reviewer, reason and optional waiver expiry.

  6. 06

    Regression & audit export

    Compare against a baseline release policy, then download a checksummed audit ZIP.

Demo findings

Follow a real requirement from the Riverside Office demo

The guided demo project seeds the same outcomes: passing rules, concrete failures, one unknown textual clause, and a waived door-width finding.

01 · Source requirement

Stockrooms must be at least 15 m² (Spec §3.2.1).

Riverside Office · Revision A

02 · Structured rule

room.roomType == stockroom && room.areaSqm >= 15

03 · Validation result

Stockroom B · 11.2 m²

Observed

11.2 m²

Required

≥ 15 m²

04 · Review decision

Fail · Critical

Reviewers record status, comment, waiver reason and expiry before the audit export.

Evidence Assistant

Ask the model in plain language. Keep deterministic answers.

The assistant explains and navigates evidence the rule engine has already produced. It is deliberately not allowed to decide compliance — validation stays deterministic, and the assistant cannot invent or override a pass, fail or unknown.

  • Rules decide, the assistant explains

    Every question triggers a server-side re-run of the rule engine. The assistant receives normalized BIM facts and generated evidence — never the authority to change an outcome.

  • Citations are verified before you see them

    Requirement and element references in the answer are checked against the generated evidence. Anything the server cannot confirm is rejected rather than displayed.

  • Unknown stays unknown

    When the model is missing a property or relationship, the result stays unknown. There is no path by which a missing fact becomes a passing check.

  • Honest about its own mode

    The panel reports the provider actually in use. With no AI provider configured it answers deterministically from the same evidence and says so.

Evidence Assistant

AI · gemini

Which stockrooms fail, and what could not be determined?

Stockroom B fails req-stockroom-min-area at 11.2 m² against a required 15 m².

Door widths for rm-stock-02 stay unknown — the model carries no door relationship for that space.

Compliance status came from the rule engine. The assistant only explained it.

Element references open the matching room or door in the workspace inspector

Pricing

Limits that the API actually enforces

Caps on projects, members, monthly validation runs, storage, file size, audit exports, API/CI access and retention are checked on every mutating request — not only shown here.

Starter

Free

For evaluating the workflow on a real project.

  • 2 projects
  • 3 members per project
  • 25 validation runs / month
  • 200 MB storage · 10 MB files
  • 5 audit exports / month
  • 30-day retention
Max file
10.0 MB
Retention
30d
API / CI
No
Audit exports
5/mo
Start free

Professional

€149 / month

For delivery teams that need review, regression and CI.

  • 15 projects
  • 15 members per project
  • 250 validation runs / month
  • 5 GB storage · 50 MB files
  • 100 audit exports / month
  • API / CLI / CI access
  • 365-day retention
Max file
50.0 MB
Retention
365d
API / CI
Yes
Audit exports
100/mo
Use Professional limits

Enterprise

Custom

Custom limits, SSO readiness and dedicated support.

  • Custom project and seat counts
  • High-volume validation runs
  • Large model storage
  • API / CLI / CI included
  • Multi-year retention
  • EU region and subprocessors as documented
Max file
100.0 MB
Retention
2555d
API / CI
Yes
Audit exports
5000/mo
Talk to us in workspace

New accounts start on Starter. Sign in and upgrade to Professional from your workspace — Enterprise is arranged directly. Set FORCE_ACCOUNT_PLAN in development to exercise higher tiers.

First project

Sign in, load the demo, then replace it with your package.

The workspace checklist walks through project → model → specification → validation → findings → review → audit export. Empty and error states name the expected format and the next step.