3D CAD Modelling Services

We build parametric 3D CAD models for individual parts, multi-part assemblies and full machines, in the CAD platform your team already standardises on. Models are built to be usable downstream — clean feature trees, sensible mating and assembly logic, and dimensions that update predictably when a design changes, rather than a model that looks right today but breaks the moment someone changes a single parameter.

This service supports both new design work (turning a concept or sketch into a modelled, dimensioned part) and documentation of existing equipment (modelling from physical parts, legacy 2D drawings or point-cloud scan data). The two use cases require slightly different mindsets: new design modelling is about capturing intent and leaving room for iteration, while documentation modelling is about capturing reality accurately, including the quirks and asymmetries a real, worn or hand-fabricated part actually has.

Models can be delivered in native format alongside neutral formats such as STEP and IGES for use in other software, and we can produce derived 2D drawings, exploded views and BOMs from the same model on request, so you're not paying twice for work that should come from a single source of truth.

Feature-tree structure is something we pay close attention to, because it's usually invisible until it becomes a problem. A model built with a logical, top-down feature history is easy for your team to pick up and modify later; a model built purely to look correct in a single configuration becomes a liability the first time a dimension needs to change. We build models the way we'd want to inherit them if the project passed to someone else.

For assemblies, we pay particular attention to mate and constraint logic — under-constrained assemblies can move in ways that aren't obvious until a downstream simulation or a physical build reveals the problem, and over-constrained assemblies fight themselves every time a dimension changes. Getting this right at the modelling stage saves significant rework later, particularly on larger assemblies with dozens or hundreds of components.

Where a model is being built to feed FEA, CFD or another simulation tool, we clean up geometry specifically for that purpose — removing cosmetic features that add mesh complexity without adding engineering value, and confirming with you which simplifications are acceptable for the analysis being run.

A model handed between people over the life of a project accumulates history — features added by one person, patched by another, adjusted under time pressure by a third. Left unmanaged, that history becomes a liability: a feature tree with unclear intent, redundant constraints, or workarounds nobody remembers the reason for. We treat model hygiene as an ongoing responsibility on longer engagements, not a one-time clean-up exercise, so a model handed off after several revisions is still something a new engineer could pick up and understand.

Configuration management deserves specific mention for teams developing a family of related products. A single master model with well-structured design tables or configuration parameters lets a team generate several product variants without maintaining separate files that inevitably drift apart over time — one variant getting a fix the others never receive, for example. Setting this structure up correctly at the start saves considerably more effort than retrofitting it after several variants already exist as independent, diverging files.