Creating a Build

You can create a build in the context of a model version or product configuration, or without context and connect it to a model version or product configuration at a later date. Builds created in the context of a model version or product configuration are end item builds and can be manufactured and delivered to customers.

When a build is created in the context of model version, it is also connected to the model associated with that model version. When a build is created in the context of a product configuration, it is connected to the model version associated with that product configuration and the model associated with that model version.

By default, a build can be connected to multiple model versions unless Unit BOM Management is installed, in which case it can be connected to only one model version.

See Also
Builds or Units Page
Build Properties Page
About Searches
  1. To create a build, do one of the following:
    • From the top bar, select Add > Product Line > Create Build.
    • From the app home page:
      1. Click .
      2. In the navigation pane, click Builds.
      3. In the toolbar, click Create Build .
    • From a model version or product configuration:
      1. Open the model version or product configuration.
      2. In the navigation pane, select Planning.
      3. Select the Units tab.
      4. In the toolbar, click Actions > Create New .
    • From a model, if Unit BOM Management is installed:
      1. Open the required model.
      2. In the navigation pane, click Units.
      3. In the toolbar, click Actions > Create New .
    • From a build, if Unit BOM Management is installed:
      1. Open the required build.
      2. In the navigation pane, select As-Built.
      3. In the toolbar, select Actions > Add New > Add New Build.
  2. Enter these details. Some fields may or may not be present or editable, depending on the context from which you accessed the page:

    Field NameDescription
    VaultClick to search for and select the vault where files related to this build will be stored.
    NameType the name of the new build or select Autoname to have the app automatically assign a name. If the number of builds value is greater than 1, you must use Autoname.
    TypeClick to search for and select the build type: hardware or software. After you select a build type, only those policies available for that build type can be selected.
    Number Of Builds Type the number of builds to generate. Multiple builds can be enabled or disabled. If enabled, you can generate up to 100 builds. Otherwise you can only specify 1 build.
    DescriptionDetails that describe the build.
    Owner Click to search for and assign an owner. By default, the person who creates the build is its owner.
    Model VersionClick to search for and select the context model version for which the build is created. If you are creating the build in the context of a model version, by default, this field is initially populated with that model version but you can select any model version under the model associated with the model version in context. After you select a model version, only product configurations associated with the model version are available for the Product Configuration field.
    Product ConfigurationClick to search for and select the context product configuration for which the build is created. If you are creating the build in the context of a product configuration, this field is populated with that product configuration by default. The Model Version field is automatically populated with the model version associated with that product configuration.
    Design ResponsibilityClick to search for and select the organization responsible for this build. By default, the design responsibility is the context organization for the model version.

    If a context model version is selected, the design responsibility is populated with the model version's design responsibility.

    Build DispositionSelect a build's disposition, or current status from the list:
    • Production
    • Shipped
    • Service
    • Inventory
    • N/A
    • blank

    This attribute is used in addition to tracking the lifecycle status of the build

    CustomerClick to search for and select the customer satisfied by this build.
    Contract NumberType the customer contract number that this build satisfies.
    Plant Click to search for and select the plant responsible for the build.
    Planned Build Date Click to select the date on which the build is planned.
    Actual Build Date Click to select a date after the planned build date to actually build the build.
    Date ShippedClick to select a date after the actual build date to ship the build to the customer or inventory location.
    PolicyThe policy applicable to this object. By default, these policies can be selected for the shown build type:

    Build TypePolicyDescription
    Hardware BuildBuildThe normal lifecycle for a build, from planning through testing and release, then obsolescence.
    Software BuildBuildThe normal lifecycle for a build, from planning through testing and release, then obsolescence.
    Software BuildThe build lifecycle with an additional media state.
    Build ArchiveUses to create an archive of a software build.

  3. Click Done.