Large CAD Assemblies: Planning, Data and Performance

Overview

Large assembly projects (thousands of parts, multiple engineers) fail most often due to lack of upfront planning — not lack of engineering skill. File management, naming conventions, revision control, and assembly strategy must be decided before the first part is created. The cost of planning is typically a small fraction (~10%) of the cost of recovering from unplanned chaos.

Key Concepts

• Skeleton Model Technique – a single reference part containing key geometry that all components reference (hub-and-spoke)
• Master Model Technique – a complex surface/solid body from which multiple child components are derived
• Product Data Management (PDM) – software systems that control file versioning, check-in/check-out, and reference tracking
• In-Context References – geometry in one part driven by geometry of another part within an assembly context
• Single-Point Database – each piece of information stored in one file only; other files reference it via external links

Common Failure Modes in Unplanned Assemblies

• Broken external references from moved files (absolute paths invalidated)
• Lost work from uncontrolled overwrites (no check-in/check-out)
• Duplicate parts with conflicting dimensions (no naming convention)
• Inability to generate accurate Bills of Materials (no custom properties)
• Cascading project delays and contractual penalties

Assembly Modelling Techniques

Skeleton Model Technique

• A single part file containing only key geometry: interfaces, mounting locations, spatial envelopes, critical dimensions
• All components reference the skeleton — not each other
• Creates a hub-and-spoke reference structure
• Best for: industrial machinery, plant layout, equipment with many mechanical interfaces
• Advantages: centralized change propagation, independent sub-assembly work, low circular reference risk

Master Model Technique

• A single master part with complex surfaces/solid bodies from which multiple child components derive
• Results in many multi-body parts
• Best for: consumer products, duct systems, automotive body panels, organic/complex shapes
• Advantages: surfaces created once and shared, automatic updates to derived components

Technique Selection Framework

Part Numbering Approaches

Intelligent Numbering

• Part number encodes information: project code, assembly zone, part type, sequence
• Example format: [Project]-[Zone]-[Type]-[Seq]
• Pros: identifiable without opening files, natural grouping, aids communication
• Cons: requires upfront scheme design, conflicts when parts move between zones, can become overly complex

Non-Intelligent (Sequential) Numbering

• Each part gets the next available number — carries no descriptive meaning
• All context stored in custom properties and metadata
• Pros: simple, no renumbering needed, no classification debates
• Cons: meaningless without a database/PDM, harder to identify at a glance

Revision Scheme Best Practices

• Use alphabetical for major revisions, numerical for minor
• Track revisions via custom properties or PDM metadata — never in the file name
• Embedding revision in file names creates separate files, breaking all existing assembly references
• Define clear triggers for what constitutes a new revision before the project starts
• Establish an approval process (self, peer, or formal workflow) based on project requirements

In-Context Reference Management

Reference Hierarchy (safest → most dangerous):

1. Part → Skeleton ✅ Ideal
2. Part → Master Model ✅ Good
3. Part → Part (same sub-assembly) ⚠️ Acceptable if documented
4. Part → Part (cross sub-assembly) ⚠️ Extreme caution
5. Circular (A → B → A) ❌ Never acceptable

Four Pillars of Strategy Implementation

Pillar 1: Document the Approach

• Write down all procedures: naming, revision scheme, assembly technique, reference rules, templates, storage, workflows
• Undocumented procedures mutate, get forgotten, and disappear
• Documentation time is a fraction of the time to fix problems caused by missing procedures

Pillar 2: Make It Accessible

• Store procedures on a shared location (intranet, common drive)
• Maintain a single source of truth — one location, one version
• Include quick-reference cards for daily workflows
• Make documentation searchable

Pillar 3: Communicate Continuously

• Discuss procedures at every planning meeting
• Address deviations immediately and constructively
• Celebrate system wins to reinforce compliance

Pillar 4: Standardize Templates and Settings

