Development Phase Lifecycle

The Design Engineer or Senior Design Engineer can create parts with the development release phase.

To promote a part in the development phase lifecycle, you must have one of these roles:

  • Baseline: Author, Leader, or Owner.
  • App-specific: Component Engineer, Design Engineer, Senior Design Engineer, Product Obsolescence Manager, orPart Family Coordinator.
You must also be assigned in the same collaborative space in which the part resides and either own the part or have created it.

The development release phase allows engineering to design new parts in a controlled environment until one of its revisions is released to production. The development process allows for multiple design iterations (revisions) to be created along with ad hoc reviews at any time in the part lifecycle. In other words, a development part may have multiple revisions active and not released at the same time.

The Development Part lifecycle includes these states:

This page discusses:

General Lifecycle Rules for Development Phase Parts

These rules are specific to Development Phase parts:

  • A change order is not required. You can promote the part without a change.
  • Promoting the parent part does not depend on the lifecycle state of the child part.
  • Child parts can be set to either development or production phase without restriction.

In Work

New parts and new part revisions are created in theIn Work state. The In Work state is used to generate the "defining documentation," drawing print, for the part. Only the owner and other user granted access (for example, Responsible Design Organization) can view the part.

The Design Engineer must perform these tasks at this state:

  • Make visible to selected users (Design Responsibility)
  • Add / update attributes
  • If an item is an assembly:
    • Add items to structure.
    • Add EBOM attributes.

Before the part can be promoted past the In Work state, it must meet these requirements:

  • At least one Part Specification connection or Reference Document connection must exist regardless of the object type related. For the Part Specification the object type can be a drawing print, CAD model, or CAD drawing. For the Reference Document, the related object type can be any Document (subtype) or a Sketch.
  • The related document must have at least one file checked in.
  • At least one Design Responsibility connection must exist regardless of the object type related. Design Responsibility can be assigned only to organizations (subsidiaries, business units, or departments) within the host company.

Frozen

Promoting a development release phase part from In Work to Frozen does not require approval; however, the part requires a product in Release state to be assigned if the part has physical collaboration. You can add new signatures using MQL or add a trigger that will force the existence of a route.

Visibility to the part remains the same as in the In Work state: Owner and organization with Design Responsibility for the part.

Approved

In the Complete state, the part can be revised for another cycle of design changes or the part can be formally prepared for the Production process.

Visibility remains to the owner and the RDO given access at the Preliminary state. The owner is limited to "view only" at this state; no modifications are allowed except revision of the part.

Note: To promote a part that is under change management to the Released state, you must have the Leader role.

Released

For the part to be released, all markup must be either approved or rejected. On promoting the part from Approved to Released, all the changes in the approved markup will be applied to the part.

Obsolete

It may be determined that a part is to be made obsolete. When this occurs a person who belongs to the special role, Product Obsolescence Manager, can login and promote the part to Obsolete.

In this state, the part cannot be used in any new bill of materials. This is accomplished by changing permissions such that no connects above the part are allowed. Once the part is in the Obsolete state, only the Product Obsolescence Manager can demote it to the Released state.

A part can be promoted to Obsolete even if its child parts are not in the Obsolete State.