Skip to main content
This setting makes step assignment a condition of moving a procedure forward, and it changes how runs read the mBOM.

​
Enforce mBOM parts assigned to steps

  1. In ION, go to Settings > Production > Procedures.
  2. Turn on Enforce mBOM parts assigned to steps.

​
What the setting changes

With the setting on:
  • Every part must be pinned to a specific mBOM version and assigned to a step before a procedure can be sent for review or released.
  • New runs follow the pinned version instead of the latest released one.
  • Once all of an assembly’s parts are assigned to steps, part quantities stay in sync with the assignments: editing a step’s assignment updates the run quantity automatically.
The gate applies to both forward transitions: Draft to In Review, and In Review to Released. It covers the procedure’s own mBOM lines and the components inside its sub-assemblies, at any depth. When something is unassigned, the transition control is disabled and names the count and the first few part numbers.
When ION can’t check the whole sub-assembly tree, it says that some components were not checked and asks you to check them before releasing, without blocking the transition. That covers a sub-assembly level holding more items than can be checked at once, and a tree nested deep enough that the check stops early. A failed data load is different: it does block, because a reload clears it.
Assigning a sub-assembly’s components still needs that sub-assembly’s own setup first: its mBOM version has to be pinned, which happens when you assign the sub-assembly in the procedure’s right rail.