What is a CAD system? — Definition and features
In short: A CAD system is software for digital design that manages parametric geometries, component libraries, and drawing derivations. Modelling functions are the core — but the real driver of success in the mid-market is how data flows into downstream systems.
A CAD system (Computer-Aided Design) is specialised software for creating and managing 3D models, technical drawings, and design documentation. For managing directors in mid-market companies, the right CAD choice means: precise control of design data and a robust bridge between engineering, procurement, and production.
The typical architecture includes parametric modelling (changes to a base dimension automatically update dependent geometries), assembly management (joining individual parts into complex assemblies), drawing derivation (automatic generation of 2D plans from 3D models), and component libraries (reusable standard parts such as screws, profiles, bearings).
In the DACH mid-market, solutions like SolidWorks, Autodesk Inventor, Siemens Solid Edge, and NX dominate — depending on industry and complexity. These systems serve as the source of truth for geometric and design data. Their connection to downstream systems (ERP, PDM, manufacturing) is strategically decisive — and rarely solved well in practice.
Why CAD systems matter now for DACH SMEs
In short: Regulatory requirements (MDR 2017/745, EU AI Act 2026) and the pressure for supply-chain transparency make CAD-system selection a strategic decision — no longer a pure engineering task.
For a long time, CAD selection was the responsibility of the engineering department. That is no longer correct. According to VDMA, the CAD landscape has shifted fundamentally. Supply-chain digitalisation demands that CAD data flow seamlessly into PDM (Product Data Management), ERP bill-of-materials modules, and — in the medical-device context — regulatory audit trails.
Three drivers make this critical in 2026. First, regulatory compliance. Medical-device manufacturers must demonstrate audit trails for every design change under MDR 2017/745. CAD systems without integrated version control and access logs create compliance gaps. Second, the EU AI Act 2026 and generative design. Generative-design tools use AI to optimise geometries — and depending on the deployment context (medical devices, safety-critical automotive parts) can fall under high-risk AI categories. Companies introducing such tools must build governance frameworks. Third, supply-chain transparency. Procurement departments demand real-time data on material availability; CAD systems must transmit BOM data to ERP procurement modules in real time.
According to the Bitkom study "Digitalisierung der Wirtschaft 2025", 76% of digitally advanced mid-market companies achieve measurable efficiency gains — but only when design and business data are consistently linked. In our projects we see the same finding: many companies run CAD and ERP in isolation and manage BOM data redundantly — manually in ERP and digitally in CAD. That is exactly where the expensive errors happen.
Practical example: CAD-ERP integration at a southern German engineering firm
In short: An engineering firm with 280 employees in Bavaria introduced bidirectional CAD-ERP synchronisation and reduced BOM error rates from around 18% to under 2%.
In our experience, the following scenario is typical in DACH mid-market companies. An engineering firm with 280 employees in Bavaria ran SolidWorks for design and SAP for production. Both systems operated in isolation: design engineers built assemblies in SolidWorks; an internal-services clerk transferred the BOM data manually into SAP. The error rate was 15–20% per design cycle — swapped part IDs, missing assemblies, inconsistent quantities.
After introducing an API-based synchronisation between SolidWorks and SAP (via web services), BOM changes flowed automatically — with change tracking and version control. Result: error rate under 2%; throughput time for BOM updates from 3 days to 4 hours. The central lesson: CAD system and ERP are not separate worlds. The error-rate reduction paid for itself through savings on manual data entry and fewer production disruptions.
How we approach CAD selection and ERP integration methodically
In short: CAD selection is not a feature comparison. It is an integration audit — strategy before software.
From our practice across more than 1,200 projects we follow four steps. First, process map: we chart which design, planning, and production processes actually run today — not those on the org chart. Second, integration assessment: we examine how CAD data is connected today to ERP, production, and quality-management systems, and where the breaks are. Third, regulatory fit: for medical devices and pharma we audit audit-trail and version-control requirements. Fourth, vendor evaluation: only then do we compare solutions against real, documented requirements — not against vendor demos.
For companies renewing their CAD system or building a CAD-ERP integration, we apply our own maturity model SCOReX®. A short audit shows whether CAD is operated in isolation today (maturity level 1) or whether CAD data flows structurally into ERP (maturity level 3+) — and which organisational changes are needed before the technology rollout.
Common mistakes in CAD rollouts
In short: The four most common mistakes follow one pattern: technology first instead of process first.
Mistake 1: "We buy the best CAD system and the rest sorts itself out." Vendor selection by feature comparison produces system islands. An engineering firm with 150 employees bought Siemens Solid Edge without first redocumenting procurement, planning, and production. Eighteen months later, design engineers used only 15% of the features; the BOM integration to SAP did not exist. Investment: €250,000. Value created: marginal.
Mistake 2: Ignoring audit-trail and compliance requirements. A medical-device company with 80 employees introduced standard SolidWorks with file-system version control. In the MDR audit 18 months later: no consistent access logs, no attribution of changes to specific individuals, no compliance reports. The correction — introducing a full CAD-PDM system — was substantially more expensive than the right choice at the start would have been.
Mistake 3: Generative design without governance. An automotive supplier introduced Autodesk Fusion with Generative Design to save costs. Six months in, internal audits revealed: geometries were generated, but material validation and manufacturability checks remained unclear. Customers — quite rightly — asked how the part had been designed. The answer "An AI optimised it" was not acceptable.
Mistake 4: CAD team isolated from ERP team. Engineering firm, 200 employees: the CAD implementation ran out of the design department; the ERP team was not involved. After go-live, conflicts emerged — CAD nomenclature did not align with ERP master data. Retroactive data harmonisation cost 40 working days — avoidable, if both teams had sat at the same table from day one.
Next steps
CAD selection is a strategic decision that reflects your integration, regulatory, and supply-chain requirements — not just a software comparison. If your company is considering a CAD refresh or a CAD-ERP integration, our recommendation is clear: start with an integration audit, not a vendor demo. The audit shows where data flows today, where islands exist, and which organisational changes are needed before the technology rollout. We accompany DACH SMEs through exactly these audits and implementations — more than 1,200 projects show that this structured approach saves both time and errors.
