Office BIM Workshops · Presenter: Ahmed Fargaly · Recorded session: 21 November 2024 · BBM-STD-31 · V0.2 · 14 October 2026 · WIP training revision; office approval pending
Purpose & scope#
Keep the daily workshop habits: organise site photos so modellers can follow them, show progress openly, balance work across assigned buildings, and use small tools to remove repetitive effort. This guide turns those habits into controlled information production. It covers progress reporting, discrepancy decisions, selective standards transfer, numbering/data edits and export checks. It does not approve a plug-in merely because it appears in a recording or shared installation folder.
The author owns the changed data; the discipline lead resolves design questions; the coordinate owner resolves site/grid reference questions; the BIM coordinator reviews bulk changes and exchange evidence. The appointed delivery authority and recipient make authorisation and acceptance decisions separately.
Standards basis#
- ISO 19650-1:2018 and ISO 19650-2:2018 support planned production and controlled information delivery. Office Manual BBM-STD-01 V0.1 §§2.1, 7.2–7.3, 9 and 12 and BEP BBM-STD-10 V0.2 §§5, 6, 8.6, 9–10 supply project workflow/data controls.
- ISO 19650-4:2022 supports exchange checks and evidence. UK BIM Framework Guidance C, edition 1 (2020), distinguishes WIP, Shared, Published and Archive transitions; folder names and Revit sync are not those decisions.
- ISO 29481-1:2025 and ISO 29481-2:2025 support explicit use cases, actors, timing and interactions. RIBA Plan of Work 2020 supplies stage context; ISO 19650-3:2020 adds operational trigger exchanges where appointed.
- ISO 23386:2020 supports controlled property identity; shared GUID, category binding and type/instance semantics must survive a data-management tool.
- Autodesk A11/A12 describe trust and loading; A06/A17/A21/A14 describe shared bindings, instance keys, schedules and phases. The exact adopted tool/release determines available commands.
Corrections retained in the working method#
| Original claim / shortcut | Controlled instruction and reason |
|---|---|
| Transfer Project Standards necessarily overwrites everything | Autodesk permits selection. The office default remains no uncontrolled inter-project transfer; the BIM coordinator may approve selected standards after comparison/testing (C17/C19). Do not check every item blindly |
| Deleting a room tag unplaces a room | The tag is annotation; deleting it leaves the room placed. Selecting/deleting the room in plan unplaces it and retains its record. Permanent schedule deletion is a separate operation, with data loss (C19) |
| Adjust architecture to structure because discrepancies are small | Record both source revisions and the discrepancy. Obtain an approved design/survey disposition; structural grids are adopted only where the approved responsibility/design basis says so |
| All named tools are free or support the listed exports | Recorded names are examples. Verify licence, exact provider/build, dependencies and the specific format/profile before use (C12) |
| Parameter manager can clean or replace everything | Required GUIDs, bindings, classifications and exchange mappings are controlled. Deletion/conversion needs impact review and before/after testing (C09) |
Supplementary correction evidence: Autodesk, Transfer Project Standards, Revit 2025 (selected transfer and duplicate handling); About Rooms and Room Tags, Revit 2025 (tag/room separation). These verify the X06/X08 corrections identified in GAPS.md.
Step-by-step procedure#
- File the evidence before modelling. Use building → floor → block → part. Put a key plan and the photographer's walking route beside each sequence. The visit register links the authorised photos, plans and verified location reference. Record capture date, source, view direction and limits; restrict site photos to authorised project access. Photographs may support provisional elevations but do not establish measured dimensions or survey accuracy. List the next visit's required checks.
- Report progress daily during mobilisation. Share a short screen review: completed objects/outputs and source revisions, next actions, blockers and requests. If absent, post the same structured record to the approved channel. Keep the workshop's weekly review after initial mobilisation where the team agrees it. Close the progress report the day before the recipient's meeting; show unfinished or rejected work accurately. Allocate buildings to keep milestone readiness balanced.
- Resolve discrepancies before realignment. Log measured difference, affected element IDs/views, drawing/model revisions, survey evidence and impact on outputs. Architecture and structure have design owners; neither wins merely because it is structural or close to a grid. Record the designer/coordinate-owner decision and permitted change. Check dependent hosts, levels, room boundaries, linked alignment, dimensions and quantities after the correction.
- Take a pre-edit snapshot. Save the controlled model revision and selected IDs; export the affected itemised audit schedule. Record relevant Project Information, units, coordinates, property bindings, types and counts. Use a controlled copy for representative tests, with a recovery route appropriate to file/cloud collaboration. A backup without a tested restore procedure is incomplete.
- Reuse standards selectively. Prefer approved template/library content. If a system type is reused by copying a representative element, inspect dependent materials, patterns, host constraints and type-name conflicts; copying is also an admission operation. For Transfer Project Standards, record the source, target, selected standards and duplicate decision. Choose only approved items; compare before/after values. Reject any unexplained coordinate, unit, Project Information, material or property change. Do not use an inter-project transfer to repair a whole model without a specific plan. Loadable families go through guide 35 before entering the approved library.
- Approve the tool and profile. Complete the inventory below. Use reviewed source packages from restricted folders. A Dynamo trusted folder permits graph execution; it is not a guarantee of safety. API add-ins use.addin manifests and release-specific assembly/loading paths; record these where applicable. Distinguish API, extension and graph loading routes. Verify the command loads and operates in the intended document/user context; retain warnings. Installation alone is not operational acceptance.
- Test one small edit. Set scope explicitly: selection, active view or whole model. Capture IDs and values before a renumbering, workset transfer or parameter update. Review the expected result in plan, tag and itemised schedule. Refresh/reopen a tool when new elements are missing, and prove the new selection count. A crossing-line selection is not proof of numbering order. Check constraints, borrowed elements and workset meaning; a workset is not an access-control or project-phase mechanism.
- Run the approved batch only after sample acceptance. Retain command inputs, selection, tool/profile version, result/error log and before/after diff. For parameter imports, match stable element keys and controlled shared property GUIDs rather than spreadsheet row positions. Reject unmatched/duplicate keys, type-instance conversions without approval, missing units and unintended overwrites. The author reviews data; the coordinator independently checks mandatory outputs before sharing. On failure stop further batches and restore via the agreed recovery procedure, preserving concurrent work and failed evidence. Use native numbering, filters, schedules and print/export commands as the manual fallback.
- Check exports in the receiving application. Use an approved output profile with naming tokens, sheet/view scope, units, phase, format and revision. Print representative pages first: paper size, intended scale/zoom, colour/line policy, raster/vector suitability, crop, title and sheet identity. A saved XML profile is versioned configuration; record its hash/revision and do not assume the recording's format list or dependencies are supported. Record any required exporter/licence/runtime and test it. A 3D visualisation/direct-link workflow also requires version, licence, privacy and geometry checks; it is not an information-acceptance decision.
- Reconcile and route the package. Count itemised records, compare stable keys and required fields, recompute totals, inspect known phase/filter scope and retain the exact source revision. The checker records failures/corrective actions. Share the checked package for coordination, then obtain appointed authorisation/acceptance for the exchange. Record rejection with issue ID, owner and due date; correct in WIP and resubmit a new revision. Retain prior packages and decisions in Archive.
Evidence, scoped changes and model-to-receiver reconciliation support the daily review loop.
Fill-in progress and tool registers#
| Review date / stage | Author / building | Done: output + revision + check evidence | Next + due date | Blocker / decision owner / issue ID |
|---|---|---|---|---|
| [fill] | [role / B01] | [not just percentage modelled] | [fill] | [fill] |
| Tool field | Required entry |
|---|---|
| Identity and rights | Tool, provider/source URL, licence evidence/date, purpose and approval owner |
| Tested environment | Revit/tool/graph/package/runtime builds; dependency list; selected export support |
| Trust and availability | Reviewed package/hash; restricted trusted source; manifest/assembly or extension route; successful load/command test |
| Run definition | Model revision, profile revision, user/date, selection IDs/count, proposed changed fields |
| Expected / actual result | Tag/schedule/geometry and export differences; warnings; accepted result and reviewer |
| Recovery | Restore baseline and responsible role, retained logs, manual fallback, retest trigger/expiry |
The recorded pyRevit tab-colouring, DiRoots numbering/filter/parameter/sheet/export commands and BIM Align operations remain examples of useful functions. Confirm their names and capabilities in the installed approved versions. Do not install during live editing; use the office-approved installation/restart procedure and preserve work. Point-cloud tools require a verified scan/control baseline. Twinmotion/Datasmith rights and connection support must be verified for the proposed environment; no licence mode here is assumed to work.
Room action decision table#
| Intended result | Select / action | Expected model data | Required check |
|---|---|---|---|
| Remove one annotation | Select room tag, delete | Room remains placed with its number/name/area | Room schedule unchanged; retag if needed |
| Move the room record elsewhere | Select room element, unplace then place existing record | Retained number/name/data; Not Placed until re-placed | Identify element, phase and destination; ensure no duplicate |
| Permanently remove an obsolete record | Review selected room in an itemised schedule, then delete with approval | Room record is removed; related annotation/data affected | Retained pre-edit snapshot and brief/finish/asset impact review |
Do not infer the selected object from how the screen looks: inspect category/ID. Grouped schedule rows can represent several rooms; ungroup and review before destructive operations. If the intended result is only a tidier drawing, permanent deletion is the wrong action.
Known-data renumber and receiving test#
Define a Room schedule: purpose = audit; phase = the exercise's New phase; units = m²; fields = stable room key, Number, Name, Level, Area and FinishKey; itemise every instance. The shared property dictionary records GUID, Rooms category binding and instance/type semantics; a room finish key uses compatible instance fields. Retain a separate exception schedule for blank/duplicate numbers, missing keys and Not Placed/Unenclosed records; do not hide failures from the only QA view.
| Stable key | Before number | Known area m² | Approved after number | Phase |
|---|---|---|---|---|
| R-A | 01 | 12.00 | GR-01 | New |
| R-B | 02 | 18.00 | GR-02 | New |
| R-C | 03 | 20.00 | GR-03 | New |
| R-D | 04 | 10.00 | GR-04 | New |
| R-E | 05 | 15.00 | GR-05 | New |
Expected New-phase count = 5 and total = 75.00 m², with identical stable keys and areas before/after. A grouped total of 75.00 is not proof that each identifier is correct. Place an additional Existing-phase control room; it must be absent from the New-phase result and present in the designated Existing audit. Test one intentionally blank finish key in the exception view before correcting it.
Export only after the known-data schedule passes. Record delimiter/encoding, decimal symbol, units, column order and receiver field mapping: stable key → RoomKey; Number → RoomNumber; Area in m² → Area_m2; FinishKey → FinishCode. In the receiver, preserve leading zeros/text identifiers, compare five keys and expected numbers, independently sum to 75.00 m² and check exceptions/phase scope. Retain model revision, schedule settings, export/profile revision, receiver version, comparison and reviewer. Published schedules must reconcile to that same model revision; later edits require a new exchange.
Timing and controlled exchange decisions#
| Trigger | Input / producer | Checked output and timing | Decision / route |
|---|---|---|---|
| Mobilisation / RIBA 0–1 where appointed | Brief, tool/template baseline / BIM coordinator | Tested setup before production | Accept readiness or hold missing evidence |
| Daily production / RIBA 2–4 as appointed | Photos, approved decisions / author | WIP model + itemised audit at daily review | Producer check; rejected edits corrected in WIP |
| Weekly coordination | Checked revisions / task teams | Shared package before agreed coordination meeting | Coordinator review; issue and resubmission record |
| Formal stage exchange / RIBA 3–6 as appointed | Agreed deliverables and requirements / delivery team | Exact checked revision at MIDP/TIDP date | Appointed delivery authority authorises; recipient accepts; Published only after relevant decisions |
| Operational change / RIBA 7 where appointed | Asset-change/maintenance trigger / asset information owner | Checked AIM update at agreed trigger | Operational recipient acceptance; retain prior state and decision in Archive |
These timings implement the approved project plan; they are not universal ISO durations. Archive retains superseded revisions and decision evidence throughout, not just at the final stage. A progress meeting cannot silently waive mandatory data or coordinate failures.
Acceptance criteria / self-check list#
- Photo/key-plan sources and revisions are traceable; uncertain geometry has a validation request.
- Progress states and exchange timing identify inputs, output revisions, responsible roles and blockers.
- Conflicting grids/designs have an approved disposition before model changes.
- Standards transfer is selected, diffed and approved; protected data and coordinates remain correct.
- Room tag, room record and grouped schedule edit scope are distinguished and tested.
- Tool/profile provider, licence, builds, dependencies, trusted source/loading and operational test are recorded.
- Baseline, selection, run logs, before/after review, rollback and native fallback are available.
- Shared bindings/key definitions, known-data phase/filter/count/totals and exception views pass.
- Receiving fields/units/identities and final schedules reconcile to the retained model revision.
- Check, share, authorise, accept, reject/correct/resubmit and Archive evidence are separately recorded.
Common mistakes#
- Calling installation or a tab colour a successful tool test.
- Renumbering whole-model scope while reviewing only one plan.
- Deleting a tag to remove a room, or permanently deleting rooms to remove tags.
- Overwriting parameter definitions because display names match.
- Hiding empty marks without retaining an exception schedule.
- Reporting tool time saved as a net benefit without baseline, validation time, licence/training cost and attributable outcome. Convenience alone is not ROI (C13).
Related guides#
- 22: collaboration/recovery; 23 and 30: reference hygiene and approved coordinates.
- 27 and 35: controlled property/content admission; 28: checked graphics and output.
- 32: room records and measurement; 33: finish/phase data; 36: schedules and reconciliation.
Editorial coverage record#
R09.1–R09.5: tool register and procedure 6–8. R14.1–R14.5: known-data schedule, binding/key requirements, phase/filter tests, receiver mapping and retained revisions. T04.1–T04.5: procedure, progress register and trigger/decision table. C04/C09/C10/C12/C13/C17/C19 resolved with distinct exchange decisions, approved discrepancy/data/tool controls and corrected transfer/room actions. P1 1/1 and P2 1/1 fixed; P3 five-element exercise included. Exercise execution remains an assessed task in the approved build.
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
- S03 — ISO 19650-3 — Operational phase of the assets. ISO, 2020, ed.1. https://www.iso.org/standard/75109.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
- 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
- S18 — ISO 29481-1 — Information delivery manual: methodology and format. ISO, 2025, ed.3. https://www.iso.org/standard/88515.html
- S19 — ISO 29481-2 — Information delivery manual: interaction framework. ISO, 2025, ed.2. https://www.iso.org/standard/88516.html?browse=tc; https://www.iso.org/standard/55691.html
- S21 — RIBA Plan of Work 2020. Royal Institute of British Architects, 2020. https://www.riba.org/work/insights-and-resources/riba-plan-of-work/; https://www.riba.org/media/sszn5kkt/2020ribaplanofworktemplatepdf.pdf
- 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
- 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
- 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
- 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
- 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/
- P03 — Calculating costs and benefits for the use of BIM in public tenders — User handbook. European Commission study by RINA Consulting / B1P; EU BIM Task Group host, 2021. https://www.eubim.eu/wp-content/uploads/2021/05/Cost-Benefit-Analysis-for-the-use-of-BIM_user-handbook.pdf; https://eubim.eu/cost-benefits/
- P05 — Data lineage. Microsoft Learn, Undated live documentation. https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-data-lineage