Revisions and change control

How items, BOMs, and routings are versioned, and how change orders promote new revisions.

Workcell versions the records that define a part so a design can change mid-production without rewriting history. Item revisions, BOMs, and routings each move through a draft-to-released lifecycle, and a change order is what promotes a set of item revisions together as one controlled event.

What is versioned

  • Item revisions track the form, fit, and function of an item over time. Each carries a revision label and an effectivity window, and a released revision supersedes the one before it.
  • BOMs carry an integer version. Revising a released BOM copies it into a new draft version one higher.
  • Routings carry an integer version the same way.

A released definition is what Production reads. The prior version stays on record as what earlier units were built from.

How a revision moves

Item revisions, BOMs, and routings all start in Draft (editable), move to Released (locked, the version in use), and end in a retired state.

Draft -> Released -> Superseded or Obsolete
  • Releasing a new item revision automatically supersedes the previously released revision for that item and sets its effectivity.
  • Obsolete retires a definition that should no longer be used.
  • A draft is the only state you can edit freely; once released, you revise into a new draft rather than editing in place.

Where change orders fit

Item revisions can be released on their own, or as part of a change order. A change order groups the affected items, routes them through approval, and on release promotes each item's target draft revision in one step. This is the controlled path for changes that need sign-off.

Where to go next