Scan-to-CAD Software Workflow: From Point Cloud and Mesh to STEP, IGES, SolidWorks, and Parametric Models
A raw mesh dropped into SolidWorks does not behave like a normal part. There is no original feature tree, no sketch history, and no design intent carried over. It is just triangles, thousands or millions of them, sitting in the workspace as a single body that needs work before it edits like a native part. Getting from that mesh to a part you can actually redesign is a separate piece of software work, and it trips up more reverse engineering projects than the scanning itself does.
This guide walks through that pipeline stage by stage: what a scanner actually captures, why STL, OBJ, and PLY are not CAD files no matter how clean they look, what makes STEP and IGES different from a mesh, and where SCANOLOGY's own software sits in that chain before a model ever reaches SolidWorks or another CAD system.
The Pipeline in Five Stages
Every scan-to-CAD project moves through the same five stages, whether the part is a turbine blade or a plastic bracket. Skipping a stage, or trying to compress two of them into one export button, is where most of the frustration in this workflow comes from.
| Stage | What happens | Typical file output |
|---|---|---|
| Capture | Scanner records point cloud data on the part surface | Raw point cloud |
| Meshing | Points are triangulated into a connected surface | STL, OBJ, or PLY |
| Cleanup | Noise removal, hole filling, smoothing to a watertight mesh | Cleaned STL/OBJ/PLY |
| Reconstruction | Surfaces and features are rebuilt over the mesh as solid geometry | Native CAD file |
| CAD export | The rebuilt model is exported for use in other software | STEP or IGES |
The first three stages are handled by scanning software. The last two require reverse engineering software with parametric or surface modeling tools, which is a different category of program built for a different job.
What Actually Comes Off the Scanner: Point Cloud to Mesh
A 3D scanner does not capture a solid part. It captures a point cloud: a set of coordinates in space, each one representing a spot on the surface the scanner could see. On its own, a point cloud has no connectivity between points and no defined surface.
SCANOLOGY's DefinSight software handles the next step during the scan itself, triangulating that point cloud into a polygon mesh in real time as the scanner moves. Pair it with a handheld scanner such as KSCAN-E, rated at up to 0.020 mm accuracy and 8.29 million measurements per second, or the smaller SIMSCAN-S Gen2, rated at up to 0.015 mm accuracy, and the operator watches a usable mesh build up on screen rather than a cloud of disconnected dots.

That mesh is a major step up from a raw point cloud, but it is still nowhere near a CAD file. It has geometry. It does not have a feature history, editable faces, or the boundary definitions a CAD kernel needs.

STL, OBJ, and PLY: Why a Clean Mesh Still Isn't a CAD File
STL, OBJ, and PLY are the three formats most scanning software exports, and each is built for a slightly different purpose. STL describes geometry only, as a set of connected triangles, and is the most common export for 3D printing and inspection work. OBJ adds references to external texture files for realistic visual rendering. PLY assigns color data to individual vertices, which is why it shows up often in cultural heritage and visualization work.
What none of the three formats carries is parametric structure. A mesh is a static shape made of flat triangular facets. There is no sketch behind a curved surface, no equation defining a hole's diameter, and no way to say "make this fillet 3 mm instead of 2 mm" the way you would in a native SolidWorks or Siemens NX part. A mesh represents geometry that already happened, not geometry you can drive with parameters.
That distinction is exactly why reverse engineering software exists as a separate category. Turning a mesh into a genuine CAD model means drawing parametric surfaces and features directly over the scanned triangles, not just changing the file extension.
STEP and IGES: What Actually Makes a File "CAD"
STEP (ISO 10303) and IGES are the two neutral formats most CAD systems use to exchange solid and surface models, and the difference between them and a mesh comes down to how the geometry is defined. A STEP file commonly stores a part as a boundary representation, or B-rep. Its surfaces, edges, and vertices are defined by exact mathematical equations rather than a fixed set of flat triangles, which is what lets CAD systems exchange complete, unambiguous product geometry instead of an approximation of it, as NIST's overview of the STEP standard describes.
IGES predates STEP and is still in use, particularly on older CAD installations and where a specific supplier requires it. Both formats can carry precise surface and solid geometry, but STEP has become the default for modern CAD exchange because it handles a broader range of product data and tends to translate more reliably between systems.
SIMSCAN-S Gen2's own output list, according to the current product specifications, includes .igs alongside .stl, .obj, .ply, .asc, .txt, .mk2, and others. An IGES export straight from scan software is useful when a downstream system needs that format, but it does not by itself give you a rebuildable feature history, sketches, or dimensions. As SCANOLOGY's own workflow guide on going from scan to STEP puts it, a scanning platform's job stops at an accurate mesh. Getting a true parametric part, the kind with a fillet you can resize or a hole you can redimension, still means reconstructing the geometry in dedicated reverse engineering software rather than relying on a direct format export from the scanner.
Mesh to Solid: Where the Reconstruction Work Actually Happens
This is the stage that determines whether a scan-to-CAD project produces something an engineering team can actually redesign. Reconstruction software works by fitting real CAD geometry, planes, cylinders, extrusions, and freeform NURBS surfaces, onto the scanned mesh, one region at a time, until the mesh underneath becomes an editable solid or surface model.
SCANOLOGY's DefinSight MODEL is built specifically for this stage. According to its current product page, it can align scan data by features, by scan-to-scan comparison, or by scan-to-CAD comparison, and it supports direct sketching and surface fitting on the mesh. SCANOLOGY describes its modeling approach as fully parametric hybrid modeling, meaning a single part can carry both exact, dimension-driven features and freeform surfaces. It also includes standard solid-modeling operations, roll and unroll, helix, draft, move face, loft, blend, shell, and thicken, along with real-time deviation control so the reconstructed surfaces can be checked against the original scan as the model is built rather than only at the end.

