BOM Item Markup Lifecycle

BOM and item markups pass through predefined states before they can be applied to assemblies or parts. BOM markups and item markups are both derived from an abstract type "Part Markup."

A BOM markup defines changes to child parts in the context of a bill of materials (BOM), and is proposed by adding objects to and deleting objects from the BOM, and/or by changing the attribute values on the BOM relationship.

An item markup defines changes to attributes of parts that are not in the context of a BOM. Item markups have the same lifecycle and follow the same process as BOM markups.

If BOM or item markups are attached to an ECR, they are copied over when the proposed change is copied from the ECR to an ECO. When new revisions of the proposed changes are created during the ECO process, approved BOM or item markups must be rejected or applied before the new revisions can be released.

The BOM Item Markup lifecycle includes these states:

This page discusses:

Proposed

Anyone who is a member of the responsible design organization can create BOM and item markups. BOM and item markups must be created in the context of an ECR or ECO prior to the Review state of those objects.

In the context of ECR, you can add affected parts (associated to a policy "EC Part Policy") to an ECR and create a BOM or item markup. The BOM or item markup will be connected to the released part and the ECR object.

In this state, the Responsible Design Engineer is the owner of the BOM or item markup attached to a proposed change for an ECR in the Review state. The Responsible Design Engineer can edit the proposed markup and decide whether to approve or reject the markup before the Plan ECO state of the ECR. All BOM and item markups must be in an Approved or Rejected state before the ECR can be promoted to the Plan ECO state.

In the context of ECO, qualified design engineers or senior design engineers can create an ECO and have the proposed changes from the ECR be associated with the ECO, or can create and release an ECO without a related ECR. An assignee or owner of the ECO the user has rights to add proposed changes and create markups for those proposed changes.

The responsible engineer or any assignees of the ECO can create a BOM or item markup, but the person who has responsibility for the proposed change becomes the BOM or item markup owner. The BOM or item markup owner can edit the proposed markup then decide whether to approve or reject the markup prior to the Review state of the ECO.

Approved

In the context of an ECR, the BOM or item markup must be approved before the ECR can be promoted to the Plan ECO state.

All markups must be approved or rejected before the ECO can be promoted to the Review state.

Applied

When the markup is applied to the current or new revision of the proposed change, it is promoted to the Applied state, the owner is changed to Corporate, and the markup is changed to read-only mode.

It is not possible to apply a markup associated with an ECR.

In the context of an ECO, approved markups connected to proposed changes on the ECO are applied during the Review state of the ECO. All approved markups must be applied before the ECO is promoted to Release. All revised proposed changes must be in the Approved state before the ECO is promoted to Review.

Rejected

When a BOM or item markup is in the Proposed or Approved states, the markup owner can choose to reject the markup. The system then automatically promotes the markup to the Rejected state.