Configuring structures by classic variants

Teamcenter supports three methods of variant configuration, classic variants, modular variants, and Product Configurator variants. Siemens Digital Industries Software recommends that you do not create both classic variants and modular variants in the same product structure, as this may cause in unpredictable results. Classic variant configuration allows you to create options (for example, color) and allowed values for each option. You can then associate these options with an item revision. For example, you might create an option called color with allowed values of red and blue. You usually implement variant configuration against a top-level assembly, but it is possible to implement them anywhere in the structure. You can then define a variant condition on those occurrences subject to variant rules. A variant rule is a set of options and values (for example, color = red, material = cotton) that is stored in the database. For example, you can specify only load IF option color = value red in the variant rule for the example option and allowed values. To configure a particular variant of the assembly or product, you must set the appropriate variant rule. To prevent users from specifying illegal option values or combinations, you can set default option values, for example, color = blue, in the variant rule. You can also create variant rule checks, for example, error if color = green AND material = cotton. If you install the Teamcenter Integration for NX, classic variants do not synchronize with NX expressions. However, you can configure saved variant rules from NX, although you cannot interactively set variant rules. Also, like configuration in Structure Manager, you can apply multiple saved variant rules from NX. Classic variants suit situations where the user chooses one or more option values from a set of values. Only text option types supported. Classic variant configuration supports: Options that are a mandatory choice or an accessory. Components that may be configured by more than one option. Variant assemblies that may be shared between products. A 120% BOM, allowing users to select multiple values for an option. This contrasts with the 100% BOM that represents the buildable product, in which users may select only one value for each option. Overlay configurations, allowing users to apply multiple saved variant rules (SVRs) to the product structure. Classic variant configuration does not support: Automatic creation of variant item. Updating of existing variant items.

Caution If you migrate from one variants technique to the other, be aware that Teamcenter evaluates the same variant condition differently in modular variants and classic variants. In some circumstances, this may result in different product structure configurations. For example, Teamcenter evaluates classic variant conditions from the left, giving all operators the same precedence. When it evaluates modular variant conditions, it automatically gives AND clauses precedence over OR clauses. If you authored a line within a product structure using Product Configurator variants, you cannot update that line using classic or modular variants.