Development Part Lifecycle

The Development Part policy is the default for all creations of type Part. The Design Engineer or Senior Design Engineer has the ability to create new parts with the Development Part policy or the EC Part (production) policy.

See EC Part Lifecycle.

The purpose of the Development Part policy is to allow engineering the ability to design new parts in a controlled environment until one of the revisions is released to production. The development process allows for multiple design iterations to be created (Revisions) 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:

Create

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

The Design Engineer must perform the following tasks at this state:


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

As the part leaves the Create state, the following checks are fired:


  • 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.

Peer Review

This is a lightweight "Peer Review" process that does not require any lifecycle signature. The owner of the part can promote to the Review state without any signature or ad-hoc route. Customers can easily add new signatures using Business Modeler or add a trigger that will force the existence of a route.

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

Complete

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.