Documentation
Concentration Chart maps failure data onto a picture of the board. Everything runs in your browser — there is nothing to install and no account needed to try it.
The fastest way to see it
Open the app and press Load demo board & data. That loads a complete synthetic dataset — a board, a placement file and three different failure export formats — and generates the chart. Nothing is downloaded and nothing of yours is involved.
Using your own data
You need three things, all of which an assembler normally already has:
- A placement file — the pick-and-place / centroid export for the board. This is what lets the tool find each component without anything being positioned by hand.
- A board image — a top-down photo, or a CAD or Gerber render.
- Failure data — whatever your test, AOI, repair or quality systems export. You can load several files at once and mix formats.
Optionally, a small CSV marking which parts are critical and which are transparent to test. See Setting up a board for the details that matter most, and Supported formats for what is read.
What the numbers mean
| Tile | Meaning |
|---|---|
| Failures shown | Records currently on the map, and the total read from your files. The two differ when parts are excluded or filters are on — the difference is always accounted for. |
| Components affected | Distinct reference designators with at least one failure in the current view. |
| Top offender | The component with the most failures in view. |
| Transparent-to-test | Records on parts the tester cannot measure. Excluded from the map by policy, never from the count. |
| Data sources | How many distinct export formats were detected across the files you loaded. |
Scoping a report
By assembly
If an export covers more than one product, the app says so. Scope the report to a
single assembly before reading the numbers — U7 on one assembly is a
different part from U7 on another, and merging them produces totals that
look reasonable and are wrong.
By period
Set a from/to window to restrict the report to a date range. With both ends set, each component also shows its change against the immediately preceding window of equal length — red for worse, green for better — which is how to check whether a process change actually helped. The comparison window is named on screen. Records with no date belong to no period and are reported separately rather than dropped.
When something looks wrong
| What you see | What it usually means |
|---|---|
| The board is empty and every record is "not on the map" | The two files spell designators differently (U7 vs U007). The report offers to match them — see Designators. |
| "N components fall outside the board image" | The board size or origin does not match the placement file. See Origin and units. |
| A file is listed with "0 records" | This should not happen — a recognized file that yields nothing is reported as an error instead. If you see it, please tell us. |
| Dates read as five-digit numbers | Also should not happen: Excel day serials are converted. If a date column comes through raw, send us a sample and we will add it. |
Anything that could place a part in the wrong spot is called out in the app rather than absorbed quietly. If you find a case where it is not, that is a bug worth reporting to support@engsecsolutions.com.