How to Run, Filter and Export Reports in EDGEBIC

Running a report in EDGEBIC by User Solutions is the same four steps every time: open the hub, click a tile, set the range or filter it asks for, and read the grid, with Export to PDF and Export to Excel one click away in the same window. The catalog is large and the shell is small on purpose. Learn one report window and you can operate all 18. This guide covers the mechanics: filters, defaults, the empty state, layout persistence, and what actually lands in a multi-sheet workbook.

If you want to know which report answers which question first, start with the report catalog overview. For the columns inside them, Column Details explains every field in place.

Step 1: Open the Hub and Pick a Tile

Reports live behind one entry in the main navigation. The hub shows one tile per report under four group headers (Operational, Supervisor / Planner, Executive / KPI, Diagnostics), and each tile's small print tells you what it will do before you click: its default range and which filters it offers. A tile reading "Default range today to +14 days, work center filter defaults to all" saves you a wrong-range reload.

Nothing here is running in the background. Reports load on demand and query fresh each time, which is why the hub is quick even on a busy schedule.

Step 2: Answer the Range Dialog

Date-ranged reports open the Select date range dialog first: pick From and To, click OK, and the report window opens and loads itself. A busy indicator runs while it queries.

Snapshot reports skip this entirely because they describe the plan as it stands right now. Job Progress and Late Jobs are the two you will use most in that mode, and Scheduler Anomalies takes only an optional job filter.

Sensible starting ranges, by intent:

Step 3: Use the Inline Filters

Several reports carry their own filters at the top of the window, and these re-query without you closing anything.

• Work Center Dispatch has From, To, and a Work Center dropdown. The dropdown lists every active work center whether or not it has work in the current window, so every station is selectable, and your selection survives a reload.
• Job Progress has a Show: All / Scheduled radio pair, so you can narrow to scheduled jobs without reopening the dialog.
• Scheduler Anomalies takes a job number, and its summary chips are themselves a filter: click a chip to narrow the grid to that check's rows, click it again to clear.
• Work Center Utilization and BOR Optimization Suggestions accept an optional job number alongside the date range.

One caveat worth remembering on the anomaly report: the inventory-integrity checks are plant-wide by design, so a job filter does not narrow them. They always scan everything.

Step 4: Read the Empty State Correctly

"No data in this window." is a result, not an error. It means the range and filters returned zero rows. Work through it in this order:

1. Widen the dates. The commonest cause is a range that misses the data entirely.
2. Clear leftover filters. A job number or work center left from the previous run is the second commonest.
3. Check the schedule exists. Reports read the plan; an unscheduled job appears nowhere.
4. Check the actuals. Daily Production, Shift Production, and every actual-hours column need logged hours. If work happened but the report is blank, hours are not being logged (log them from the Gantt right-click, or through the shop-floor kiosk).

That last one is the difference between a blank report and a blank habit. OEE behaves the same way and is honest about it: without kiosk punches carrying good, scrap, and rework pieces, its Quality factor and the OEE column read "n/a" rather than a fabricated 100%.

Step 5: Shape the Grid (It Sticks)

Every report grid is fully arrangeable: reorder columns, resize them, group, sort, hide what you never read. All of it is saved automatically per report and restored next time, with no save button. Layouts are per user and per machine, so if your carefully arranged Late Jobs grid looks default, you are on a different workstation or a different login rather than looking at a bug.

Data is never cached. Layouts persist; numbers do not. Reopen or reload to refresh.

Step 6: Export

Two buttons, two behaviours.

Export to PDF prints the primary grid as you have laid it out. This is the shift-start dispatch sheet, and the artefact to file when a report justifies a decision.

Export to Excel produces a spreadsheet of the grid for most reports, and a multi-sheet workbook for the two heavyweights:

The Backlog Detail sheet is the most useful page in the product for a capacity argument. It flattens every scheduled operation across all work centers with its setup hours, queue time, flow step, transit days, transfer batch size, and transfer delay, so you can see which throughput parameters are actually driving a station's load.

One export rule to remember: hidden columns are not exported. If you hid the currency columns last month and now need them in a costing workbook, unhide them first. The dollar columns in Earned Value only exist at all when at least one work center carries an hourly rate above zero; with every rate at zero, the report suppresses them automatically.

The One Setting That Changes Job-Level Numbers

If your routings use parallel work centers, one option changes what the job-grain reports count. A parallel step logs the same wall-clock work on every parallel machine, so a naive job total double-counts: a three-hour chain with a parallel sibling on each step reads as six.

Tick Primary hours only (exclude parallel) in Options, Schedule, and Job Progress, Earned Value, Sales Order Progress, Late Jobs, Job Audit, and End-Product Actuals all switch to counting the primary path. Per-work-center rows and cost stay full-effort by design, because the parallel machine really was occupied. That is why the sum of per-station hours can legitimately exceed the job total, and it is worth explaining once to anyone who reconciles the two.

A Weekly Rhythm Worth Adopting

Reports pay for themselves when they are habitual rather than forensic.

That cadence mirrors standard lean daily management practice, where a short daily review beats a long monthly one. The APICS and ASCM body of knowledge is the reference most planners already share for the underlying metrics; our own manufacturing KPI guide covers the generic definitions, and schedule adherence is the one to read before your first Daily Production review.

What to Do With What You Find

Reports observe; they never change the plan. When one exposes a problem, the fix happens elsewhere: move the work on the Gantt, adjust the routing in the designer, override a day's capacity on the work center, or re-run the schedule. Two neighbours help here. When the arithmetic in a report surprises you, report reading mistakes covers the traps that produce a wrong conclusion from a right number. When a station is red, work center overload causes and fixes is the triage list. And when you want the always-on version of the same data, the dashboard tabs are the glanceable layer above these reports.

For the full picture of the system generating all of this, the complete EDGEBIC guide is the pillar. Want to see your own jobs in these grids? Bring an export to a demo.