Open a BIM model in your favorite cloud viewer and zoom into a curved wall or a cylindrical column. You will likely discover that the curve isn’t actually a curve: it is a polygon approximation, a series of flat faces assembled to mimic roundness. Zoom in far enough, and the illusion shatters.
Most people accept these jagged edges as a fact of life in BIM modellers and viewers. We don’t. We do not think this is a display glitch; it is a fundamental failure of the underlying geometry engine.
This article makes the case for why Boundary Representation (B-Rep) is the only geometry standard capable of meeting the precision requirements of BIM 2.0, and why this distinction dictates the success of your project long after it leaves the screen.
What is B-Rep, and why does it matter?
B-Rep defines a 3D solid by mathematically describing its exact boundaries. Think of it like a hollow cardboard box: instead of approximating the volume, a B-Rep model commands the geometry through its precise constituent parts:
- Faces: the surfaces enclosing the object.
- Edges: the intersections where faces meet.
- Vertices: the exact points where edges meet.
B-Rep’s true power lies in its topology. The system understands how these elements connect. Modify one vertex, and the adjacent edges and faces update automatically. This topological intelligence separates B-Rep from static, simpler geometry formats.
Mesh geometry: Good for visualization, dangerous for engineering
Most cloud-based BIM viewers and many authoring tools rely on mesh geometry: a collection of triangles or quads that approximate a shape. While meshes render efficiently in a browser, they are inherently imprecise.
Think of mesh geometry as a low-resolution photograph: it looks fine from a distance, but zooming in reveals the underlying grid. A B-Rep model, by contrast, functions like a vector graphic. The geometry remains mathematically defined and perfectly precise at any scale.
This distinction fundamentally breaks traditional BIM workflows:
- Mesh models force quantity approximations. You calculate surface areas and volumes from polygon counts, not exact geometry. On large-scale projects, these small inaccuracies snowball into material and cost errors that are difficult to detect and expensive to fix.
- Mesh pipes break section cuts. A section cut through a mesh pipe produces a jagged polygon, not a circle. Dimensions derived from that section are, by definition, incorrect.
- Mesh-based clash detection traps you in a visual loop. It flags problems but fails to provide the geometric precision needed to resolve them. Engineers must retreat to separate authoring tools, fix the geometry, and rerun the detection. That's an iterative loop that drains time and adds coordination overhead.
- Mesh geometry destabilizes Boolean operations. Joining or subtracting meshes often produces "non-manifold" results. Errors where walls share surfaces rather than remaining geometrically closed and watertight.
How Qonic leverages B-Rep geometry
Qonic runs exclusively on B-Rep geometry. Our underlying modeling kernel supports NURBS surfaces and analytical geometry, representing every curve through exact mathematical definitions.
What you see in your browser is a mesh, simply because web browsers cannot yet render B-Rep directly. However, Qonic generates these meshes in real-time from the underlying B-Rep model. The Source of Truth remains exact; the visual representation merely follows.
This choice empowers every downstream workflow. When Qonic reports a volume, it extracts that figure from exact geometry. When you generate a section cut, Qonic calculates a mathematically accurate curve. When two elements intersect, you resolve the clash directly within the platform.
B-Rep: The language of the factory, not the animator
There is a useful way to frame the difference between B-Rep and mesh. Mesh is the language of the animator: optimised for visual output, rendered frames, and screen-based presentation. B-Rep is the language of the factory. CNC mills, laser cutters, robotic fabricators, and 3D printers all operate on precise geometric data derived from solid models. They do not understand approximations.
BIM 2.0 must bridge design and fabrication without translation loss. This bridge only exists when design and manufacturing share the same geometric DNA. Mesh files typically require extensive repair before they can reach a factory floor; B-Rep models export directly to CAM environments without loss.
Furthermore, B-Rep enables granular metadata attachment. You can assign properties to specific faces, edges, or vertices—not just the whole object. This precision is vital for operations like filleting or linking component-level data to the geometry it describes.
For Qonic, BIM 2.0 requires more than just an approximation of a building; it demands geometry that defines it, applying the same rigorous standards used in aerospace and automotive manufacturing to the built environment.
A note on complex freeform geometry
For complex organic forms, Qonic will incorporate SubD (subdivision surface modeling). SubD offers the artistic flexibility of meshes while enabling conversion to NURBS and therefore to B-Rep solids suitable for engineering. We expect to release SubD capabilities in 2027.
On Universal Scene Description (USD)
We are following USD closely. Currently, the standard supports only mesh geometry. Qonic’s roadmap includes USD compliance as soon as the standard provides robust support for B-Rep schemas. This is essential for maintaining solid-modeling integrity in collaborative pipelines.
What’s next
This is the third article in a ten-part series exploring the technical requirements of BIM 2.0 by Erik de Keyser. You can read the original article here. In our next article, Erik will tackle 3D modeling and 2D drawings and why we must rethink the relationship between model and output for the next generation of construction.
Try Qonic
Ready to see the difference between mesh and math? Explore B-Rep modeling directly in your browser: app.qonic.com
Questions or feedback? Email us at info@qonic.com, connect on LinkedIn, or join the Qonic community to continue the conversation.
