Revising allocations

Allocations do not depend on a particular revision of an item. The allocation exists between the representation of the source item in the source structure and the target item in the target structure. The target item is not a specific revision because all revisions of an item are (by definition) compatible in form, fit, and function. For example, if a source item is revised from revision A to revision B, you can optionally use the same allocations between revision B and the target. To do this, the administrator can configure the system so that, when the allocation map is revised at the same time as the item, all the allocations are carried forward.

For example, allocation A2 assigned to allocation map revision XYZ/A has the function Ignite Air Fuel Mix in the functional view, which is allocated to the Ignition Coil and Spark Plugs components in the assembly view.

When you revise allocation map AllocMapRev_XYZ/A to AllocMapRev_XYZ/B, Teamcenter optionally copies the entire set of allocations to the new revision. You can then edit the existing allocations, add new allocations or delete selected allocations.

In this kind of example, allocation A2 could be edited with respect to the target structure, and reallocated to the ignition coil and a resistor. Similarly, revision B could include a new allocation between the functional component Generate Torque and the physical component Drive Belt.

Note

By default, Teamcenter does not carry forward allocations when you revise an allocation map. To configure this behavior, your administrator sets the necessary preference.

You can delete the source or target of an allocation (or both) and Teamcenter does not delete the allocation itself. If appropriate, you can make a new assignment to replace the deleted source or target.

If appropriate, you can manage changes to allocation with incremental changes. Allocations may be added to or removed from an allocation map in the context of a specified incremental change order.