ArchHubBABOOMDownload

Properties shared parameters and classification

BBM-STD-72 · V0.3 · Maintain one property dictionary connecting requirements, native bindings, tag/schedule presentation and receiving schemas.

Download WordFormsAll standards

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

1 Purpose identity and control#

Maintain one property dictionary connecting requirements, native bindings, tag/schedule presentation and receiving schemas. This standard covers, and. The Information Manager owns dictionary revisions; the content curator maintains controlled definitions; discipline designers own value sources; an independent checker verifies the scoped result. Office adoption and actual holder/delegation remain pending under BBM-STD-51 and BBM-STD-55.

Use Manual V0.5 section 3.2, BEP V0.5 sections 8.6 and 8.11, AIR and EIR and LOIN. The editable dictionary and tests are the maintainable drafting records, not a newly approved native definition file. ISO 19650-1:2018 clauses 5 and 11 and ISO 19650-2:2018 clauses 5.1.4 and 5.6 are reading pointers for requirement-led information and production controls; verify licensed text before formal compliance claims.

Each Dictionary row has stable PropertyID, canonical key, explicit meaning, datatype/unit, allowed values, applicability/source and accountable owner. Bindings and Mappings join that ID, never the visible label. Add semantic revision, actual approver/effective date and exact dictionary hash to the project control record. Missing these fields holds production adoption. Alias records may translate names but cannot collapse different meanings or conflicting values. Asset_ID is the office key; generic D13 AssetIdentifier and AssetTag are mapped aliases, not a second office identity. Financial-register identifiers and physical tags remain separate unless a relationship is authorised. Never invent an existing GUID.

Dictionary entries requested by other standards (each gets a PropertyID, datatype, unit and owner from the curator before use; held until then, no GUID invented): Fire_Rating as integer minutes plus Fire_Rating_Standard and Fire_Rating_Source (Manual V0.5 §3.2); date fields as text YYYY-MM-DD checked by rule VAL-DATE-01 (BEP V0.5 §8.6.1); room fields OccupancyClass, OccupantLoadFactor_Source and AccessibilityRequirement (BBM-STD-58 §2); plant fields Native_Adaptive, Irrigation_Demand_Basis and Rating_Credit_Ref (BBM-STD-61 §2); finish fields Reaction_To_Fire_Class (with test standard) and Rating_Material_Credit (BBM-STD-62 §2, BBM-STD-71 §4); element and space classification Classification_Code with the pinned Uniclass release, IfcSpace rooms classified with SL (BBM-STD-58 §1).

2 Observed source and proposed native bindings#

Read-only inspection on 2026-10-16 found 120 PARAM definitions in BABOOM-BIM-STANDARD/02-LIBRARIES/05-PARAMETERS/BBM-SHARED_PARAMETERS.txt; SHA-256 e85adf1e1a505f31737f9aeaa06bdaee6967f3b4a12758e40e1d0228ce962950. The family CSV has 568 rows; SHA-256 ccb2ced96efd2e3b91cfaf70a5279dcd9800ca5a583ba3d6d94f9bbef9ceb38b. It indexes content and classification labels; its short hashes and populated codes do not prove RFA contents, actual bindings, native release or current code validity. Only the reviewed subset below is proposed for reconciliation; the remaining definitions stay unadopted pending the curator's full applicability assessment. No share file was edited or copied as a competing master.

Re-read on 2026-11-04 (read-only): the TXT now holds 122 PARAM definitions, modified 2026-10-30, SHA-256 f62febe1d1692e05f426b87f453fa613b33368cf7bbefa9c5b4d0d9ae6cc8a60; the reviewed subset below must be re-confirmed against this revision before adoption. BBM-SHARED_PARAMETERS.txt must carry every Manual V0.5 §3.2 core parameter under its canonical name — Classification_Code (with ClassificationTable, ClassificationTitle, ClassificationRelease), System, Fire_Rating (with Fire_Rating_Standard, Fire_Rating_Source), Asset_ID, Export Exclude and Model Origin OK? — plus the COBie parameters of the EIR's COBie version (default COBie 2.4); the file is updated in the next template pass, with GUIDs assigned once by the curator and never invented. The family index is BABOOM-BIM-STANDARD/02-LIBRARIES/01-FAMILIES/BBM-FAMILY-LIBRARY-INDEX.csv: BBM-STD-69 read it with 878 rows (SHA-256 6d4ecac1...) on 2026-10-16 and on 2026-11-04 it has 889 rows, modified 2026-10-29, SHA-256 5b586168d9ff202f747b85bf14d0caaacbee48485bf24529aa5712d6cb504aaa. The 568-row file (ccb2ced9...) quoted above is an earlier snapshot whose filename was not recorded and which is no longer on the share; it is kept only as history. The index grows between reads, so every use quotes filename, row count, date and full hash, and all three snapshots are recorded in the BBM-STD-51 register.

