Scan-to-BIM quality is decided in the field long before a modeler draws a wall. A model cannot recover the back of a pipe, the top of a beam, or the edge of an opening that the capture never observed. The field team needs a model-oriented scope, viewpoints for critical elements, a coordinate bridge, and a clear record of uncertainty and exclusions.
Artec lists Jet as a SLAM mobile LiDAR system with LAS, LAZ, PLY, and E57 point-cloud export. Those formats can move geometry into survey and BIM pipelines, while the model specification decides what must be represented. buildingSMART defines IFC as an open international standard for sharing BIM data and publishes schema, property sets, and exchange mechanisms. An IFC request still needs a named version, model view, element scope, properties, and delivery test.
Translate the BIM brief into observable geometry
“Create a BIM” leaves the field team guessing. Convert it into an element matrix with required extent, representation, expected detail, attributes, tolerance, and acceptance view. Include only features that serve the project use.
| Element | Field surfaces needed | Common blind spot | Supplement |
|---|---|---|---|
| Wall | Faces, returns, openings, intersections | Behind finishes or casework | Opposing room passes |
| Slab | Usable floor and soffit areas | Materials, ceilings, equipment | Phased capture or targeted stations |
| Beam/column | Faces, ends, connection context | Fireproofing and ceilings | Higher/lower viewpoint |
| Pipe/duct | Enough circumference, fittings, branches | Dense rack overlap | Parallel routes at two elevations |
| Equipment | Envelope, base, nozzles, access zones | Back side and underside | Cell-specific detail loop |
| Opening | Edges, depth, host context | Closed doors or coverings | Both sides plus field dimension |
The matrix should name whether the model represents visible geometry, design intent, nominal components, or a combination. A scanned pipe with insulation presents an outer surface; inferring the carrier diameter requires other information. Preserve that distinction in the model metadata.
Agree on coordinates and origin behavior
The survey and BIM leads define the project coordinate reference, vertical reference, units, shared coordinates, origin, rotation, and any software-specific working origin. Large coordinate values can affect some authoring workflows, so test a sample before full production. Never shift a cloud to an arbitrary local origin without recording the exact reversible transformation.
Establish stable control through the building and across levels. Reserve independent checkpoints to assess the delivered cloud. If separate capture days or modes are used, provide overlap and control for each. A floor-by-floor collection that lacks a trustworthy vertical relationship becomes painful at stairs, shafts, risers, and façades.
Plan paths for model continuity
The core route should connect rooms, corridors, stairs, shafts, and exterior references rather than producing isolated bubbles of data. Add detail branches around MEP, equipment, openings, and above-ceiling access. Loop closures and cross-connections strengthen the SLAM geometry, particularly across repetitive corridors and large open floors.
Artec’s listed 360 by 290 degree field of view supports broad observation while moving. Occlusion remains decisive. The operator should think like the future modeler: can a centerline be inferred from enough pipe surface, can a wall thickness be seen at a return, can an opening edge be distinguished, and can an element be connected through a congested zone?
Use a field completeness board
Track completeness by level and model zone. Each cell lists required elements, captured routes, current occlusions, supplemental measures, and status. The live point-cloud preview helps identify obvious holes. A targeted cross-section or quick office sync during the shift can reveal subtler failures.
- Green: required geometry appears from adequate directions and control is observed.
- Amber: modelable with a documented limitation or supplemental source.
- Red: missing critical surface, unresolved coordinate issue, or unsafe/inaccessible area.
Red cells remain open. Amber cells require acceptance by the deliverable lead, not a quiet assumption by the operator.
Capture attributes alongside geometry
BIM users often need asset tag, system, level, room, material, service, status, and capture date. The point cloud may show a label, but it does not automatically establish the correct asset identity. Coordinate the owner’s asset register, photographs where permitted, field notes, and tag mapping. Keep external attributes linked by stable IDs.
Optional color imagery can make navigation and identification easier. Artec documents color capture through a supported camera. The team should include image privacy, lighting, exposure, synchronization, storage, and site permission in the plan. Geometry collection in zero light does not guarantee useful color.
Give the modeler a controlled source package
Preserve raw observations and create an approved registered master. Export zone files at agreed extents and resolution, with coordinates and units tested in the target application. Avoid ad hoc cropping that removes continuity at zone boundaries. Every file receives a revision and checksum or other integrity record where the project requires it.
The source package should contain the cloud, coordinate statement, control and checkpoint report, capture dates, equipment and deployment, processing log, zone map, completeness board, occlusion register, photographs or asset mapping if permitted, and a file manifest.
Define model verification separately
The BIM team should verify modeled elements against the approved point cloud using project-defined sections, samples, or surface comparisons. Sampling should cover levels, zones, element types, and difficult geometry. A clean view in one room cannot qualify the entire facility.
IFC delivery needs a schema/version and exchange requirement. Check element types, coordinates, units, property mapping, geometry, and receiving-software behavior. A native authoring file, IFC, coordination model, and 2D sheets may each serve different users; list which output is contractual.
The field handoff should let the modeler distinguish observed surface, inferred geometry, owner data, and accepted gaps.
Final field-to-BIM gate
- Element matrix and model use approved.
- Coordinates and target-software test completed.
- Routes connect levels, rooms, exterior references, and critical systems.
- Required surfaces reviewed by zone; exclusions accepted explicitly.
- Control, independent checkpoints, and processing records complete.
- Attributes mapped through stable asset identifiers.
- Source package and model verification method agreed.
A fast capture becomes a strong BIM source when the crew collects with the modeler’s questions in mind. Seeing that chain click—from a deliberate second pass around a pipe rack to a clean, traceable model—is one of the most rewarding parts of reality capture.