Understanding Modular Variant of Structure in Teamcenter
Modular variant of structure
Modules are self-contained, plug compatible units that can be reused in the structure. That means each module in the structure is independent of other modules. Options and associated logic of modules are placed on module item and not on top-level item as was the case with classic variant. To load the component, variant condition on it makes references only to parent module .So, in a structure, if one module is restructured or replaced with any other module, it does not affect the rest of the structure. To design a product, these modules needs to be linked to each other and variant data needs to be propagated(not set) up and down the structure, so that end user can set the options on modules on lower level from top level assembly.
Modular Variant Example
Let’s take an example of a bicycle to demonstrate modular variants in the structure. A quick overview of a bicycle structure and its terminology is as follows: ...
button on the toolbar or choose Tools→Variant Rule. 
on the incremental change toolbar to create an incremental change. Effectivity data will not be set without releasing incremental change (manually or through release status defined in preference)
on the incremental change toolbar to set active incremental change. All the edits will be made in context of this active incremental change. 
