Work in Progress . . . Please check back again soon.
Click on Image to View
Database Library Manager for Altium DBLibs.
The intersection of Version Control Systems (VCS) like Git and Product Lifecycle Management (PLM) / PDM is one of the most critical architectural challenges in hardware engineering. While software development enjoys a unified toolchain, hardware engineering bridges two distinct worlds: rapid, iterative design source control and rigid, lifecycle-governed manufacturing data.
Trying to force a PLM tool to act as a source code repository—or trying to use Git as an enterprise BOM and lifecycle manager—creates unnecessary friction. Each system serves a distinct domain:
| Focus | Version Control (Git / TortoiseGit) | PLM / PDM (OpenBOM / Enterprise) |
|---|---|---|
| Artifacts | Source files, schematic symbols, PCB footprints, automation scripts (VBA/DelphiScript). | Assembled BOMs, Approved Vendor Lists (AVL), lifecycle states, ECOs. |
| Tracking | Line-by-line diffs, branching, merging, commit histories, tag releases. | Assembly revisions (Rev A, Rev B), where-used analysis, compliance tracking. |
| Users | Design engineers authoring layout, schematics, and automation code. | Cross-functional stakeholders: procurement, manufacturing, quality, management. |
| Approach | Decentralized, file-centric, optimized for iteration and parallel engineering. | Centralized/cloud-managed, database-centric, single source of truth governance. |
The core challenge in hardware version control is that CAD tools (Altium Designer, SolidWorks) generate large binary files (.PcbDoc, .SchDoc). Standard Git diffing cannot inspect inside binary blocks. To make Git effective for hardware, teams separate design source from snapshots:
A robust workflow uses Git and PLM sequentially rather than treating them as competing systems:
Copilot Request
Compare two Excel workbooks. Report all value changes, formula changes, added/removed rows, and missing worksheets. Generate the results as an Excel report.
What you did is actually the correct upload method. The issue is that Copilot Web can handle uploaded Excel files in a few different ways depending on the session and feature rollout.
To maximize the chance that I receive the actual workbook binary (so I can create a downloadable comparison workbook):
.xlsx files from your PC.Compare these two Excel files and create an Excel differences report.
A few things to avoid:
.xlsx files directly from disk.What happened in this session is that Copilot exposed the workbook contents as searchable document data rather than giving me direct access to the workbook files themselves. I could read and compare the data, but I couldn't generate and return a new .xlsx report from those attachments.
A quick test:
Based on the files you uploaded, I was able to determine that the two workbooks are effectively identical except for the worksheet name (parts vs Imported). [Parts Demo...61103.xlsx | Excel], [Parts Demo...61103.xlsx | Excel]
If you'd like, I can also show you a very robust Excel/VBA or Python comparison utility that will generate the exact differences report locally on your machine for large BOM and parts-library comparisons.