Making allocations between configured structures

You can use configuration management to determine those components that appear in a target structure. When those components are configured, you can determine the allocations that are possible.

You can manage configurations in Teamcenter by placing options and variants on components in the structures. You can then place allocations between the components in the various structures; these allocations have no conditions associated with them. If a source component is configured in, the associated allocations are configured in. If the target component is not configured in, the allocation is not configured in. You can create multiple allocations from one source component to various target components.

In an example structure, components can be either configured in or configured out. Allocations exist between various components, and there are three basic cases:

• Allocation from function 1.1 to part 1.1.1 — Part 1.1.1 is configured out, so the allocation is configured out or invalid.
• Allocation from function 1.2 to part 1.2 — Function 1.2 is configured out, but part 1.2 is configured in. As the source component is configured out, the allocation is configured out as an unused allocation. (The allocation is not evaluated because Teamcenter does not need to look for allocations related to this function.)
• Allocations from function 1.3 to part 1.2.1 and to part 1.2.2 — Part 1.2.1 and part 1.2.2 are variants of each other. Only one part is configured in at any time. The allocation to the part that is configured in is valid, and the allocation to the second part is configured out.