Renovation design
Build an existing-condition reference around the elements the design team will retain, remove, connect to, or modify.
Point cloud / defined model scopeMODEL 02
Scan-to-BIM that models the right information, not every visible point.
A smaller model with the right categories, alignment, and limitations is usually more valuable than a visually impressive model that does not support the next design decision.
DIRECT
ANSWER
What does this service do?
Scan-to-BIM converts a reviewed point cloud into selected building or facility geometry for a BIM workflow. The result is not an automatic digital twin: model categories, detail, tolerances, coordinates, naming, file version, and non-geometric information must be defined before production.
USE / FIT
Start with the project condition
When this workflow earns its place.
Match the method to the uncertainty or decision it must resolve. Equipment and output follow from that use.
MEP coordination
Model agreed systems, equipment, structure, and clearance context in congested areas.
Documentation baseline
Create a controlled model for drawing production, quantity review, or facility planning.
Interface design
Represent the geometry needed for new assemblies, routes, supports, or prefabricated connections.
Before productionSCOPE INPUTS
Four decisions that keep the data useful.
- 01Categories
- Walls, floors, structure, equipment, ducts, pipes, cable tray, or other agreed elements.
- 02Representation
- Model detail, geometric tolerance, family strategy, simplification, and irregular-condition rules.
- 03Coordinates
- Shared coordinates, levels, grids, origin, units, true north, and any survey relationship.
- 04Environment
- Revit release, worksets, naming, classification, parameters, linked files, and exchange format.
Controlled sequenceMODEL 02
From requirement to reviewed handoff.
- 01
Accept data
Confirm the registered point cloud, coverage, coordinate basis, and reference documentation.
- 02
Set rules
Agree categories, detail, tolerance, families, exclusions, and treatment of irregular geometry.
- 03
Establish framework
Create project coordinates, levels, grids, and the model organization expected downstream.
- 04
Model
Develop only the selected visible geometry against the reviewed cloud.
- 05
Compare
Review representative sections, overlays, and decision-critical areas against the source data.
- 06
Handoff
Package model, point-cloud references, notes, exclusions, and software/version information.
Project-definedOUTPUTS
Files are selected for the receiving workflow.
No format or derived deliverable is automatic. The project scope confirms coordinates, detail, organization, software version, and the intended use.
Revit model
RVT produced for an agreed software release, category list, and project standard.
IFC exchange
An IFC export may be included when the receiving platform and exchange need are defined.
Model + cloud package
Coordinated model, reference point cloud, readme, and agreed review material.
Derived documents
Plans, sections, or elevations when drawing production is part of the engagement.
QA / REVIEW
Model QA should test fitness for use, not visual resemblance alone.
Representative slices and decision-critical areas are compared to the registered data. The handoff should also verify origin, units, levels, grids, file version, category coverage, and documented exclusions.
Scope boundariesREAD BEFORE USE
What the workflow does not automatically establish.
- Only visible, captured, and agreed elements can be modeled with confidence.
- LOD labels alone do not define tolerance, irregularity, family behavior, or information requirements.
- Modeled objects may intentionally simplify sag, deformation, damage, or nonstandard construction.
- A Scan-to-BIM model is not automatically a record drawing, fabrication model, or code-compliance assessment.
Technical answersFAQ
Questions project teams ask before they commit.
What does “point cloud to Revit” mean?
It means using a registered scan dataset as geometric reference while creating selected native or project-approved Revit elements. The exact categories and level of representation must be agreed.
What LOD should an existing-condition model use?
Use the least detailed representation that supports the project decision. Define element categories, geometric tolerance, family behavior, irregular-condition treatment, and required properties instead of relying on an LOD number alone.
Are concealed systems included?
No, unless another verified source is supplied and its use is explicitly documented. Laser scans record what is visible from the capture positions.
Can you use a customer-supplied point cloud?
Often yes. The team first reviews format, registration, coordinates, coverage, density, noise, and whether the source data supports the requested model scope.
Next coordinatePROJECT / SCOPE
Define the site. Define the output. Then plan the capture.
Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.