AI Geometry Manipulation
AI Geometry Manipulation
“Change all of them” should be an instruction, not a week.
AI geometry manipulation edits existing Siemens NX geometry on instruction: resize and re-tolerance holes, place and pattern features, move and position bodies and components, fix colors, attributes and layers — as reviewable functions and batch jobs built on NXOpen. An instruction becomes a recipe; the recipe runs over one part or a whole set; every run produces a diff preview, and nothing is committed until an engineer confirms. Parametric where the model allows — and honest about it where the model does not.
It is the “edit” engine of our AI-Assisted Geometry Creation discipline. For single ad-hoc operations driven conversationally, the NX Action Assistant is the chat-side sibling — this page is where its “wrong tool for 500-part batches” honestly points.
Who this is for
- A supplier change, a norm update or a platform decision means the same edit on dozens of parts.
- Design changes ripple through variants and fixture sets that nobody wants to open one by one.
- Library hygiene — colors, attributes, layers, naming — has drifted for years and audits keep noticing.
- You script some of this in NX journals today, but every new case means new code and the backlog wins.
- The edits are describable in one sentence — executing them is the expensive part.
// One recipe, twelve parts — reviewed as one diff, not twelve sessions
On family mounting_plates (12 parts): change all clearance holes Ø6.5 → Ø8.4 where bolt spec = M8; re-center the pattern on the pad; set attribute SUPPLIER_REV = C; move construction sketches to layer 61.
| Part | Change | Result |
|---|---|---|
| MP-1004 | 6 holes Ø6.5 Ø8.4 · pattern re-centered | parametric edit |
| MP-1017 | 4 holes Ø6.5 Ø8.4 · attrs + layers | parametric edit |
| MP-1031 | hole not feature-based (imported region) | flagged — manual edit |
11 parts clean parametric edits1 flagged for review (imported geometry)runtime 4 min
The diff is the contract. You review one change list, not twelve part files. Applied edits are real feature and expression changes — undo-safe, logged per part — and the flagged part tells you exactly why it needs eyes.
What the jobs do
Holes, threads, fits — across sets
Diameter, thread and fit changes driven by a rule (“where bolt spec = M8”) — found by meaning, changed as features, not by opening files.
Features positioned and patterned
Bosses, holes and cutouts placed or re-patterned per instruction — positions driven by expressions, patterns stay associative.
Bodies and components arranged
Bodies moved, components repositioned, assemblies re-arranged against references — with constraint-aware previews before anything commits.
Colors, attributes, layers — at scale
The library cleanup nobody staffs: attributes corrected, colors and layers normalized per your standard — whole folders in one reviewed run.
How it runs
Instructions become recipes: a scoped selection rule (which parts, which features), the change, and the guardrails. The matching — finding “clearance holes for M8” across models that never followed one modeling style — is where AI assists; execution stays plain NXOpen: parametric edits where the model carries them, honest flags where it does not. Recipes are versioned and reusable; runs are logged per part. On your infrastructure, on-premises or EU cloud.
Honest limits
Parametric where the model allows — flagged where it doesn’t. Feature-based geometry gets feature edits; imported or feature-less regions are flagged instead of butchered with direct-modeling guesses. On imported, feature-less regions we say so plainly: those edits stay manual (or synchronous), and the diff tells you which parts they are before the run.
It executes instructions; it does not make design decisions. “Enlarge to Ø8.4 where bolt spec is M8” is a job. “Decide whether M8 is right” is engineering and stays with you. Ambiguous instructions come back as questions during recipe definition — before the run, not in it. And single ad-hoc edits at the designer’s desk remain the domain of the NX Action Assistant — this engine starts paying off from dozens of parts.
Fixed price — fixed scope
Geometry Manipulation PoC
€9,900 fixed
- Two recipes from your real backlog, defined with your team
- Runs over one real part set on your infrastructure — diff preview, confirm gate, per-part log
- Clean/flagged split measured and explained per part
- Recipes versioned and rerunnable by your team
- Rollout blueprint: recipe library, governance, scheduling
2–3 weeks · results are yours either way.
For comparison
The forty-session week
minutes × parts per change wave
- The same edit opened, made and saved part by part
- The part someone missed — found downstream
- Library hygiene postponed for the fifth year running
Frequently asked questions
What is AI geometry manipulation?
How does this relate to the NX Action Assistant?
What happens on parts where the edit isn’t feature-based?
Is a run reversible?
We already script NX journals. Why this?
Where does it run?
Related engines: Parametric Part & Variant Generation creates the families these recipes maintain, and Rule-Based PMI Creation annotates what you’ve changed. Overview: AI-Assisted Geometry Creation.
Somewhere on your desk is a change note that means the same edit on a dozen parts. Don’t open them one by one.
Send us that change note and three of the parts — we’ll return the recipe, the diff preview and the honest clean/flagged split for the set.
Talk to an EngineerPoC as an NX Sprint, €9,900 · fixed scope · on-premises option