That hybrid approach is useful on parts that mix organic shapes with functional features. A purely automatic surfacing pass can wrap a smooth NURBS skin over an organic shape quickly, which is fine for a housing or a fairing where the surface itself is the design intent. A part with functional features, bolt holes at a specific diameter, a bore that has to match a mating shaft, a flat face that has to stay perpendicular to a datum, needs those features rebuilt as actual parametric geometry, not just a surface that happens to pass through the same points. Hybrid modeling means an engineer can use automatic surfacing where speed matters and switch to feature-based, dimension-driven modeling where the part's function depends on getting a specific value exactly right.
Handing the Model to SolidWorks and Other CAD Systems
Once a part exists as either a cleaned mesh or a reconstructed solid, the next question is how it lands in the CAD system an engineering team actually works in day to day. There are two common paths, and they produce very different results.
The first path imports the mesh or point cloud directly into the CAD software using a dedicated add-in. SOLIDWORKS ScanTo3D, available in higher SOLIDWORKS tiers, is a common example: it reads mesh and point-cloud files into SolidWorks, lets an engineer section and sketch directly against the scan data, and walks through a surface wizard that fits organic surfaces automatically and guides the extraction of simpler analytic regions like cylinders and planes. This keeps the whole rebuild inside one program, which is convenient for occasional reverse engineering work but ties the process to whichever CAD license and add-in tier the team already owns.
The second path builds the model in dedicated reverse engineering software first, such as DefinSight MODEL, then exports it as a neutral CAD file for SolidWorks or another platform to open. This is generally the more reliable route for complex or highly featured parts, since the reconstruction work happens in software purpose-built for it rather than as an add-in bolted onto a general CAD package, with the current release's export options determining exactly which neutral formats are available at handoff.
The tradeoff to know going in: a STEP import typically arrives in SolidWorks as a single imported body without SolidWorks's own native feature tree, so an engineer edits it with direct-editing tools, moving or deleting faces, rather than rolling back through a parametric history the way they would with a part built from scratch. That is a normal, expected limitation of file-based CAD exchange, not a defect in the reconstruction. It is also exactly why the roll/unroll, move-face, and shell tools built into reconstruction software like DefinSight MODEL matter: they let an engineer do a meaningful amount of that editing before the file ever leaves the reverse engineering stage.
How Much Rebuild Do You Actually Need?
Not every scan needs a full parametric rebuild, and pushing every project through the most expensive path in this pipeline wastes time without adding value. The right amount of reconstruction depends on what the model is for.
A cleaned mesh, exported as STL or OBJ, is enough when the end goal is 3D printing, a quick visual comparison for a colleague, or a lightweight reference model that nobody plans to redesign. SCANOLOGY's ScanViewer handles that lighter tier directly, including distance checks, GD&T call-outs, and color deviation maps, without requiring the mesh to ever become a parametric solid.
A surface wrap, meaning a fitted CAD surface built with automatic surfacing rather than individual features and exported as STEP or IGES, is enough when the geometry needs to go into finite element analysis, a CNC toolpath, or a one-time manufacturing run where nobody expects to change the design afterward. It gives you real CAD surfaces without the added time of feature-by-feature reconstruction.
A full parametric rebuild is worth the extra time when the part is going back into an active design process: tooling that needs a dimension changed, an obsolete component being reproduced with a manufacturing update, or a part that has to mate precisely with other components in an assembly that is still being revised. That is the case DefinSight MODEL is built around, and it is the point where the extra reconstruction time pays for itself in how much of the resulting file an engineer can actually edit later.
Frequently Asked Questions
Can I just convert an STL file to STEP automatically? Not in a way that produces genuine parametric CAD. Format converters can wrap a mesh's triangles in a B-rep shell, but the result is still a fixed surface with no features, no editable dimensions, and no design intent. A real STEP deliverable requires reconstructing the geometry in reverse engineering software, not just changing the file extension.
Why doesn't a direct export from scanning software give you a parametric STEP model? Direct format export from a scanner covers the mesh or a simple surface representation of it, which a format like IGES can carry. A parametric solid with rebuildable features requires the reconstruction step that dedicated reverse engineering software, such as DefinSight MODEL, performs, which is a distinct stage from scanning itself.
Do I need DefinSight MODEL if I already have SolidWorks with ScanTo3D? It depends on part complexity and how often the team does this kind of work. ScanTo3D keeps simpler reconstruction inside SolidWorks, which is convenient for occasional projects. For parts that combine datums, bores, or other functional features with organic surfaces, dedicated reverse engineering software like DefinSight MODEL brings more complete hybrid parametric and freeform surfacing tools to that mix, which is where a dedicated tool starts to save real time over an add-in.
What is the difference between STEP and IGES in practice? Both formats can carry precise CAD geometry, but STEP is the current default for most CAD systems because it handles a broader range of product data and tends to translate more reliably between platforms. IGES is older and still shows up on legacy installations or where a specific supplier requires it. Use STEP unless you have a specific reason to use IGES instead.
Does a parametric rebuild change the part's dimensions? It should not, if the reconstruction is done against the scan data with deviation checking, which is what DefinSight MODEL's real-time deviation control and tools like ScanViewer's color deviation maps are for. The rebuilt surfaces are fit to the scanned points and verified against them, not redrawn from a fresh guess at the part's shape.