BBM-STD-61-LANDSCAPE_MODELLING-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
Revision history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | Initial controlled WIP draft. |
| V0.2 | 2026-11-04 | Closed audit rows: plant/irrigation rating fields, IDS 1.0 property checks (LSC-IDS), single DM circular index URL; DDA Circular 400 pointer; IMI Framework naming; current set links; spacing fixes + cross-doc pointer pass. |
1 Scope uses and ownership#
This annex covers: terrain/external levels, planting, hardscape, landscape furniture and irrigation interfaces. Use BoD, EIR and LOIN, survey/civil, templates, dictionary and federation. Preserve Manual V0.5 authoring, coordination and issue procedures. The editable landscape pack contains LOIN, planting, interfaces, quantities and release forms.
The landscape lead owns landscape intent and authoring; competent horticultural/irrigation designers validate planting and watering criteria; civil owns agreed terrain/drainage/utilities; electrical owns lighting and supplies; the coordinator checks interfaces; a distinct competent checker reviews; scoped authoriser/recipient makes separate decisions. Confirm actual appointments/boundaries/dependencies before modelling. No plant performance, hydraulic design, accessibility approval or jurisdiction compliance is established by a model or this specimen.
| Purpose and agreed exchange | Required scope | Limit |
|---|---|---|
| Brief/option decision | Site/source boundaries, proposed/retained zones, terrain concept, planting strategy and assumptions | Indicative forms are not selected nursery stock or surveyed terrain |
| Spatial coordination | Controlled site levels, hardscape extents/build-ups, planting/root/canopy envelopes, furniture, irrigation routes and civil/MEP interfaces | Detail and uncertainty fixed by decision, not automatic stage/LOD |
| Construction/operational exchange when appointed | Approved species/product/specification, set-out, quantities, evidence, irrigation/access and maintenance instructions | Installed/as-constructed claims require actual verification under BBM-STD-75/77 |
Map these uses to actual TIDP/MIDP milestones and BBM-STD-54 geometry/alphanumeric/documentation requirements. Retained landscape, demolition/transplanting, proposed works and options have separate states; do not combine all options or symbolic canopies into plant quantities. Freeze exact source/model/revision and authoring/export/receiving builds. Unknown native category/site representation or unsupported exchange holds that route under BBM-STD-65/74.
2 Plant identity and source constraints#
Allocate stable Plant_ID per counted occurrence or controlled Area_ID for area planting, separate from Type_ID, nursery batch and asset-maintenance identity. Dictionary records species botanical name and authority/reference, common name alias, cultivar if specified, plant form, maturity/stage, scheduled supply size and units, spacing/density basis, quantity rule, source/nursery evidence and permitted substitutions. Do not infer botanical identity from a family name, rendering or generic tree icon. State source confidence and who verifies suitability to actual soil, climate, utilities, water and maintenance requirements.
Preserve type data versus occurrence-specific position/condition, existing/proposed state, survey/inspection date and source. Mature canopy, root protection and maintenance envelope dimensions require a competent project-specific source; a supply height is not a predicted mature size. Nursery stock constraints include approved source/availability date, sizes/condition, traceability and substitution/inspection authority. No botanical, survival, water-demand or performance number may be invented to fill a mandatory field. Missing required evidence holds species/installation reliance. Statutory green ratings set landscape water and planting credits (Al Sa'fat 2nd edition (January 2023): Silver Sa'fa is mandatory for all new buildings in Dubai; Estidama Pearl Rating System: minimum 1 Pearl for private and 2 Pearl for government-funded projects in Abu Dhabi (DMT, 8 January 2025); statutory minimums owned by BBM-STD-57 §2 and BBM-STD-85 §7); each plant type or area therefore also records Native_Adaptive (Y/N with source), Irrigation_Demand_Basis and Rating_Credit_Ref (Estidama Pearl or Al Sa'fat credit). Local landscape design manuals are not confirmed in this revision and are added through BBM-STD-57 when assigned.
The synthetic Type PL-T01 is labelled TRAIN-TREE-A, deliberately not a botanical species claim. Three proposed occurrences P-001/002/003 use that type. Botanical/cultivar/nursery/supply-performance evidence is Unverified and must be populated before real procurement/design use. A test root envelope radius 1000 mm is a declared geometric fixture only; it is not a recommended protection radius or horticultural criterion.
3 Terrain irrigation utilities and maintenance interfaces#
Use the single BBM-STD-63 survey/datum baseline; retain source date, horizontal/vertical reference, units, transformation, uncertainty, control points, measured/interpolated/assumed surfaces and limits. Civil and landscape agree the owner of existing/proposed terrain, grading, retaining edges, drainage and interfaces; reference the owner's model rather than recreating a competing terrain surface. A repeated visual mesh is not a second authorised earthworks quantity source.
Irrigation design links IrrigationZone_ID and system/lateral/emitter identities to planting IDs/areas; record water-source quality/availability, design basis, flow/pressure/unit/source, connection owner, controls, isolation, drainage and maintenance access. Actual hydraulic calculations and plant demand remain with competent designers. A drawn pipe connection is not proof that a planting zone receives an adequate supply. Check utility routes/depth, root/soil volumes, structures, waterproofing, drainage and future access against approved constraints. Underground records not surveyed remain explicitly uncertain.
External lighting positions, foundations, cables/earthing, access and plant growth/shade interfaces are coordinated with electrical/civil owners; ornamental symbols do not substitute for calculations or safe access criteria. Inspection, pruning, replacement and irrigation access/withdrawal envelopes need actual source/owner and maintained routes. Significant residual risks follow Manual §9.4 with recipient acknowledgement; a generic clash status cannot approve a safety-critical interface.
4 Levels falls drainage and access criteria#
The BoD/BBM-STD-57 register supplies applicable design criteria, source clause/edition and competent reviewer for paths, ramps, crossfalls, level thresholds, drainage, water features, walls and lighting. Record criterion/value/unit, direction/run definition, source, geometry IDs, actual calculation/measurement, uncertainty and disposition. Do not import an illustrative gradient as a universal access or drainage limit. Competent civil/accessibility reviewers decide adequacy and authority requirements.
The fictional specimen SYN-L61 R01 is a 10 m by 6 m local engineering site: X east, Y north, Z up, millimetres; no geodetic/survey claim. Corner elevations are Z10000 at X0 and Z9900 at X10000, independent of Y. This is a planar 1% fall in +X over 10 m. Coordinate owner must confirm its relationship to actual source datum before any real use. The hardscape rectangular plan area X0..6000, Y0..2000 is 12 m2; remaining planted plan area 48 m2; these are horizontal projected areas, not sloping-surface quantities or material volumes.
Set planting centres at (2000,4000),(5000,4000),(8000,4000)mm with terrain-derived Z9980/9950/9920 mm. Test-only root envelopes are horizontal radius 1000 mm; their depths/heights are outside this 2D clearance test and need separate actual project criteria. Utility route positive variant runs X0..10000 at Y5800; centre-to-route separation 1800 mm exceeds the test radius by 800 mm. Negative route Y4500 gives separation 500 mm and intersects the test envelope. This demonstrates a defined plan-interface test only, never full 3D utility/safety clearance. Irrigation lateral at Y3500 branches to all three plants; one missing branch is the adverse connectivity case. Flow/pressure adequacy remains Unverified.
5 Representation quantities and exchange#
Use the admitted native categories/site objects and declared geometry/data mappings; record actual software release, object category, type, GUID/stableID, link/phase and export support. Avoid hiding meaningful planting as uncounted generic graphics. At early use, simplified canopy/symbols may satisfy reviewed purpose; at detailed use geometry and documentation follow the specified LOIN, including levels/build-ups, interfaces and controlled details. Do not model every leaf or root without an information need. Seasonal representations retain same occurrence IDs and counts; seasonal appearance does not change approved species or maturity data.
Every counted/scheduled object has one quantity source and explicit unit, phase/option, boundary, inclusion/exclusion and measurement rule. Itemise occurrences for identity/count checks and separate grouped type totals. The specimen has 3 trees, not 6 when root envelopes are displayed; hardscape 12 m2 plus planting 48 m2 equals 60 m2 site plan area. Material/spec/detail IDs are controlled references, not invented construction specifications; thickness, waste, earthwork cut/fill and irrigation quantities require their actual measurement/design sources. Report exclusions/uncertainty rather than imply full bill accuracy.
Exchange native/IFC/data/drawing sets under BBM-STD-74 with exact profile, maps, source/output hashes and receiver builds. Check plant IDs/count/type/state, coordinates, levels and units, material/spec/detail links, utility/irrigation relationships and receiver visibility of required envelopes. Plant, area and irrigation property checks for IFC exchange use the IDS 1.0 file LSC-IDS-<rev>, with the checker and version named (BBM-STD-89); geometry and clearance tests stay in BBM-STD-50. A pretty seasonal render or schema-valid IFC is not recipient acceptance.
6 Checklists evidence and release#
Complete the LOIN, Plants, Interface, Quantities and Checklist blank forms with actual requirement/source revisions, accountable owner, mandatory applicability, expected and observed result/unit/uncertainty, evidence URI/hash, independent checker/date, issue/retest, submission authorisation and receiving decision. Native/site qualification, actual species/nursery/soil/water inputs, code/design criteria, source survey and recipient tests remain Not executed here.
Synthetic expected cases: positive datum/fall/3-plant/60 m2 partition tests pass arithmetic only; shifted terrain datum, a fourth hidden duplicate plant, route Y4500 or missing irrigation branch fail their defined checks. Correct the actual source owner/revision, preserve failed evidence and repeat affected interfaces/quantities/receiver checks under one ChangeID. Do not average away an unresolved mandatory design, identity, access or exchange failure. Review required landscape/civil/MEP dependencies and scope before release; actual receiving acceptance is a separate decision.
References#
- Office sources linked above and matrix; Manual/BEP, coordinate/dictionary and BoD ownership retained. All numeric dimensions here are synthetic fixtures.
- ISO 19650-1:2018 clauses 5/11 and 19650-2:2018 clauses 5.6–5.7 are requirements/production/exchange reading pointers; 19650-3:2020 operational and 19650-5:2020 security context. Public catalogue evidence is not licensed clause audit.
- ISO 7817-1:2024, purpose-led information; BS EN 17412-1:2020 predecessor, retain contracted edition until controlled change; IMI Framework resources (formerly UK BIM Framework, renamed May 2025).
- BCA Singapore BIM Guide v2 (August 2013), historic benchmark, Appendix B responsibility-matrix context including landscape designer; it is precedent, not a UAE landscape design code. Checked 2026-10-16.
- DMT infrastructure documentation v1.0 October 2020, project appointment/deliverable context; DM circular index (the BBM-STD-51 §3 register entry used by BBM-STD-57), DDA Circular 400 (registered once, with verified URL, date and subject, in BBM-STD-57). Determine actual jurisdiction/submission profile through BBM-STD-57, not by generic geography. Primary sources rechecked 2026-10-16.
- Current sources, checked 2026-11-04: IMI Framework resources (formerly UK BIM Framework, renamed May 2025); buildingSMART IDS 1.0 (June 2024); Al Sa'fat, Estidama Pearl minimums (DMT news, 8 Jan 2025). UAE requirement detail: BBM-STD-85.