Objective: Connect your Duro account to First Resonance and upload Bill of Materials (BOMs) to First Resonance by submitting a Change Order.

Difficulty: Easy

In this article:

Overview
Connect your account
Populating a BOM in ION by creating Change Orders in Duro

Navigate to a Duro assembly
View assembly tab to see full BOM
Approved Change Order process
View ION parts library to see same assembly structure

Duro is the only PLM to have a native integration with First Resonance’s Factory Operating System (OS), ION. The integration with First Resonance allows your engineering and manufacturing teams to share data fluidly without glitches and delays.

Overview

This revolutionary partnership empowers our clients with seamless communication channels, component traceability, and automatic file transfers among other benefits. Our connection with First Resonance’s Factory OS, ION, eliminates the time-consuming back and forth dialogue that occurs when teams are segmented and unable to collaborate easily. Installation of ION is quick, and managing it is simple.

Connecting your PLM to your factory OS closes the loop between engineering and manufacturing teams, enabling you to transfer Engineering Bill of Materials (eBOM) and Manufacturing Bill of Materials (mBOM) details with speed and ease. This transfer happens upon approving a Change Order with one click. In this article, we cover how to connect your account, as well as how to get started with Bill of Material (BOM) uploads within the integration.

Connect your account

Enable the First Resonance - Duro integration by completing the below steps:

Login to your Duro account.
Navigate to your avatar and select Integrations.
On the line for First Resonance, click on Connect.
Enter your First Resonance account credentials (account URL, username, and password).

For instructions on how to add Duro from First Resonance, please see the ION Factory OS article on Duro. The linked directions can be completed within ION in order for ION to accept the data push from Duro. Then, once a CO is approved within Duro, ION integrates the altered part information to keep all products up-to-date. ION provides a GraphQL mutation to be used and also provides descriptions of connected inputs including the following:

templateName
keycloakClientId
keycloakClientSecret
apiHost
apiKey
apiVersion
customConfig

Populating a BOM in ION by creating Change Orders in Duro

Once your First Resonance and Duro accounts are linked, parts information is shared between the two platforms. By uploading a BOM to a Change Order in Duro, then subsequently approving and submitting said Change Order, your BOM gets automatically uploaded into ION. To understand how this is mapped in real time, we’ll walk you through an end to end demonstration to provide you with a concrete visualization of your company’s data management. The actions covered in the following sections are as follows:

Navigate to a Duro assembly.
View assembly tab to see full BOM.
Approved Change Order process.
View ION parts library to see same assembly structure.

Step 1: Navigate to a Duro assembly

Navigate to your Duro library and select an assembly to use for this exercise.* There are a few different ways to do this:

Select an assembly from your Duro dashboard
Select an assembly from your product library
Search for an assembly using the Search Bar

*Note: Components in the Design stage will not automatically create a Change Order in Duro.

Step 2: View assembly tab to see full BOM

Once you’ve selected an assembly, navigate to the assembly tab, which is located beneath the Product Overview, Details, Team, and Build Schedule tiles. For more information on what this tab houses, please visit the Assembly section of Anatomy of the Product Table.

Step 3: Approved Change Order process

Now, navigate to the assembly page within Duro of the component previously selected in First Resonance. In this section, we’ll create, submit, and approve a Change Order in Duro.

Click on the pencil icon in the upper right toolbar to edit the assembly..
Update a few different fields within the page (e.g., a spec field, the description, and the unit of measurement).
Click Save to record the updates. This will create a new Change Order.
Click on the Change Order icon located in the upper right toolbar, represented by the red triangle.
Select Add to Change Order.
Upload your BOM to the Change Order.
Give the Change Order a name, designate a Change Order type, and add any other information as desired.*
Finally, click on Submit for Approval.
Approve the Change Order. This action closes the Change Order, triggering the upload in First Resonance.

*Note: for more information on how to submit a Change Order, please refer to our article on Change Orders.

Step 4: View ION parts library to see same assembly structure

Navigate to your ION library to see the changes made within Duro reflected within ION. Find the selected component that was modified. If the description was altered, the new content will be visible here. If any of the custom attributes were altered, those will display the new category values. Attributes can be mapped per integration, and you can decide which fields specifically should be brought over. However, description and revision values are top level attributes that are always brought over from Duro.

Within your ION library, the following assembly information is visible: update revision scheme dropdown, a description, an export control option, lead time, tracking level options, associated procedures, finish attribute, and custom attributes among other options. The description provides information about the component, product, or assembly in ION as is before any modification. Properties with ION are mapped to specific fields in Duro; for example, the custom attribute (ION) is linked to the category attribute (Duro) and the finish attribute (ION) is linked to the FINISH spec field (Duro).

In summation, our integration with ION provides you with field mapping flexibility and automatic data uploads between the two platforms. If you have any issues, please contact us at info@durolabs.co.