From scope
to something you can use.

What we need from you

A useful scan scope needs four things: the areas in play, the decision the data supports, the access rules, and the format your downstream team works in. Existing drawings help even when they are wrong — they tell us what changed. Site-specific safety training, badging lead times, and escort availability are worth raising early, because they shape the schedule more than the scanning does.

What we hand back

Every project closes with the data, a registration and QA report, and a short review call. The report states the control used, the residuals, the coordinate system, and any area we could not see. That last part matters: an honest coverage note is what keeps a modeler from inventing geometry behind a tank. See the deliverables page for formats.

Survey control, registration residuals, and modeling standards

Field accuracy starts with network geometry. On multi-room, multi-floor, or campus projects across New York, New Jersey, and Connecticut, our crews combine survey-grade terrestrial tripod LiDAR (2 to 3 mm single-station accuracy) with target-based and cloud-to-cloud registration to hold 3 to 6 mm network accuracy across the facility. Where mobile SLAM capture (10 to 25 mm local accuracy) or aerial RTK/PPK photogrammetry (1 to 3 cm horizontal accuracy under FAA Part 107 commercial UAS rules) is combined with terrestrial scanning, all sensors are locked to a shared survey control network.

Point cloud exports follow the ASTM E2807 standard for E57 3D imaging data alongside indexed Autodesk ReCap (.rcp/.rcs) and ASPRS LAS/LAZ geospatial point cloud specifications. When converting registered point clouds into native Autodesk Revit (.rvt, 2021–2025), IFC, or 2D AutoCAD (.dwg) drawings, our modeling matrix aligns with BIMForum LOD 200, LOD 300, and LOD 350 definitions and USIBD Level of Accuracy (LOA) guidelines so every modeled element is checked against the underlying scan before handoff.