ArchHubBABOOMDownload

Project Initiation: Worked Example

BBM-STD-25 · V0.3 · Read the commission before drawing.

Download WordAll standards

BABOOM-BIM-STANDARD · Office BIM workshops · Presenter: Ahmed Fargaly · Revision v0.3 · 4 November 2026 · Status: training draft for office review

Purpose & scope#

Read the commission before drawing. Break it into tasks, buildings, discipline scope, stages and exchanges; then plan people and time. This worked example keeps the office workshop’s initiation method without carrying a client project identifier into its title or reusable example. It covers project planning and enough software mobilisation to prove the starter environment is usable.

Standards basis#

ISO 19650-1:2018 provides the requirements and party concepts; ISO 19650-2:2018 supports appointment, confirmed BEP, mobilisation and information delivery planning; ISO 19650-4:2022 supports exchange decisions; ISO 19650-5:2020 supports sensitivity-based custody. RIBA Plan of Work 2020 stages 0–7 are a framework, not a requirement for two revisions at every stage. This serves office Manual v0.1 §§2.1–2.3 governance/roles/milestones, §3.3 partitioning, §8.1 Project Initiation Protocol, §8.2.3 initiation methodology and §12 CDE. UK BIM Framework Guidance C (2020) and F (2020) explain workflow and planning implementation.

Prerequisites and controlled baseline#

Work in a training copy until the exercise is checked. Obtain the applicable exchange information requirements (EIR), confirmed BEP, office Manual and approved content library. The BIM manager assigns the trainer/checker; the task-team lead owns the model work. These instructions do not confer project acceptance authority.

Record before useValue / evidence to enter
Project/training model and revision[identifier; WIP location; baseline revision]
Revit release and full build[Help > About; record all build digits; check every collaborator]
Template and content revision[approved RTE/RFA identifiers, revision and controlled location]
Requirements and office documents[EIR/BEP/Manual revisions; approved deviations]
Exchange and recipient[native/open format, IFC schema/profile, exporter build and receiving tool]
Trainer, checker and date[roles; test date; evidence location; decision]

The 2024 workshop is historical teaching evidence. No exact installed build or approved library revision was supplied for this rewrite. Complete this form and run the exercise in the adopted release before project use; do not substitute “latest” for a tested version. References to Autodesk Help identify the documented release, not an office installation.

1. Read and break down the commission#

Use a synthetic two-task commission. Task A refurbishes existing buildings, with interiors, services, facade and structural intervention subject to survey. Task B designs new low-rise buildings using the accommodation brief; its discipline scope includes landscape. Specifications, permits, studies, tender and supervision are separate explicit scope entries, included only where appointed. An early area estimate informs workload; it does not establish accepted accommodation or verified existing conditions.

PackageSynthetic stage sequenceRequired clarification
A — refurbishmentA1 concept; A2 technical development; A3 tender packageAny omitted schematic package must have its required decisions/information allocated elsewhere.
B — new buildingB1 concept; B2 schematic development; B3 technical development; B4 tenderConfirm procurement, authority route, discipline responsibility and review periods.
SupervisionSeparate appointment, if requiredConfirm appointment, deliverables and mobilisation; do not assume it follows design automatically.

A1/B1 are local package labels, not RIBA stage numbers. Map them to required outcomes and exchanges; RIBA Stage 3 is Spatial Coordination, Stage 4 Technical Design, and Stages 4/5 can overlap by procurement. The nine manual phases (Intro, Setup, Modeling, Delivery, Information, Coordination, Discipline, Authority, Handover) organise training/workflows and do not replace those project stages.

The workshop planned a review issue followed by an approval issue. Use that pattern only if the actual commission agrees it; revisions are not limited to two, and final submission still needs checks and receiving acceptance. Approval comments and changes must have owners, dates and revised scope/programme consequences.

Task labels and review revisions are local planning choices; a receipt alone does not authorise information.

2. Project records and CDE mapping#

Keep the office’s useful PM, Correspondence/Submittals, MOM/Memo/Report and Supervision record classes. Replace catch-all “Misc” with a controlled intake/index queue: assign an owner, sensitivity, destination and review date. These are record classes, not new top-level workspace folders. Inside ArchHub they stay within the authorised numbered area; do not create MISC or scatter files at root.

Record / containerWorking state and accessTransition and retained evidence
Commission, contract, authorisations, CV evidenceRestricted project administration; approved copies separately controlledRequirements owner confirms applicable revision; minimise personal data and distribution.
Task-team models/calculations/drawingsWIP; producer/checker accessInternal check and approval for sharing before Shared.
Coordinated discipline packageShared; permitted delivery-team recipientsLead-appointed-party review/authorisation for intended use; failed information returns for correction.
Authorised contractual exchangePublished/accepted-use baseline under the agreed CDE workflowAppointing-party acceptance decision against requirements; revision, suitability, transmittal and receipt retained.
Superseded issues, decisions and audit historyArchive; controlled read accessRetain exact versions and decisions; do not overwrite the accepted record.
Authority submission and receiptSubmission record linked to exact exchange revisionReceipt proves delivery, not technical approval or all CDE decisions. Record authority disposition separately.

