ArchHubBABOOMDownload

Native templates view assets and software release

BBM-STD-65 · V0.3 · The BIM Manager owns the supported configuration

Download WordFormsAll standards

Ribbon tools that apply it: New Project from Template, Apply BABOOM Standard, Worksets, Sync Queue, Visibility Doctor, Hide in Views / Unhide, Colour by Value, Section Box, Select, Measure, Where Used, View Templates, Filters, Toggles, View Settings, Grids Display, Room Views

The library it governs: the templates

BBM-STD-65-TEMPLATES_AND_RELEASE-V0.3 | Office standard | 5 November 2026 | V0.3 | Private controlled WIP draft

Revision history

VersionDateChange
V0.12026-10-16Initial controlled WIP draft.
V0.22026-11-04Closed audit rows: 1.1 supported-release summary (matrix in BBM-STD-91), DM permit export preset, 4.1 seed upgrade, discipline standards 58-62 linked, IFC schema/MVD columns, relinked Manual V0.4/BEP V0.5; share paths updated to the 2026-11-04 folder map; IMI Framework naming; spacing fixes + cross-doc pointer pass. + template alignment (..148) + folder names without dots
V0.32026-11-05One office Revit template for all disciplines, BBM-GEN-TMP-R23-REV04: discipline templates retired; discipline settings merged; no loadable model families or details in the template (§1, §2, §4.1)

1 Inventory support and authority#

This standard covers, and. The BIM Manager owns the supported configuration; each discipline template custodian owns its contents; QA provides independent verification; project/appointment owners approve deployment and recipient capability. Use BBM-STD-51, BBM-STD-54, BBM-STD-63, BBM-STD-72, Manual V0.5 §4, BEP V0.5 §9.2.1 and the editable release pack. These are draft interfaces; no native file is released by this pack.

Read-only inspection on 2026-10-16 found 9 RTE candidates below BABOOM-BIM-STANDARD/01-TEMPLATES (folders renamed 2026-11-04: Revit seeds now under 01-TEMPLATES/02-REVIT, AutoCAD under 01-TEMPLATES/01-AUTOCAD; the top-level R23 REV00.0165-0167 candidates moved to 01-TEMPLATES/98-ARCHIVE), recorded with actual bytes/full SHA-256 in Manifest. Filenames indicate architectural/R23 and historical references; native full builds and contents were not opened. The top-level R23 REV00 is 52371456 bytes/hash e0d9ce6ccb97c57d32103b7f9ec74e8c948f1886e89f93ebd30afbb8ed9da6ea; indexed R23 is 42299392 bytes/hash d929381930d39317bac9c02a9879e371dd103a78a4447846ee80f207662fbe28. They are different artifacts, not interchangeable current masters. Highest numeric suffix, modification date or indexed presence does not select the authoritative seed. Custodian comparison/adoption is required; preserve all sources read-only and publish only the chosen approved reference after tests. Historical candidates are not deleted by this standard.

The office Revit template is ONE file for every discipline: BBM-GEN-TMP-R23-REV04 (01-TEMPLATES/02-REVIT/BBM-GEN-TMP-R23-REV04.rte, founder decision 2026-11-05). Architecture, structure, MEP, landscape and interiors start every project from it; there are no discipline templates (the former BBM-ARC-TMP-R23-REV03, BBM-MEP-TMP-R19-REV03 and BBM-STR-TMP-R21-REV01 are retired to 01-TEMPLATES/98-ARCHIVE). It carries the settings each discipline needs: view templates and filters per discipline (ARC 51, GEN 35, NO-DISCIPLINE (schedules, sheets, 3D) 11, STR 34), browser organisation, object and line styles, line and fill patterns, MEP system, duct, pipe, cable tray and conduit types with pipe segments and electrical types (14 duct, 3 pipe, 8 cable tray types; 15 mechanical and 22 piping systems), structural rebar bar and cover types (21 and 6), shared parameters (418 bindings) and 99 schedules. It carries no loadable model family, detail component family, detail group or drafting-view detail: those live in the family library (02-LIBRARIES/01-FAMILIES) and the details library (02-LIBRARIES/03-DETAILS) and are loaded per project. The template holds no loadable model family at all, not even fittings, profiles or railing parts: it keeps annotation families (tags, symbols, title blocks) only. MEP fittings, profiles and railing parts that system types use are loaded by the ribbon (Load discipline kit) from the library; until then those routing preferences and profile slots are empty. REV03 to REV04: loadable model families 86 to 0, detail groups 12 to 0, drafting views 100 to 1. It is authored in the oldest Revit release in office use, currently Revit 2023, and must open and upgrade cleanly in Revit 2023–2027; new projects start in a supported release (2024–2027) by upgrading the template and recording the upgrade test. Revit 2023 stays out of Autodesk support (previous-versions list checked 2026-11-04): legacy authoring release, recorded risk. The qualified build per release is a recorded field in BBM-STD-91; it does not prove office installation, exporter compatibility or a project's approval. Exact installed OS/update/native/cloud/checker/receiver builds, licences and plugin hashes remain required. Keep an appointed project's existing major release until an authorised upgrade; no “or later” permission. Each discipline's readiness is proved by its §2 fixture run on the one template.

