科研 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.
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
UNKNOWNand 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-coordinationor 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执行计划和信息交付要求。
所属插件
安装该插件会一并获得同领域的 44 个 Skill / MCP。
同插件的其他科研 Skill
- 建筑图纸矢量生成Produces coordinated architectural drawings (plans, sections, elevations, SVG/DXF) from structured specs with layer and standard checks. Use when drafting or generating drawing sets.
- 建筑项目全流程协调Coordinates end-to-end AEC work across briefing, design, BIM/CAD production, and handover by routing to specialist skills. Use for ambiguous or multi-discipline AEC tasks.
- 建筑任务书空间排布Converts briefs into traceable room programs, area schedules, adjacency logic, and requirement matrices. Use for space planning, briefing, or program validation.
- 建筑成果红队复核Independently challenges an architecture deliverable for hidden assumptions, coordination gaps, and unsupported claims before submission. Use for final adversarial review before issue.
- 建筑面积工程量核算Calculates and audits architectural areas, room schedules, quantities, and takeoffs with explicit units and measurement basis. Use for quantity reconciliation and takeoff sanity checks.
- AutoCAD DWG制图工作流Plans and reviews safe AutoCAD DWG workflows: layers, blocks, xrefs, layouts, plotting, and AutoLISP/.NET automation. Use for AutoCAD-specific drafting and DWG package preparation.
- 建筑围护结构性能设计Develops and reviews facade, roof, and foundation envelope strategies for thermal, water, air, and acoustic performance. Use for assembly design, condensation risk, and envelope QA.
- CAD/BIM自动化工作流Plans safe, least-destructive automation of CAD/BIM workflows such as batch edits and model-data extraction across Revit, IFC, DWG, and DXF. Use for repetitive model or document tasks.
- 建筑场地土木协调Coordinates architecture with civil/site engineering: grading, earthworks, access, drainage, utilities, and Civil 3D workflows. Use for site grading concepts and civil-architectural handoff.
- 建筑概念方案评审Critiques architectural concepts and compares design options against stated project goals across program, site, climate, and constructability. Use for design critique or option comparison.
- 建筑概念与方案设计Generates and develops concept and schematic design options (parti, massing, blocking, circulation, floor plans) from a validated brief. Use for early design option generation and comparison.
- 施工阶段行政管理支持Supports construction-phase administration: RFIs, submittals, site observations, change tracking, and punch lists. Use during tender clarification, construction, and closeout.
- 施工图文件集编制Develops and coordinates construction-document sets including sheet registers, schedules, details, and issue packages. Use for technical design production and permit or tender drawing sets.
- 土木项目成本管理Manages civil-engineering project budgets: contract sum, variation log, forecast final account, cashflow, and invoice register. Use for cost events such as variations, invoices, or budget review.
- 建筑造价与价值工程Supports architectural cost planning, option comparison, and value engineering using traceable quantities and cost sources. Use for early cost plans, budget reconciliation, and VE workshops.
- 项目文件发布核查Audits live civil-engineering project documents after a milestone to flag drift between proposed, contracted, and delivered work. Use after report issue or scope change to update project records.
- 建筑图纸质量检查QA checks architectural drawing sets for cross-sheet coordination, annotation, dimension, and revision issues. Use for reviewing PDFs, exported drawings, or issue sets before release.
- 岩土勘察与地基评估Plans and interprets geotechnical site investigations for foundation design: desk study, borehole/CPT interpretation, and bearing capacity checks. Use before foundation or earthworks design.
- 竣工移交与运维协调Coordinates architectural handover, O&M manuals, asset data, defects, and post-occupancy evaluation. Use from practical completion through building operation and facilities handoff.
- 历史建筑保护评估Researches heritage significance, listing status, and conservation constraints for existing buildings, and structures conservation-led options. Use for listed or historic buildings.
- 土木项目安全环保管理Manages civil-engineering health, safety, and environment: safety plans, incident register, method statement review, and statutory reporting. Use for any HSE incident, near-miss, or safety review.
- 室内装修布局设计Develops interior and fit-out layouts, furniture zoning, RCP concepts, finish strategies, and fit-out documentation. Use for workplace, residential, retail, or hospitality interior projects.
- 结构与无损检测根因调查Runs a systematic root-cause investigation protocol for structural and NDT findings before any remediation is proposed. Use when a defect, anomaly, or unexplained inspection finding is reported.
- 建筑生命安全与无障碍设计Coordinates life-safety and accessibility design using jurisdiction-specific requirements: egress, fire compartmentation, and accessible routes. Use for code-review matrices and egress studies.
常见问题
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 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。