Capstone: A Small Project, Modelled End to End

The project begins not with geometry but with a *question the client must answer*: what do you need, and why? Our client — a public health authority who will own and operate the centre for decades — states their information requirements (the EIR, Module 5): they need a coordinated design, reliable quantities for tendering, and — crucially, because they'll run the building — a clean asset-information handover with the equipment data their facility team will use (Module 8). That last requirement, set *now*, is what makes the whole model worth building; a client who asks only for drawings gets only drawings.

The team responds with a BIM Execution Plan (lesson 10.2), scaled to this modest project — a few sharp pages, not a mega-project tome. It names the roles (lesson 10.1: a small team, so the architect wears the information-manager hat, one engineer covers structure and one covers services, with clear ownership of each part). It sets the standards — naming, classification, the level each element must reach and when (Module 3's LOD, traced to a use — model the clinical rooms and services carefully, the site boundary loosely), and the exchange formats (IFC where the disciplines must share, Module 4). And it establishes the Common Data Environment (Module 5) — the single shared place where information lives and moves through its states from work-in-progress to shared to published. Before a single wall exists, the information has been *defined, planned and given a home*. That front-loading (Module 1) is the whole game: the effort spent here is why the later stages flow.

Now the disciplines build their models — but as information, not drawings (Module 1). The architect's walls, doors and rooms are objects that know what they are (Module 3); the structural engineer's frame and the services engineer's ducts and pipes are likewise data-rich objects, each authored to the agreed level. Each discipline works in its own model, in its own space in the CDE, and every plan, section and schedule they issue is simply a *view* of that model (Module 1) — change the object once, and every view updates, consistently.

Then the crucial move: the models are federated and coordinated (Module 6). The three discipline models are combined and run through clash detection — the classic catch on our little health centre: a large supply duct crossing exactly where a structural beam sits above the treatment room ceiling. On paper, across three separate drawing sets, this collision might have surfaced on site, as expensive rework mid-construction. Here it's caught in the model, weeks early, raised as a tracked issue (the BCF loop, Module 4), and resolved by the engineers before anyone pours concrete. Meanwhile the model does more quiet work: quantities flow out for the tender (Module 2's 5D — reliable because they're counted from the objects, not measured by hand), and simple analysis checks daylight in the wards and the building's basic energy behaviour (Module 6). The model has become what the whole course promised: the coordinated single source of truth from which drawings, quantities and checks all derive — and stay consistent.

The coordinated model now goes to construction (Module 7). The contractor uses it to *plan the sequence* — a simple 4D link of the model to the programme shows the build stage by stage, surfacing a site-logistics clash (materials stacked where the next pour needs access) before it happens. Quantities and payment (5D) run off the model as work proceeds. And where useful, the model reaches the field — setting-out points taken from it, a prefabricated services module built off it (Module 7's DfMA) because the coordination was trustworthy enough to fabricate from. Throughout, the model is kept honest: as things change on site, the information is updated toward an as-built record (Module 7), because a model that stops matching the building stops being useful.

Then the moment the whole thing was really for: handover (Module 8). Because the client asked for it at the very start (the EIR, back in stage one), the team delivers not just a building but an Asset Information Model — the equipment, the finishes, the maintainable components, each carrying the data the facility team needs, in a structured handover (COBie, Module 4). This is the golden thread made real: a requirement stated in the first stage, carried through plan, design, coordination and construction, arriving as usable operational information (Module 5). The health centre's facility manager can now, years later, click the air-handling unit and find its model, its service interval, its supplier — the information that *runs* the building. And honesty to the end: this handed-over model is an asset information model, not a digital twin (Module 8) — a trustworthy static record, the ideal foundation for a twin if the authority ever adds live sensors, but not one yet. That is the whole course, on one small building: information defined, planned, produced, coordinated, built from, handed over, and kept alive — the model becoming, exactly as promised in lesson 1.1, the thing that doesn't stop being useful when the building is finished.