CAD customization for Creo, SolidWorks and BricsCAD

Modelcam builds CAD customization and design automation for PTC Creo, SOLIDWORKS and BricsCAD: add-ins and macros that remove repeat clicks, rule-based models that configure themselves, automated drawings and BOMs, and AI checks trained on your own standards. Current to Creo 13, SOLIDWORKS 2026 and BricsCAD V26.

CAD
PTC Creo, SOLIDWORKS, BricsCAD
What we build
Add-ins, macros, rules, drawings
AI
Checks and assistants on your standards
Delivery
India, the US and remote worldwide
Design automation runSample · illustrative

Inputs from sales: pump base, motor frame 180M, coupling guard, mild steel, 6 mm plate

  • 3D model rebuilt from rulesCreo, SOLIDWORKS or BricsCADDone
  • Drawings and title blocks updatedCompany template, all sheetsDone
  • BOM, cut list and cost sheetExported for ERP and purchaseDone
  • Standards checkTwo notes for the designerReview
Designer approvesReleased to Windchill or PDM
Illustrative, no client data shown.

What is CAD customization, and how is it different from design automation?

CAD customization changes how your CAD system works for your company: templates, commands, menus and add-ins that remove repeat work. Design automation goes further: a model, its drawings and its BOM build themselves from rules and a few inputs. AI now adds checking and drafting on top of both.

CAD customization compared with design automation and AI-assisted CAD
CAD customizationDesign automationAI-assisted CAD
What it doesShortens everyday tasksBuilds a model, drawings and BOM from inputsChecks, explains and drafts, for a designer to approve
ExamplesTemplates, custom commands, batch export, title block fillConfigure-to-order products, sized parts, quote drawingsDrawing checks against your standards, macros from plain language
Built withMacros, LISP, mapkeys, add-insRules, parameters, relations, API programsLanguage models, your rules and part libraries
Typical gainMinutes saved per taskHours saved per orderErrors caught before release
Creo 13 and Creo+ 13.3 · June 2026

Creo customization and automation

We build Creo add-ins with Creo TOOLKIT and Creo Object TOOLKIT, rule-based models with relations, Pro/PROGRAM and family tables, and drawing automation that fills formats, BOM tables and title blocks. We also port old Toolkit and J-Link applications to Creo 12 and 13.

  • Creo TOOLKIT (C)
  • Object TOOLKIT C++
  • Object TOOLKIT Java and J-Link
  • Relations and Pro/PROGRAM
  • Family tables
  • Mapkeys
  • Windchill Workgroup integration
  • Configure-to-order models: inputs in, model and drawings out
  • Drawing automation: formats, views, BOM balloons, title blocks
  • Windchill-aware tools: attributes, workspaces and check-in handled for the designer
  • Porting of legacy Toolkit and J-Link apps to Creo 12 and 13, then upkeep at each release
  • Modelcam Creo Bridge: AI for Creo 10 and above, in pilot
SOLIDWORKS 2026 · 2027 launches November 2026

SOLIDWORKS automation

