Model Version Lifecycle

A Product Manager, System Engineer, Software Engineer, Senior Design Engineer, or Leader can create a model version.

A model version is created in the Private state. It is only visible to the Owner who created it. The Owner can add or remove features from it, delete it, or promote it to the In Work state.

In the In Work state, the model version is visible to all users with access to the collaborative space.

A Product Manager, System Engineer, or Leader can add features, marketing related rules, images, and reference documents to the model version when it is in the In Work state. They can demote or promote the model version to another state, or delete it.

In the In Design state, the model version is visible to all users with access to the collaborative space.

A Design Engineer, Senior Design Engineer, or Leader can add parts and engineering-related rules, and review the structure and rules of the model version. They can demote or promote the model version to another state, or delete it.

In the Frozen state, the model version is visible to all users with access to the collaborative space, the organization to which the model belongs, and any of its parent organizations.

A Product Manager, System Engineer, Design Engineer, Senior Design Engineer, or Leader can perform a final review of the model version and make any required changes. They can also demote or promote it to another state. In the Frozen state, the model version cannot be deleted. When the model version is in the Frozen state or later, if someone changes the mandatory status of configuration features or configuration rules associated with the model version's parent object, this change is not inherited down to the model version.

The model version cannot be promoted to the Released state until all of the related features and parts are in a Released state. The exception for those that are perpetual resources, which must be in the Available state. When the model version is promoted to the Released state, all rules associated with the model version are validated to ensure that no features have been deleted, which would make the rule invalid. A model version cannot be promoted to the Released state if an ancestor derivation has not been released.

In the Released state, the model version is visible to all users with access to the collaborative space, the organization to which the model belongs, and any of its parent organizations.

In the Released state, the model version is considered "frozen" and cannot be modified or deleted. A Product Manager or Leader can update the model version's pricing, as needed, and promote or demote it to another state. When the model version is promoted to the Released state, all rules connected to the model version are automatically promoted to the Released state.

In the Obsolete state, the model version is visible to all users with access to the collaborative space, the organization to which the model belongs, and any of its parent organizations.

The Obsolete state is considered "frozen", so the model version cannot be modified, revised, or deleted. A model version in the Obsolete state is not available for sale. A Product Manager or Leader can demote it the Released state to make it available for sale again.