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:
There can be numerous variants of a bicycle. Wheels, drivetrain are few modules on bicycle .These are self-contained and plugged in to form the final product. The posts on modular variant will refer to these two modules of bicycle.
Wheels
Wheels of bicycle comes in different sizes (generally used 24inch, 26inch, 27.5 inch). Depending on the purpose of bicycle, it can have different wheel size or equal wheel size for the two wheels. Mountain bikers uses bigger front wheel in their bicycle. Wheels consists of rim, spokes, hub and other components.
Error Check: Bigger rear wheel is of no use and not recommended for bicycles.
Drivetrain
In drivetrain gear assembly chain moves between crankset teeth and cog teeth to apply gear. Mostly there can be up to 10 cogs in a cassette. Crankset generally have up to 3 chainrings. Each combination is responsible for a gear i.e. crankset with 2 chainrings and cassette with 5 cogs will provide 2×5=10 gears in the bicycle.
This module is often bought by the manufacturer of bicycle. The module can be plugged in to any other bicycle with help of its interface.
Please Note: In reality, bicycles have much more complicated structure and the explanation above denotes the very simplified representation of bicycle for understanding the concepts of modular variant.
Understanding bicycle assembly w.r.t. modular variant
- For two wheels in bicycle, same module is reused with different variant data in the bicycle. This wheel module can be used in other bicycles as well.
- Drivetrain module plugged in to rear wheel module.
- Different permutation and combination of crankset and cogs to set number of gears in bicycle. Reuse and restructuring of modules.
How modules communicate with each other in structure?
Following structure representation demonstrates how modules communicate with each other to propagate options.
Key:
From parent module, option propagates to referenced options in child module
 Child Option presented to parent module to set values by user
Value set by external option
 Public Option
Child module option and parent module options are linked to each other (when propagating or presenting options).Based on variant condition (number of condition can be set with expressions) occurrences are loaded in structure. Variant rule will configure the structure based on option values, set only on top level. Error check are in place to avoid invalid configurations.
The expressions set on variant condition or the private option are written in modular variant language (MVL).
Details on the terminology related to modular variant is discussed in next post.
Also Read:
Connecting Modules with Options & Modular Variant Language(MVL)
Classic Variant Configuration in Teamcenter
Difference between Classic & Modular Variants