We automate SOLIDWORKS with API add-ins in C# and VB.NET, VBA macros, the Document Manager API for batch work without opening SOLIDWORKS, and SOLIDWORKS PDM add-ins and workflows. Configurations and design tables become rule-driven product configurators.

  • SOLIDWORKS API (C#, VB.NET)
  • VBA macros
  • Document Manager API
  • PDM Professional API
  • Design tables and configurations
  • Custom properties
  • Product configurators for sized and configure-to-order parts
  • Batch jobs: PDF, DXF and STEP export, renaming, property clean-up
  • Drawing and BOM automation with your templates and numbering
  • PDM workflows and data cards, and handoff to Windchill or ERP
  • Natural-language macros, reviewed and hardened for production use
BricsCAD V26 · V26.2 March 2026

BricsCAD customization and automation

We customize BricsCAD with LISP, BRX (C++) and .NET, and move AutoCAD routines across. Most AutoCAD LISP runs unchanged; calls to AutoCAD's application object, compiled ObjectARX files and .NET Framework add-ins need work, because BricsCAD V26 moved its .NET API to .NET 8.

  • LISP and Visual LISP
  • BRX (ObjectARX-compatible C++)
  • .NET 8 API
  • Parametric blocks
  • BricsCAD Mechanical BOMs
  • DCL dialogs
  • AutoCAD LISP and .NET tools moved to BricsCAD and tested
  • .NET Framework add-ins migrated to .NET 8 for V26
  • Parametric blocks and drawing standards for your products
  • BricsCAD Mechanical BOMs exported to ERP
  • Licences too: we are an authorised BricsCAD reseller

What can you automate in CAD?

Anything your designers repeat with the same rules. These eight are where manufacturers usually start.

Sales to designConfigure-to-order modelsSizes and options from a quote become a model, drawings and BOM.
DocumentationDrawing automationViews, dimensions, balloons, title blocks and revision tables filled the same way every time.
ManufacturingBOM, cut lists and costingExported in the format your ERP and purchase team need.
QualityStandards and DFM checksDrafting standards, hole sizes, materials and tolerances checked before release.
DataBatch jobsExport, rename, convert and clean up properties across thousands of files.
PLMPLM and PDM handoffsAttributes, numbering and check-in to Windchill or PDM without manual steps.
CalculationEngineering calculatorsSizing and load calculations linked to model parameters.
AIDrawing review with AITitle block, BOM and note checks against your own standards, flagged for a designer.

Where does AI fit in CAD automation in 2026?

CAD vendors now ship general assistants: the Creo AI Assistant in Creo 13, AI companions and natural-language macros in SOLIDWORKS 2027, and BricsCAD Assist for help. They know the software, not your company. The value is in your rules, standards and part libraries, and that is the part we automate.

Every AI step ends with a designer's approval, and nothing is released without it. For AI across engineering data, see AI for manufacturing.

  • Drawing checks trained on your drafting standards
  • Plain-language requests turned into tested automation scripts
  • Agents that call CAD and Windchill functions, with approval at each step
  • BOM and title block extraction from legacy PDF drawings

How does a CAD customization project run?

Start with one repetitive task or one product family. We capture the rules, prove them on your real parts, then build, deploy and keep the tool working through every CAD upgrade.

  1. Capture the rules

    A workshop with your designers on one task or product family, and the inputs it needs.

  2. Prove on real parts

    A working prototype on your own models and drawings, before the full build.

  3. Build and test

    The tool built, tested by your designers, and documented.

  4. Deploy and maintain

    Installed, trained, and ported at each new CAD release.

Questions about CAD customization

Updated

What is CAD customization?

CAD customization means adapting CAD software to how your company designs: templates, custom commands, macros and add-ins that remove repeat work and apply your standards automatically.

What is the difference between CAD customization and design automation?

Customization speeds up tasks a designer still does by hand. Design automation builds the model, drawings and BOM from rules and a few inputs, so a configure-to-order product can be drawn in minutes.

Can you customize Creo 13?

Yes. We build Creo add-ins with Creo TOOLKIT and Creo Object TOOLKIT, plus relations, Pro/PROGRAM, family tables and mapkeys, for Creo 13, Creo 12 and earlier releases.

Will our old Creo Toolkit or J-Link programs work in Creo 13?

Often they need recompiling and some code changes. We test each program on the new release, port what breaks, and can maintain it at every future release.

Can SOLIDWORKS files be processed without opening SOLIDWORKS?

Yes, for many jobs. The SOLIDWORKS Document Manager API reads and updates file properties, references and configurations in batch without starting SOLIDWORKS.

Do AutoCAD LISP routines work in BricsCAD?

Most run unchanged. Routines that call AutoCAD's application object or depend on AutoCAD-only features need small changes, and compiled ObjectARX files must be rebuilt with BRX.

Will our .NET add-in work in BricsCAD V26?

BricsCAD V26 moved its .NET API to .NET 8, so add-ins built on .NET Framework usually need migration. We migrate and test them.

How much does CAD customization cost?

We price after a short workshop on one task or product family, usually as a fixed price per module. Send us one repetitive task and we will tell you what it takes.

Does AI replace CAD customization?

No. Vendor AI assistants know the software, not your rules. Company-specific automation still needs your standards, part libraries and logic, and AI works best on top of it.

Do you also work with AutoCAD?

Yes. We customize AutoCAD with LISP and .NET, often as part of moving a team to BricsCAD.

Send us one repetitive design task.

We will show you how much of it can be automated, and what it would cost.

Send a task

or email ai@modelcamtechnologies.com