Spur gear family, generated from Excel
A single parametric gear model, driven from an Excel sheet of tooth count, module and bore, produced an entire catalog of configurations — parts, drawings and STEP files — in one generation run.
Representative engagements
The examples below illustrate the kind of configuration and automation work typical of Auto-Configure engagements. They are representative scenarios rather than measured client results.
A single parametric gear model, driven from an Excel sheet of tooth count, module and bore, produced an entire catalog of configurations — parts, drawings and STEP files — in one generation run.
A legacy fastener library with inconsistent naming and annotation was passed through the Standardizer to unify custom properties, colours and drawing formatting across hundreds of parts.
A hydraulic manifold block family was built using Design Tools for Manifold, with component libraries shared across two design offices and colour-coded networks for design review.
An AI agent reads a released model's revision history and drafts the routine sections of an engineering change order, leaving the engineer to review, adjust and approve before release.
A design team adopted CADPilot to create routine sketches and features by voice in their own language, cutting the clicks between knowing what to build and the model reflecting it.
A multi-thousand-part model library was relocated to a new server using ProcessWorks, with every assembly's references mapped and verified, and standard custom properties applied to the entire copied set.
Illustrative scenarios based on common Auto-Configure use cases. Documented outcomes from comparable projects are shared on request.
Tell us about it and we'll outline the right approach.