A QUICK RIDE TO TEAMCENTER FUNDAMENTALS. . .
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
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.
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: ... 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
