Read the Full Series
This article is one part of a walkthrough detailing how we recreated an NXP i.MX 8M Mini–based computer using Quilter’s physics-driven layout automation.
Board complexity changes what a layout comparison can tell you. A workflow that performs well on a small controller may need different preparation and review on a mixed-signal or high-speed design. Build a test set that reflects your work before choosing a single productivity number.
Updated September 2026: earlier timing, via-count and manual-adjustment results were removed because their original test records were unavailable. This article now provides a method for collecting and interpreting those measurements.
Select representative board classes
- Simple controller: examine connectivity, placement effort, routing and release preparation.
- Mixed-signal board: include power, analog isolation and mechanical constraints in the acceptance criteria.
- High-speed board: include the applicable interface constraints and the required signal/power-integrity review.
These are test categories, not measured sample boards. Record actual layers, components, pin count, routing density and special requirements for every project. More layers alone do not define difficulty.
Keep inputs and responsibilities comparable
Archive the same project revision and document any differences needed by each tool. Record fixed placement, allowed vias, stack-up and fabrication rules. State whether you are comparing routing only or the full placement-and-routing process.
Altium and KiCad are CAD environments; an automation-assisted workflow can include Quilter plus one of those environments for final review. Count the preparation and cleanup in that combined workflow. Do not treat exporting a candidate as equivalent to approving a released board.
Collect measurements that explain the result
For each board and workflow, record active engineering time, automated runtime, calendar time, manual changes and unresolved violations. Count vias by type and relevant interface where useful. A lower via count is not automatically better: assess whether the design meets its electrical and manufacturing requirements.
Define a manual adjustment consistently. Moving a connector, changing one via and reworking a large routing area are different amounts of effort. Pair any adjustment count with the actual time and reason for the change.
Calculate and report carefully
Calculate time reduction separately for each board using a clearly identified baseline. Report the raw hours and the acceptance outcome alongside the percentage. Do not average percentages across unequal projects without explaining the weighting; summing comparable hours first can provide a portfolio-level effort measure.
Retain failed runs and disclose operator experience, tool versions and review boundaries. A reproducible result needs original project files and enough run information for another engineer to understand the procedure.
Turn the comparison into a pilot decision
Use the results to identify where automation helps and where expert layout work remains necessary. Review current Quilter capabilities and KiCad design tools when defining the pilot. Confirm project fit and required analyses before setting a delivery target. A defensible conclusion describes the tested boards and conditions rather than declaring a universal winner.









.webp)



