• Part template: custom properties, material defaults, unit system pre-configured
• Assembly template: BOM structure settings, display states
• Drawing template: title block linked to custom properties, standard views, dimension styles
• Embedding required fields in templates ensures engineers cannot forget mandatory metadata

Essential Custom Properties for Every Part

Why custom properties matter:

• Feed directly into Bills of Materials (no manual BOM creation)
• Serve as search criteria in PDM systems
• Enable advanced selection filtering in assemblies
• Can trigger workflow transitions automatically

System-Level Performance Settings

File Management Fundamentals

Single-Point Database Concept

• Information stored in one file only; other files reference it
• References use absolute paths — if a file moves, the reference breaks
• No reverse file pointers by default (a component does not know which assemblies use it)
• PDM systems solve this via a relational database tracking both directions ("where used" capability)

Manual Data Management Methods (and Why They Fail)

Product Data Management (PDM)

Core Functions

1. Search and find referenced files by properties/relationships
2. BOM generation and "where used" tracking (forward and reverse references)
3. Collaboration and change control via check-in/check-out and workflows
4. Revision history and secure vault storage with full rollback capability

Workgroup vs. Enterprise PDM

PDM Daily Workflow

1. Search vault for file (by part number, description, or any property)
2. Check out file → copied to local cache; locked in vault
3. Edit locally → fast performance, no network latency
4. Check in → new version saved; previous version preserved; change logged; file unlocked
5. Notifications sent → engineers with referencing assemblies are alerted

Complete Pre-Project Planning Checklist

Phase 1: Pre-Design Planning

1. Estimate assembly size and composition
2. Choose assembly technique (skeleton or master model)
3. Define naming convention (intelligent or sequential)
4. Establish revision scheme and triggers
5. Define in-context reference rules and maximum depth
6. Select data management method (PDM level)
7. Define document workflow (states, transitions, approvers)
8. Create custom property list for parts, assemblies, drawings

Phase 2: Infrastructure Setup

9. Create standardized part template with all custom properties
10. Create standardized assembly template with BOM settings
11. Create standardized drawing template with auto-populating title block
12. Configure PDM vault structure (folders, permissions, workflows)
13. Define system-level performance settings for all workstations
14. Build skeleton model or master model
15. Validate templates and model with a test sub-assembly

Phase 3: Documentation and Communication

16. Write procedures document covering all Phase 1 decisions
17. Create quick-reference cards for daily workflows
18. Publish documentation to shared location
19. Conduct team kickoff meeting to review procedures
20. Schedule regular check-ins for questions and deviations

Phase 4: Ongoing Enforcement

21. Monitor compliance with naming conventions and property completion
22. Review in-context references periodically for unplanned cross-references
23. Audit vault for orphaned files, duplicates, or broken references
24. Update procedures as lessons are learned
25. Onboard new team members using documentation (not tribal knowledge)

Diagrams

Assembly Technique Selection

flowchart TD
    A[New Large Assembly Project] --> B{Primary Geometry Type?}
    B -->|Interfaces, Envelopes, Datums| C[Skeleton Model Technique]
    B -->|Complex Surfaces, Organic Forms| D[Master Model Technique]
    C --> E[Hub-and-Spoke References]
    D --> F[Parent-Child Derived Parts]
    E --> G[Independent Sub-Assembly Work]
    F --> H[Shared Surface Updates]

In-Context Reference Hierarchy

flowchart TD
    A[In-Context Reference Choices] --> B["Part → Skeleton ✅ Ideal"]
    A --> C["Part → Master Model ✅ Good"]
    A --> D["Part → Part Same Sub ⚠️ Caution"]
    A --> E["Part → Part Cross Sub ⚠️ High Risk"]
    A --> F["Circular A → B → A ❌ Never"]

PDM Check-Out / Check-In Workflow

