Tutorial: Interface Analysis in Onshape's CAD software
This guide shows a Step-by-Step tutorial of a mechanical design being analyzed in the CAD software Onshape. The guide shows how a manual interface analysis is done within the environment of Onshape’s CAD software. By applying the interface analysis method, on this specific design, the complexity between two parts are explored and can be used to synthesize a exactly constraint design with would result in an interface score of “0” which is ideal – reflecting that only the exact needed information for the product is carried along.
STEP-BY-STEP GUIDE – MECHANICAL DESIGN BEING ANALYZED IN ONSHAPE CAD
- OPEN ASSEMBLY OF THE GIVEN PRODUCT
- IDENTIFY THE TWO PARTS AND THE INTERFACE FOR ANALYSIS
- In this case – the CAP and the BASE PLATE.
- NOTE THE PART NAMES IN THE INTERFACE TABLE
- ISOLATE THE TWO PARTS CONTAINING THE INTERFACE FOR ANALYSIS
- INSERT SCREENSHOT FOR REFERENCE
- DETERMINE THE INTENT OF THE INTERFACE BY THE DOFs
- FIND APPLICABLE VIEWS FOR INTERFACE ANALYSIS
- ASSIGN A SUITABLE COORDINATE SYSTEM IF THE GLOBAL COORDINATE SYSTEM IS NOT SUITED
- IDENTIFY CONTACT SURFACES IN THE GIVEN VIEW
- IDENTIFY INTENT & ACTUAL CONSTRAINTS
- Join RD8 online courses to learn how to identify and count constraints.
- IDENTIFY AMBIGUITIES AND NOTE SCORE
- See RD8 Interface Rules documentation for identification of ambiguities.
- REPEAT PROCESS FOR ALL FUNCTIONAL SURFACES
- Join RD8 online courses to learn more about how to review interfaces in multiple dimensions systematically.
- CALCULATE THE INTERFACE SCORE
- The interface score equals the absolute difference between “actual” and “intent” DOF-sets plus the identified ambiguities.
Quantification of a mechanical interface example
The before-after example of two parts (grey and green) - shown in a section cut - illustrates some mating features in the interfaces.
Move the slider to see the before and after example.
The interface score for the first interface is 4 – meaning 4 additional and unnecessary geometry features that adds complexity to the product. A score of 0 is ideal – the interface in equilibrium – and have exactly the amount of information/constraints that is needs.