- Home
- Blog
- EDGEBIC How-To
- How to Record a Piece Count in EDGEBIC
To record a piece count in EDGEBIC by User Solutions, tap the GOOD and SCRAP counters at the shop floor terminal during a run, or type daily piece totals into the Log Actuals grid on the planner desktop. Both paths write to the same place: daily actual pieces on the operation, which sit beside the plan and never overwrite it. Which path you use is a shop decision, not a software one.
The wider picture of what actuals capture and why is in shop floor actuals tracking explained. This post is the count itself.
Before You Start
| Prerequisite | Why |
|---|---|
| For the terminal path: the operation is in a run punch, not setup or paused | Piece counters only increment during a run |
| For the planner path: the operation has an actual start | Daily values are logged against an opened operation |
| The routing step has a pieces-per-hour rate if you want auto-calculation | The rate is what converts between hours and pieces |
Path A: Counting at the Terminal
Step 1: Tap GOOD Per Accepted Piece
During a run, tap the large green GOOD counter once per finished piece. The count increments the open run punch immediately. Count as pieces come off the machine, not from memory at shift end: a running count survives interruptions, breaks, and shift changes.
Step 2: Tap SCRAP and Pick a Reason
Tap the red SCRAP counter for a rejected piece. A reason picker replaces the button before the count moves. Choose a category first, then the specific reason:
| Category | Typical use |
|---|---|
| MACHINE | Tooling, spindle, coolant, alarm-driven defects |
| MATERIAL | Bad stock, wrong grade, incoming defect |
| QUALITY | Dimensional, cosmetic, process defects |
| WAITING | Losses tied to waiting on something upstream |
A piece can never be scrapped without a reason. Use Change reason if the defect category shifts mid-run, which starts a fresh reason on subsequent taps.
Step 3: Undo a Mis-Tap
An UNDO button appears for about ten seconds after each piece tap and takes the last count back. The undo is itself recorded, so a supervisor sees it in the history drawer. It is a correction, not an erasure.
Step 4: Fix Totals Outright With EDIT COUNTS
Past the undo window, tap EDIT COUNTS. The Enter Counts dialog replaces the current good and scrap counts for this run. Replaces, not adds. If twenty taps already landed and you type 25, the result is 25, not 45. This is the single most common surprise in the whole counting workflow.
Path B: Counting on the Planner Desktop
Step 1: Open Log Actuals
Select the job in the Job View tab, right-click the operation's bar and choose Log Actuals, or use the Log Actual header button and pick the work center.
Step 2: Fill the Actual Pcs Column
The grid shows one row per calendar day. Type into Actual Pcs for the day the pieces came off.
| Column | What it holds |
|---|---|
| Date | The calendar day |
| Sched Hrs / Sched Pcs | What the plan expected that day |
| Actual Hrs / Actual Pcs | What really happened, typed by you |
| Rate (Pcs/Hr) | The rate used to convert between the two |
| Source | Blank for hand entry, Auto-filled where the system filled from plan |
Step 3: Decide Whether to Auto-Calculate
Leave Auto Calc Hours (derive missing side from Rate) ticked to enter one side only. Enter 12 pieces on a step rated at 2 pieces per hour and 6 hours derive. Untick it to record both sides independently, and the grid stores exactly what you typed along with the observed ratio between them.
For a single-cell fix, double-click the Actual Pieces cell on the operation row in the Job View grid to open the Quick Log popup instead of the full dialog.
Step 4: Save
Click Save. If you changed values that had already been reported, a reason is required and an empty reason cancels the save.
What Changes When You Save
| Surface | Effect |
|---|---|
| Daily actual pieces on the operation | Stored beside the plan, never over it |
| Job View header and progress reports | Percent complete and remaining recompute from the roll-up |
| Rate column | Shows the observed pieces-per-hour ratio for days with both sides entered |
| Scrap reporting | Scrap totals and their reason codes feed quality analysis, separately from good pieces |
| The next reschedule | Logged values are history: the engine plans only remaining work forward |
How to Check It Worked
On the terminal, the counter reads what you expect and the shift handoff summary lists the day's good and scrap totals with recent pauses. On the planner side, open the operation's Log Actuals grid: the day's row carries the pieces, and the rate column shows the ratio against the hours logged for the same day. The Actual Live card for the step reflects the updated progress percentage.
Common Mistakes
- Expecting EDIT COUNTS to add. It replaces the run's totals. Type the number you want to end up with.
- Tapping pieces while paused or in setup. The counters will not move. Resume the run first.
- Counting scrap as production. Good pieces alone drive daily actual pieces, which is why a scrap-heavy day correctly shows low output.
- Hand-typing both hours and pieces on the same day while auto-calculation is on. With both values present, your numbers stand as entered. That is fine when deliberate and confusing when accidental.
- Leaving a stale pinned rate in place. If the rate no longer matches how the step actually runs, derived values on the other side will be wrong every time.
Next Steps
Hours are the other half of the same grid: how to enter actual hours for yesterday. Starting the run in the first place is how to start a job on the kiosk, and closing it out is how to complete an operation.
Browse the full task list on the EDGEBIC how-to hub. Bring one shift of real piece counts to a demo of EDGEBIC and we will run them through both paths.
Expert Q&A: Deep Dive
Q: Our operators count at shift end from a tally sheet rather than tapping. Does that break anything?
A: It costs you the within-shift picture and the scrap reasons, and it survives fine otherwise. A tally typed into EDIT COUNTS or the Manual Entry day grid produces the same daily actual pieces the taps would have. What it cannot reconstruct is which pieces were scrapped and why, because reason codes attach at the moment of the tap. If scrap analysis matters to you, the compromise that usually sticks is tapping scrap live (a handful of taps per shift) and entering good pieces at the end. Scrap is the low-volume, high-information side of the count. Good pieces are the high-volume, low-information side.
Q: The pieces we enter never match hours times the rate. Is that a data problem?
A: Usually not. It is the variance you built the count to see. With Auto Calc Hours unticked, hours and pieces are stored exactly as typed, and the observed ratio between them is kept alongside the routing's expected rate. A step rated at 2 pieces per hour that produced 18 pieces in 6 hours is running at 3, and the grid preserves that rather than smoothing it away. What to do about it depends on which number is right. If the shop consistently beats the routing rate, the routing is stale and every schedule built on it is pessimistic. If a single day is an outlier, the count or the hours are wrong. Look at the rate column across several days before you change the routing.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
