ArchHubBABOOMDownload

Setting Up a Building File: URS, Levels, Links and Plug-ins

BBM-STD-30 · V0.2 · Set up a building model from the office template and link it to the URS (Unique Reference System): the office reference model for the site, plot boundaries and approved shared coordinates.

Download WordAll standards

Office BIM Workshops · Presenter: Ahmed Fargaly · Recorded session: 20 November 2024 · BBM-STD-30 · V0.2 · 14 October 2026 · WIP training revision; office approval pending

Purpose & scope#

Set up a building model from the office template and link it to the URS (Unique Reference System): the office reference model for the site, plot boundaries and approved shared coordinates. Keep the workshop rhythm: work in loops, model what is known, mark what is missing, and refine it when verified evidence arrives. A useful provisional model is acceptable for an internal study; it is not a surveyed or as-built record.

This guide covers requirements, levels and grids, coordinate relationships, file and cloud links, starter outputs and the plug-ins used during setup. The building author produces the model; the coordinate owner approves its site relationship; the BIM coordinator checks the starter package. The project information-management function records the exchange decision. Appointment roles govern authorisation and acceptance.

Standards basis#

  • ISO 19650-1:2018 and ISO 19650-2:2018 support agreed information requirements, responsibilities, mobilisation and controlled delivery. Office Manual BBM-STD-01 V0.1 §§2.1, 3.3, 8.2, 9 and 11–12 serve these arrangements.
  • Office BEP BBM-STD-10 V0.2 §§8.2, 8.3, 8.5 and 9 define the project's origin/orientation, naming, model segregation and technology baseline. Use the approved project annex where office examples conflict; do not copy another building's identifiers.
  • ISO 19650-4:2022 supplies the exchange-quality basis. A link that looks right is only one check; the received export must preserve the agreed position and data.
  • ISO 7817-1:2024 defines purpose-led level of information need. Record required geometry, properties and supporting documents for the current exchange rather than assuming a stage or LOD number completes the requirement.
  • Autodesk A01/A10/A06/A21 and buildingSMART S12 support template, coordinate, parameter, schedule and exchange checks. A11/A12 support automation trust/loading. These are implementation guidance, not invented ISO clauses.

What V0.2 corrects, and why#

Workshop shorthandV0.2 instructionReason
Scale against an assumed corridor or map and place the buildingUse only for labelled provisional WIP; obtain survey control before sharing an authoritative coordinate baselineAssumed dimensions cannot establish survey accuracy (C10)
Ground stays at zero until levels arriveRecord the provisional datum and uncertainty; approve its later transformationA display value of zero is not a verified elevation
Move a level and the building moves with itTest each host, offset, constraint, linked element and unhosted objectElements respond differently to a level change
Roof is always structuralName each datum by its purpose; agree structural, finished and roof-reference levelsA modelling convention cannot decide every roof design
Shared Site steps work for every modelUse a tested file publish/acquire route; cloud models cannot use Publish CoordinatesThe storage route changes the supported operation
Plug-ins are free and checkedVerify provider, licence, build, dependencies and sample outputInstallation, a shared folder or past pricing is not approval (C12)
Clear chat uploads routinelyRetain the controlled source and receipt under the project retention policyDeleting a communication must not remove decision evidence

Baseline register — complete before setup#

FieldRequired entry / example
Purpose and exchangeInternal concept study / coordination exchange; due date; intended receiving tool
RequirementsApproved BEP/EIR references and required geometry, properties and documents
Model allocationBuilding B01; architecture author role; site URS owner role; structural/MEP reference owners
Revit environmentExact major release and build; approved add-in/exporter builds; file-based or cloud collaboration
Template and contentApproved template filename, revision/hash and library release; units and discipline
Source evidenceSurvey filename/revision/date, responsible survey role, issue receipt; plan/photo provenance
Coordinate authorityCoordinate owner; CRS identifier or documented local system; horizontal units; vertical datum/units; north convention
Control pointsTwo separated plan points with approved XYZ values, plus a verified elevation benchmark; uncertainties and tolerances
Model split and linksContainer IDs, source revisions, path/access route, link owner and reload frequency
Approval and freezeCoordinate decision ID, date, checker and permitted use; change/recovery baseline

Unknown fields are marked UNVERIFIED, with an owner and due date. The coordinate owner sets project tolerances from the survey and exchange purpose. No generic tolerance in this guide certifies accuracy. Hold the authoritative shared exchange until missing coordinate authority is resolved.

