Subassembly Costing

While costing an assembly, you can either use a Flat Tree mode or a Nested Tree mode. You can also cost subassemblies or apply purchased cost to them.

The two modes of Costing are:

Flat Tree

Costs top assemblies without costing subassemblies. The Flat Tree option costs assemblies as per the existing behavior.

Nested Tree

Costs the top assembly and its subassemblies or applies purchased cost to subassemblies.

With assembly costing, you can:

Apply Purchased Cost

You can cost the assembly in Nested Tree mode and apply cost overrides to individual subassemblies by using the option Use Purchased Cost on the shortcut menu. If you apply purchased cost to any subassembly then all components in this subassembly are greyed out in the CostingManager.

Apply component cost changes to multiple instances across the whole assembly.

When you change the cost of a component having multiple instances within or outside of subassemblies, the cost change is applied across all instances in the assembly.

Costing preference. Following is the order of preference for Costing for an uncosted assembly:
  1. Custom property cost. If a custom property cost is defined for a subassembly or component and the custom property is defined in the Costing template, then this cost is considered over the cost defined in the template.
  2. Calculated cost. If both, custom property cost and cost in template are not defined, then the costs are calculated individually. If a subassembly is already saved with Costing data, then saved cost is considered over other type of costs.

Options in CostingManager:

Option Description
Use Cost from Template Applies cost defined in template
Use Purchased Cost Applies cost override on existing cost
Use Custom Property Cost Applies cost defined as a Custom Property.
Use Calculated Cost Applies calculated cost of components and subassemblies