The shift production report in EDGEBIC by User Solutions lives in the Reports hub: it takes a date range and returns planned versus actual hours, pieces, and an operator count for each work center per day, each row carrying an on-rate status badge. It is the daily production picture with the people added: how much a station ran, how much it made, and how many operators were on it.
It shares its source data with daily production totals and adds the operator count on top, so read that first for the base view and this for the staffing layer. Both depend on hours and punches being logged, which is covered in logging actual hours and pieces. Every task in this library is mapped on the EDGEBIC how-to hub.
Before You Start
- Actual hours are being logged. The report compares planned against actual, so an unlogged shop shows planned hours only.
- Operators are punching in through the kiosk if you want the operator count to populate. The count comes from punches, not a roster.
- You know the window you want. The report takes a From and To date range.
Step 1: Open the Report and Set the Window
Open Reports from the main navigation and click the Shift Production card. A date range dialog appears. Set the From and To dates, then click OK. The report groups production by work center and day and builds one row per station per day.
Step 2: Read a Row
Each row is one station on one day:
- Planned hours and actual hours, the plan against the logged reality.
- Actual pieces, the output logged for that station and day.
- Operator count, the number of distinct operators who punched in on that station.
- Status badge, a quick read of the hours gap: on rate when actual and planned are within a quarter hour, a negative figure when the station logged fewer hours than planned, or an overtime figure when it ran longer.
Step 3: Use the Status Badge for End-of-Day Triage
Run the report for today only and scan the status badge column. On rate is the healthy majority. The rows that read a shortfall or overtime are your handful of stations to ask about while operators are still on shift and the answer is fresh. A shortfall usually means a late start, a breakdown, or unlogged time; overtime means genuine extra hours or a duplicate punch.
Step 4: Correlate Staffing With Output
Sort by operator count to compare output on low-staffing days against high-staffing days on the same station. Where the operator count reads zero next to real hours, you have found a station whose time is being captured without kiosk punches, which is a usage gap to close rather than an idle machine.
Understanding the Combined Shift Label
Every row currently labels the shift as Combined, because the report groups by work center and day rather than by named shift. The totals are accurate; they are simply not yet split across your first, second, and third shifts in separate columns. For a per-shift read today, narrow the date window and cross-reference your shift calendar. The Combined row still gives you the day's planned-versus-actual story per station.
How to Check It Worked
The report is read-only, so nothing is saved. Confirm it worked by checking a station where you know both the hours and who ran it: the actual hours and operator count should match your expectation. If the operator count is zero on a station you know was staffed, the operators were not punching in through the kiosk.
Common Mistakes
- Reading a zero operator count as an empty station. The count comes from punches. Hours without operators is a kiosk gap, not idle time.
- Expecting per-shift columns. Output rolls into a Combined row per station per day. Narrow the window for a per-shift read.
- Ignoring the status badge. It is the fastest triage signal on the report. The not-on-rate rows are where the day's questions are.
- Running a wide window for end-of-day checks. For same-day correction, set the window to today only so the rows reflect the shift you can still ask about.
Related Reading
- How to see daily production totals: the base production view this report adds operators to.
- How to log actual hours and pieces: the punches that feed the operator count.
- EDGEBIC platform overview: where shop-floor reporting fits in the wider system.
Expert Q&A: Deep Dive
Q: A station shows real actual hours but an operator count of zero. Which is wrong?
A: Neither is wrong; they come from different sources and the gap between them is the finding. Actual hours can be written from schedule actuals, while the operator count only comes from kiosk punches that carry an operator name. So a station with hours but no operators means the time was captured without anyone punching in through the kiosk. That is worth chasing, because the operator count is what makes the rest of the report, staffing efficiency and accountability, meaningful. Treat it as a prompt to tighten kiosk usage on that station rather than as a data error. Once punches are flowing, the operator count fills in and you can start correlating staffing against output.
Q: How do I use the status badge to catch problems at the end of the day?
A: Run the shift production report for today only and read down the status badge column. On rate means actual and planned hours are within a quarter hour of each other, which is the healthy majority. A negative badge means the station logged fewer hours than planned, which usually points at a late start, a breakdown, or unlogged time. An overtime badge means it ran longer than planned, which is either genuine overtime or a duplicate punch. Scan for the badges that are not on rate, and those are your handful of stations to ask about while the operators are still on shift and the answer is fresh.
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
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.