Skip to main content

Project Structure

Folder Hierarchy

Create a consistent folder structure at the start of each project. This makes it easier to find and manage components as your project grows.

Naming Conventions

Components

Follow a clear naming pattern:
Examples:
  • BASE_Platform_v1
  • FEATURE_MountingHole_M6
  • ASSY_TopModule_Final

Features

Use descriptive, consistent names:

Version Control

Component Versions

Track changes systematically:
  1. Use version numbers (v1, v2, v3)
  2. Add date stamps when needed
  3. Keep notes on major changes

Model Tree Organization

Structure

Reference Geometry

Keep construction elements organized:
  • Named reference planes
  • Center axes
  • Construction sketches

Best Practices

1. Component Management

  • Group related components
  • Use subfolders for complex assemblies
  • Keep reference geometry separate

2. Feature Organization

  • Order features logically
  • Group related operations
  • Name patterns clearly

3. Assembly Structure

Working with Teams

Shared Components

  • Use clear component names
  • Document dependencies
  • Note any constraints

Collaboration Tips

  1. Standard Naming
    • Follow team conventions
    • Use clear descriptions
    • Include version numbers
  2. Documentation
    • Add comments to complex features
    • Note design intentions
    • Document dependencies
Consistent organization is key for team projects. Establish standards early and document any deviations.

Project Management

File Organization

Design States

Track model status:
  • WIP (Work in Progress)
  • REVIEW (Under Review)
  • APPROVED (Final Version)
  • DEPRECATED (Obsolete)

Tips for Success

Regular Cleanup

Remove unused features and organize regularly

Clear Hierarchy

Maintain logical structure from start

Version Control

Track changes and maintain history

Documentation

Keep notes on important decisions

Common Mistakes to Avoid

  1. Inconsistent Naming
    • Mixed conventions
    • Unclear descriptions
    • Missing versions
  2. Poor Structure
    • Deep nested folders
    • Unclear hierarchies
    • Mixed component types
  3. Lack of Documentation
    • Missing change notes
    • Undefined references
    • Unclear dependencies
Take time to organize at the start of each project. Good organization saves time and reduces errors in the long run.
Remember that organization is an ongoing process. Regular maintenance keeps your projects manageable as they grow in complexity.