BIM
execution
plan.
The client says what information it needs. The BEP says how, by whom and when it will be produced.
“I want it in BIM” is not a requirement.
If nobody writes down what information is needed, each team understands something different and the delivery is useless for what the client needed.
From strategy to data.
Requirements cascade down: from what the organisation needs to know about its assets to what each appointment must deliver.
Who asks and who answers.
The appointing party appoints a lead appointed party, which coordinates its appointed parties. Together they form the delivery team.
The BEP answers the EIR.
The EIR says what information the client wants. The BEP explains how the team will produce it, with what resources and under which standards.
Seven minimum sections.
The standard sets what the BEP submitted with the tender response must include. The rest is form: neither page count nor logos make it better.
Who produces what.
Each deliverable, crossed with the team that produces it. In the tender response it is high level; after the appointment, it is detailed down to the information container.
Each team, its own plan.
Each task team writes its TIDP: which information containers it delivers and when. The lead appointed party combines them into a single MIDP.
Information arrives when a decision is due.
Milestones are set where the client needs data to make a decision, not when the team finishes modelling.
No more, no less.
For each milestone and purpose, you set how much geometry, which data and which documents. Excess costs as much as gaps.
Four states per container.
Every file moves from work in progress to shared, published and archived. Each step has a check and someone who signs it off.
Updated, not filed away.
The BEP is offered, confirmed at appointment and revised whenever something that affects the information changes: a stage, a team, a program.
Specific, named and checkable.
A BEP copied from another project shows: it speaks in generalities. A useful one answers each requirement with a person, a date and a way to check it.
- “BIM software will be used”
- “The team will coordinate the models”
- “The standard will be followed”
- Program, version and format per team
- Weekly federation, named person in charge
- IFC4 validated against the EIR’s IDS
Six parts, one language.
Concepts, delivery phase, operational phase, exchange, security, and health and safety. In Spain they are published as UNE-EN ISO 19650.
Eight activities, two BEPs.
Part 2 organises each appointment into eight activities. The BEP appears in the tender response and is confirmed at appointment.
Born British, made ISO.
The BEP and the EIR come from UK standards and moved into ISO in 2018. The revision under way could change their names.
A name that explains itself.
The UK annex proposes field-based names and a status code for every file. It is the model many CDEs and tender documents copy.
The Plan BIM sets dates.
The Spanish State requires a BIM level according to contract value. From October 2025, Intermediate level for works above the EU threshold.
Other guides, same idea.
The United States, Singapore and Peru have their own BEP guides. Names and order change; the question-and-answer structure stays.
Every decision ends up as a setting.
Template, properties, names, coordinates and export: what the BEP decides is configured once in each program and shared with the team.
From template to data.
Almost all are written in text templates and spreadsheets. Some platforms turn them into data linked to the checks.
The platform enforces the BEP.
A well-configured CDE sets aside non-compliant names, assigns status codes and blocks publishing without approval.
From S0 to A1, signed off.
Every status change is a workflow: who reviews, who approves and which folder the file moves to. The BEP says it; the platform runs it.
Open formats, in the contract.
The EIR sets the format for each deliverable and the BEP says which program and settings produce it. Spain’s Plan BIM requires IFC and BCF.
The machine-readable EIR.
With IDS, the part of the EIR that asks for data is written in XML that any checker reads the same way. The BEP says who runs it and when.
FireRating required
Five questions per delivery.
Before sharing or publishing, every container answers: what it is called, what state it is in, what data it carries, whether it coordinates and whether it is in the right place.
Each check, its tool.
The CDE polices the names; an IDS, the data; a federated viewer, the coordination. The BEP says which one is used and who signs the report.
The BEP itself is reviewed too.
Before the appointment, the client scores the pre-appointment BEP: whether it answers every requirement and whether the team has the real capacity to deliver it.