Skip to main content
ION tracks mBOM changes through explicit versions. See Bills of materials overview for how versioning relates to part revisions and in-flight runs.

​
When a new version is needed

In general, structural changes (what gets installed, where, and how many) need a new version. Metadata changes (notes, alternates, and clarifications) can be in-place edits.

​
Version states

mBOM versions move through: Only one version of an mBOM is Released at a time. Releasing a new version automatically archives the previously released version.

​
Release a new version

  1. Open the mBOM card on the part page with the version in Draft.
  2. Make the structural changes.
  3. Use the status dropdown to move the version through In Review and then Released. The previous released version moves to Archived.
To start the next version once the current one is released, click Create new mBom version in the card header.

​
Step installations left on the superseded version

Part-step assignments are copied onto a new version when you create it, not when you release it. Anything assigned to the old version in the meantime stays there, so the procedures that carry those assignments come up short once the new version governs. ION tells you which ones. When the release supersedes an earlier released version that held step installations, a v<n> released notice opens listing each affected procedure by number and title, and asks you to review the step installations on them and reassign anything missing. Click Got it to dismiss it. The notice appears after the release lands, so it never blocks or cancels the release. It appears on both routes to Released: the status dropdown and the approval that completes the review gate. On a very large version the notice says the list may be partial rather than under-reporting silently.
The notice reaches whoever released the version. When someone else’s approval is what releases it, the procedures’ owners aren’t notified, so tell them to re-check their assignments.

​
Review and approve a version

A Draft version can go through review before it’s released. Reviewers are assigned per role, and each role can require a set number of approvals. Open the review panel from the mBOM card:
  1. On a Draft version, open the review panel and expand the Reviews section.
  2. Click the add-reviewer control to add a reviewer row. Pick a role, then pick the reviewer (a user or team that holds that role). ION creates an approval request for that reviewer.
  3. Resolve any open feedback and assign every required reviewer.
  4. Click Move to In Review to submit the version. The button is enabled only when all feedback is resolved and every required reviewer is assigned.
Once the version is In Review, each assigned reviewer approves or rejects with the approve (check) and reject (X) controls. A reviewer can act only on their own assigned review, and can’t change it after approving. When the required approvals are in, move the version to Released with the status dropdown.

​
In-flight runs

When you release a new mBOM version, in-flight runs are unaffected:
  • Each run captures the mBOM version it was started against at create time.
  • New runs started after the release pick up the new version.
To apply a structural change to an in-flight run, use a redline. To bring the units already being built onto a newly released version, raise a change order, which updates each unit’s aBOM rather than the run’s captured version.

​
Switch between versions

The mBOM card on the part page has a version dropdown (for example, v1, v2) in its header. Pick a version to view its lines. Each option shows the version’s status, and Draft versions can be deleted from the dropdown. To see a version’s full line items, open the full mBOM with the Go to full mBom link in the card header.

​
Programmatic comparison

ION has no built-in page that diffs two mBOM versions. For integrations or scripts, adapt the Compare two aBOM versions query template: fetch the line items for both versions and diff them client-side.