## Overview Top-down assembly design is a parametric modeling methodology where individual components are created or modified within the context of the overall assembly, rather than in isolation. Designers reference existing geometry, dimensions, and positioning to define new components. This creates interconnected relationships where changes to a primary framework automatically propagate to all dependent parts, ensuring perfect fit and alignment. While powerful, this approach generates external references that must be carefully managed, and virtual components offer an alternative for simplified file handling. ## Key Concepts - **Top-Down vs. Bottom-Up Design** – Bottom-up design creates parts independently and then mates them together; top-down design starts with the assembly framework and builds parts directly into their final spatial context - **In-Context Design** – Referencing geometry (faces, edges, planes) of one component to sketch or build features on another, while working inside the assembly environment - **External Reference** – A parametric link created when a feature or sketch in one part relies on the geometry of a different part in the assembly; if the parent geometry changes, the child geometry updates automatically - **Virtual Component** – A part saved internally within an assembly file rather than as a separate external file on a storage drive ## Detailed Notes ### Edit Part Mode - **Working inside the assembly** requires activating a specific part while the assembly remains open — this is typically called **Edit Part** mode - When a part is activated, the rest of the assembly usually becomes **transparent or changes colour** to visually indicate that only a single component is being modified - While in this mode, you can select **faces, vertices, and planes** from surrounding inactive components to use as references for the active part ### Component Visibility - Assemblies can become cluttered, so effectively managing **visibility** is crucial for top-down design - Components obstructing the view can be **temporarily hidden** to allow clear access to necessary reference geometry - Changing surrounding parts to **wireframe or transparent modes** allows viewing of internal interactions and hidden edges without completely removing parts from view ### In-Context Features - **Geometry dependency** — features such as extrusions, cuts, or holes created on one part can trace or align directly to another part - **Automatic updates** — if a mounting pin on one part is moved, an in-context hole on a dependent part will automatically shift to maintain alignment - **Best practice** — link parts to a **primary master framework** rather than daisy-chaining references across many minor parts, as excessive in-context features can create circular references or slow down assembly calculations ### Inserting a New Component - Instead of opening a new part file, a **new blank part** can be inserted directly into the assembly environment - The first step is usually selecting a **face or plane** on an existing part to place the new component's origin or first sketch plane - This immediately defines the new part's **spatial relationship** to the rest of the assembly ### Understanding External References - Designing parts in the context of an assembly **guarantees proper fitment** between components - If the **parent geometry** (the referenced part) changes, the **child geometry** (the part with the external reference) automatically adjusts to match - **Reusability problem** — inserting a part with external references into a *different* assembly may generate errors or unpredictable behaviour because the original geometric context is missing ### Managing External References - **Listing** — most 3D modelling programs allow users to view a complete list of all external references tied to a specific component, revealing its dependencies - **Locking:** - Temporarily suspends the external reference - The part ignores updates from parent geometry while locked - Can be unlocked later to restore dynamic updating - **Breaking:** - Permanently severs the parametric link between parts - Once broken, the reference **cannot be re-established automatically** - The part maintains its current size and shape but becomes fully independent ### Removing Broken References Completely - When a reference is broken, the sketch or feature relies on geometric anchors that no longer exist, causing the component to become **undefined or under-defined** - **Cleanup process:** 1. Open the component's underlying sketch or feature 2. Identify and delete specific geometric constraints (relations) flagged as broken or missing 3. **Fully define** the geometry independently by applying static dimensions or fixed spatial relations ### Designing Without External References - Many design environments feature a toggle (e.g., "No External References") that **prevents the creation of links** while still allowing in-context design - When activated, the software allows snapping to existing geometry for sizing or placement but records **independent coordinates or static dimensions** rather than establishing a parametric link - **Ideal use case** — designing standard components (like hardware or generic brackets) that must fit the current assembly but are guaranteed to be reused elsewhere ### Virtual Components - Virtual components live **entirely inside** the main assembly file - **Advantages:** - **Simplified file management** — eliminates "missing part" errors when sharing or moving assemblies - **Assembly-specific** — ideal for highly customised parts that will never be used in other projects - **Easy iteration** — copy a virtual component within the assembly to create independent variations without cluttering storage with multiple file versions - **Conversion** — a virtual component can be converted into a standard external component at any time if reuse becomes necessary; conversely, standard components can be internalised into virtual components ## Tables ### Top-Down vs. Bottom-Up Design | Characteristic | Top-Down Design | Bottom-Up Design | | --- | --- | --- | | **Starting Point** | Assembly or layout sketch | Individual part files | | **Component Interactivity** | High — parts drive each other's geometry | Low — parts are isolated until mated | | **Handling Revisions** | Fast — changes propagate automatically | Slow — each part must be updated manually | | **Best Use Case** | Custom machinery, complex housing, tightly integrated systems | Standardised components, hardware, modular designs | ### Managing Links: Lock vs. Break | Action | Description | Reversibility | Best Use Case | | --- | --- | --- | --- | | **Lock** | Temporarily suspends the connection to the parent part | **Reversible** — can be unlocked | Complex assemblies where you want to improve performance or temporarily prevent unwanted updates | | **Break** | Permanently severs the connection to the parent part | **Irreversible** — cannot be undone | Finalising a part for reuse in other assemblies, making it completely independent | ### Component Types: Virtual vs. External | Component Type | Storage Location | Reusability | File Management | | --- | --- | --- | --- | | **Virtual** | Internal — inside the assembly file | Limited to the current assembly | Highly simplified; no separate files to track | | **External** | External — separate file on the drive | Universal; can be used in any number of assemblies | Requires careful tracking of file paths and references | ## Diagrams ### Top-Down Design Workflow ```mermaid flowchart TD A[Start Top-Down Design] --> B[Create or Open Main Assembly] B --> C[Insert New Blank Component] C --> D[Enter Edit Part Mode] D --> E[Select Face on Existing Part as Reference] E --> F[Sketch and Extrude New Feature] F --> G{Changes Required?} G -->|Yes — modify parent part| H[Parent Geometry Adjusts] H --> I[Child Feature Updates Automatically] I --> G G -->|No| J[Exit Edit Part Mode / Complete] ``` ### Removing External References Process ```mermaid flowchart TD A[Review Part Dependencies] --> B{Are dynamic updates still needed?} B -->|Yes| C[Lock External References Temporarily] B -->|No| D[Break External References Permanently] D --> E[Open Component Sketch or Feature] E --> F[Delete Broken Relational Constraints] F --> G[Apply Independent Dimensions] G --> H[Geometry is Fully Defined and Independent] ``` ### External Reference Management Decision Map ```mermaid flowchart TD A[Part Has External References] --> B{Will part be reused in other assemblies?} B -->|No| C[Keep References Active] C --> D[Benefits: Automatic updates maintained] B -->|Yes| E{Need to restore link later?} E -->|Yes| F[Lock References] F --> G[Unlock when ready to resume updates] E -->|No| H[Break References] H --> I[Clean up broken constraints] I --> J[Apply static dimensions] J --> K[Part is fully independent and reusable] ``` ### Virtual vs. External Component Decision ```mermaid flowchart TD A[Creating a New Component] --> B{Will this part be reused in other assemblies?} B -->|Yes| C[Create as External Component] C --> D[Stored as separate file on drive] B -->|No| E[Create as Virtual Component] E --> F[Stored internally in assembly file] F --> G{Reuse needed later?} G -->|Yes| H[Convert Virtual to External] G -->|No| I[Keep as Virtual — simplified management] ``` ## Key Terms - **Parametric Modeling** – A design approach where features are controlled by variables and parameters, allowing easy dimension changes and design iteration - **Edit Part Mode** – A state within an assembly workspace where a single part is isolated for modification while surrounding parts remain visible for reference - **External Reference** – A geometric link between two separate files (a parent part and a child part) created during in-context design - **Parent/Child Relationship** – A dependency where the child feature or part relies on the parent feature or part for its definition - **Locking** – Temporarily suspending parametric links between parts; reversible at any time - **Breaking** – Permanently severing parametric links between parts; irreversible once completed - **Fully Defined** – A state where a sketch or part has all necessary dimensions and constraints, requiring no external input to determine its shape or size - **Virtual Component** – A component whose file data is stored entirely within the host assembly file, simplifying file management - **In-Context Feature** – A feature created on one part that references the geometry of another part within the assembly environment ## Quick Revision - **Top-down design** builds parts within the context of the assembly, contrasting with bottom-up design where parts are made in isolation first - **Edit Part mode** allows modification of one part while viewing the whole assembly for spatial reference - **Component visibility** management (transparency, hiding, wireframe) is essential for accessing reference geometry clearly - **In-context features** automatically update when their referenced parent geometry changes - **External references** dynamically link parts but can cause errors when parts are reused in different assemblies - References can be **listed** (to audit dependencies), **locked** (temporarily suspended, reversible), or **broken** (permanently severed, irreversible) - **Breaking** a reference requires manually deleting broken relations and applying independent static dimensions to fully define the part - A **"No External References" toggle** allows in-context design without creating parametric links — ideal for reusable standard parts - **Virtual components** are saved internally within the assembly file, simplifying file management and preventing lost-file errors - Virtual components can be **converted to external** files later if reuse is required, and vice versa