ArchHubBABOOMDownload

Survey coordinates and civil modelling

BBM-STD-63 · V0.2 · P1 establishes survey acceptance and the single controlled coordinate baseline before federation.

Download WordFormsAll standards

Ribbon tools that apply it: Link Picker, Coordinates Check, Review Links, Topo from Survey

BBM-STD-63-SURVEY_AND_CIVIL-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft

Revision history

VersionDateChange
V0.12026-10-16Initial controlled WIP draft.
V0.22026-11-04Closed audit rows: CRS summary with pointer to BBM-STD-86, at least three control points plus SYN-H3, ADM Code of Practice recorded once, 3.1 IFC georeferencing, grid-north vs true-north, Object Catalogue gate; relinked Manual V0.4/BEP V0.5; IMI Framework naming; spacing fixes + cross-doc pointer pass.

1 Scope survey acceptance and control#

This standard covers and. P1 establishes survey acceptance and the single controlled coordinate baseline before federation. P2 civil modelling activates only for the appointed civil/infrastructure scope. The survey lead establishes control and provenance; the competent surveyor supplies measured evidence; the civil lead owns design objects; the coordinator implements the approved transform; an independent survey/coordinate checker verifies it. An Information Manager cannot approve unsupported survey accuracy. Use BBM-STD-51, BBM-STD-54, BBM-STD-72, BBM-STD-57, the Manual and BEP. The editable control and test pack is the working form schema.

Accept a survey only after its extent/purpose, capture date, surveyor/competence and commission, instrument/method/calibration, original source files/revisions/hashes, horizontal and vertical reference systems, units, controls and declared accuracy/limitations are reviewed. Record occlusions, interpolation, inaccessible areas, utilities not located and survey age. Separate measured, record-derived, interpreted and assumed data. A DWG insertion point, EPSG number, terrain screenshot or point-cloud appearance alone cannot establish datum, axis order, height reference or accuracy. Missing datum/unit/accuracy or an unsuitable survey extent holds affected modelling and federation.

The CRS register requires horizontal datum/reference frame, projection/zone, axis order/direction, coordinate epoch where relevant, horizontal unit, vertical datum and height type (orthometric/ellipsoidal/local), geoid/vertical transformation where relevant, vertical unit, grid-to-ground/scale considerations, benchmark/control source and authority confirmation. Record explicit N/A with reason; do not assume every UAE site shares one CRS. Actual project numeric tolerances derive from purpose/appointment/survey evidence, not an ISO universal tolerance. Levels/grids have stable IDs and one surveyed origin relation; published spot elevations state the approved height datum.

CRS defaults (summary only; the register, EPSG codes, transformations and procedure are owned by BBM-STD-86 and recorded in BEP §8.2): Dubai horizontal = DLTM, EPSG:3997 "WGS 84 / Dubai Local TM", metres; Dubai vertical = DMD (Dubai Municipality Datum, equal to the Port Rashid datum), no EPSG code; Abu Dhabi horizontal = the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, recorded with its EPSG code and transformation; Abu Dhabi vertical = Ras Ghumays (EPSG datum 1146); other sites = per the accepted survey. Never hard-code a UTM zone (for example EPSG:32640) as a default.

2 Independent control and accuracy checks#

The survey lead approves control before linking. Retain calibration/transform establishment points separately from at least three well-distributed, independently checked horizontal controls plus an elevation benchmark and elevation/unit probes (check procedure in BBM-STD-86 §5). Check points must not simply be the points used to fit the same transform. Record control mark IDs/photos or protected references, measured E/N/H, uncertainty and confidence basis, independent method/source/date, expected transformed values, residual components and norm, permitted criteria/source and checker decision. The receiving discipline rechecks after any source, unit, north, link placement or coordinate change. Use closure/baseline distances and orientation as independent checks; one coincident point cannot reveal rotation, scale or mirroring.

Where combined uncertainty exceeds the required decision tolerance, hold acceptance and obtain better evidence or an authorised purpose/criterion change; never label a rounded display as precise evidence. Re-establish disturbed benchmarks and quantify change before affected work resumes. Do not move a shared origin or all geometry to hide a bad link.

3 Local shared GIS and north transformation#

