AI BCF Coordination for openBIM
Short answer: Yes — with Archi Automate you can point an AI client (Claude, Cursor, VS Code, Codex, or any MCP client) at a .bcfzip file and triage open coordination issues in plain language, then author and hand off new BCF topics complete with referenced IFC elements and auto-embedded snapshots. BCF is the open, vendor-neutral standard for trackable coordination issues, so everything you read or write stays portable across Solibri, BIMcollab, Navisworks, Revit, and Archicad. The whole flow runs headless through the openBIM connector, and any file write is gated behind an explicit Allow-changes permission so nothing is altered without your say-so.
Coordination is where BIM projects either hold together or quietly fall apart. Clashes, RFIs, missing data, and design questions pile up across disciplines, and the format that keeps them honest is BCF. Below is how AI-driven BCF coordination actually works, from reading a messy container someone emailed you to authoring a clean issue set you can pass to any tool on the project.
What BCF is, and why it's the lingua franca of coordination
BCF (BIM Collaboration Format) is an open buildingSMART standard for exchanging coordination issues without exchanging the whole model. A .bcfzip container holds topics — each one a discrete issue with a title, a type (Issue, Clash, or Request), a status, a priority, an assignee, a comment thread, and one or more viewpoints. Critically, a topic can reference specific IFC elements by their GlobalId, and it can carry a saved camera position and snapshot so the next person sees exactly what you saw.
That design is what makes BCF the lingua franca of coordination. Instead of mailing a 400 MB federated model every time someone spots a duct running through a beam, you send a few-kilobyte .bcfzip that any BIM tool can open. Solibri, BIMcollab, Navisworks, Autodesk® Revit®, and Graphisoft Archicad® all read and write it. Because BCF sits alongside IFC in the openBIM ecosystem, your coordination history is never trapped in one vendor's database. Pairing it with AI doesn't change the format — it changes how fast you can read, sort, and author the issues inside it.
Triage existing issues with AI
The first job is usually reading someone else's container. Open a .bcfzip and the open file becomes the session — no CAD application, no license, nothing to launch. The openBIM connector is headless, so it works on BCF and IFC produced by any tool, and in its default state it is strictly read-only. You can interrogate the whole container in conversation.
Ask "summarize open issues by assignee" and the AI lists topics grouped by who owns them, with status and priority alongside. Ask "which topics are unresolved?" or "how many clashes are still open and high priority?" and you get a ranked answer instead of clicking through dozens of rows. Under the hood the assistant composes governed operations at runtime: bcf_* calls that list every topic (guid, title, type, status, priority, assignee, plus comment and viewpoint counts) and, when you want detail, fetch a single topic's full record — its description, author and date, the entire comment thread, and the GlobalIds of the IFC elements it references.
For a project lead this turns a Monday-morning triage that used to mean opening a checker and scrolling into a two-minute conversation: who is overloaded, what is stale, which high-priority clashes nobody has touched since last week. Because everything is just the BCF data, the answers are exact, not paraphrased guesses.
Author new issues and hand them off
Reading is half the value; the other half is authoring. With Allow-changes enabled, you can create a brand-new BCF container from scratch, or add topics to an existing one, entirely through conversation. Tell the AI to "add a clash topic, high priority, assigned to the MEP lead, referencing these two elements" and it writes a properly structured topic with the status, priority, assignee, and the IFC GlobalIds you named.
The detail that saves real time: when you add a topic that references elements by GlobalId, each new topic gets an auto-embedded snapshot and camera framing those elements. The recipient opens your .bcfzip in their tool of choice and lands on the exact view — no "which beam did you mean?" round-trip. You can also add comments to build out the thread, then save the container back to .bcfzip when you're done.
That makes the author-and-handoff workflow genuinely fast: describe the problem, name the elements, let the assistant assemble the topic with its snapshot, and save. The output is a standards-clean container any downstream tool will accept, which is the whole point of working in BCF rather than a proprietary issue tracker.
The one-step validate-to-BCF move
One workflow deserves a special mention. If you're running an IDS (Information Delivery Specification) check against a model, every requirement that fails is, in practice, a coordination issue someone needs to fix. Instead of transcribing those failures by hand, bcf_from_ids turns an IDS validation result into a ready-made BCF issue set in a single call — each failing element becomes a topic with the right references already attached. It's the fastest path from "this model doesn't meet the brief" to "here's the tracked issue list, assigned and ready." There's a full walkthrough in validating IFC to BCF in one step.
Vendor-neutral handoff to any tool
The reason all of this matters is portability. A BCF container you author with AI is not a proprietary export — it is the same open format your consultants, contractors, and checkers already use. Save the .bcfzip, drop it in your CDE or email it, and the receiving party opens it in Solibri, BIMcollab, Navisworks, Revit, or Archicad with the snapshots, cameras, and element references intact. The AI accelerates the reading and writing; the format guarantees the handoff. You never trade speed for lock-in.
That neutrality also means BCF coordination slots cleanly into the rest of an openBIM pipeline — clash detection feeding issues in, IDS checks feeding issues in, and a clean container flowing back out to whoever needs to act.
A note on safety
Because BCF coordination can both read and write files, the guardrails matter. By default the connector is read-only: you can open a container, list and triage topics, and pull full detail without any risk of altering the file. Creating a container, adding topics or comments, and saving all require you to switch to Allow-changes first. Every operation is audited, and nothing is auto-saved — the assistant composes governed operations at runtime, but the write only lands when you've explicitly permitted it and the save step runs. In practice that means you can hand the read/triage workflow to anyone without worrying they'll clobber the container, and reserve write access for when you're deliberately authoring.
Where to go next
BCF coordination is one piece of a broader AI-for-openBIM workflow. If you want to see how the issues get created upstream, or how to connect a client in the first place, these are good next reads:
- MCP for IFC and openBIM — the headless connector that powers BCF and IFC sessions.
- IFC clash detection with AI — find the conflicts that become BCF clash topics.
- IFC IDS validation with AI — the checks that feed
bcf_from_ids. - Validate IFC to BCF in one step — turn validation failures into a tracked issue set.
- Revit to IFC QA pipeline — get clean IFC out before you coordinate on it.
- Connect Claude to your AEC tools — set up the AI client side.
Archi Automate is AI for AEC: one Windows installer bridges Revit 2025–2027, Rhino 8, Archicad 29, and the headless openBIM connector to whichever AI client you already use. There's a 14-day trial with no key required, so you can open a real .bcfzip and triage it the same afternoon. Start with Archi Automate AI for AEC.
