Skip to main content

Overview

Releasing a part means more than the model being finished — it means no rebuild errors, no dangling external references, correct metadata, and a package of the right files in the right formats waiting for whoever picks it up next: a supplier, a PLM system, or a shop. Missing any one of these is a common source of a release getting bounced back. Nexus runs the pre-release check, tells you exactly what’s blocking release (not just that something is), and generates the release package once the model is clean. Where you use a PDM or PLM system, it can also push the revision and metadata update.

What Nexus can help with

  • Pre-release checks — Confirm no rebuild errors or warnings, no suppressed features left unexplained, no in-context (external) references, and correct material and custom properties.
  • BOM verification — Confirm the BOM structure matches the assembly as modelled, with no missing, duplicate, or mismatched-quantity items.
  • Release packages — Generate the standard bundle for release: dimensioned PDF drawing, neutral-format model (STEP, IGES), and BOM, in your defined folder structure and naming convention.
  • Revision and metadata updates — Bump the revision and update title-block and custom-property metadata across a part and everywhere it’s referenced in parent assemblies.
  • PDM/PLM sync — Where connected, check in files and update state and metadata in SolidWorks PDM or Teamcenter as part of the release step.

Example prompts

Tips for part release prompts

  • State your release checklist explicitly — “no rebuild errors” means different things at different companies. If you have a house checklist, give it to Nexus once and reuse it as a skill for every release.
  • Name your PDM/PLM system — if metadata needs to sync to SolidWorks PDM or Teamcenter, say so — the check-in and state-update steps are system-specific.
  • Ask for blockers, not silent fixes — for release-critical items (missing material, in-context references), ask Nexus to report the issue rather than guess at a fix. Some decisions belong to you.
  • Specify the package contents and naming convention — file formats, naming pattern, and destination folder should be explicit so the package matches what your downstream process expects.
  • Run the pre-release check before generating the package — catching a blocker before the package is built avoids releasing files that need to be redone.