A portal can implement some CDE functions; its existence alone does not prove the agreed permission/state workflow. Record the actual platform, state names, access groups, transition actors and evidence links. Contract/protocol particulars determine who can authorise and accept. A job title or folder name does not grant that power.

Folder locations for these records follow the one project folder tree in Manual V0.5 §12.1 (state → data type → discipline; folder names NN-NAME without dots). This guide defines no folders of its own.

Step-by-step procedure#

  1. Project manager and requirements owner review the commission/RFP, signed appointment and information protocol. Record decisions, exclusions, interfaces, assumptions and requested clarifications. Confirm legal document precedence with the authorised contract owner; this guide supplies no replacement hierarchy.
  2. Split scope by task/building/discipline/package. Assign accountable package leads and detailed production responsibilities, including specialist studies. Assess CV/competence evidence, actual staff availability and required experience. Allocate work by expertise where useful (sections, finish schedules, details) while retaining a named owner for each delivered container and cross-building interface.
  3. Define each exchange’s purpose, recipient, date, LOIN, formats, quality criteria and sensitivity. Derive task-team TIDPs and consolidate the MIDP; a RACI is not a delivery plan. Include dependencies, production duration, review/authorisation/acceptance windows and an agreed baseline/change owner.
  4. Build the programme in the approved scheduling tool; the workshop used a scheduling application, but the tool is not an ISO requirement. Include team mobilisation, authorisations, authority registration, surveys, design and realistic review time. Test a delayed review scenario and adjust dependencies; do not assume a two-week review will always finish in two weeks.
  5. Collect existing drawings/archive records, site observations/photos and available surveys. Log origin, revision, date, survey method, accuracy/uncertainty and intended permitted use. Designate the coordinate/datum owner and authoritative levels, units, reference system, origin/north strategy and survey controls. Approximate/as-recorded inputs stay provisional until independently verified for the intended use.
  6. For new development confirm the applicable controlled regulation/brief: height, floors, coverage, uses, access and interfaces with demolition/extensions. The authorised discipline/authority owner confirms current requirements and evidence. No generic numerical code limit is invented here.
  7. Approve the model split and linked-reference register: datum/site file, discipline/building files, link owner/revision/reload route and coordinate method. Check two separated control points and one elevation against the accepted reference with recorded tolerances. Resolve misalignment before coordination.
  8. Complete the exact software/build/template/content/exporter baseline. Create a representative starter model from the approved template. Set project units and discipline, controlled view templates/graphics, browser organisation, required parameters, title block and initial approved families. Verify datum/reference positioning and record any approved deviation. Guide 21 supplies detailed interface practice; these checks remain mandatory here.
  9. Produce one starter plan/section sheet, an itemised schedule and a shared-parameter tag. Populate synthetic IDs and compare model/tag/schedule/title-block values. Export the agreed IFC profile and open it in the receiving tool; reconcile object counts, mapped properties, coordinates and dimensions. Log missing/invalid data and correct/retest before releasing setup.
  10. Test permissions and the complete exchange route: producer check, sharing, team authorisation, receiving acceptance/rejection, resubmission, archive and transmittal receipt. Name each actor and retain the exact revisions and decisions. Platform publication and formal acceptance are separately recorded.
  11. Agree the common architectural identity through approved option/mood-board review where appointed. Reuse facade/interior/room principles with controlled variations per building; a repeated theme must still meet each building’s constraints and required information.
  12. Preserve the accepted compatible starter baseline and all linked/content revisions. Upgrade only a copy after approval, including add-in/exporter compatibility and representative output checks. Revit files are not backward-compatible. Rollback restores the preserved compatible baseline for the coordinated team; never upgrade the only copy.

Initiation register and worked assessment#

IDDecision/outputOwner / dependencyExpected checkEvidence / status to enter
INIT-01Task/building scope and exclusionsProject manager; appointmentEvery deliverable/interface has an owner[matrix revision; unresolved query; date]
INIT-02Survey/datum and source registerDatum owner; verified surveyPoint/elevation tests and uncertainty accepted[reference revision; deviations; approval]
INIT-03TIDPs → MIDP baselineTask leads / delivery-team plannerDependencies and review windows reconciled[container IDs; dates; baseline decision]
INIT-04Build/template/content baselineBIM/IT ownerExact compatible revisions approved[inventory; access test; rollback copy]
INIT-05Starter sheet/schedule/IFCAuthor/checker/recipientKnown values reconcile end to end[model; PDF; schedule; IFC; report]
INIT-06CDE and mobilisation releaseAssigned authoriser/acceptorPermission/state/decision loop exercised[transmittal; rejection/retest; acceptance]

