How SOLIDWORKS LEO Is Changing the Way Mechanical Engineers Approach CAD Design

By Panshul Technologies LLP

How SOLIDWORKS LEO Is Changing the Way Mechanical Engineers Approach CAD Design

Most software assistants answer questions. SOLIDWORKS LEO is designed to do something more specific: reason about your engineering design and act on it inside your active SOLIDWORKS session. For senior engineers, CAD professionals and engineering managers, that shifts the conversation from “can AI chat about CAD?” to “which parts of my daily workflow can I safely delegate?”


What is LEO?


LEO is one of the SOLIDWORKS AI virtual companions, alongside AURA and MARIE. At 3DEXPERIENCE World 2026, Dassault Systèmes described LEO as the companion that brings engineering reasoning across mechanics, structures, motion, simulation and manufacturing.

In practice, LEO is a conversational layer on top of your design environment. You state an objective in everyday language, LEO interprets it, selects an appropriate skill, asks for clarification when needed, and in many workflows takes action in the open model or assembly.


Because LEO’s skills work on the designs and drawings loaded in your session, it is available inside SOLIDWORKS rather than as a standalone web assistant. Access runs through a Virtual Companions or Labs tab in the task pane, and your session must be connected to the 3DEXPERIENCE platform.


What can LEO do today?


Based on SOLIDWORKS’ own What’s New material for the 2026 functional deliveries that lead into 2027, LEO’s skills fall into a few groups.


Modelling and geometry


  • Convert imported STEP or IGES geometry into native, editable SOLIDWORKS features
  • Generate assembly structures from a prompt
  • Explain rebuild and sketch errors, with guidance on what went wrong
  • Select entities from a plain-language description, across parts, assemblies and drawings

Performance and analysis


  • Find assembly performance bottlenecks based on structure, component complexity, rebuild behaviour and graphics load, then act on them, for example by creating SpeedPaks or suppressing threads
  • Flag which components and subassemblies a change affects before you make it, and warn if a geometry change causes fit issues



Documentation and automation


  • Generate drawing views, dimensions, annotations and sheet layout from a described intent
  • Produce step-by-step assembly instructions with visual snapshots, editable before you export
  • Generate macro logic from a natural-language description and refine it conversationally
  • Apply or update material appearances across an assembly

Knowledge and data


  • Answer SOLIDWORKS best-practice questions in context
  • Surface PLM information such as configurations, open tasks and change history without leaving the session

The 2027 roadmap adds further LEO skills, including Spec to CAD, Image to Mesh and Drawing to Parametric Model. These have been listed as upcoming, so confirm availability in your release.


Using natural-language prompts well


Good prompting for LEO looks a lot like writing a clear instruction to a capable junior engineer. Vague in, vague out. Illustrative examples (adapt to your own models):

  • Modelling guidance: “Why is this sketch over-defined, and what is the minimum change to fix it?”
  • Performance: “Which components are slowing this assembly down, and what can you do about it without changing the design?”
  • Impact: “If I increase this shaft diameter, which parts and subassemblies are affected?”
  • Automation: “Write a macro that exports every part in this assembly to STEP with the custom property ‘Part Number’ as the file name.”
  • Documentation: “Create a manufacturing drawing for this part with front, top and section views and overall dimensions.”

The pattern that works: state the goal, give constraints, and say what must not change.


How LEO changes the engineer’s workflow

The biggest change is not speed on any single task. It is where your attention goes.


  • Less hunting, more deciding. Tracing a rebuild error or finding a performance bottleneck becomes a conversation instead of a trial-and-error loop.
  • Earlier awareness of consequences. Change impact analysis surfaces dependency problems before you commit, which is when they are cheapest to fix.
  • Lower barrier to automation. Engineers who never wrote VBA can now describe a macro and iterate on it, while experienced programmers get a faster first draft.
  • Documentation stops being a bottleneck. Drawings and assembly instructions start as drafts you review rather than blank sheets you build.

For SOLIDWORKS CAD users working on large assemblies, the performance and impact-analysis skills are often the quickest to show value, because the time savings are easy to measure.


Where LEO fits with simulation and validation


LEO’s roadmap includes simulation-oriented capability such as impact analysis, but it supports engineering analysis rather than replacing it. Treat LEO’s outputs as prompts for investigation. Structural, thermal and motion questions should still be settled with proper analysis in SOLIDWORKS Simulation, with assumptions you can defend in a design review.


What managers and CAD administrators should plan for


  1. Access and licensing. SOLIDWORKS states that commercial SOLIDWORKS Design Offer and Design with Cloud Services customers get access to AURA and LEO without an additional licence. Cloud Services activation and a 3DEXPERIENCE connection are required.
  2. Beta status. Some features have carried beta labels and enrolment requirements. Pilot before standardising.
  3. Review gates. Define who checks AI-generated drawings, macros and converted models before release.
  4. Data governance. Keep AI-assisted work inside your managed environment on the 3DEXPERIENCE platform.
  5. Skills. Train teams to prompt precisely and to critique outputs.

Limits worth stating plainly


LEO does not know your tolerances, supplier constraints or the history behind a design decision unless that information is in the model or the prompt. It can generate a macro that runs but does the wrong thing, or a drawing that is complete but dimensioned for the wrong manufacturing method. The accountability for the design stays with the engineer.


FAQ


Is SOLIDWORKS LEO the same as a general chatbot? No. LEO is built around SOLIDWORKS skills and acts on the model open in your session.


Can LEO write macros for me? Yes, it can generate macro logic from a natural-language description that you then refine. Test it on a copy of your data first.


Do I need the cloud to use LEO? The virtual companions require a connection to the 3DEXPERIENCE platform, so Cloud Services need to be active.