> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cosmon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Part Release

> Run pre-release checks and generate release packages before a part or assembly goes to manufacturing or PLM.

## 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

<AccordionGroup>
  <Accordion icon="clipboard-check" title="Run a pre-release check">
    ```text theme={null}
    Run a pre-release check on C:/Projects/Pump/pump_asm_v2.SLDASM and every part it references. Confirm: no rebuild errors or warnings, no suppressed features without a design-table or configuration reason, no in-context references to other assemblies, and every part has material and part number custom properties set. List every blocker before I proceed.
    ```
  </Accordion>

  <Accordion icon="table-list" title="Verify the BOM before release">
    ```text theme={null}
    Compare the BOM on the assembly drawing against the actual component structure in pump_asm_v2.SLDASM. Flag any component in the model missing from the BOM, any BOM line with no matching component, and any quantity mismatch.
    ```
  </Accordion>

  <Accordion icon="box-archive" title="Generate a release package">
    ```text theme={null}
    Generate a release package for the bracket at C:/Projects/Bracket/bracket_v3.SLDPRT: a dimensioned PDF of the drawing, a STEP AP214 export of the model, and the BOM as a CSV. Name each file <part_number>_<rev>.<ext> and place them in C:/Releases/ECN-4471/.
    ```
  </Accordion>

  <Accordion icon="code-compare" title="Bump revision across an assembly">
    ```text theme={null}
    Bump the revision from B to C on C:/Projects/Bracket/bracket_v3.SLDPRT and update every parent assembly drawing that references it. Add a revision table entry noting "Updated per ECN-4471" on each affected drawing.
    ```
  </Accordion>

  <Accordion icon="database" title="Sync release metadata to PDM">
    ```text theme={null}
    Once the pre-release check passes, check in C:/Projects/Bracket/bracket_v3.SLDPRT to SolidWorks PDM, set its state to "Released", and update the revision and effective date custom properties to match the drawing.
    ```
  </Accordion>
</AccordionGroup>

## 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.