Duro

Duro’s Product Lifecycle Management (PLM) platform manages data for hardware companies to build disruptive products. Duro’s helps make engineering collaboration simple yet also maintains governance to ensure repeatable processes, quality products, and traceability.

Integration Overview

The Datum Source and Duro integration is built to automate your BOM and part as well as streamline the communication between the engineering and procurement teams. Datum automatically sync’s parts libraries, and any updates to new or existing parts in Duro are automatically reflected in Datum.

There are multiple triggers and integration points that connect our systems; however, the ulitmate use case is keeping the part information and files in Datum in sync with Duro at all times. This eliminates the need for requesters to create parts in Datum. Instead, requesters can simply search for a specific part number or name, and they can add the part(s) to a request. Importantly, the Duro <> Datum integration is configurable to meet your specific use cases.

Integration Details

The following integrations are available between Duro and Datum. Please reach out to [email protected] for further information and/or to discuss implementation.

1. Part Library Sync

   Parts are initially created in Datum when a Duro component’s status is approved for Prototype. After that point, all approved changes component updates/modifications are automatically sync’d to Datum as well. Parts added in Datum via this integration will have an “External” flag on the part to indicate the part was created via automation. Notably, the part name, number, and revision fields for External parts are read only and can not be edited by users directly in Datum.

   

   For easier navigation, we recommend including a URL custom field in Datum, and our integration will automatically populate this field with the corresponding component URL in Duro.

   

   Datum takes a conservative view on component updates, and only modifications that have completed an approved change order process (ECO, MCO, or DCO) will trigger a part update via the integration. To accommodate the in between, ‘modified state’ in Datum, the integration automatically adds an Open Change Order flag to the corresponding Datum part whenever an unapproved modification is in process. For the avoidance of doubt, the Open Change Order flag in Datum is equivalent to the Modification alert in Duro.

   

   If a change order in Duro results in a component revision, Datum will automatically create a new part and flag the prior revision with an Inactive flag. This flag is intended to signify that there are one or more subsequent revisions to a part number.

   

   See below for a visual representation of the Duro —> Datum integration throughout the lifecycle of a component.

   
2. Part Files Sync

   The Duro —> Datum integration for part files operates similarly to the broader part library sync outlined above. The only difference in this integration flow is the timing by which files are initially added to parts.

   Specifically, part files from Duro are initially pushed to Datum when a part is added to a request. We structured this event based integration to align file transfer and mgmt to when the files are most relevant to the procurement team and associated suppliers. After files are initially transferred to a Datum part, then the part files sync is fully aligned with the same logic as the broader part library sync outlined above. Namely, only modifications that have completed an approved change order process (ECO, MCO, or DCO) will trigger part files from Duro —> Datum to re-sync.

   

   See below for a visual representation of the Duro —> Datum files integration throughout the lifecycle of a component.