Survey to BIM: Prove the Coordinates Before Setting Out

buildingSMART’s georeferencing use case, updated in August 2026, addresses multidisciplinary model positioning and exchange through IFC, including infrastructure. Its stated purpose reaches beyond making separate models look aligned. [1]

OlbrichCo recommends a coordinate-control package before any model-derived setting-out file is released. The decision is whether the surveyor, designer, BIM coordinator and site team can reproduce the same position and level from the issued evidence. Apply it first to an interface where correction would be difficult: foundation grids, prefabricated connections or an extension meeting an existing building.

RICS includes survey accuracy, control, coordinate grid and datum within its measured-survey standard. Its accuracy-band approach explicitly addresses digital data and scale-independent requirements. [2]

For an Iranian project, commission the survey for the intended construction decision, not merely a drawing scale or point-cloud density. Ask the surveyor and responsible designers to define the required horizontal and vertical accuracy, control arrangement, checking method and acceptance authority. Keep survey uncertainty, digital-transfer error and permitted construction deviation separate; this note sets no universal millimetre tolerance.

NOAA describes a datum as a reference framework for consistent survey coordinates and distinguishes horizontal position from vertical elevation. A height therefore needs a stated reference, not only a number. [3]

Require a signed reference sheet: project grid or coordinate reference system, units, axis order and directions, origin, north convention, vertical reference, benchmark identities and the relationship between project zero and surveyed levels. Where relevant, include reference epoch, transformation and grid-to-ground treatment. Have the competent surveyor determine these details; do not infer them from a file name or an online map.

Make the local site grid and any wider mapping system explicit rather than assuming they are interchangeable. Ask the surveyor to document how coordinates pass between them and which system each deliverable uses. For satellite-derived observations, require the declared height type and any approved conversion. Never nominate a foreign datum or conversion service for an Iranian site simply because an example uses it.

Deliver the sheet in Persian with unchanged technical identifiers and a sample coordinate record showing field names, units, decimal convention and order. Keep point identifiers as identifiers, not reformatted numbers. Test the actual spreadsheet or instrument import used by the receiving team. An offline copy should carry its revision and approval status so a connectivity interruption does not force the crew to guess.

Autodesk’s Revit 2026 guidance recommends deriving shared coordinates from one file. It also distinguishes these shared relationships from a model’s internal coordinates and notes a different sharing workflow for cloud collaboration. [4]

Use that as a coordination principle, not a requirement to buy a particular platform. Nominate the approved survey or site file as the project’s coordinate authority, with a named owner and controlled revision. Let the BIM coordinator implement the approved relationship, while the surveyor verifies its geospatial meaning. Do not allow each discipline to establish an undocumented alternative origin.

Before combining models, record the authoring application and version, linked-file position, units, rotation, offsets and approved reference revision. Retain the original received files. If a model appears displaced, raise a discrepancy and compare the reference records before moving it. A convenient visual adjustment must not silently become the coordinates later used for excavation, fabrication or installation.

In refurbishment, distinguish an inherited drawing’s assumed grid from control established by the current survey. Require a reconciliation of the relevant existing structure, boundaries and proposed works by the responsible specialists. This process does not certify a property boundary or settle ownership. Put survey scope, permitted reliance, transformation responsibility and the response to missing records into the appointment and construction contracts.

In IFC4 ADD2 TC1, IfcMapConversion relates a local engineering system to a map system using position, orientation and scale information. Its definition expressly excludes the map projection from geodetic coordinates. [5]

Consequently, our exchange check asks two questions separately: is the approved reference described, and does the receiving workflow place the geometry correctly? Agree the IFC version and export settings that the actual software supports. Do not treat the presence of one entity, a successful import or a screenshot as proof of the complete coordinate relationship.

Create a small reference specimen containing identifiable check points distributed across the relevant plan extent and height range. Have the surveyor specify adequate geometry and independent expected coordinates. Export through the intended delivery route, import into the receiving application and compare each result with the approved values. Preserve differences by axis, units, software versions and settings; do not hide an outlier inside an average.

Repeat the check for the actual setting-out file or instrument workflow, not just the federated BIM viewer. Require the receiving surveyor to confirm that identifiers, axes, units and levels survive the transfer. Use a witnessed trial on a safe, non-production reference area. Until it passes the project’s agreed criteria, keep model-derived coordinates out of released construction instructions.

Our proposed field test uses verified control and check observations that were not merely reused to fit the same transformation. Ask the surveyor to document that independence and the selected method’s limitations. Checking a copied coordinate against another copy of itself is a document comparison, not independent evidence of position on the site.

Have the survey team identify, protect and record the control marks and benchmarks needed for the work, with location photographs and recovery descriptions. Agree checks before use and after suspected disturbance, excavation nearby, loss of a mark or a relevant site event. A mark’s continued presence is not, by itself, the agreed verification of its accepted coordinates.

For an illustrative discrepancy, suppose the office exchange check passes in plan but the field level comparison fails. Hold the affected setting-out release. Have the surveyor investigate the benchmark, vertical reference, height conversion, units, instrument setup and issued revision before proposing a correction. Do not shift every model vertically to force one point to agree; retain the original observation and investigation record.

Separate approval of the coordinate framework from acceptance of installed work. Ask the responsible engineer to decide what previously issued files or completed elements are affected by a confirmed error. Map the scope, withdraw superseded instructions, obtain a reviewed disposition and recheck the corrected chain. Avoid both an undocumented local workaround and an unsupported conclusion that the whole project must be rebuilt.

Pilot one consequential interface with the people who will actually exchange and use the data. The release pack should contain the approved reference sheet, control register, transformation record, source and exported file revisions, check-point results, exceptions and named approvals. Include a readable export alongside native files; prove that the site team can retrieve the package without the original modeller present.

For procurement in Iran, verify access to the required software versions, licensed tools, instruments, technical support and competent survey staff before promising a digital workflow. Price the verification and rechecking effort explicitly. If connectivity or a cloud function is uncertain, agree and test a supported offline exchange. Do not replace a failed transfer with an unreviewed manual coordinate transcription.

Track complete reference packages against planned releases, failed exchange checks by cause, unexplained coordinate changes, disturbed control marks, time to resolve discrepancies and superseded files still found in use. Record the population and review period for each measure. These are proposed process indicators, not claims of reduced rework, positional accuracy or financial return achieved by OlbrichCo.

Reopen verification after a reference change, new survey, relevant software or export change, replacement control or a changed construction interface. Retain the approved history for the owner’s later alterations and surveys. Applicable Iranian requirements, contracts, actual site conditions and competent local surveying and engineering review control implementation. The cover expresses a shared physical reference; it is not an approved survey setup.