AI-Powered Generative Design System for Mechanical Parts

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI-Powered Generative Design System for Mechanical Parts
Complex
from 2 weeks to 3 months
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

A client receives a CAD file of a part, but the design is over-engineered: safety factor of 3 when 1.5 is required. Long manual optimization begins—iterations, recalculations, new prototypes. A month of engineer work, and mass reduced by only 10%. We offer a different approach: AI finds the optimal shape in hours, not weeks. Topology optimization can reduce mass by 30-40% without losing strength (SIMP, classic method).

Example: for an aircraft bracket weighing 2.3 kg with safety factor 3, we reduced mass to 1.4 kg without strength loss. Manual optimization would take 3 weeks, AI did it in 6 hours. Material savings — 0.9 kg, which at aluminum price of $2.5/kg saves $2.25 per part, and for a series of 10,000 parts — $22,500. Design time reduced by 10x, making AI generative design 10 times faster than traditional manual optimization.

We develop a generative design system that analyzes loads and boundary conditions, then generates a structure with minimal possible weight under given strength requirements. Stack — Python, PyTorch, Scipy, OpenCASCADE. Applying machine learning in engineering (ML for CAD) automates routine tasks. Result — up to 40% material savings and 5-10x acceleration of the design cycle.

How Generative Design Works: From SIMP to VAE

Topology Optimization with SIMP (Time-Efficient)

The classic method is SIMP (Solid Isotropic Material with Penalization). The algorithm iteratively distributes material in a discrete grid, aiming to minimize compliance under a given volume. Suitable for problems with clear loads: brackets, frames, supports.

import numpy as np
from scipy.sparse import lil_matrix
from scipy.sparse.linalg import spsolve

class TopologyOptimizer:
    def __init__(self, nelx=60, nely=30, volfrac=0.5, penal=3.0, rmin=1.5):
        self.nelx = nelx
        self.nely = nely
        self.volfrac = volfrac
        self.penal = penal
        self.rmin = rmin

    def optimize(self, load_case, boundary_conditions, max_iterations=100):
        x = np.full((self.nely, self.nelx), self.volfrac)
        xold = x.copy()
        for iteration in range(max_iterations):
            U = self._finite_element_analysis(x, load_case, boundary_conditions)
            dc = self._sensitivity_analysis(x, U)
            dc = self._filter_sensitivity(x, dc)
            x = self._oc_update(x, dc)
            change = np.max(np.abs(x - xold))
            xold = x.copy()
            if change < 0.01:
                break
        return x
    # ... methods omitted for brevity

Why SIMP Isn't Suitable for Complex Parts?

SIMP is sensitive to initial conditions and can get stuck in local minima. For problems with multiple loads or nonlinear constraints, neural network methods are better — they generate diverse options from which the engineer selects the best.

How VAE Generates New Designs?

We use a variational autoencoder (VAE), trained on a dataset of 2,000 optimized designs. Input is a vector of physical conditions (loads, boundaries), output is a new shape with desired properties. This yields hundreds of options in seconds. Variational autoencoders were proposed by Kingma and Welling (Auto-Encoding Variational Bayes).

import torch
import torch.nn as nn

