Skip to main content
Change orders are in beta. To try them, contact First Resonance support.
A change order applies an engineering change to inventory that already exists. Releasing a new mBOM version changes only the runs started after the release. Units already built or in progress keep the version they started against. A change order names the change, the units it applies to, and what happens to each unit’s aBOM, and it goes through review before ION writes anything. A change order differs from a redline. A redline edits one run’s steps for that build. A change order adopts a released definition across many units, and each unit keeps its own record of what changed.

​
Change order types

The type sets what a change order changes. Today, ION has one type:

​
Statuses

Return to draft takes a change order under review or approved back to Draft and reopens every review request, so the change order is reviewed again. Reopen brings a completed or canceled change order back.

​
Review

A change order needs at least one reviewer before it can go for review. In the Reviews section of the change order, pick a role, then a user or team that holds it. You can add reviewers in Draft or Under Review, and remove them only in Draft. Each reviewer records Approve or Reject there, and Reset approvals starts the review over. Once the change order is Approved, the verdicts are the record of that approval and can’t be changed. To review again, return the change order to draft.