Exercise: build the two-task scope and programme, including one delayed client review, then populate INIT-01–06 using a synthetic two-level starter building. Include one deliberately wrong parameter value and one rejected exchange; show correction and resubmission. Retain scope/programme, baseline, annotated datum/sheet screenshots, itemised schedule, receiver report and CDE decision record. Assessor checks that no activity starts on an unresolved critical dependency and that authority is assigned by appointment.

Acceptance criteria / self-check list#

  • Scope/stage outcomes, discipline interfaces, excluded supervision and change authority are explicit.
  • Named container producers, dependencies, production/review periods and exchange recipients form a reconciled baseline.
  • Authoritative datum/source provenance and point/elevation tests are complete; provisional data is labelled and excluded from inappropriate use.
  • Units, graphics/templates/content and exact builds are approved; compatible rollback baseline exists.
  • Starter sheet/tag/schedule and recipient IFC reconcile required geometry/data/documents with no mandatory failures.
  • Tested CDE workflow separates submission receipt, authorisation, technical acceptance and rejected/resubmitted revisions.
  • Team access, competence/capacity and assessed mobilisation evidence are recorded before project use.

Common mistakes#

  • Starting geometry before reading the commission: record scope and requirements first.
  • Treating task labels or two issues as universal RIBA rules: map actual outcomes and review obligations.
  • Calling archive drawings verified as-built: record uncertainty and independent verification.
  • Confusing a receipt with approval: retain separate receiving decisions.
  • Assuming the team will cope with a late review: update dependencies and escalate the programme impact.

Keep the workshop attitude: problems require a clear owner and next action. That includes pausing an exchange whose critical requirements remain unresolved; determination is not a reason to issue unverified information.

  • 21–22 — starter model/worksharing; 26–28 — parameters and documents.
  • 30 — datum/site setup; 31 — daily controls; 32 — existing-condition checks.
  • Office OIR/BEP, Directory, TIDP and MIDP: approved editions and project-specific responsibilities.

Assessment record and release#

Retain the exercise model/family, annotated screenshots, schedules or exports named above, and the completed checks together in the controlled training evidence location. Record learner, task, exact revisions, checker, date, result, defects, correction and retest. A mandatory failure means rework and reassessment; attendance alone is not a pass. The trainer records competence for this task; project use still follows the approved BEP and appointment authority. Do not distribute sensitive models or screenshots beyond their authorised audience.

Research coverage and correction trace#

R01.1: steps 1/8; R01.2: step 8; R01.3: steps 5/7; R01.4: steps 9–10; R01.5: step 12. G25 has no independent P1 factual defect; private case replaced by a synthetic office example and retitled. P2: initiation/CDE/baseline/exchange controls. CROSSWALK C03/C04/C07/C08/C10/C11/C12/C14: explicit boundaries and tested mobilisation.

References#

Sources used from RESEARCH.md (with supplemental verification in GAPS.md where identified). Edition labels describe source evidence; confirm applicability against the approved project baseline. Standard-level references are used because the supplied research does not verify individual ISO clauses.

SourceTitlePublisherYear / editionURL / evidence note
S01ISO 19650-1 — Concepts and principlesISO2018, ed.1Catalogue / abstract; published, revision underway
S02ISO 19650-2 — Delivery phase of the assetsISO2018, ed.1Catalogue / abstract; publisher result exposes English abstract and status
S04ISO 19650-4 — Information exchangeISO2022, ed.1Catalogue / abstract
S05ISO 19650-5 — Security-minded approach to information managementISO2020, ed.1Catalogue / abstract
S07ISO 7817-1 — Level of information need: concepts and principlesISO2024, ed.1Catalogue / abstract
S21RIBA Plan of Work 2020Royal Institute of British Architects2020Current resource page; 2020 template
G-CGuidance C — Facilitating the CDE workflow and technical solutionsUK BIM Frameworked.1, September 2020Official PDF; archived guidance
G-FGuidance F — About information delivery planningUK BIM Frameworked.1, September 2020Official PDF; edition actually verified. Its federation section is a placeholder; use other sources for technical federation guidance.
G-EGuidance E — Tendering and appointmentsUK BIM Frameworked.2, February 2021Official PDF; archived guidance
A01Project Templates; Create a ModelAutodesk Revit HelpRevit 2026Template contents; creation and backward-compatibility warning
A06Create Shared Project ParametersAutodesk Revit HelpRevit 2026Category bindings, instance/type and tag/schedule use
A10How to set up Shared Coordinates using one Revit model as the Site or Base fileAutodesk Support15 August 2026Local workflow and cloud limitation
A21Schedules; About SchedulesAutodesk Revit Help2026 / 2024Schedule types and outputs; grouping and live model data
S12Industry Foundation Classes (IFC)buildingSMART InternationalUndated live page; 2024 ISO editionVersion and implementation context

Office source: BBM-STD-01-MANUAL-V0.1, sections identified under Standards basis; applicable confirmed project BEP and controlled Glossary. Preserve the source workshop export unchanged.

Document history
RevisionDateChange
v0.214 October 2026Training draft for office review
v0.32026-11-04folder names without dots: §2 points to the one project folder tree in Manual V0.4 §12.1