How to Capture Hours or Pieces for a Work Center in EDGEBIC

There is no kiosk entry mode to set in EDGEBIC by User Solutions. The terminal captures both measures at every machine: during a run the elapsed clock advances on its own, and the good and scrap counters are there to tap. Which measure becomes the recorded truth for an operation is decided when the day is logged, through the Auto Calc Hours control in the daily actuals grid, not by a per-machine setting.

If you came here looking for a field on the work center editor, this page saves you the search and shows you the controls that genuinely govern hours-versus-pieces capture.

Before You Start

• You know how the work is naturally measured at this machine: by elapsed time, by piece count, or by both.
• The operation has a routing step, because the pieces-per-hour rate that connects the two sides lives there.
• You understand this is about capture, not about scheduling. Changing which side you record does not change how a job plans.

Step 1: Check How the Machine Is Measured

Open the Workcenter tab and read the grid. Capacity Type shows Hours, Pieces, or Both, and Unit of Measure sits beside it. Both are read-only columns: they tell you what constrains this machine, and they are not edited on the work center dialog.

Hours means the machine is planned by time, which is the normal case. Pieces means it is planned by output rate. Both means whichever constraint binds first wins, so a slow line is never over-promised.

Step 2: Set the Rate on the Routing Step

Piece-rate math is configured on the routing step that runs at the work center, not on the work center record. That is where the pieces-per-hour figure and any batch sizing belong, and it is the number every later conversion uses.

Getting it right matters beyond this task, because the same rate is what the scheduler reserved capacity with. See how to choose the pieces per hour rate for actuals, and if the machine should be planned by output rather than time, how to schedule a work center in pieces instead of hours.

Step 3: Let the Terminal Capture Both

Nothing to configure here, which is the step people expect to be hard. During a run the terminal shows an elapsed run time clock that advances on its own, plus a green GOOD counter and a red SCRAP counter with tap zones.

Two behaviors are worth telling operators about. Pieces only count during a run punch, so a counter that will not increment usually means the operator is still in setup or paused. And every scrap tap requires a reason, chosen from the machine, material, quality, or waiting categories, which is what keeps scrap out of the produced quantity and makes the resulting analysis usable. The walkthrough is how to record a piece count.

Step 4: Choose the Side When You Log the Day

The daily actuals grid is where the convention is actually expressed. It has one row per day with the scheduled hours and pieces, the actual hours and pieces, and the rate. The same grid appears in the planner's Log Actuals dialog and in the terminal's manual entry.

• Leave Auto Calc Hours ticked to type one side and let the other derive from the rate. Enter six hours on an operation rated at two pieces per hour and twelve pieces fill in, or enter the pieces and the hours derive.
• Untick Auto Calc Hours to record both sides independently, when the gap between a measured time and a measured count is the signal you want.

Pick the side your shop genuinely counts and stay consistent within an operation. A job with some days typed on the hours side and others on the pieces side produces an effective rate that describes nothing.

What Changes When You Save

The day's hours and pieces are stored next to the plan, never over it. Whichever side you typed, both numbers end up in the same daily record, so the schedule, the Job View, and the reports read them uniformly. Nothing about capacity, routing hours, or shift assignment changes, so a plan built before and after is identical.

How to Check It Worked

1. Open the operation's daily grid and confirm the day carries the number you meant to record, with the scheduled figure beside it for comparison.
2. Read the rate column for that day and the effective rate below the grid. In a derived entry it matches the planned rate; in a both-recorded entry it is the ratio your two numbers produced.
3. Check the Job View operation row, which carries the actual hours, actual pieces, and the rate together.

Common Mistakes

• Hunting for an entry mode field. It does not exist on the work center dialog, and the terminal does not vary its display by machine. The control you want is Auto Calc Hours in the daily grid.
• Trying to edit Capacity Type in the editor. It is read-only in the grid. Configure piece-rate behavior on the routing step instead.
• Typing both sides inconsistently. Mixing hand-entered values on both columns across some days and not others is the most common cause of a rate nobody recognizes, and it is far more likely than a real production problem.
• Expecting a scheduling effect. How you capture actuals does not change how work plans. If a plan looks wrong, look at the routing hours, the rate, and the shifts.

Next

To stand a terminal up in the first place, read how to set up a shop floor kiosk. For the full entry flow from the planner side, read how to log actual hours and pieces, and for the concept behind hours-versus-pieces conventions, what is an actual entry mode. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at EDGEBIC.