flowchart TD
    A[Search Vault] --> B[Check Out File]
    B --> C[File Copied to Local Cache]
    B --> D[File Locked in Vault]
    C --> E[Edit Locally]
    E --> F[Check In File]
    F --> G[New Version Saved to Vault]
    F --> H[Previous Version Preserved]
    F --> I[Change Log Updated]
    F --> J[File Unlocked]
    J --> K[Notifications Sent to Referencing Engineers]

Project Planning Phases

flowchart LR
    A[Phase 1: Pre-Design Planning] --> B[Phase 2: Infrastructure Setup]
    B --> C[Phase 3: Documentation & Communication]
    C --> D[Phase 4: Ongoing Enforcement]

Key Terms

• Skeleton Model – a single reference part containing key assembly geometry; all components reference it instead of each other
• Master Model – a part with complex surfaces/bodies from which multiple child components derive their geometry
• PDM (Product Data Management) – software that manages file versioning, access control, and reference tracking for engineering data
• In-Context Reference – a geometric relationship created between parts within the context of an assembly
• Single-Point Database – architecture where each piece of data exists in one file only; others reference it
• Absolute Path – a complete file location path; breaks if the file is moved
• Check-In / Check-Out – a PDM mechanism that locks files during editing to prevent concurrent overwrites
• Where Used – a PDM query showing all assemblies that reference a given component
• Custom Properties – metadata fields embedded in part files (e.g., material, revision, cost) that drive BOMs and searches
• BOM (Bill of Materials) – a structured list of all components in an assembly, generated from custom properties
• Vault Replication – synchronising a PDM vault across multiple physical locations for distributed teams
• Intelligent Numbering – a part numbering scheme where the number itself encodes information (project, zone, type)
• Non-Intelligent Numbering – sequential numbering where the part number is a unique ID only; all context lives in metadata

Quick Revision

• Plan before modelling — the cost of planning is ~10% of the cost of recovering from unplanned chaos
• Choose your assembly technique (skeleton vs. master model) before creating the first part
• Never embed revisions in file names — use custom properties or PDM metadata to track revisions
• Keep in-context references in a hub-and-spoke pattern; never allow circular references
• Custom properties are the foundation for automated BOMs, PDM search, and workflow triggers
• PDM systems prevent overwrites, track versions, and provide "where used" capabilities that manual methods cannot
• Enterprise PDM adds vault replication, multiple workflows, SQL search, and change notifications over workgroup-level PDM
• Standardised templates eliminate repetitive setup work and ensure every file starts with required metadata
• Document all procedures, store them in a single accessible location, and enforce them continuously
• Onboard new team members from documentation — not tribal knowledge

Overview

CAD software performance can be significantly improved by adjusting system options, document properties, and operating system settings. There is no universal configuration — optimal settings depend on hardware capability and project complexity. Performance gains often trade off against visual quality, so each setting should be understood before being changed. Settings fall into two categories: system options (apply globally) and document properties (apply per-document via templates).

Key Concepts

• System Options — global settings that affect the entire CAD environment regardless of which file is open; not saved with individual documents
• Document Properties — per-file settings controlled by templates; must be configured in templates to apply to future files
• Large Assembly Mode — an automatic performance mode that disables resource-heavy features when component count exceeds a threshold
• Tessellation — the process of approximating curved surfaces with triangles for shaded display; higher tessellation = smoother visuals but slower performance
• Lightweight Components — components loaded with minimal data to reduce memory and processing overhead
• Freeze Bar — prevents unnecessary rebuilding of features above the bar, saving processing time
• Rebuild Verification — a check that validates each face against all others in a model; thorough but slow

General System Options

• Disable thumbnail graphics in the OS file explorer — generating previews consumes CPU cycles
• Disable news/alert feeds in the welcome dialog — unnecessary network and rendering overhead
• Enable Freeze Bar — prevents automatic rebuilding of frozen features, reducing recalculation time

Drawing Options

