ArchHubBABOOMDownload

Family authoring native library and release

BBM-STD-69 · V0.2 · Content curator owns admission/release and dependency history

Download WordFormsAll standards

Ribbon tools that apply it: Load BABOOM Shared Parameters, Family Library, Detail Library, Clean Family, Thumbnails, Family Tools, Room Data to Elements, Thresholds from Door Saddle

The library it governs: the family catalogue

BBM-STD-69-FAMILY_STANDARD-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review

1 Scope source and family routes#

This standard consolidates Manual 6.1/8.2.2 and guides 26/27/35/37 for /063. Content curator owns admission/release and dependency history; category/discipline author produces native content; independent content and discipline reviewers check intended use; receiving team accepts the exact release. Follow Manual, BEP, EIR and LOIN, template release and dictionary. Use the editable creation and release pack. Written manufacturer-family benchmarks are specification examples only, not a delivered native library or QA result.

The existing published native library is BABOOM-BIM-STANDARD/02-LIBRARIES/01-FAMILIES; BBM-FAMILY-LIBRARY-INDEX.csv and CATALOGUE.html are its existing index and user browser. Users consume read-only; curator changes pass through the existing library-production owner, never this writing lane. Read-only observation on 2026-10-16 found 878 index rows/878 distinct relative paths. Index 342182 bytes has SHA-256 6d4ecac1310377706ce3937e98a64a5fc097f0d07784a617d450691cd5ae45a4; catalogue 526197 bytes has SHA-256 0abe792428db237940692fdcc1d8f348fcc1f43eb59aa0ec8075282850081531. The index's sha256_16 is a 16-character prefix, not a full release digest. One sampled RFA prefix was independently verified by reading its bytes; that does not validate all 878 files, their save releases, rights, types, geometry or receiving behavior. Re-read on 2026-11-04 (read-only): the index has 889 rows, modified 2026-10-29, SHA-256 5b586168d9ff202f747b85bf14d0caaacbee48485bf24529aa5712d6cb504aaa; every use quotes the snapshot it relied on (reconciled with BBM-STD-72 §2).

Select route by function: system families use controlled RVT/RTE type-transfer specimens; loadable component/annotation families use RFA and their appropriate RFT; in-place content needs a project-specific justification and cannot become reusable simply by renaming. Use a category/hosting template suitable for wall, face, workplane, level-based, adaptive or annotation behavior. Saving an existing RFA under an RFT name does not change its hosting/category template. Rebuild only the approved required content with preserved property/function mapping and comparison evidence; keep original bytes.

2 Category identity parameters and graphics#

