Scanning a 250,000 Sq Ft Distribution Center in 4 Days

Forklifts humming. Pickers moving. Dock doors cycling every minute. We scanned a 250,000 sq ft distribution center just south of Columbus without stopping a single aisle. Four days on site. No shutdown, no racking emptied, no “come back after third shift.” Here’s exactly how we pulled it off, what accuracy we achieved, and what the data did for the client’s retrofit.

Project snapshot

• Location: Groveport–Rickenbacker logistics corridor (Columbus, OH)
• Facility: 250,000 sq ft single-story DC with 36-ft clear height, 38 loading docks, 64 pick aisles, 2 mezzanines, battery/charger rooms, and compressor/MCC rooms
• Objective: Full interior as-built point cloud and base drawings to support conveyor upgrades and a new HVAC layout
• On-site time: 4 days (two-person crew, 10-hour shifts)
• Tools: NavVis VLX3 mobile LiDAR (primary), Leica RTC360 (targeted static scans), control targets and survey ties
• Accuracy: ±6 mm registered to control; typical point density 5–10 mm at 10 m
• Deliverables: E57 master point cloud (320 GB), RCP decimated set (140 GB), LAS by zone, Revit LOD 200 model, 2D AutoCAD floor plans and RCPs
• Turnaround: Point cloud in 5 business days; Revit and CAD in 10–12 business days
• Impact: 0 hours of operational downtime; 18 RFIs avoided; ~ $95,000 estimated rework prevented

If you need the high-level version: this is what building 3D laser scanning looks like when it’s tuned for a live, high-throughput warehouse.

Site conditions that make DCs tricky

Distribution centers give reality-capture teams fits for three reasons:

1) Long, repetitive aisles and racking create SLAM drift risk.

2) Overhead MEP and top-of-rack strutwork hide in occlusions.

3) People and forklifts never stop moving.

We walked the site the afternoon before Day 1. The operations lead showed us the busiest aisles, the quiet windows (5:15–6:45 a.m. pre-shift; 11:30–12:30 lunch), and a “golden path” around the dock doors that stays passable. We also spotted two problem areas: a conveyor penthouse where the slab jogged 1-1/2 inches at an old expansion, and a battery room with constant forklift swaps.

We planned the sequence accordingly: knock out dock and mezzanine loops early, then burn down pick aisles in alternating sets to keep the SLAM happy and operations fed.

Capture strategy: mobile first, static where it counts

We leaned on the NavVis VLX3 for 85% of the footage. At walking pace, the VLX3 covered most aisles at roughly 18–22 minutes per 100,000 sq ft of continuous floor—so a single full-building loop averaged 55–65 minutes. That pace isn’t magic; it’s how we structure the loops.

• Closed loops by zone. We split the building into five zones with 360-degree loop closures. Each zone tied into two adjacent loops at choke points.
• Anchored to control targets. We staged 28 checkerboard and 12 spherical targets across the slab and mezzanines, shot to the owner’s control (local grid). This capped cumulative drift and kept the whole cloud seated on the facility grid.
• Alternated aisles to reduce repetition. Instead of marching Aisle 1 to 64 in order, we scanned 1, 3, 5… then doubled back for 2, 4, 6. That pattern improves SLAM feature variety.
• Paused for top-of-rack capture. We paused in certain spans to get overhead structure from cross-aisle vantage points.
• Brought in the tripod when needed. The Leica RTC360 handled the conveyor penthouse, MCC, and long-shot diagonals across the floor for crisp steel flanges and roof bracing. 74 static setups, average spacing 45–60 ft.

We didn’t ask the client to empty racking. Instead, we leveraged oblique passes at the ends of runs and mezzanine overlooks to peek into bays. You won’t see through pallets—no sensor will—but you can pick up frames, posts, and bracing from multiple angles with smart pathing.

If you want a primer on how this walking-pace capture works under the hood, this piece goes deeper: inside the NavVis VLX3.

Safety and operations: scanning around the work

Two rules: we never block an aisle and we never outrun our spotter.

• Two-person crew at all times: operator + spotter with radios.
• High-vis banners and cones only at loop connection points for 5–7 minutes at a time.
• Dock doors: we hugged the wall, never the pit edge.
• Battery room: captured during the planned 20-minute forklift swap lull.

We coordinated the day’s path every morning in the shipping office. The ops manager slid magnets around their route board; we mirrored with our scan path and times. It sounds simple. It’s what kept us invisible.

“We didn’t shut down a single bay. I actually forgot they were in the building by Day 3.” — Facility Manager, Columbus DC

Accuracy, control, and QC

Mobile LiDAR is only as good as its control and closures. We spent a solid half-day on Day 1 and one hour each on Days 2–4 doing nothing but target placement, loop checks, and QC.

• Control: The client provided a local grid and four known points. We expanded control to 40 points using targets.
• Registration: Hybrid approach—VLX3 SLAM with target constraints; RTC360 targetless cloud-to-cloud with tie-ins to targets for absolute alignment.
• Residuals: Mean loop-closure residual 4.3 mm; maximum 7.2 mm in the tallest bay (36-ft clear).
• Alignment: RTC360-to-VLX3 tie-in RMS 5.1 mm (six shared control spheres).
• Density: Typical 5–10 mm spacing at 10 m; better than 3 mm within 3 m for static setups.

We don’t publish “manufacturer brochure” numbers. These are the metrics from the registration report we hand over with every job. If you’re curious how our tolerances map to deliverables, see our guide on how to write a 3D scan deliverable spec.

Deliverables and file sizes

The client’s design team wanted one master cloud plus lightweight subsets for vendor coordination. We delivered:

