Small Models, Large Work: MeshWorks Builds Toward Agentic Manufacturing

The BOM comes first

An agent cannot make a manufacturing process reliable if the underlying record is unclear. Before a model can prepare a purchase action, compare a revision, or explain a production risk, the team needs a consistent bill of materials with clear identity, ownership, hierarchy, and revision history.

That is why MeshWorks has kept the BOM at the centre of the product. The BOM connects engineering intent to procurement, suppliers, production, project costs, and customer communication. It gives every later action a place to be checked.

Why smaller models are useful

We are building agents around focused jobs rather than one system that tries to do everything. A smaller model can classify a part against rules, find a change between two BOM revisions, prepare a procurement batch, draft a supplier email, or identify missing information in a quote. Each job has a defined input, a visible result, and a clear point where a person can review it.

This approach is practical for engineering teams. It keeps the context close to the task, makes failures easier to investigate, and lets the platform choose a model that fits the work. A model can propose an action. The project record, permissions, and approval rules still decide what happens next.

What the CAD add ins are for

Neutral CSV and Excel imports remain an important part of MeshWorks because companies work with many design systems. Native connections add depth where a team needs a shorter path from design to operations.

The first native connection is being developed for SOLIDWORKS. The work is focused on bringing useful assembly context into the MeshWorks record, including part identity, parent and child relationships, configurations, weldments, and cut list information where the source provides it. The integration path is designed to authenticate the user, respect the target project rules, and return a receipt for an accepted update.

The purpose is not to remove engineering judgement. It is to reduce repeated export work and make the impact of a design change easier to trace through the records that follow it.

SOLIDWORKS first, Inventor next

Autodesk Inventor is the next planned native connection. It needs its own adapter because its API and host environment differ from SOLIDWORKS. Both adapters should use the same MeshWorks contract for authorization, project selection, hierarchy handling, and controlled updates. That keeps the platform consistent while allowing each CAD tool to retain its own engineering context.

The open import route remains available for teams that prefer a neutral file, work with legacy systems, or receive design data from customers. Native connections and neutral imports are two entry points to the same manufacturing record.

Large tasks need controlled steps

Manufacturing work is large because it is connected. A change to one part can affect purchasing, stock, supplier communication, production timing, cost, and delivery. The useful role for an agent is to follow those links, gather the relevant evidence, and prepare the next bounded step.

MeshWorks is wiring that model into the platform. Agents work with the same project state as the team, explain what they found, and operate within the permissions and confirmations already defined for the organisation. The record stays authoritative and every accepted change can be traced.

The local boundary remains yours

The same principle applies to deployment. In a customer managed, fully offline installation, the BOM and related project information stay on the company infrastructure. MeshWorks cannot see that data in that profile. Optional services such as email, AI assistance, analytics, or update channels are deployment choices that the organisation can review and enable deliberately.

Start with the process

The first step toward workflow automation is not choosing a model. It is making the BOM process dependable. MeshWorks can help teams define part identity, ownership, revision rules, approval points, and the links between engineering and operations. Once that foundation is clear, focused agents can take on useful work without becoming a second source of truth.

That is the direction of the product: open CAD entry points, a robust manufacturing record, and small, accountable automations that help teams move large jobs forward.