Contacts
Get in touch
Close

Contacts

Romania, Cluj-Napoca – 400157
Str. Ploiești Nr. 9

Romania, Vama – 447350
Str. Fermei Nr. 14

+40 774 463 429

info@inteliscience.net

Live Model Check Assistant

Live Model Check Assistant

Live Model Check Assistant

The release review finds what the designer could have known three weeks earlier. Move the check to where the mistake happens.

The Live Model Check Assistant is an event-watcher that runs alongside the designer in Siemens NX and checks the model against your house standards and design rules at modeling time — not at release. When a rule is violated, it says so in plain language, cites the exact rule, and suggests a fix. It never blocks, never auto-corrects, and never decides: the designer sees the flag and stays in charge.

It is the “watch” member of our NX AI Assistants & Chatbots family — a watcher that runs with your NX session, wired to your rulebook.

Who this is for

  • Your design guidelines live in a 90-page PDF that new designers read once and veterans quote from memory — differently.
  • Standards violations surface at design review or release, where every fix costs a loop.
  • The same findings repeat: wall thickness, draft angles, forbidden features, naming, layers — reviewers are tired of writing them.
  • Rules exist as tribal knowledge: the check depends on who reviews.
  • You’ve considered NX Check-Mate but need checks that speak your standard’s language — with the rule text, not an error code.

// Tuesday, 10:41 — the assistant watches while the designer models

10:41:02 OK

Pocket feature created on housing_base — wall thickness 3.2 mm, within rule

10:43:17 OK

Draft applied, 2.0° — meets minimum for tool release

10:47:55 WARN

Rib added near boss group — wall drops to 1.8 mm at the junction

WARN · in plain language, rule cited

The new rib thins the wall between rib and boss to 1.8 mm — your casting guideline requires 2.5 mm minimum for AlSi9Cu3. [KR-041 §4.2 · rev F]

Suggested fix: offset the rib base 1.2 mm outboard, or reduce rib height to 14 mm — both keep the connection stiffness target. Your call.

The assistant flags; the designer decides. No blocking, no silent auto-fix — a violation costs one glance now instead of one loop at release. Every flag and every decision is logged, which your quality team will appreciate at audit time.

What it checks — your rules, not textbook rules

Geometry rules

Manufacturability limits

Wall thickness, draft angles, radii minima, forbidden feature types per process — your casting, machining and sheet-metal guidelines, checked as geometry changes.

Structure rules

Model organization

Layers, naming, expression conventions, template conformity, reference-set hygiene — the discipline that makes models reusable by the next person.

Standards rules

House standards & ISO GPS basics

Standard-part usage, thread series, fit pairings, material-dependent rules — with the rule text cited, not an error code to look up.

Extendable

Your existing checks, live

Check-Mate checks and custom NXOpen validations you already own can feed the same event stream — one feed, one language, one log.

How the event-watcher works

The check assistant runs with your NX session and reacts to modeling events as they happen: feature created, parameter changed, sketch closed. Each event triggers the rules relevant to it; nothing polls, nothing scans overnight. Deterministic geometry checks run first; the AI layer translates findings into your rule’s language and drafts the fix suggestion. On-premises or EU cloud; the model never leaves your infrastructure. This is deliberately a different channel from the Vision4NX Connector — the Connector is our MCP interface for programming NX and getting NX help with Claude Code; the live watcher does not run through it. The two meet only when you hand an approved fix to the NX Action Assistant.

01 · Events

NX session, subscribed

Feature, sketch and parameter events via NXOpen — as they happen.

02 · Rules

Your rulebook, encoded

Deterministic checks per rule; versioned, testable, yours.

03 · Feed

Plain language + citation

AI phrases the finding, cites the rule, drafts a fix. Designer decides.

Honest limits

It warns; it never decides. There is deliberately no blocking mode and no auto-fix: a rule engine that stops designers mid-thought gets disabled within a week, and an auto-fix that guesses wrong destroys trust permanently. The assistant’s job is to make the violation visible while fixing it is still cheap — the judgement call stays with the designer, including the call to ignore a warning with reason.

A rule it can check is a rule you can write down. “Looks wrong” is not checkable; “wall < 2.5 mm for AlSi9Cu3” is. The PoC starts with one part family precisely because encoding a rulebook honestly takes workshops with your senior designers — and a full multi-family rollout is a bigger program than a PoC, which we say here rather than in the follow-up offer. For checks at release against MBD/PMI completeness, the right tool is our MBD/PMI Compliance Automation — batch, deterministic, release-gate. This page is the modeling-time companion, not its replacement.

Fixed price — fixed scope

Live Check PoC

€16,900 fixed

  • Rule set encoded for one part family — workshops with your senior designers included
  • Event-watcher live in your NX, on your parts — designers try it themselves
  • Replay validation against past release findings — would-have-caught, measured
  • False-positive rate reported honestly — a noisy checker is a dead checker
  • Rollout blueprint: more families, more rules, Check-Mate integration — scoped as its own program
Start the PoC conversation

4 weeks · fixed scope, no obligation afterwards.

For comparison

The cost of the late find

1 loop per finding

  • Review finds the 1.8 mm wall three weeks after it was modeled
  • Rework, re-review, sometimes re-release — per repeat finding
  • Senior reviewers spending judgement on findings a rule could catch

Frequently asked questions

What is a live model check assistant?
A live model check assistant is an event-watcher that runs alongside the designer in Siemens NX and checks the model against company design rules at modeling time. When a rule is violated it flags the violation in plain language, cites the rule, and suggests a fix — without blocking the designer and without changing the model itself.
Does it interrupt or slow down the designer?
No. Checks run on modeling events in the background; findings appear in a feed the designer glances at, not a modal that demands attention. There is no blocking mode by design — and the PoC measures the false-positive rate, because a checker that cries wolf gets ignored, which is worse than no checker.
Where do the rules come from?
From your design guidelines and your senior designers — encoded together in PoC workshops, versioned like code, testable against example parts. The AI does not invent rules; it phrases findings and drafts fixes. If a rule isn’t written down yet, the workshop writes it down — many customers consider that document alone worth the exercise.
How is this different from NX Check-Mate?
Check-Mate runs checks when invoked and reports in checker language; this assistant watches continuously and reports in your rulebook’s language, with the rule cited and a fix drafted. They are not rivals: existing Check-Mate checks can feed the same live event stream, so prior investment carries over instead of being replaced.
Can it fix the violation automatically?
It drafts the fix; applying it is the designer’s move — either manually or by handing the suggested fix to the NX Action Assistant, which previews the change and applies it after confirmation. The two assistants share the confirm-gate philosophy: nothing touches the model without an engineer’s explicit yes.
What about checks at release — PMI completeness, MBD readiness?
That is a different discipline: batch, deterministic, gate-keeping — covered by our MBD/PMI Compliance Automation. The live assistant reduces what the release gate finds; it does not replace the gate.

Related in the family: the NX Action Assistant applies the fixes you approve, and the MBD & PMI Authoring Assistant creates annotations the compliance gate will later verify. Overview: NX AI Assistants & Chatbots.

Your reviewers write the same three findings every week. Let them stop.

Send us one chapter of your design guideline and one part that violates it — we’ll show the violation flagged live, in your rule’s own words, while the model is being edited.

Talk to an Engineer

PoC as an NX Sprint Plus, €16,900 · one part family · on-premises option