Step-by-step procedure#

  1. Work in a controlled loop. Collect the available drawings and photos; mark missing dimensions/elevations with issue IDs and requests to the site team. Keep source revisions. Use model lines for the reusable outline and detail lines for view annotations. A generic group name such as B01-OUTLINE is an internal aid, not survey proof. Do not scale against a guessed width and describe the result as verified.
  2. Create from the approved template. Confirm its revision and exact Revit build. The recording used Revit 2023; this is history, not the current software specification. Set length/area units, precision, discipline, object styles, view templates and required starting content. Fill Project Information from the approved register. Validate the project's filename grammar and metadata against the BEP annex rather than changing one token in an old name.
  3. Establish levels and grids. Record source, datum, intended function and owner for each. Retain the office uppercase labels where the annex adopts them, with unique names and no hidden duplicates. Distinguish structural slab, finished floor and roof-reference levels. Check sections and elevations against verified sources. Before deleting a template level, find its hosted elements, dependent views and constraints; rehost or retain it under an approved plan. Copy/Monitor only agreed levels/grids, then review each monitoring difference with the owner.
  4. Understand the three references. The internal origin is the model's internal reference; the project base point supports a project-local reference; shared coordinates express its agreed relationship to the site. Project North serves working plans; True North represents site orientation. Shared transforms do not require dragging geometry far from its internal origin. Record both north settings and check representative views. Never reset a datum or origin to make one view look aligned.
  5. Prepare the URS. Open the correct local of a file-based central, or the supported cloud model, using guide 22. Confirm the survey and plot revision, controls, units, datum and north. If a PDF/CAD underlay is used, record scale evidence and compare at least two independent distances; pin approved links. Paste Aligned to Same Place preserves a placement operation only within the relevant model references; verify the resulting geometry rather than treating paste/rotation as establishing shared coordinates.
  6. Choose one coordinate route. The coordinate owner documents which model is authoritative, which operation is permitted and who saves each change. Test on controlled copies before applying it to the live collaboration model. Do not acquire from a building that acquired from an unverified site.
RouteControlled operationVerification / stop condition
File-based URS publishes to buildingLink building into the authoritative URS by an approved initial positioning method; move/rotate only under the coordinate owner's instruction; use supported Publish Coordinates/shared-site workflow; select and save the intended site relationship to the linked fileRecord named shared site, transform and saved revisions; verify independently in building and URS. A save warning or wrong site means stop, not repeated blind synchronisation
Building acquires from file-based URSLink authoritative URS into the building; establish and check its placement; Acquire Coordinates from that URS; save approved building baselineCheck the resulting shared values and True North; reload/relink using the agreed shared-coordinate position and verify controls
Cloud building acquires from URSPublish Coordinates is unavailable for cloud models. Link the authoritative site model through the project's supported cloud route; establish its verified placement; Acquire Coordinates into each receiving building; save/synchronise under the project's cloud procedureProve this route in the adopted release and tenancy on a test model. Record source revision and coordinates in every building. Do not substitute cloud sync/publish for a coordinate operation
  1. Bring the site reference into the building. Once the baseline is saved, link the URS By Shared Coordinates where the agreed setup supports it. Compare the two separated XY controls and elevation benchmark, then inspect an independent grid/outline direction. Pin the approved link and record its placement. By Linked View may provide coordinated graphics, but it is independent of coordinate authority. Use matching URS plan phase, level and view where required. Reload controlled revisions; a reload does not authorise a changed survey transform.
  2. Prepare the building package. Create floor plans from accepted levels; apply WIP/coordination templates, scales and phase scope. Keep the template's NOT FOR CONSTRUCTION status for unfinished outputs. Remove unused starter sheets only after checking references. Split large plans into parts using the project's series/part numbering and match lines. A browser view named Published and a published graphics template do not change CDE state (C04).
  3. Test starter outputs together. Place a plan and a 3D view on a starter sheet; inspect title block, identifiers, scale, dimensions, grids and north. Place representative sample elements, populate required shared parameters, and check tag/schedule values and category/type-instance bindings. Export the agreed native/open deliverable with the approved exporter/profile. In a receiving tool, check required objects/properties, units, both XY controls, benchmark elevation and north/orientation. Retain the input model revision, exporter settings, output revision and screenshot/report. Failed mandatory data or position prevents release.
  4. Check before sharing. The author checks WIP; the coordinator reviews the proposed Shared package; the appointed delivery-team authority authorises the exchange and the appointed recipient accepts it as required. Record rejection, corrections and resubmission as new revisions; retain superseded decisions in Archive. Editable native models can be controlled containers. Sync, cloud publish and browser organisation remain separate from formal issue authorisation.

Survey authority, supported file/cloud positioning and independent receiving checks form the startup gate.

Plug-in approval and controlled changes#

Align commands, pyRevit, printing/export tools and screen capture remain useful workshop techniques. Promote only tested commands to the Quick Access Toolbar. Record screenshots as coordination evidence with issue ID, element/view reference, source revision, owner and due date; minimise sensitive content. Retain the controlled issue record and receipt before any permitted removal of chat copies.

Inventory / test fieldFill before use
Tool, provider, purpose and rightsExact package/source URL; licence evidence/date; permitted use; approval owner
Build and dependenciesRevit build, tool build, extension/graph package versions, runtime dependencies, exporter/print profile
Trust / loadingReviewed source/hash; approved restricted folder; manifest/assembly match where applicable; extension/graph loading route
Operational testDate/user/test model; exact command; expected output; loading warnings; before/after counts and geometry/data differences
Acceptance / recoveryOutput reviewer, approved result, log location, rollback baseline, manual fallback and expiry/retest trigger