1.1 Supported releases#

Summary (the full matrix with support status, qualified build, IFC exporter, seed hash and library save version per release is owned by BBM-STD-91): Autodesk supports Revit 2024, 2025, 2026 and 2027; Revit 2023 is out of Autodesk support and is legacy, used only on existing projects with recorded risk acceptance and an upgrade plan, never for new projects; it remains the office template's authoring release. The latest Revit 2027 update is 2027.3 (15 September 2026); the Revit IFC exporter 27.4.0.30 (30 October 2026) exports IFC4x3. The default release for new projects is reviewed annually against the Autodesk list.

2 Discipline template content specifications#

The one office template must contain qualified project units/precision, start view, property dictionary/bindings, approved categories/subcategories/materials, levels/grids/shared-frame placeholders, view types/templates, schedules/tags/legends, browser organisation, phasing, sheet/title-block assets and export/print profiles. Seeds contain no real project/client data, active cloud/central connection, imported confidential model, credentials or unmanaged plugin dependency. Coordinate placeholders must not masquerade as a surveyed origin. Register all dependency IDs/revisions/hashes; no hidden font/lookup/family dependency. Done in the office template (REV02-REV04): title blocks BBM-G-TTB-A1, BBM-G-TTB-A2 and BBM-G-TTB-A3 present, A2 and A3 created (Manual V0.5 §4.10); view template and filter names without ":"; the workset file BBM-STD_WRKST.txt (52 worksets) regenerated to the four Manual §3.3 user worksets; the shared-parameter file BBM-SHARED_PARAMETERS.txt carries the Manual §3.2 core parameters and the COBie parameters per BBM-STD-72 §2.

Discipline release IDRequired representative content and checksCurrent native stateContent defined in
SYN-TPL65-ARC R01Wall/door/room, plan/section/elevation, itemised door schedule, tag, material cut, A1 sheetOne office template BBM-GEN-TMP-R23-REV04; fixture run per §5BBM-STD-58 §1, §2, §5
SYN-TPL65-STR R01Structural member/level/grid, analytical interface as appointed, reinforcement presentation if required, member scheduleIn the one office template (STR view templates, rebar/cover types, structural line styles); fixture run per §5BBM-STD-59 §2-§4
SYN-TPL65-MEP R01Equipment/connector/system, duct/pipe/circuit representative categories, system browser/filter, equipment schedule and tagIn the one office template (MEP view templates and filters, system, duct, pipe, cable tray types, segments); fixture run per §5BBM-STD-60 §1-§4
SYN-TPL65-LSC R01Ground/planting/irrigation category interface, site plan, coordinates, planting scheduleIn the one office template; landscape content from the family library when appointedBBM-STD-61 §2, §3, §5
SYN-TPL65-INT R01Room/finish/ceiling/joinery interfaces, finish schedule, reflected plan/detailsIn the one office template; interiors content from the family library when appointedBBM-STD-62 §2, §3, §5

Use the Content requirements sheet for every asset type and discipline, not a generic checked box. Reference actual category/type/view/schedule IDs and expected values in test fixtures. The discipline modelling standards BBM-STD-58 to BBM-STD-62 define the content each seed carries, mapped in the last column. Native release still waits until the actual assets pass the tests below.

3 View filters browser phasing and graphics#

Retain Manual browser structure Discipline > Purpose > Level/Zone > Type with COORD/DOC/DETAIL/QA/SHT-PREP purposes. Start view STD00-STARTING-VIEW is not placed on sheets. View-name grammar remains DISC-LEVEL/ZONE-TYPE-DESC. DOC views use assigned controlled templates; apply-once settings are not continuous enforcement. Record which parameters are included/excluded, why, and who may change exclusions. No unexplained per-element override in issue views; deliberate exception needs owner, purpose and recheck.

Graphics are evaluated by Revit's actual precedence, not by this list's order. Register Object Styles, category overrides, linked/imported-category controls, view filters and their order, phase filters/overrides, workset/design-option/view range/detail/discipline settings, hide/isolate/temporary states, element overrides, halftone/transparency, cut patterns and scope/crop. Source Manual §4.1/4.2 retains lineweight indices, not millimetre widths. Export/plot specimens must establish the printed result. The owning view template locks only included settings; unsupported coordination-model visibility or linked-view settings need an explicit qualified route.

