Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.
As designs grow, you'll want to share components between projects. CAD tools provide mechanisms to reuse designs: derive, link, library components.
Cross-file sharing.
Use these three in order. Each builds on the one before.
In one paragraph, explain cross-file sharing.
Walk me through Fusion 360's Derive feature.
I'm running a 5-person team. How do we share designs?
WHY SHARE:
You design a standard part (e.g., a snap-fit bracket).
You use it in multiple projects.
Without sharing: redraw each time.
With sharing: change once, all projects update.
SHARING METHODS:
1. COPY-PASTE:
Copy the geometry; paste into a new file.
No connection between them.
Pro: independent files.
Con: changes don't propagate.
2. DERIVE FROM ANOTHER FILE:
Fusion 360: 'Derive' a body from another file.
OnShape: 'Link' between documents.
Pro: changes propagate.
Con: dependency between files.
3. EXTERNAL REFERENCE:
Some CAD: import another file as a 'live' reference.
The reference geometry stays in sync.
Pro: same as derive but more flexible.
Con: file management complexity.
4. PUBLIC LIBRARY:
In Fusion 360: 'Public Components' are shared across team.
In OnShape: 'Shared Documents' or 'Library'.
PRACTICAL EXAMPLE: A FAMILY OF BOXES.
Approach 1: separate files.
- small-box.f3d
- medium-box.f3d
- large-box.f3d
- Each with its own parameters.
- Update one; manually update others.
Approach 2: master + derived.
- master-box.f3d: contains the parametric box.
- small-box.f3d: derives from master-box.f3d, sets specific parameters.
- Similarly for medium-box.f3d, large-box.f3d.
- Update master; all variants update.
Approach 3: configurations within one file.
- master-box.f3d with multiple configurations:
- 'small': specific parameters.
- 'medium': specific parameters.
- 'large': specific parameters.
Pro: single file; all variants accessible.
Con: parameter changes affect all.
FUSION 360 — DERIVE:
- Open File B.
- File → Insert → Insert Derive.
- Select File A.
- Choose which bodies to derive.
- File B now has those bodies; changes in A propagate to B.
ONSHAPE — DOCUMENT LINKING:
- 'Link to Component' or 'Component Versions'.
- Reference another document.
- Changes propagate.
LIBRARY DESIGN:
For a personal library:
- Have a 'shared-parts' folder.
- Each common part (bracket, bolt, knob): own file.
- Reference them in projects.
Update the library; all projects update.
ORGANIZATIONAL LEVEL:
For teams:
- Centralized library.
- Version control (cloud or git).
- Peer review of library updates.
For solo:
- Local folder.
- Backups (cloud, drive).
WHEN NOT TO SHARE:
Some parts are project-specific:
- One-off designs.
- Customer-specific work.
For these: independent files.
NAMING CONVENTIONS:
shared/bracket-2020.f3d (year of design)
shared/screw-m3.f3d
shared/magnet-pocket.f3d
Easy to find; clear what each is.
DEPENDENCIES:
Watch out for circular dependencies:
File A → uses File B → uses File C → uses File A.
This breaks.
Keep the dependency tree shallow.