Keep geometry in the qualified authoring working range, recording the explicit transform to the shared/survey/GIS frame. Record direction of transform, handedness, axes, origin/offsets, rotation sign/unit, scale, model/document units, vertical offset and any geodetic operation/grid files. GIS lat/long in degrees cannot be inserted as metres. A projected coordinate transform is not automatically a geodetic datum transformation. Apply only the appointed geodetic operation supported by the survey evidence; confirm GIS receiver axis order and height interpretation. The source survey is linked read-only; acquire/publish/shared-site operations are controlled changes to isolated copies and require review before project rollout.

SYN-T63 R01 is a fictional local engineering transform, not a real UAE survey, geodetic CRS or modification to BBM-STD-54's separate SYN-CRS01 fixture. First convert model millimetres to local metres: x=X_mm/1000, y=Y_mm/1000, z=Z_mm/1000. Then E=5000+xcos(30°)-ysin(30°), N=7000+xsin(30°)+ycos(30°), H=100+z. Positive rotation is counterclockwise about +Z from local +X toward shared +Y; scale=1 after unit conversion, right-handed axes, +H up. Inverse: x=(E-5000)cos(30°)+(N-7000)sin(30°), y=-(E-5000)sin(30°)+(N-7000)cos(30°), z=H-100; multiply by 1000 for mm. No EPSG or geoid claim is made.

Independent fixture controlLocal model mmExpected shared mPurpose
SYN-H110000, 0, 05008.660254, 7005.000000, 100.000000Horizontal control distinct from declared origin; local baseline 10 m
SYN-H20, 20000, 04990.000000, 7017.320508, 100.000000Independent second direction; local baseline 20 m
SYN-H3-10000, 10000, 04986.339746, 7003.660254, 100.000000Third horizontal control, opposite quadrant, so the three controls are well distributed
SYN-BM10, 0, 20005000.000000, 7000.000000, 102.000000Elevation benchmark; +2 m local rise

These expected values are arithmetic specifications, not measured residuals. For the synthetic fixture only, REQ- sets horizontal residual <=0.002 m and vertical <=0.001 m, with an assumed combined control uncertainty <=0.0005 m. Real acceptance needs actual justified accuracy, not these invented survey claims. Native/export/receiver residuals remain unmeasured. The grid-north vector (shared +N) in the local XY frame is (0.5,0.8660254); project north is local +Y. Record the grid convergence angle at site from the survey, with its sign convention; true north is grid north corrected by that convergence. The synthetic fixture declares convergence 0, which is not true of real sites away from the projection's central meridian; test grid north and true north separately. Revit internal, project and shared frames must be recorded separately; inspect both Project North and True North views and exported coordinates. A correct north-arrow picture is insufficient without the vector/control tests.

Round trip: reopen the exact exported DWG/IFC/GIS profile in the named receiver, report H1/H2/H3/BM1 in the agreed frame, apply the inverse and compare local values/units and both north orientations. Log source/export hashes, profile/builds, placement/shared-site settings and any receiver axis transformation. Reject unexpected scaling, mirroring, false elevation, swapped axes or double-applied offsets before federation. A PDF carries presentation checks, not editable coordinate proof.

3.1 IFC georeferencing#

IFC georeferencing (IfcProjectedCRS and IfcMapConversion for IFC4/IFC 4.3; the property-set fallback for IFC2x3, used only when an appointment or authority profile requires it) is specified once in BBM-STD-86 §4. The round-trip test reads these values back in the named receiver and compares them with the register; a receiver that ignores them fails the georeferencing use.

4 P2 civil authoring and underground uncertainty#

When appointed, allocate stable IDs and source revisions for existing/proposed surfaces, boundaries/breaklines, alignments, stationing equations, profiles, crossfalls/road corridors, drainage catchments/inlets/manholes/pipes and utility networks. Civil design retains actual design/code criteria and competent approvals through BBM-STD-12/57. Define object ownership, construction/existing/abandoned status, levels/inverts, topology/connectivity, material/size, source accuracy and associated documentation before exchange. Grids and levels in adjacent building models reference the same approved coordinate baseline; they do not become new civil control.