• Disable real-time view dragging — clearing "show contents while dragging" eliminates real-time recalculation during view repositioning
• Disable auto-update on open — drawings open faster; views update only on manual rebuild
• Disable auto-hide components on view creation — calculating hidden components is expensive; disabled by default in Large Assembly Mode
• Save tessellation for drawings — reduces file size and data loaded on open, but may cause empty views in view-only or lightweight viewer modes
• Use draft quality for new views — reduces rendering overhead compared to high-quality display
• Use plain backgrounds — movable/gradient backgrounds require recalculation on every viewpoint change
• Set assembly transparency to "Maintain" — avoids intensive recalculation of transparency levels during in-context editing

Default Templates

• Use default templates for auto-generated documents (mirrored parts, new subassemblies) to save time and ensure consistency
• Prompt for template selection only if multiple templates exist for different use cases
• Pre-configuring templates eliminates repetitive setup and ensures correct document properties are applied automatically

Document Properties — Image Quality

• Image quality slider controls tessellation density for shaded display
• Set the slider as far left as tolerable (2–3 ticks from minimum) for best performance
• Moving from low to high can generate ~2,500× more triangles — a massive performance hit
• In assemblies, each component's image quality is controlled by its own document properties
• Use "Apply to all referenced part documents" to normalize resolution across components
• Save tessellation with part document — essential for proper display in viewers and view-only mode; do not clear this option

Add-Ins

• Disable all unused add-ins — each consumes system resources (memory, CPU) even when idle

Assembly Options

• Large Assembly Mode activates automatically when component count exceeds a configurable threshold
• Disables resource-heavy functions to improve responsiveness

• Trade-off of suspended rebuild: errors from sequential changes become harder to isolate since feedback is deferred

External References

Performance Options

• Verification on rebuild — checks every face against all other faces in the model
  • Recommended workflow: leave OFF during normal work → periodically enable and force a full rebuild (Ctrl+Q equivalent) to validate geometry → disable again
• Transparency quality — lower quality for both static and dynamic views improves speed during panning/rotating
• Level of detail slider — move to far right; simplifies small components to blocks during movement, restoring detail when movement stops
• Lightweight component loading — enable if working below the large assembly threshold with few active components
• Always resolve sub-assemblies — keep unchecked; auto-resolving removes lightweight loading benefits
• Check out-of-date lightweight components — set to "Indicate" to flag stale components without auto-resolving
• Resolve lightweight components — set to "Always" only when tasks require fully resolved geometry
• Rebuild assembly on load — set to "Always" to avoid working on outdated geometry
• Mate animation speed — turn OFF to skip intermediate position calculations
• Software rendering fallback — enable only if hardware graphics acceleration is unsupported; software rendering degrades with assembly size

View Options

• Turn off view transitions — calculating intermediate positions and transparencies consumes processing power better used for modelling
• Auto-recover — recommended OFF if you save frequently; auto-saving large files can interrupt workflow at inconvenient times
• File Explorer locations — select only frequently used locations; unnecessary locations are read and populated each time the tab opens

Search & Indexing

• Set indexing to idle time only — prevents background indexing from competing with active design work for CPU resources
• Schedule any disk maintenance tasks (defragmentation, etc.) for non-working hours

Operating System Optimization

• Disable visual enhancements — features like transparency effects, font smoothing, pointer shadows, and cascading menu animations consume GPU/CPU resources
• Set system performance mode to "Adjust for best performance" rather than appearance
• General rule: if a setting improves how the display looks, it is consuming resources that could be used for CAD performance

System Maintenance

• Defragment hard drives regularly — contiguous data sectors enable faster file loading
• Clear temporary and backup files — frees storage space and prevents conflicts with programs writing temp data
• Uninstall unused applications — especially those that load at startup and consume background resources
• Clean the system registry — uninstalled programs may leave orphaned entries that degrade performance
• Stay current with service packs — review release notes before installing to verify relevance to your issues

Resource Management

