NX BOM Management

Objective: To instruct users how to save changes and release parts from NX to Duro.

Difficulty: Easy.

In this article:

1. Saving Changes to a Part
   • Steps to Save Changes to a Part
2. Releasing a Part
   • Release Actions Based on Lifecycle Status
   • Steps to Release a Part
3. Get Latest

Efficiently saving changes to and releasing parts in Duro's NX integration is essential for keeping project data organized and current. This article outlines the processes of saving changes and releasing a part from NX CAD to Duro.

---

Saving Changes to a Part

Saving changes pushes updates made to a part from NX to Duro. This includes changes to the custom properties, images, and documents, such as production and source files. This workflow acts as a sub-revision release, allowing updates to be submitted for review without a formal change order. This process is essential for saving changes and tracking revision history outside a formal change order. 

Steps to Save Changes to a Part

Before saving changes to a part, ensure that you have pulled a part number so that Duro tracks your component.

Follow the steps below to save changes to a part from NX to Duro:

1. Sign in to the NX Duro add-in with your Duro credentials.
2. Create or open the part you wish to save changes on.
3. Click the “Publish” icon and select the “Save Changes” option to open the "Save Changes to Duro" modal.
4. Select the parts to push to Duro by checking the box to the left of the line item.
5. Optional: select the boxes for “Include Production Files (PDF, STP)” and/or “Include Source Files (SLDPRT, SLDASM)” to include in the push.
6. Click the “Save Changes” button.

Saving changes to the part will create a sub-revision with the current state. If you checked the boxes in Step 5 above, ensure all necessary files are uploaded to Duro. Monitor the updates and visual feedback to confirm the action is complete.

Releasing a Part

Releasing components from NX CAD to Duro encompasses all the functions of saving changes, including parts metadata and new documents. However, a release sends parts through a formal review process by initiating a change order. 

Release Actions Based on Lifecycle Status

• Design Status: Creates a release on the release page and increments the revision based on the desired increment. A release of components in this lifecycle status will not create a change order.
• Prototype/Production Statuses: Creates a change order and attaches all components and associated documents to the change order. This must be resolved and approved before the part is released.

Assembly Conditions

Duro will not generate a change order if all components in an assembly are in Design. However, if it is part of an assembly with other components in Prototype or Production, a change order will still be initiated upon the release of the assembly.

Steps to Release a Part

1. Launch NX, and open the part(s) you wish to release.
2. Click the “Publish” icon and select the “Release” option to open the Release modal.
3. Add a name, notification list, and notes to your release.
4. Select the parts to release by checking the box to the left of the line item.
5. Either individually select or use the bulk change methods for revision values, workflow states, and/or procurement methods for the selected parts by doing the following:
   1. Click the “Set Revision,” “Set Workflow,” and/or “Set Procurement” buttons to generate the respective modals.
   2. Enter the value you want to apply to the selected components.
   3. Click the “Update” button.
   4. This will automatically update the modal values.
6. Optional: select the boxes for “Include Production Files (PDF, STP)” and/or “Include Source Files (SLDPRT, SLDASM)” to include in the release.
7. Click the “Release” button.

After completing this workflow, your parts will immediately be released, initiating a change order in Duro.* Once the change order is approved in Duro, the parts move to the released status, ensuring all team members have the most current information. 

Whenever a part is released in Duro, the system automatically generates files into your Windows directory. Please be aware that if the file names are identical to the part names, the newer will overwrite the older version, regardless of the file extension.

Note: As per the requirements listed in “Release Actions Based on Lifecycle Status.”

Get Latest

"Getting the latest" is a feature in the Duro add-in for NX that pulls updated information from Duro into NX. This ensures engineers have the most current designs, revisions, and part data, reducing errors and inconsistencies. 

To get the latest information, open the “Manage Parts” modal and click on the “Get Latest” button: . A warning message will pop up telling you that “Local files will be updated. By getting the latest, any changes in Duro that are currently not present in your local files will be updated. This action cannot be undone.”