Back to Cookbook
KiloClaw

openBIM Exchange Pack Builder

IFC handoffs with receipts, not guesswork

Standardizes model exchanges between tools (IFC, DWG) by creating a versioned exchange pack: export settings, scope notes, a validation checklist, and an issues log — so consultant handoffs come with receipts instead of surprises.

CommunityWork10 min setup

INGREDIENTS

📄Google Docs✉️Email💬Slack

PROMPT

Create a skill called "openBIM Exchange Pack Builder". When I'm preparing a model exchange with a consultant (IFC or DWG), you should: 1. Create an exchange pack folder with a version tag and transmittal stub 2. Prompt me for: export settings used, scope (views/levels/categories), and coordinate system 3. Generate a validation checklist for the receiving party: geometry, classification, properties, units, and coordinates 4. Open an exchange issues log with fields for reproducible steps, screenshots, and resolution status 5. Draft a consultant message summarizing what changed, what to validate, and next steps Default format: IFC 4.3. Default coordinate basis: shared coordinates.

How It Works

Model exchanges between disciplines are where coordination falls apart.

Someone exports an IFC with the wrong settings, elements go missing, and

nobody can reproduce the problem. This recipe creates a versioned "exchange

pack" for every handoff — documenting what was sent, how it was exported,

and what to validate on the receiving end.

What You Get

  • Versioned exchange pack: folder with a version tag and transmittal stub for every export
  • Export settings record: captures the settings used, scope (views/levels/categories), and coordinate system
  • Validation checklist: geometry, classification, properties, units, and coordinate checks for the receiving party
  • Exchange issues log: structured log with reproducible steps and a screenshots checklist for failures
  • Consultant message draft: what changed, what to watch for, and next steps — ready to send

Setup Steps

  1. Set your default exchange format (e.g., IFC 4.3 or your project standard)
  2. Confirm coordinate basis (shared coordinates, project base point, etc.)
  3. Define what the pack includes: export settings record, scope note, validation checklist, issue log
  4. Connect to email and docs for automatic pack assembly and distribution

Tips

  • The validation checklist is the highest-value piece — it catches problems before they become RFIs
  • Always record the coordinate system used; misaligned coordinates are the #1 IFC headache
  • Version-tag every exchange so you can trace which export introduced a problem
  • Schedule weekly exchanges on the calendar to build the habit before it becomes urgent
Tags:#architecture#interoperability#ifc#openbim#coordination#documentation