• Close all unnecessary programs while working in CAD — other applications consume RAM, disk I/O, and CPU
• Virus protection configuration:
  • Scheduled scans — set to run outside working hours
  • On-demand scans — manually triggered, no passive impact
  • Real-time scans — can significantly slow down work when many files are accessed simultaneously; configure exclusions for CAD working directories if possible

Built-In Diagnostic Tools

• Diagnostics tab — examines system configuration and CAD settings, highlighting issues that need correction
• System Maintenance tab — consolidates cleanup tasks: clearing temp files from multiple locations, running disk checks and defragmentation
  • Can run immediately, at a scheduled time, or on a recurring schedule
  • Further scheduling refinements possible through OS task scheduler

Saving & Backing Up Settings

• System options — export as registry backup files using the settings wizard; covers options, keyboard shortcuts, menu customization, and toolbar layout
• Document properties — stored within template files; invest time creating comprehensive templates with all required settings, reference geometry, custom properties, and start geometry to eliminate repetitive setup

Performance Impact Summary

Rebuild Verification Workflow

System Options vs Document Properties

graph TD
    A[CAD Settings] --> B[System Options]
    A --> C[Document Properties]
    B --> D[Apply globally to all files]
    B --> E[Saved in system registry]
    B --> F[Backed up via settings wizard]
    C --> G[Apply per-document only]
    C --> H[Controlled by templates]
    C --> I[Backed up by saving templates]

Performance Optimization Workflow

flowchart TD
    A[Start: Assess Current Performance] --> B[Run Built-In Diagnostics]
    B --> C[Fix Highlighted Issues]
    C --> D[Configure System Options]
    D --> D1[Disable thumbnails & news feeds]
    D --> D2[Enable Freeze Bar]
    D --> D3[Configure Large Assembly Mode]
    D --> D4[Disable unused add-ins]
    D --> D5[Set view transitions to OFF]
    C --> E[Configure Document Properties]
    E --> E1[Lower image quality slider]
    E --> E2[Save tessellation with parts]
    E --> E3[Use draft quality for drawings]
    C --> F[Optimize Operating System]
    F --> F1[Adjust for best performance]
    F --> F2[Schedule scans & indexing off-hours]
    F --> F3[Run system maintenance]
    D1 & D2 & D3 & D4 & D5 --> G[Save Settings Backup]
    E1 & E2 & E3 --> G
    F1 & F2 & F3 --> G
    G --> H[Improved CAD Performance]

Large Assembly Mode Decision Tree

flowchart TD
    A[Opening an Assembly] --> B{Component count > threshold?}
    B -->|Yes| C[Large Assembly Mode activates]
    B -->|No| D[Normal mode]
    C --> E[Hide planes, axes, annotations]
    C --> F[Disable edge display in shaded mode]
    C --> G[Suspend automatic rebuild]
    C --> H{Component count > design review threshold?}
    H -->|Yes| I[Use Large Design Review mode]
    H -->|No| J[Continue in Large Assembly Mode]
    D --> K{Performance acceptable?}
    K -->|Yes| L[Work normally]
    K -->|No| M[Manually enable performance settings]

Virus Protection Strategy

flowchart LR
    A[Virus Protection] --> B[Scheduled Scans]
    A --> C[On-Demand Scans]
    A --> D[Real-Time Scans]
    B --> E[Run outside working hours]
    C --> F[Manual trigger as needed]
    D --> G[Can slow large file operations]
    G --> H[Configure exclusions for CAD directories]

Key Terms

• Tessellation — approximation of curved surfaces using triangles for rendering; higher density = smoother appearance but heavier computation
• Large Assembly Mode — performance mode that auto-disables resource-intensive features when component count exceeds a set threshold
• Lightweight Components — components loaded with reduced data to minimize memory and processing requirements
• Freeze Bar — a boundary in the feature tree; features above it are not rebuilt, saving processing time
• Rebuild Verification — a thorough check that validates each model face against all others to detect geometry errors
• Level of Detail — a setting controlling how much geometric simplification occurs during dynamic view manipulation
• Real-Time Scanning — antivirus method that checks files as they are accessed; can degrade performance when many files are in use
• Defragmentation — reorganization of disk storage so files occupy contiguous sectors, improving read/write speed
• Document Template — a pre-configured file that defines default document properties, geometry, and custom settings for new files
• Settings Wizard — a utility for exporting and importing system-level configuration as backup files

