Office BIM Workshops · Presenter: Ahmed Fargaly · Recorded session: 10 December 2024 · BBM-STD-33 · V0.2 · 14 October 2026 · WIP training revision; office approval pending
Purpose & scope#
Model the core first, check rooms, then add finishes. Keep this workshop order: poor room boundaries create poor finish results. Finish automation is a production aid after geometry and data checks, not a way to bypass them. This guide covers finish representation, room finish keys, reviewed plug-ins, renovation phases and the checks that make the design base usable.
The author owns room/finish geometry and data; the discipline lead approves material/quantity and demolition intent; the BIM coordinator approves the tool sample and checks coordinated outputs. The appointed exchange authority and recipient authorise and accept the delivered revision. Assign building/envelope/interior ownership without assuming that dividing work prevents every edit conflict.
Standards basis#
- ISO 19650-1:2018 and ISO 19650-2:2018 support agreed information production and controlled exchange. Office Manual BBM-STD-01 V0.1 §§3.2–3.3, 7.2–7.3, 8.2, 9 and 12 and BEP BBM-STD-10 V0.2 §§6.5–6.6, 8.6–8.10 and 10 serve finish/data/QA decisions.
- ISO 19650-4:2022 supports exchange-quality checks and retained evidence. ISO 7817-1:2024 supports purpose-led geometry, properties and documentation: presentation-only finish information is distinct from quantities and procurement requirements.
- ISO 23386:2020 supports controlled property definitions. Autodesk A06/A17 support shared bindings and instance-only key schedules; A20/A21 support material/layer and quantity checks; A14 supports phase status, filters and infill.
- A11/A12 and Penn State BIM Project Execution Planning Guide v2.2 (2019, P02) support reviewed tool provenance, loading and tested infrastructure. Tool commands and phase/category capability must be verified in the approved build.
V0.2 corrections and office choices#
| Recording shortcut | Controlled V0.2 rule / reason |
|---|---|
| One click covers the whole project | Approve a representative sample, scope, expected geometry/data and rollback before any batch (C12) |
| Worksets show/hide stages | Use Phase Created/Phase Demolished plus view/schedule phase filters; worksets organise collaboration/visibility separately |
| Clean walls have no fractions | Check geometry against verified dimensions and project tolerance; fractional measured/sloped geometry is legitimate where justified |
| Core, then finish means add finishes everywhere | Choose compound layers or separate finish objects for each quantity-bearing surface; prevent duplicate reporting |
| Latest drawing plus photo is the final truth | Confirm controlled revision, reliability and source authority; register unresolved survey/design conflicts rather than adopting the last file blindly |
| Concept plans are moved to Published | Apply approved stage graphics and phase scope; CDE state changes only after the relevant exchange decisions (C04) |
Revit construction phases are not RIBA project stages, CDE states or the manual's nine learning phases. Label these separately in metadata and instructions. A phase called Demolition is an office timeline choice; an element's demolished status is derived relative to the view phase.
Finish strategy and property record#
| Surface / output | Chosen representation | Quantity source / exclusions | Required properties and owner |
|---|---|---|---|
| Wall finish | [compound finish layer OR separate finish wall] | [material take-off/layer OR separate object area; exclusions for doors, windows, returns] | FinishCode, material specification, phase; discipline owner |
| Floor finish | [compound layer OR separate finish floor] | [one source; thresholds, voids and room scope] | FloorFinish, thickness/material and room relationship |
| Ceiling finish | [modelled ceiling OR documented appearance/finish code only] | [quantity-bearing geometry or explicit non-geometric requirement] | CeilingFinish, elevation, room scope and required documentation |
| Skirting / base | [linear geometry OR documented length rule] | [one length method with openings/deductions] | BaseFinish, material, height and measurement rule |
| Presentation | [material appearance / graphics] | Appearance-only decisions are excluded from unproved physical quantities | Separate visual approval and quantity/data ownership |
Compound structures have layer material, thickness and function; review joins and opening wrapping (A20). Colour, texture or a room code alone does not establish installed material thickness or a measured take-off. Use purpose-led information need to decide what must be modelled now. Record quantity units, gross/net deduction convention and exclusions; the same finish must not appear in both compound-layer and separate-object totals.
Step-by-step procedure#
- Verify the core baseline. Inspect enclosure, wall location lines, levels, intersections and approved dimensions. Resolve a room leak against the real design: repair the wall/opening or use a justified separation line. Record measured/provisional evidence and outstanding survey dependencies. When linked structure bounds a room, check its room-bounding setting, phase mapping and loaded revision under guide 32.
- Set the finish strategy. Complete the table above by surface and output. Decide whether separate finishes should participate in room bounding; prove the boundary/calculation outcome rather than accidentally shrinking room areas twice. Assign element IDs/room relationships for reconciliation. Define how openings, returns, joins, offsets, reveals and thresholds affect quantities.
- Build the room finish key. Use Rooms category and Schedule keys; choose a controlled key name such as RoomFinishKey. Key schedules use instance parameters (A17). Define Base Finish, Wall Finish, Floor Finish and Ceiling Finish fields in that fixed workshop order; existing built-in fields may be used where they satisfy the required definition. Required shared fields retain their GUID, type/unit, Rooms binding, instance semantics, owner and IFC mapping. Do not create same-name aliases. Test key changes and manual override behaviour on one room; record how an exception is managed without corrupting the controlled key.
- Populate and check rooms. Assign an approved key to every required room, verify the resulting four finish codes in the room properties, itemised schedule and tags where required. Maintain an exception schedule for missing key, invalid code, missing identifier and Not Placed/Unenclosed rooms. A finish tool should not run on failed room records.
- Approve the automation environment. Record provider/download source and licence, exact Revit/pyRevit/extension or graph versions, dependencies and hashes, command purpose, responsible reviewer and allowed scope. Use office-reviewed restricted packages; do not bypass a firewall or trust every file in a shared folder. The BIM/IT owner resolves blocked installation through the supported process. API add-ins use manifests/assemblies; extensions and graphs use their documented loading route. Prove command loading and successful execution in the intended model context; a visible button is insufficient.
- Run a representative sample. Preserve model revision and affected IDs/quantities before execution. Include a rectangular room, a room with a door/window, a corner/column, a linked boundary, a room with a phase change and an invalid enclosure. Choose the approved finish type and height/offset. Generate only the selected valid sample; inspect openings, joins, wrapping, intersections, room bounds and type/material/data assignment. Record expected and actual counts/areas, warnings and every changed/deleted ID. An invalid room must be rejected or skipped with a logged exception, not silently approximated. The author checks output; the coordinator reviews the result before wider use.
- Record rollback and manual fallback. Retain input revision, command/profile, logs, sample diff, reviewer/approval and restore procedure before batching. Stop on unexpected joins, duplicate finishes, changed room areas or lost property data. Isolate the failed result and restore through the file/cloud collaboration procedure, preserving concurrent work; do not blindly replace the central. Native walls/floors/ceilings and manually checked room finish schedules are the critical-task fallback. Retest after tool, dependency, template, phase or profile changes.
- Set construction phases. Agree ordered phases such as Existing and Renovation. Assign each element's Phase Created and, if removed, Phase Demolished. Use demolition status for real removed construction rather than deleting the existing evidence. Correct mistakenly modelled objects through reviewed data correction; demolition is not a substitute for fixing an error. Check rooms/finishes in their phase context and inspect temporary elements created and demolished in the same phase.
- Configure views, schedules and linked phases together. Use the intended phase/filter matrix below. Inspect the actual New/Existing/Demolished/Temporary settings rather than trusting a filter name. A Show Previous + Demolished filter can include retained previous construction as well as demolition; it is not necessarily a demolition-only output. Test a known element of each status, material schedule scope and linked model phase mapping. Workset visibility/open state, crop, section box, discipline/detail level and By Linked View settings remain independent display controls.
- Check demolition and infill. Demolish a test insert in a retained existing host; inspect generated infill, its phase/material/geometry and quantity treatment. Compare new/demolished/retained/temporary totals under the approved deduction rules. Check that a separately generated finish neither covers a new opening nor appears twice through an existing compound layer. Test changes to a host/opening after generation; the tool may not maintain updates automatically.
- Validate building by building. Use the approved source/document register, task allocation and milestone sequence, with generic building codes. Do not adopt the recording's private work order. Envelope/interior owners share an issue when a defect crosses their scope: include screenshot, source revision, affected ID, expected result and responsible role. Review floor/ceiling levels, room data, photos and outstanding assumptions before extracting the schematic/design report.
- Prepare the checked exchange. Apply the approved stage templates, sheet names, scales and dimensions; verify stage graphics separately from construction phase. Retain the exact model, linked revisions, key schedule, quantity report, phase matrix, tool log/profile and checked sheets. Reconcile any issued quantity/schedule to that revision and the agreed receiving format. Author check → coordination Shared review → appointed authorisation and recipient acceptance. Failed mandatory data or quantity checks return to WIP for correction and new-revision resubmission; archive the failed/superseded decision evidence.
Room, finish-source and construction-phase checks precede bulk generation and formal issue.
Controlled room finish key — fill-in template#
| Key / revision | Space use | Base Finish | Wall Finish | Floor Finish | Ceiling Finish | Owner / approved exception |
|---|---|---|---|---|---|---|
| FK-01 / [rev] | Dry work space | BF-01 | WF-01 | FF-01 | CF-01 | [role / decision] |
| FK-02 / [rev] | Circulation | BF-02 | WF-02 | FF-02 | CF-02 | [role / decision] |
Codes are synthetic office-style examples, not specifications or classification assignments. The data dictionary supplies allowed values, definitions, shared GUID where applicable, binding, units and exchange mapping. The discipline lead supplies approved materials/specification references. Change one key and check every linked instance; switching a type parameter is not an equivalent room key operation.
Phase and display acceptance matrix#
| Output intention | View / schedule phase | Required included status | Explicit exclusions / test |
|---|---|---|---|
| Existing survey baseline | Existing | Construction present at Existing | No future new work; verify baseline and room totals |
| Demolition information | Renovation | Demolished plus any explicitly approved context | Retained context is visually distinguished; new excluded from demolition quantity total |
| New construction | Renovation | New | Retained/demolished excluded from new quantity total; temporary handled separately |
| Completed renovation | Renovation | Existing retained + New | Demolished and temporary excluded from completed total |
| QA diagnostic | Chosen phase with explicit all-status display | Known samples of each status | Use for diagnosis only; not an issue filter without approval |
Record actual filter cells, graphic overrides, schedule/category capability and linked phase mapping in the accepted configuration. Default filter names can be edited; test results establish the configuration. When a link appears cut/partial, inspect phase mapping/filter, link workset open state, section box/crop, visibility/detail/discipline, linked-view choice and loaded revision. Do not fix a phase error by switching off a workset or accepting a misleading Show All view.
Worked exercise — retained, demolished and new finishes#
Use two synthetic rooms with fixed approved net floor extents: R01 = 12.00 m² and R02 = 20.00 m². Create separate finish floors so the test has one quantity-bearing source per surface. In Existing, both existing finish floors total 32.00 m². In Renovation retain R01's 12.00 m², demolish R02's 20.00 m² and add a new 20.00 m² floor for R02.
Expected Renovation reports: retained = 12.00 m²; demolished = 20.00 m²; new = 20.00 m²; completed retained + new = 32.00 m². Adding all status reports gives 52.00 m² and is wrong as a completed floor total. Add an intentional duplicate separate finish over a compound finish layer: the exception/diff must identify two representations of one intended finish and require correction before issue.
Test one 4.000 × 3.000 m wall face with a 1.000 × 2.000 m opening: agreed simple net face area = 10.00 m² before any reveals/returns. Revit/tool quantities must be interpreted against the chosen measurement rule; a difference is investigated, not forced to this number by changing an unrelated field. Demolish an insert in a retained host and document infill/display/quantity effects. Repeat after a linked phase change. Submit minuscule-sample and batch-scope logs, key/phase schedule, quantity reconciliation, plan/section and reviewer decision. Only correct quantities, visible status and retained evidence pass.
Acceptance criteria / self-check list#
- Core geometry, room enclosure/IDs, level, phase and linked bounds are checked before finish generation.
- Each physical surface has one quantity source; compound/separate duplication and appearance-only treatment are explicit.
- Room finish keys use instance fields; required shared identities/bindings and resulting codes are verified.
- Tool provider/licence, exact builds/dependencies, reviewed source/trust/loading and operational sample are recorded.
- Sample checks openings, joins, room area effects, materials/quantities and invalid rooms; reviewer approves before batch.
- Logs, expected/actual diff, preserved baseline, restore responsibility and native fallback exist.
- Created/demolished status, filters, room/schedule scope and linked phase mapping pass known-object tests.
- Demolition/infill, retained/new/temporary quantities and host-change results are independently inspected.
- Sheets/schedules/received quantities reconcile to the retained model revision; formal issue and browser status are separate.
Common mistakes#
- Generating every room before the linked boundaries or finish keys are validated.
- Counting a finish layer in the compound host and a second separate finish object.
- Treating room codes, render appearance and quantity-bearing model layers as interchangeable.
- Using worksets to hide demolished elements instead of assigning demolished status.
- Assuming Show Previous + Demolished is a demolition-only quantity report.
- Bypassing tool trust/loading problems or restoring an old central over concurrent edits.
Related guides#
- 22: collaboration/recovery; 28: sheet templates and graphics; 30: levels/coordinates and tool baseline.
- 31: daily scoped changes and logs; 32: room/measurement/linked-boundary checks.
- 35: approved external content; 36: key schedules, complete/exception views and receiving reconciliation.
Editorial coverage record#
R11.1–R11.5: strategy table, appearance distinction, construction-phase matrix, instance key procedure and quantity/infill exercise. R09.1–R09.5: procedure 5–7 covers inventory, source/trust, loading, logged sample/rollback, output owner and native fallback. C04/C09/C10/C12/C17/C19 addressed through defined source/data/phase/exchange controls. P1 1/1 and P2 1/1 fixed; P3 demolition/new-finish exercise included. No exercise or installed-tool result is claimed before office assessment.
References#
Source IDs refer to the supplied RESEARCH.md register. Autodesk Help describes the listed release; verify commands in the project-approved build. Public ISO abstracts establish scope and edition, not clause-level compliance.
- S01 — ISO 19650-1 — Concepts and principles. ISO, 2018, ed.1. https://www.iso.org/standard/68078.html?browse=tc
- S02 — ISO 19650-2 — Delivery phase of the assets. ISO, 2018, ed.1. https://www.iso.org/fr/standard/68080.html
- S04 — ISO 19650-4 — Information exchange. ISO, 2022, ed.1. https://www.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/82/78246.html?browse=tc
- S07 — ISO 7817-1 — Level of information need: concepts and principles. ISO, 2024, ed.1. https://www.iso.org/standard/82914.html?browse=tc
- S16 — ISO 23386 — Methodology to describe, author and maintain properties in interconnected data dictionaries. ISO, 2020, ed.1. https://www.iso.org/standard/75401.html?browse=tc
- A06 — Create Shared Project Parameters. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Model/files/GUID-114C68A9-FF2B-4D4C-A2DF-3AE7E1F174C8.htm
- A17 — Key Schedules; Create a Key Schedule. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-CD22DA24-4162-4AB2-B1D3-02CEBE918444.htm; https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-75B3B9C4-6899-4DC9-8424-DFC901701B48.htm
- A20 — Compound Structure. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Model/files/GUID-08E47F82-BFA1-4CAB-B2EA-6C8DC9049AD8.htm
- A21 — Schedules; About Schedules. Autodesk Revit Help, 2026 / 2024. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-F50D6FF4-859E-43A2-A2F6-81C84A1BA0EB.htm; https://help.autodesk.com/cloudhelp/2024/ENU/Revit-DocumentPresent/files/GUID-73090B70-8A13-4E12-909C-F25D724D5BA7.htm
- A14 — Project Phasing. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-2E104AB8-68B9-46F2-9BE2-B54E767429E5.htm
- A11 — About Graph Security and Trusted Folders. Autodesk Dynamo Player Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/RevitDynamo/files/Dynamo_Player/RevitDynamo_Dynamo_Player_About_Graph_Security_and_Trusted_Folders_html.html
- A12 — Add-in Registration. Autodesk Revit API Developer's Guide, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-API/files/Revit_API_Developers_Guide/Introduction/Add_In_Integration/Revit_API_Revit_API_Developers_Guide_Introduction_Add_In_Integration_Add_in_Registration_html.html
- P02 — Define Supporting Infrastructure for BIM Implementation. Penn State, v2.2, 2019. https://psu.pb.unizin.org/bimprojectexecutionplanningv2x2/chapter/define-supporting-infrastructure-for-bim-implementation/
- G-C — Guidance C — Facilitating the CDE workflow and technical solutions. UK BIM Framework, ed.1, September 2020. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf