Difference between Classic Variants and Modular Variants
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 :
Usage of Classic/Modular Variants based on Business Practices:Â
| When same part does not need to be configured differently with option values. | Same part can be configured differently, at different location with different values of same option. E.g. Bicycle Wheel |
| Classic Variants | Modular Variants |
|---|---|
| When generic assemblies in product structure is not frequently reused. | Used when lower level assemblies in product structure is reused frequently. |
| When product structure does not need to be restructured. | Generic assemblies or modules are independent of other modules, hence facilitating restructuring. |
| When there is no need to synchronize with expression in NX. | Synchronizes option values with expressions in NX. |
| When Variant Items are not frequently required. Creation of variant items is partially supported.(Not required due to limited option values) | Use of Variant Items is utilized effectively. (Required due to large permutation of variant structure possible) |
Difference between Classic/ Modular Variants based on Implementation:
| Classic Variants | Modular Variants |
|---|---|
| Options needs to be created in the product structure. | Options from external item can also be referred to within module(External Option & Global Option) |
| Options & values associated with item revision are usually placed on top-level assembly, but these variant data can be placed anywhere in the structure. Options can then configure components lower in the structure. | Uses self-contained, plug compatible units called modules. Options & Values are stored on modules and can be propagated up and down the structure. |
| User can set values for options(when allowed for user to set & not set by derived default etc.) placed anywhere in the structure. | User can set option values for top-level module only. |
| Options have a string type or a numeric type | There are more option types including Real & Logical type. Options itself can be private or public. |
| Options have limited number of allowed values. Options can be mandatory or accessory. | Option allowed values can be unlimited. User can type in values for integer and real option types. All options are mandatory to be set, to fully configure the structure. |
| User can select multiple values for an option (120% BOM) .Even multiple SVR (overlay BOM) can be selected to configure structure. | Single value needs to be selected for each option. One SVR can be applied to configure structure. |
| Variant condition can refer to any options in the upper generic assemblies to  configure components at different places in the structure. | Variant condition on components can only refer to options of parent module. |
| Logic for variant condition & error checks are simple | Logic for variant condition, error checks etc. can be more complicated, hence modular variant language can be used to create complex expressions. |
| Same assembly cannot be configured differently with same options. | Same module can be configured differently with same options, by defining structure path(occurrence name, e.g. Front,Rear). |
Also Read:
Classic Variant Configuration in Teamcenter
Configure Classic Variants with Variant Rule
Modular Variant Configuration in Structure Manager
Connecting Modules with Options & Modular Variant Language(MVL)
