How to Scope a Utilization Report to a List of Jobs in EDGEBIC

The work center utilization report in EDGEBIC by User Solutions accepts a comma-separated list of job numbers, so one run can show exactly how much of each station's load belongs to one customer, one program, or one rush batch. The filter is precise about what it changes, and knowing the one thing it does not change is what keeps the numbers honest.

For the unfiltered report, see how to run the work center utilization report. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• The jobs are scheduled. The report reads the plan, so an unscheduled order contributes nothing.
• You have the exact job numbers to hand, ideally copied from the Drive Schedule grid rather than typed from memory.
• You know which question you are asking. This filter answers how much of a station these jobs consume, not whether the station is overloaded.

Step 1: Open the Report

Open Reports from the main navigation and click the Work Center Utilization tile in the Diagnostics group. This is the heavyweight capacity report and the authoritative one, because its available hours come from the real shift calendars and any per-day overrides rather than an approximation.

Step 2: Enter the Job List

The report prompts for its parameters before it loads. In the job field, type the job numbers separated by commas:

JOB-2026-0101,JOB-2026-0102,JOB-2026-0103

Points that matter:

• Matching ignores case, so the numbers do not have to match the grid's capitalization.
• Empty entries between commas are ignored, so a trailing comma is harmless.
• Type the numbers exactly as they appear on the order, with no extra characters. A number that does not match contributes nothing and raises no error.

Set the date range in the same prompt, then load.

Step 3: Read What the Filter Changed

Every schedule-derived figure now reflects only the jobs you listed. That includes the per work center rows, the daily heatmap, the top jobs by load, and the plan against actual comparison. The KPI strip at the top reflects the same filter.

The report keeps its four tabs, so a filtered run is still a full lens:

Step 4: Read the One Number the Filter Does Not Change

The available hours denominator is always plant-wide. It is not reduced to the filtered jobs, and it should not be, because capacity belongs to the station rather than to a customer.

The consequence is direct: utilization percentages on a filtered run read low, and they are not a statement about how busy the station is. A mill that is genuinely at 96% for the window will show a small percentage when only three jobs contribute the numerator. That number means those three jobs consume that share of the station's capacity, which is a useful figure and a different one.

When somebody asks whether a station is overloaded, clear the filter and run again.

Step 5: Export the Pair

If the filtered run is driving a conversation, export both the filtered and the unfiltered run for the same date range. Use Export to Excel (the export routine is the same for every report) for the full workbook, which carries the per work center rows, the heatmap, the top jobs, the plan against actual comparison, the capacity waste view, and a flat backlog detail with every operation's timing parameters. Reports are point in time, so a dated export is what makes the picture provable next week.

What Changes When You Run It

Nothing in the plan. Every report in the catalog is read-only and queries fresh when you open or reload it, holding nothing in the background. Your column layout on the grid persists per user and is restored next time, but the data itself is never cached.

How to Check It Worked

Pick one work center row and drill into its backlog. Every job listed should be one of the numbers you typed. If a job you did not list appears, the filter did not take, which usually means the numbers went into the wrong field on the prompt. If a job you did list is missing, check its spelling and then widen the date range before assuming anything else.

Common Mistakes

• Quoting a filtered utilization percentage as a load figure. The denominator is plant-wide, so the percentage understates the station.
• Adding spaces after the commas out of habit. Type the list cleanly and the entries match reliably.
• Filtering to diagnose an overload. Run unfiltered for that, then filter to attribute it.
• Comparing a filtered run against an unfiltered one from a different date range. Hold the range constant or the comparison means nothing.
• Using the lighter performance report for capacity. Its available-hours figure is an approximation that ignores shift calendars, so when the two disagree, the utilization report is the authority.

See how load, capacity, and the plan stay in one system on the EDGEBIC product page.