Classic Variant Configuration

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 .

Example

Let’s say the product is car that can be of model – economy or luxury and can be built with different types of engine (1200, 1500), gear can be automatic or manual, music system can be stereo, stereo-cassette or stereo-CD, airbag included or excluded. Choices can be made here and these options and their values are set to configure a particular variant of a car. Few options selected may not go together, say with engine 1500, gear cannot be manual. Checks needs to be set, so that incorrect variant of car is not configured.

Above example will be referred while discussing variant configuration in this post.

Variant Data

Following types of variant data can be placed on the structure to configure the variant of a product:

Options & Values

Option is defined with all the allowed values. Based on the value(s) selected (as applicable) for the option (in variant rule), structure will be configured.

To create Options & Values, select the line representing owning item revision (where options should be placed) and set the allowed values, by selecting the Option branch in the Variant tab of Show/Hide Data Panel.

Options attached to Item Revision

Options are associated with item revision. It is preferably attached to top level item in the product. It will propagate lower in structure to configure different component. A specific option value, does not necessarily relate to one component, but can relate to different components at different places in the structure.

Options can be mandatory choices or accessory

Options can be mandatory choices or an accessory. For mandatory choices, user must select a value for the option to configure the structure. For example- gear, engine.

Accessories are options for which the user does not have to make a choice. They are additional components and by default no accessories are configured. In the referred example, airbag is an accessory. Unless specified, it will not be configured in the product.

Options & Shared Assembly

Music System is on Dashboard Assembly of Car. Dashboard assembly can be shared between different product (different car type). In this case it will be better to attach music-system option on dashboard assembly than at top level to product car. Otherwise option and values for music-system will configure only one car type.

Option name not unique

Option names are not unique .In case there are multiple options with same name, it has to be specified with its owning item. PSE_show_option_item_prefix preference shows or hides the owning item ID as a prefix to the option name.

Example of shared assembly & not Unique Option Name

Option can be of string type or integer type.

Examples:

Variant Condition

After creating option & values, variant condition should be specified on each component of structure to configure it correctly. For example, to load automatic gear component in the structure, condition is specified on it, i.e. this component should be loaded only if option gear has value automatic.

Creating Variant Condition

To create following variant condition on a component:

Load IF Airbag = Yes AND (Model = Luxury OR Model = Economy)

Select component in structure and click the Variant Condition button on the toolbar to launch the variant condition dialog

Add Clauses

Airbag = Yes
AND Model = Luxury
OR Model = Economy

Select last two clauses after AND then click on (…) to add brackets.

Airbag = Yes
AND (Model = Luxury
OR Model = Economy)

Quick look to Variant Rule

To determine the variant of the structure to be configured, variant rule is set. For the defined options, values are set (from the list of values for the specific option) in the variant rule dialog box

The rule set makes the variant condition true or false for the component to be configured in the structure.

A typical variant rule :

Fixed Default

Fixed default allows the option to be set to a specific value. This variant data is set to item revision. The position of its placement in the structure decides its precedence, top level fixed default being of highest priority. The default is applied globally to whole loaded structure.

E.g. Gear = Automatic

To set fixed default, select the line representing owning item revision (where fixed default should be placed) and set the specific value, by selecting the Option default branch in the Variant tab of Show/Hide Data Panel. The created fixed default should be added to this Option default branch.

While setting variant rule, in the variant rule dialog, the option value for fixed default will be automatically set. This value is allowed to be reset to some other value. Option default for gear is set to ‘Automatic’. Unless specified otherwise in the rule, gear will be automatic in car.

Derived Default

Derived defaults allow one option value to set any number of other related option values based on certain condition. Options having derived values are indicated as potentially derived in variant rule and should be completed last.

They are created in Variant tab under Option default branch. This variant data is attached to item revision but applied globally on the loaded product structure.

Let’s say, music-system is Stereo-CD if Model is Luxury.

So, in this case when setting variant rule in variant rule dialog, if model is set to luxury, music system will be populated as Stereo-CD.As discussed earlier , music system option is positioned on dashboard assembly(for sharing between products). Derived default is also attached on dashboard assembly.

Model option is on Car .Setting derived default as below:

In the variant rule dialog box:

 

Precedence of Defaults

In case of conflict between fixed default and derived default, while configuring structure, derived default is given precedence.

In case of two conflicting derived default, specifying different value for same option (based on respective condition), error message is displayed in above variant tab , while creating the derived default. The error message will also appear while setting variant rule in variant dialog, for the derived default.

Variant Rule Check

To prevent users from specifying illegal option value or combination of illegal option values, variant rule check is created. This rule is evaluated at the time of setting variant rule in the dialog, preventing users from setting invalid value combinations. This variant data is attached to item revision. Variant Rule Check is not evaluated if the item to which it is attached is not loaded in the structure. This rule check can also be attached to top level item in the product.

Variant rule check is created in Variant tab under ‘Rule Checks’ branch. Let’s say, with Engine =1500, gear cannot be manual. Error message should be displayed for this combination as “gear error”. Created Variant Rule Check for this invalid combination:

Also Read:

Classic Variant-Variant Rule

Modular Variant Configuration in Structure Manager

Difference between Classic & Modular Variants

Revision Effectivity & Nested Effectivity

Occurrence Effectivity in Teamcenter

Was this post helpful?