EngineeringMechanical EngineeringPlatform
SOLIDWORKS Workstation Specification & Hardware Certification
A workstation that benchmarks well can still perform poorly in parametric modelling. The workload rewards clock speed over core count, is memory-bound before it is processor-bound, and depends on a graphics path that vendors certify explicitly. Specifying against the wrong characteristic is the most expensive procurement error in engineering.
- Group · Platform
- Series · Administration
- Baseline · SOLIDWORKS 2026
- Reading · 16 min
01 Why CAD Specification Is Not General IT Procurement
A workstation that scores well on a general benchmark can perform poorly in parametric modelling. The workload has an unusual shape, and specifying against the wrong characteristic is the most common and most expensive procurement error in engineering.
Three properties distinguish CAD from the office and server workloads that most hardware policy is written around. Parametric rebuild is largely sequential, so it rewards clock speed rather than core count. Display rendering runs through a graphics path that vendors certify explicitly, so raw graphics capability without certification produces instability rather than speed. And assembly work is memory-bound long before it is processor-bound, so memory capacity sets the practical ceiling on what an engineer can open at all.
Specifying against a standard corporate desktop image, or against a gaming-oriented specification with an impressive headline, both fail — for opposite reasons. The first under-provisions memory and graphics; the second provides ample capability through an uncertified path.
Figures here reflect the SOLIDWORKS 2026 release family. Minimum requirements, supported operating systems and certified hardware lists are revised with each annual release and periodically within a release. Verify against the vendor's current published system requirements and hardware certification listing before raising a purchase order.
02 Processor Selection
The single most misunderstood component. More cores is the intuitive answer and, for the dominant workload, the wrong one.
Why single-thread performance dominates
Features in a design tree are evaluated in order: each depends on the geometry produced by those before it. This dependency chain cannot be parallelised in the general case, so rebuild time is governed by how fast one core can execute the sequence. Instructions per clock and sustained frequency under load are therefore the properties that determine perceived responsiveness — opening a part, editing a feature, waiting for a rebuild after a dimension change.
A processor with many cores at a modest base frequency will feel slower in this work than one with fewer, faster cores. The practical selection rule is to choose the highest sustained single-core frequency available within the thermal envelope, and treat core count as a secondary consideration.
Where cores genuinely matter
- Simulation solvers. Structural, thermal and flow analyses parallelise well and scale with core count and memory bandwidth. A team doing regular analysis justifies a different specification from one doing pure design.
- Rendering. CPU-based rendering scales close to linearly; GPU-accelerated rendering shifts the requirement to graphics memory instead.
- Background operations. Import processing, drawing view generation and some file operations run off the main thread, so additional cores prevent these from blocking interactive work.
- Concurrent applications. Engineers routinely hold a modelling session, a spreadsheet, a PDF and a vault client open simultaneously. Headroom matters even when the CAD workload itself is sequential.
Specify for the highest sustained single-core frequency in the class, then take as many cores as come with it without sacrificing that frequency. For a design-only role this typically lands on a mid-range part rather than a top-tier many-core processor — and the money saved is better spent on memory and graphics.
03 Memory Sizing
Memory is the constraint that converts from "slow" to "impossible". An assembly that exceeds available memory does not degrade gracefully; it pages to disk and becomes unusable.
Published minimums for the 2026 release family sit at 16 GB. That figure permits installation and supports part-level work, but it is not a working specification for assembly design. Memory consumption is driven by the number of loaded components, the complexity of each, the number of open documents, and whether drawings and simulation results are resident at the same time.
| Working scale | Memory | Notes |
|---|---|---|
| Parts and small assemblies | 16 GB | Viable for component design and detailing. Leaves little headroom for concurrent applications. |
| Assemblies to a few thousand components | 32 GB | The realistic default for production design work. Accommodates drawings and a vault client alongside the model. |
| Large assemblies, routine simulation | 64 GB | Required once analysis results are held in memory alongside the model, or where very large assemblies are opened resolved. |
| Very large assemblies, large-scale analysis | 128 GB+ | Specialist. Verify against actual models rather than component counts, which correlate poorly with memory demand. |
Techniques that reduce demand
Specification is not the only lever. Lightweight and large-design-review modes load a reduced representation of components; selective loading brings in only the subassemblies being worked on; configurations with suppressed detail reduce the resident geometry. These are design-practice controls rather than procurement controls, but a team using them well operates comfortably one tier below a team that opens everything fully resolved.
Two assemblies with the same component count can differ by an order of magnitude in memory demand, depending on feature complexity, imported geometry, surfacing and the depth of the reference tree. Size from measured consumption on your own representative models, not from a supplier's component-count table.
04 Graphics & Hardware Certification
This is the area where the correct answer is least intuitive and the consequences of getting it wrong are most often misdiagnosed as software faults.
Certification, not capability
SOLIDWORKS renders through OpenGL and depends on driver behaviour that hardware vendors validate specifically for the application. Consumer gaming cards have ample raw capability, and often exceed professional cards on general graphics benchmarks — but they are not supplied with the certified professional drivers the application expects. The observable consequences are advanced display modes unavailable, visual artefacts in shaded views, and instability that appears under large assemblies and is difficult to reproduce on demand.
The correct procedure has two parts, and both matter:
- Select a card that appears on the published hardware certification listing for your release and workstation platform.
- Install the specific driver version certified for that combination — not simply the newest driver the vendor offers.
A fleet-wide Windows driver update policy will silently move every workstation off its certified driver version. The symptom appears weeks later as unexplained graphical faults across multiple machines simultaneously, with no software change to correlate against. Exclude CAD workstation graphics drivers from automatic update policy and manage them as a deliberate, tested change.
Sizing graphics memory
For modelling, graphics memory requirements scale with the amount of visible geometry and display resolution rather than with raw component count. Entry professional cards are adequate for parts and modest assemblies; mid-range cards suit production assembly work and high-resolution or multi-monitor setups; high-memory cards become necessary only for photorealistic rendering, very large visible geometry, or virtual-reality review.
Entry professional
Parts, small assemblies, drawing production. Adequate for the majority of detailing roles.
Watch for: under-provisioning where the same seat later moves to assembly work.
Mid-range professional
Production assembly design, high-resolution and multi-monitor use. The mainstream choice.
Watch for: driver version drift — the specification is only as good as the driver on it.
High-memory professional
Photorealistic rendering, very large visible geometry, immersive review.
Watch for: specifying this tier for modelling roles where it delivers no benefit.
05 Storage & Displays
Storage
Solid-state storage is a requirement rather than an upgrade. Open, save and vault check-in operations are dominated by many small random reads and writes, which is precisely the access pattern where mechanical drives fail worst. Specify NVMe where the platform supports it.
- Retain free capacity. Published guidance calls for meaningful free space to be preserved; solid-state performance degrades as drives approach capacity, and temporary files during large operations can be substantial.
- Separate the local vault cache where practical. On a second volume, cache traffic does not compete with the operating system and application.
- Do not treat the local cache as storage. It is a working copy. Capacity planning should assume it can be cleared and repopulated.
Displays
Two displays is the practical minimum for drawing production — model on one, drawing or reference on the other. High-resolution displays are well supported but interact with Windows display scaling; verify that the application and any add-ins render correctly at the intended scaling factor before standardising on a display, as mixed-DPI multi-monitor configurations remain the most common source of interface rendering complaints.
06 Specification Tiers
A starting framework to be validated against your own models, not a substitute for that validation.
| Tier | Role | Processor | Memory | Graphics | Storage |
|---|---|---|---|---|---|
| Detailer | Parts, drawings, small assemblies | High-frequency mid-range | 16–32 GB | Entry certified | NVMe, 512 GB |
| Designer | Production assembly design | High-frequency mid-range | 32–64 GB | Mid-range certified | NVMe, 1 TB |
| Analyst | Regular simulation alongside design | Higher core count, sustained frequency | 64–128 GB | Mid-range certified | NVMe, 1 TB + scratch volume |
| Visualiser | Rendering and animation | Higher core count | 64 GB+ | High-memory certified | NVMe, 1 TB+ |
Before committing to a fleet purchase, run your own representative models on a single evaluation unit: a large assembly open and rotate, a full rebuild on a complex part, a drawing view regeneration, and a vault check-in of a sizeable assembly. Record the times. This takes an afternoon and reliably exposes specifications that look correct on paper and disappoint in use.
07 Common Specification Errors
| Error | How it presents | Correction |
|---|---|---|
| Consumer graphics card | Artefacts, missing display modes, intermittent crashes under large assemblies | Replace with a certified card; verify driver version against the certification listing |
| Many cores, low frequency | Rebuilds feel sluggish despite a strong specification on paper | Prioritise sustained single-core frequency for design roles |
| Under-provisioned memory | Large assemblies will not open, or open and thrash | Size from measured consumption on representative models |
| Mechanical or shared storage | Slow open, save and check-in; poor perceived responsiveness across all work | Local NVMe with retained free capacity |
| Standard corporate desktop image | Systematically under-specified graphics and memory across the whole team | Establish a separate engineering workstation standard with its own refresh cycle |
| Driver managed by general IT policy | Simultaneous unexplained faults across multiple machines after an update window | Exclude CAD graphics drivers from automatic update; manage as a tested change |
08 Procurement Checklist
- Certification verified. The proposed card and driver version both appear on the current certification listing for the release in service and the workstation platform.
- Frequency prioritised. Processor selected for sustained single-core frequency where the role is design rather than analysis.
- Memory measured. Sizing derived from observed consumption on representative models, not from component-count tables.
- Storage local and solid-state. NVMe where supported, with free capacity retained and no reliance on network storage for working files.
- Benchmarked. A single evaluation unit has run your own models with results recorded before the fleet order.
- Driver policy agreed. CAD graphics drivers excluded from automatic update, with a named owner for tested driver changes.
- Refresh cycle defined. Engineering workstations have their own standard and replacement cycle, separate from the general desktop estate.
- Roles mapped to tiers. Each seat is assigned a tier deliberately, and reassignment is triggered when a role changes.
09 Frequently Asked Questions
Our engineers say a gaming card would be faster and cheaper. Are they wrong?
On raw capability, often not — consumer cards frequently outperform professional cards of similar price on general graphics measures. The issue is not speed. It is that the vendor validates specific driver builds against the application, and those certified drivers are supplied only with the professional line.
The practical outcome of an uncertified card is not slower work; it is missing display features and intermittent instability under large assemblies that is difficult to reproduce and easy to misattribute to the software. The cost of investigating those faults typically exceeds the hardware saving within one incident.
Is it worth specifying a top-tier processor?
For design roles, generally not. Top-tier parts usually trade sustained frequency for core count, which is the wrong direction for sequential rebuild. The money is better allocated to memory and a properly certified graphics card.
For roles running regular simulation or CPU rendering, the calculation reverses — those workloads scale with cores. This is a strong argument for specifying by role rather than issuing one standard machine to everyone.
Can engineers work effectively on laptops?
Yes, within limits. Mobile workstations with certified professional graphics are well established. The constraints are sustained frequency under thermal load, upper memory limits, and display size for drawing work.
The workable pattern is a mobile workstation with a docking station driving external displays, specified one tier above what the equivalent desktop would need, to allow for thermal throttling. Standard business laptops with integrated graphics are not a viable platform for assembly work.
How often should engineering workstations be replaced?
The useful trigger is not age but capability against current work. Two signals matter: models that no longer open comfortably within available memory, and a graphics card that has dropped off the certification listing for the release you intend to adopt.
The second is the one that catches organisations out, because it converts a software upgrade into an unplanned hardware programme. Check the certification listing for the next release against your installed fleet each year, ahead of upgrade planning.
Series context. This page is part of the KEVOS® SOLIDWORKS environment administration series. It presents general administration practice and is written to be release-independent wherever possible. Where specific versions, limits or supported platforms are cited, they reflect the SOLIDWORKS 2026 release family and should be verified against current vendor documentation before being relied upon for procurement, platform or upgrade decisions.
SOLIDWORKS is a registered trademark of Dassault Systèmes SolidWorks Corporation. Product names are used here for identification and reference only. KEVOS® is independent and is not affiliated with, endorsed by, or a reseller for Dassault Systèmes.