A life cycle is an automated, graphical model, employing phases and gates, used to manage

business objects as they progress from conceptualization through obsolescence

When created, a life cycle-managed objeWindchill PDMLink supports the following business
processes that you can use to manage the life cycle of a part, document, or CAD document. You
can use transition rules to control when in the life cycle this operation is available. For example:

•Set State—Enables you to informally set the life cycle state of an object.

•Promote—Enables you to set the state of one or more objects to a new life cycle state as part
of a review process.

•Change—Enables you to execute a change order for a product development object.

•Revise—Enables you to create a new version of the object.ct enters a life cycle phase, where it
is assigned an initial state, which is associated with the initial phase of its life cycle.

Each Windchill object type can have unique sets of life cycle states. While an object is in a
specific life cycle phase, certain business rules apply, such as access control rules or a specific
workflow defined for that phase.

Basic Life Cycle And Advance Life Cycle Differenece :

Basic- The basic life cycle is designed to use a team context. A basic life cycle does not include
workflow process definitions and relies on the workflow process definitions with change
management, routing, or promotion processes.

When you create an object with a basic life cycle and select a team template, the selection of
the team has no effect. Basic life cycles do not utilize teams or workflows.

Advance - The advanced life cycle type provides the ability for a separate team to be assigned
for instances of this object type. You can also include workflow process definitions within the
life cycle states to manage the maturing of the object type.

Use this type for managing objects that require company-specific business processes, special
access control requirements, or additional flexibility in managing these types of objects.

1
Working With Life Cycle Template ----

Site, organization, and application context managers manage life cycle templates.

•Site administrators create, modify, delete, and view life cycle templates in the site context.

•Organization administrators create, modify, delete, and view life cycle templates in the given
organization context. Organization administrators can view life cycle templates from the site
context.

•Application context managers create, modify, delete, and view life cycle templates in the given
application context. They can view life cycle templates from the parent organization context
and the site context.

When you create a life cycle template, the system saves the new life cycle template in the
System cabinet or folder of the context in which it is created. You must have the necessary
access permissions to create or edit a life cycle. For more information,

Using Life Cycle Transitions -----

The Transitions tab appears when creating or editing a life cycle template. You can use
transitions to define paths from the selected state to any other state within the life cycle
template.

Using a set of transition rules, you can define appropriate sets of business processes for the
stage of development for an object. For example, the processes for developing a part can be
informal in the early stages of development, but will require more formal processes if the part is
introduced into production.

Change -----------

The state to which an object is moved when the change process completes.

For more information, see Administration of Change Process Transitions .

lock----------------

This transition is only valid when using the promotion request process. It identifies a temporary
state to apply to an object while reviewers consider a promotion request.

For example, you add the Pending Approval phase to a life cycle and configure a restricted set

2
of access policies that apply to objects in the Pending Approval state.

From the Released phase, you specify the Pending Approval state for the Lock transition. As a
result, when a user creates a promotion request for an object that is in the Released state, the
object is placed in the Pending Approval state until the promotion process completes.

Obsolescence-----------------

Defines the path used to make object versions obsolete through a change process.

For more information, see Administration of Change Process Transitions .

Production Released------------

Defines the path used when releasing object versions to production through a change process.

For more information, see Administration of Change Process Transitions .

Promote-------------

The Target Promotion State options available when creating a new promotion request.

Refine---------------------

The state of objects being reworked or being refined. This transition is not used out-of-the-box,
but can be used in a custom workflow.

Review----------------

The state of objects progressing through a review process. This transition is not used out-of-the-
box, but can be used in a custom workflow.

review

Set the initial state of a new object version created from an existing object.

This applies to versions created through the following actions:

•review

•New View Version

•New One Off Version

-------SetState

The Target State options available when performing the Set State action.

3
*

This transition only applies to non-administrative users who are granted access to the Set State
action. Administrators can continue to use the Set State action to move an object between all
available states.

To perform a Set State operation, non-administrative users must have the Set State permission
granted through the Policy Administration utility. For more information, see Planning Object
State Change Policies