A QUICK RIDE TO TEAMCENTER FUNDAMENTALS. . .
Depending on the product structure, classic or modular variants method can be used for variant configuration of structure. Based on the business practices, one of the two approaches will be more suitable to configure the product structure. Both classic variants and modular variants should not be used together in the same product structure.
Differences between Classic Variants & Modular Variants is illustrated below : ... Continue Reading
Variant structure will be configured by setting variant rule. Options and values are set on the top level module. All the lower level modules should be fully configured with the options set on the top level module. Click the Variant Rule 
button on the toolbar to display the Configuration dialog box to set values for the options on the top level module.
After configuring the variant structure, current configuration can be saved by clicking on Save button in Configuration dialog. ... Continue Reading
The bicycle example will be referred in this post while discussing Options & MVL.
For modular variant, options can be created with visibility of private & public. Options can be defined with following types: ... Continue Reading
Teamcenter supports two methods of variant configuration. Classic variant & modular variant configuration. The method to use for variant configuration depends on the product structure. If the product structure is non-modular and does not need to be re-structured and generic assemblies are not reused often in different scope, classic variant method is more suitable for variant configuration.
Variant configuration is required to configure a product based on different allowed choices or options .Basically, variant data is attached to occurrences or its corresponding item revision,that is utilized (to set options , default values, validate values , satisfy condition to load occurrence) by variant rule to configure different variants of a product . ... Continue Reading
