Skip to main content
The Part Installs (aBOM) dialog lets you edit an aBOM’s build requirements directly: add a part to the build, delete one, set the quantity, configure substitutes, and call out Made on Assembly (MOA) parts.

​
Prerequisites

  • Permission to edit aBOMs on the part inventory you’re working with.
  • An existing aBOM. ION creates one automatically when a part inventory is staged for a build.
  • The Part Installs (aBOM) dialog is open. You can launch it from a part inventory page or from inside an active run.

​
Open Part Installs (aBOM)

The dialog shows the parent assembly card at the top, then a searchable list of build requirements for that assembly. If you’re working inside a sub-assembly, breadcrumbs at the top of the dialog let you navigate back up the assembly tree.

​
Turn on Edit Mode

Toggle the Edit Mode switch in the bar at the top of the dialog. In edit mode you see a You are in edit mode. banner with a Learn More link, and the Add New Build Requirement dropdown becomes available. Add, delete, and quantity changes are available only while edit mode is on.

​
Add a part

  1. With edit mode on, open the Add New Build Requirement dropdown under the edit-mode banner.
  2. Optional: To mark the part Made on Assembly, turn on the Add as MOA switch before selecting. See Made on assembly (MOA).
  3. Select the part to add. ION creates a new build requirement with a quantity of 1.
The dropdown excludes parts that are already on the aBOM, so you can’t add the same part twice.

​
Set the quantity

In edit mode, each build requirement card has a quantity input representing the count of that part required to complete one parent assembly. ION multiplies this by the parent assembly’s quantity to compute total demand for the build. When the run builds more than one parent unit, the input is labeled / assembly to make the per-assembly unit clear.
Quantity is per one parent unit. If the parent has a quantity of 5, ION calculates total demand as quantity × 5.

​
Configure substitutes

Expand a build requirement card and open the Substitutes dropdown to add alternate parts that can be installed in place of the primary part. When operators install against this build requirement during a run, they can scan any of the listed substitutes to satisfy the requirement. For more information, see Alternates and substitutes.

​
Add reference designators

For build requirements that need positional callouts, such as R12 or U7 on a PCB, expand the card and open the Reference Designators dropdown to enter them. Each designator must be unique within the build requirement and counts toward the total quantity required. For more information, see Reference designators.

​
Edit or remove an installation

Each build requirement lists the inventory already installed against it. To adjust or remove a recorded installation, click Uninstall on that installation. A popover opens with these controls:
  • Quantity to Remove: the amount of the installed quantity to take back off the assembly. Enter less than the full installed quantity to reduce the installation and keep the remainder installed. Enter the full quantity to remove the installation entirely.
  • Move to Location: optionally move the removed inventory to a chosen location.
  • Scrap item: optionally scrap the removed inventory instead of returning it to stock.
Click Submit to apply the change, or Cancel to close the popover without changes.
When the same part inventory is installed across a shared aBOM, removing it clears it from every lot it’s shared with, not only the one you’re on. ION shows a confirmation before applying the removal. After you confirm, the removal is held for about 10 seconds, and a countdown toast lets you cancel before it applies.

​
See and change which steps a part installs at

A build requirement card shows a N steps badge next to its availability badge when the requirement is assigned to run steps. Click the badge to list every assigned step with its required and installed quantities and its status. A requirement assigned to no step shows no badge and reads Not assigned to a step, which is a normal state rather than a problem. Depending on your settings, edit mode replaces a card’s install controls with an Assigned steps surface, so you can map a part to steps without leaving the dialog. This surface appears when your organization enforces mBOM parts assigned to steps. For more information, see Enforce mBOM parts assigned to steps.
  1. With edit mode on, expand the build requirement card and click Assign to step in the Assigned steps section.
  2. Pick the run step. The picker leaves out steps the requirement is already assigned to.
  3. Set the Quantity for that step.
  4. Click Assign.
A step must be in Redline to be assigned. When the selected step isn’t, the row says so and offers Put in redline; a step that’s already complete offers Reopen step first, then Put in redline. Per-step quantity is editable, and the unassign control (X) is offered, only while that step is in redline. Outside redline the row shows a static installed/required quantity, states the gate, and offers Enter redline, or Reopen step when the step is already complete. Unassigning takes effect immediately with no confirmation, and the part stays on the aBOM.

​
Delete a build requirement

In edit mode, click the trash icon on a build requirement card. ION shows a Delete Build Requirement confirmation; click Delete to confirm. Any build requirement can be deleted, whether it came from the mBOM or was added by hand. When the requirement is assigned to run steps, the confirmation previews the cascade: Steps losing this requirement lists each step with its required quantity and any installed quantity, and Existing installs, by step lists the steps that hold installs. With nothing installed, the dialog confirms that it’s safe to delete.
You can’t delete a build requirement that already has installed inventory. Delete stays disabled and the dialog states the reason next to the button. Remove the recorded installations first, then delete the requirement.

​
Install a run’s kitted parts

When the run has a kit holding inventory, the dialog’s toolbar shows a banner counting the kitted parts, such as 3 parts kitted for this run, with an Install all from kit button that installs them against this assembly in one action. The banner is hidden while edit mode is on, and a run whose kit holds nothing shows no banner. When the run has no kit at all, the toolbar offers Request All Parts instead, which creates the kit request.
The Hide complete switch at the top of the dialog hides build requirements that already have full installations recorded, which helps when working through a long aBOM late in a build. An as-required requirement (quantity 0) stays visible until something is installed against it. The layout control next to it switches between a compact and a comfortable row layout, and ION remembers your choice.
The Expand All / Collapse All button toggles every build requirement card open or closed in one click, so you can review substitutes, MOA settings, and installations across the whole aBOM at once.
Click Expand aBOM on a build requirement whose part is itself an assembly to drill into that sub-assembly’s aBOM. The breadcrumbs at the top of the dialog let you walk back up the assembly tree at any point.
Use the Search box to narrow the build requirement list by part number or description while editing.