On this page

Excel and Google Sheets vs Arc, managing a robotics BOM

Keep an Excel BOM or Google Sheets BOM when a named owner can maintain the structure and the team can reconstruct approved revisions and serial applicability. Evaluate a controlled product record when those release checks repeatedly fail or take more upkeep than the team can sustain. Test the spreadsheet and any replacement against the same robot release.

Arc publishes this comparison as a software vendor. It compares a designed spreadsheet process with Microsoft's and Google's documented controls, and with Arc's documented engineering change and configuration-evidence scope. The R-01 replay below is a procedure to run, with no executed outcomes or time-saving claims.

Set up Excel or Google Sheets BOM controls for a fair comparison

Use a table for item definitions and another for parent-child relationships. Store item IDs, revisions, manufacturer numbers and serials as text. Keep quantity and unit separate. Derive totals from the structure rather than entering the flattened buying totals by hand.

Add a release table with the configuration, BOM revision, drawing, ECAD and firmware references. Add serial applicability and a separate approval reference, approver and decision date. A receipt or as-built log should record delivered and installed identity against the relevant serial.

Protect calculation and accepted-release cells from casual editing. Use validation for IDs, supply policy and units, and flag duplicate keys or missing references. Agree how draft changes become an accepted release and who can make that decision. Keep one authoritative workbook location and a named owner for formula maintenance.

The R-01 template supplies the data structure and copyable rows. This article tests how that structure is maintained through a release, rather than adding another template.

Separate file history from release approval

Microsoft documents previous versions for Office files using the supported Microsoft 365 storage path in OneDrive or SharePoint. Confirm the actual storage and client conditions for the workbook. A local file emailed between colleagues should not be assumed to have the same shared history.

Google Sheets supports named versions and protected ranges. Name the review point, identify the accepted release in the release table and limit editing of the relevant ranges. Confirm permissions and how the team records later corrections.

File history can recover an earlier state and show edits. The release decision should explicitly identify the inspected workbook version, selected references and applicable builds. Neither a version named “approved” nor a protected range, by itself, explains who accepted the engineering baseline and on what evidence.

Control Spreadsheet evidence to retain
Change proposal Separate proposed values or a controlled review copy, linked to the source release
Review context Selected workbook version, change reason, linked source documents and owner comments
Approval Explicit attributable decision beside version history
Configuration Release table linking BOM, drawing, ECAD, firmware and serials
Purchasing handoff Approved derived view plus stock/order and receipt reconciliation

Inspect Arc's documented review scope and the workflow still to prove

Arc's documented change control includes branches, record-level differences, contextual discussion, review and merge. Its public capability record also supports attributable approval decisions and configuration-specific requirements and evidence. Those practices give the trial a review mechanism to inspect.

Ask to see the exact robot BOM mapping, accepted A/B context and serial resolution, then the buying view and supplier handoff in the intended setup. Generic engineering-review capability does not establish that those parts and procurement tasks have been executed. Record what the demonstration actually shows beside any unresolved steps.

Replay the harness release in every candidate

R-01 is a fictional indoor inspection robot with five pilot serials. Each robot uses two in-house drive modules, a complete purchased PCBA, a harness, a sensor and a chassis plate. Each drive module consumes four SC-130 A screws and the sensor mount consumes two more, giving ten per robot.

ECO-017 changes HR-300 and DW-HR-300 from A to B from serial 003. Installation interfaces and acceptance requirements remain controlled and unchanged. BOM-R01 A and CFG-R01-A apply to 001–002. BOM-R01 B and CFG-R01-B apply to 003–005. DW-R01 A, ECAD CB-200 A and firmware 1.2.0 stay selected.

Replay step Expected result Outcome and evidence to record
Reconstruct the A release Original identities, drawings and approval remain available Record recovered version/source and selected references
Propose and accept B Harness and drawing change visible against the reviewed release Record difference, reviewer, decision and accepted revision
Resolve two serials 002 selects A, 003 selects B Record the lookup or workflow used and any manual intervention
Roll up the pilot Fifty screws, ten motors, ten brackets, five each PCBA/sensor/chassis, two A and three B harnesses Record formulas or derived view and independent quantity check
Prepare buying and receipt checks Complete PCBA bought once, harness revisions separately allocated Record approval reference and how a wrong revision is held for disposition
Export for another engineer Selected structure and release evidence can be reconstructed Record format, lost context and reconstruction steps

Run the spreadsheet baseline with its planned controls enabled. Run Arc in the actual edition and permissions under consideration. Label documented features separately from observed trial results. Preserve unresolved questions and necessary manual steps rather than marking a product as incapable from missing documentation.

Decide when to keep the spreadsheet or evaluate another tool

Stay with the spreadsheet when its owner can maintain the relationships and formulas, the team consistently records approvals, and buyers and builders can reconstruct serial applicability. Review the process again when another variant, parallel release or source relationship makes those checks harder to maintain.

Consider another tool when observed failures recur, such as an overwritten accepted release, an untraceable source change or a buying list that loses revision applicability. Record the failure and test whether the candidate resolves it under the team's conditions. A general software demonstration cannot answer an untested receipt or supplier-handoff question.

If Arc is under consideration, ask to see the reviewed ECO-017 difference, attributable acceptance and retained A/B context. Then request the exact BOM import, pilot buying split and exit package. The BOM shortlist provides other documented candidates, while the first-tool guide covers adoption ownership and migration costs.

Move faster without compromising engineering rigour.

Review one product release, its change decisions and supporting evidence with Arc.