Build Lifecycle

The lifecycle of a build consists of the six states shown below. The main tasks performed in each state are listed under the state. The Product Planner and Manufacturing Planner roles are only available when the X-BOM Unit Tracking application is installed.

The Build lifecycle includes these states:

Plan

In the Plan state, a Product Manager or Product Planner plans for a new build and creates the build object. A Product Manager, System Engineer, Product Planner or Manufacturing Planner can modify, connect, disconnect, or delete the build or promote it to the Build state.

Build

In the Build state, a Product Manager, Product Planner or Manufacturing Planner can modify, connect, disconnect, or delete the build, demote it to the Plan state, or execute the build and promote it to the Internal Testing stage.

Internal Test

In the Internal Test state, a Product Manager, Product Planner or Manufacturing Planner performs various internal tests on the build. When internal tests are passed, the build is promoted to the External Test state. Before the build is promoted, a Product Manager, Product Planner or Manufacturing Planner can also modify, connect, or demote the build to the Build state.

External Test

In the External Test state, a Product Manager, Product Planner or Manufacturing Planner performs various external tests on the build. When external tests are passed, the build is promoted to the Complete state. Before the build is promoted, a Product Manager, Product Planner or Manufacturing Planner can also modify, connect, or demote the build to the Build state.

Complete

In the Complete state, a Product Manager, Product Planner or Manufacturing Planner confirms the various tests on the build and the status is set to Release. The build cannot be modified. A Product Manager, Product Planner or Manufacturing Planner can choose to promote the build to the Release state or demote it to the External Test state.

When X-BOM Unit Tracking is installed, promoting a build from the Complete state to Release state is known as shipping the build. Before a build can be shipped, its As-Built structure must be completed and when the build is shipped, a read-only view of its As-Shipped structure is made available. These items are done through a series of three triggers. By default, these triggers are disabled and only activated when X-BOM Unit Tracking is installed. You can choose to disable any of the triggers.

Upon promotion to the Release state, a promote check trigger validates that the build's As-Built structure, if any, is complete. The build's As-Built structure is complete when:


  1. The build is either installed or uninstalled and can no longer be allocated.
  2. The build has an assigned serial number.
  3. The build has an assigned part number.
  4. All first level child builds are in the Complete or Release state.

Next, a promote action trigger updates the build's shipped date with the system date and a second promote action trigger creates the build's read-only As-Shipped view. The As-Shipped view is a view of all its child builds that have been installed. A child build is considered installed when its installed date is not null and is greater than its uninstalled and allocated dates (including null uninstalled and allocated dates).

Release

In the Release state, a build can be used with a product. A Product Manager, Product Planner or Manufacturing Planner can modify, connect, or disconnect the build, promote it to the Obsolete state, or demote it to the Complete state.

When X-BOM Unit Tracking is installed, A Product Manager, Product Planner or Manufacturing Planner can modify the build through the Allocate, Deallocate, Add New, Add Existing, and Replace With commands. The ability to modify the build allows for service and maintenance jobs after a build is shipped.

Obsolete

In the Obsolete state, a Product Manager, Product Planner or Manufacturing Planner can demote the build to the Release state. The build cannot be modified.