Module
Four thousand clashes in. The sixty that matter out.
Pull every clash test straight from the live Navisworks model, or drop in a BCF. Bimiq folds them into real issues, ranks them by what actually goes wrong on site, and writes your decisions back into Navisworks.
From the raw test to the sixty that matter.
Pull
Bimiq reaches into the open Navisworks model through the Bridge and pulls every clash test, result by result: elements, GUIDs, positions, distances, native status. Large models sync in resumable chunks, so a 50,000-result pull doesn't time out or start over. No export, no manual round trip.
Or drop in a BCF 2.1 file. Both sources run through the same pipeline.
Sync from Navisworks
Syncing32,480 / 50,000 results
65%
elements, GUIDs, positions, distances, native status
Group
Every raw clash is folded by the pair of elements that actually collide. One duct crossing one girder becomes one issue, not the eleven results Navisworks logged for it. This step is deterministic: it costs nothing, and it never drifts between runs.
Navisworks
+ 8 more
Bimiq issue
Duct DT-4021 vs Girder GR-118
11 results folded into 1
Prioritise
Bimiq reads the categories, levels, models and properties of both elements and ranks each issue by real-world consequence, not by which two disciplines happened to collide. Blocking egress or breaching a fire-rated wall is critical. A duct sitting low under a ceiling is medium.
L03 · MECH ↔ STR: 600×400 supply duct vs W21×44 girder, west bay
Critical: Passes through a fire-rated separation on the protected escape route.
It flags genuine noise too: duplicates, tolerance overlaps, temporary objects, already-approved conditions, each with a reason. And it's deliberately conservative: when it isn't sure, it doesn't dismiss.
+16m · Bay E4
MECH ↔ STR
+16m · Bay E5
FIRE ↔ ARCH
+12m · Bay B2
STR ↔ ELEC
Act
Assign an owner. Set a status. Raise an RFI with the clash already attached, log a decision against it, or open the exact clash in the live Navisworks model.
L03 · MECH ↔ STR
600×400 supply duct vs W21×44 girder
CriticalZones
“Where do I go on Monday?”
Bimiq groups issues by where they physically are in the building, using the coordinates of the clash itself. A bay where one duct fights six members reads as one place, and usually one RFI, instead of six scattered rows.
Not from layer names. Level names are only as honest as whoever set up the file: on a real ArchiCAD export they arrive as 3DWALLS and cladding-dims. Those are layers, not storeys, and a tool that zones on them will confidently send you to “3DWALLS.”
Coordinates don't lie, so Bimiq uses those, and falls back to level and grid only for sources that carry no position at all.
Clash Matrix
The matrix your BEP already specifies.
Set the rules once. Structural against MEP on Level 3 is critical, and it belongs to the mechanical lead. Rules apply in the order you put them in, and they run before the AI ever weighs in.
The rules you set always take priority. The AI only weighs in where the matrix is silent.
The model changed. Your decisions didn't.
Issues are keyed to the elements themselves, so a re-sync re-reads the model without re-litigating your calls. Bimiq carries your work into the next run.
Sync on Monday. Sync again Thursday. Thursday's list is what changed, not what you already decided.
The round trip
It goes back into Navisworks.
Push your triaged decisions into the native clash results, matched by GUID. Your coordination doesn't sit in a parallel tool that everyone forgets to check. It lands in the model the team already opens.
In BimiqIn Navisworks
Sync to Navisworks
PreviewWrite 47 results
Nothing moves until you confirm.
You see exactly what will be written, and how many results it touches, before anything moves.
Status writes on every supported version. Priority write-back needs Navisworks 2026+.
Every issue, in a file you own.
Every issue exports with its title, priority, status, owner and Bimiq's reasoning intact.
Bimiq is where the coordination happens, but your data isn't locked inside it. It leaves in a format the rest of your toolchain already reads.
BCF 2.1
The open handoff. Lands in BIMcollab, Solibri or ACC the way any BCF does.
Excel
The weekly coordination report your PM asks for, already filled in.
CSV
Plain rows, for whatever your team has built around them.
Your next coordination cycle starts soon
Connect your model, drop in your specs, and see what Bimiq finds in the first hour.
14-day free trial. No credit card required.