A robot variant BOM should resolve one chosen option set into an explicit list of selected parts, revisions, quantities and units. Define which base rows are shared, which an option replaces and which it adds. Apply compatibility rules before expansion, then give the resulting candidate its own identity and release decision.
Variant choice, engineering revision and serial applicability answer different questions. A gripper option identifies a product choice. A gripper revision identifies its controlled design state. Applicability identifies the builds that use that selected combination. Record all three so a buyer can derive one unambiguous parts requirement.
Keep future options separate from the five-unit pilot
R-01 is the fictional indoor inspection robot in Arc's BOM series. Its established five-unit pilot selects harness A for 001–002 and harness B for 003–005. ECO-017 changes strain relief during manufacture while retaining the installation interfaces and acceptance requirements. Both configurations keep DW-R01 A, ECAD CB-200 A and firmware 1.2.0. R-01 configuration matrix
This article introduces V0, a future option-planning exercise based on the B structure. It proposes optional grippers, a different sensor and a payload tray. All option IDs, interface rules and design selections are fictional. No new option is approved for pilot serials 001–005, and the original two-A, three-B harness requirement stays unchanged.
Use an option-model identity such as OPT-R01 01 to describe the rules under review. Give an expanded selection a separate candidate identity such as CFG-R01-V-JW 01. Assign future serials only after the selected package is accepted. An option set that expands correctly still needs engineering evidence and a release decision.
Define the base and every option's operation
Begin with a controlled base snapshot. The B engineering structure contains two DM-100 A drive modules, one CB-200 A controller, one HR-300 B harness, one SN-400 A distance sensor and one CH-500 A chassis plate. It also includes two direct SC-130 A sensor screws. Each drive module contains a motor, bracket and four more screws. R-01 BOM relationships
The following operations give the future options a precise meaning.
| Selection | Operation on the base | Candidate items and quantities | Owner of the proposed scope |
|---|---|---|---|
| Shared base | Retain selected rows and quantities | DM-100 A ×2, CB-200 A ×1, CH-500 A ×1 and base screw relationships | Product-data owner |
| No gripper | Add nothing at the proposed payload-tool position | No gripper assembly or adapter row | Mechanical owner |
| Jaw gripper J | Add one complete gripper and its adapter | GR-610 A ×1 and AD-611 A ×1 | Mechanical and gripper-interface owners |
| Vacuum gripper V | Add a mutually exclusive complete tool and adapter | GR-620 A ×1 and AD-621 A ×1 | Mechanical and gripper-interface owners |
| Standard sensor S | Retain the base sensor and harness | SN-400 A ×1 and HR-300 B ×1 | Sensor and electrical owners |
| Wide-field sensor W | Replace the base sensor and harness | Remove SN-400 A and HR-300 B, select SN-410 A ×1 and HR-310 A ×1 | Sensor, electrical and firmware owners |
| Tray payload T | Add one tray at the proposed payload position | PL-700 A ×1 | Mechanical owner |
In this model, GR-610 and GR-620 each arrive complete with their internal hardware. AD-611 and AD-621 are separately purchased complete adapter lines. Each adapter includes the mounting hardware required by its declared gripper-to-adapter and adapter-to-robot scope, so no separate mounting-fastener line is added here. The gripper price and quantity exclude that separately purchased adapter. SN-410 is assumed to retain the two selected sensor screws for the arithmetic exercise. These are proposed design conditions to inspect before approval, with no demonstrated physical compatibility.
Microsoft Dynamics 365 documents product masters, dimensions and variant configurations, including a selected subset of BOM lines. Its dimension-based rules can enforce or prohibit combinations. Those are examples of category behaviour. They do not implement or approve this fictional R-01 model. Microsoft product-variant documentation and configuration rules
Make compatibility a decision rule
Use Boolean symbols only where they make the rules easier to inspect. Here, J, V and T mean the corresponding option is selected. S and W represent the two sensor choices. HB and HW mean the B base harness and proposed wide-field harness are selected. A value of 1 means selected and 0 means unselected.
| Rule ID | Explicit rule | Meaning and disposition |
|---|---|---|
| R-V01 | J + V <= 1 |
At most one gripper occupies the tool position. Reject a selection containing both. |
| R-V02 | S + W = 1 |
Select exactly one sensor type. Hold missing or duplicate sensor choice. |
| R-V03 | HB + HW = 1 |
Select exactly one harness in this option model. |
| R-V04 | S = HB and W = HW |
Standard sensor uses HR-300 B. Wide-field sensor uses HR-310 A. Reject a mismatched pair. |
| R-V05 | T AND (J OR V) = false |
Tray and gripper share the proposed mounting position and cannot coexist in model 01. |
| R-V06 | W implies FW-W |
Wide-field sensor needs the separately identified compatible firmware candidate FW-W. Hold it while that exact artefact and inclusion remain unresolved. |
Rule R-V04 is a declared compatibility constraint, with electrical and sensor owners responsible for its evidence. It says nothing about the real interfaces of a catalog sensor. The project must inspect power, connection, signal meaning, mounting and firmware support before accepting the selection. The robotics ICD guide provides the detailed endpoint-review method.
Preserve the inspected rule-model revision with each expanded candidate. Changing a compatibility rule after selection needs a review of the affected candidates. NASA's configuration-management method supports keeping identified configuration documents and their controlled changes recoverable. NASA configuration-management guidance
Expand one valid candidate without double counting
Candidate CFG-R01-V-JW 01 selects jaw gripper J, standard sensor S and base harness HB. V, W, HW and T are 0. It satisfies the stated rules in OPT-R01 01. It uses the retained 1.2.0 firmware selection as a proposed inclusion and carries no approval to build.
Resolve the base rows first, apply replacements, then add the selected options. A flat purchasing candidate for one robot is shown below.
| Item and revision | Quantity | Unit | Derivation or purchase boundary |
|---|---|---|---|
| MT-110 A | 2 | ea | One motor in each of two in-house drive modules |
| BR-120 A | 2 | ea | One bracket in each drive module |
| SC-130 A | 10 | ea | Two sensor screws plus two modules with four screws each |
| CB-200 A | 1 | ea | Buy complete controller PCBA |
| HR-300 B | 1 | ea | Retained standard-sensor harness |
| SN-400 A | 1 | ea | Retained standard sensor |
| CH-500 A | 1 | ea | Retained chassis plate |
| GR-610 A | 1 | ea | Added complete jaw gripper |
| AD-611 A | 1 | ea | Added complete adapter scope |
DM-100 remains an in-house build output in the assembly record. Purchasing buys its children once. The gripper option adds neither a vacuum assembly nor a tray. The sensor and harness each appear once. This table gives the selected design demand. Manufacturing additions and process materials need a separately accepted transformation. EBOM-to-MBOM guide
Reject the sensor and harness mismatch
Candidate CFG-R01-V-WX 01 selects W=1 and HB=1 while S=0 and HW=0. It violates R-V04. The wide-field sensor is paired with the base harness instead of its required candidate harness. The product-data owner records the rejected expansion and holds its purchasing and build handoffs.
The electrical owner can propose replacing HR-300 B with HR-310 A. The firmware owner must resolve FW-W. The sensor and mechanical owners inspect the selected interface and mounting scope. If the requested option remains W, those records and the inclusion approvals must be ready before the candidate can become a build package.
Another remediation is to retain the standard sensor and HB, then issue a corrected standard selection for review. The owner preserves the original rejected candidate and reason. Relabelling HB as compatible does not supply the missing engineering evidence or authorise a new rule.
Robot variant BOM questions
Should every option get a separate copied BOM?
A shared rule model can resolve several options, provided each selected output is identifiable and reconstructable. Separate controlled BOMs can also work. Choose the arrangement that keeps the accepted selections and changes inspectable.
Does a valid option combination mean it is released?
It means it satisfies the stated rule model. Engineering approval and exact package inclusion still need recorded decisions and supporting evidence.
Why does a replacement remove the base row?
Replacement chooses a different occupant of the same defined position. Retaining both as consumed rows would count two sensors or harnesses when the selected design calls for one.
Can future options inherit pilot serial applicability?
Assign applicability after reviewing the new selected package. This future R-01 exercise gives no new option approval for the original pilot serials.
Continue the variant review
Collect a selected candidate with the whole-robot release manifest. Use the ICD guide for compatibility evidence and the build-record template for the later installed unit.