I'm reconciling our batch of 205 for fixture-based dimensional inspection with Fairino FR5 in a small production cell tracking inspected items, using a molded housing. The dashboard looks nearly finished because its post-restart counter includes repeat inspections. Items can have failed checks followed by reviewed retries.
I want the accepted-item count to be accurate without discarding that attempt history.
Pick a traceable item and compare all of its inspection attempts with its current accepted disposition. Does your counter count the attempts rather than the item?
@MiaArcher0383 I've traced one item in our saved history and found several successful attempts with the same identity. Our counter adds each success, inflating the apparent batch progress.
Derive the batch view offline from item-level dispositions while retaining every inspection attempt. Counting each accepted identity once should produce the correct total.
You're right about that missing qualification. Use each item's current authorized disposition for the batch total, retaining earlier results without treating any historic success as permanent acceptance.
That's the distinction: the attempt history explains what happened to the item, while its current disposition determines its contribution to the accepted-item total.
@MiaArcher0383 On my report, we put attempts and accepted items beside each other. People stopped expecting the numbers to match once the repeated inspections were visible.
@DineshAli0212 Preserve the identity of the physical item and assign a distinct identity to each inspection attempt, keeping the relationship between them explicit.
@MiaArcher0383 The newer entries distinguish item and attempt identity, but some older results lack the item link needed to include them reliably in an accepted-item total.
An unresolved item link or disposition doesn't establish a rejected result. Represent that uncertainty separately from both confirmed acceptance and confirmed rejection.