PropertyObserved definition and GUIDProposed use and qualification
P72-002 Classification_CodeClassification.Uniclass.Pr.Number; 8212e2e8-d020-4127-bada-a9cc7f5f4dcc; TEXTType when every occurrence shares the product code; exact Pr table/release
P72-004 SystemClassification_CodeClassification.Uniclass.Ss.Number; f16eb500-0976-4c80-b5d1-082470821ef8; TEXTSeparate Systems meaning; never overwrite Products code
P72-006 Zone_IDZONE; b74c1318-b14e-496c-b132-cef36e96a24e; TEXTInstance only where applicable; join controlled zone register
P72-008 DesignFlow_m3_sAIR-FLOW; fe7d605e-a591-46a0-8078-2906c565f42b; TEXTLegacy source is text, not a native flow spec. Parse only an approved unit-bearing source; do not change its datatype in place
P72-001 Asset_IDNo unambiguous canonical shared definition establishedReconcile existing model/family definitions and identity meanings before allocating; native tag/export activation held

The TXT describes definitions and groups, not actual project category bindings or whether a parameter is instance/type. Every binding above is proposed until a protected project/family inspection records categories, scope, spec/group, shared GUID, tag label and schedule field identity. Use the same definition GUID in the element and compatible tag. A parameter recreated with the same name is a different definition. Retain existing values, export a before snapshot, approve migration, reload only an isolated specimen, and compare after values and identities before rollout.

For AIR-FLOW, the fixture 1200 L/s converts to 1.2 m3/s by dividing by 1000. Bare 1200, a mixed decimal separator or an unknown unit is rejected. Preserve the legacy text/GUID and record the approved output conversion. If a native measurable-flow parameter is required, the curator must govern a new compatible identity/migration and prove tags, formulas and exports; it is not allocated by this pack. No formula may silently substitute zero for missing/inapplicable information.

3 Classification and managed mappings#

Retain Uniclass 2015 as the office default; the canonical fields are Classification_Code plus ClassificationTable/Title/Release, and "Assembly Code" or "Classification Code (Uniclass)" are mapped aliases. For this draft fixture freeze the July 2026 release: Products Pr v1.43 and Systems Ss v1.43 for objects, Spaces/locations SL v1.36 for rooms, areas and zones, and Activities Ac v1.27 where activities are classified; NBS's live download page showed these releases on 2026-10-16 and again on 2026-11-04. The same release-pinning rule applies to every table. NBS tables use CC BY-ND 4.0: retain attribution, release and unmodified table identity; keep office mappings separately and do not add local codes to an NBS table. Actual adopted table files/hashes and licence review are required before activation; the Uniclass licence is held once as a LicenceID (LIC-nnn) entry in BBM-STD-94 and each pinned table file records that ID. Classification is purpose-led under BBM-STD-54, not a universal requirement for every object.

Dictionary concepts follow ISO 12006-3:2022 (the object-oriented framework behind the buildingSMART Data Dictionary, bSDD) together with ISO 23386:2020 and ISO 23387:2025. Each Dictionary row carries an optional bSDD_URI: where an office property matches a published bSDD property, record its URI and dictionary version; where none matches, the row stays office-only and is not published to bSDD by this standard.

Library-only exception: the detail library (BBM-STD-70) keeps its pinned MasterFormat section/folder classification because its published IDs depend on it. MasterFormat is not an office classification; each detail carries a Uniclass Pr/Ss mapping with the pinned release, and the curator records the MasterFormat edition actually used.

The observed library storage-unit example uses Pr_40_30_87 and Ss_40_15_35_80. NBS's live taxon pages confirm their titles, but do not validate all 568 library rows. In the synthetic SYN-CAB01 fixture the product code describes the cabinet and the Ss code describes its system context. The native library row remains source evidence, not the synthetic project itself. An IFC class is not a Uniclass code.

For client/authority/cost mappings record FromSystem/Table/Release/Code, ToSystem/Table/Release/Code, relationship (exact/broader/narrower/none), purpose, evidence, reviewer and effective ChangeID. No one-to-one mapping is presumed. ADM's October 2020 Code of Practice section 4.2 refers to Uniformat II; that is an appointment-specific interface requiring its exact adopted issue and scope, not authority to replace the office Pr/Ss fields. Unknown target codes hold affected exchanges. On any classification update, compare adds/retirements/renames, affected type/instance counts, requirements, schedules, exports and recipients; approve/retest before making it effective. Preserve old received classifications and the historical crosswalk.

4 Controlled definition file formulas and lookup assets#

