Projects & BOMs

BOMs

Bills of materials: drafting lines, approval into immutable revisions, comparing revisions, coverage, and building kits.

Structure

A BOM (Partners group) defines what a target item is made of: component lines with quantities and units, reference designators where they matter (K1, K2…), required flags, approved alternates, and even sub-BOMs for nested assemblies. The list shows each BOM's code, version, status, and target.

Draft → approve → revise

A BOM starts as a draft — edit lines freely. Approve freezes it into an immutable revision: the thing projects link to and builds consume from. Later changes happen in a new draft revision (bump the version), which is reviewed and approved in turn; the revision history compares any two revisions line by line, so "what changed between 1.0 and 1.1" is a view, not an argument.

Views on the BOM page: Structured (as designed), Flat (the explosion through sub-BOMs), Coverage (required vs available stock for a build quantity), and Revisions.

Build and unbuild

Build executes the BOM: it consumes component stock and produces the target item into a destination you choose, writing one connected set of ledger movements (with the revision recorded). Unbuild reverses a build. Coverage answers "can we build N?" before anyone picks; shortfalls route into reservations or purchasing.

Approval and build carry their own permissions — designers draft, approvers approve, production builds.