科研 Skill

BIM执行计划编制

bim-execution-plan

Drafts and reviews ISO 19650 BIM Execution Plans and Exchange Information Requirements: roles, CDE workflow, LOIN, and federation strategy. Use before modeling starts on a BIM-delivered project.

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

SKILL.md

BIM Execution Plan (BEP / ISO 19650 Delivery Strategy)

Define how information will be produced, managed, and exchanged on a project before modeling work starts, so model federation, data exchange, and responsibility are agreed rather than discovered mid-project. This complements openbim-ifc-coordination (exchange mechanics) and cad-bim-automation (tool-level automation) by covering the upstream planning document those workflows execute against.

Prerequisites

  • A defined project scope, delivery team structure (appointing party, lead appointed party, task teams), and project stage (concept, pre-contract, post-contract).
  • The appointing party's Exchange Information Requirements (EIR) or equivalent client information requirements, if already issued. If not yet issued, this skill can help structure a response that assumes a requirements-gathering step still needs to happen with the client.
  • Familiarity with the project's intended authoring tools and the openBIM/IFC or proprietary exchange format in use.

Preflight

Record before drafting:

  • Information management framework in use: ISO 19650-1/-2 (or -3 for operational phase) is assumed as the default reference framework here; note explicitly if the project instead follows a different national annex, a proprietary client standard, or a legacy framework (e.g. PAS 1192-2 transitional projects), since terminology and some obligations differ.
  • Appointing party's purposes for information (design coordination, cost planning, programme sequencing, asset/FM handover) — the BEP should be scoped to serve these, not produced as a generic template.
  • Task team structure: who models what, in which native tool, and which discipline owns which federated volume or zone.
  • Common Data Environment (CDE) platform already selected, or still to be agreed.

Leave unresolved items as UNKNOWN rather than assuming a default CDE, tool set, or naming convention — these must be confirmed with the appointing party and lead appointed party.

Workflow

1. Confirm/structure the Exchange Information Requirements (EIR)

If the EIR does not yet exist in usable form, structure one covering, at minimum:

  • Purpose of information at each project stage (what decisions the information must support).
  • Required file formats for exchange (native + a neutral format such as IFC). State explicitly whether native-format exchange or IFC-only exchange is required, since this affects tool choice and federation strategy.
  • Level of Information Need (LOIN) per ISO 19650-1, replacing the older LOD (Level of Development) terminology where the project framework has moved to it — note which terminology the actual project documents use, since both remain common in practice.
  • Classification system required (Uniclass, OmniClass, or a project-specific system) and where it must be applied (object properties, sheet naming, cost breakdown structure).
  • Security/CDE requirements: access control, revision/status workflow (WIP, Shared, Published, Archive), and any ISO 19650-5 security-sensitive information considerations if the project has security sensitivities.

2. Draft the BIM Execution Plan response

Structure the BEP to answer the EIR, covering:

  • Delivery team organisation: task team breakdown, named information manager role(s), and the responsibility matrix (who authors, who checks, who approves each information container/model).
  • High-level responsibility matrix: by discipline and project stage, mapped to federation strategy (which discipline's model/volume federates with which).
  • CDE workflow: the WIP → Shared → Published → Archive status flow, naming convention for containers (following ISO 19650's recommended structure: project–originator–volume/level–type–role–number, or the project's own confirmed convention), and approval gates between states.
  • LOIN/LOD schedule: by element type and project stage, stating geometric detail and attached data requirements — do not invent numeric LOD values without the EIR or client standard specifying them; flag as UNKNOWN and a question for the appointing party if absent.
  • Federation strategy: coordinate system/survey datum agreement, model splitting strategy (by level, zone, or discipline), and the frequency and method of clash detection/coordination (tool, pass/fail criteria, issue tracking via BCF).
  • Software and hardware: named authoring tools, version policy, and the interoperability/exchange chain between them.
  • Quality assurance: model validation checks before each Shared-state submission (naming compliance, coordinate check, clash status, data completeness against LOIN).

3. Review an existing BEP for gaps

When reviewing rather than drafting:

  • Check the BEP answers every clause of the EIR; flag any EIR requirement with no corresponding BEP response as a gap.
  • Check the responsibility matrix has no orphaned scope (an element type with no assigned task team) and no unresolved federation conflicts (two teams claiming the same volume).
  • Check the naming convention and classification system are fully specified with examples, not left as "to be agreed" this late in the process.
  • Check LOIN/LOD values are stated per project stage and element type, not as a single blanket value for the whole project (different elements legitimately need different detail at the same stage).
  • Check the CDE workflow defines who can promote a container from WIP to Shared, and what the approval record looks like.

4. Master Information Delivery Plan (MIDP) / Task Information Delivery Plans (TIDP)

  • Confirm each task team's TIDP lists what containers they will deliver, in what format, by when, aligned to project milestones.
  • Confirm the MIDP aggregates all TIDPs into a single delivery schedule tied to the programme — flag any task team whose TIDP milestones don't reconcile with the overall programme.

Deliverables

  • EIR structure/response checklist
  • Draft or reviewed BIM Execution Plan document
  • Responsibility matrix (discipline × stage × information container)
  • CDE naming convention and status-workflow definition
  • LOIN/LOD schedule by element type and stage
  • MIDP/TIDP alignment check

Verification

  • Every LOIN/LOD, classification, and naming requirement in the BEP traces back to either the EIR or an explicit, recorded client decision — not an invented default.
  • The responsibility matrix has no gaps (unassigned scope) or unresolved overlaps (two teams assigned the same deliverable without a stated split).
  • Terminology used (LOD vs. LOIN, PAS 1192 vs. ISO 19650 vocabulary) matches what the actual project documents and contract use, stated explicitly if mixed.

Professional boundaries

  • A BEP produced or reviewed here is a coordination and planning document; it does not itself grant or withhold contractual information-delivery obligations, which depend on the appointment/contract wording.
  • Do not assert ISO 19650 "compliance" as a certified outcome; state that the document is structured to the standard's recommended content, and that formal compliance assessment (if required, e.g. for a certification scheme) is a separate process.
  • Security-sensitive information handling (ISO 19650-5) requires specialist security-minded appointment advice beyond this skill's scope if the project is flagged as security-sensitive.

Limitations

  • This skill assumes ISO 19650 as the default reference framework; projects governed by a different national or proprietary framework need their own terminology substituted throughout, not just a label change.
  • Does not perform actual clash detection, model federation, or IFC validation — route that execution work to openbim-ifc-coordination or the project's native BIM coordination tool once the BEP defines the process to follow.
  • LOIN/LOD numeric schedules and classification mappings must come from the client's EIR or an agreed project standard; this skill cannot invent defensible values where none has been specified.

示例提示词

帮我按ISO 19650起草这个项目的BIM执行计划和信息交付要求。

所属插件

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

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

同插件的其他科研 Skill

常见问题

BIM执行计划编制能做什么?

Drafts and reviews ISO 19650 BIM Execution Plans and Exchange Information Requirements: roles, CDE workflow, LOIN, and federation strategy. Use before modeling starts on a BIM-delivered project。

如何安装BIM执行计划编制?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「BIM执行计划编制」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

BIM执行计划编制需要哪些权限?

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

BIM执行计划编制经过官方审核吗?

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