The synthetic road/drainage fixture comprises SUR-SYN-EX01 and SUR-SYN-PR01, alignment AL- with chainage 0–100 m, road profile PR-, two drainage nodes DN-/02 and a connecting PIPE-. All following civil coordinates are local metres under SYN-T63, with shared H=100+local z. Node inverts local z10.0m/H110.0m and z9.5m/H109.5m over 50 m yield a declared design gradient 1%; these are fictional inputs, not a code minimum or construction evidence. Both surface boundaries are local XY rectangles (0,-5),(100,-5),(100,5),(0,5); EX01 is flat local z11.8/H111.8, PR01 flat z12/H112, with breaklines along y=-5,0,5 at their respective heights. AL- is the straight local centreline (0,0) to (100,0), chainage 0–100 m, no station equation or curve. PR- has points station 0/z12 and 100/z12, no vertical curve, zero grade. The road fixture is a 10 m-wide flat strip; its zero crossfall is a synthetic test value, not an accepted drainage design. DN01/02 are at local XY(0,0)/(50,0), cover local z12/H112; PIPE01 connects their inverts. UT01 crosses at x25, y-5..5 with unknown depth. These definitions populate Civil specification. Separate cover levels, nominal pipe size and invert-height units; do not parse legacy text INVERT LEVEL without an approved unit/datum mapping. Surface triangulation/breakline/interpolation, corridor sections and network direction must be checked in the civil application and receiver.

For each buried utility segment, record measured/record/assumed source, survey method/date, uncertainty in horizontal/vertical position and status (exposed, detected, record-only, unverified). Mark uncertainty zones and verification actions; do not turn a record line into an accurately surveyed asset. Unverified crossing near the synthetic drain triggers trial verification or redesign by the appointed owner before affected construction release. This pack specifies no excavation safety distance or blanket clash tolerance; use the approved pair/zone rule in BBM-STD-50 and competent utility/safety controls.

5 ADM and other authority exchange applicability#

ADM's infrastructure Code of Practice section 3.3 requires the BEP to state datum, units, offsets, rotation and shared coordinates relative to its GIS system. Its October 2020 platform/version/size/classification examples must not be imported as current office-wide or UAE-wide obligations. The ADM Code of Practice is recorded once, with its verified scope (infrastructure) and issue, in the BBM-STD-51 §3 edition register and assigned only through BBM-STD-57 and BBM-STD-85; other standards cite that entry. Confirm the actual appointment EIR, GIS/as-built profile and receiver before issue. The ADM Infrastructure BIM Object Catalogue v2.0 (May 2021) is the candidate object/property source; it is read in full and its section IDs are entered before the Authority mapping tab is used, and the tab stays Hold until then. Do not invent ADM attribute codes to fill the gap.

The Authority mapping tab records each required civil object/property, candidate catalogue section, actual requirement/edition, native key, destination format/schema/field, unit/datum, owner and evidence status. Road alignment, surface, node/pipe topology and asset IDs require distinct receiver tests; a building IFC viewer need not support civil semantics. Confirm whether selected exchange uses native Civil 3D, LandXML, IFC4.3, DWG and/or GIS and precisely which aspects each preserves. A required property unsupported in one format needs an agreed complementary deliverable, not silent omission. DM permit/openBIM, DDA design approval and ADM municipal-infrastructure routes remain separate applicability entries in BBM-STD-57; no nationwide threshold is asserted here.

6 Release checks and change recovery#

Use Survey acceptance, CRS, Transform, Controls, Civil objects, Authority mapping, Tests and Acceptance sheets and their blank forms. Every source/control/transform revision links one ChangeID to affected models, EIR/LOIN, BEP, TIDP/MIDP, native/export presets and already shared products. Retain the original surveyed and model baseline. Rehearse rollback by reopening the preserved baseline and rechecking controls; never use a major-version save-back assumption. Notify and obtain acknowledgment from affected recipient owners before the new transform becomes effective.

Before authorisation, require a complete/competent survey acceptance, independent H1/H2/H3/BM1 checks (at least three horizontal controls), north/inverse round trip, all mandatory civil properties/topology, actual receiver evidence and resolved design/safety requirements. A required wrong/missing datum/unit/accuracy holds federation. Native authoring/federation, survey capture, authority acceptance and actual receiver tests are Not executed by this writing pack. Producer check, independent verification, submission authorisation and recipient acceptance remain separate fields, with no synthetic signature or approval.

References#