Start from a released engineering bill of materials (EBOM), then map it into a planned manufacturing bill of materials (MBOM) with assembly stages and material requirements. Preserve item identities and explain each changed grouping, quantity and purchase boundary. The MBOM describes the intended build process and needs reconciliation with the later as-built record.
R-01 is a fictional indoor inspection robot with two drive modules, a controller PCBA, a harness, a sensor and a chassis plate. The engineering structure shows the drive modules as assemblies. Manufacturing makes those modules in house, buys the controller PCBA complete and groups the sensor's two mounting screws into a virtual kit.
The manufacturing view also adds AD-900 adhesive or threadlocker at 2 mL per finished robot. That is process material with a volume unit. It is accounted for separately from the engineering assembly quantities.
Start from one approved engineering release
Choose the product configuration before transforming the structure. For a serial-003 R-01 build, CFG-R01-B selects BOM-R01 B and HR-300 B with DW-HR-300 B. ECO-017 approved the strain-relief manufacturing improvement from that serial. The installation interfaces and acceptance requirements remain controlled and unchanged.
Keep the original EBOM as the source record. The spreadsheet template shows its nine parent-child relationships and the roll-up method. Manufacturing should identify which source release its own view represents and record approval of the transformation.
A flat export can hide where quantities originate. If manufacturing sees four screws under DM-100, it must still multiply by two modules per robot. The total is eight module screws plus two sensor screws.
Use the Onshape BOM-to-CSV steps or the SOLIDWORKS BOM-to-Excel configuration checks to capture the engineering source. Retain the assembly view and release identity before reorganising its rows into manufacturing stages.
Map the engineering BOM into manufacturing assembly stages
| Engineering view | Manufacturing decision | Quantity and purchase consequence |
|---|---|---|
| R-01 contains two DM-100 A modules | Create an in-house drive-module assembly stage | Build two modules using two motors, two brackets and eight screws in total |
| Each DM-100 A contains MT-110 A, BR-120 A and four SC-130 A | Preserve the module recipe | Buy the leaves and issue them to the module stage |
| R-01 contains CB-200 A | Install a purchased complete PCBA | Buy one PCBA, with no extra purchasing of its electronic children |
| R-01 contains HR-300 B | Install the released harness | One HR-300 B for each B-configured robot |
| R-01 contains SN-400 A and two SC-130 A directly | Group sensor hardware for installation | A virtual kit groups only those two screws, with zero extra kit purchase line |
| R-01 contains CH-500 A | Issue the bought-to-drawing chassis plate | Buy one plate to its controlled drawing reference |
| Process material absent from the EBOM | Add AD-900 to the manufacturing view | Consume 2 mL per robot with the process owner recorded |
Manufacturing owns the stage organisation and process-material basis. Engineering owns the design selections and controlled interfaces. Agree who reviews a transformation that might change the design, such as a new fastener specification or another harness route. A stage label alone cannot authorise that change.
Reconcile the virtual kit without increasing demand
The sensor hardware kit is a grouping for issuing two SC-130 A screws to the sensor installation stage. Those are the same two screws already present directly under R-01. Move or reference that quantity once in the manufacturing representation so the kit adds no material demand.
Do not add another two screws to the robot total while retaining the original direct requirement as an independently consumed line. The reconciliation should still show ten SC-130 A per robot and fifty across five robots.
The kit is virtual in this fixture, so it has no supplier price or purchase line. If the real team later buys a physical packaged kit, review the item identity, contents, buying unit and whether its components remain separately purchased. That would be a changed boundary requiring its own record.
Carry release applicability into material planning
The five-unit pilot spans two configurations. Serials 001–002 use HR-300 A. Serials 003–005 use HR-300 B. A manufacturing view that groups work by assembly stage must retain that distinction when it creates material requirements.
| Material requirement | Five-unit gross quantity |
|---|---|
| MT-110 A motors | 10 ea |
| BR-120 A brackets | 10 ea |
| SC-130 A screws across both contexts | 50 ea |
| CB-200 A complete PCBAs | 5 ea |
| HR-300 A harnesses | 2 ea |
| HR-300 B harnesses | 3 ea |
| SN-400 A sensors | 5 ea |
| CH-500 A chassis plates | 5 ea |
| AD-900 process consumable | 10 mL |
The ten drive modules are in-house build outputs. The virtual kit is a stage grouping. Neither becomes an additional purchase requirement in this view.
Reconcile these gross quantities with approved stock and open orders by item and revision. Check pack size and minimum order quantities when calculating cash and order quantities. At receipt, compare the supplied harness revision and drawing with the release for the intended serials. The configuration matrix keeps that applicability visible.
Review the transformation with the people using it
Have engineering trace every finished-robot item back to the EBOM. Have manufacturing explain the assembly-stage and process-material additions. Ask purchasing to derive its buying list without buying the drive modules and their children twice.
Resolve differences in a mapping table like the one above before accepting the manufacturing view. Use the costed BOM to see how the same purchase boundary avoids double-counting cost. Keep the source release and approved transformation with the build instruction so the next pilot can repeat it.