Glossary (EDGEBIC)

What Is Pieces Per Hour in Work Center Capacity? EDGEBIC Definition

User Solutions TeamUser Solutions Team
|
6 min read

Pieces per hour is a station's rated output speed: how many units it produces in one hour of running. In EDGEBIC by User Solutions, this is the figure that lets a station be scheduled in units rather than in clock time. What the plan is built on is the effective rate, the speed the line genuinely sustains, and that is the number the routing step should carry.

The everyday version: a copier rated at forty pages a minute that reliably turns out thirty-six. Forty is what the box says. Thirty-six is what you should count on when you promise someone their handouts.

For the broader vocabulary of planning, see the manufacturing glossary.

How Pieces Per Hour Works

Most scheduling is described in hours. A routing step says how many hours per unit an operation takes, multiply by quantity, add setup, and you have the claim on a machine.

That framing suits machining and assembly. It fits some equipment badly. A packaging line is not naturally described as hours per bag; it is described as bags per hour. A press is described in strokes. For those stations, output is the honest unit and hours are a derived quantity.

Pieces per hour is the rate that makes the honest description possible. It says what the station produces per hour of running, and from that the engine can work out how long a quantity takes rather than being told directly.

Two figures matter here, and confusing them is the most common mistake with this setting.

The rated speed is the nameplate: what the equipment does when material is good, the crew is up to speed, and nothing interrupts. It is a real number and it is not a planning number.

The effective rate is what the line sustains once changeovers, the ramp at the start of a run, and the occasional jam are inside the average. A line rated at five thousand bags per hour that delivers forty-five hundred over a shift is running at ninety percent of its rating, and forty-five hundred is the figure a schedule should assume. That is the number to enter on the routing step, using the converter beside the hours value if you think in pieces per hour rather than hours per piece.

Separately, the work center's capacity type decides what the station is scheduled against at all: hours, pieces, or both. It appears as a read-only column on the work center grid and is loaded through the work center import rather than typed on the edit dialog, and an honest rate on the step does not by itself switch a station to pieces-based scheduling. If both limits apply, whichever binds first constrains the plan, which suits equipment with a cycle limit and a second physical limit such as tonnage.

A Concrete Example

Packaging line, rated five thousand bags per hour. Job 42 needs sixty thousand bags packed.

On the rated figure that is twelve hours, comfortably inside two shifts. The plan says the job clears Tuesday.

The line does not sustain five thousand. Across a real shift, with changeovers, a jam or two, and the ramp at the start of each run, it averages forty-five hundred. That is ninety percent of its rating, and forty-five hundred is what its routing steps should carry.

Sixty thousand bags at forty-five hundred an hour is thirteen and a third hours, not twelve. On this one job the difference is under an hour and a half, which feels tolerable.

It is not tolerable, because it is not one job. Every job through that line is planned about eleven percent short. Across a week the shortfalls accumulate into a station that is quietly overbooked, work that spills into the next shift, and downstream operations whose start times were never real. The line is not underperforming; the plan was written against a number the line never claimed to deliver.

Scheduling on the effective rate makes the same line finish when the board says it will.

How EDGEBIC Uses It

Pieces per hour is the rate the capacity calculation sizes a piece-limited operation from:

  • It gives a station an output rate, so equipment naturally measured in units can be planned in units rather than in inferred hours.
  • It lives on the routing step, entered as a per-piece time, which is why the effective rate rather than the nameplate speed is what the plan is built on.
  • It works with the capacity type, which decides whether a station is scheduled on hours, on pieces, or on both with the binding limit constraining the plan.

For the value that chooses the unit, see what is capacity type in a work center, and for the routing step's own version of that choice, hours, pieces, or both with the binding limit constraining the schedule, see what is a requirement type in a routing step. For the difference between rated and delivered speed, and where each machine's is recorded, see what is work center efficiency in scheduling. To switch a station over, follow how to schedule a work center in pieces instead of hours.

Expert Q&A: Deep Dive

Q: My packaging line is always late even though the schedule says it fits. What should I check?

A: Check whether the line is scheduled on its rated pieces per hour or its effective rate. The rated figure is the nameplate number and almost no equipment sustains it across a shift. Open the routing steps that run on the line and read the per-piece time each one carries. If they were entered from the nameplate rather than from what the line actually delivers, every job through that station is planned a little short, and the shortfalls compound into consistently late work.

Q: My work center is measured in pieces but the schedule keeps showing hours. Why?

A: The station's capacity type is probably still hours. That value decides what the work center is scheduled against: hours, pieces, or both, with the binding limit constraining the plan when both apply. A piece requirement on the step is not on its own enough; the capacity type has to say pieces are what this station is measured in. It shows as a read-only column on the work center grid and is loaded through the work center import rather than typed on the edit dialog, so correct it there and re-import.

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

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.

Let's Solve Your Challenges Together