New adopted content follows ORG-DISC-CAT-TYPE-DESC-vNN per Manual, with approved token lists, meaningful neutral description and lower-case vNN. Example BBM-ARC-FRN-CAB-STORAGE-v01 is synthetic. Native type names are controlled size/option labels, e.g. W0600-D0400-H0800, separate from occurrence Asset_ID and external eight-token container grammar. Existing published identifiers are immutable references until an approved migration maps aliases, dependencies and recipients. A published abbreviated name or folder code is not permission to silently rename it. Title blocks keep the published series BBM-G-TTB-A0…A3 (ORG BABOOM, the library's published general token G, CAT TTB, size as DESC): BBM-G-TTB-A0 and BBM-G-TTB-A1 exist; BBM-G-TTB-A2 and BBM-G-TTB-A3 are created in the same series; G here is not the BBM-STD-93 Survey ROLE. Conflict W3-C01 records this distinction; it is registered in the Decisions Log, discipline/role tokens come from the one code dictionary BBM-STD-93 and BBM-STD-51 owns the register.

For each family record purpose/stage/LOIN, actual category/template ID/hash, host, origin/reference planes, insertion/rotation behavior, type list, parameter definitions/GUIDs, datatype/unit, type/instance binding, value domain, formula/association dependencies, material and nested-content links. Reuse BBM-STD-72 definitions; matching display names do not prove identity. Manufacturer/product properties are mapped to ISO 23387:2025 data templates where a template exists; each property definition follows ISO 23386:2020 through the BBM-STD-72 dictionary, and environmental (EPD) properties use ISO 22057:2022 via BBM-STD-81. Do not invent missing Asset_ID/shared GUIDs or replace a valued vendor property with an empty office alias. Type properties apply only when valid across every occurrence/type as defined; occurrence identifiers and host/system/location relations remain correctly scoped. Classification Pr/Ss and release/title relationships follow the controlled dictionary. Cleaning-policy D14 tables contain office proposals, not universal crosswalk equivalences or native per-type proof.

Use native geometry and reference frameworks sufficient for the use; control cut/projection, subcategories, coarse/medium/fine, plan/elevation/3D visibility, symbolic lines and materials. Avoid detail too small for intended plotting/coordination unless required. Verify actual category-specific visibility behavior in recipient views; a plan mask cannot hide bad host cutting or geometry. Use Manual 4 and BBM-STD-67 for graphics; do not copy an external template's whole standards set without a reviewed need and duplicate-resolution plan.

3 Constraints flexing connectors and catalogues#

Flex the reference skeleton before forms, then every type after geometry, voids, nested content, formulas and material associations. Record min/nominal/max and mixed extremes, expected dimensions/clearances/origin and invalid-input behavior. Test formulas for unit consistency, circular dependencies and boundary values; reject warnings rather than accepting dialogs. Check host thickness/orientation, flips/mirroring/rotation, placement and reloading with both type/instance value-preservation choices as supported. Named constraints and associations must survive reload; a screenshot at nominal size is insufficient.

SYN-FAM69-CAB is an unhosted Furniture bounding-envelope specimen: minimum W/D/H 400/300/600 mm, nominal 600/400/800 mm, maximum 1000/600/1200 mm and mixed 400/600/1200 mm. Origin stays at base centre; overall envelope follows W/D/H without inverted solids or detached parts. This is a family-behavior test, not a cabinet design. Store source values separately from measured native/receiver results. Other representative fixtures are SYN-FAM69-DOR (wall-hosted door cutting two declared host thicknesses), SYN-FAM69-VLV (piping valve with two correctly associated typed connectors), SYN-FAM69-ANO (annotation/text/visibility at two intended scales), and SYN-FAM69-WAL (system-wall RVT transfer), each with its own purpose and accepted test criteria.

For MEP, specify connector domain/classification/type, logical key, position/orientation, dimensions, flow direction/configuration, units and linked behavior. Test in a small connected system/schedule; graphical arrows alone do not prove propagation. Valve fixture uses logical IN/OUT on SYN-HS69 (Piping, HydronicSupply): connectors at local x=-50/+50 mm, flow fixture 1 L/s mapped to 0.001 m3/s in SYN-X69 R01, with declared reference supply/sink ports. This is a conversion/connectivity fixture, not valve sizing. The cabinet positive nested fixture has one unshared knob, one scheduled parent cabinet occurrence and no separately identified child asset; an added shared/independent child changes declared object count and must be reviewed. The door positive specimen is a 900x2100 mm test opening cut through each isolated 100/200 mm thick, 4000 mm long, 3000 mm high host, without joins; inspect both faces and compare the opening void. All these values are synthetic behavior inputs only. Valve fixture uses logical IN/OUT on one declared piping system; actual native category/enums and connected reference equipment are qualified in the chosen build. Material parameters reference approved library IDs; no image/material purge based solely on an empty current view. Nested shared status is deliberate: record parent/child IDs, dependency revision, visibility, tag/schedule and IFC counting expectations; verify no doubled independent assets or lost child IDs.

Where many types need catalogues or lookup tables, preserve original type names/values unless an approved mapping exists. Register file encoding/delimiter, datatype/unit tokens, primary keys and family revision relationship. The synthetic cabinet catalogue specification has three exact type keys W0400-D0300-H0600, W0600-D0400-H0800 and W1000-D0600-H1200 with matching W/D/H mm values. Load one selected type and verify exact dimensions/properties/count; unknown/duplicate keys or mismatched units fail. No TXT catalogue or lookup file is delivered as native-tested by these forms.

4 Intake rights cleaning and custody#

Intake records supplier/source, acquisition date, original hash, authorship/rights evidence, allowed modification/use/distribution, dependency rights, technical data revision and accountable reviewer. Unknown rights holds that use; a public download link or material texture availability is not permission. Preserve original quarantined bytes; approve a bounded change list and run isolation/trust checks before project loading. Curator controls supported Revit releases/full builds, save/upgrade route and exact native/template dependencies. Library master save release = the office template's authoring release, the oldest Revit release in office use (currently Revit 2023), as set in BBM-STD-91 §3 ( as refined by; supported majors 2024–2027), saved in the build recorded in BBM-STD-91. Revit 2023 is out of Autodesk support: it is the legacy authoring release, a recorded risk, never a project release. No upgrade inside the library and no save-back to an older release; newer projects upgrade a copy on load, and when the office stops using its oldest release the curator releases a tested upgraded copy per BBM-STD-91 §3. Review annually and whenever Autodesk changes its supported-version list. Do not infer a file's save release from path, filename or mtime. Upgrade only a protected copy and retest; unsupported save-back is not recovery.

System-family routing references are not RFA support; conflicting type classifications require review/splitting rather than first-row precedence. No library cleaning, native save, placement or server write is performed by this standard-writing task.

5 Native specimens and release qualification#

Use Fixtures, Flex, Properties, Cleaning, Checks, Tests and Release forms. Capture exact RFA/RVT/catalogue/lookup/material/dependency hashes; authoring/receiving/exporter full builds/presets and hardware/workload. Native checks cover category/host/origin, every type and prescribed extremes, stable values/GUID/bindings/formulas, native tags and itemised/grouped schedules, view/printed graphics and shared-nested counting. IFC check records agreed schema/entity/classification/property mappings, IDs, dimensions/materials/units and source/receiver counts. IDS/property passes supplement independent geometry/design/readability checks. Unsupported required fields hold release or require an authorised complementary profile, never silent omission.

Measure load/place/regenerate/schedule/export behavior in representative sparse and dense contexts on recorded hardware, with approved purpose-specific limits and actual timings/file sizes. There is no invented universal family MB/time threshold. Qualify every advertised supported native release/receiver combination; a successful newer release does not prove older compatibility. Tests specify positive and independently reset adverse cases: invalid flex extent, GUID collision/lost value on reload, wrong connector units/system, duplicate catalogue key, nested double count, export property loss and unsafe cleaning of a valued/dependent parameter. Retain separate failed evidence, correction and competent independent retest.

6 Release manifest change and recovery#

Manifest records immutable content ID, actual native family/type identities, revision, source and all dependency hashes, rights/use limits, supported builds, applicable uses/LOIN, author/checker/curator, test evidence, approval and publication/index/catalogue revision. New vNN follows approved geometry/schema changes; assess downstream tags/schedules/materials/exchange and existing instance values before replacing. Preserve earlier releases/history and notify affected recipients under one ChangeID. Retirement records replacement and old-to-new mapping, last supported use and withdrawal acknowledgment; no silent deletion or batch-renaming of published assets.

Publish only through the established curator's release mechanism after all mandatory checks and rights/design approvals for the scoped uses. A real future release reconciles index paths/type list/classification and full hashes against actual native files and CATALOGUE targets, then tests read-only consumer access and load/receiver behavior. File presence, library folder counts, benchmark examples and filled synthetic reports never count as native acceptance. Rollback reopens the preserved compatible native release and restores its index/dependency mapping through the owner; do not overwrite a live library to experiment. Producer/content review, discipline engineering review, curator authorisation and recipient acceptance are separate records. All actual native tests, rights/adoption decisions and library changes remain Not executed here; the published library was only inspected read-only.

References#

Document history
VersionDateChange
V0.116 October 2026First controlled draft.
V0.24 November 2026closure: cleaning-policy source restated in §4; library save release tied to BBM-STD-91; W3-C01 sent to the Decisions Log; ISO 23386/23387 property mapping in §2; references trimmed and re-checked; links moved to Manual V0.4/BEP V0.5; number spacing fixed. + cross-doc pointer pass. + template alignment (..148) + folder names without dots