Synthetic precedence fixture SYN-V65 places three walls (one New, one Existing and one Demolished) and the AHU plus two valves. DOC-PLAN-100 includes scale 1:100 and phase New Construction. Custom phase filter PF65-ALL sets New=By Category, Existing=Overridden, Demolished=Overridden and Temporary=Not Displayed; phase override Existing=RGB128,128,128 solid and Demolished=RGB255,0,0 dashed. These are declared fixture settings, not Revit defaults. New wall is created New Construction; Existing wall is created Existing and not demolished; Demolished wall is created Existing and demolished New Construction. Phase cases G65-05/06 verify each independently. Filter F65-REQ selects missing mandatory Asset_ID on applicable mechanical equipment; F65-NEW selects built-in Comments=SYN-New on that equipment and proposes blue. The order F65-REQ above F65-NEW proposes red for overlapping colour; confirm in the native build. A deliberate red per-element override on the New wall must be detected, removed and restored to black solid category graphics without changing the Existing/Demolished specimens. Existing/Demolished content cannot disappear merely because a filter is convenient.

4 Exact compatibility and upgrade boundaries#

Compatibility is per use: new-project creation, editable native transfer, federation, IFC/property export, drawing/PDF/DWG output and asset import. Compatibility sheet freezes authoring full build, OS/runtime, native asset hash, exporter package/binary/hash, preset/dictionary/CRS revisions, schema/profile, checker and actual receiver build/configuration. An IFC export does not provide editable backward-native compatibility. Record receiver sign-off and rights/access separately. The Compatibility sheet also records, per IFC preset: IFC schema, MVD, the exporter build that supports it and receiver verified (Y/N). Default is IFC 4.0.2.1 Reference View; IFC 4.3.2.0 (ISO 16739-1:2024) Reference View is used only by recorded approval after a test export from the project's Revit build passes the project IDS and the receiver passes a test exchange; IFC2x3 Coordination View 2.0 only when an appointment or authority profile requires it; authority submissions use the schema the authority states.

When the Dubai Municipality BIM permit route applies (circular 9-1-2 of 13 October 2023, Open BIM from 1 January 2024; circular 9-1-3 of 15 January 2026, effective 1 April 2026), the release carries a controlled preset EXP-DM-PERMIT-<schema>-<rev> (the preset behind BEP V0.5 §7.4 exchange EX-P06; Manual V0.5 §11.2 calls it DBP-<schema>-vNN, an alias of the same asset): IFC export setup, mapping file and hash, using the IFC schema and export setup stated in the current Dubai BIM Standard (buildindubai.gov.ae/bim), checked at project start and recorded in the BEP, and tested in the qualified build. Profile detail lives in BBM-STD-85.

Upgrade assessment records affected models/links/families/templates/plugins/cloud projects, unsupported dependencies, source/target full builds, backup hashes, interruption owner, migration tests, recipients, decision/effective date and rollback evidence. Revit cannot save an upgraded native file back to an earlier major release. Rollback reopens the preserved old baseline with its original toolchain and restores approved state/links; it is not a down-save. Do not replace a shared project or upgrade links during this writing task. Never install a newer seed solely because its filename is higher.

4.1 Seed upgrade#

The office template BBM-GEN-TMP-R23 is authored in Revit 2023, while new work uses a supported release. Upgrade a copy of the template to the qualified build of each supported release in use, run the section 5 fixtures, record the upgrade test and new hash and publish it through the manifest. Library and template content is saved in the template's authoring release (currently Revit 2023); content is not upgraded inside the library and an upgraded copy is never saved back ( as refined by, BBM-STD-91).

5 Isolated fixtures and release evidence#

Create isolated new projects from the nominated seed, retaining its exact hash. For ARC fixture place the wall/door/room and equipment/valves specified in the workbook, load native content and shared definitions, inspect warnings and IDs, create plan/section/schedule/tag and A1 sheet, test coordinates via BBM-STD-63 and parameters via 72, then export/reopen in the frozen receiver. Verify missing property/wrong GUID/unsupported family/newer-major faults fail and the positive specimen preserves all mandatory content. Test phasing and each filter interaction separately. Native fixtures are specifications here; no RTE/RVT/RFA or export is generated.

Release dependencies must join a manifest asset, dictionary/TXT/binding revision/hash, coordinate profile, family/tag/font/lookup asset and view/export/plot presets. Build/receiver/settings and evidence fields are editable. Test records capture expected and actual results, input/output hashes, operator/date, independent reviewer, disposition and scoped recipient acceptance. The Release checklist links test IDs and requires complete content, compatible licensed tools, no unsafe/unapproved dependency, native open/create, printed readability and receiving persistence. Native readiness requires actual passing evidence for the exact release; these records remain Not executed/Hold.

6 Distribution change and acceptance#

Custodian nominates one exact baseline per use/discipline, independent QA checks fixtures, BIM Manager recommends office release, delegated office/project authority approves within scope, and actual recipients acknowledge. Publish a read-only approved manifest reference through the standards register; retain old project baselines and migration crosswalks. No author edits the shared master in place. Any dependency/build/view/filter/property/coordinate change triggers impact review and relevant regression tests, ChangeID propagation to BEP/TIDP/MIDP and recipient notices. Recover using preserved hashes and actual old toolchain. A native file is ready only after the applicable application and receiver checks, not because this editorial pack is complete.

References#