Good, Scrap, and Rework Counts Explained in EDGEBIC

In EDGEBIC by User Solutions, the kiosk keeps three separate piece counters, good, scrap, and rework, and every scrap piece carries a reason code so loss always has an attributable cause. Good pieces measure yield, scrap measures defects with a documented driver, and rework measures parts recovered through a second pass. Keeping them separate is what lets one clean stream of taps feed the schedule, the quality report, and the downtime Pareto without any of them contaminating the others. It is a core part of shop floor data collection in the platform.

A single "pieces made" number hides everything that matters. Did 100 parts run clean, or did 120 run with 20 scrapped and 5 reworked? Those are very different days, and only the second story tells maintenance and quality where to look. This article explains what each counter captures, where it flows, and why the boundaries between them are strict.

The Three Counters

Good. During a run, the operator taps the green Good counter once per finished, acceptable part. Good pieces are the only count that becomes a day's actual pieces on the plan. They are the yield number: how much sellable product the operation produced.

Scrap. For a defective part, the operator taps the red Scrap counter. A reason picker immediately replaces the button, offering four categories (Machine, Material, Quality, Waiting) and then the specific code. The scrap increment and its reason are written together, so a scrap with no reason cannot exist. Scrap never counts toward produced quantity; it is tracked on its own with its cause.

Rework. Parts that need a second pass are counted on a rework state, separate from the good and scrap counters on the primary run. Rework hours and pieces are recorded so the true cost of recovery is visible, without pretending a reworked part was a clean first-pass good one.

Why Good Only Feeds the Plan

A day's actual pieces, the number the schedule and reports read, counts good pieces only. Scrap is excluded on purpose. If scrap padded the produced quantity, every yield, earned value, and progress figure would overstate output. By counting good alone, the plan always answers the honest question: how many acceptable parts came off the machine? A run that logs 42 good and 1 scrap reports 42 actual pieces for that day, and the scrap lives in the quality and Pareto surfaces where it belongs.

Why Scrap Always Carries a Reason

The reason code is not paperwork; it is what makes scrap actionable. EDGEBIC's four categories map to the people who can act on them:

Because every scrap event carries a category and a specific code, scrap rolls up into a Pareto chart that ranks causes by frequency. A shop can see that dimensional rejects on one machine account for 60% of a week's scrap, and send that finding to quality with real data behind it. A bare scrap count of "14 this week" sends no one anywhere.

Undo, Edit, and the Honest Correction

Piece counting on a touchscreen invites mis-taps, and EDGEBIC handles them without letting anyone quietly rewrite the count. An Undo button appears for about ten seconds after any piece tap. Tapping it decrements the last counter by one, clamped so it never drops below zero, and it writes an audit row that supervisors can see. To correct totals after that window, Edit Counts replaces the run's good and scrap counts outright, and a supervisor adjustment records the change with a mandatory reason beside the original. Nothing is deleted, which keeps the count trustworthy, the same discipline behind why actuals are immutable.

A Worked Example

An eight-hour CNC run on Monday. The operator taps Good as parts finish and Scrap once when a part gauges oversize.

The plan records 42 actual pieces for Monday, not 43. The quality figure for this operation reads 42 divided by 43, which is 97.7%. The single scrap piece appears on the quality Pareto tagged as a dimensional reject, ready for the inspector to review. One clean stream of taps, three separate destinations.

Where the Counts Surface for Planners

The three counters do not just sit on the punch; they surface where planners and supervisors act. Good pieces become each operation's daily actual pieces on the Job View and progress reports, so a planner reading a job sees real produced quantity per day, not an estimate. Scrap, with its reason, feeds the scrap Pareto and the quality report. Rework hours and pieces surface where the cost of recovery is tracked. And every correction, whether an undo or a supervisor edit, appears in the history drawer with who changed what and why. The result is that anyone looking at a job can trace its produced quantity back to individual taps, and trace any adjustment to a named reason, which is what makes the numbers defensible when a customer or auditor asks. One caveat matters before anyone reconciles a counter against a bin: the counters only increment while a run punch is open, as what the good counter actually counts works through.

Where the Counts Feed Quality

The three counters are the entire basis of the platform's quality measurement. The quality percentage is good pieces divided by good plus scrap plus rework. That figure then multiplies into the OEE calculation, so a shop's overall equipment effectiveness reflects real first-pass yield, not an assumption. Because quality is computed from kiosk piece rows, a work center with no punches shows quality as n/a rather than a fabricated 100%. For the full mechanics, see how kiosk punches feed OEE and how piece counts feed the EDGEBIC schedule.

The Bottom Line

Good, scrap, and rework are three separate truths, and EDGEBIC keeps them separate on purpose. Good measures yield and is the only count that feeds the plan. Scrap measures loss and always carries a reason so it can drive a Pareto. Rework measures recovery so its cost stays visible. Corrections are audited, never silent. From those clean counters flow honest produced quantities, a real quality figure, and a downtime analysis that points at causes, all supporting trustworthy production scheduling. See the whole loop in the shop floor execution guide, or explore the platform at EDGEBIC.