- Home
- Blog
- Glossary (EDGEBIC)
- What Is Work Center Efficiency in Scheduling?
Work center efficiency is the percentage of a machine's nominal, rated capacity that it actually delivers in practice. A machine seldom produces exactly what its nameplate promises, and efficiency captures the gap. It is a description of the machine rather than of the plan, and a schedule is only trustworthy when it is built on the real figure. EDGEBIC by User Solutions gives you two honest places to record that figure, both of which the engine reads on every run.
How it works
Efficiency is a ratio: delivered output over rated output. At 100%, the machine delivers its full rating. Below 100%, it delivers proportionally less, so an older machine consistently running at 85% of its rating needs more time for the same work than its nameplate suggests.
The important thing is that efficiency describes the machine's running speed, not how busy the plan keeps it. Two quite different ideas turn a shift into a finish date. Efficiency is one: how much of its rated speed the machine actually delivers, which decides how long the work takes. Available hours is the other: how much of the clock the machine offers before any job is placed, which decides how much fits in a day. Keeping them separate stops one number from doing two jobs, and it is why the fix for a too-tight plan differs depending on which is really binding.
Because efficiency scales the work, it shapes finish dates quietly. The same routing on a full-speed machine and an 85% machine will not finish at the same time, and that is the point: the plan reflects the real difference between the two.
A concrete example
Think of a copier rated at 40 pages a minute that, in daily use, reliably turns out 36. It is not broken and it is not idle; it simply delivers 90% of its rating when it runs. That 90% is its efficiency. If you planned a big print run assuming 40 a minute, you would come up short every time. Planning at 36 a minute matches reality.
Now compare that to whether the copier is busy at all. It might sit unused for hours, then run a job at its honest 36 a minute. Its efficiency is still 90% whether the job lasts five minutes or five hours; how much of the day it spends running is a separate question, and that is utilization, not efficiency.
In the plant, an older mill rated identically to a newer one but delivering 85% of that rating should be planned at 85% of the newer mill's speed. Scheduled work then takes longer on it, and the finish date is honest instead of optimistic.
How EDGEBIC uses it
There is no efficiency field on the work center edit dialog in current releases, and the documented capacity formula for a day is shift hours less downtime and holiday overlap, multiplied by the instance count and by a utilization percentage that itself sits at 100%. So a machine's real speed is recorded where the engine will actually read it:
- In a work center group, where each member row carries its own factor. That factor multiplies the step's base run hours for work bound to the group, and it is never applied to setup, which is why a member with a genuinely different changeover gets a setup override of its own instead. The step-by-step is in how to add a machine to a pool.
- On the routing step, for a machine that is not part of a pool. The step's per-piece time is what every job through it is sized from, so entering the rate the machine really sustains is the whole of the job.
Where planning headroom belongs instead of a percentage is covered in how to set work center efficiency in EDGEBIC, the arithmetic behind rating and delivered output is in production efficiency calculation, and the way shifts, holidays, and downtime combine into a day's usable hours is in how EDGEBIC calculates work center capacity.
Because a slower machine consumes more hours for the same work, an honest speed figure ripples into every downstream number: the finish dates on the Gantt, the load in the capacity views, and the utilization that reads off them. Record it truthfully and the whole plan calms down, because it stops promising nameplate speed the floor never hits.
The related choice of what unit that capacity is even measured in, time or output, is the companion term capacity type. For the wider vocabulary, see the manufacturing glossary, and to see the difference inside a live plan, explore EDGEBIC.
Expert Q&A: Deep Dive
Q: Our old mill is rated the same as the new one but never keeps up. How do I stop the schedule from over-promising on it?
A: Put the two mills in a work center group and give the old mill a factor above 1.0 on its member row. A factor of about 1.18 on a mill that delivers roughly 85% of the new one's output stretches its run hours accordingly, so the same routing scheduled on either machine reflects the real difference between them instead of pretending they are identical. Setup is never scaled by the factor, so if the old mill genuinely changes over differently, give it a setup override on the same row. If the mill is not interchangeable with anything and always runs the same work, the simpler answer is to put its true per-piece time on that routing step.
Q: Should I lower efficiency to leave slack for breakdowns and changeovers?
A: No, and not only because there is no field to lower. Efficiency should describe how fast the machine runs when it is running, never how much of the week you want to reserve, because folding the two together makes both numbers unreadable. Planned slack belongs in the calendar: define the shift as the genuinely productive window, add a downtime event for losses that recur on a known pattern, or set a per-day capacity override on the dates concerned. Each of those leaves the run estimates truthful while shrinking the hours the engine may book, and each carries a visible reason the next planner can read.
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
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.
