Product Variant Lifecycle

Product variants represent a variation on the selection of features for a product that offer specific capabilities to customers. Product variants control the number of variations available for marketing configuration. They are used to generate the EBOM.

The Product Variant lifecycle includes these states:

This page discusses:

Preliminary

Product Managers and System Engineers can create new variations of a product with specific capabilities from its base product structure. The product variant is created in the Preliminary state. Product Managers, System Engineers, Software Engineers, Design Engineers, Senior Design Engineers, Specification Managers, and Marketing Managers can modify the product variant when it is in the Preliminary state.

Review

In the Review state, Product Managers and System Engineers can make modifications to the product variant, such as changing which logical features are associated with the product variant. The Design Engineer and Product Manager must perform a final review then approve the product variant before it can be automatically promoted to the Release state when its associated product is Released. If the product variant is in the Review state or later, any mandatory configuration features or configuration rules created on its parent product or the parent product's parent object (such as the product line or model) are not inherited to the parent product or to its child product variant.

Release

A product variant is promoted to the Release state after it is approved by the Design Engineer and Product Manager and its associated product is Released.

Obsolete

A Product Manager inactivates the use of the product variant by promoting it to the Obsolete state so that it is no longer available.