class DesignGeneratorVAE(nn.Module):
    def __init__(self, latent_dim=64, design_resolution=64):
        super().__init__()
        self.latent_dim = latent_dim
        res = design_resolution
        self.encoder = nn.Sequential(
            nn.Conv2d(1, 32, 4, stride=2, padding=1),
            nn.ReLU(),
            nn.Conv2d(32, 64, 4, stride=2, padding=1),
            nn.ReLU(),
            nn.Conv2d(64, 128, 4, stride=2, padding=1),
            nn.ReLU(),
            nn.Flatten()
        )
        encoder_out_size = 128 * (res // 8) ** 2
        self.fc_mu = nn.Linear(encoder_out_size, latent_dim)
        self.fc_logvar = nn.Linear(encoder_out_size, latent_dim)
        self.condition_proj = nn.Linear(16, latent_dim)
        self.decoder_input = nn.Linear(latent_dim * 2, 128 * (res // 8) ** 2)
        self.decoder = nn.Sequential(
            nn.ConvTranspose2d(128, 64, 4, stride=2, padding=1),
            nn.ReLU(),
            nn.ConvTranspose2d(64, 32, 4, stride=2, padding=1),
            nn.ReLU(),
            nn.ConvTranspose2d(32, 1, 4, stride=2, padding=1),
            nn.Sigmoid()
        )
        self.res = res

    def generate(self, conditions, n_samples=1):
        with torch.no_grad():
            z = torch.randn(n_samples, self.latent_dim)
            c = self.condition_proj(conditions.expand(n_samples, -1))
            zc = torch.cat([z, c], dim=1)
            h = self.decoder_input(zc)
            h = h.view(n_samples, 128, self.res // 8, self.res // 8)
            return self.decoder(h)

Integration with CAD (via Python-OCC)

The obtained density matrix is converted to a 3D mesh via Marching Cubes, smoothed, and exported to STL. Then import into any CAD system for final refinement.

from OCC.Core.BRepBuilderAPI import BRepBuilderAPI_MakeSolid
from OCC.Core.TopoDS import TopoDS_Shape
import trimesh
import numpy as np

def density_to_mesh(density_matrix, threshold=0.5):
    from skimage.measure import marching_cubes
    density_3d = np.stack([density_matrix] * 10, axis=-1)
    verts, faces, normals, _ = marching_cubes(
        density_3d, level=threshold, spacing=(1.0, 1.0, 1.0))
    mesh = trimesh.Trimesh(verts=verts, faces=faces, vertex_normals=normals)
    mesh = trimesh.smoothing.filter_laplacian(mesh, iterations=10)
    return mesh

def export_to_stl(mesh, output_path):
    mesh.export(output_path)

How to Implement AI Generative Design: Step-by-Step Guide

  1. Audit current designs and loads — collect data on boundary conditions, materials, safety factors.
  2. Choose method — SIMP for clear tasks, VAE for multi-variant generation.
  3. Develop model — implement algorithm, train VAE on your dataset (if required).
  4. Generate and validate — obtain variants, verify with finite element analysis (NASTRAN, Ansys).
  5. Integrate with CAD — convert to STL/STEP, import into SolidWorks, CATIA, or Fusion 360.
  6. Test and refine — finalize design, deliver documentation (model card).

What Results Can Be Achieved with Generative Design?

Domain Task Constraints Goal Material Savings
Aviation Bracket Shear loads -40% weight Significant at material cost
Medical Bone implant Biomechanical loads Porosity for osseointegration Custom
Automotive Shock absorber bracket Impact loads -30% material Substantial
Architecture Load-bearing columns Wind + snow loads Minimal material Custom

Comparison of SIMP and VAE Methods

Method Applicability Data Requirements Generation Time Outcome
SIMP Clear physical problems, linear elasticity Load parameters, boundary conditions Minutes Single optimal solution
VAE Multiple loads, nonlinear constraints Dataset of optimized designs (1000+) Seconds (after training) Multiple variants
Typical Mistakes in Generative Design Implementation
  • Ignoring boundary conditions: if attachment points are incorrectly specified, AI outputs a beautiful but useless shape.
  • Overfitting VAE on a small dataset: less than 1000 samples leads to hallucinations — unrealistic designs.
  • Lack of finite element validation: AI result must be verified in NASTRAN or Ansys.

What Our Work Includes (Deliverables)

We deliver turnkey projects with the following items:

  • Documentation: model card, retraining instructions, and usage guide.
  • Source code: complete AI pipeline and integration scripts.
  • Integration: export to STL/STEP and CAD environment setup.
  • Support: 12 months of updates and troubleshooting.
  • Training: optional session for your engineering team.

Our Experience and Guarantees

We have been in AI engineering for over 7 years, completed 20+ projects in aviation, automotive, and medical industries. We provide a guarantee on algorithm performance in your conditions. If needed, we retrain the model on new data. All source code and model card are delivered to the customer.

Timeline

Basic SIMP prototype — 1–2 weeks. Full VAE system — 4–6 weeks. Timelines are calculated individually after problem analysis. We have experience accelerating projects through transfer learning and quantization (INT8) — p99 latency reduced by 2x.

Evaluate Potential for Your Part

In projects, we achieve 35-40% mass reduction for aluminum and titanium parts. If your current design process takes weeks of manual optimization, contact us for a demonstration. Our AI for structural optimization and neural network shape generation enable rapid iteration. Automated design engineering with AI reduces manual effort. Request an audit of your part and receive a demo calculation in 2 days — get in touch.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.