Geometry Creation Assistant
Geometry Creation Assistant
Geometry from a prompt is easy. Geometry your team can still edit next year is the actual product.
The Geometry Creation Assistant creates geometry in Siemens NX on request: sketches and features from a prompt, parametric parts generated from requirements, variant geometry on command. Every result is proposed as preview geometry the engineer accepts, edits or discards — and everything it builds is fully parametric: real features, real sketches, real expressions, on your part template. Never dumb solids.
It is the “create” member of our NX AI Assistants & Chatbots family, executing through the Vision4NX Connector and NXOpen in your running session.
Chat is one way in; the full discipline — rule-based PMI creation, instruction-driven edit jobs and template-based part generation as reviewable workflows — lives under AI-Assisted Geometry Creation.
The modeling tools behind this assistant, which NX operations they cover today and the acceptance test each one passes, are described under AI CAD modeling in Siemens NX.
Who this is for
- Your team models structurally similar parts from scratch, month after month — brackets, flanges, adapters, fixtures.
- “Quick” geometry requests interrupt seniors: a fixture here, a spacer there, each an hour of routine modeling.
- Variant requests arrive as prose — “same as 4471 but 120 mm spacing” — and become an afternoon.
- Imported or hand-built one-offs pollute your library with unparametric, uneditable models.
- Your modeling guideline defines how a part should be built — compliance depends on who models it.
// One prompt — one parametric proposal, feature tree open
engineer> Mounting bracket for the 80×60 profile: 4× M8 on 100×70 spacing, slotted on one axis, 5 mm steel, our standard chamfers.
- Sketch “base_profile” on datum plane — fully constrained
- Extrude, t = thk (5 mm)
- Hole set 4× M8, positions driven by sp_x / sp_y
- Slot feature on X-pair, length slot_l
- Chamfer set per house standard WN-203
| name | value |
|---|---|
| thk | 5 mm |
| sp_x / sp_y | 100 / 70 mm |
| slot_l | 12 mm |
| thread | M8×1.25 |
Preview geometry, not committed geometry. The proposal sits in your session for inspection — rotate it, interrogate the tree, change an expression. Accept keeps it on your part template; discard leaves no trace.
Parametric by design — never dumb solids
The cheap way to generate geometry from a prompt is a mesh or a boundary-representation lump: looks right, edits like concrete. We refuse that shortcut, because a model’s value is its editability — the second week of its life matters more than the first minute:
- No feature history — every change is surface surgery
- No expressions — “make it 6 mm” means remodeling
- Ignores your templates, layers and naming
- Technical debt from the moment it enters the library
- Clean feature tree, constrained sketches — edit anywhere
- Named expressions drive the dimensions that matter
- Built on your part template — layers, naming, attributes per your modeling guideline
- A model the next engineer can pick up without asking who made it
What it creates
Sketch & feature creation
Described geometry — profiles, holes, slots, ribs, chamfer sets — as constrained sketches and real features, on request, mid-session.
Parametric part generation
A requirements list becomes a part proposal with named expressions for the driving dimensions — the starting point at ninety percent, not a finished design.
Variant geometry
“Same bracket, 120 mm spacing, M10” — the variant proposed from the parametric original, expressions adjusted, ready for review.
Fixtures, blanks & helpers
Reference geometry, simple fixtures, raw-stock blanks — the supporting cast nobody enjoys modeling, created by describing it.
Honest limits
A proposal is a starting point, not a design. The assistant gets you to a reviewable parametric part fast; judging load paths, choosing the compromise, deciding what “good” means — that is engineering, and it stays with the engineer who accepts, edits or discards. Ambiguous prompts get questions back, not guesses.
Prismatic and rule-driven is its home turf; Class-A surfacing is not. Brackets, housings, fixtures, machine elements — yes. Sculpted freeform and styling surfaces — honestly, no; that craft stays manual. And when a part family needs hundreds of systematic variants, deterministic automation beats conversation: that path is AI Workflow Automation for Siemens NX or a dedicated variant generator like our transformer variant design work — we’ll tell you which, before you buy either.
Fixed price — fixed scope
Geometry Creation PoC
from €16,500 fixed
- One part class from your real portfolio, on your part template
- Your modeling guideline encoded — naming, layers, expression conventions
- Prompt-to-preview loop live in your NX — designers try it on real requests
- Tree-quality review by your senior designers — editability judged by the people who inherit the models
- Rollout blueprint: more part classes, variant workflows, library governance
5–7 weeks · price creditable against rollout · on your infrastructure.
For comparison
Routine modeling, by hand
1–3 h per routine part
- Structurally similar parts modeled from zero, repeatedly
- Senior time interrupted for fixtures and spacers
- Guideline compliance depending on who models
Frequently asked questions
What is a geometry creation assistant?
What does “fully parametric” mean here?
Does it follow our modeling guideline?
What happens with an ambiguous request?
Can it do freeform / Class-A surfaces?
We need hundreds of variants of one family — is this the right tool?
Related in the family: the NX Action Assistant modifies what exists, and the Drawing & Documentation Assistant documents what you accept. Overview: NX AI Assistants & Chatbots.
There’s a part your team models from scratch every single month. Describe it to us in one sentence.
We’ll return it as a parametric proposal — feature tree open, expressions named, on your template — so your designers can judge the editability themselves.
Talk to an EngineerPoC from €16,500 · fixed scope · creditable against rollout · on-premises option