Quick Revision

• Lower the image quality slider as far as tolerable — high settings generate up to 2,500× more rendering triangles
• Enable Large Assembly Mode with an appropriate component threshold to auto-disable expensive features
• Disable all unused add-ins — each one consumes resources even when idle
• Turn off view transitions and mate animations — they waste processing power on non-essential visual calculations
• Set external references to read-only and disable file location searches to speed up file open/save times
• Enable Freeze Bar to prevent unnecessary feature rebuilds
• Run rebuild verification periodically (not constantly) — enable, force rebuild, then disable
• Configure the OS for best performance over appearance and schedule maintenance tasks outside working hours
• Close all non-essential programs while working in CAD to free RAM, CPU, and disk I/O
• Back up system options via settings wizard and maintain well-configured document templates to preserve and reuse optimized settings

Overview

A large assembly in CAD software is not defined by component count or physical size alone. It is defined by its impact on system resources and productivity. Performance degradation in large assemblies is primarily caused by poor modelling practices rather than hardware or software limitations, making design strategy the most critical factor in managing assembly performance.

Key Concepts

• Large Assembly – any assembly that consumes all available system resources and reduces design productivity
• Performance Bottleneck – the combination of modelling habits, file management, and system configuration that causes slow performance
• Best Design Practice – a set of modelling, assembly, and data management strategies that minimise performance loss
• Simplified Representation – reduced-detail versions of components used to lower memory and processing demands

What Makes an Assembly "Large"

• Not defined by component count or physical dimensions
• Defined by two primary characteristics:
  • Consumes all system resources (memory, CPU, GPU)
  • Hurts productivity (slow operations, long wait times)

Traits of Large Assemblies

Physically Large

• Requires layout planning or engineering input to position all components
• Contains so many components that management, calculation, and memory demands reduce productivity

Complex

• Contains many parametric relationships between parts
• Has a large number of mates/constraints
• Taxes computing resources beyond comfortable limits
• Includes many different component types requiring active management
• Contains imported data that must be located and loaded at runtime
• Features geometric complexity that is difficult and slow to rebuild

Multi-Discipline / Multi-Source

• Assemblies often span multiple systems and data sources:

Where Performance Degrades

• Opening, closing, and saving files
• Rebuild/regeneration time
• Drawing creation and updates
• Rotating, panning, and zooming
• Inserting new components
• Switching between part, assembly, and drawing environments
• Adding or editing mates/constraints

Root Cause of Performance Issues

• ~80% of performance problems are under user control
  • Poor software setup and data management options
  • Failure to plan work efficiently
  • Suboptimal modelling practices
• ~20% of performance problems are under software control
  • Bugs, algorithm efficiency, internal code
• Hardware upgrades alone will not solve performance issues caused by poor modelling practices
• Slower assemblies are an accumulation of many small problems — there is no single quick fix

Best Design Practices

Effective Part Modelling

• Set a proper origin to simplify placement and mating
• Use simple, easy-to-build features — avoid unnecessarily complex geometry
• Remove in-context relationships where possible to reduce dependency chains
• Eliminate circular references between features or parts
• Create simplified versions of parts for use in large assemblies

Effective Assembly Modelling

• Organise components into logical subassemblies
• Use the proper level of detail for the task at hand
• Apply proper mates/constraints — avoid over-constraining or redundant mates

Reducing Memory Load

Data Sharing Best Practices

• Ensure all team members have access to necessary files
• Always work with the most current version of each file
• Make changes to files with responsibility and traceability
• Protect files from accidental overwrites by unauthorised users

