For PCB assembly quality teams

See where failures cluster
on the board.

A Pareto chart tells you what fails most. Concentration Chart adds where — your test, AOI and repair exports drawn as counts on the board image itself, so a process problem clustered around one corner of the board is visible in a glance instead of being reconstructed by hand.

No account required. Nothing to install. A worked example loads in one click.

What it does

1 Load what you already have

Your pick-and-place file, a photo or render of the board, and whatever failure data your systems export — ICT, AOI, flying probe, repair logs, quality records. Excel workbooks and CSVs in any common dialect are read as they come.

2 It places every failure

Records are normalized and aggregated per component, each component is located from the placement data, and the counts are drawn on the board with cause breakdowns underneath — no manual tallying, no hand-placed arrows.

3 Share the result

Export a PNG for a slide, or a single self-contained HTML file that stays interactive and opens from an email attachment on a machine with no network.

Your board data never leaves your browser

Board layouts and failure histories are usually the most sensitive thing a contract assembler holds. Most tools ask you to upload them. This one cannot: every file is parsed and rendered inside the page, and the page is served with a content security policy that forbids it from opening a network connection at all.

And it is checked, not asserted

On every deployment, the full flow — load files, generate the chart, export it — is driven through Chromium, Firefox and WebKit against the live site. The run fails if a single request leaves the page, if the policy is violated, or if any security header is missing.

  • You can confirm it yourself in about a minute with your browser's network tab.
  • Nothing to negotiate before a trial: there is no data for us to receive.

Read the security model →

Built around what a quality team actually has

Exports are messy, and that is fine

Semicolon and tab separated files, a title row above the header, Excel workbooks with dates stored as serial numbers, European decimal commas, placement files from Altium, KiCad or Eagle with their own units and origin conventions. Reading them is the tool's job, not yours.

See every format we test against →

Wrong answers are worse than none

Nothing is silently dropped. A file that is recognized but yields no records is an error. Parts that fall outside the board image, designators the two systems spell differently, exports covering several assemblies, rows with no date — each is surfaced rather than quietly folded into the totals.

How the mapping works →

Try it on the demo board

The app ships with a complete synthetic dataset — a board, a placement file and three different failure-export formats — so you can drive the whole flow before deciding whether to point it at anything of your own.