---
name: bep-builder
description: Draft a BIM execution plan (BEP) aligned with ISO 19650-2 from the appointing party's information requirements - project information, roles and responsibilities, model uses tied to project goals, level of information need per milestone (ISO 7817-1), information delivery milestones and the responsibility matrix, CDE workflow and naming, exchange formats (IFC, BCF, IDS, COBie), coordination and QA procedures - flagging every decision that needs the owner. Use when the user prepares a BEP, "plan de ejecución BIM", "PEB", a pre-appointment or post-appointment BEP, a BIM tender response, or needs to answer an EIR/OIR/AIR.
---

# BIM execution plan builder

## Inputs
- The appointing party's exchange information requirements (EIR) and, if available, OIR/PIR/AIR, the project information standard and the information protocol in the contract.
- Team, disciplines, software and versions; schedule milestones; CDE platform (Forma/ACC, Procore, Trimble Connect, another).
- The project's goals (from the owner or `vdc-implementation-plan`).

## Procedure
1. Requirements map: list every requirement in the EIR with its reference, and where the BEP answers it. Unanswered requirements stay visible until the end.
2. Project and team: roles (lead appointed party, task teams, information manager), contacts, responsibilities. Names come from the user.
3. Model uses: select only the uses that serve a goal (coordination, quantities, 4D, FM handover...), with who produces, who consumes, when, and the success measure.
4. Level of information need (ISO 7817-1): per milestone and element group, the geometry, alphanumeric information and documentation needed for each purpose. Express the alphanumeric part as a table that can become an IDS (`loin-to-ids`).
5. Information delivery plan: master information delivery plan (MIDP) and task information delivery plans (TIDPs) by milestone, container and author; responsibility matrix.
6. CDE and naming: workflow states (work in progress, shared, published, archived), status and revision codes, naming convention (checked with `iso19650-naming-check`), approval steps.
7. Exchanges and QA: formats (IFC schema and MVD, BCF for issues, IDS for checks, COBie if required), coordinates and georeferencing, units, model QA before each exchange (`ifc-model-qa`, `ifc-ids-validation`, `ifc-clash-check`), coordination meeting rhythm (`ice-session-planner`).
8. Risks and open decisions: every item that needs the appointing party is listed with the question and date needed.

## Output
- BEP draft in sections (markdown or the user's template), requirements map, LOIN table, MIDP/TIDP skeleton (CSV), open decisions list.

## Never
- Never invent client requirements, codes, names or dates; mark "[to confirm by appointing party]".
- Never claim compliance with ISO 19650; the BEP describes how the team will meet the requirements.
- Never copy text from the standards; reference clause numbers and let the user consult the standard.