r/AskElectronics • u/Pouloch • 17h ago
Multi-board systems: I prototyped a single source of truth for diagrams, harness docs and BOM. Real need or just our process?
Hi all,
I design multi-board electronic systems using Altium for PCBs, but I find its handling of inter-board cabling and multi-board projects lacking. I’d like to know whether this is a common pain point or just a symptom of our company’s process.
Our current workflow:
- A system-level diagram showing boards and interconnections (nested subsystems when needed)
- Harness documentation made with WireViz
- A manually built BOM linked to our inventory tool
That’s three redundant sources of truth, all filled in by hand. It’s slow and error-prone.
What I prototyped:
A tool built around a single database (parts, boards, harnesses, full systems) with a graphical editor for structured diagrams. The BOM and wiring docs are auto-generated from the diagram, so they can’t drift apart. I’m also considering release management with validation tests, and since the diagram format is LLM-readable, an AI-assisted check before publishing a release.

Questions:
- Do you face the same consistency problem between diagrams, harness docs and BOM?
- How do you handle it today (tools, scripts, PLM)?
- Would a tool like this be useful to you, or is it a non-problem?
Any feedback, including harsh, is welcome!




