Scan-to-BIM automation: what software can do between the point cloud and the model
Zakhar Vityk, CEO, Consedge Tech
"Automatic scan to BIM" is promised often and delivered rarely. The honest picture is more useful. Some steps between a point cloud and a Revit model automate very well. Others still need a person who understands buildings.
This article goes through the pipeline step by step, shows where software helps today, and explains why assisted modelling plus automated checking is the practical target for scan-to-BIM automation.
The pipeline, and what automates
| Step | Automates well? | Notes |
|---|---|---|
| Capture | Partly | Scanners and mobile mapping are fast. Planning the scan positions is still a skill |
| Registration | Yes | Scanner software aligns scans largely on its own. A person checks the result |
| Cleaning and indexing | Yes | Noise filtering, decimation and conversion to RCP are routine |
| Levels and main planes | Yes | Floors, ceilings and large walls are found reliably as planes |
| Topography | Yes | Ground points become a surface with little manual work |
| Pipes and round ducts | Mostly | Cylinders fit well. Fittings, insulation and tight plant rooms are harder |
| Walls, openings, structure | Partly | Geometry is found. Type, thickness and what is hidden are decisions |
| Ornament and irregular forms | No | Heritage detail is modelled by a person |
| Checking model against scan | Yes | Deviation is a calculation |
The amber and red steps are where a project's budget goes, and where an accuracy agreement matters most.
The pattern is consistent. Software is good at geometry and weak at meaning. It finds a plane. It does not know whether the plane is a fire wall or a partition that will be demolished.
What still needs a modeller
- Interpretation. Which wall type this is, what is behind the ceiling, which pipe belongs to which system.
- Idealization. An old wall leans. Should the model lean, or show a vertical wall with a note? That depends on what the model is for.
- Level of detail. A model for a permit and a model for prefabrication need different things from the same scan.
- Families and standards. The client's template and naming rules.
These decisions are where an experienced modeller earns their fee. Automation should give them more time for it.
Assisted modelling inside Revit
The most productive tools are not fully automatic. They work with the modeller, one element at a time.
- The modeller picks a spot on the cloud.
- The plugin samples the points around it and fits a plane or a cylinder.
- The plugin creates the element, a wall, floor or pipe, aligned to the fit, with the type the modeller chose.
- The modeller accepts or adjusts it.
The same idea covers larger steps: levels proposed from horizontal planes, a toposolid generated from ground points, a grid of sections cut through the cloud for tracing.
What decides adoption is not the algorithm. It is clicks per element. A tool that fits a wall perfectly and needs six clicks loses to tracing by hand.
Automate the checking first
If only one part of the process is automated, it should be verification.
A deviation check compares every modelled surface with the nearest scan points and colours the result. It shows in minutes where the model is off by more than the agreed tolerance. Without it, accuracy is a promise. With it, accuracy is a report that ships with the model.
This also changes how work is reviewed. A lead modeller looks at a colour map instead of spinning through the model looking for mistakes.
Agree accuracy before modelling
Most disputes about scan-to-BIM deliverables start with an unstated expectation. Three things should be written down before work starts:
- the level of detail per discipline,
- the tolerance between model and scan, and where a stricter one applies,
- what is modelled as built and what is idealized.
LOD 300 suits most design and permit work. LOD 350 to 400 is for fabrication, renovation detailing and facility management.
Where AI stands
Machine-learning models that label points as wall, floor, pipe or furniture are improving quickly, and they are good at speeding up the first pass. Their output still needs checking against the scan. Treat them as a faster way to produce a draft, and keep the deviation check as the judge.
Our work in this area
Consedge Tech works on both sides of this topic. Our BIM production team models from point clouds and drawings at LOD 300 to 400: heritage buildings for restoration documentation, industrial facilities and MEP-heavy projects in the US and Europe.
On the software side, we have worked on Revit plugins for scan-to-BIM teams, including a redesign of their interface driven by feedback from the modellers who use them every day. That is where the "clicks per element" lesson above comes from.
If you run a scanning or modelling business and want a tool around your own process, book a Feasibility Review. You get a written verdict on what can be automated and what it depends on. If you need the model itself, see BIM production. More on tools: plugin development.
FAQ
Can scan to BIM be fully automated?
Not today for a complete building model. Planes, levels, topography and many pipes can be created automatically. Interpretation and detail still need a modeller.
Which point cloud formats does Revit accept?
Revit links RCP and RCS files. Other formats, such as E57, LAS or PTS, are converted first.
How accurate is a model made from a scan?
As accurate as the scan and the agreed tolerance allow. Ask for a deviation report that shows the difference between model and point cloud.
What level of detail should I ask for?
LOD 300 for most design and permit work. LOD 350 to 400 for fabrication, renovation and facility management.
Working on something like this?
Thirty minutes with the engineers who would build it, then a written verdict — including “don’t build this” where that is the answer.
- First call free, no obligation
- Straight answers
- Fixed-price written verdict
- Senior engineers, not account managers