Using saved variant rules or default and derived values

You can use both saved variant rules and default and derived option values to configure a bill of materials from a single high level entity. In the case of saved variant rules, this entity is a variant rule workspace object. In the default/derived values case, this entity may be a single option that is defined on the top level assembly from which all other option values are derived. Alternatively, you can create a separate item for a particular variant. The derived defaults method allows you to define dependencies as an integrated part of the structure. Its main disadvantage is the complexity of setting up derivation rules. Saved variant rules are simpler to set up, but they are not as tightly coupled with the structure. Siemens Digital Industries Software recommends you use saved variant rules when initially building your structure. You can then convert to default and derived values once you have fully analyzed the interactions. Saved variant rules may provide a useful configuration mechanism to store marketing packages after the structure is released.

Note If a default or derived default value exists and you try to save the variant rule, Teamcenter displays the Save As… dialog box and you can select the Save default and derived default values as user set check box to save the default and derived default values in the SVR. If no default or derived values exist, it does not display the Save As… dialog box.