BBM-STD-80-VISUALISATION-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Audience, purpose and truthful source#
This standard addresses. The visualisation lead controls scene/output production; design leads confirm represented geometry/materials; an independent reviewer checks technical truth and visual quality; the appointed design approver decides the specific design issue. Delivery authorisation and recipient acceptance are separate scoped decisions with actual role holders. A quick render is not approved design, product performance, verified site context or a permit.
Retain BoD, template/software release, family and material owners. The editable scene/output/review forms provide specifications and blank records; no third-party images, textures or native scene are supplied. BBM-STD-51 controls adopted IDs, rights and dependencies.
Before production record BriefID/revision, audience/distribution, marketing use (yes/no), decision/question, views/deliverables, source model/container/revision/hash and extraction timestamp, phase/option/zones, design criteria and permitted illustrative elements. Identify approved-for-this-purpose, provisional, illustrative and omitted/unknown elements separately. Every added object, overlay or image edit retains origin, intended effect and limitations; never silently improve an opening, remove structure, replace specified materials or imply surveyed context. Render-only changes require ChangeID and model-owner reconciliation before any source-model update.
Where the brief marks marketing use, the client confirms before release that the advertising permit required by the real-estate regulator for the emirate (in Dubai, the RERA/DLD advertising permit route) is held, and every image carries the caption "Illustrative image: not a design commitment"; the office records the permit reference given by the client and does not obtain it. SYN-VIS80 R01 asks an internal reviewer to compare proportions of an invented box on a plane, with one still and a camera move. Geometry/materials/illumination are synthetic; no people, photographs, product textures, HDRIs or scenery. No actual project, product, lighting design or site is represented.
2 Scene, tool, rights and reproducible setup#
Record scene ID/revision/hash, source/reference manifest, transformations/units/axis/origin/north, exact renderer/exporter/add-in build, CPU/GPU/driver, integrator, sampling/adaptive thresholds, denoising/seed and compositing. Qualify through BBM-STD-65; a version label is a candidate until actual build/licence/compatibility evidence exists. Render appearance cannot overwrite physical/thermal properties under BBM-STD-71.
Each asset/texture/font/material/dependency requires source URI/hash/revision, creator/licence/entitlement/expiry, allowed modifications/distribution, relative path and rights reviewer; the licence terms, owner and renewal of renderers, add-ins (for example the Enscape and Lumion folders under 02-LIBRARIES/07-PLUGINS) and asset libraries are held once in the licence register BBM-STD-94. Quarantine unknown/unlicensed content; a subscription does not grant every bundled asset's rights. Missing dependencies must warn/fail rather than silently substitute. No third-party imagery is incorporated here. Keep office libraries read-only and use their owner, never a parallel master.
The future test recipe uses Cycles CPU in the current Blender LTS release (the blender.org LTS page, checked 2026-11-04, lists 5.2 LTS, last updated to 5.2.3 on 22 Oct 2026, and 4.5 LTS), frozen with its exact build in BEP V0.5 §9.2.1 when adopted; actual full build/environment to be recorded. Blender is not in the BEP V0.5 §9.2 software register, so this recipe is fixture-only: production renders use a renderer registered in BEP §9.2/9.2.1 and qualified under BBM-STD-65, and adding a renderer row is a BEP change, not a decision of this standard. Metres, unit scale 1, right-handed Z-up; BOX80 dimensions 2x1x1 m, centre (0, 0, 0.5); PLANE80 dimensions 10x10 m, centre (0, 0, 0), no displacement; apply object scale. Opaque standard surface shaders: box linear RGB (0.5, 0.5, 0.5), metallic 0, roughness 0.5; plane linear RGB (0.2, 0.2, 0.2), metallic 0, roughness 1. No textures. CAM80 position (6, -6, 4) m, target (0, 0, 0.5), roll 0, perspective 50 mm, horizontal sensor 36 mm, clip 0.1..100 m, depth of field off. LIGHT80 square area light at (2, -2, 6) m aimed at (0, 0, 0.5), 500 W, size 4 m; world neutral grey strength 0.2. These are invented scene parameters, not lighting-design values.
Set 64 fixed samples, adaptive/denoising/motion blur/compositing off, seed 7, transparent film off. Bounce limits total 8, diffuse 4, glossy 4, transmission 8, volume 0, transparent 8. Capture clamp/caustic and all other remaining defaults before reference qualification; save exact scene/configuration/hash/build/environment and reviewer freeze as SYN-SCENE80 R01. No unspecified default is declared reproducible across builds. Reuse that frozen scene rather than recreate from current defaults. Actual native scene creation/rendering is Not executed.
3 Colour, dimensions, naming and output profile#
Select a profile per brief: working colour space, OCIO/configuration ID/hash, texture versus data-map interpretation, display/view transform/look/exposure/gamma, output colour space/ICC metadata, format/bit depth/alpha, pixel dimensions/aspect, compression and recipient display/print requirements. Separate scene-linear computation from display-encoded files; never apply the view transform twice. An uncalibrated monitor is no physical colour proof. Interpret normal/roughness maps as appropriate data, not automatically as colour textures.
SYN-OUT80 R01 is a training profile: 1600x900 pixels at 100%, 16:9, square pixels; PNG RGB 8 bit opaque; sRGB display/output, Standard view, no extra look, exposure 0, gamma 1, no curves. Pin the actual bundled OCIO configuration/hash. These are brief-specific values, not universal office resolution or physical colour accuracy. A print brief instead names physical size, effective image resolution, printer profile and proof approval; a DPI tag alone cannot set quality. Name any high-dynamic-range intermediates and their transform/recipient purpose separately.
Use the existing eight-token identity, with Rnn/state/suitability separate. Example report bundle CLI-OFF-P080-Z01-L01-RP-A-0001.pdf uses the retained RP type. Allocate any image/animation/native-scene type in BBM-STD-51's project dictionary before issue; internal STILL80/CAMMOVE80 keys are not approved external codes. Frames have controlled FrameID/zero-padded index and first/last/count in the manifest. Never overwrite a reviewed revision/hash. The brief selects native scene, editable review, lossless still and animation/container/codec; receiver support must be tested.
4 Still, animation and review-image workflows#
Still workflow: freeze model/scene; produce a proof; compare geometry/material/camera to source; render final profile; inspect full frame and critical crops at delivery size; release the reviewed revision with caption/status, manifest and permitted recipients. Markup is a separate layer/derivative joined to base-image hash, source revision, camera and view/region. Crops/enhancement cannot conceal a relevant omission; preserve original/derivative lineage.
Animation workflow: approve camera keyframes/path/interpolation, frame range/rate/time basis, object motion, profile, titles/legend and sound rights if used; render controlled image sequence then encoded derivative. Check missing/duplicate frames, noise/flicker, clipping, text and actual playback duration. SYN-CAMMOVE80 uses frames 1..240 inclusive at 24 fps, 10 s; camera moves linearly from (6, -6, 4) on frame 1 to (-6, -6, 4) on frame 240, continuously aimed at (0, 0, 0.5), roll 0, unchanged lens/sensor. Review 1, 120, 240 plus entire playback. Actual encoder/container/profile/full build must be approved before the real run; no video is supplied or claimed approved.
Apply Manual 9.4, Directory recipient controls and records. Cloud rendering, AI image edits, uploads and public sharing each need approved data/service/rights scope before transfer. Inspect metadata/file paths, annotations, location/security content, thumbnails and embedded dependencies. Scrub only the authorised derivative, retain original evidence, and verify allowed/denied access, expiry/revocation and download/retention. A private checkbox/password is not tested access control.
5 Technical review, comments and approval trace#
Compare authoritative source and final output: dimensions/phase/option/visibility and object counts; material/specification/appearance mapping; orientation/camera projection and clipping; lighting/sun assumptions; complete licensed dependencies; colour/alpha/encoding/resolution; text legibility and actual delivery-viewer appearance. Fixture checks require BOX80 dimensions 2x1x1 m, opaque neutral materials, visible box/plane, no missing dependency. Check geometry in the source; perspective appearance is not a measurement. Colour cannot establish U-value, fire resistance, daylight or energy performance.
Actual client/user comments need CommentID, commenter authority, dated image/source revision and region, requested change, owner, response/disposition, correction and independent retest. Design approval, visualisation approval, issue authorisation and receiving acceptance have distinct scopes/signatures. SYN-COM80-01 changes box length 2 to 2.2 m; record SYN-CH80-01/SYN-MOD80 R02, new scene/output revisions, rerun source/material/camera/output checks, and resubmit. No real client or sign-off is invented. Retain R01; approval never silently transfers to altered output.
6 Repeatability, adverse cases and release#
Workbook Brief, Scene, Assets, Output, Review, Comments, Repeatability, Acceptance tabs have paired empty forms. Recipe/settings are specifications; native scene, render runs and recipient tests remain Not executed. Future operator creates and freezes SYN-SCENE80 R01, records builds/input/config hashes, and renders twice unchanged on the same pinned environment. Compare manifests, dimensions/profile, dependency warnings and full/crop views. This deterministic training test requires identical decoded pixel buffers on that same environment; exclude container timestamps/metadata. If different, report Fail and obtain investigated/reviewer-approved criterion change before claiming repeatability. No cross-device pixel identity is assumed.
Reset each adverse case independently. T80-01 puts near clip through box: Fail; restore 0.1 m, rerender. T80-02 uses unresolved texture path: Fail even if fallback looks plausible; restore procedural material. T80-03 applies display transform twice: Fail; restore once-only transform and compare decoded output. T80-04 omits frame 120: 239/240, Fail; rerender 120 and verify 240/240. T80-05 substitutes R02 source under R01 caption: Hold; correct source/scene/output/approval lineage. T80-06 allows unapproved public access: Hold; use approved incident/revocation process and requalify permitted/denied access without publishing real sensitive data.
Release exact source/scene/output revisions only after producer checks, independent design/material/visual QA, licensing/data review, scoped delivery authorisation and recipient viewing evidence. Mandatory defects hold affected issue regardless of average visual score. Register dependencies/output hashes/comments/sign-offs and unresolved exclusions. Office adoption, build/licence qualification, actual scene repeatability and real design/receiving decisions remain activation holds; quick-render exercises never close them.
References#
- Matrix, plan 33; office guide 29 quick renders, guide 37 review images and linked BoD/template/family/material/record owners.
- Blender LTS releases and current render manual, checked 2026-11-04 (the 4.0 manual is kept only as history of the first draft), compared with Autodesk render sharing: technical/recipient questions, not installed capability. No source imagery copied.
- NIBS v4 BEP and BCA Guide v2, historic benchmark (2013), use-led review context; office procedures here are original.
- ISO 19650-2 clauses 5.6/5.7 and IMI Framework (formerly UK BIM Framework, renamed May 2025) archived Guidance Part A ed2 are reading pointers; verify licensed text before conformity claims. ISO 19650-1, -3, -5, ISO 7817-1 support lifecycle/security/current LOIN context; BS EN 17412-1 is legacy predecessor where appointed.
- UAE applicability remains with BBM-STD-57 and BBM-STD-85: DM building permit circulars index, ADM BIM Code of Practice, October 2020, DDA design; Dubai Land Department for the real-estate advertising permit route (requirement confirmed by the client per project). Visual review is not statutory approval. Primary research checked 16 October 2026; no paid-standard paragraphs reproduced.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: Blender 4.0 replaced by the current Blender LTS frozen per BEP V0.5 §9.2.1; Blender marked fixture-only outside the office software register; marketing-use field (advertising permit, "illustrative" caption); asset/font licences pointed to BBM-STD-94; reference labels corrected; IMI Framework naming; links to Manual V0.4/Directory V0.3; spacing fixed. + cross-doc pointer pass. + folder names without dots |