Creating allocations

You can create allocations at various levels of a structure, but in each case they specify an object of interest—one that performs a particular function. It is possible that every item revision in a structure could contain an allocation. For example, this may be necessary for manufacturing purposes, where all items must be consumed.

Because allocations are independent of the structures they map, you can create and manage them independent of the structures themselves. For example, a functional designer may design the functional model, whereas a mechanical engineer designs the physical model. When both structures are complete, a systems engineer may map the functional model to the physical model. The systems engineer may trade off studies between allocating functions to different components and perform the actual assignments.

Note

The model is the representation of a particular aspect of the product, not the CAD model. For example, the functional model of a car represents a product containing an air conditioning system, power braking, power steering, and other functionality. In Teamcenter, the model is represented by the product structure.

When you create an allocation, Teamcenter automatically assigns it a unique identifier. The identification scheme is determined by user exits set by the Teamcenter administrator.

Because you can configure structures in Teamcenter, you can create allocations between variable product structures. Allocations are valid only in a particular context and therefore all allocations between two structures are part of a group, and Teamcenter evaluates them as a unit. The allocations tie together various components and revisions of items in the structures.

Optionally, a customizer can create subtypes of allocations and allocation maps using the Business Modeler IDE. The Teamcenter administrator can set preferences that determine the allocation subtypes that are valid in a particular allocation map type and, similarly, the allocation maps that are valid between structure type (BOM view types). The administrator also determines whether each allocation subtype is valid for:

• One source and one target.
• One source and multiple targets.
• Multiple sources and one target.
• Multiple sources and multiple targets.