Skip to content
KitWren

Search tools

Practical projectsFree BIM course about 240 min

Project: Plan BIM for a small building

Act as information manager for a small community building: set requirements, plan models and exchanges, define coordination, and plan handover — the documents that make BIM work.

By the end of this project you will

  • Write clear information requirements
  • Plan the delivery team's approach in a BEP
  • Design naming, breakdown and coordination
  • Plan verified handover information

Project brief

Objective

Produce a concise BIM information package for a small building: requirements, BEP summary, model breakdown and naming, clash matrix and handover plan.

Skills you need

The brief

A two-storey community centre (hall, kitchen, meeting rooms, offices, plant room). Client: a local council with a small facilities team. Team: architect, structural, mechanical/electrical/hydraulic engineers and a builder. The council wants fewer site errors, reliable quantities for cost checks, and useful handover data.

A cycle: brief and requirements, then discipline models, a federated model, coordination and clash review, documentation, construction, and a handover model for operations.RequirementsDiscipline modelsFederated modelClash reviewDocumentationConstructionHandover modelshared, structuredinformation
Figure: Information flows through a BIM project. Original KitWren diagram.

Step 1 — Requirements

  1. 1Write three OIR/AIR statements for the council.
  2. 2Write an EIR of about ten requirements: uses, software-neutral formats (IFC version), coordinates, naming, LOIN at each stage, exchange cadence, handover format.

Step 2 — BEP summary

  1. 1List models, owners and software.
  2. 2Define origin, survey point, true north, units and level names.
  3. 3Write the naming convention with an example for each model.
  4. 4Set up the CDE states and who approves sharing and publishing.

Step 3 — Coordination

  1. 1Write a clash matrix with tolerances and priorities.
  2. 2Set a fortnightly coordination cycle with deadlines.
  3. 3Define issue statuses and use of BCF.

Step 4 — Handover

  1. 1Choose asset types that need data and the parameters for each.
  2. 2Assign responsibility by stage.
  3. 3Describe how data is checked and tested in the council's FM system.

Deliverables

Hand in (or keep for your portfolio) the following. Each item maps to a checklist line below.

DeliverableFormatWhat it proves
Information requirements (OIR/AIR/EIR)2 pagesThe client's needs are specific and measurable
BEP summary with naming and coordinates2 pagesA team could start modelling from it
Clash matrix and cycle1 pageCoordination is focused and scheduled
Handover data plan1 pageOperations data has owners and checks

Common mistakes

  • Copying a long template BEP unchanged.

    Cut everything that doesn't change what someone does on this project.

  • Vague requirements like 'models to be accurate'.

    Write measurable requirements: formats, tolerances, dates, levels of information.

  • Leaving coordinates for later.

    Define origin, survey point and true north before anyone models.

Your task

Review

  1. Swap packages with someone else (or re-read yours a day later).
  2. Check that a new team member could set up a model correctly from it alone.
  3. Cut anything that doesn't change what someone does.

You should end up with: A short, usable package — typically 4–6 pages.

Completion checklist

0 of 6 checked · saved on this device

Project quiz

1 / 4

What should the EIR avoid, according to ISO 19650's approach?

Finished this project?

Taking the quiz marks it complete too. Your course page picks up where you stopped.

Free KitWren tools that help

Free, independent learning material written for KitWren. We never provide software downloads, licence keys or cracks — use the official sources.