科研 Skill

openBIM IFC协同工作流

openbim-ifc-coordination

Plans and reviews openBIM interoperability using IFC, BCF, IDS, and IfcOpenShell/Bonsai workflows. Use for IFC export/import, model audit, and cross-platform BIM coordination.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

openBIM / IFC Coordination

Treat IFC as structured building data, not just geometry. Preserve GUIDs, schema/version, units, spatial containment, classifications, properties and issue traceability.

Preflight

  • IFC schema/MVD or exchange target, authoring tool/version, coordinate strategy, model purpose, information requirements and receiving software.
  • Federation disciplines, file/revision IDs, BCF/issue workflow, classification/property requirements and IDS when available.

Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.

Workflow

  1. Inventory project/site/building/storey/space structure, element counts, GUID stability, units, coordinates and schema.
  2. Validate required classes/properties/classifications/materials/quantities against project requirements or IDS; remember IDS checks alphanumeric information, not geometry.
  3. Federate and clash/issue-coordinate with BCF-style identifiers rather than screenshots alone; preserve issue status and viewpoints.
  4. Round-trip sample exchanges before full delivery; compare element counts, GUIDs, property sets, geometry extents and quantities.

Deliverables

  • IFC exchange/validation plan
  • Information requirement or IDS mapping
  • Federation/BCF issue register
  • Round-trip verification report

Verification

  • Schema, units, coordinates, GUIDs and spatial hierarchy are explicit and checked.
  • Export success is not treated as interoperability success until the receiving workflow is tested.

For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.

Professional boundaries

  • Do not invent IFC property requirements or claim IDS validates geometry.
  • Third-party BIM/MCP tools are optional and must be reviewed before granting write access.

If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.

If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.

Optional Gridline source-bound IFC4 exchange

Discover the installed architectural-drawing-generation skill before invoking its own scripts/component_ifc.py; report a missing dependency rather than inventing a path. The bounded exporter requires IfcOpenShell 0.9.0.post1 plus pytest for actual EXPRESS validation, a selected signed state database, explicit matching project requirements and separately trusted native receipt/owner-key pins. It checks typed source/units/spatial/room/material/quantity/host/void/filling data, raw and independently evaluated geometry, and stable source mappings. Public --verify additionally requires the retained IFC receipt pin and preserves published bytes. Read its command help, optional requirements and source/licensing boundaries first; no dependency is automatically installed.

Use an owner-selected persistent globally unique project identity. The accepted synthetic fixture and its minimal provenance requirements are not a client's IDS, certified MVD or regulatory brief. Unsupported requirements, unknown mandatory materials or missing source approvals block export. Report the actual checked scope and all receiving-client/IDS/professional gaps. IFC maps material identities; packed photographic PBR remains in Blender/GLB. This file-only pipeline grants no live-host edit permissions and does not close every #13/#15 interoperability or transaction criterion.

示例提示词

帮我检查一下这个IFC模型导出的空间结构和属性集是否完整。

所属插件

建筑学与土木工程面向建筑与土木研究和设计:场地分析与方案设计、Revit/AutoCAD/Rhino-Grasshopper 与 OpenBIM-IFC、机电与结构协调、消防与无障碍、围护结构与日照能耗、造价与工程量,以及土木工程项目的进度、质量、安全、风险与 RFI 管理。

安装该插件会一并获得同领域的 44 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

openBIM IFC协同工作流能做什么?

Plans and reviews openBIM interoperability using IFC, BCF, IDS, and IfcOpenShell/Bonsai workflows. Use for IFC export/import, model audit, and cross-platform BIM coordination。

如何安装openBIM IFC协同工作流?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「openBIM IFC协同工作流」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

openBIM IFC协同工作流需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

openBIM IFC协同工作流经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。