BBM-STD-77-POINT_CLOUD_AND_SCAN-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Survey brief purpose coverage and security#
This pack covers. Define the capture decision before commissioning a sensor or modelling a cloud. Retain survey/coordinates as the control/datum owner and use EIR/LOIN, templates/builds, quality, federation and Manual V0.5. The editable brief manifest and acceptance pack provides blank/populated specifications, not an actual survey or tested point cloud.
The survey/scan lead agrees acquisition and quality with a competent surveyor; the coordinate owner controls reference transformations; receiving discipline defines objects/use and model abstraction; independent survey/model checkers review within competence; the appointed recipient accepts specified reliance and exclusions. Record actual appointments/deputies, permitted data recipients, fieldwork authority and safety arrangements before capture. A modeller cannot approve unsupported survey accuracy or unseen conditions.
The Survey brief requires BriefID/revision, purpose/decision, site/asset/zone/object scope, required geometry/data/documentation, acquisition date/time and validity trigger, coordinate/datum/reference/epoch, units, control/check points, required accuracy/uncertainty and object-specific fit tolerance with source, coverage/density/occlusion criteria, access/permits, protected/sensitive areas, methods/instruments/calibration, deliverable formats/builds, schedule/owners, security/custody/rights, review/acceptance and unresolved limitations. Define interiors/exteriors/roofs/voids/underground boundaries explicitly; inaccessible spaces remain unresolved and are not inferred complete. The coordinate fields name the required CRS from the CRS register in BBM-STD-86 (Dubai: DLTM, EPSG:3997, vertical datum DMD; Abu Dhabi: the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, vertical datum Ras Ghumays), the vertical datum, the control-point source authority (for example the authority geodetic network point IDs) and the transformation, as recorded in BEP V0.5 §8.2; no CRS is hard-coded here. Required accuracy is stated per object class as a USIBD Level of Accuracy band, separately for measured and represented accuracy, or as the RICS measured-survey equivalent; the specification edition used is recorded at adoption.
Apply Manual 9.4/ISO 19650-5 sensitivity assessment before capture/distribution. Minimise faces, plates, security systems and operationally sensitive detail in the authorised output; protect original evidence and record any approved redaction. Obtain the actual site/capture permissions and competence/safety arrangements; no drone, confined-space or work-at-height operation is authorised by this annex. A drone (UAS) capture adds the brief field "UAS permit": the permit reference issued under the current UAE General Civil Aviation Authority (GCAA) and emirate civil aviation authority requirement for the site (in Dubai, the Dubai Civil Aviation Authority), the operator licence, no-fly/restricted-zone check and site security permission. The permit route and its current requirements are confirmed through BBM-STD-57 and BBM-STD-85 at brief stage; this standard states no permit thresholds. No raw site/learner/client material goes to unapproved public/AI services. Retention/access/backup and eventual disposal follow BBM-STD-76, with no credentials in forms.
2 Acquisition registration control and uncertainty#
Register sensor/method, serial/source identifier, calibration/check reference/date, acquisition conditions and stations/trajectory, raw-file identities/hashes, timestamps/timezone, nominal settings and achieved coverage. Laser scan, total-station survey and photogrammetry have different uncertainty sources; record range, incidence, surface/reflectivity/motion, visibility and method limitations rather than assigning one generic scanner tolerance. Agree required density/spacing at defined object distances and surface areas; a total point count is not proof of usable detail everywhere.
Record registration method (targets/control, surface matching or a justified combined method), station/overlap graph, transforms and direction/units, residual definition/statistic, exclusions, registration report/tool/full build and operator. Preserve calibration/fit controls separately from independent check points and elevation benchmarks under BBM-STD-63; tie to at least 3 well-distributed control points plus elevation/unit probes. Fit residuals can be small while the entire cloud has the wrong scale/datum; do not accept an arbitrary report colour or overlap percentage as absolute accuracy. Qualify actual software metrics and settings rather than importing vendor help examples as project acceptance limits.
The competent surveyor supplies uncertainty/confidence/bounded-error basis, control network/benchmark source and checks, systematic errors, transformations and limitations. The recipient agrees sufficient coverage and accuracy for the decision before reliance. Keep instrument capability, internal scan-to-scan registration, independent survey/control accuracy and modelling abstraction/fit as separate values and evidence. Do not simply add RMS values or infer a statistical confidence level without a justified error model; independent systematic effects and covariance may matter. Rounded coordinates are not accuracy evidence.
3 Object specific model fit and acceptance budgets#
For each object/use record ObjectID, source cloud/segment/date/hash, feature/region, measured/modelled/record-derived/inferred status, modelling method/idealisation, expected measurement plane, source uncertainty, fit tolerance/unit/source, representative sample locations/count/selection, signed/absolute deviation and statistic, uncertainty treatment and competent reviewer. Separate centreline, visible face and concealed construction. A best-fit wall plane does not prove thickness, concealed reinforcement or services completeness. Nonvisible objects need other authorised evidence or explicit non-reliance.
Approve acceptance rules before extraction. One permissible project-specific bounded-error test is absolute model-to-observed deviation plus an independently justified source bound <= allowed decision tolerance. It is not a universal scan/BIM formula or an automatic statistical combination. A tolerance exceeding source accuracy does not excuse missing mandatory coverage or incorrect identity. A requirement needing finer accuracy than the reliable source must be held or resurveyed; do not type extra decimal places or stretch geometry to appear compliant.
SYN-SCAN77 R01 is a separate fictional local engineering test frame in millimetres, X east/Y north/Z up, with no geodetic/real survey claim. It does not replace BBM-STD-63's SYN-T63 or BBM-STD-54's SYN-CRS01. Control inputs at (0,0,0), (10000,0,0), (0,10000,3000) mm are declared independent of registration-fit points for this fixture. Expected residual component vectors are (3,4,0), (0,0,6), (8,0,0) mm: norms 5, 6, 8 mm; three-dimensional RMS sqrt((25+36+64)/3)=6.455 mm to three decimals, maximum 8 mm. Synthetic CHECK77-01 permits max 10 mm; the arithmetic case passes that criterion only. An illustrative 2 mm internal registration residual is a different metric and cannot replace those independent checks.
For the model-fit example, fictional FIT77-01 permits 20 mm conservative decision tolerance and assumes an independently justified bounded source error 8 mm. That bound is a scenario input requiring actual survey evidence; it is not inferred from the largest check residual or registration RMS. Sample absolute model-to-cloud deviations 4, 9, 13 mm give 12, 17, 21 mm with the bound: first two pass, third fails. Corrected third deviation 10 mm gives 18 mm and is an expected retest pass. All numbers are test specifications; no sensor, cloud or model was actually measured or certified.
4 Formats provenance transformations and storage#
Preserve unmodified authorised raw data in controlled custody. Register exchange format/version (for example adopted E57), structured/unstructured status, stations/images/colour/intensity/other attributes actually present, units/CRS, bounding extent, point count/density/coverage, sensor/source/timestamp, rights, bytes/hash and dependencies. Select exact vendor export/import builds and supported formats, loss/limitations and readback tests; E57 is a format family, not an accuracy certificate or guarantee that every proprietary attribute survives conversion.
Partition/index by agreed site/building/level/zone/epoch without duplicating authority; Manifest records source-to-segment relationships, overlap and intentional shared extents. Keep raw versus cleaned/decimated/indexed/modelled derivatives distinct with TransformationID, source/output hashes, full parameters, tool/build, operator/time, crop/exclusion/decimation/filter/masking method, units/transform and review. Quantify information loss at critical features. Do not permanently erase the only evidence to improve a screenshot or silently re-register an accepted cloud.
Autodesk ReCap RCP is a project reference to scan data; it does not contain all referenced RCS bytes. Package the RCS/support dependencies and permitted images/reference material when that route is selected; copying an RCP alone is insufficient. Qualify path portability in an isolated destination and inspect index/source identifiers, extents/counts and control coordinates after conversion. Breakage or unsupported attribute loss holds the affected use. Storage/performance limits and loading/segment strategy depend on measured hardware/build and actual task need, not a universal file-size rule.
The fictional coverage specimen is a 10x10 m plan region. Its declared coverage map has 80 m2 observed and 20 m2 occluded/unknown. Those figures describe this 2D test denominator only, not whole-building surface completeness or hidden services. Register inaccessible zones, scan stations/date, distance-based density evidence, occlusions, reflective/moving surfaces and mitigation/resurvey owner. An attractive continuous mesh or interpolated patch must not relabel the 20 m2 unknown as surveyed. No physical E57/RCP/RCS or native model is delivered by this editorial specification.
5 Deviation checking sampling and change verification#
Freeze the cloud/control/model input revisions and compare independent known features in the selected frame before fit testing. Define sampling by object class, space, surface orientation/height and consequence, including critical edges/openings/equipment/interfaces, transitions and apparently poor coverage. Record population, sampled/unsampled counts and selection rationale; a random handful of easy wall faces is insufficient for an unqualified full-scope claim. Critical and mandatory coverage requires its agreed complete check. Report signed/absolute values, maxima/distribution, outliers/exclusions and local versus global misalignment; an average cannot hide a critical deviation.
The Coverage and Deviation forms record actual source/evidence, point/feature IDs and coordinates, expected/observed values, method/uncertainty, criterion and reviewer. An unexplained zero-point/applicability result holds the check. Distinguish no observed object, no captured surface and confirmed absence. Verify sample planes/distances independently; automatic nearest-neighbour distances across an opening or unrelated surface can give misleading agreement. Keep screenshots/sections, numerical report and annotated issue locations together.
Label delivered records as as-existing at the verified capture date with stated limitations; the filename as-built alone is insufficient. For later construction/alteration, compare dated source sets/control stability and known changed/unchanged features, log material changes and require resurvey/inspection before relying on stale regions. Update object identity/state, cloud/model/record revisions, BoD/AIR/interface and residual-risk owners as affected. Capture and model dates are distinct. A scan-derived model cannot establish conditions hidden or changed after capture.
6 Acceptance reports issues and receiving reliance#
Complete Survey brief, Manifest, Transformations, Controls, Coverage, Deviation and Acceptance forms. Record actual operator/date, full builds, input/output/source hashes, all relevant requirements and approved criteria, observed results/uncertainty, exclusions/unsampled areas, issue/corrected revision/retest, competent independent survey/model checks, submission authorisation and receiving decision/acknowledgement. Recipient verifies datum/control, coverage, object IDs/units and intended use in actual receiving software; schema checks and a registration report alone are insufficient.
Adverse cases reset independently: swapped units/axes, deliberately omitted RCS, an occluded region mislabelled measured, out-of-tolerance object/edge, unstable benchmark or stale acquisition after alteration. Expected FAIL/Hold is recorded with exact source/affected scope; correct or resurvey through the responsible owner and repeat affected controls/coverage/fit/receiver checks. The synthetic third-fit retest changes 13 to 10 mm under same criterion/bound and requires a new corrected model/output hash. It is an expected 18 mm bounded result, not an executed PASS.
Release only the accepted purpose/object/area/date scope with unresolved regions explicitly non-reliant and assigned for action. A conditional information decision cannot override required safety, legal or accuracy requirements. Actual survey contract/permissions, sensor calibration, capture, source files, justified uncertainty/criteria, full build/format qualification and real recipient acceptance remain Not executed. Editorial review establishes this specification/forms pack; only actual survey and receiving evidence can establish reliance.
References#
- Office survey/requirements/build/QA and federation owners linked above; guide 30 coordinate setup and matrix. BBM-STD-63 remains actual coordinate/control authority.
- ISO 19650-1:2018, clauses 5/11; 19650-2:2018, clauses 5.1.4–5.1.5/5.6–5.7 as methods/production/exchange reading pointers; 19650-3:2020 operational and 19650-5:2020 security context. Public catalogues are not licensed-text conformity evidence.
- ISO 7817-1:2024 and retained BS EN 17412-1:2020 predecessor, purpose/object/use-led information; IMI Framework (formerly UK BIM Framework, renamed May 2025) resources. Preserve appointment editions until authorised change.
- USIBD Level of Accuracy Specification and RICS measured surveys of land, buildings and utilities, accuracy-band frameworks; pages reached 2026-11-04; editions recorded at adoption. GCAA and Dubai Civil Aviation Authority for UAS permits, via BBM-STD-85.
- ASTM E2807 publisher catalogue, E57 3D data-exchange format context, catalogue search checked 2026-10-16; actual adopted issue/licensed details to register, not silently selected from a current listing.
- Autodesk ReCap Registration Quality Report and capture/index/RCP-RCS process, checked 2026-10-16. Vendor example metrics are not office/project acceptance thresholds or installed-build evidence.
- BCA Singapore BIM Guide v2 August 2013, historic benchmark (2013), survey/responsibility precedent; DMT BIM Code of Practice October 2020 and infrastructure documentation, jurisdiction/appointment context. DM circular index and DDA Circular 400 (held as a register row in BBM-STD-57; date and content not restated here) remain separate applicability checks through BBM-STD-57; no universal UAE scan accuracy or permission inferred.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: Survey brief CRS/vertical datum/control-source fields from BBM-STD-86; UAS permit field routed via BBM-STD-85/57; accuracy stated as a USIBD LOA band or RICS equivalent; control-point rule; links to Manual V0.4; spacing fixed. + cross-doc pointer pass. |