Home/DriveWorks guides/DriveWorks vs SOLIDWORKS equations: when to switch
DriveWorks vs SOLIDWORKS equations: when to switch
Move from SOLIDWORKS equations to DriveWorks when the "smart" model starts to slow down or becomes hard to debug. If you plan to keep evolving a configured product, the right time was yesterday. DriveWorksXpress is already included in SOLIDWORKS, so the first step costs nothing.
The story everyone tells
Talk to DriveWorks users and the conversation follows the same storyline. First: "We used SOLIDWORKS and piled equation after equation into the model to make it smart." Then: "The smart model became unwieldy, slow, and difficult to debug."
In most cases SOLIDWORKS was never intended to be used that way. Equations, configurations, and design tables are good at relating a handful of dimensions inside one part. They struggle when the logic is really product knowledge: which options are allowed together, which parts get swapped, what the drawing should show, what it costs.
Signs you have outgrown equations
- Rebuilds are slow, and opening the top-level assembly is something people plan around.
- Nobody wants to touch the logic. It is spread across equations, configurations, and design tables in many files, and one person understands it.
- Debugging means opening models and hunting, because there is no single place where the rules live.
- The logic stops at the model. Price, quote text, the bill of materials, and the order in the ERP are all still done by hand, from the same answers.
That last point is the real reason to switch. The questions you ask to drive a model are the same questions needed to configure, price, and quote the product. Rules in DriveWorks can serve all of them. Equations in a part file cannot.
The upgrade path
| Step | What it adds | Cost of trying |
|---|---|---|
| DriveWorksXpress | Rules drive dimensions, features, and custom properties from a form; a drawing for each part and assembly | Included free in every seat of SOLIDWORKS |
| DriveWorks Solo | The full form designer with dynamic validation, tabular data in rules, multiple drawings, quote and BOM documents, on-demand preview | Free trial available from DriveWorks |
| DriveWorks Pro | Shared groups with users and teams, SQL Server, browser access (Live), unattended generation (Autopilot), SOLIDWORKS macros, web services and API integration | Licensed by module |
Source: the DriveWorks feature comparison. A project built in DriveWorksXpress can be migrated up to Solo or Pro, so nothing learned at the first step is wasted.
Xpress is the place to prove the idea and to show others what design automation looks like. Solo shows how far one engineer can push it. Pro is where the work becomes shared: other people can use what was built, sales can configure in a browser, and the output can flow into other systems. For a configure, price, quote tool, Pro is the natural destination.
"We don't have time to automate right now"
This is the most common objection, and it is backwards. You do not have time not to. As the business grows, the product range expands, and people are added, the non-value-added work grows with them. Driving it down is not only good for business. It is how a growing company keeps its culture and its speed.
The sooner the mundane work is automated, the sooner the investment pays back. Whether you are getting your feet wet with DriveWorksXpress or ready for DriveWorks Pro, Base 10 can help you start, and the guide on choosing a first project is the next thing to read.
Common questions
When should we move from SOLIDWORKS equations to DriveWorks?
When the model starts to slow down or becomes hard to debug. If you plan to keep evolving a configured product, start sooner: the earlier repetitive work is automated, the earlier it pays back.
Is DriveWorksXpress really free?
Yes. DriveWorksXpress is entry-level design automation included in every seat of SOLIDWORKS. It is activated from inside SOLIDWORKS and is enough to drive one model from a form and rules.
What is the difference between DriveWorks Solo and DriveWorks Pro?
DriveWorks Solo is design automation for a single engineer working inside SOLIDWORKS. DriveWorks Pro adds shared groups with users and teams, SQL Server support, browser access through DriveWorks Live, unattended generation with Autopilot, and integration with other systems through databases, web services, and an API.
Can we keep our existing SOLIDWORKS models?
Often yes, but models built for manual editing usually need restructuring to be driven well. Bottom-up part architecture, consistent custom properties, and fewer in-model equations make a model much easier to automate.
Do DriveWorksXpress projects carry over to Solo or Pro?
Yes. DriveWorks states that a project created in DriveWorksXpress can be migrated to DriveWorks Solo or DriveWorks Pro.
Related
Base 10 Consultants is a DriveWorks Authorized Services Partner: CPQ configurators, design automation, and CAD-to-ERP integration for manufacturers.
Book a 30-minute callBase 10 Consultants is a DriveWorks Authorized Services Partner and an independent company. This page is not written, reviewed, or endorsed by DriveWorks Ltd. DriveWorks is a trademark of DriveWorks Ltd; SOLIDWORKS is a trademark of Dassault Systèmes SolidWorks Corp. Behavior described here can differ between versions, so check the DriveWorks documentation for the version you run.