Sharing and reuse
Export report (HTML)
Produces a single self-contained HTML file: the viewer, the styles, the board image and the records are all inside it. There are no external references of any kind, so it opens from a file on disk or an email attachment on a machine with no network — the situation a factory PC is often in.
It stays interactive. Whoever you send it to can filter by failure type, drill into a component's cause breakdown and switch to the executive view, none of which a screenshot allows. The report states how it was scoped — which assembly, which period, and whether any designators were matched — so a shared file cannot quietly mean something different from the screen it came from.
Export PNG
A rendered image of the current chart, for a slide or an email body. Use the executive view first if it is going to a management audience.
Save board package
Setting up a board — image, placement file, size, origin, calibration, criticality — is the slow half of the work, and it does not change between analyses. Saving the board package writes all of it to a single file on your machine. Loading it back means a repeat analysis only needs the new failure export.
The package stores your placement file verbatim and re-reads it on load, so there is one source of truth for what the coordinates mean. It is an ordinary local file: nothing is uploaded, and you can keep it wherever your other board records live.
A board package contains your board image and placement data. Treat it with the same care as those files — if they are covered by an NDA, so is the package.
Sample files
Under Expected input formats & sample files in the app, every file in the demo dataset can be downloaded individually — including the board image — so you can run the whole flow yourself before involving any real data.