How to See Daily Production Totals in EDGEBIC

The Daily Production report in EDGEBIC by User Solutions is in the Reports hub under Operational: give it a date range and it returns planned hours, actual hours, variance, adherence and jobs touched for every work center on every day in the window. It is the "did we hit rate yesterday" check, and run the same day it is also the fastest way to catch a bad actual before it poisons the month's numbers.

For the wider report catalog, see EDGEBIC reports explained. To break the same planned-versus-actual figures down by shift instead of by day, see how to see shift production totals. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Actuals are being logged. The report totals logged hours, so an unlogged day is an empty day.
• Jobs are scheduled, so there is a plan to compare against.
• Kiosk punches are flowing if you want the operator count that the companion Shift Production report adds.

Step 1: Open It and Choose the Days

Open Reports and click Daily Production in the Operational group. Set From and To, then OK.

The window depends on the question:

Step 2: Read One Row

Each row is one day on one station.

The grid sorts by date descending, then by station, so the most recent day is at the top.

One thing to know about planned hours: it is the per-day planned allocation the scheduler wrote, not the routing estimate for the whole operation. A day showing zero planned but some actual means work was logged against a day the plan did not book, which happens after a manual punch with no matching schedule.

Step 3: Scan Adherence First

Adherence is the fastest column to read. A cluster near 100% is a station tracking its plan. A run of low numbers on one station is chronic under-running worth investigating. Anything above 100% is overtime or an over-log, and the two are worth telling apart.

Because adherence is capped at 200, a row reading exactly 200 is not "twice the plan" precisely; it is "at least twice, and the report stopped counting". On a normal operation that is almost always a data error rather than genuine output.

Step 4: Use It as a Same-Day Data Check

The highest-value use of this report is catching bad actuals while they are still fixable. Each afternoon, run it for today only and look for two patterns:

• Zero actual on a station that ran. Punches are not being submitted for that station. Fixable while the operator is still on shift and remembers the day.
• Adherence well above 150%. Usually a duplicate punch or a clock-entry slip, not genuine over-delivery.

A data error found today is a correction. The same error found at month-end is an argument in a meeting, which is why the afternoon scan pays for itself. It also protects everything downstream: the same actual hours feed the OEE report, so a doubled adherence today becomes a distorted availability figure tomorrow.

Step 5: Add Operator Context With Shift Production

For the same day-by-day hours plus a count of operators from kiosk punches, open the Shift Production report in the same Operational group. Each row carries a status badge (on rate, a shortfall, or overtime) that makes chronic over- and under-running stations jump out.

A note on that report: the shift name reads Combined, because it groups by day and station rather than by individual shift. Operator count comes from punches, so a station showing hours but zero operators means the hours came from schedule actuals rather than kiosk punches, which is a kiosk-adoption gap rather than an empty machine.

What Changes When You Run It

Nothing. Both reports are read-only and query fresh each time.

What the report changes is behavior: catching a zero-actual station or a doubled adherence today means the correction happens while the shift is still on the floor, before the bad number flows into OEE, earned value, and every percent complete downstream.

How to Check It Worked

After a same-day correction, re-run Daily Production for today. The station that read zero actual should now carry hours, and the row that read 200 adherence should fall to a believable number once the duplicate punch is removed. If the numbers have not changed, the correction did not land, usually because the punch was edited but not saved, and the row will still show the error.

Common Mistakes

• Reading a capped 200 as the true over-delivery. The cap hides how large the over-log actually was. Investigate any 200.
• Treating zero actual as an idle machine. On a station that ran, zero actual is a logging gap, not a breakdown.
• Comparing planned here to the routing estimate. Planned hours is the scheduler's per-day allocation, not the whole-operation estimate.
• Skipping the same-day check. Actuals found wrong at month-end cannot be fixed with the operator's memory. Run it daily.

See how logged actuals flow into the whole reporting layer on the EDGEBIC product page.