I was pleased with our FR10 inspection total until one of the students asked why the tray had fewer mounting plates than the screen. We had retried several pieces after review, then restarted the app, and the counter had treated more successful attempts as more accepted items.
I'm using this to review the real batch records now. I want one accepted count for physical plates, but I also want the failed attempts left where we can see them. Has anyone untangled this without making the history look as though everything passed first time?
Have you got a stable ID for each plate? With that, you can keep attempts attached to a plate and count its current accepted decision once. Without it, the software has no reliable way to know you inspected the same thing again.
Yes, plate IDs are on every attempt. They're also in quality's register. The dashboard just adds successful rows, so the identity is there and doing absolutely no work.
Use the current disposition per ID, then. Does quality ever put a passed plate back on hold? If so, any pass in its history won't be enough to decide whether it belongs in today's accepted count.
What exactly gets added at restart? Previously saved attempts, or new attempts created by the restart itself? Those would leave different problems in your records.
Saved attempts are loaded, then the counter increments for each pass again. No new inspections ran. And yes, quality can put a plate back on hold after a pass.
Our bracket dashboard had the same pass-history trap, including later holds; make the current reviewed disposition explicit instead of treating the latest successful test as acceptance.
And can the operator open the attempt history from that plate? They shouldn't have to choose between an honest item count and finding out why something is held.
There's a history page, but it opens for the whole batch. Holds only show in quality's register. I've asked for per-plate history and the current decision on the same row.
The developer is using the reviewed disposition records directly. We've agreed to show unknown if they can't be read, rather than rebuilding acceptance from the test rows.
Try a pass followed by hold, then restart. That's a small example which should expose both of the mistakes you've found, without needing to rerun a whole physical batch.
Both examples now count correctly in the offline test. History still has the original failures and retries. I was relieved to see the numbers get smaller for once.
Have you compared the full saved batch with quality's reconciled list yet? Small examples are useful, but the existing records may contain another case nobody remembered to model.
That comparison matches too, including plates on hold. Workshop rollout still pending. The students have requested credit for noticing that a tray is not the same thing as a dashboard.
Fair request from the students. Keep their original counter example in the checks; it caught a real mistake that all the happy-path demonstrations missed.