NX Action Assistant
NX Action Assistant
Say the operation once. Confirm it once. Stop clicking it fifty times.
The NX Action Assistant is a chat assistant that executes modeling operations in Siemens NX: it creates and modifies features, sets parameters and expressions, and runs repetitive modeling steps — through the Vision4NX Connector and NXOpen, inside your running NX session. Every operation is shown as a preview first and applied only after the engineer confirms it; applied actions are undo-safe and logged.
It is part of our NX AI Assistants & Chatbots family — the “act” tier: not an assistant that tells you which menu to open, but one that opens it, fills it in, and waits for your go.
Who this is for
The assistant earns its keep where modeling work is frequent, small and annoying — the operations nobody ever wrote a dedicated NXOpen tool for. You are a candidate if most of these sound familiar:
- Your designers perform the same few operations dozens of times a week — standard bosses, rib patterns, counterbore changes, attribute updates.
- House standards define exactly how these features must look, and applying them is pure typing, not design.
- You have NXOpen tools for the big jobs, but the small repetitive work never justified one.
- Every engineer solves the same micro-task slightly differently — and downstream checks catch the drift.
- New hires spend weeks learning where things are in NX before they can be productive on real work.
// One request, one confirmation — watched live in your NX session
Change the counterbores on the mounting face from M6 to M8 and update the hole table.
Found 6 counterbore features on face MF-1. Proposal per house standard:
| Parameter | Current | Proposed |
|---|---|---|
| thread | M6×1 | M8×1.25 |
| cbore ø / depth | 11.0 / 6.4 | 14.0 / 8.4 |
| hole table, sheet 2 | rev C values | regenerate |
applied by engineer · one undo step · logged 09:14:22 · 6 features + hole table updated
The preview is the contract. What you see in step 02 is exactly what NXOpen will execute — no more, no less. Close the preview, and the model is untouched.
What designers hand over first
House-standard features on command
Bosses, ribs, counterbores, chamfer sets — created exactly per your works standard, every time, by name: “M8 boss per house standard on these pads.”
Expressions & parameter changes
“Set flange thickness to 12 across the family” — expression edits with a diff preview of every value that will change, before anything does.
Small-batch modeling steps
The 15-part edit that never justified a dedicated tool: attribute updates, renames, layer moves — proposed as a list, confirmed once.
Guided model cleanup
Unused expressions, stray sketches, off-standard layers — found, listed, and removed only after you’ve seen the list.
How it connects to your NX
No macros, no screen automation. The assistant speaks MCP to the Vision4NX Connector; confirmed actions execute through NXOpen inside your session, with results visible live. It runs under your license and your permissions, on-premises or in an EU cloud under your control — and it is model-agnostic on the assistant side, including Claude Code via MCP.
Your assistant, your model
Any MCP-capable assistant — cloud, EU cloud, or fully local.
Preview & confirm gate
Builds the proposal, renders the preview, executes only confirmed actions.
Native execution in NX
Supported Siemens APIs — the same surface your own tools use. Undo-safe, logged.
Honest limits
It will not design for you. The assistant executes well-defined operations; design intent — what the part must do, which compromise to take — stays with the engineer. If a request is ambiguous, the assistant asks instead of guessing, and anything it does propose still passes the confirm gate. Nothing is ever applied without your confirmation, and every applied action is logged.
It is the wrong tool for nightly 500-part batches. High-volume, rule-based jobs belong in deterministic pipelines with fixed rules and testable results — that discipline is covered by AI Workflow Automation for Siemens NX. And the operations the assistant can execute are bounded by what NXOpen exposes plus what we map in the PoC: your custom features and templates work, but they are mapped deliberately, not discovered magically.
Fixed price — fixed scope
Action Assistant PoC
€9,900 fixed
- One bounded workflow — the operations your designers repeat most, mapped to your standards
- Preview-and-confirm loop working in your NX, on your parts
- Runs on your infrastructure — on-premises or EU cloud
- Proposal-quality report measured on your requests — not a marketing number
- Rollout blueprint: more operations, more seats, governance
2–3 weeks · results are yours either way.
For comparison
The cost of fifty clicks
hours weekly per designer
- The same standard features, built by hand, dozens of times a week
- Slight per-engineer drift that downstream checks catch late
- Micro-tasks too small for a tool, too frequent to ignore
Frequently asked questions
What exactly is an NX action assistant?
Can I undo what the assistant did?
Which operations does it support?
Does it work with our custom NXOpen tools and templates?
Which AI assistant does it need — are we locked in?
What happens when the assistant proposes something wrong?
Related assistants in the family: the Geometry Creation Assistant creates new parametric geometry from a prompt, and the Drawing & Documentation Assistant takes over once the model needs sheets. Overview: NX AI Assistants & Chatbots.
Your designers repeat a few operations more than all others combined. You know which ones.
Send us the one that costs the most time — we’ll show it running from a chat prompt on your own parts, preview and confirm included.
Talk to an EngineerPoC as an NX Sprint, €9,900 · fixed scope · on-premises option