Validate the IFC before you send it.

buildingSMART IDS specs, model-health audits, clash detection, naming and life-safety rules — all in a browser tab. Findings come back ranked, with 3D drill-in, and leave as BCF 2.1, HTML or XLSX so they land in whatever coordination tool the project already runs on.

Every model you issue is a claim about your competence. This is how you check the claim first.

  • Standard: buildingSMART IDS
  • Checks: IDS · health · clash · clearance · egress
  • Reports: BCF 2.1 · HTML · XLSX
  • Authoring: Build IDS specs without writing XML

Start here — IFC, RVT, NWD Checker

Run the project's IDS, get the report the project asked for. Drop the model and the .ids file. Every specification is applied element by element, and what comes back is a pass/fail per requirement with the failing elements listed by GlobalId — not a score, not a percentage. Export it as BCF and it opens in the coordinator's desktop tool with the issues already positioned.

  • buildingSMART IDS, applied requirement by requirement
  • Failures listed by GlobalId, clickable into the 3D view
  • Report out as BCF 2.1, HTML or XLSX

Open IFC, RVT, NWD Checker

What this set does

Health before compliance

Orphans, duplicate GlobalIds, missing storey assignments, a 12 km coordinate offset, broken external references. The things that break the next tool, found before it breaks.

Clash, without the seat

Run geometric clash and clearance checks online and export the result as BCF, so the coordination room gets the same artefact it always gets.

Write your own rules

IDS Maker builds buildingSMART-compliant specs visually — pick classes, restrict properties, set patterns. The XML comes out the other end; you never open it.

Tools in this category

How it works

  1. Upload. The IFC, plus an .ids file or a spec you saved earlier.
  2. Run the check. IDS, Health Check, clash, naming — whichever the deliverable is judged on.
  3. Send the findings. BCF into the coordination tool, XLSX to the QA spreadsheet, HTML to whoever asked for a PDF.

When you'd use it

The handover gate

The BEP names an IDS and a delivery date. You want to know you pass before the delivery date, not from the client's rejection email after it.

The inherited federation

Three consultants, three exports, one merged file, and no idea which of the three broke the storey structure.

The reply that has to be specific

Sending back 'your model is wrong' starts an argument. Sending back a BCF with 43 positioned issues starts a fix.

Where it stops

  • This complements a desktop validator, it doesn't replace one — the deep proprietary rule sets that ship with those tools aren't reproduced here.
  • Clash detection is geometric. It doesn't know your project's tolerance conventions unless you tell it.
  • An IDS pass means the model satisfies the spec you ran. It doesn't mean the spec was the right one.

FAQ

Which validation standards are supported?

buildingSMART IDS (Information Delivery Specifications) is the primary standard. The Health Check covers schema-level checks; Clash Detection handles geometric coordination. BCF 2.1 issues round-trip into any BCF-compatible coordination tool.

Can I author my own IDS rules?

Yes. The IDS Maker lets you build specs visually — pick classes, restrict properties, set value patterns — then export buildingSMART-compliant XML. No need to hand-edit the schema.

What format is the validation report in?

Choose HTML (shareable), BCF 2.1 (round-trips into desktop tools), or XLSX (sortable, filter-friendly for QA teams).

Does this replace a desktop validator?

For IDS validation and basic clash, yes — and you keep the same BCF outputs. For the deep proprietary rule sets that ship with some desktop validators, no. BIMCamel complements rather than replaces a desktop validator.

Do these tools take Revit and Navisworks files?

Most of them do. A Revit (.rvt) or Navisworks (.nwd) file is converted to IFC when you open it, then the tool runs on that IFC; your original file is not changed. Revit and Navisworks: IFC, RVT, NWD Checker; Validate IFC, RVT, NWD Element Names; IFC, RVT, NWD Health Check; IFC, RVT, NWD Repair Center; IFC, RVT, NWD Clash Detection; IFC, RVT, NWD Walkable Clearance Check; Swept Path Vehicle Tracking for IFC, RVT, NWD; Compare IFC, RVT, NWD Files; Assert Element Count; Abort on Validation Failure; Create and View IFC, RVT, NWD Issues; Find IFC Elements by Attributes; IFC, RVT, NWD Geometry Health Check; IFC, RVT, NWD Schema & Identity Check; IFC, RVT, NWD Spatial Structure Check; IFC, RVT, NWD Coordinate Check; IFC, RVT, NWD Data Completeness Check; IFC, RVT, NWD Performance Check; IFC, RVT, NWD Level Consistency Check; IFC, RVT, NWD Unit Consistency Check. Revit only: IFC, RVT Fire Compartmentation Check; IFC, RVT Space Program Conformance; IFC, RVT Accessibility Check; IFC, RVT Fire Escape & Egress Check; IFC, RVT Floor Area Takeoff. IFC files only for now, because they need IFC data the conversion doesn't carry yet: IFC Load-Bearing Continuity Check.

Related BIMCamel tool categories

  • Clean — for fixing what the health check just found.
  • Extract — when the answer needs to be a spreadsheet.
  • Create — to write the IDS or set up the clash tests first.