In conversations with investors and project managers, the phrase “3D model” comes up frequently — and often means something completely different to each party. For some it’s an impressive visualisation, for others a spatial design or a basis for further engineering, and for others still it is a technical database, or even the point cloud itself, the direct output of 3D laser scanning.
Yet behind this single term lie products of fundamentally different structure, capability, and price. Confusing them when ordering a service is one of the most common sources of misunderstandings and can cause unplanned costs.
Two Products That Look Alike
Side by side, a mesh model and an engineering (CAD) model can look nearly identical. Both represent an object in three dimensions; both are derived from a point cloud. That is where the similarities end.
A mesh model records an object’s surface as a dense grid of triangles — vertices, edges, and faces mapping the shape in a 3D space. Most of the model generation is automatic and happens by converting a point cloud into a polygon mesh, or as an export from an existing CAD model (a process that cannot be reversed). This makes it relatively quick and inexpensive to produce. It can be enriched with real-world texture and color, making it visually attractive and highly readable in presentations.
More on mesh models can be found in our previous article: Mesh Models in 3D Scanning – Why Quality Starts at the Survey Stage
A CAD model is an entirely different philosophy. In the context of industrial plant documentation, two variants are worth distinguishing.
Primitive-Based CAD
Primitive-based CAD uses simple solids — cylinders, cuboids, cones, spheres — each described analytically with just a few parameters. This is the native format for plant design environments such as AVEVA E3D: the file is lightweight and can be imported without loss of data. When each primitive is enriched with technical attributes such as line number, material specification and operating parameters, it becomes what is known as a smart solid: an object that carries both geometry and a full information layer, forming the backbone of intelligent databases and Digital Twins.
Solid Modeling CAD
Solid modeling CAD (as used in Solidworks, CATIA, or Inventor) describes objects through their boundary surfaces and supports arbitrarily complex geometry — including holes, cutouts, and castings. It is fully editable within CAD environments. However, when imported into AVEVA it loses its structure and is reduced to a polygon mesh, making it unsuitable as a basis for plant design work.
Where Does the Difference Matter in Practice?
The key difference becomes apparent the moment a model needs to serve as a working tool rather than just spatial documentation.
A mesh model, without advanced decimation (deliberate simplification of the mesh), is a collection of enormous amounts of data. Such a “heavy” file can significantly slow down or completely block work in standard design software. The size of an individual triangle is critical: the finer the mesh, the more faithful the surface representation — but a finer mesh also means a heavier file, making any further processing much more difficult and time consuming.
More importantly, a mesh model is not suited for engineering-related editing. Geometry can be manipulated to a limited degree, but generating engineering outputs such as revised pipe diameters, repositioned equipment axes, or flat documentation, is not what the format is designed for.
A CAD model has none of these limitations. Every element can be modified freely in its dedicated software — though only the primitive-based model retains full functionality in plant design environments. Developing a CAD model from a point cloud is far more time-consuming than generating a mesh, because it requires manual engineering work, but the result is a product that genuinely supports further design work.
Where Does a Mesh Model Work Best?
A mesh model has undeniable strengths for specific applications. It excels wherever exact reproduction of irregular shapes is required. The most common use cases include:
- Digitisation of heritage objects, sculptures, and architectural details
- Marketing visualisations and investor presentations
- Volume measurements of open-pit mines, excavations, or stockpiles of bulk materials
- Passive clash detection for newly designed elements (as a faithful representation of the existing environment)
The real problem arises when a mesh model ends up in applications it was never designed for — for example advanced design and retrofitting of industrial installations, or pipeline prefabrication. If clash analysis requires editable geometry of the surrounding environment and designers need to insert and modify conflicting elements of the existing as-built state, the mesh model is simply not the right tool for the job.
The False Economy
A mesh model is cheaper — and that is a fact rooted in the automation of its creation. A CAD model requires hours of engineering work on every installation element, which translates to a higher upfront cost.
The problems begin when the cheaper product is ordered for purposes it is not suited for. Choosing a mesh model with the intention of later designing a retrofit often ends in having to redo the entire modeling process from scratch — this time to CAD standards. If the wrong format is chosen, the total cost becomes significantly higher while timeframes are extended, causing project schedule delays.
How to Make the Right Decision
The choice of format should follow directly from the intended use of the data:
- A mesh model is the right choice for documenting objects with complex, irregular forms, for visualisations, and wherever exact reproduction of appearance is the priority.
- A primitive-based CAD model — as a plant model in AVEVA E3D, a smart solid, or an intelligent BIM model — is the right choice for retrofit design, installation prefabrication, and building a digital asset database.
It is also worth remembering that in many projects the optimal approach is a hybrid one — the point cloud itself as a precise spatial backdrop for the entire facility, with CAD modeling only for key areas requiring technical attributes or editability. This delivers full functionality while optimising costs. We will cover this approach in more detail in upcoming articles in the series.
A conscious choice of data format is not just a technical matter — it is a strategic business decision that directly affects the schedule, budget, and usability of data throughout the entire project lifecycle.
Next article: As-Built vs Design Intent — why the “perfect” design rarely fits the reality of an industrial plant.
Not sure which data format is right for your project? Contact us — our experts will analyze your needs and advise which data standard will deliver maximum utility at optimal cost.