File Management Considerations

• All project team members must have appropriate file access
• Protect files from accidental overwriting by non-team members
• Ensure file properties and metadata are filled in correctly

Avoiding Common Pitfalls

• Inability to locate files — use structured folder conventions or a data management system
• Working on the wrong version — enforce version control practices
• Modelling problems — follow best practice guidelines from the start
• Hardware problems — use certified or recommended hardware configurations
• Network problems — ensure reliable access to shared file locations

Producing Parts, Assemblies, and Drawings Efficiently

• Use in-context features only where appropriate during initial design
• Break in-context relationships once the design stabilises
• Share data between engineering, manufacturing, and design teams seamlessly
• Limit configurations to two or three per component where possible
• Design simplified parts to reduce rebuild overhead
• Use neutral-format bodies or simplified representations for library or purchased parts

Large Assembly Performance Factor Breakdown

pie title Root Cause of Performance Issues
    "User-Controlled Factors" : 80
    "Software-Controlled Factors" : 20

Best Practice Workflow for Large Assembly Design

flowchart TD
    A[Plan Assembly Structure] --> B[Design Simplified Parts]
    B --> C[Set Proper Origins & Easy Features]
    C --> D[Organise into Subassemblies]
    D --> E[Apply Proper Mates/Constraints]
    E --> F[Use Lightweight/Simplified Modes]
    F --> G[Implement File & Version Management]
    G --> H[Optimised Large Assembly]

    style A fill:#2a9d8f,color:#fff
    style H fill:#2a9d8f,color:#fff

Three Pillars of Assembly Optimisation

graph TD
    A[Large Assembly Optimisation] --> B[Effective Part Modelling]
    A --> C[Effective Assembly Modelling]
    A --> D[Memory & Data Management]

    B --> B1[Proper origins]
    B --> B2[Simple features]
    B --> B3[Remove in-context refs]
    B --> B4[Simplified versions]

    C --> C1[Subassembly organisation]
    C --> C2[Proper level of detail]
    C --> C3[Clean mates/constraints]

    D --> D1[Lightweight modes]
    D --> D2[Quick open / Design review]
    D --> D3[Version control & file access]

Key Terms

• Large Assembly – an assembly that exhausts system resources and impairs productivity, regardless of component count
• In-Context Relationship – a reference between parts created while editing one part within the context of the assembly; creates dependencies that slow rebuilds
• Circular Reference – a dependency loop where Feature A depends on Feature B, which in turn depends on Feature A; causes rebuild errors and slowdowns
• Lightweight Mode – a display state where components are loaded with graphical data only, without full model information
• Large Design Review – a read-only, resource-efficient mode for viewing large assemblies without loading full model data
• Simplified Configuration – a reduced-detail representation of a part or subassembly used to lower processing demands
• Mate/Constraint – a geometric relationship (coincident, concentric, parallel, etc.) that positions one component relative to another
• Subassembly – a self-contained group of components within a larger assembly, used to organise structure and improve performance
• Parametric Relationship – a dimension- or equation-driven link between features that updates automatically when inputs change
• Neutral-Format Body – a geometry file exported in a non-native format (e.g., STEP, Parasolid) to strip parametric history and reduce complexity

Quick Revision

• A large assembly is defined by its impact on resources and productivity — not by component count
• ~80% of performance issues are caused by user practices; only ~20% are software-related
• Upgrading hardware alone will not fix assemblies slowed by poor modelling habits
• Effective part modelling includes proper origins, simple features, and removing in-context/circular references
• Subassembly organisation and clean mating strategies are essential for assembly performance
• Use lightweight, simplified, and quick-open modes to reduce memory consumption
• File management (version control, access rights, metadata) prevents costly errors in team environments
• Limit configurations to two or three per component to avoid excessive rebuild overhead
• Use simplified or neutral-format parts for library and purchased components
• There is no single quick fix — performance is the result of many accumulated good (or bad) practices