API add-ins use.addin registration; record the appropriate release-specific user/all-user manifest and assembly locations. Availability also depends on document/command context. An installed button does not prove the command works. Review graph/package provenance before trusting a Dynamo Player folder; folder trust does not certify every current or future graph. Test a small controlled sample, inspect modified elements and retain logs before batch use. On unexpected changes, stop, isolate the result and restore the approved baseline through the collaboration recovery procedure; do not overwrite another author's newer work. Manual fallback is native alignment/annotation and individually reviewed export/print operations.

A Revit file upgraded to a newer release cannot be saved back to the older native format (A01). Retain the original baseline; test upgrades on copies with linked models, templates, add-ins, tags, schedules and exporter. Approve one coordinated project migration. An IFC export can support an agreed exchange but does not restore full native editability or constitute native downgrade.

Worked exercise — two building files#

Use synthetic Building B01 and B02 linked to one test URS. The coordinate owner supplies a local test system in metres, CP-A (100.000, 200.000, 10.000) and CP-B (120.000, 200.000, 10.000), and an eastward 20.000 m separation. These are exercise values, not a real survey. Record the project's test tolerance before testing.

  • Establish the approved shared relationship in both files and verify CP-A/CP-B values plus the 10.000 m benchmark in the URS, each building and the received export. An east/north swap, scale change or 20 m separation error fails.
  • Copy/Monitor one agreed grid and level. Change a level by a recorded 0.100 m in a copy: inspect one level-hosted wall, one element with an offset and one unhosted element. Record actual behaviour; accept only intended changes.
  • Produce one starter sheet and a sample schedule, then export/reconcile. Repeat the cloud acquire branch if the project is cloud-based; the file route alone is insufficient evidence for cloud readiness.
  • Submit baseline register, two-point/elevation results, sheet, schedule, export checks, issue/decision log and approved rollback instruction. A failed coordinate or mandatory-property check requires correction and reassessment.

Acceptance criteria / self-check list#

  • Survey authority, CRS/local system, units, vertical datum, north, two separated controls, benchmark and tolerances are recorded and approved.
  • Provisional evidence is labelled with owner/due date; no authoritative share relies on guessed dimensions.
  • Levels/grids, model split, link revisions, geometry response and supported coordinate route are checked; cloud route excludes Publish Coordinates.
  • Exact software/template/content baseline, units, discipline and graphics are recorded; upgrades preserve the original and have coordinated approval.
  • Starter sheet, parameter/tag/schedule and receiving export checks pass against required outputs; model revision and evidence are retained.
  • Tools have provider/licence/build/dependency/trust/loading and controlled sample evidence, assigned reviewer, logs, rollback and manual fallback.
  • Coordinate changes have impact review, approval and a new baseline; producer, checker, authoriser and recipient decisions are traceable.

Common mistakes#

  • Treating an outline pasted at the same place, a pinned map or matching north arrow as survey evidence.
  • Copying every level and deleting the defaults before reviewing hosts and dependent views.
  • Acquiring from the wrong linked revision or repeating coordinate commands after an unexplained warning.
  • Treating all roof datums, all level-host behaviour or all plug-in licences as universal.
  • Calling a view Published before the exchange has passed its formal checks.
  • 21: initiation/template fundamentals; 22: correct file/cloud collaboration and recovery.
  • 23: clean CAD references; 25: project initiation responsibilities and registers.
  • 28: checked sheets and graphics; 31: approved daily tools and data changes.
  • 32: measured existing-condition/room checks; 36: schedule reconciliation.

Editorial coverage record#

R08.1–R08.5: baseline register, three references, coordinate-route table, cloud acquire branch and receiving/change checks. R01.1–R01.5: baseline register, procedure 2–3/8–9 and controlled-upgrade paragraph. R09.1–R09.5: plug-in inventory, provenance/loading, sample/log/rollback and assigned output review/manual fallback. C02/C04/C09/C10/C12 are resolved through project-controlled identifiers/data, distinct CDE decisions, coordinate authority and tested tools. P1 1/1 and P2 1/1 fixed; P3 two-building exercise included. These are document corrections; exercise results must be demonstrated on the approved project 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
  • 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
  • A01 — Project Templates; Create a Model. Autodesk Revit Help, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Customize/files/GUID-4C16B54A-7ADA-4DEB-A278-C199B1BC4207.htm; https://help.autodesk.com/cloudhelp/2026/ENU/Revit-GetStarted/files/GUID-3FF8DDB0-A015-4F94-B9DA-1FA96181FCA3.htm
  • A10 — How to set up Shared Coordinates using one Revit model as the Site or Base file. Autodesk Support, 15 August 2026. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-set-up-Shared-Coordinates-using-one-Revit-model-as-the-site-or-base-file.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
  • 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
  • S12 — Industry Foundation Classes (IFC). buildingSMART International, Undated live page; 2024 ISO edition. https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/?lang=en
  • 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