The server TXT stays the observed master candidate until its owner adopts a named revision/hash. Only the curator may release changes through the supported Revit UI/API; authors do not hand-edit shared definitions or switch to an uncontrolled personal file. Register dictionary revision, TXT URI/hash/encoding, binding-table revision, lookup assets, authoring full build, change owner and approval as one release dependency set. A model already containing definitions must be reconciled; pointing at a TXT does not update stored model values.

Lookup specification SYN-LK72 R01 has CSV header TypeKey,NominalDiameter##length##millimeters, unique keys SYN-V50 and SYN-V80 and values 50 and 80. This is a fixture specification; no lookup asset is loaded. Qualify exact Revit size-lookup syntax/encoding/build and missing-key behavior in isolation. Fail on duplicate keys or unsupported units. Derived test property Flow_L_s = DesignFlow_m3_s * 1000 is a schedule/export calculation with m3/s-to-L/s provenance; it is not an additional independently editable source. Native category/spec/formula restrictions must be tested. Record tag family/revision/GUID, schedule field, itemisation, sorting/filtering, totals and display precision; a grouped count cannot prove per-instance uniqueness.

5 IFC IDS COBie cost and asset destinations#

The Mappings tab defines candidate paths by PropertyID with schema/profile revision, applicability, units, conversion and null handling. Use separate IFC classification associations for Pr and Ss under the agreed exchange profile. Asset_ID maps to the explicitly agreed BBM_Exchange.Asset_ID custom-property route and proposed COBie Component.Name; native UniqueId/IFC GlobalId remain distinct identifiers in the crosswalk. These are office profile proposals, not standard IFC/COBie property claims. Define the exact IFC schema/entity/property set (default IFC 4.0.2.1 Reference View), IDS 1.0 requirement/checker per BBM-STD-89 and COBie edition/import fields (version as specified in the EIR; default COBie 2.4, NBIMS-US V3, unless the EIR names COBie v3) before use. No schema name proves exporter/receiver capability.

Mappings profile DM-PERMIT: for a Dubai Municipality BIM permit submission (circular 9-1-2 of 13 Oct 2023; circular 9-1-3 of 15 Jan 2026, effective 1 Apr 2026) the Mappings tab maps PropertyIDs to the Model Attribute Matrix issued with the current Dubai BIM Standard (buildindubai.gov.ae/bim), downloaded at project start and recorded in the BEP information-requirements section with its file hash. The profile stays on Hold until that matrix is downloaded; no attribute name is invented from secondary sources. Triggers and the submission route are owned by BBM-STD-85 and BBM-STD-57.

Where native scope is Type and destination is occurrence, retain occurrence-to-type joins and test every relevant occurrence. Do not apply one type's value indiscriminately to mixed classifications. Cost/asset systems receive quantities/units and stable foreign keys under their selected dictionary; no prices are included here. Keep missing, unknown, withheld and not applicable distinct. A mandatory applicable blank fails; an inapplicable valve airflow can be N/A with its rule. IDS checks agreed information requirements; geometry, conversion correctness, source truth, safety and full application acceptance require separate checks.

6 Filled examples tests and release#

The workbook contains a synthetic cabinet classification example and the three AIR/EIR asset records AHU-001, VLV-001 and VLV-002; source revisions are R01. Dictionary, Binding, Mapping and Alias joins are explicit. The Examples tab is a test specification, not an exported native payload. Classification for the mechanical fixture remains not required by its narrow EIR; do not invent a code merely to fill a cell. Independent adverse tests reset from the positive fixture: missing Asset_ID, duplicate asset key, same-name/different-GUID tag, wrong flow unit, Pr/Ss confusion, lost export value and incompatible lookup key.

Before use, record exact input/output hashes, authoring/export/receiving full builds and presets, operator/date and evidence for native category binding, itemised schedule, tag identity, lookup/formula behavior, IFC/classification and recipient reimport. Compare every mandatory applicable field and identifier/value/unit against the approved snapshot. Producer check, independent technical review, submission authorisation and recipient scoped acceptance are separate records. Unresolved mandatory failures hold affected release regardless of an overall coverage percentage. All actual tests here remain Not executed; no RFA/RVT/IFC/IDS/COBie native asset is delivered or claimed ready.

References#

Document history
VersionDateChange
V0.116 October 2026First controlled draft.
V0.24 November 2026closure: DM-PERMIT mapping profile in §5; links to Manual V0.4 §3.2 and BEP V0.5 §8.6/8.11; family index named and the 568/878/889-row snapshots reconciled in §2; ISO 12006-3:2022 and bSDD in §3; Uniclass SL/Ac tables in §3; MasterFormat library-only exception for the detail library (from BBM-STD-70); /121 applied; IMI Framework naming. + cross-doc pointer pass. + template alignment (..148) + folder names without dots
V0.35 November 2026Standard watch no. 1: ISO 12006-2:2015 status corrected to last confirmed 2020, to be revised (ISO/DIS 12006-2.2 under development)