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 |
Cost
the assembly in Nested Tree mode and apply cost overrides to
individual subassemblies
using
the option Use Purchased
Cost.
If you apply purchased cost to
a
subassembly then all components in
the
subassembly are
grayed
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. The order of
preference for Costing for an uncosted assembly is as follows:
- 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.
- Calculated cost. If both
custom property cost and cost
in
the template are not defined, then the costs are calculated
individually. If a subassembly is already saved with Costing data, then the
saved cost is considered over other
types
of costs.
Options in CostingManager:
| Option |
Description |
| Use
Cost from Template |
Applies the cost defined
in
the template |
| Use
Purchased Cost |
Applies the cost override on
existing cost |
| Use
Custom Property Cost |
Applies the cost defined as a
Custom Property. |
| Use
Calculated Cost |
Applies the calculated cost of
components and subassemblies |