BBM-STD-71-MATERIALS-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review
1 Scope identity and approval states#
This standard covers /066. Material curator controls the reusable definitions and release manifest; specification lead owns product/performance selection; competent structural/thermal/design leads approve analytical uses; independent reviewers verify the actual source, native and receiving evidence. Follow BoD, templates, drawing outputs, dictionary and Manual. Use the editable material register and release pack.
The existing server route BABOOM-BIM-STANDARD/02-LIBRARIES/02-MATERIALS was read-only enumerated 2026-10-16 and contained zero entries; on 2026-11-04 it holds only an intake folder 99-INTAKE, which is quarantine, not released content. There is no approved native material/texture collection established by that empty folder. This standard defines candidate records, native asset/test specifications and release controls; it neither fills the share nor claims an installed library. Use the existing library owner and template-release process, not a parallel store. Candidate, technically reviewed, curator-approved and retired content remain distinct from CDE WIP/Shared/Published/Archive and project material approval.
Allocate a stable MaterialID and unique controlled native name, revision, material family/category, source/specification/classification references, manufacturer/product where relevant, permitted use, restrictions and curator. The synthetic SYN-MAT71-A / BBM-MAT--NEUTRAL is an abstract data/appearance fixture, not an actual manufacturer product. ClassificationTable/Code/Title/Release are separate controlled BBM-STD-72 fields; this fixture claims no invented publisher code. Identity changes and property changes need lineage and an explicit old-to-new mapping, not same-name silent replacement.
2 Property meanings source and analytical uses#
Separate identity/graphics, physical, thermal and appearance asset responsibilities. Analytical-use mappings identify the geometry/assembly/calculation input and receiving field; they are not an additional universal Revit asset type. Do not assume AutoCAD, Revit LT or another receiver supports full Revit physical/thermal semantics. Record the exact application/version-specific native asset type and parameter mapping before qualification.
Technical property sets follow ISO 23387:2025 data templates (property definitions per ISO 23386:2020 through BBM-STD-72); environmental and carbon data follow the ISO 22057:2022 EPD data templates via BBM-STD-81. Every applicable property record needs MaterialID/revision, PropertyID/definition, datatype, unit, value/domain, test/declaration method, source document/edition/page/revision, applicability/temperature/moisture/orientation conditions where relevant, uncertainty/status, approving specialist and target mapping. Density, modulus, strength, conductivity, heat capacity and fire/acoustic evidence have different meanings and cannot be inferred from colour, texture or a material name. A material conductivity does not by itself establish an assembly U-value; retain thicknesses, layers, bridges and calculation assumptions. Structural strength is not elastic modulus. An image with concrete-like texture is no evidence of concrete grade.
Unknown, not supplied, not applicable and withheld are explicit states with reasons. Do not put 0 into a mandatory physical property because no source exists; a missing required property holds that analytical use. N/A is allowed only when the declared use does not require the property and the responsible owner confirms the rule. Preserve source values/units and approved converted values; record conversion, precision and receiver units. Never overwrite a source declaration with a rounded schedule value.
SYN-DATA71 R01 is the complete fictional input vector for SYN-MAT71-A: density 1000 kg/m3, conductivity 0.2 W/(m K), test slab volume 0.125 m3 and thickness 0.1 m; appearance RGB 128/128/128 and checker repeat 600 mm. These are explicitly invented test data for transformation checks, not technical product properties or code requirements. Expected mass 125 kg; for the deliberately simplified homogeneous layer only, thermal resistance 0.1/0.2=0.5 m2 K/W, excluding surface films, joints, bridges and all real-design adequacy. Receiving density expressed in kg/L is 1.0. All actual model/analysis results remain Not executed. Real library approval requires genuine controlled product/test/design evidence in place of this fictional vector for each technical use.
3 Images appearance scale and portability#
No third-party images, unlicensed textures or downloaded product photographs may enter this pack or its proposed texture fixtures. Use office-original geometric/procedural assets or newly authored original bitmap fixtures with recorded author, creation method/date, rights and permitted distribution; unknown origin holds intake. No external images are downloaded here. Technical manufacturer documents may be referenced as property evidence without copying their images into the appearance library. A copyright-free-looking image or public URL is not sufficient provenance.
Register each appearance asset separately from technical MaterialID: native asset ID/name/revision, parent relationships/shared use, colour-space/colour interpretation, maps/channels, image pixel dimensions where applicable, repeat size in model units, offsets/rotation, bump/normal/transparency meaning, real-world sample and permitted rendering uses. Editing an appearance asset shared by several materials can change all of them; inspect its consumers and duplicate only for an approved independent variant. Sharing appearance does not merge two different physical/thermal materials.
The synthetic texture test specification SYN-TEX71-CHECKER defines an original two-tone geometric repeat, 600x600 mm sample size, on an orthographic 1200 mm-wide panel with exactly two horizontal repeats and a model-scale reference. Source generation, colour space and all byte hashes must be recorded when the original asset is actually produced. A proposed original PNG would live at bundle-relative Textures/SYN-TEX71-CHECKER.png; it is not supplied by this editorial task. Native procedural realization may instead use an explicitly qualified mathematical checker with no bitmap dependency. Do not invent a bitmap hash or claim the proposed path exists.
No absolute user-machine paths, cache directories or unmanaged network texture links are accepted in a portable release. The manifest records bundle root, relative path/native procedural dependency, exact hash and rights. Test a clean relocated bundle/receiver with original search paths unavailable: all required images/maps/parameters must resolve without fallback. Inspect colour, orientation, repeat scale, seams and missing-image warnings in fixed camera/light/exposure/render settings and compare the declared model dimension. Visual realism review concerns the intended appearance only; it does not certify physical, thermal, fire or acoustic properties.
4 Library variants substitutions and retirement#
Use existing governed categories and one curator-controlled native material source, e.g. a qualified material RVT/RTE transfer specimen and optional supported material-library container under BBM-STD-65. Determine actual supported formats/builds; an.adsklib name is not proof that every asset/property/map is carried. No ASSET/RVT/ADSKLIB/bitmap or live server release is delivered here. Register dependency hashes and source/destination native names; inspect collisions before transferring selected definitions into an isolated project copy.
Technical variants receive controlled identity/revision and a documented reason: different grade, thermal property, finish, manufacturer, environment or approved project substitution is not just a colour rename. Project substitutions retain original MaterialID/spec criterion, proposed replacement, affected elements/assemblies, code/product evidence, independent design/specification decision, authorisation and notified recipients. Appearance changes alone cannot approve a technical substitution. Each material record and substitution also carries local evidence fields: Al Sa'fat credit reference (Dubai, 2nd edition January 2023; Silver Sa'fa is the statutory minimum for new buildings) or Estidama credit reference (Abu Dhabi; 1 Pearl minimum private, 2 Pearl government-funded), VOC and recycled-content evidence, UAE Fire & Life Safety Code of Practice (September 2018 edition plus emirate amendments current at project start) reaction-to-fire / facade test certificate reference, and Civil Defence approval or listing reference. For interior finishes the record carries the same field names BBM-STD-62 §2 uses: Reaction_To_Fire_Class with its test standard, and Rating_Material_Credit; the definitions live in the BBM-STD-72 dictionary. Clause numbers are taken from the edition recorded in BBM-STD-51 §3 and BBM-STD-85, not from this standard; a blank required evidence field holds the affected use. Any shared-asset edit triggers consumer review of families, templates, details, specifications, quantities and downstream analysis/exports. Retirement records reason, replacement/use restrictions and acknowledgment, retaining issued history and a compatible rollback baseline.
5 Native asset and output test specifications#
Construct future isolated specimens from the approved source vector and qualified native assets: material applied to one plain slab/cube for quantity/property mapping, a repeated-texture panel, a second material sharing then independently duplicating appearance, a schedule/tag specimen where supported and a selected IFC/analysis/receiver profile. Record exact source/asset/dependency hashes, authoring/export/render/analysis/receiving full builds, presets, hardware and source revision. Link geometry volumes and layer thickness to the same revision as the property vector.
Positive expected values are the density/mass/resistance and two-repeat fixture results in sections 2/3. Independently mutate density units without conversion, remove a required property, assign the wrong MaterialID, share-edit an unrelated appearance, change 600 mm repeat to 600 m, break the relative texture path and strip a required exported property. Each must produce its declared failure/hold rather than a healthy-looking fallback render or zero schedule. Reset from the baseline for every case. Record actual source/receiver values/units and counts, warnings, failed evidence, approved correction and independent retest. The synthetic technical vector cannot be promoted to real technical approval even when its arithmetic passes.
Compare every applicable mandatory material property, exact specification/classification and object-to-material identity, itemised schedule quantity/unit, IFC material/property mappings and recipient analytical interpretation. Exact IFC schema/entity/property and native field paths remain to be selected and tested under the exchange owner; no custom fixture field is represented as a standard IFC property. Keep quantity testing distinct from construction measurement conventions and approved design performance. Render tests include verified portability, scale and realistic appearance under recorded settings. Actual native/schedule/IFC/render/receiver test results are Not executed here.
6 Registers release and acceptance#
The workbook Register, Properties, Appearance, Native assets, Schedule, Checks, Tests and Release sheets supply a populated synthetic slice and genuinely blank reusable forms. Property values cite SYN-DATA71 R01 in this standard; unknown real source/approval fields remain held. Release requires a complete source-backed property register for the declared use, technical review by competent owners, independent source/native/schedule/exchange/output evidence, original-image rights/provenance and portable correctly scaled appearance tests. Do not accept a percentage average that hides a mandatory blank, wrong unit or unresolved dependency.
Record MaterialID/native asset/type identity, revision/hash/dependency list, technical/appearance use limits, supported releases/profiles, source/specification/BoD links, author, independent reviewers, curator authorisation and recipient scoped acceptance. Append confirmed changes to the existing standards/library index and notify affected consumers through its owner; this task edits no share. Rollback reopens the preserved compatible native/texture source and rechecks dependent properties/outputs. Editorial approval of this pack is distinct from native library release, project material selection, manufacturer certification and authority approval; all such actual decisions and native execution remain Not executed or Hold as stated.
References#
- Office Manual V0.5, BEP V0.5, glossary V0.3, BBM-STD-51/54/55/57/63/65/67/72, BoD BBM-STD-12 and MIDP/TIDP V0.3 are controlled prerequisite owners. Synthetic IDs in this standard create no office adoption, appointment or native acceptance.
- ISO 19650-1:2018, clauses 5/11; ISO 19650-2:2018, clauses 5.1.4/5.6.3/5.6.4/5.7, are reading pointers for requirements, container checks, content review and exchange. ISO 19650-3:2020 addresses operational update context; ISO 19650-5:2020 security-minded lifecycle context. Public catalogues/guidance support scope and pointers, not a licensed clause conformity audit; no paid paragraphs copied.
- IMI Framework (formerly UK BIM Framework, renamed May 2025) Part 2 ed5 and Part D ed2 inform purpose, responsibilities and review; both are archived guidance editions on ukbimframework.org/resources, checked 2026-11-04. ISO 7817-1:2024 is the current researched LOIN concepts reference; BS EN 17412-1:2020 BSI record is predecessor context. Preserve an adopted appointment edition until controlled change.
- Local evidence sources, checked 2026-11-04: Al Sa'fat Dubai green building system (DM); Estidama Pearl minimums (DMT news, 8 Jan 2025); UAE Fire & Life Safety Code of Practice, September 2018 (DCD).
- ISO 23387:2025, ISO 23386:2020 and ISO 22057:2022, checked 2026-11-04.
- Autodesk About Material Properties and Assets, Revit 2025 (checked 2026-11-04; Revit 2023 is out of support) and appearance/map scale RevitLT 2026, checked 2026-10-16: versioned asset/appearance concepts, not proof of installed physical/thermal support. Library save version and Revit support per BBM-STD-91 §2–§3. Read-only server material-folder enumeration: zero entries (2026-10-16); no imagery or property data taken from third parties.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: ISO 23387/ISO 22057 property templates in §2; UAE evidence fields (Al Sa'fat, Estidama, UAE FLS, Civil Defence) in §4; Autodesk help re-pointed to Revit 2025; references trimmed; links to Manual V0.4/BEP V0.5; spacing fixed. + cross-doc pointer pass. + folder names without dots |