• E57 master (full building, unified coordinates): 320 GB
• RCP (Autodesk ReCap) decimated to ~12 mm aggregate density: 140 GB
• LAS by zone (5 files, each 18–26 GB) for vendor-specific viewers
• Revit LOD 200 model: grid, columns, beams, joists, perimeter walls, dock equipment, rooftop units and curbs (from ladder access), major MEP mains, and mezzanines
• 2D AutoCAD: floor plan, roof plan, reflected ceiling plan, column schedule, dock elevation sheets

We turned the point cloud in 5 business days. The Revit model and 2D sheets followed in 10–12 business days. If you need different formats, we routinely export E57, RCP, LAS, and PTS, plus Scan to CAD linework. For BIM-heavy scopes, our Scan to BIM team handles LOD 200/300/400 with discipline-specific packages.

If you’re inventorying or checking stockpiles along with building capture, we can fold in volumetric scanning on the same mobilization.

What the data changed for the project

This wasn’t scanning for scanning’s sake. The owner had three near-term moves: a conveyor line extension over four aisles, a make-up air unit replacement on the roof, and a re-route of sprinkler mains that conflicted with new lighting.

• Conveyor supports: The vendor used our RCP to pre-fit five support frames off site. Field bolt-up took one night, not two.
• Sprinkler clearance: The model flagged two 1.75-inch interferences with lighting trays at Aisles 21 and 34. Solved on paper by shifting the lighting run 6 inches—no field rework.
• Roof curb reuse: We confirmed curb sizes and spacing off scans, avoiding a lift rental for a separate survey.

The GC counted 18 RFIs they didn’t have to write. They put a $95,000 value on avoided rework and schedule churn. Could it be more? Maybe. What matters is the scanner showed them the slab undulations, rack post plumbness, and MEP real estate they would’ve discovered the hard way.

For context on how other teams use this data up front, the estimating teams we support use workflows like those in Preconstruction Estimating with Point Cloud Data.

Why mobile LiDAR made the difference here

We still love tripods. We used them. But the spine of this job was SLAM. Warehouses are built for wheels and footsteps; scanning at that pace keeps up with the building.

Here’s the trade-off we explained to the client before we started:

The warehouse didn’t need every bolt fully modeled at LOD 400; the team needed reliable geometry and clearances. This is a classic case of why mobile LiDAR beats tripod-only approaches.

Workflow details our field team swears by

• Map the loop closures on paper before Day 1. Five loops for this footprint is the sweet spot.
• Place targets where SLAM is weakest: long, uniform aisles. We hit end caps and cross aisles so we can resection any segment.
• Mix capture heights. VLX3 already rides high, but mezzanine overlooks add crossfire on the top-of-rack steel.
• Respect reflective floors. Polished slabs can bloom returns. Slightly oblique paths help; so does avoiding wet-clean time.
• Pause at problem intersections. We stop and slow pan at MEP junctions to fatten the return. The data’s richer where decisions happen.

Behind the scenes, our registration stack runs target-constrained SLAM, then merges static scans with cloud-to-cloud alignment. We push out a registration report with residual histograms and screenshots so your QA team can sign off quickly. If you need formal as-built documentation packages, we wrap the metadata and drawings so procurement and closeout align with your standards.

“4 days” is capture. Don’t forget registration and QC.

Reality capture compresses field time, but the desk work still matters. For this facility, we scheduled:

• Day 1–4: Field capture and provisional QC (on-site checks each afternoon)
• Day 5–7: Registration (target tie-in, loop closure validation, static merge)
• Day 8–9: QA review with client; deliver E57/RCP/LAS
• Day 10–15: Modeling and CAD; issue Revit LOD 200 and 2D sheets

Skipping the registration window is the fastest way to miss expectations. We bake it into scopes and calendars up front. If you’re scoping your own project, our checklist on choosing the right 3D scanning provider is a good gut-check.

Cost and value, without the hand-waving

Every site is different, but for a 250k sq ft DC like this, two-person mobile-first capture with targeted tripod scans typically runs less than a week of MEP coordination headaches. The GC’s estimate put the payback inside the first phase of demolition, strictly from reduced surprises. As-built capture isn’t a silver bullet; it’s a bankable input that lets designers and supers make decisions with their eyes open.

If you’re new to this, our primer on modern as-built documentation lays out where point clouds fit in construction workflows.

Tips if you’re planning a DC scan

• Pick the accuracy you actually need. ±6 mm is more than enough for rack, MEP, and conveyor coordination at schematic and DD. Save LOD 400 for fabrication zones only.
• Lock deliverables early. Decide on E57 master plus either RCP or LAS subsets, plus whether you need a Scan to BIM model or just 2D floor plans.
• Time your quiet windows. Pre-shift and lunch are gold. If you have a night cleaning window, use it for mezzanines and docks.
• Share your grid. If your building runs on a plant grid, give us two points ahead of time so our control lands where you live.
• Give vendors access. Half the value comes when the conveyor or racking vendor can open the RCP and solve their own clearances.

Where this fits in your portfolio

We scan a lot of warehouses and process facilities across Ohio and the Midwest. If you’re in the business of retrofits, new process lines, or expansion joints, our industrial sector work will feel familiar. If you want to browse past engagements, the highlights live in our portfolio.

And if your scope runs beyond one building—campus work, multiple DCs—we can replicate this approach at scale. See how we handled a multi-building environment in our university campus case study.

What you get with ZEALOT

• Field-experienced crews who know how to be invisible in a live facility
• The right mix of SLAM and tripod scanning to hit accuracy and schedule
• Concrete deliverables in E57, RCP, LAS, Revit, and AutoCAD—no surprises on file size or naming
• Real QC: target reports, residuals, and documented loop closures
• A partner who writes scopes that protect you in procurement and during handoff

If you’re weighing options or just need to ballpark a scope, our team answers in plain English and backs numbers with past project stats.