- Home
- Blog
- EDGEBIC Platform
- EDGEBIC Reports Explained: 18 Answers to the Week'…
EDGEBIC Reports Explained: 18 Answers to the Week's Real Questions
EDGEBIC by User Solutions ships 18 built-in report panes on one hub screen, grouped into four families that match the four questions a production week actually asks: what is happening now, what changed, how are we performing, and is the schedule itself healthy. Every report is point-in-time. It queries fresh when you open it, holds nothing running in the background, and caches nothing between opens. This guide is the catalog: what each family is for, which report answers which question, and the two or three rules that keep everyone in the plant reading the same numbers the same way.
The reports are the drill-down layer beneath the dashboard cockpit. Dashboards tell you something is wrong in one glance; reports tell you which job, which machine, which hour, and who moved it. If you want the mechanics of running and exporting them, that lives in the step-by-step setup guide.
The Hub: Four Families, One Screen
Open Reports from the main navigation and you get one tile per report, each with its own small print naming its default range and filters. The tiles sit in four groups, and the grouping is the fastest way to learn the catalog.
| Family | The question it answers | Reports |
|---|---|---|
| Operational | What is happening on jobs and stations, day to day? | Job Audit Trail, Sales Order Progress, Daily Production, Shift Production, Job Progress, Work Center Progress, Work Center Dispatch |
| Supervisor / Planner | What changed, and what is late? | Reschedule History, Resource Replacement Audit, Late Jobs, Work Center Performance |
| Executive / KPI | How are we performing? | Earned Value (EVM), OEE, On-Time Delivery, BOR Change History |
| Diagnostics | Is the schedule itself healthy, and where is capacity leaking? | Scheduler Anomalies, Work Center Utilization, BOR Optimization Suggestions |
Shops running the inventory feature set also see a Stock on Hand report, which reads on-hand quantity from the inventory ledger rather than a cached field and sorts shortages first.
Every one of them opens in the same shell: a title, a subtitle carrying the headline numbers, the data grid, and four buttons (Column Details, Export to PDF, Export to Excel, Close). Date-ranged reports show a Select date range dialog first. Learn one report window and you have learned all 18.
Which Report Answers Which Question
This table is the one worth pinning next to the planner's desk. It is the catalog reorganized by intent rather than by menu position.
| You want to know | Open |
|---|---|
| What should this station run next? | Work Center Dispatch |
| Which jobs are late, and which is worst? | Late Jobs |
| Is this job on budget and on schedule (SPI and CPI)? | Earned Value (EVM) |
| How far along is each job right now? | Job Progress |
| Which steps of a job are behind? | Work Center Progress |
| How is a customer's whole order doing? | Sales Order Progress |
| Did each station hit its planned rate yesterday? | Daily Production, plus Shift Production for operator context |
| Who moved this job, when, and why? | Reschedule History |
| Which jobs got moved to a different machine? | Resource Replacement Audit |
| Which machines are overloaded or idle? | Work Center Utilization |
| How effectively is a machine really running? | OEE |
| Are we delivering on time, and trending which way? | On-Time Delivery |
| Is the schedule data itself healthy? | Scheduler Anomalies |
| What routing changes would buy back the most hours? | BOR Optimization Suggestions |
| Which routing version was this job scheduled against? | BOR Change History |
| Everything that ever happened to one job | Job Audit Trail |
The Operational Family: The Daily Loop
Work Center Dispatch is the one supervisors touch every morning. It lists every operation whose planned window overlaps the range you set, grouped by work center with groups auto-expanded, ordered by planned start. Material-only rows are excluded because material does not queue at a machine. The column that earns its place is Remaining Hours: required hours minus actual hours, floored at zero, so an operator picking up a half-finished operation reads the truth rather than the original estimate. Set the range, pick the station, export to PDF, hand it over.
Daily Production answers "did we hit rate yesterday?" with one row per day and work center: planned hours, actual hours, variance, adherence percentage, and jobs touched. Shift Production is the same lens with an operator count drawn from kiosk punches and a plain-language badge on each row ("on rate", "-1.5h", "+2.0h overtime"), which makes chronic over-runners obvious at a scan.
Job Progress is a snapshot of every job with no date range, and it carries one rule worth knowing: a job reads Completed only when every operation step has an actual end date. Marking one early step complete does not flip the job, and the finish date stays empty until the last step is done. Percent complete is hours-first (actual divided by planned), falling back to pieces only when no hours exist. Work Center Progress is the step-grain companion: when Job Progress says 60%, this tells you which steps make up the missing 40%.
The Executive Family: Performance With Formulas
The KPI reports are where acronyms live, and each is a real formula rather than a vibe. The deep dive on the on-time family works the arithmetic; here is the map.
Earned Value (EVM) measures every active job in hours. BAC is total planned hours, PV is hours planned to be done by the cut-off, EV is plan times percent done, AC is hours actually logged. From those come SPI (EV divided by PV, below 1.0 means behind schedule) and CPI (EV divided by AC, below 1.0 means burning more hours than earned), then EAC and VAC forecast the landing point. Rows sort worst SPI first, so trouble is at the top. Dollar columns appear on their own once work centers carry an hourly rate.
OEE is availability times performance times quality per work center. Availability is actual hours over shift-available hours. Performance is actual pieces over theoretical pieces derived from the routing's cycle time. Quality is good pieces over good plus scrap plus rework, which requires kiosk punches. Without punches, Quality and therefore OEE read "n/a" rather than a fabricated 100%. If you need the concept before the product view, our OEE explainer covers the generic metric.
On-Time Delivery judges finished jobs by their actual end (On time or Late) and unfinished jobs by their scheduled end (On track or Forecast late), so the same report is both a scorecard and an early-warning list. It pairs naturally with the generic on-time delivery KPI guide.
The Diagnostics Family: Before You Blame the Scheduler
Scheduler Anomalies runs 22 automated checks across seven categories against the current schedule: inverted actual dates, orphaned hour rows, duplicate allocations, dependency violations, off-calendar bookings, inventory drift, and more. The top strip shows one chip per check with a count; click a chip to filter the grid to that check's rows, click again to clear. Severity is Critical (physically impossible or corrupt data) or Warning (likely a problem, possibly explainable). Run it after bulk imports, major routing edits, and upgrades, and always before escalating a "the scheduler is wrong" report. Our troubleshooting guide organizes the same territory by symptom.
Work Center Utilization is the heavyweight and the capacity authority: a KPI strip plus four tabs (per work center with a job backlog drill-down, a 14-day daily heatmap, top jobs by load, and plan versus actual variance). Its ratings are fixed bands: CRITICAL above 100%, HIGH 85 to 100, GOOD 60 to 85, LOW 30 to 60, IDLE below 30. For the department roll-up of the same numbers, see department capacity analysis; when a station shows red, work center overload causes and fixes is the triage.
BOR Optimization Suggestions ranks what to change in your routings to recover hours, across seven rules: excessive wait gaps, lot-streaming opportunities, unflagged bottlenecks, one-per-day waste, alternates configured but never used, parallel processing left unspecified, and the queue-time plus flow-step conflict. It suggests only. You review, edit the routing, and re-run the schedule.
Three Rules That Keep Everyone Honest
Utilization outranks Performance for capacity. Work Center Performance approximates available hours with a coarse 24-hour formula; Work Center Utilization computes them from real calendars and per-day overrides. Quote the second one in a capacity meeting.
Reports are only as good as your actuals. Daily and Shift Production, the actual-cost half of EVM, OEE's Quality factor, and every percent complete depend on logged hours and punches. A blank report is usually a logging habit, not a bug.
Export the evidence when a report drives a decision. Reports are point-in-time; tomorrow's picture differs. When a report justifies moving a job or adding a shift, export the PDF into the job's records so the decision keeps its arithmetic.
A Ten-Minute Investigation
Monday morning, a customer asks about a 200-piece order due on the 28th. Late Jobs shows it four days late at 38% complete with the hint "Significantly behind plan". Job Progress confirms 38% and shows the daily pieces track flat since Wednesday. Work Center Progress, filtered to that job, points at the mill step: 41 of 101 hours, nothing logged in three days. Reschedule History shows one row, a four-day push on Thursday from an automated run. Work Center Utilization shows that mill at 104%, and its backlog drill-down names the two rush jobs inserted ahead. Four reports, ten minutes, and the conversation with the customer now contains a cause and a plan instead of an apology.
That loop is the whole point of the catalog. For the wider system these reports observe, start with the complete EDGEBIC guide; for the outcomes they measure, see the documented results and the generic manufacturing KPI reference.
Want to see these reports over your own orders? Bring an export to a demo and we will run your jobs through the catalog.
EDGEBIC ships 18 built-in report panes grouped into four families on one hub screen. Operational covers job audit trail, sales order progress, daily production, shift production, job progress, work center progress, and work center dispatch. Supervisor and planner covers reschedule history, resource replacement audit, late jobs, and work center performance. Executive covers earned value, OEE, on-time delivery, and BOR change history. Diagnostics covers scheduler anomalies, work center utilization, and BOR optimization suggestions.
Work Center Dispatch is the run queue you hand each station. It lists every operation whose planned window overlaps your chosen date range, grouped by work center and ordered by planned start, so top to bottom is the run sequence. It defaults to today through plus 14 days, excludes material-only rows, and carries a Remaining Hours column so an operator knows what is genuinely left on a half-run operation.
No. Every report is point-in-time: it queries the database fresh when you open it and again when you reload with new filters, and nothing runs in the background between opens. Reports are read-only, including the anomaly scanner, so running one during production changes nothing. Your grid layout persists per report and per user; the numbers never do.
Because one approximates available hours and the other computes them. Work Center Performance estimates capacity as 24 hours times days times instances times efficiency, which ignores shift calendars, weekends, and holidays. Work Center Utilization derives available hours from the real shift calendars and per-day capacity overrides. When they disagree, Work Center Utilization is the authority; Performance is for quick trend comparison only.
Expert Q&A: Deep Dive
Q: A customer just called about a job. Which reports do I open, in what order, to answer honestly in ten minutes?
A: Four reports, in this order. Late Jobs tells you whether the concern is real and by how many days, with a percent complete and a blocker hint such as 'Significantly behind plan'. Work Center Progress, filtered to that job, tells you which step is stuck: a step showing 41 of 101 hours with nothing logged in three days is your answer. Reschedule History over the last seven days shows whether the job was pushed, by whom, and whether a reason was entered. Work Center Utilization then shows whether the machine that holds it is at 104% because two rush jobs were inserted ahead of it. That sequence turns 'we are looking into it' into a date with arithmetic behind it.
Q: We just started with EDGEBIC and half the reports are empty. Which ones work before we log any actuals?
A: Everything that reads the plan works on day one: Work Center Dispatch, Late Jobs, Work Center Utilization, the daily heatmap, and BOR Optimization Suggestions all run purely off the schedule. What stays empty is everything that compares plan to reality: Daily Production, Shift Production, and Earned Value's actual-cost column need logged hours, and OEE's Quality factor plus the operator counts need kiosk punches with good, scrap, and rework pieces. That is deliberate: OEE shows 'n/a' rather than inventing a 100% quality figure. Report quality equals actuals discipline, so start logging hours in week one and the second half of the catalog lights up.
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 an Open EDGEBIC Screen Notices Someone Else's Edit
On a shared database, a change made on one workstation reaches every other open screen within a few seconds, without anybody pressing anything. How the change signal works and why your selection survives it.
What Changes When EDGEBIC Moves to a Shared Database
Moving EDGEBIC from one workstation to a shared SQL Server changes three assumptions at once: who may overwrite whom, how an open screen stays current, and who may run the scheduler.
What the EDGEBIC Refresh Button Actually Does
The refresh button forces a full re-read from the database, which is not the same as closing a screen and reopening it. Why the distinction matters on a shared database, and when to press it.
