Product Feature Lifecycle

The lifecycle of a product feature consists of the six states shown below. The main tasks performed in each state are listed under the state.

Preliminary State

In the Preliminary state, a Product Manager, System Engineer, Software Engineer or Senior Design Engineer creates a product feature.

Product Management State

In the Product Management state, a Product Manager or System Engineer adds sub-features, marketing related rules, images, and reference documents. They also review the structure and rules defined for each feature.

Design Engineering State

In the Design Engineering state, a Design Engineer or Senior Design Engineer adds parts, and engineering related rules, creates a generic BOM, reviews the structure and rules of the feature.

Review State

In the Review state, a Product Manager, System Engineer, Design Engineer or Senior Design Engineer performs a final review. A trigger is fired when promoting from this state which will validate all rules for the context feature and the sub-features connected to it. If a sub-feature has no further features connected to it, it will only be validated.

Release State

In the Release state, a Product Manager updates the pricing, as needed. The sub-features list is frozen and changes cannot be made at this stage. A trigger is fired when demoting from this state which demotes all the rules connected to the feature to the Preliminary state.

Obsolete State

In the Obsolete state, a Product Manager inactivates the use of the product feature and the product is no longer sold.