Assembly configurations in Solidworks - Real Business Scenario

Scenario Mode

👤 Your Role: You are a product design analyst at a manufacturing company.

📋 Request: Your manager wants a report showing how different assembly configurations affect the total cost and weight of the product.

📊 Data: You have data on various assembly configurations, including the number of parts, cost per part, and weight per part for each configuration.

🎯 Deliverable: Create a dashboard that compares total cost and total weight for each assembly configuration to help the manager decide the best option.

Sample Data

Configuration	Number of Parts	Cost per Part ($)	Weight per Part (kg)
Config A	10	15	2
Config B	8	18	2.5
Config C	12	14	1.8
Config D	9	16	2.2
Config E	11	15	2.1

1

Step 1: Calculate total cost for each configuration by multiplying Number of Parts by Cost per Part.

Total Cost = Number of Parts * Cost per Part

Expected Result

Config A: $150, Config B: $144, Config C: $168, Config D: $144, Config E: $165

2

Step 2: Calculate total weight for each configuration by multiplying Number of Parts by Weight per Part.

Total Weight = Number of Parts * Weight per Part

Expected Result

Config A: 20 kg, Config B: 20 kg, Config C: 21.6 kg, Config D: 19.8 kg, Config E: 23.1 kg

3

Step 3: Create a table showing Configuration, Total Cost, and Total Weight.

Table columns: Configuration, Total Cost, Total Weight

Expected Result

Table with all configurations and their total cost and weight values.

4

Step 4: Build a bar chart comparing Total Cost across configurations.

X-axis: Configuration, Y-axis: Total Cost

Expected Result

Bar chart showing costs: Config C highest, Config B and D lowest.

5

Step 5: Build a bar chart comparing Total Weight across configurations.

X-axis: Configuration, Y-axis: Total Weight

Expected Result

Bar chart showing weights: Config E highest, Config D lowest.

6

Step 6: Combine the two bar charts into a dashboard for side-by-side comparison.

Dashboard layout: Two bar charts side by side with clear labels and legends.

Expected Result

Dashboard showing cost and weight comparison for all configurations.

Final Result

Bar Chart: Total Cost

↓

Bar Chart: Total Weight

✓Config C has the highest total cost and a relatively high weight.

✓Config E has the highest total weight but a slightly lower cost than Config C.

✓Config B and Config D have the lowest total cost but differ in weight.

✓Config D has the lowest total weight among all configurations.

Bonus Challenge

Add a calculated metric for cost per kilogram for each configuration and include it in the dashboard.

Show Hint

Calculate Cost per Kilogram = Total Cost / Total Weight, then add a new bar chart or table column.

Practice

1. What is the main purpose of assembly configurations in SolidWorks?

easy

A. To export assemblies to different file formats

B. To simulate motion of parts in an assembly

C. To create multiple versions of an assembly within a single file

D. To generate 2D drawings from 3D models

Solution

1. Step 1: Understand the concept of assembly configurations

   Assembly configurations allow you to have different versions of the same assembly in one file.

2. Step 2: Compare options given

   Exporting assemblies to different file formats, simulating motion of parts in an assembly, and generating 2D drawings from 3D models describe other features of SolidWorks, not assembly configurations.

3. Final Answer:

   To create multiple versions of an assembly within a single file -> Option C

4. Quick Check:

   Assembly configurations = multiple versions in one file [OK]

Hint: Think: one file, many assembly versions [OK]

Common Mistakes:

• Confusing configurations with exporting files
• Mixing up assembly motion simulation with configurations
• Thinking configurations generate drawings

2. Which of the following is the correct way to create a new assembly configuration in SolidWorks?

easy

A. Click 'File' > 'Export' > 'New Configuration'

B. Use the 'Save As' command to save a new file

C. Drag and drop parts into the assembly window

D. Right-click the assembly name in the ConfigurationManager and select 'Add Configuration'

Solution

1. Step 1: Identify how to add configurations

   In SolidWorks, new configurations are added via the ConfigurationManager by right-clicking the assembly name.

2. Step 2: Eliminate incorrect options

   Using the 'Save As' command to save a new file, dragging and dropping parts into the assembly window, and clicking 'File' > 'Export' > 'New Configuration' describe unrelated actions.

3. Final Answer:

   Right-click the assembly name in the ConfigurationManager and select 'Add Configuration' -> Option D

4. Quick Check:

   Add configuration = right-click in ConfigurationManager [OK]

Hint: Right-click assembly in ConfigurationManager to add configs [OK]

Common Mistakes:

• Trying to create configurations by saving new files
• Confusing part insertion with configuration creation
• Looking for configuration options under export

3. Given an assembly with two configurations: Config1 where Part A is visible and Config2 where Part A is hidden, what will happen if you switch from Config1 to Config2?

medium

A. Part A will remain visible in both configurations

B. Part A will be hidden in Config2 but visible in Config1

C. Part A will be deleted from the assembly

D. The assembly will crash due to conflicting configurations

Solution

1. Step 1: Understand visibility control in configurations

   Configurations can control part visibility independently, so Part A can be visible in one and hidden in another.

2. Step 2: Analyze the effect of switching configurations

   Switching to Config2 hides Part A, but Config1 keeps it visible; no deletion or crash occurs.

3. Final Answer:

   Part A will be hidden in Config2 but visible in Config1 -> Option B

4. Quick Check:

   Visibility changes per configuration = Part A hidden in Config2 [OK]

Hint: Visibility can differ per configuration [OK]

Common Mistakes:

• Assuming parts get deleted when hidden
• Thinking visibility is global, not per configuration
• Believing conflicting configs cause crashes

4. You created a new assembly configuration but notice that changes to part positions are not saved when switching configurations. What is the most likely cause?

medium

A. Part positions are not set to vary between configurations

B. The assembly file is corrupted

C. You forgot to save the assembly file

D. Configurations only control part visibility, not position

Solution

1. Step 1: Understand configuration control over part properties

   Configurations can control part visibility, size, and position if set to vary.

2. Step 2: Identify why position changes are not saved

   If part positions are not set to vary, changes won't be saved per configuration.

3. Final Answer:

   Part positions are not set to vary between configurations -> Option A

4. Quick Check:

   Positions must vary to save changes per config [OK]

Hint: Enable 'vary' for part positions to save changes [OK]

Common Mistakes:

• Assuming file corruption causes this
• Forgetting to save the file
• Believing configurations can't control position

5. You want to create an assembly with three configurations: Default, Compact, and Extended. In Compact, some parts are hidden and others moved closer. In Extended, all parts are visible but some are repositioned. Which approach correctly manages these configurations?

hard

A. Use assembly configurations to control part visibility and position for each version

B. Create separate assembly files for each version to avoid confusion

C. Use part configurations inside each part instead of assembly configurations

D. Only change part colors to differentiate versions

Solution

1. Step 1: Analyze requirements for multiple versions

   You need to control visibility and position differently in each configuration.

2. Step 2: Match approach to requirements

   Assembly configurations allow controlling visibility and position per version in one file, fitting the need.

3. Step 3: Eliminate other options

   Separate files increase management effort; part configurations control part internal states, not assembly layout; color changes don't affect visibility or position.

4. Final Answer:

   Use assembly configurations to control part visibility and position for each version -> Option A

5. Quick Check:

   Assembly configs control visibility & position per version [OK]

Hint: Use assembly configs to vary visibility and position per version [OK]

Common Mistakes:

• Creating multiple files instead of configurations
• Using part configs for assembly layout changes
• Relying on color changes only