Item lifecycle phases


Classifies item lifecycle phases, which distinguishes the lifecycle phases of documents, internally developed parts, and partner parts.

Where used

Documents, parts

Data fields

This is the complete name for the lifecycle phase.
The abbreviation is used where the full lifecycle Name may be too long, such as on the BOM, Sources and References lists.
This describes the lifecycle phase and its function.
Relative maturity
This value is used to indicate the maturity of the item to which this lifecycle phase is assigned, relative to other items' lifecycle phases. By definition, a zero value represents unrestricted production. Lower values are pre-production, and higher values are post-production.
Relative maturity is used within PDXpert to determine whether to apply the initial revision sequence or subsequent revision sequence to a part or document. See help topics Program concepts > Items: Common elements and Program concepts > Document and part iterations.
Active: users can select
Default member of collection
Permanent member of collection
For a description of these checkboxes, see the Collections reference > Managing collections help topic.

Setup suggestions

The number of lifecycle phases is primarily determined by your business rules for controlling how an item should be constrained if it's not at Production (relative maturity 0).

Some people distinguish document lifecycle phases from part phases. For instance, a document may have Preliminary (design, review, validate) and Production status. A part may go through a more detailed cycle of Preliminary (internal review, vendor quote, customer discussion), Prototype (design validation), Field test (production validation / customer acceptance), Production (unconstrained), and Service (for repair but not for new design).

As is often the case, defining fewer members makes the collection easier to understand and manage.


Learn More
Help Guide Contents [PDF]