Objective: To learn about our Onshape integration.
In this article you will find:
- Overview: Duro PLM for Onshape
- Feature List Summary
- Feature Overview: Data Sync (via Pull Part Number)
- Feature Overview: Release
Duro integrates with Onshape through an integrated cloud application, called Duro PLM, available in the Onshape App Store. When Onshape is paired with Duro PLM, companies can truly leverage the power of the cloud to manage their hardware product data across distributed teams, reducing overhead and accelerating engineering output.
Overview: Duro PLM for Onshape
Duro’s integration with Onshape extends the CAD tool's value by providing a simple means to set up a PLM-based part numbering system, manage configurations, and allow design releases to be centralized in a system accessible to all. With Duro, Onshape users can now implement a PLM system in just a few simple steps, whether migrating from spreadsheets or an existing PLM platform. With both Duro and Onshape, building a centralized system of records that spans across design, supply chain management, and manufacturing, couldn’t be any easier.
Duro and Onshape share a philosophy around cloud-native tools and have a cultural alignment. We work with fast-moving companies and talented engineering teams globally that need to move quickly, and this speed is one of the key competitive advantages in the industry.
Feature List Summary
Data Sync (via Pull Part Number): Associate Onshape part numbers with Duro customer part numbers (CPNs) and instantly create new component listings in the Duro Web Application.
Release: Built directly into Onshape’s existing release management workflow, users can release approved revisions to the centralized Duro Web Application, build a history of releases, and store important production files.
Configuration Management: Duro provides a great way to get both part and assembly configurations out of Onshape. Duro automatically maps both types of Onshape configurations to your Duro account.
Link Back to past Onshape versions: Duro provides a link back to the exact Onshape release for any revision documented in Duro. Find the link in the EID field in the Duro component page.
Feature Overview: Data Sync (via Pull Part Number)
Onshape users can leverage the benefits that PLM-based part numbering best practices bring, including reducing CAD merge issues, preventing conflicts with external part numbers, and navigating multiple Bills of Materials (see Duro’s step-by-step guide for centralizing your part numbering system).
To assign Duro-based CPNs to Onshape parts in assemblies within the Duro PLM app, load the desired Part Studio or Assembly from the drop-down in the left navigation and follow these steps:
Select the desired parts and assemblies from the left sidebar.
Select the Pull Part Number button.
Assign an appropriate category for each item and click Continue, then Done.
That’s all there is to it. Within seconds you can assign Duro PLM-based CPNs to Onshape native parts and assemblies.
Duro’s category-driven part numbering scheme allows all company members to run parametrically-based searches for product-related information created in Onshape or any other integrated application. Duro’s automated data validation engine can even scan your parts and assemblies for the most common mistakes that frequently lead to manufacturing delays.
Feature Overview: Release
Built directly into the existing Onshape Release Management workflow, the Duro PLM app for Onshape allows teams to publish and centralize approved releases, drawings, and production files to Duro's cloud-based PLM application. Duro supports the direct publishing of released component files as well as the ability to run a parallel approval process through Duro's Change Order feature. Control over release processing through Duro is controlled through Duro's Progressive Lifecycle Status System.
Progressive Lifecycle Status System
Duro runs a progressive lifecycle status system that identifies the appropriate stage of the lifecycle for all components. The system mirrors the natural progression of a component (or product) as it matures from an initial concept design through prototyping, into production, and eventual end of life. The lifecycle status value options in Duro include: Design, Prototype, Production, or Obsolete.
These status values play a significant roll in the Duro PLM app for Onshape as they determines the release workflow that the component will follow. More information regarding these workflows can be found below.
Duro's Release Workflows are built on top of Onshape's Default Release Workflow (shown below).
Release from Onshape to Duro (Design Status)
In accordance with Duro's Progressive Lifecycle Status System (see above), parts or assemblies that are in Design status are not revision controlled and are thus not subject to approval through an Engineering Change Order (ECO) in Duro. When in Design status, a part or assembly can be submitted for approval (or released without submitting for peer approval) within Onshape. Once approved, Onshape will immediately publish the released documents to Duro, without initiating an Engineering Change Order (ECO) in Duro.
Release from Onshape to Duro (Prototype and Production Statuses)
When a part or assembly is set to Prototype or Production status, the component is now eligible to go through a review and approval process in both Onshape and Duro. Onshape approval follows the default release workflow, while Duro approval follows the Duro Change Order workflow.