Most BIM coordination tools are pretty good at finding clashes. The hard part is sifting through hundreds (sometimes thousands) of results, figuring out which ones matter, identifying the root causes, and deciding how to resolve them.
I've been building something called ORCA to see how much of that process can be automated.
The idea is to go beyond clash detection and actually propose and validate resolutions.
Here's what it currently does:
- Triages all clashes, including those that appear to share the same underlying cause.
- Proposes geometric fixes rather than simply flagging the problem.
- Validates each proposed fix against the model geometry, checking whether the original clash is resolved, required clearances are maintained, and new clashes haven't been introduced.
- Rejects failed proposals and attempts alternative solutions.
- Shows before-and-after results, so you can review what actually changed.
- Connects to CDEs (currently ACC, Procore).
It runs entirely through the browser. No Navisworks plugin or desktop installation required. Just upload your IFC models.
ORCA recently took 3rd place in the Startup track at Meta's Global AI Developer Hackathon, which was encouraging. But hackathon demos and real construction projects are two very different things.
I'm also looking for a few people willing to test ORCA on real-world models. So far, it's only been tested on demo models, and I'd much rather find out where it breaks than assume it works because it passed a demo.
I'll appreciate some input from people working in this space.
A few questions for those of you doing this regularly:
- Would you trust a tool to suggest resolutions, provided you could review the geometry and validation results? Or would you prefer to work out the fix yourself?
- Where would this be most useful in your workflow? Before coordination meetings, during them, or somewhere else entirely?
I'm particularly interested in the edge cases that make automated coordination difficult.
For example, moving a duct might eliminate a clash but compromise access for maintenance, violate a required fall, interfere with insulation, or simply be impractical to install.
If you're interested, leave a comment or send me a DM.
For anyone curious about what it actually looks like:
Watch the demo video
Meta Hackathon submission
Would appreciate any criticism, particularly from people who've spent too many hours resolving clashes that should never have made it to a coordination meeting.