- Home
- Blog
- Glossary (EDGEBIC)
- What Is Adherence Percent on a Daily Production Re…
What Is Adherence Percent on a Daily Production Report? EDGEBIC Definition
Adherence percent on a daily production report is the actual hours logged for one work center on one day divided by the planned hours for that same cell, expressed as a percentage and capped at 200. One hundred percent means the day ran exactly to estimate. Below means the work took less time than planned, above means it took more. EDGEBIC by User Solutions computes it per date and per work center, so it answers a capacity question rather than a job question.
This entry is part of the EDGEBIC glossary series introduced on the platform overview; the wider vocabulary index sits in the manufacturing glossary. It is the daily, machine-level cousin of planned versus actual hours, and it should not be confused with schedule adherence, which measures something else entirely.
How Adherence Percent Works
Think of the estimate on a car repair invoice. The garage said four hours; the bill says four and a half. The ratio between those two numbers is not a judgment about whether the car was fixed, and it is not a judgment about whether the work started on time. It is a statement about how good the estimate was, or how the day actually went. Adherence percent is that ratio, computed for every machine on every day the shop logged hours.
The calculation groups the day's logged hours by date and work center. Every per-day hour record with actual hours above zero enters the group, planned and actual hours are summed across the group, and the ratio is taken:
- Adherence percent = actual hours divided by planned hours, times 100
- Variance = actual hours minus planned hours, the same story in absolute terms
- Jobs touched = how many distinct scheduled operations contributed to the cell
Two guards shape the output. The result is capped at 200 percent, because one badly estimated half-hour task can otherwise produce a four-figure percentage that swamps the column and hides the rows that matter. And when planned hours are zero the result is zero, not an error and not infinity.
That zero deserves its own attention. A row with real logged hours and a zero adherence reading is telling you that work happened on a work center where the plan expected none. Unplanned work is one of the most common reasons a schedule that looked achievable on Monday is behind by Thursday, and this is where it shows up first.
A Concrete Example
Take a three day window, Monday June 16 to Wednesday June 18, on a shop with two machines. The per-day hour records look like this:
| Date | Work center | Schedule | Planned h | Actual h |
|---|---|---|---|---|
| Jun 16 | Mill-1 | 10 | 8.0 | 7.5 |
| Jun 16 | Mill-1 | 11 | 4.0 | 4.0 |
| Jun 17 | Mill-1 | 10 | 8.0 | 8.0 |
| Jun 18 | CNC-1 | 20 | 6.0 | 9.0 |
Grouped by date and work center, the report reads:
| Date | Work center | Planned h | Actual h | Variance | Adherence | Jobs |
|---|---|---|---|---|---|---|
| Jun 18 | CNC-1 | 6.0 | 9.0 | +3.0 | 150% | 1 |
| Jun 17 | Mill-1 | 8.0 | 8.0 | 0.0 | 100% | 1 |
| Jun 16 | Mill-1 | 12.0 | 11.5 | -0.5 | 95.8% | 2 |
The June 16 Mill-1 row merges schedules 10 and 11 because they share a date and a machine, and the jobs column reports 2 so you know the row is a sum. Its 95.8 percent is the kind of number that needs no action: half an hour under across two jobs is normal shop noise.
June 18 is the row to read twice. CNC-1 logged nine hours against a six hour plan, three hours of overtime on a single job. Either the routing for that operation is estimated short, which means every future job through it is planned optimistically, or the day genuinely ran long. Those are different fixes, and the variance column is what prompts the question.
How EDGEBIC Uses Adherence Percent
The column lives on the Daily Production report, sorted by date descending and then by work center name, so the most recent day is at the top. Its close relative is the Shift Production report, which reads the same underlying hours but adds a plain-language status badge instead of a percentage: within a quarter of an hour of plan reads "on rate", short reads as the shortfall in hours, and over reads as the excess with an overtime note. Same data, two ways of asking about it.
Because the whole report is built from logged hours, it is empty until actuals exist. A report with no rows is not a report failure, it is a logging gap, and the fix is upstream at the point where hours are recorded rather than in the report itself.
Two habits make the column pay for itself:
- Scan for zeros before you scan for extremes. A zero row is unplanned work, which is a plan problem rather than an execution problem.
- Read variance beside adherence. Ninety-five percent on a twelve hour cell and 95 percent on a one hour cell are the same ratio and very different amounts of time. The variance column keeps the scale visible.
The step by step for running the report and choosing its date range is in how to see daily production totals.
Adherence percent is the actual hours logged on one work center on one day divided by the planned hours for that same cell, expressed as a percentage. One hundred percent means the day ran exactly to plan, below means it ran short, above means it ran long. EDGEBIC caps the value at 200 percent so one small mis-planned cell cannot dominate the column, and returns zero when there were no planned hours at all.
No, and the shared word causes real confusion. Schedule adherence is a dashboard metric counting operations that started within an hour of their planned start, so it measures sequence discipline. Adherence percent on the Daily Production report is an hours ratio for one work center on one day, so it measures effort against estimate. A shop can score 100 percent adherence percent while its schedule adherence is poor, because the right amount of work got done on the wrong day.
Because there were no planned hours in that cell. The formula divides actual hours by planned hours, and rather than divide by zero EDGEBIC returns zero for the row. A day with real logged hours and a zero reading is therefore telling you the work was unplanned on that work center, not that nothing happened. It is one of the most useful signals on the report, because unplanned work is usually the reason the rest of the schedule slipped.
Expert Q&A: Deep Dive
Q: One row reads 150 percent adherence. Should I be pleased or worried?
A: Worried enough to look. A row at 150 percent means a work center logged half again the hours its plan expected for that day, in the book's example nine actual hours against a six hour plan. Either the routing underestimates the work, in which case every future job through that step is planned short, or the day genuinely ran overtime, in which case the capacity your plan assumes is not the capacity you are using. Both are worth fixing and they are fixed in different places: the routing hours or the work center calendar.
Q: Two schedules on the same machine merged into one row. Was that a mistake?
A: No, that is the report's grain. Daily Production groups by date and work center, so every schedule that touched Mill-1 on June 16 collapses into a single Mill-1 row for that date, and the jobs count column tells you how many were involved. The planned and actual hours are summed across them before the ratio is taken, which is what you want for a capacity question. When you need the per-job breakdown instead, drop to the job-level reports rather than reading this one row by row.
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.
